Dojang: On-Chain Attestations

Dojang (도장, the seal) is GIWA’s attestation service: trusted off-chain facts issued as on-chain attestations, with zero PII on-chain. It is built entirely on Ethereum Attestation Service (EAS), deployed at the standard OP Stack predeploy slots, with a GIWA issuer and schema framework on top. The key design property: identity lives as attestations about an address, never as tokens owned by an address. That makes Dojang credentials non-transferable by construction, the exact property ERC-8004 lacks, and Dojang gets it for free. This is the same property the Builder Passport inherits.

Attestation types

Attestation type	Schema content	What it proves
Verified Address	`bool isVerified`	This wallet passed KYC with the issuer (currently Upbit Korea; a TESTNET FAUCET attester exists on Sepolia)
Balance Root	`coinType, snapshotAt, leafCount, totalAmount, root`	Merkle root summarizing all users’ balances at a snapshot
Verified Balance	`balance, salt, proofs[]`	Per-user merkle proof against the Balance Root: provable without revealing anyone else’s balance
Verified Code	`codeHash, domain`	An off-chain OTP verified on-chain

Tokscale’s Usage Root design borrows the Balance Root / Verified Balance pattern directly: a public commitment with private per-user proofs. See Evidence Ladder.

Contract architecture (public GIWA Sepolia, chain ID 91342)

EAS itself sits at the OP Stack predeploy slots, permissionless. GIWA’s framework sits on top. All addresses below are live on public GIWA Sepolia:

Contract	Address	Role
SchemaRegistry (predeploy)	`0x4200000000000000000000000000000000000020`	Read schema records
EAS (predeploy)	`0x4200000000000000000000000000000000000021`	Issue and read attestations
SchemaBook	`0x78cBb3413FBb6aF05EF1D21e646440e56baE3AD6`	Registry of Dojang schemas
DojangAttesterBook	`0xDA282E89244424E297Ce8e78089B54D043FB28B6`	Registry of authorized official issuers
AttestationIndexer	`0x9C9Bf29880448aB39795a11b669e22A0f1d790ec`	Indexes Dojang attestations
AddressDojangResolver	`0x692009FE206C3F897867F6BF7B5B45506B747F9e`	Per-schema EAS hooks fired on issue/revoke (Verified Address schema)
DojangScroll	`0xd5077b67dcb56caC8b270C7788FC3E6ee03F17B9`	Convenience read contract: `isVerified(address, bytes32 attesterId)`

The documented Verified Address schema UID is 0x072d75e18b2be4f89a13a7147240477481c4b526d5795802acba59046b426e08 and its schema text is bool isVerified. Reading a Verified Address result is one call to DojangScroll.isVerified, and GIWA’s docs ship a ~10-line onlyVerified Solidity modifier. Attester IDs are namespaced (keccak256("dojang.dojangattesterids.<issuer>")), making the system multi-issuer by design; external issuers are explicitly invited.

The three permission lanes

Lane	Contracts	Permission	Tokscale’s position
Read + gate	DojangScroll → EAS	Open	Verified Address status is available as provenance; gating Passport registration on it is Phase 2
Publish	SchemaRegistry + EAS	Permissionless	Register Tokscale schemas and issue attestations as our own attester; the first public Usage Root is now live on GIWA Sepolia
Official Dojang issuer	DojangAttesterBook	GIWA approval	Phase 2 graduation: apply with schemas already live and indexed

Archived GIWA Testnet Faucet compatibility fixture

On GIWA Sepolia, the DojangAttesterBook resolves the documented Testnet Faucet attester ID to 0x63CCe2b569A7bC35895ee24306c1512fefc06121. Tokscale retains one block-pinned read-set against this public attester as an interoperability regression fixture: it proves that our validator can read GIWA’s existing Verified Address graph end to end. It is archived test evidence, not a Tokscale issuer credential. It is not rendered on the public disclosure page, has no public product API, and does not represent a Tokscale KYC claim or official issuer status.

Tokscale’s read-vs-publish split

Read side (delivered, read-only). Tokscale consumes deployed Dojang as provenance through a fail-closed validator: it requires the complete GIWA Sepolia read set at one pinned block, rechecks the block hash, pins the EIP-1967 implementation slots, and verifies the schema fingerprint and the EAS record behind any isVerified result. DojangScroll.isVerified alone is never treated as sufficient. The API contract carries informationalOnly: true, so an observation cannot become a payment or entitlement authority. Tokscale does not deploy Dojang contracts and is not a Dojang issuer.

Owner verification and Passport visibility

The console’s live verification belongs to the exact GIWA Sepolia wallet that authenticated the session. It is not an account-wide badge. A linked wallet cannot stand in for the signed-in wallet, and a session without wallet authentication does not request or refresh Dojang evidence. A refresh asks a server worker to make one bounded observation at a finalized block. The worker accepts a positive result only after it checks the pinned policy, contract graph, issuer, schema, and EAS attestation. It records either a verified or unverified observation for that wallet. It never converts a reader failure into an unverified result.

Observation	Meaning
Verified	A matching active Dojang attestation was observed at the displayed finalized block.
Not verified	No matching active attestation was found at that finalized block.
Refreshing or stale	A new observation is pending, or the last trustworthy observation is out of date.
Unavailable	A trustworthy result could not be established. This is not negative evidence.

