root registry

Issuer dashboard

The issuer registry stores the credential root plus committed sanctions and revocation roots. Gates compare all three roots against the proof public signals before moving value.

registered roots

Credential, sanctions, and revocation roots

issuer id-

credential root-

sanctions root-

revocation root-

public directory

Issuer metadata

Metadata is fetched server-side with private-IP and redirect rejection before allowlisted fields are shown here.

issuer	name	jurisdiction	license	metadata
loading	-	-	-	-

root provenance · real data

Where these roots come from

The roots are not placeholder data. The credential is backed by a real KYC-verified identity and the issuer roster is exact-name screened against the live OFAC list before publishing roots on Stellar testnet.

Credential — real Sumsub KYC

provider: Sumsub (GREEN applicant)
identity: country + DOB→age from a verified NGA passport
note: investor_type is issuer-asserted, not independently verified
root tx: 0441ebf5…

Sanctions — real OFAC SDN list

source: U.S. Treasury OFAC SDN list (19,123 entries)
proof: in-circuit non-membership; an exact SDN/ALT roster match is inserted into the sanctions tree and cannot prove absence
sanctions tx: 6bbd81e4…
revocation tx: da9cf4ad…

run it live · Sumsub

Verify your identity yourself

Run a real Sumsub identity verification in your browser. The short-lived access token is minted by the AnchorShield backend — the secret never touches the browser. When you reach GREEN, the verified document maps to the exact credential fields the circuit uses (kyc_passed, country, age). Sandbox mode — use Sumsub's test documents.

idle — click to start a live KYC session

policy checks

Policies consume the same credential root

The public signal layout appends sanctions and revocation roots at indices 17 and 18 so indices 0-16 stay stable for existing action binding.

gate	policy	asset	amount	root checks
loading	-	-	-	-