Skip to main content
GIWA Dojang 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

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: 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

​
The TESTNET FAUCET attester (for demos)

On GIWA Sepolia, the DojangAttesterBook resolves the documented Testnet Faucet attester ID to 0x63CCe2b569A7bC35895ee24306c1512fefc06121. Tokscale demos use it to stand in for a KYC issuer. It is technical test evidence, not a KYC claim, not an allowlisted issuer, and it never authorizes payment, credit, Passport eligibility, or Earn access.

​
Tokscale’s read-vs-publish split

Read side (delivered, read-only). Tokscale consumes deployed Dojang purely 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. Every successful result is explicitly informationalOnly: true. Tokscale does not deploy Dojang contracts, is not a Dojang issuer, and Dojang is not a payment or entitlement authority in the product. 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:
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. Anchoring has landed only on the local EAS fixture so far; the first real Usage Root on public Sepolia is the next milestone, tracked on Live Evidence.
Local and public are never mixed. The local fixture (LocalDojangScroll) is sealed, deterministic, and marked informational-only; 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"). This is framed as a graduation, not a pitch: the schemas will already be live and indexed on the public chain, so the application is a formality over running infrastructure rather than a promise. It rides Dojang’s own arc (KYC attestation live, balance attestations live, professional credentials in progress via the Shinhan Bank pattern, third-party issuers invited).

​
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.