Gateway Protocol

  • Name: Gateway Protocol
  • URL: https://github.com/identity-com/on-chain-identity-gateway
  • Category: wallet-bound access-control protocol / permissioned-token middleware / identity-verification oracle infrastructure
  • Summary: Gateway Protocol is best understood not as a generic KYC product or a branded pass program, but as a reusable wallet-bound access-control layer that bridges offchain identity checks into onchain permission decisions. Its core mechanism is the split between gatekeeper networks that define a verification framework, gatekeepers that perform offchain checks and issue non-transferable passes, and dApps or token hooks that only need to verify the presence and state of the right pass. That makes Gateway Protocol a useful comparison class for attestation registries, permissioned-token transfer hooks, and issuer-admission middleware: the important question is not just whether a user has been checked, but who can issue the pass, which network’s framework it represents, how pass state changes over time, and where governance and slashing authority sit.
  • What it does:
    • Lets a dApp or token issuer require a wallet-bound Gateway Pass before permitting interaction, transfer receipt, or other onchain actions
    • Organizes verification into Gatekeeper networks, each tied to a specific requirements framework such as jurisdiction, age, investor status, residency, or other policy conditions
    • Lets approved Gatekeepers perform offchain compliance or identity checks and then issue, freeze, unfreeze, expire, or revoke passes tied to a wallet
    • Separates pass verification from personal-data custody, so the relying dApp checks pass presence and state instead of storing user KYC material itself
    • Includes open-source Solana libraries and programs for pass issuance, pass discovery, and onchain integration by dApps
    • Supports downstream gating modules such as TokenGuard and the Civic Pass Transfer Hook, which use Gateway passes to guard NFT mints, payment flows, and permissioned-token transfers without rewriting the guarded protocol itself
    • Adds governance and supervision layers through governance-token staking, guardian audits, gatekeeper admission, and network-level framework changes
  • Key claims:
    • The whitepaper’s most useful framing is cross-chain oracle token model. That is a better analytical starting point than treating the system as a simple identity app, because the protocol is really about importing offchain verification decisions into onchain admission checks.
    • The main mechanism is the split between the framework, the pass, and the verifier. A Gatekeeper network defines the rules; a Gatekeeper attests that a wallet satisfies them; the dApp only checks for an active pass from an accepted network.
    • Pass state is an important control surface. The whitepaper defines active, expired, frozen, and revoked states, which means ongoing eligibility and investigatory pauses are built into the design rather than treated as offchain exceptions.
    • The gatekeeper role is more than KYC provider. The whitepaper positions gatekeepers as audited oracle operators that can be admitted to multiple networks, are staked and slashable, and can be removed if they fail service, documentation, or audit requirements.
    • Governance is more centralized-in-practice than the basic token story suggests. The governance docs introduce guardians with network-specific supervisory power and note that Identity.com initially serves as sole maintainer of the protocol, which makes implementation and governance drift a material part of the trust model.
    • The downstream Civic repos sharpen the real comparative value. TokenGuard shows the pass as a composable precondition for unrelated Solana apps such as Candy Machine mints, while the Transfer Hook repo shows the same primitive reused at the token-transfer layer for permissioned assets and RWA-style markets.
    • Those downstream repos also surface an important architectural insight: Gateway Protocol is not just for one issuer’s KYC widget. It can function as a lower-layer admission rail beneath other apps, hooks, and token standards.
    • Gateway Protocol belongs in the active corpus because it isolates a distinct design family between attestation registries and permissioned assets: wallet-bound passes issued by audited gatekeepers and checked by any onchain program that wants a reusable admission test.
  • Whitepaper: Yes. The strongest primary materials in this pass were the official Gateway Protocol whitepaper repository and section files, the open-source on-chain gateway monorepo, and downstream Civic integration repos collected in ../whitepapers/gateway-protocol-primary-sources-2026-05-14.md.
  • Sources:
  • Last reviewed: 2026-05-14 UTC