feat(cli): add get-user-first-nonce + get-user-number-queued-proofs cli commands

[PatStiles]

Add get-user-first-nonce to cli

Description

Adds a function to the aligned-cli get-user-first-nonce to retrieve the users nonce from ethereum. This is useful in scenarios where you need to replace your proofs with higher fees. For that, you'll need the first proof's nonce corresponding to the value in the BatcherPaymentService contract.

Adds a function to the aligned-cli get-user-number-queued-proofs to retrieve the number of proofs a user has in the batcher queue.

To Test:

• Setup a local devnet.
• Fund a wallet:

cast send <YOUR_WALLET_ADDRESS> --private-key <ANVIL_RICH_ACCOUNT> --value 1ether

• cd into aligned cli: cd batcher/aligned
• Fund wallet on batcher wallet:

cargo run --release -- deposit-to-batcher --network devnet --amount 0.1ether --keystore_path <KEYSTORE_PATH>

• Send some proofs with a low max fee to the batcher so that they are not submitted:

cargo run --release -- submit  --proving_system Risc0 --proof ../../scripts/test_files/risc_zero/fibonacci_proof_generator/risc_zero_fibonacci.proof  --vm_program ../../scripts/test_files/risc_zero/fibonacci_proof_generator/fibonacci_id.bin --public_input ../../scripts/test_files/risc_zero/fibonacci_proof_generator/risc_zero_fibonacci.pub --repetitions <BURST_SIZE> --keystore_path <YOUR_KEYSTORE_PATH> --network devnet  --max_fee 10  --nonce "0"

• Get the nonce from ethereum:

cargo run --release -- get-user-nonce-from-ethereum --user_addr <YOUR_WALLET_ADDRESS>

You should see it is 0.

• Get the nonce from the Batcher:

cargo run --release -- get-user-nonce --user_addr <YOUR_WALLET_ADDRESS>

You should see it is <BURST_SIZE>

• Get the amount of proofs in batcher queue:

cargo run --release -- get-amount-of-proofs-in-batcher-queue --user_addr <YOUR_WALLET_ADDRESS>

• Bump the fees using the nonce you got from the Ethereum:

cargo run --release -- submit  --proving_system Risc0 --proof ../../scripts/test_files/risc_zero/fibonacci_proof_generator/risc_zero_fibonacci.proof  --vm_program ../../scripts/test_files/risc_zero/fibonacci_proof_generator/fibonacci_id.bin --public_input ../../scripts/test_files/risc_zero/fibonacci_proof_generator/risc_zero_fibonacci.pub --repetitions 3 --keystore_path <YOUR_KEYSTORE_PATH> --network devnet  --max_fee 1000000000000  --nonce "0"

Type of change

Please delete options that are not relevant.

• New feature

Checklist

• “Hotfix” to testnet, everything else to staging
• Linked to Github Issue
• This change depends on code or research by an external entity
  • Acknowledgements were updated to give credit
• Unit tests added
• This change requires new documentation.
  • Documentation has been added/updated.
• This change is an Optimization
  • Benchmarks added/run
• Has a known issue
  • Link to the open issue addressing it
• If your PR changes the Operator compatibility (Ex: Upgrade prover versions)
  • This PR adds compatibility for operator for both versions and do not change batcher/docs/examples
  • This PR updates batcher and docs/examples to the newer version. This requires the operator are already updated to be compatible

[github-actions]

Changes to gas cost

Generated at commit: 069fea945ca651ff7906b3d4e58ef3fd011665d6, compared to commit: 8b6ef0c71f65d1233d392c2d58f2f1442ba27fab

🧾 Summary (10% most significant diffs)

Contract	Method	Avg (+/-)	%
AlignedLayerServiceManager	createNewTask	+302 ❌	+0.40%

---

Full diff report 👇

Contract	Deployment Cost (+/-)	Method	Min (+/-)	%	Avg (+/-)	%	Median (+/-)	%	Max (+/-)	%	# Calls (+/-)
AlignedLayerServiceManager	5,231,234 (0)	createNewTask receive	56,083 (0) 23,317 (0)	0.00% 0.00%	76,066 (+302) 46,915 (+373)	+0.40% +0.80%	76,217 (-24) 47,195 (0)	-0.03% 0.00%	77,030 (0) 47,195 (0)	0.00% 0.00%	256 (0) 256 (0)

[avilagaston9]

As discussed offline, we have to use get_nonce_from_ethereum in batcher/aligned-sdk/src/sdk.rs:633, which returns the next nonce from Ethereum for a given address. This will simplify the code a lot and we should update the docs explaining how this method can be useful.

[JulianVentura]

Got some unexpected behavior while testing it locally that should be discussed offline

[JulianVentura]

Got some unexpected behavior while testing it locally that should be discussed offline

This error was related to the usage of non paying addresses. It works as expected for paying addresses

[JulianVentura]

Looks good and works as expected locally

[avilagaston9]

Code looks good and works in my machine!

[JuArce]

There is missing to update the docs

[JuArce]

Docs is outdated