-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question for C Chain Atomic transactions #343
Comments
The assetID is the hash of the transaction that created the asset on the X-Chain. Import/export transactions currently only support AVAX. ERC-20/ERC-721 tokens do not have an equivalent Avalanche Native Token representation, so they cannot be moved to the rest of the Primary Network. The requirement to move assets across the Primary Network is not to update contract state, but to communicate via Shared Memory: https://github.com/ava-labs/avalanchego/blob/master/chains/atomic/README.md. The current plan to support this by adding a shared memory precompile, which will require a contract to explicitly call the precompile to import/export an asset defined by a contract. |
yeah. makes sense. This requires special logic to exists in such ERC20/ERC721 to leverage precompile addresses. |
Just wanted to confirm that. Thanks. |
Re-opening until we update the documentation for import/export transactions, since I see this is not sufficiently clear here https://docs.avax.network/reference/avalanchego/c-chain/txn-format#gantt-evm-input-specification |
* fix trie metrics * add new prefetcher metrics * use flush item pointer * add warn if anything unexpected found in cache * simplify trieproc tracking * make DEBUG * nits
for Atomic transactions , I have following questions
it does feel that only AVAX can be imported / exported out of chain. As for ERC20/721 created within C-Chain, it would require modification to evm update contract state in a standard erc20/erc721 contract.
The text was updated successfully, but these errors were encountered: