0G private routing and Hedera testnet runway are checked live. The full TEE proof, signatures, auctions, and atomic swaps are still independently verified during execution.
How the private call worksInspect the trust boundary
This page calls 0G directly. There is no application API route, and the user's key stays in this tab's React state.
Every request sends X-0G-Provider-Trust-Mode: private. 0G documents that this routes only to TeeML, where the model and prompt stay inside the enclave.
The Router must return tee_verified: true. The browser also recovers the provider's EIP-191 signer and matches it to the acknowledged signer recorded on 0G.
0G calls this private or sealed inference. It is not the separate draft _e2ee HPKE payload protocol: production uses a normal OpenAI-compatible messages request plus the private routing header.
After 0G returns the verified plan, mocked seller inventory and demo rival profiles enter real HCS English auctions. Bid ordering, winner selection, NATA payment, and claim-NFT delivery execute on Hedera testnet; no local auction or simulated receipt is substituted.