x402 Gauntlet methodology

Evidence has a boundary.

Gauntlet certifies one declared, mechanically testable endpoint contract. It does not issue a general security, legal, compliance, or correctness opinion.

1. Server-observed probe

The buyer submits an HTTPS endpoint, task contract, and JSON input. Gauntlet sends the input itself and derives status, latency, output, provenance, and price from the real response. Caller observations are ignored.

2. Network safety

The probe rejects embedded credentials, redirects, local or reserved hosts, private or reserved DNS answers, unsupported content, oversized bodies, and timeouts. Connections are pinned to DNS addresses that passed those checks.

3. Payment proof

• Algorand: confirmed payer, receiver, ASA, and amount.
• Base: successful receipt and exact USDC Transfer event.
• Solana: successful transaction, signed payer, mint, and exact owner balance deltas.

The competition route remains Algorand-only. The multichain route lets a buyer select one enabled network; it does not bridge funds.

4. Recovery and replay

The first proof for a network and transaction is stored atomically. A repeated settlement returns the original record. MainNet rejects ephemeral storage and checks the durable store before payment handling; an unhealthy store returns a bounded 503 before settlement is attempted. Signing-key IDs preserve historical verification across planned rotations.

5. Honest limits

TestNet runs, controlled fixtures, self-payments, and team-controlled wallets are rehearsal evidence only. They do not prove independent demand, competition eligibility, ranking, revenue, or a future result.

Last reviewed: July 26, 2026 · contact@jalenbuilds.com