# Tokscale

## Docs

- [Dojang: On-Chain Attestations](https://docs.giwa.tokscale.ai/builder-passport/dojang.md): Learn how Tokscale reads Dojang as provenance, publishes its own schemas permissionlessly, and what official issuer status would add.
- [Dual Identity: GitHub & Wallet](https://docs.giwa.tokscale.ai/builder-passport/dual-identity.md): Learn how GitHub and wallet sign-in resolve to one account, and the replay and substitution defenses on both flows.
- [Verified Usage and the Evidence Ladder](https://docs.giwa.tokscale.ai/builder-passport/evidence-ladder.md): Learn what separates self-reported usage from attested usage, and what it takes for a receipt to climb each rung.
- [Builder Passport](https://docs.giwa.tokscale.ai/builder-passport/overview.md): Learn what goes into a Passport, why it cannot be sold or transferred, and which parts of it are not built yet.
- [Verifying a Receipt](https://docs.giwa.tokscale.ai/builder-passport/verify-a-receipt.md): Learn to recompute every digest yourself, from the EIP-712 signature to the merkle path and the on-chain attestation.
- [Gateway API](https://docs.giwa.tokscale.ai/gateway/api.md): Route table, authentication, 402 payment challenges, receipts, and fail-closed behavior of the giwa-gateway binary and its x402 adapter.
- [Client Integration](https://docs.giwa.tokscale.ai/gateway/client-integration.md): What changes in an AI client to route through the verified gateway, and what gateway-verified usage means once it does.
- [Contracts](https://docs.giwa.tokscale.ai/gateway/contracts.md): The test payment asset, why a shared chain ID can never authorize a deployment, and how upstream bytecode is pinned before it ships.
- [Network Separation: Localnet vs Sepolia](https://docs.giwa.tokscale.ai/gateway/network-separation.md): Learn why a valid receipt proves nothing about which network produced it, and which declaration and binding actually draw the line.
- [Gateway Overview](https://docs.giwa.tokscale.ai/gateway/overview.md): The processes behind the gateway, how one paid request moves through them, and which stages are proven on the public chain versus locally.
- [The Public Chain](https://docs.giwa.tokscale.ai/gateway/public-chain.md): GIWA Sepolia network facts, every Tokscale contract deployed on it, the transactions that prove the payment path, and the read-only checks.
- [Receipt Attestation (EAS)](https://docs.giwa.tokscale.ai/gateway/receipt-attestation.md): Learn the EAS schema behind a Usage Root, how salting keeps epoch totals private, and how the publisher avoids double-attesting.
- [The Gateway and Its Workers](https://docs.giwa.tokscale.ai/gateway/service.md): How the gateway admits and prices a request, and what each of the five bounded worker processes around it is allowed to do.
- [UsageReceiptV1](https://docs.giwa.tokscale.ai/gateway/usage-receipt-v1.md): The signed off-chain statement the gateway issues per request: its EIP-712 typed data, evolution rule, and four-step provability chain.
- [Verification Log](https://docs.giwa.tokscale.ai/gateway/verification-log.md): What the maintainers' harness runs, what each target proves, and the exact pass marker it prints on success.
- [x402 Payments on GIWA](https://docs.giwa.tokscale.ai/gateway/x402-payments.md): How Tokscale ported the x402 payment protocol to GIWA, how a 402 challenge becomes a settlement, and what prevents a double settle.
- [x402 Stage A: Credit Top-Up](https://docs.giwa.tokscale.ai/gateway/x402-stage-a.md): Learn why a plain token transfer can never mint credit, and what evidence the reconciler demands before it does.
- [x402 Stage B: Per-Request Settlement](https://docs.giwa.tokscale.ai/gateway/x402-stage-b.md): Learn how one signature binds to exactly one request, and the three independent layers that prevent a double settlement.
- [Tokscale on GIWA](https://docs.giwa.tokscale.ai/index.md): Pay per model request with x402, get a signed receipt for every call, and turn verified usage into a Builder Passport on GIWA.
- [Design Principles](https://docs.giwa.tokscale.ai/overview/design-principles.md): Learn the constraints the repository actually enforces, from network identity rules to labels that are allowed to say not yet.
- [FAQ](https://docs.giwa.tokscale.ai/overview/faq.md): Direct answers to hard questions about Tokscale on GIWA, covering what is public, what is forgeable, token plans, and x402 support.
- [Glossary](https://docs.giwa.tokscale.ai/overview/glossary.md): Definitions for the terminology used across the Tokscale documentation, from the evidence ladder to the V1 wire identifiers.
- [Live Evidence](https://docs.giwa.tokscale.ai/overview/live-evidence.md): Which Tokscale claims are verifiable on-chain today, which are hermetic fixtures only, and which do not exist yet.
- [Manifesto: Proof of Actual Work](https://docs.giwa.tokscale.ai/overview/manifesto.md): Why an AI-skill premium exists that almost nobody can verify, and the constraints Tokscale accepts to be the exception.
- [Five Proven Patterns](https://docs.giwa.tokscale.ai/overview/market.md): Comparables, market sizing, and the structural fixes that keep Tokscale out of the web3 reputation graveyard.
- [The Proof Loop](https://docs.giwa.tokscale.ai/overview/proof-loop.md): How paid gateway usage becomes signed receipts, an anchored Usage Root, a Builder Passport, and ecosystem income.
- [Why GIWA](https://docs.giwa.tokscale.ai/overview/why-giwa.md): Learn which three GIWA primitives the product depends on, and why an anonymity-first competitor could not run here.
- [The Open-Source Base](https://docs.giwa.tokscale.ai/usage-tracker/open-source-base.md): How the shipped CLI and the GIWA gateway relate, and why one produces forgeable data while the other does not.
- [Quickstart: Track Your Usage](https://docs.giwa.tokscale.ai/usage-tracker/quickstart.md): Read token usage from the coding agents already installed on your machine, then publish a profile you control.
- [Client Reports](https://docs.giwa.tokscale.ai/usage-tracker/report-clients.md): Which coding agents developers actually work in, how much they consume, and which models they reach for inside each one.
- [Model Reports](https://docs.giwa.tokscale.ai/usage-tracker/report-models.md): Real-world model adoption measured from developer machines, with token economics and the coding agents each model runs inside.
- [Supported Clients](https://docs.giwa.tokscale.ai/usage-tracker/supported-clients.md): Every coding agent whose token usage the CLI can read locally, and where each one keeps its data on disk.
- [How Usage Reports Work](https://docs.giwa.tokscale.ai/usage-tracker/usage-reports.md): The snapshot, the two comparison windows, and the ranking rules every client and model report is built on.

## Optional

- [Explorer](https://sepolia-explorer.giwa.io)
- [Faucet](https://faucet.giwa.io)
- [GIWA Docs](https://docs.giwa.io)