Replies: 1 comment 4 replies
-
This is very confusing. The server worked well for several days and suddenly failed to schedule its eth txs. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Module Affected
Rust Version
1.74.0
Operating System
Issue Description
After starting the server service, when a batch is submitted, the transactions for ProveBatch and ExecuteBatch will be immediately generated and attempted to be sent in the eth_tx table (at this time, the calculation of the batch by the Prover has not yet ended), accompanied by a "replacement price" warning ending up "invalid quotient evaluation" in sepolia. I am quite certain that the use of nonce is correct. This is the scene.

To sum up, there are two questions: first, why are the transactions of provideBatch and executeBatch generated in advance? The second issue is the occupation of nonce.
proof is set to used instead of skipping.
Expected Behavior
the transactions for ProveBatch and ExecuteBatch are sent after prover jobs done.
Current Behavior
sending two wrong transactions.
Repository Link (if applicable)
No response
Additional Details
No response
Prior Research
Beta Was this translation helpful? Give feedback.
All reactions