Sp1 task sender #2039
Merged
Sp1 task sender #2039
Conversation
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
JuArce
approved these changes
Jul 31, 2025
maximopalopoli
approved these changes
Jul 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sp1 task sender
Aligned Payment Service Testing Guide
This guide walks you through testing the Aligned payment service with different proof systems. You'll need to set up wallets, fund them, and then choose from three different proof verification options.
Prerequisites
Make sure you have a local Anvil node running on
http://localhost:8545Setup Steps
1. Create Wallets File
First, create a file with test wallet private keys:
2. Fund Wallets
Fund the wallets in the Aligned payment service:
cargo run --release --manifest-path ./crates/task-sender/Cargo.toml -- generate-and-fund-wallets \ --eth-rpc-url http://localhost:8545 \ --network devnet \ --funding-wallet-private-key 0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80 \ --number-wallets 5 \ --amount-to-deposit 1.0 \ --amount-to-deposit-to-aligned 0.1 \ --private-keys-filepath ./wallets.txtTesting Options
After completing the setup steps above, choose one of the following proof systems to test:
Option A: RISC Zero Proofs
cargo run --release --manifest-path ./crates/task-sender/Cargo.toml -- send-infinite-proofs \ --private-keys-filepath ./wallets.txt \ --random-address \ --burst-size 5 \ --burst-time-secs 10 \ --network devnet \ risc0 \ --proof-path ./scripts/test_files/risc_zero/fibonacci_proof_generator/risc_zero_fibonacci_2_2_0.proof \ --bin-path ./scripts/test_files/risc_zero/fibonacci_proof_generator/fibonacci_id_2_2_0.bin \ --pub-path ./scripts/test_files/risc_zero/fibonacci_proof_generator/risc_zero_fibonacci_2_2_0.pubOption B: Gnark Groth16 Proofs
cargo run --release --manifest-path ./crates/task-sender/Cargo.toml -- send-infinite-proofs \ --private-keys-filepath ./wallets.txt \ --random-address \ --burst-size 5 \ --burst-time-secs 10 \ --network devnet \ gnark-groth16 --proofs-dir ./scripts/test_files/gnark_groth16_bn254_scriptOption C: SP1 Proofs
cargo run --release --manifest-path ./crates/task-sender/Cargo.toml -- send-infinite-proofs \ --private-keys-filepath wallets.txt \ --burst-size 5 \ --burst-time-secs 10 \ --random-address \ sp1 \ --proof-path ./scripts/test_files/sp1/sp1_fibonacci_5_0_0.proof \ --elf-path ./scripts/test_files/sp1/sp1_fibonacci_5_0_0.elf \ --pub-path ./scripts/test_files/sp1/sp1_fibonacci_5_0_0.pubWhat Each Option Does
Each test will continuously send proofs to random addresses using the funded wallets until manually stopped.