Real commerce verification
Real USDC commerce events have been verified against intended requests, protected against replay and converted into evidence and portable proof.
Current evidence comes first. Historical engineering artifacts remain available so reviewer, hackathon and audit links do not break — but old testnet work is not presented as current production proof.
Real USDC commerce events have been verified against intended requests, protected against replay and converted into evidence and portable proof.
A real 0.07 USDC API purchase completed with signed commerce evidence. Recovery completed without a second authorization or second charge.
A real Base Mainnet merchant pilot completed payment verification, fulfillment and evidence creation with visible outcome records.
Agent-readable verification exposes deterministic post-payment evidence without granting SafeGate wallet authority.
The public SDK provides commerce-verification and agent-facing surfaces while preserving error and assurance semantics.
Observed evidence is not silently labeled validated. Unsupported links remain explicit evidence gaps or UNVERIFIED where the relevant contract requires it.
SafeGate accumulated many controlled reviewer and hackathon artifacts while the product evolved. They remain useful for lineage, regression evidence and architectural review, but they should not dominate the storefront or be mistaken for the latest product state.
Useful for post-payment state, receipt and access-flow lineage. These do not imply Pi Mainnet settlement or current product dependence on Pi.
Historical proof of deterministic verification, replay rejection and wallet-bound access patterns before later Base Mainnet production evidence.
Reviewer material around portable proof, signed checkpoints and external-anchor design. Anchor design must not be confused with a payment rail.
Hedera, The Graph, Celo and other adapter artifacts remain distribution and interoperability evidence; they do not redefine the SafeGate core.