-
Notifications
You must be signed in to change notification settings - Fork 44
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
Verifier fixes #205
Verifier fixes #205
Conversation
b2fdfbf
to
cb0e2ae
Compare
Could someone else try whether tx-repeater works alongside a sequencer compiled from this branch, because it does not work on my local setup. Tx-repeater itself it fine but the sequencer goes into infinite loop because it is unable to verify batches. P.S. I'm trying to repeat mainnet transactions. |
Looks like this is an issue with the stream itself, I get timeouts locally trying to sync from it. Will take a look |
I got either "erigon state root mismatch" if a tx is a funding (from our faucet wallet) or "error in response: EXECUTOR_ERROR_DB_KEY_NOT_FOUND" if a tx is a regular repeated mainnet tx. |
@kstoykov what if you disable the upstream executor? |
@hexoscott I drafted that until the known issue with erigon-to-erigon is fixed |
Tx-repeater works as expected by disabling the remote executor. |
I think there is a separate task here to make the datastream stage also async like the verifier which will solve the stream problems. At the moment the stream is only populating when you get block N+1 because we're waiting on verifications. Going to make this a proper PR now that erigon-to-erigon sync is working again. |
caused by us not sending the scalable details in the witness
05b0c9f
to
ef78e19
Compare
Quality Gate passedIssues Measures |
No description provided.