Issuer onboardingmainnet

Become an HSK Passport issuer

Stake native HSK on HashKey Chain mainnet IssuerRegistry, publish your metadata, and start issuing credentials. Your tier (Community / KYC Provider / Institutional) is determined automatically by stake size. Misissuance is slashable via 48-hour governance Timelock. Credentials and KYC continue to issue on testnet pending third-party audit.

Soft-mainnet — owner is an EOA today
The IssuerRegistry on mainnet is owned by a deployer EOA 0x0b17…50DF, not yet a Safe + 48h Timelock. Migration to multi-sig governance is planned for Q3 2026. If the deployer key is compromised before then,slash() can be called without delay. Stake at your own risk — the Timelock copy below describes the post-migration end state.
Community
0 HSK

Limited groups, public sandbox issuance. Best for hackathon entries, research projects, demo issuers.

KYC Provider
≥ 1,000 HSK

Full credential issuance, reputation tracked publicly, eligible for production dApp integrations.

Institutional
≥ 10,000 HSK

All KYC Provider rights plus institutional credential types and direct dApp listing priority.

1 · Build your metadata

On-chain we store your stake, tier, and reputation. Off-chain at your metadataURI we expect this JSON shape (Issuer.json schema). Fill the form below; the JSON updates live.

Operating name
Website
Compliance contact email
KYC method
Jurisdictions (comma-separated ISO codes)
Supported credential types

Final issuance authority is on-chain via HSKPassport.approveIssuer + delegate assignment per group.

Key custody (recommended)

KYC Provider tier should use HSM, MPC, or multisig. hot-wallet is only acceptable for Community tier.

Generated metadata.json
{
  "name": "",
  "contact": {
    "email": ""
  },
  "kycMethod": "sumsub",
  "jurisdictions": [],
  "publishedAt": "2026-05-07T11:44:08.702Z"
}