Cowrie Research

gateway-protocol

3 min read

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
  • Tags: solana-ecosystem
  • Summary: Gateway Protocol is reusable admission middleware. Gatekeepers do the checks, issue wallet-bound passes, and downstream apps or token hooks just test pass state. The useful question is not did someone do KYC, but who gets to issue, freeze, revoke, or recognize those passes.
  • 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 cross-chain oracle token model framing is the right starting point. Gateway Protocol imports offchain verification decisions into onchain admission checks instead of pretending identity itself moved onchain.
    • The mechanism is simple enough to keep straight: a Gatekeeper network defines the framework, a Gatekeeper issues the pass, and the dApp or token hook only checks whether an accepted pass is active.
    • Pass state is the live control surface. Active, expired, frozen, and revoked are not edge cases; they are the actual policy levers.
    • Gatekeepers are closer to audited admission operators than generic KYC vendors. The whitepaper gives them staking, slashing, audit, and removal logic, which makes issuer admission part of the protocol design.
    • The governance story is weaker than the neutrality pitch. Guardians have supervisory power and Identity.com initially acts as sole maintainer, so governance concentration remains part of the trust model.
    • The downstream Civic repos are the reason to keep the note. TokenGuard and the Transfer Hook show the same pass primitive reused beneath Solana apps, NFT flows, and permissioned-token transfers without rewriting each guarded app from scratch.
  • 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:

Internal linkages

  • Regulated-token stack contrast where issuer allowlists and claim registries sit closer to the asset itself: erc-3643 and onchainid.
  • Shared-attestation contrast where publication is generalized and verifier admission is looser: ethereum-attestation-service.

Control surface

  • Practical authority sits with gatekeeper admission, network-framework selection, guardian oversight, pass-state transitions, and whichever downstream apps or token hooks decide which networks they will honor.

  • That is the useful cut. Gateway Protocol is reusable compliance and admission middleware, not a neutral identity layer.

  • Last reviewed: 2026-06-18 UTC

Graph View