Live Evidence

Tokscale’s claims fall into four strictly separated categories: public-chain facts independently verifiable in the explorer, attributed hosted application evidence, hermetic localnet proofs, and work that does not exist yet. This page is the authoritative source for all four.

Proven on public GIWA Sepolia (chain ID 91342)

Every row is verifiable in the explorer at https://sepolia-explorer.giwa.io. The source and the deployment manifests behind every contract row are public in junhoyeo/tokscale-giwa-contracts, and the explorer reports every contract Tokscale deployed for this evidence as source-verified.

What	Evidence
tUSD “Tokscale Test USD” (ERC-20, 6 decimals, EIP-3009 subset), source-verified on the explorer	`0x58d5608e89b5c1c3b96481a199756b1a292061a9`, created inside its deployer’s constructor in tx `0x109e586d…` (block 31330856)
`TUSDDeployer`, the deterministic deployer that creates tUSD at a pinned CREATE2 salt, source-verified on the explorer	`0x016af5632b7d2d3bbd2a6e589b65e828d1a5b125`
ERC-3009 `exact` settlement executed once, 1.0 tUSD against a consumed authorization nonce, then replay-rejected by the pinned facilitator on retry with the authorization-used selector	tx `0xad1a2f7b…` (block 31331118)
x402 Upto Permit2 Proxy, source-verified on the explorer, deployed from the source-locked upstream artifact	`0x4020A4f3b7b90ccA423B9fabCc0CE57C6C240002`, deployed in tx `0xea7708f6…` (block 31395852)
Permit2 `upto` settlement executed on-chain: the transfer moved the ACTUAL 1.0 tUSD against a signed MAXIMUM of 1.5 tUSD, which is the `upto` scheme’s defining property	tx `0x93bf1e60…` (block 31917698, `status 0x1`)
The replayed `upto` authorization was rejected at the facilitator before broadcast, reverting on `Permit2 InvalidNonce()` during gas estimation. Replay protection is proven by the consumed Permit2 nonce bit, not merely by the error	Same authorization as the settlement above; no second transaction was broadcast
x402 Exact Permit2 Proxy, source-verified on the explorer, deployed to satisfy the pinned facilitator’s startup invariant	`0x402085c248EeA27D92E8b30b2C58ed07f9E20001`, deployed in tx `0x2e5516c9…` (block 31398196)
ERC-6492 UniversalSigValidator (CC0, source-verified on the explorer), deployed with three-way cross-chain code-hash agreement and a Sourcify creation-and-runtime match	`0xdAcD51A54883eb67D95FAEb2BBfdC4a9a6BD2a3B`, deployed in tx `0x147fdcee…` (block 31398214)
Pinned x402-rs facilitator (`ghcr.io/x402-rs/x402-facilitator@sha256:89ab5c03…`) passes startup checks and a smoke settlement on `eip155:91342`	Smoke settlement tx `0x890c0892…`
Multicall3 at the canonical address	`0xcA11bde05977b3631167028862bE2a173976CA11`
Permit2 source comparison closed: observed runtime hash matches the repository source-locked hash for chain ID 91342	`0x000000000022D473030F116dDEE9F6B43aC78BA3` (OP Stack preinstall)

The x402 proxies and the ERC-6492 validator are upstream components. Tokscale deployed them only to satisfy the pinned facilitator’s fixed-address invariant, and their explorer verification comes from upstream compilation inputs: their provenance is recorded, not claimed as Tokscale-authored source. tUSD and TUSDDeployer are the Tokscale-authored contracts. 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 or production authorization. The standalone Upto settlement above proves actual-versus-maximum semantics on-chain, but it was submitted directly with the payer and facilitator held by one key. It is contract-level evidence, not evidence that the hosted product delivered a model response or issued a receipt.

Anyone can rebuild the Tokscale-authored contracts and check them against the live chain, with no Tokscale access. tUSD compiles under Solidity 0.8.30, optimizer enabled at 200 runs, evmVersion = prague:

