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.

Sign up for GitHub

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

Jump to bottom

Handle both AEVM and FATE registry contracts #176

Open

mradkov opened this issue Nov 8, 2019 · 1 comment

Assignees

Labels

area/contracts area/lima area/tokens

Member

mradkov commented Nov 8, 2019

Implement check whether the contract called is using FATE or AEVM to determine which registry should be used.

mradkov added area/contracts area/tokens area/lima labels

mradkov mentioned this issue

Token registry contract #174

Open

Member Author

mradkov commented Nov 8, 2019 •

edited

Loading

Suggested steps:

call the middleware /contnracts/transactions/address/{address} to get the first transaction of the contract ContractCreateTx (eg. https://mainnet.aeternal.io/middleware/contracts/transactions/address/ct_QnzUd9dztc9ZKfK28kuHghr7wNo8X9P3x8bAvRu3FzSTnQG31)
look for the abi_version field

{
    "transactions": [
         {
            "block_height": 147705,
            "block_hash": "mh_....",
            "hash": "th_.....",
            "signatures": [ 
                "sg_...."
             ],
             "tx": {
                 "abi_version": 1,
                 "amount": 0,
                 "call_data": "..."
             }
          }
     ]
}

compare the ABI versions

petarbaykov self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment