This screen exercises the P2/P3 launch rail with Earth evidence: challenge, BBS+ verification, replay protection and signed receipt. The SDK, quickstart and portable HTTPS links are visible now. A3-G8 has bounded canary reward evidence only; Product release/readiness, hosted rewards, production wallet payout and private payment stay closed until their own gates pass.
The safe path is one SDK call that creates a challenge through seed-clear and returns the portable HTTPS link. This static page shows a format fixture; live integrations call the API to create a fresh challenge.
/c/challenge_format_fixturePresentation links carry request material: challenge, verifier, policy, claim types, expiry, and an optional signed envelope. They must not carry raw credentials, wallet keys, SEED addresses, secrets, or reusable proof material.
/p/sample-requestReceipt links are first-class, but this surface does not invent a live receipt fixture. Real receipts come from the P3 verify path. The SDK verifies the receipt signature contract offline with a pinned SPKI public key and fails closed on mismatch.
/r/receipt_format_fixtureThis is the SDK path the product should make easiest. It creates a challenge through the API and distributes only the HTTPS link. Today that call targets the bounded P2/P3 service evidence. Economic accounting can reference the bounded A3-G8 canary evidence only as NO_GO release/readiness input; it is still not a hosted rewards or production payout claim.
import { ClearClient } from "@seed/clear-sdk";
const clear = new ClearClient({
endpoint: process.env.SEED_CLEAR_ENDPOINT ?? "http://localhost:4187",
apiKey: process.env.SEED_CLEAR_API_KEY ?? "",
});
const { challenge, link } = await clear.createPortableChallenge({
verifierId: "verifier-local",
policyId: "agent-clearance-v1",
claimTypes: ["agent.clearance"],
});
console.log(challenge.challengeId);
console.log(link);Console setup stays narrow: one app, one policy, one API key, one sandbox and one receipt path. It creates verifier challenge material, shows sandbox verification, and lists receipts without inventing reward counters, claim buttons or private-payment execution.
create app
choose policy
generate API key
run sandbox challenge/verify
inspect one signed receiptCurrent service shape is health, readiness, loopback metrics, and Bun startup with HOST and PORT. Earth serves the runtime with health/readiness over HTTPS plus public metrics refusal.
The interface has bounded evidence for the canonical BBS+ verifier, issuer trust path, production receipt signer and durable replay store. Missing or mismatched proof material still fails closed.
The local bridge contract is green for paid-event input, deterministic batches and local settlement/accounting artifacts. A3-G8 now proves the bounded canary path through consume, materialize, fund, release, claimable-balance query, canary `MsgClaim`, replay guard, holder-vault credit and 45/30/15/10 reconciliation. Hosted rewards, production payout, hidden amount and private-payment rail remain closed.
Private Value Rail is in protocol closure. The product wallet surface waits for frozen proof and state contracts, wallet witness handling, and E2E evidence. V1 must not sell or execute private-payment actions.