The contract keeps that observation separate from Passport visibility. An observation is publicly visible only when it belongs to the exact active Passport publication for the same wallet, wallet epoch, and policy version. Republish, wallet replacement, or a policy change creates a new publication boundary. Evidence from an earlier publication remains private and cannot appear on the new public Passport by accident. The owner view therefore reports both facts: the observation and whether it is public, awaiting an observation for the current publication, attached to another published wallet, or private because there is no active Passport publication. This preserves the reader-facing distinction between a missing attestation and a missing trustworthy observation. The deployed-read check is a bounded, block-pinned observation (fixture block 31129890), run by an operator with a caller-supplied RPC. It sends no transaction and needs no key:

DOJANG_GIWA_RPC_URL=https://sepolia-rpc.giwa.io bun run dojang:giwa:validate

A read-set or attestation mismatch fails the run; a missing endpoint exits as a skipped external validation. It proves the deployed Dojang graph and the public Testnet Faucet attestation at that one block; it is not evidence of a continuously available live integration. Publish side (permissionless). Anyone can register schemas and attest on EAS. Tokscale’s schema set (Usage Root mirroring Balance Root, Verified Usage mirroring Verified Balance, Skill Signal, Bounty Completion) follows Dojang’s own commitment idiom. The first Usage Root is now anchored on public GIWA Sepolia; see Usage Root EAS integration-test attestation below.

Local and public are never mixed. The local fixture (LocalDojangScroll) is sealed and deterministic; local artifacts are never shown next to Sepolia explorer links. Anvil borrows chain ID 91342, so chain ID is not a network identity; see Network Separation.

The Phase 2 path: official issuer

Phase 2 registers Tokscale in the DojangAttesterBook as an official issuer, under the attester ID keccak256("dojang.dojangattesterids.tokscale"), after GIWA approval. Until then, Tokscale’s public EAS records are permissionless application attestations, not official Dojang issuer evidence. Once approved, this page and the public disclosure will show the registered attester ID and the first official issuer attestation separately from the testnet record below.

Usage Root EAS integration-test attestation

Tokscale’s first public Usage Root is anchored on GIWA Sepolia (chain ID 91342). It is a real attestation published by Tokscale’s disposable one-time test attester under an application-defined, permissionless EAS schema. It commits a Merkle root over a frozen three-receipt integration-test vector, mirroring Dojang’s Balance Root idiom. The public disclosure page labels this record Usage Root EAS integration-test attestation. It demonstrates the complete publish-and-read path under a Tokscale-owned schema without claiming that Tokscale is a GIWA Dojang issuer. The record is fixture-backed: its recipient is a test-vector subject, and it is not a Verified Address, identity credential, KYC result, wallet-ownership claim, or production-usage record.

Field	Value
Receipt Attestation V1 schema UID	`0xc52687af0e022f52c2ffdfb0287a132a185e361d480cfdd1f92dfeb199622c70`
First attestation UID	`0xfd08b025d6f2bca820f1df27d21d77b191cb1398ead6ecfd4a0a96138845a9e5`
Test publisher	Tokscale-controlled disposable test attester
Attester (disposable, one-time)	`0x5888c8CFF775bbe3eaFEA9B2158C982cd3a7671D`
EAS (predeploy)	`0x4200000000000000000000000000000000000021`
Dojang reference	None; both Dojang reference fields are zero
Recipient	Fixture subject `0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266`
Receipt root	`0xf5dd2b6805f87aa62ce37754a22ebcd59dceac22b01c4c3639a110516ed70ebe`
Summary commitment	`0x3652a3ef2b66c9292b173509d998c6ca904995edecc73120727d38e2674e4ed3`
Epoch / subject epoch / receipts	19675 / 7 / 3
Anchor block	`32824105` (`0x4441da8d2e8a4949d2acdb05b2008844b95c152586a7569086b5d44ffdfc34aa`)
Anchor transaction	`0x44b2cab6...f7b2`
Schema registration transaction	`0xc5389dfa...5173`

Anyone can confirm the anchor independently against the public RPC, with no key and no transaction:

cast call 0x4200000000000000000000000000000000000021 \
  'isAttestationValid(bytes32)(bool)' \
  0xfd08b025d6f2bca820f1df27d21d77b191cb1398ead6ecfd4a0a96138845a9e5 \
  --rpc-url https://sepolia-rpc.giwa.io
# -> true

The canonical record is checked into the Tokscale GIWA repository. The attester key is a disposable one-time testnet signer; this anchors a real public test vector, not a production identity or usage authority.

Next steps

For the Tokscale schema that mirrors Dojang’s Balance Root, see Receipt Attestation.
For the credential Dojang is meant to gate, see Builder Passport.
For the full address list including GIWA’s own Dojang contracts, see The Public Chain.
For why an anonymity-first design cannot run on this chain, see Why GIWA.

Identity

Proof

Dojang: On-Chain Attestations

Attestation types

Contract architecture (public GIWA Sepolia, chain ID 91342)

The three permission lanes

Archived GIWA Testnet Faucet compatibility fixture

Tokscale’s read-vs-publish split

Owner verification and Passport visibility

The Phase 2 path: official issuer

Usage Root EAS integration-test attestation

Next steps

​Attestation types

​Contract architecture (public GIWA Sepolia, chain ID 91342)

​The three permission lanes

​Archived GIWA Testnet Faucet compatibility fixture

​Tokscale’s read-vs-publish split

​Owner verification and Passport visibility

​The Phase 2 path: official issuer

​Usage Root EAS integration-test attestation

​Next steps

Attestation types

Contract architecture (public GIWA Sepolia, chain ID 91342)

The three permission lanes

Archived GIWA Testnet Faucet compatibility fixture

Tokscale’s read-vs-publish split

Owner verification and Passport visibility

The Phase 2 path: official issuer

Usage Root EAS integration-test attestation

Next steps