config-proof-aggregator-ethereum-package.yaml

aligned_service_manager_address: "0x851356ae760d987E095750cCeb3bC6014560891C"
proof_aggregation_service_address: "0xcbEAF3BDe82155F56486Fb5a1072cb8baAf547cc"
eth_rpc_url: "http://localhost:8545"
eth_ws_url: "ws://localhost:8546"
max_proofs_in_queue: 1000
last_aggregated_block_filepath: config-files/proof-aggregator.last_aggregated_block.json
proofs_per_chunk: 512 # Amount of proofs to process per chunk
# This number comes from the blob data limit
# Since each blob has a capacity of (4096 * 32) = 131.072 bytes
# But to not surpass the field modulus we pad with a 0xo byte so we have (4096 * 31) = 126.976 bytes
# of usable data
# Since each proof commitments takes 32 bytes hash
# We can aggregate as much proofs as 126.976 / 32 = 3968 per blob
total_proofs_limit: 3968
db_connection_urls: 
  - "postgres://postgres:postgres@localhost:5435/"

# Monthly ETH budget for on-chain proof verification. This value must be non-negative.
# This value will be used to calculate how much gas we can spend per second to send proofs on-chain.
# Note that this value is for the entire month. For example, if you set it to 15.0 ETH,
# then after 24 hours you can spend (15.0 ETH / 30 days) = 0.5 ETH.
monthly_budget_eth: 15.0

# These program ids are the ones from the chunk aggregator programs
# Can be found in the Proof Aggregation Service deployment config
# (remember to trim the 0x prefix)
sp1_chunk_aggregator_vk_hash: "00d6e32a34f68ea643362b96615591c94ee0bf99ee871740ab2337966a4f77af"
risc0_chunk_aggregator_image_id: "8908f01022827e80a5de71908c16ee44f4a467236df20f62e7c994491629d74c"

# These values modify the bumping behavior after the aggregated proof on-chain submission times out.
max_bump_retries: 5
bump_retry_interval_seconds: 120
base_bump_percentage: 10
max_fee_bump_percentage: 100
priority_fee_wei: 3000000000 // 3 Gwei

ecdsa:
  private_key_store_path: "config-files/anvil.proof-aggregator.ecdsa.key.json"
  private_key_store_password: ""