Skip to main content
If an answer here ever disagrees with Live Evidence, the evidence page wins.

​
Is any of this actually public?

Yes, and only the parts that are. Public GIWA Sepolia: the tUSD payment asset, the x402 Permit2 proxies, the ERC-6492 validator, one ERC-3009 exact settlement (tx 0xad1a2f7b…), and a passing facilitator smoke test (tx 0x890c0892…). Everything else is labeled local. We publish availability, not aspiration. See Live Evidence.

​
Isn’t your existing data forgeable?

Yes. The OSS Tokscale tracker measures usage on the user’s own machine, so it sits at the bottom of the evidence ladder: self-reported, consistency-checked, source-verified, gateway-verified, attested. Self-reported usage is forgeable, which is exactly why the product is the migration path up those tiers. See Verified Usage and the Evidence Ladder.

​
Web3 reputation projects always die. Why is this different?

They die for nameable reasons: no proprietary data source, no economic loop, transferable credentials, token-first design. Tokscale is the point-by-point negation of each. The gateway generates proprietary usage data as a side effect of a paid product. The loop runs from usage to proof to identity to income. The Passport is Dojang-bound and non-transferable. And there is no token.

​
Isn’t x402 volume mostly wash trading?

Mostly, yes, and that is the opportunity. Most x402 volume today does not map to real consumption. Tokscale’s payments map 1:1 to real inference requests: a builder pays, a model responds, a receipt is issued. We are the organic demand the rails are waiting for, and we already settled on GIWA Sepolia (tx 0xad1a2f7b…).

​
Isn’t this a B.AI copy?

We openly bring the proven model to GIWA. Every ecosystem gets its own version of proven infrastructure; GIWA’s did not exist. The adaptation is the work: verification instead of anonymity, humans alongside agents, and a real starting dataset from the OSS project instead of zero. B.AI is built for agents and their wallets; Tokscale is built for builders and their verifiable work history.

​
Why not just use ERC-8004?

Its identity is a transferable ERC-721. Reputation that can be sold is not a work credential. Tokscale’s Passport binds Dojang attestations (EAS, KYC-grade, PII never on-chain) to one human, non-transferable by construction. See Builder Passport and Dojang: On-Chain Attestations.

​
Gateway margins are thin. Where is the business?

Thin routing margin is OpenRouter’s own long-term weakness, and we are not betting on it. The gateway is a data-generation engine. The moat is the verified-identity layer that routing-only players cannot copy, because they do not see the work. The payoff is Earn: bounties routed to builders whose history is provable.

​
Why might a receipt show a different domain name than the docs?

The EIP-712 domain and merkle separators are hashed into every signature and proof already issued, so a receipt verifies against the exact strings it was signed under, which a verifier selects from its persisted schema version. A renamed namespace is a new schema version verifying alongside V1, never an edit to V1. See UsageReceiptV1.

​
Why does this need a chain at all?

Three reasons, all GIWA-native. Payments: per-request crypto settlement is the only billing model that works for autonomous agents, and Flashblocks makes it feel like a Web2 API. Anchoring: one epoch Merkle root on-chain covers every receipt in it, so proving 1M or 100M requests costs the same, and anyone can verify one receipt against the root in the explorer. Identity: Dojang attestations give KYC-grade, non-transferable builder identity that a private database cannot offer. A centralized database could store receipts, but no third party could verify them without trusting us.

​
Practical: is there a token, is GIWA mainnet live, does GIWA officially support x402?

  • Is there a token? No. None is planned. The business model is payments and verification, not a reputation token.
  • Is GIWA mainnet live? No. GIWA Sepolia (chain ID 91342) is the only public GIWA network today, and every public claim in this documentation names it.
  • Does GIWA officially support x402? No. We ported the stack ourselves: self-hosted pinned x402-rs facilitator, canonical Permit2 proxies, and an ERC-6492 validator, all deployed on GIWA Sepolia and listed in The Public Chain. That port is what makes the project GIWA-native rather than ported.
A claim you cannot verify in this documentation is a claim we did not make: every public contract and transaction links the explorer, and every “it works” claim ends in a command with a quoted pass marker.

​
Next steps

  • For every command with its pass marker, see Verification Log.
  • For the authoritative public-versus-local accounting, see Live Evidence.
  • For any term used above that you have not met yet, see the Glossary.