Skip to content
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

Historical receipts are missing l1 data on snap sync nodes #270

Open
quickchase opened this issue Mar 16, 2024 · 0 comments
Open

Historical receipts are missing l1 data on snap sync nodes #270

quickchase opened this issue Mar 16, 2024 · 0 comments

Comments

@quickchase
Copy link

System information

op-geth version 1.101308.2-stable-0402d543

Expected behaviour

The response to eth_getBlockReceipts and eth_getTransactionReceipt should be identical regardless of sync method.

Actual behaviour

Snap sync nodes return null for l1 data and are missing the field l1FeeScalar entirely for historical blocks

Steps to reproduce the behaviour

Query:

{"jsonrpc":"2.0","id":1,"method":"eth_getBlockReceipts","params":["0x1234"]}

Result:

❯ diff <(jq --sort-keys . ~/tmp/snap.json) <(jq --sort-keys . ~/tmp/full.json)
13,15c13,16
<       "l1Fee": null,
<       "l1GasPrice": null,
<       "l1GasUsed": null,
---
>       "l1Fee": "0x4d0d1b312dc7a",
>       "l1FeeScalar": "1.5",
>       "l1GasPrice": "0x2b61b593ee",
>       "l1GasUsed": "0x12f2",

So the full sync full nodes have l1Fee and l1Gas data, but the snap sync node does not.

relevant op-geth flags:

--op-network=op-mainnet
--state.scheme=path
--history.transactions=0
--syncmode=snap
--gcmode=full
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

No branches or pull requests

1 participant