Shibui Enterprise Ethereum Alliance (EEA)

One verification.
Every chain. Every token.

Shibui is a shared identity primitive that lets institutions verify once and enforce everywhere.

  • Verify once — KYC, accreditation, and compliance checks happen at one institution
  • Use everywhere — That proof works across any token on Base, Optimism, Arbitrum, or mainnet
  • Stay sovereign — Each institution keeps full control of their own compliance process

The Passport System for Tokenized Assets

Five roles make global passports work. The same five make Shibui work.

I
Sovereign
Who verifies
II
Document
What format
III
Border
Who accepts
IV
Interpol
Who revokes
V
Scanner
What reads
Read full story

The Passport System for Tokenized Assets — simplified.

Institutions keep their compliance process. Shibui standardizes the passport format and how tokens scan it.

Problem: identity and compliance proofs do not travel
Problem: identity and compliance proofs don’t travel. The same investor is re-verified again and again.

1) The stamp (what gets published). After an institution completes KYC/KYB, it publishes a compact result: “verified, category, jurisdiction, expiry, revocation.” Not the underlying documents — just the stamped conclusion.

Attestation anatomy: the stamp structure
The stamp is structured data (EAS schemas). This is the ICAO-like part: a shared, machine-readable core.

GLEIF, ISO 20022, and vLEI feed in. Shibui publishes the stamp.

2) Two passports (holder + asset). One document is about the holder (who they are / what category they are). Another is about the asset (what border rules this token enforces).

Full architecture: how stamps connect to token enforcement
Same passport format → any token on any chain can scan the stamp and enforce border rules.

3) The border check (who accepts whose stamp). Each token/issuer chooses which attesters it trusts for which topics. Enforcement is deterministic: allow/deny based on valid stamps.

Scope boundary: what Shibui standardizes vs what it does not
Scope: Shibui standardizes format + scanning + revocation. It does not run onboarding, renewals, lost-passport handling, or liability.

In one sentence: Shibui is the shared passport format for tokenized assets — so verification becomes portable, and enforcement becomes universal.

How it works

1

Institution verifies

GLEIF, your KYC provider, or compliance team does their normal work.

2

Proof published

Verification result is published as an EAS attestation on-chain.

3

Tokens read proof

Any ERC-3643 token on any supported chain can check eligibility.

For builders
  • 3 document formats (EAS schemas) — Investor Eligibility (the passport), Issuer Authorization (accreditation certificate), Wallet-Identity Link (visa pages)
  • Scanner network (EAS) — Ethereum Attestation Service already deployed on 15+ chains with built-in revocation and expiry
  • Border enforcement (ERC-3643) — Token issuers control trust via addTrustedAttester() — granular per compliance topic
  • Multi-chain support — Works on Base, Optimism, Arbitrum, and Ethereum mainnet

Identity Management Solutions — Reference map

A curated landscape of identity + compliance approaches (on-chain primitives, credential standards, institutional platforms, pilots, and Travel Rule networks).

Open the reference map