The facilitator’s own fee-payer signing key. Needs its own TestNet ALGO balance to co-sign settlement fee-payer transactions.
ALGOD_SERVER
No
https://testnet-api.algonode.cloud
The algod endpoint the containerized facilitator itself talks to.
EVM_PRIVATE_KEY
Yes
—
Any well-formed throwaway hex key. Required by the upstream multi-chain facilitator example to start, but never exercised — Ward only tests the Algorand scheme.
SVM_PRIVATE_KEY
Yes
—
Any well-formed throwaway base58 key. Same as above, for the Solana scheme.
docker-compose.yml uses Compose’s ${VAR:?message} syntax for AVM_PRIVATE_KEY,
EVM_PRIVATE_KEY, and SVM_PRIVATE_KEY — Compose refuses to start with a clear error if any is
unset, rather than starting the facilitator in a broken state.
Receives this service’s own x402 payments for POST /verify-facilitator. Deliberately separate from the WARD_* test-harness accounts above — this is service revenue, not a test fixture.
SERVER_PORT
No
4030
Local-dev only. Deployed instances bind to PORT, assigned by the host platform.
PAYMENT_FACILITATOR_URL
No
https://facilitator.goplausible.xyz
The facilitator that processes payment to this service — never the facilitator being tested. See Deployment.
Prints a fresh keypair (address + base64 secret key) for WARD_FUNDER, WARD_CLIENT,
WARD_PAYTO, and AVM_PRIVATE_KEY, plus throwaway well-formed EVM_PRIVATE_KEY /
SVM_PRIVATE_KEY values — paste all of it straight into .env. See the
Quickstart for the full walkthrough, including the one manual
funding step this script can’t automate.
Fund the accounts this script generates
⌘I
Assistant
Responses are generated using AI and may contain mistakes.