Skip to main content
Tokscale’s claims fall into three strictly separated categories: what is deployed or proven on public GIWA Sepolia (verifiable in the explorer), what is proven only on a local localnet (hermetic Anvil fixtures, no explorer links), and what does not exist yet (Phase 2 or pending). This page is the authoritative source for all three.

​
Proven on public GIWA Sepolia (chain ID 91342)

Every row is verifiable in the explorer at https://sepolia-explorer.giwa.io. GIWA-provided infrastructure we build on (not our deployments): EAS SchemaRegistry 0x4200000000000000000000000000000000000020 and EAS 0x4200000000000000000000000000000000000021 (OP Stack predeploys), DojangScroll 0xd5077b67dcb56caC8b270C7788FC3E6ee03F17B9, DojangAttesterBook 0xDA282E89244424E297Ce8e78089B54D043FB28B6, and the Testnet Faucet attester resolving to 0x63CCe2b569A7bC35895ee24306c1512fefc06121.
Scope, stated plainly: tUSD is a test token, not a stablecoin. The exact settlement is test-only ERC-3009 evidence, not a public payment route, credit top-up, or production authorization. The Upto settlement above proves the scheme’s actual-versus-maximum semantics on-chain, but it does not enable a public upto route: it was submitted directly with the payer and facilitator held by one key, so it is contract-level evidence rather than a product route. Public facilitator behavior, dedicated RPC, and key/treasury custody remain external gates. The hardest open question, whether x402 works on GIWA at all, is answered; the product path on public Sepolia is not open yet.
Re-verify the tUSD deployment and settlement records against the live chain:

​
Proven on local localnet (hermetic Anvil fixtures)

Local means a disposable Anvil topology that borrows chain ID 91342. Chain ID is not a network identity: GIWA_NETWORK plus the immutable database binding is. Nothing in this section carries a Sepolia explorer link, and every result below is maintainer-run: the harness is not publicly available. The full loop, end to end: gateway, x402 payment, receipts, attestation pipeline, and browser-rendered checks.
Stage A credit top-up with crash recovery: the reconciler is killed mid-settlement and recovers with exactly-once semantics.
Stage B upto per-request settlement with fault injection: durable actual-usage settlement across facilitator failures on the local topology.
Protocol vectors verified three independent ways: Rust (Alloy), TypeScript (viem), and Solidity (Forge). Independent oracles, not one shared library trusted twice.

​
Not yet: Phase 2 or pending

None of the following is live today.
  • Public Usage Root on GIWA Sepolia: no Usage Root exists on real Sepolia today. Anchoring lands only on the local EAS fixture until the first public anchor ships, which means one EAS schema registered, one real Usage Root published, and an explorer link added here at that moment.
  • Dojang eligibility gate: the Passport is not yet gated on a Dojang Verified Address. The read path is validated; the gate is Phase 2.
  • TokscaleScroll read contract: the DojangScroll-style convenience reader is Phase 2.
  • Transactional Earn: no bounties table, no apply flow, no payouts. Phase 2.
  • Public app URL: no public host, DNS, production GitHub OAuth app, credentialed provider run, or externally reachable gateway origin yet.
  • Public Stage B upto route: the end-to-end product route is proven locally only. The settlement primitive itself is proven on public GIWA Sepolia in the table above; what remains external is the product path around it, per the gates in the warning.
  • GIWA mainnet: does not exist. No GIWA token is planned.

​
Next steps

  • For every address and transaction with its deployment record, see The Public Chain.
  • For every command above with its pass marker, see Verification Log.
  • For why a local artifact and a Sepolia artifact can share chain ID 91342 and still be different networks, see Network Separation.