The ERC-8319 Regulatory Compliance Protocol (RCP) has been submitted to Ethereum’s official standards repository, ethereum/ERCs. Oraclizer’s shared reference for the legal effect of regulatory enforcement actions on tokenized assets has cleared every automated check in the repository and, as a Standards Track proposal, now awaits Ethereum editor review. RCP was developed by Oraclizer together with Horizen Labs (CEO Rob Viglione) and Dan Spuller, EVP of Industry Affairs at the Blockchain Association.
From a Draft to Ethereum’s Official Process
Last December, we released our own draft of the protocol. This submission means that document has entered Ethereum’s official standardization process: the same public repository, and the same review, that the token standards the whole industry stands on, such as ERC-20 and ERC-721, have passed through. The number ERC-8319 is now the proposal’s permanent, citable public identifier.
RCP: Into Ethereum’s standards process
Dec 2025
EIP-RCP draft released
Self-published draft, first public reference point for compliant tokenization.
Jan 2026
Co-authors join
Horizen Labs and Dan Spuller (Blockchain Association) join as EIP-RCP co-authors.
Jul 2026
Submitted as ERC-8319
ethereum/ERCs, Standards Track. All CI checks passed. Assigned a permanent, citable number. Under editor review.
Figure 1: The path from a self-published EIP-RCP draft to submission as ERC-8319 in Ethereum’s official standards repository.
What the ERC-8319 Regulatory Compliance Protocol Establishes
The ERC-8319 Regulatory Compliance Protocol is the shared regulatory reference that tokenized assets have lacked. Until now, Ethereum held no common, citable foundation for the legal meaning of regulatory enforcement. It is not a glossary. It brings together, as a single reference, five things: a closed taxonomy of six regulatory actions (freeze, seize, confiscate, liquidate, restrict, recover); the legal effect of each, whether it can be undone and what becomes of ownership and finality; the regulatory dynamics that govern how an asset moves between these states; 31 compliance requirements compiled from the published guidance of 15 financial regulators (FATF, BIS-IOSCO, ESMA, and others) under five principles; and a coverage mapping of how far existing standards already meet them.
Figure 2: RCP is one citable reference in five parts: a taxonomy of six regulatory actions, the legal effect of each, the dynamics between them, 31 requirements from 15 regulators, and a coverage map. It layers non-invasively on existing standards.
Deployed security-token standards handle this enforcement each in their own terms, or leave its legal effect undefined altogether. In one example, a regulator’s reversible freeze and a court’s irreversible confiscation can remain the very same action on-chain. RCP reaches past any single case to give the whole range of regulatory enforcement one defined reference that standards can share.
These definitions rest on a state model checked with Isabelle/HOL formal verification, so they stand on verified ground rather than on our word. Above all, RCP is a non-invasive reference layer that sits on top of existing standards without touching them: it mandates no interface and adds no code dependency, and a standard simply references it, voluntarily, when it needs to.
Why This Submission Matters
The biggest barrier to bringing institutional capital markets on-chain has never been the technology; it has been the absence of a common language for describing regulatory compliance. Regulatory semantics is a separate discipline for most protocol designers, and until now the Ethereum process offered no neutral, citable reference for the legal effect of enforcement actions. The ERC-8319 Regulatory Compliance Protocol places exactly that shared regulatory reference inside Ethereum, kept under the same process and license as the standards that would cite it, and gives future standards a foundation to build their own compliance upon.
RCP confers no authority and creates no obligation; it documents positions that regulators have already published. The policy perspective Dan Spuller contributed makes that plain: by foregrounding due process and privacy-first compliance, it keeps RCP legible as a set of tools for lawful workflows, not a built-in enforcement mandate. That Horizen Labs and a Blockchain Association policy leader signed on as co-authors shows the work carries the weight of both industry and policy, not the pitch of a single company.
What Comes Next
The ERC-8319 Regulatory Compliance Protocol is now open to the Ethereum community’s review. Public discussion is underway on the Ethereum Magicians thread, and feedback is welcome both before and during editor review. This is one step in a long road toward regulatory-compliance standardization, and we will keep sharing what comes next here.
The full proposal is available for download below.
Learn More
- Read the full proposal (ERC-8319): the Regulatory Compliance Protocol specification on ethereum/ERCs
- Public discussion (Ethereum Magicians): ERC-8319: Regulatory Compliance Protocol
- Submission and review status: ethereum/ERCs pull request #1848
- EIP-RCP Draft Proposal Released
- Horizen Labs and Dan Spuller Join as EIP-RCP Co-Authors
