Context
Hi! I maintain AlgoVoi, a multi-protocol (x402 + MPP + AP2) facilitator covering seven mainnet networks: Base, Solana, Tempo (the three you support today), plus Stellar, Algorand, VOI, and Hedera. We're now production-tested on Base+Solana+Stellar with USDC settlement — Stellar mainnet xChain shipped 2026-05-05 (first mainnet bridge from Base settled in ~2 minutes).
Two questions about how x402-proxy could surface AlgoVoi to its users:
1. Facilitator extensibility
The README mentions x402-proxy "auto-pays HTTP 402 on Base, Solana, and Tempo" but I couldn't find a documented model for adding/recognizing third-party facilitators. From a quick read of the source, it looks like the proxy parses the 402 response and signs locally, treating the facilitator URL from the response as authoritative — which is exactly the right design for an open ecosystem.
Question: would a documented allowlist of "known good" facilitators (or a small starter list bundled with the binary) help your users discover production-grade facilitators across the three chains you cover? Happy to PR an examples/facilitators.md with AlgoVoi entries if useful.
2. Inbound link from AlgoVoi docs
We just added a Complementary facilitators in the x402 ecosystem subsection to our docs (docs.algovoi.co.uk/concepts/xchain) that points to pay.sh, Built on Stellar, and Coinbase Hosted Facilitator. Happy to add x402-proxy as the recommended multi-chain CLI client — covers exactly the three chains where AlgoVoi has the most production traffic. Let me know if you'd prefer a specific framing or canonical URL.
Cross-references
Thanks for shipping x402-proxy — the wallet derivation from a single mnemonic across EVM and Solana is exactly the right primitive.
Context
Hi! I maintain AlgoVoi, a multi-protocol (x402 + MPP + AP2) facilitator covering seven mainnet networks: Base, Solana, Tempo (the three you support today), plus Stellar, Algorand, VOI, and Hedera. We're now production-tested on Base+Solana+Stellar with USDC settlement — Stellar mainnet xChain shipped 2026-05-05 (first mainnet bridge from Base settled in ~2 minutes).
Two questions about how x402-proxy could surface AlgoVoi to its users:
1. Facilitator extensibility
The README mentions x402-proxy "auto-pays HTTP 402 on Base, Solana, and Tempo" but I couldn't find a documented model for adding/recognizing third-party facilitators. From a quick read of the source, it looks like the proxy parses the 402 response and signs locally, treating the facilitator URL from the response as authoritative — which is exactly the right design for an open ecosystem.
Question: would a documented allowlist of "known good" facilitators (or a small starter list bundled with the binary) help your users discover production-grade facilitators across the three chains you cover? Happy to PR an
examples/facilitators.mdwith AlgoVoi entries if useful.2. Inbound link from AlgoVoi docs
We just added a Complementary facilitators in the x402 ecosystem subsection to our docs (docs.algovoi.co.uk/concepts/xchain) that points to pay.sh, Built on Stellar, and Coinbase Hosted Facilitator. Happy to add x402-proxy as the recommended multi-chain CLI client — covers exactly the three chains where AlgoVoi has the most production traffic. Let me know if you'd prefer a specific framing or canonical URL.
Cross-references
pay.sh-compatible catalog (version=2 envelope, ETag, conditional GET): https://api.algovoi.co.uk/.well-known/pay-skills.jsonThanks for shipping x402-proxy — the wallet derivation from a single mnemonic across EVM and Solana is exactly the right primitive.