Skip to content

disable log index validation for jovay#238

Merged
artemrootman merged 2 commits into
mainfrom
arootman/jovay-disable-log-index-validation
Jul 17, 2026
Merged

disable log index validation for jovay#238
artemrootman merged 2 commits into
mainfrom
arootman/jovay-disable-log-index-validation

Conversation

@artemrootman

Copy link
Copy Markdown
Contributor

Jovay numbers receipt logIndex per transaction instead of globally within a block, so the EVM log-index validator permanently marks any jovay upstream as fatal.

Verified against the public RPC — block 0xa35383, tx 0xb65be0ae831c293944697cf7e309853ddf44e66d18b7cdcf0de066407bd73f4d (txIndex 0x1) starts at logIndex: 0x0 even though the first tx in the block has 5 logs:

curl -s -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","method":"eth_getTransactionReceipt","params":["0xb65be0ae831c293944697cf7e309853ddf44e66d18b7cdcf0de066407bd73f4d"],"id":1}' https://rpc.jovay.io

This is chain-wide client behavior, not a broken node, so disable the validator for jovay — same as zeta-chain.

@artemrootman

Copy link
Copy Markdown
Contributor Author

CI was already red on main since #220 added support-finalized-block-tag/support-safe-block-tag for viction without updating the yamale schema — added both keys to the schema here, yamale passes locally now.

@artemrootman
artemrootman merged commit a2e634a into main Jul 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants