chore(prover-node): track estimated L1 fee when proof publishing is disabled#22691
Merged
AztecBot merged 1 commit intoApr 22, 2026
Conversation
spypsy
changed the title
PhilWindle
approved these changes
Apr 21, 2026
Collaborator
Flakey Tests🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry. |
AztecBot
force-pushed
the
spyros/a-929-track-proof-submission-fee-estimate-in-fisherman-prover-node
branch
from
6cbb288 to
340a470
Compare
…isabled When `PROVER_NODE_DISABLE_PROOF_PUBLISH=true` (as set on mainnet), the prover node previously finalized the proof and then silently dropped it. This PR changes that path to: - Run the same on-chain validation as a real submission (`validateEpochProofSubmission`) — catches public-input mismatches early - Encode the proof submission calldata and call `l1TxUtils.estimateGas` to get an accurate gas limit - Fetch the current gas price via `l1TxUtils.getGasPrice()` and the latest block's `baseFeePerGas` - Compute `estimatedTotalFee = gasLimit * (baseFee + priorityFee)` and record it Three new metrics are emitted under `aztec.prover_node.estimated_submission.*`: - `gas` — estimated gas limit for the proof submission tx - `gas_price` — estimated effective gas price (gwei) - `total_fee` — estimated total fee (ETH) This gives us visibility into what a mainnet prover would have paid per epoch, enabling profitability analysis against the rewards tracked by `aztec.prover_node.rewards_per_epoch`. Fixes [A-929](https://linear.app/aztec-labs/issue/A-929/track-proof-submission-fee-estimate-in-fisherman-prover-node)
AztecBot
force-pushed
the
spyros/a-929-track-proof-submission-fee-estimate-in-fisherman-prover-node
branch
from
340a470 to
e8ea1dc
Compare
AztecBot
deleted the
spyros/a-929-track-proof-submission-fee-estimate-in-fisherman-prover-node
branch
chrismarino
pushed a commit
to chrismarino/aztec-packages
that referenced
this pull request
May 5, 2026
BEGIN_COMMIT_OVERRIDE fix(kv-store): ensure LMDB cursor is closed on iteration abort (AztecProtocol#22509) fix(telemetry-client): use appropriate histogram buckets for L1 gas prices (AztecProtocol#22512) fix(telemetry-client): log warning when BatchSpanProcessor drops spans (AztecProtocol#22511) fix(stdlib): wrap HA signer databaseUrl in SecretValue (AztecProtocol#22510) fix(prover-client): don't mark in-progress epoch N jobs as stale when epoch N+1 starts (AztecProtocol#22508) chore: (A-730) graceful shutdown for services in node startup failure path (AztecProtocol#22112) fix(prover-client): reject stale job promises and count timeouts toward retry limit (AztecProtocol#21842) feat(archiver): validate historical L1 log availability at startup (AztecProtocol#22644) fix(archiver): do not query MessageSent events by blockhash (AztecProtocol#22641) refactor(e2e): skip initial sequencer in p2p and epochs tests (AztecProtocol#22535) fix: handle missing L1 finalized block on devnets (AztecProtocol#22663) fix(world-state): treat historical block 0 queries as historical, not latest (AztecProtocol#22679) fix(sequencer): re-check parent checkpoint validity before pipelined L1 submission (AztecProtocol#22586) fix(world-state): make block 0 a first-class historical block (AztecProtocol#22711) chore: show all running versions (AztecProtocol#22376) chore: fix prettier inside worktrees (AztecProtocol#22557) feat: use optimized verifier for rollup (AztecProtocol#21840) fix(kv-store): skip pool creation on ephemeral deleteDb to unstick browser tests (AztecProtocol#22693) chore: rm claude lockfile (AztecProtocol#22718) fix(e2e): wait for first checkpoint in fee_asset_price_oracle_gossip test (AztecProtocol#22719) chore(prover-node): track estimated L1 fee when proof publishing is disabled (AztecProtocol#22691) fix(ci): rerun squashed PR check on base branch change (AztecProtocol#22713) feat(archiver): decouple calldata from blob fetching in L1 synchronizer (AztecProtocol#22716) refactor(e2e): enable pipelining in e2e_epochs tests (AztecProtocol#22544) feat(p2p): reject and evict txs with insufficient max fee per gas (AztecProtocol#22118) refactor(world-state): always index block 0 regardless of initial tree size (AztecProtocol#22724) fix(e2e): fix redistribution test (AztecProtocol#22729) END_COMMIT_OVERRIDE
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When
PROVER_NODE_DISABLE_PROOF_PUBLISH=true(as set on mainnet), the prover node previously finalized the proof and then silently dropped it. This PR changes that path to:validateEpochProofSubmission) — catches public-input mismatches earlyl1TxUtils.estimateGasto get an accurate gas limitl1TxUtils.getGasPrice()and the latest block'sbaseFeePerGasestimatedTotalFee = gasLimit * (baseFee + priorityFee)and record itThree new metrics are emitted under
aztec.prover_node.estimated_submission.*:gas— estimated gas limit for the proof submission txgas_price— estimated effective gas price (gwei)total_fee— estimated total fee (ETH)This gives us visibility into what a mainnet prover would have paid per epoch, enabling profitability analysis against the rewards tracked by
aztec.prover_node.rewards_per_epoch.Fixes A-929