Cowrie Research

onchainid-primary-sources-2026-05-08

3 min read

ONCHAINID primary-source snapshot

Fetched: 2026-05-08 UTC

1) ONCHAINID overview

Source: https://docs.erc3643.org/erc-3643/smart-contracts-library/onchain-identities

Selected excerpts from the official source:

ONCHAINID is a blockchain-based identity management system that creates a unique, globally accessible identity for each participant.

ONCHAINID complies with the ERC-734 and ERC-735 standards.

All ONCHAINIDs are deployed as upgradeable proxies (beacon proxy) through an IdFactory contract.

This cross-chain compatibility allows claims signed on one chain to be valid across multiple chains without requiring new signatures from claim issuers.

Additional signals from the source:

  • The docs frame ONCHAINID as a reusable identity-and-claims contract rather than just a token whitelist entry
  • Deterministic deployment and address reuse across chains are one of the most important mechanism clues because they make issuer attestations portable without changing the identity anchor
  • The same page also notes that ONCHAINIDs can function directly as wallets and discusses possible ERC-4337 compatibility

2) ONCHAINID interface

Source: https://docs.erc3643.org/erc-3643/smart-contracts-library/onchain-identities/onchainid-interface

Selected excerpts from the official source:

The ONCHAINID interface defines the set of functions and events used to manage identities and claims on the blockchain. It extends the functionality of two key interfaces: IERC734 and IERC735.

function execute(address _to, uint256 _value, bytes calldata _data) external payable returns (uint256 executionId);

function addClaim(uint256 _topic, uint256 _scheme, address issuer, bytes calldata _signature, bytes calldata _data, string calldata _uri) external returns (bytes32 claimRequestId);

Additional signals from the source:

  • The interface makes clear that ONCHAINID is not only a passive claims bucket; it also has execution, approval, and key-purpose management surfaces
  • This reinforces the view that ONCHAINID sits closer to a programmable identity account than to a simple credential registry

3) Identity Registry

Source: https://docs.erc3643.org/erc-3643/smart-contracts-library/onchain-identities/identity-registry

Selected excerpts from the official source:

The Identity Registry is responsible for managing and verifying the identities of participants in the ecosystem.

During a token transfer or any other regulated action, the Identity Registry checks the participant’s ONCHAINID and associated claims to ensure compliance.

If all claims are valid and meet the requirements, the isVerified function returns true, allowing the transfer to proceed. If not, it returns false, blocking the transfer.

Additional signals from the source:

  • The identity object alone does not decide eligibility; the transfer path is routed through registry logic at token-operation time
  • This page is the clearest evidence that ONCHAINID belongs in the corpus as compliance-credential infrastructure, not generic self-sovereign identity rhetoric

4) Claim Topics Registry + Trusted Issuers Registry

Sources:

Selected excerpts from the official sources:

The Claim Topics Registry (CTR) is responsible for listing the claim topics required for a token.

Registers a ClaimIssuer contract as a trusted claim issuer.

Returns an array of all claim issuer addresses that are allowed to issue a given claim topic.

Additional signals from the sources:

  • These registries reveal where practical authority really sits: token operators and registry owners choose which claims matter and which issuers are trusted to supply them
  • That makes ONCHAINID portable at the contract layer but still policy-gated at the issuer and claim-topic layer

Notes

  • ONCHAINID appears best cataloged as onchain identity contract / compliance-claims infrastructure / trusted-issuer credential layer.
  • The key reusable mechanism is not merely “identity onchain” but the way portable identity contracts plug into token-specific issuer allowlists and claim-topic requirements.
  • No standalone ONCHAINID whitepaper surfaced in this pass.

Graph View