-
Notifications
You must be signed in to change notification settings - Fork 521
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
homa predeploy reverts for old blocks #2789
Comments
can't find anything interesting around that block so not exactly sure why it failed |
I believe it should be working not too long ago, since this code worked before, which starts indexing at block 4440289 |
oh nevermind I think the first tx being indexed is at block |
I will adjust the new indexer to start after |
yeah the block number is |
@xlc should we keep the issue open? It does look like a bug, just not blocking us for now |
The |
interesting, does homa fetch exchange rate from it? |
This Homa https://acala.subscan.io/extrinsic/4444103-2?event=4444103-11 you can check list here https://acala.subscan.io/event?module=evm&event_id=ContractPublished |
cool that makes sense |
it's odd that
homa.getExchangeRate()
reverts for old blocks, did some binary search and the boundary seems to be block 444102: it reverts before block 4444102 and works afterwards.I think we should already have homa up and running at block
4444102
, right?The text was updated successfully, but these errors were encountered: