Skip to content

fix: use dedicated L1 account for bot bridge resume tests to avoid nonce race #21148

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.

Sign up for GitHub

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

Merged
alexghr merged 1 commit into from
Mar 6, 2026
Merged

fix: use dedicated L1 account for bot bridge resume tests to avoid nonce race #21148

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions yarn-project/end-to-end/src/e2e_bot.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,7 +134,10 @@ describe('e2e_bot', () => {

l1RpcUrls,
feePaymentMethod: 'fee_juice',
l1PrivateKey: getPrivateKey(),
// Use a dedicated L1 account (index 7) for bridging. The default mnemonic account (index 0)
// is shared with the sequencer which sends L1 block proposals, causing nonce races on the
// approve/deposit calls in bridgeL1FeeJuice. Indices 8 and 9 are used by other tests below.
l1PrivateKey: new SecretValue(bufferToHex(getPrivateKeyFromIndex(7)!)),
flushSetupTransactions: true,
// Increase fee headroom to handle fee volatility from rapid block building in tests.
// Fees can escalate >10x due to blocks built by earlier tests and bridge operations.
Expand Down Expand Up @@ -174,7 +177,8 @@ describe('e2e_bot', () => {

l1RpcUrls,
feePaymentMethod: 'fee_juice',
l1PrivateKey: getPrivateKey(),
// See comment above — dedicated L1 account to avoid nonce races with the sequencer.
l1PrivateKey: new SecretValue(bufferToHex(getPrivateKeyFromIndex(7)!)),
flushSetupTransactions: true,
// Increase fee headroom to handle fee volatility from rapid block building in tests.
// This test is especially susceptible because changing salt triggers a new bridge claim,
Expand Down
Loading