Round 1 against STRATEGY-2026-10-23.md's backlog:
- Wire register_agent/stake/set_credit_score/deposit_liquidity to the real
Casper Testnet contracts (lib/casper/live_bridge.ts), verified live against
the real RPC node with a freshly generated (unfunded) keypair
(npm run casper:keygen). Honesty flags built in for the Odra payable
calling convention and the admin-gated set_credit_score call.
- Unblock NEAR's paid x402 route (npm run near:keygen generates a real
implicit account id); QIE stays correctly flagged as blocked on unconfirmed
external facts (asset contract, facilitator), not env plumbing.
- New public Home tab: live-stats hero, how-it-works, a real competitor
comparison table, and a "90-second proof" that calls the real API live in
the browser (verified end-to-end with gstack browse).
- Cold-start UX: visible retry state in X402Playground + the TS SDK, plus a
keep-warm self-ping (lib/services/keepalive.ts) so the free Render dyno
rarely idles out from under a real first-time caller.
- New GET /v1/credit-score/:agentId alias + docs/integrations/ samples for
Skyfire/Nevermined/Coinbase x402.
- Self-hosting quickstart: root docker-compose.yml + scripts/bootstrap.sh,
both run for real; fixed a real EACCES crash-loop bug in infra/Dockerfile
(non-root user never owned the /data volume mount) found while verifying.
450/450 tests pass, typecheck clean, frontend build clean.
The paid Mainnet endpoint returned 502 x402_facilitator_unavailable and
could never have sold anything:
Facilitator does not support scheme "exact" on network
"algorand:wGHE2Pwdvd7S12BL5FaOP20EGYesN73k"
@x402/avm exports ALGORAND_*_CAIP2 truncated to 32 chars, because CAIP-2
caps a chain reference at 32. The GoPlausible facilitator's /supported and
every catalogued Bazaar resource use the untruncated 44-char genesis hash,
and the resource server matches facilitator capabilities by exact string,
so registration failed outright. Latest @x402/avm (2.26.0) truncates too,
so this is an interop mismatch rather than a stale dependency.
The truncated id was also wrong on the wire: it is what we advertised in
PAYMENT-REQUIRED and what the Bazaar would have recorded, so buyers keyed
on the full hash could not have matched our offer.
Safe in both directions -- the SDK's own normalizeAlgorandNetwork accepts
algorand:<full genesis hash> and maps it back internally, so the AVM
scheme still resolves the right genesis hash when signing and verifying.
Config still accepts the friendly name and either id spelling.
Verified against the live facilitator with a real Mainnet configuration:
the endpoint now returns 402 with network
algorand:wGHE2Pwdvd7S12BL5FaOP20EGYesN73ktiC1qzkkit8=, USDC ASA 31566704,
extra.tag=x402-global-challenge, and a facilitator-injected feePayer.
Also adds the two secrets CRED402_ENV=mainnet requires. Without both,
loadConfig throws at import and the service crash-loops before binding a
port rather than degrading to a 503.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The Mainnet durability gate only checks that CRED402_DATA_DIR is set, not
that it is a mounted disk, so the paid path does enable on the free plan.
The facilitator is the system of record for settlements, so Bazaar listing
and leaderboard standing survive a restart either way.
Documents what free actually costs: an ephemeral replay barrier (one spent
proof can replay once per restart, 0.01 USDC), a usage projection that
resets, and cold starts slow enough to time out a buyer -- volume risk,
not eligibility risk.
Also records the generated receiver address. Public by construction: it is
advertised in every 402 challenge header.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The blueprint pinned CRED402_DATA_DIR to /tmp/cred402 on the ephemeral
container filesystem and declared no disk, so loadAlgorandX402Config
would have refused to enable the paid path on Mainnet no matter what the
dashboard said -- the replay barrier and durable receipt proofs cannot
survive a restart there. It also still declared network=testnet with no
CRED402_ENV and no Mainnet indexer.
Attach a 1GB disk at /var/data and point the journal at it, switch the
network/env pair to mainnet, and pin the Mainnet indexer. This requires
a paid instance type: Render only attaches disks to paid plans, and the
free tier sleeps, which would drop paid traffic during the challenge's
live-measurement window.
PAY_TO and the Mainnet release acknowledgement stay sync:false. The
acknowledgement is a deliberate human gate, so committing its value
would defeat the thing it exists to be.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
- render.yaml: always-on web service `cred402-api` (node runtime, installs dev
deps so tsx is present, health check /v1/health) — Render runs the long-lived
node:http + SSE server the serverless Vercel deploy can't.
- api/server.ts: honor the platform-provided PORT (Render) before CRED402_PORT.
- frontend/vercel.json: rewrite /api/*, /v1/*, /graphql → https://cred402-api.onrender.com
so the deployed console reaches the backend same-origin (no CORS, no code change).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>