Skip to main content
The Giwa Cube An AI gateway needs three things on one chain: high-frequency micropayments, trustworthy operator identity, and verifiable record anchoring. GIWA is the only environment that ships all three, so Tokscale is GIWA-native rather than ported.

​
Three primitives, one chain

  • Flashblocks: ~200ms preconfirmation on GIWA Sepolia (https://sepolia-rpc-flashblocks.giwa.io). Per-request x402 payments feel like a Web2 API call. Preconfirmation is a user-experience primitive, never finality.
  • Dojang (도장, the seal): GIWA’s attestation service. Trusted off-chain facts (KYC status, balances, credentials) issued as on-chain attestations, with no personally identifiable information on-chain. Identity lives as attestations about an address, never as tokens owned by an address, so it is non-transferable by construction.
  • EAS predeploys: the Ethereum Attestation Service (EAS) sits at the standard OP Stack slots on GIWA Sepolia: SchemaRegistry at 0x4200000000000000000000000000000000000020, EAS at 0x4200000000000000000000000000000000000021. Schema registration is permissionless, so Tokscale attestations anchor on public infrastructure from day one.
No other chain pairs an exchange-grade identity layer with sub-second payment preconfirmation and a permissionless attestation substrate.

​
Why an anonymity-first competitor cannot run here

B.AI proved the crypto-paid AI gateway category on TRON with an anonymity-first design: no mandatory KYC, agent identity as transferable ERC-8004 tokens (details in Five Proven Patterns). That design cannot run on GIWA. Verification is the chain’s entire premise: Dojang exists because Upbit’s KYC sits behind it. A GIWA-native version of this category has to be verification-first, humans alongside agents, identity bound to a Dojang Verified Address. The constraint is also the differentiation.

​
The precedents that prove it

  • Coinbase Verifications on Base is the direct Dojang analog: an exchange issuing KYC attestations via EAS on its own OP Stack L2, gating apps and perks. It drew ~9,300 attestations on day one, 15% of all EAS attestations at the time. Upbit (13M+ users) to Dojang to Tokscale is the identical play, and Base already ran it.
  • Shinhan Bank is migrating professional-credential verification onto GIWA: doctor-loan qualification checks, expanding to lawyers and accountants. A Builder Passport is the same category (professional credential attestation) for a profession GIWA does not yet cover: AI-native developers.

​
The x402 port, settled on the public chain

GIWA does not officially support x402. We ported the stack ourselves: a self-hosted x402-rs facilitator (image pinned by digest), the canonical Permit2 proxies, and an ERC-6492 signature validator, all deployed on public GIWA Sepolia. Then we settled a real payment on it: one ERC-3009 exact settlement of 1.0 tUSD in tx 0xad1a2f7b5aff4033e7779437ec487e8b51eb8170ba1c6c8cc971f6de37fcb9f8, replay-rejected by the facilitator on retry. That answers the hardest open question: does x402 work on GIWA at all. Re-verify the deployment and settlement records against the live chain:
Every contract and transaction behind this claim is listed with explorer links on Live Evidence and The Public Chain.

​
What Tokscale gives back

  • The x402 gateway GIWA lacks. GIWA has no crypto-paid AI gateway and no x402 facilitator; Tokscale ships both, including operating the facilitator role itself.
  • A GIWA Wallet use case people check daily. The Builder Passport is a wallet-readable credential with real content behind it (verified usage, skill signals, verification rate), not a static badge. For more information, see Builder Passport.

​
Riding Dojang’s roadmap

Dojang’s implicit roadmap, read from GIWA’s own moves:
  1. KYC attestation (live: Verified Address, issued by Upbit Korea; a Testnet Faucet attester exists on Sepolia).
  2. Balance and financial attestations (live: Balance Root and Verified Balance).
  3. Professional credentials (in progress: the Shinhan Bank pattern).
  4. Third-party issuers (architecture ready; external issuers are explicitly invited at buidl@giwa.io).
  5. Privacy-enhanced attestations (Bojagi convergence).
Tokscale rides that arc instead of fighting it. Tokscale schemas follow Dojang’s own design idiom (the Usage Root mirrors Balance Root) and publish permissionlessly from the MVP; the Phase 2 step is registration in DojangAttesterBook as an official issuer. That application is a graduation, not a pitch, because the schemas will already be live and indexed.

​
Next steps