Node parameters and environment
payment_node parameters
Parameter |
Default |
Description |
|---|---|---|
|
|
Where keys live and how transactions are sent. |
|
|
|
|
off |
Publish and consume escrow signatures on |
|
|
Largest single payment, in USDC |
|
|
Total spend allowed per rolling window, in USDC |
|
|
Rolling window length |
Caps are strings, so pass them quoted: -p max_per_transaction:="'0.10'".
The passphrase is deliberately not a parameter. Parameters can be listed by any node on the graph.
Environment variables
Variable |
Purpose |
|---|---|
|
Path to a file holding the wallet passphrase. Must be mode |
|
Passphrase in the environment. Convenient for development, weaker than a file. |
|
Your own Base Sepolia RPC endpoint. Public endpoint used if unset. |
|
Your own Base mainnet RPC endpoint. Public endpoint used if unset. |
|
Enables tests that talk to a real network |
If neither passphrase variable is set, the node prompts on the terminal with input hidden.
Files on disk
Everything robopay stores lives under ~/.robopay/:
Path |
Contents |
|---|---|
|
Encrypted private key (scrypt + Fernet), mode |
|
Payment lifecycle records |
|
Escrows opened by this robot, for automatic refunds |
Back up the wallet files together with their passphrases. Without both, funds in that wallet are unrecoverable.