ERC-8320 Regulated asset claims registry (Regulated Asset Claim)

Draft · Vaults & DeFi · created 2026-07-03

A registry standard for registering an onchain asset's identity, valuation, investment mandate, and compliance status as signed, versioned claims, which validators and activators approve for publication.

Why it is needed

For assets and capital in a market to find and evaluate each other, core facts such as what an asset is, what it is worth, and where a fund will allocate must exist in a machine-readable, verifiable form. Today, however, this information is scattered across offchain materials such as PDFs or emails, requiring manual checking every time and repeated rework for every integration. Standards such as ERC-4626, ERC-7575, and ERC-7540 define how value is held, divided, and settled, and ERC-7943 and ERC-3643 define how regulated assets are transferred and who may hold them, but all of these address how an asset behaves, not what the asset is, what it is worth, or what a fund intends. Without this standard, every issuer, manager, and tokenization platform discloses information in its own way, resulting in repeated, isolated integrations.

What to implement

In depth

Asset identification and assetId

assetId is computed as keccak256(chainId, contract, subAssetId), distinguishing different sub-assets within a single contract, such as tranches or share classes. registerAsset can only be called by the registry admin, and an assetId that is already registered cannot be registered again. removeAsset deactivates an asset but does not delete its references and claim history, which remain intact. isAssetActive only indicates whether the registry will accept new claims for that asset; the business operational status (launch, suspension, termination, etc.) is contained within the payload defined by the schema.

8 claim types and their owners

There are 8 claim types: IDENTITY (the asset's identity, typically the issuer), VALUATION (valuation, the administrator), MANDATE (investment mandate, the manager), TERMS (subscription, redemption, and fee terms, the manager), COMPLIANCE (holding and trading eligibility, the compliance provider), BACKING (collateral and reserves, the auditor), EVENT (corporate actions, dividends, etc., the issuer or manager), and RISK (risk framework, the risk manager). Each type has its own author, cadence, and questions, and who holds AUTHOR authority for a given type defines that party's actual role (administrator, auditor, etc.). The grant table itself, not a fixed label, is the list of service providers.

Three roles and the maker-checker structure

Roles are granted per (assetId, claimType) and come in three kinds: AUTHOR (propose), VALIDATOR (validate, revoke), and ACTIVATOR (activate, suspend). Only the registry admin can grant or revoke roles via grantRoleToClaimType and revokeRoleToClaimType, and authority for one claim type cannot be used for another. The rule that a proposer cannot also be a validator (maker-checker, four-eyes) is enforced, since validateClaim requires the signer to differ from the author. The signer may be an EOA or a contract implementing ERC-1271 (such as a multisig).

Claim lifecycle states

A claim advances from PROPOSED to VALID to ACTIVE; ACTIVE can be reverted to VALID via suspendClaim, and a claim can be moved to REVOKED from any of PROPOSED, VALID, or ACTIVE via revokeClaim. If validUntil is nonzero and the current time exceeds it, a VALID or ACTIVE claim is automatically treated as EXPIRED without any transaction. That is, a claim is live only when now is greater than or equal to validFrom, and validUntil is 0 or now is less than validUntil. Multiple versions of the same (assetId, claimType) can be ACTIVE simultaneously, and getActiveClaims returns only those that are actually live.

Signatures and the EIP-712 domain

Every state transition function requires a signature over an EIP-712 type hash, verified via ECDSA for EOAs and ERC-1271 for contracts. The domain is fixed with name="RegulatedAssetClaimRegistry", version="1", chainId, and verifyingContract set to the registry address, binding the signature to a specific registry and chain. The signed hash must include a nonce and a deadline, and the call must revert if block.timestamp exceeds the deadline. The signed nonce must equal nonces(signer), and that nonce increments by 1 once the signature is successfully used. targetState is not a caller-supplied input; the implementation must derive it internally from the function that was called.

Payload envelope and content hash

The off-chain payload referenced by uri is the actual content of the claim, such as facts about the asset or fund rules, and contentHash covers the entire file. Every payload must include a common envelope: schemaId, schemaVersion, claimVariant, assetId, claimVersion, attestorProfile, authoredAt, dataAppliesAt, accessClassification (PUBLIC_DISCOVERY, PERMISSIONED_DISCLOSURE, RESTRICTED_EXECUTION, PRIVATE), and data. The envelope's assetId, schemaId, and claimVersion must match the on-chain claim. It is recommended that payloads be stored in a content-addressed system so that the uri remains resolvable for the asset's required retention period.

Discovery and registry approval

Claims are discovered through event history. ClaimProposed and ClaimActivated index assetId and claimType, letting indexers build a market view without calling each contract individually. tags are public labels for filtering only and must not be treated as binding information. If an asset implements IRegistryAnchor, it can manage which registries it approves via setRegistry, getRegistries, and isRegistryApproved, and consumers should only trust claims from registries for which isRegistryApproved returns true. If an asset does not implement this interface, or is off-chain or immutable, registerAsset is merely a declaration that the registry handles that asset, and consumers should rely on claims only if they trust the registry and its admin.

Proposal status

This standard was created on 2026-07-03 and is currently in Draft status. It is an early proposal still undergoing community discussion and revision, and its interfaces or detailed rules may change in the final version.

Things to watch out for

Original ERC · ← ERCs