git clone https://github.com/junhoyeo/tokscale-giwa-contracts
cd tokscale-giwa-contracts
forge fmt --check && forge build && forge test

Then compare the explorer’s bytecode at each address against runtimeCodeHash in the matching manifest under deployments/. Those manifests also pin the tUSD EIP-712 domain separator, the consumed ERC-3009 authorization behind the public exact settlement, and the CREATE2 salt, init-code hash, and observed runtime hash for each deterministic deployment. The maintainers’ own re-validation against live chain state is a separate, non-public target:

bun run contracts:giwa:sepolia:validate
# pass marker: "GIWA_TUSD_LIVE_VALIDATION_OK"

Proven on the hosted payment lane (attributed)

The hosted GIWA Sepolia environment exposes only its user-facing surfaces:

Web console: https://giwa.tokscale.ai.
Gateway: https://api.giwa.tokscale.ai.
Payment and worker services: private, with no public domains.

The public console and gateway were healthy on 2026-08-05. A dedicated macOS Keychain payer, 0x02cdd4a6f1308d310d624292a731c2d276310dc5, signed fresh Stage A exact terms and the live facilitator settled them. Representative explorer evidence: tx 0xf6093345…, tx 0xfe84d874…, and tx 0xca7b2b8d…. Hosted Stage B evidence stops before success. The gateway issued valid body-bound Upto challenges; the same Keychain payer signed the challenge-issued expiry; Permit2 allowance preflight passed; and paid presentations reached claude-gw. The configured models returned provider Unavailable before durable Upto admission. Database inspection found no Upto audit binding, payment row, adapter journal row, or transfer for those attempts. This proves hosted challenge/signing compatibility and fail-closed no-charge behavior. It does not prove terminal Upto settlement or delivery. A hosted Upto run is successful only when the same journey observes all three: a terminal 2xx completion body, a settlement transaction, and a receipt verified against the pinned signer. HTTP 202 is only admission, and an on-chain transfer alone is not delivery. No hosted Upto success marker was emitted on 2026-08-05.

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.

BUILDX_BUILDER=desktop-linux bun run local:e2e
# pass marker: "GIWA_LOCAL_E2E_OK"
# browser artifacts: "verified=receipt,passport,transactions"

Stage A credit top-up with crash recovery: the reconciler is killed mid-settlement and recovers with exactly-once semantics.

bun run local:stage-a:crash:e2e
# pass marker: "GIWA_LOCAL_STAGE_A_CRASH_E2E_OK … authorization_used=1 credited=1"

Stage B upto per-request settlement with fault injection: durable actual-usage settlement across facilitator failures on the local topology.

bun run local:x402:fault:e2e
# pass marker: "GIWA_LOCAL_X402_FAULT_E2E_OK"

Protocol vectors verified three independent ways: Rust (Alloy), TypeScript (viem), and Solidity (Forge). Independent oracles, not one shared library trusted twice.

bun run receipt-vectors:verify
bun run attestation-vectors:verify
# pass condition: all three harness suites green (Rust, TypeScript, Forge)

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.
Terminal hosted Stage B upto proof: the hosted route issues valid challenges and fails closed without charging when claude-gw is unavailable, but no run has yet produced the required terminal 2xx, settlement transaction, and verified receipt together.
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 the contract source and the deployment manifests behind this page, see junhoyeo/tokscale-giwa-contracts.
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.

Start here

Vision

Evidence

Resources

Proven on public GIWA Sepolia (chain ID 91342)

Proven on the hosted payment lane (attributed)

Proven on local localnet (hermetic Anvil fixtures)

Not yet: Phase 2 or pending

Next steps

​Proven on public GIWA Sepolia (chain ID 91342)

​Proven on the hosted payment lane (attributed)

​Proven on local localnet (hermetic Anvil fixtures)

​Not yet: Phase 2 or pending

​Next steps

Proven on public GIWA Sepolia (chain ID 91342)

Proven on the hosted payment lane (attributed)

Proven on local localnet (hermetic Anvil fixtures)

Not yet: Phase 2 or pending

Next steps