-
Notifications
You must be signed in to change notification settings - Fork 15
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
Database Inconsisteny for CallToIndex
MDBX Table
#57
Comments
This issue is stale because it has been open for 40 days with no activity. Remove stale label or comment, or this will be closed in 7 days. |
This issue is stale because it has been open for 40 days with no activity. Remove stale label or comment, or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
This issue is stale because it has been open for 40 days with no activity. Remove stale label or comment, or this will be closed in 7 days. |
This issue is stale because it has been open for 40 days with no activity. Remove stale label or comment, or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
This issue is stale because it has been open for 40 days with no activity. Remove stale label or comment, or this will be closed in 7 days. |
Background
Optimism Bedrock sets block header's coinbase as address of SequencerFeeVault:
0x4200000000000000000000000000000000000011
.CallToIndex
Table stores mapping(key: address, value: bitmap storing blocknumber which address tainted the block). Otterscan API(ots_searchTransactionsBefore
) searchesCallToIndex
and find block number, and trace transaction included inside each block.Bug
Although coinbase is included in
CallToIndex
, there is no transactions which caused coinbase to be included inCallToIndex
.Expected behavior
Coinbase address must not be inserted to
CallToIndex
Table. Need to find out the root cause and fix it.Mitigations
See #10. When inconsistency detected, do not progress and early terminate.
The text was updated successfully, but these errors were encountered: