Mainnet readiness

What must be true before real value.

SettleProof is live on Solana devnet for product validation. Mainnet should wait until custody, key management, merchant policy, and operations can survive real disputes and external review.

Current devnet status

AreaDevnet stateMainnet gap
Programsaap-custody + aap-attestor deployed and testedExternal audit and upgrade authority policy
SettlementRelease, refund, partial release, and x402 demo flowsExpanded negative tests and real USDC edge-case review
APIOpenAPI, signed relay, persistent indexer, evidence digest/signature surface, hosted smoke scriptRate limits, auth tiers, alerting, and SLOs
Attestor keysDevnet self-custody shown in the browserMerchant KMS/HSM or merchant-owned signer service
RegistryMVP merchant registry and suspension statesKYB, dispute policy, slashing/suspension process

Recommended beta limits

LimitBeta valueReason
First wedgeAPI/data commerceDelivery evidence is objective: HTTP status, response hash, request id, and timestamp.
Max escrow100 USDCLow-value cap while contract, registry policy, and operations mature.
Max TTL24 hoursKeeps refund windows short for initial agent/API integrations.
MerchantsAllowlisted Active merchants onlyReduces fraud and makes attestor ownership review practical.
AssetsUSDC onlyAvoids multi-mint accounting and pricing complexity at launch.

Required gates

GateRequired evidence
Contract reviewExternal Anchor/Solana review, documented findings, fixed issues, light-audit notes, and reproducible test suite.
Token safetyReal USDC mint handling, ATA creation/recovery paths, rent assumptions, and partial-release math review.
Key custodyNo production browser secrets; merchant-owned signer, KMS/HSM option, rotation flow, and revocation playbook.
Indexer operationsPersistent storage, replayable sync, event retention policy, monitoring, and backfill procedure.
Incident responseAlert routing, pause/upgrade authority handling, disclosure policy, and customer communication template.
Merchant policyKYB baseline, attestor ownership checks, service terms, and dispute escalation rules.
Economic policyFee model, minimum escrow amount, griefing analysis, and rate limiting for public relay/API.

Devnet acceptance checklist

  • Hosted pages resolve: settleproof.xyz, demo.settleproof.xyz, and api.settleproof.xyz.
  • /openapi.json, /v1/status, /v1/escrows/prepare, /v1/relay, and /v1/indexer pass hosted smoke checks.
  • Guided demo explains challenge, custody, attestation, settlement, and indexed state without requiring a live walkthrough.
  • Threat model clearly separates devnet self-custody from production key custody expectations.

Future privacy track

LayerPossible roleConstraint
CloakPrivate funding or shielded agent wallet flows before escrow creation.Do not hide the settlement evidence SettleProof needs for merchant liability.
Evidence packetsRemain public at the hash/state/link level for auditability.Sensitive delivery details can move behind viewing keys or off-chain compliance access later.
Product timingEvaluate after the API/data commerce wedge is validated.Not a blocker for devnet or first mainnet beta.

Mainnet position

Not mainnet-ready yet

The current deployment is strong enough for a devnet hackathon demo and integration conversations. It should not custody real funds until the gates above are complete.