Skip links

Type and hit enter

Subscribe
Oraclizer Research

UPDATES

Our State Synchronization Research Is Now on Ethereum’s Research Forum

Our State Synchronization Research Is Now on Ethereum’s Research Forum

Two Oraclizer research posts now stand on ethresear.ch, Ethereum's research forum: machine-checked proofs that atomic cross-domain synchronization behaves correctly, and a follow-up giving synchronization strength a formal, checkable basis. In between, a public exchange with an Ethereum researcher sharpened the work into what it is now.
Oraclizer Core ⋅ Jul 21, 2026
Our State Synchronization Research Is Now on Ethereum’s Research Forum

Our State Synchronization Research Is Now on Ethereum’s Research Forum

Two Oraclizer research posts now stand on ethresear.ch, Ethereum's research forum: machine-checked proofs that atomic cross-domain synchronization behaves correctly, and a follow-up giving synchronization strength a formal, checkable basis. In between, a public exchange with an Ethereum researcher sharpened the work into what it is now.
Oraclizer Core ⋅ Jul 21, 2026

Show more →

CORE

Sync Degree Enforcement: What Turns a Classification Into a Constraint

Sync Degree Enforcement: What Turns a Classification Into a Constraint

A classification does nothing on its own. Sync degree enforcement closes the gap between labeling an asset S2 and having the system refuse to touch it any other way. It rests on a two-directional result: over-provisioning preserves every guarantee, under-provisioning admits a state that defeats all of them. So the check leaves runtime and enters Rust's type system.
Oraclizer Core ⋅ Jul 16, 2026
Sync Degree Enforcement: What Turns a Classification Into a Constraint

Sync Degree Enforcement: What Turns a Classification Into a Constraint

A classification does nothing on its own. Sync degree enforcement closes the gap between labeling an asset S2 and having the system refuse to touch it any other way. It rests on a two-directional result: over-provisioning preserves every guarantee, under-provisioning admits a state that defeats all of them. So the check leaves runtime and enters Rust's type system.
Oraclizer Core ⋅ Jul 16, 2026

Show more →

PROOFS

The Cross-Domain State Preservation Functor: What It Closed, and What It Was For

The Cross-Domain State Preservation Functor: What It Closed, and What It Was For

The cross-domain state preservation proofs are closed: homomorphism, functor completion, a natural-transformation tower, and unconditional bounded convergence. Ten theory files, zero sorry. The harder work was catching what passes a prover while saying nothing: a trivial functor, a bypassed threshold, a witness outside the roster. Each retreat left the rest firmer.
Oraclizer Core ⋅ Jul 16, 2026
The Cross-Domain State Preservation Functor: What It Closed, and What It Was For

The Cross-Domain State Preservation Functor: What It Closed, and What It Was For

The cross-domain state preservation proofs are closed: homomorphism, functor completion, a natural-transformation tower, and unconditional bounded convergence. Ten theory files, zero sorry. The harder work was catching what passes a prover while saying nothing: a trivial functor, a bypassed threshold, a witness outside the roster. Each retreat left the rest firmer.
Oraclizer Core ⋅ Jul 16, 2026

Show more →

PROTOCOL

OIP v0.5 Checkpoint: Three Discoveries and the Big Map

OIP v0.5 Checkpoint: Three Discoveries and the Big Map

OIP v0.5 closes the specification integration review: cumulative protocol decisions are placed on one table and checked for coherence across five design areas. Three discoveries emerge: a missing header slot for threshold signatures, redrawing validation as criteria rather than axes, and recognizing BVC and 3-Phase as nested layers.
Oraclizer Core ⋅ Apr 26, 2026
OIP v0.5 Checkpoint: Three Discoveries and the Big Map

OIP v0.5 Checkpoint: Three Discoveries and the Big Map

OIP v0.5 closes the specification integration review: cumulative protocol decisions are placed on one table and checked for coherence across five design areas. Three discoveries emerge: a missing header slot for threshold signatures, redrawing validation as criteria rather than axes, and recognizing BVC and 3-Phase as nested layers.
Oraclizer Core ⋅ Apr 26, 2026

Show more →

ECONOMY

Insurance and Recovery Economics: Preparing for Black Swan Events

Insurance and Recovery Economics: Preparing for Black Swan Events

Earlier designs cut node risk by 73%, but the unpredictable 27% needs different rules. This study fixes how a staking insurance pool is sized (15% of stake, not protected value), bootstrapped, and banded; why a reserve held in its own token collapses with it; and how session protection follows the sync-degree hierarchy when security breaks mid-session.
Oraclizer Core ⋅ May 29, 2026
Insurance and Recovery Economics: Preparing for Black Swan Events

Insurance and Recovery Economics: Preparing for Black Swan Events

Earlier designs cut node risk by 73%, but the unpredictable 27% needs different rules. This study fixes how a staking insurance pool is sized (15% of stake, not protected value), bootstrapped, and banded; why a reserve held in its own token collapses with it; and how session protection follows the sync-degree hierarchy when security breaks mid-session.
Oraclizer Core ⋅ May 29, 2026

Show more →

RWA

Tokenized Securities Under the CLARITY Act: The Weight of Codification

Tokenized Securities Under the CLARITY Act: The Weight of Codification

The CLARITY Act tokenized securities clause settles a single proposition in statute: tokenization is a delivery method, not a new asset class. That one sentence codifies the regulatory status of tokenized securities in U.S. law for the first time and derives an entire infrastructure specification for boundaries the token crosses.
Oraclizer Core ⋅ May 23, 2026
Tokenized Securities Under the CLARITY Act: The Weight of Codification

Tokenized Securities Under the CLARITY Act: The Weight of Codification

The CLARITY Act tokenized securities clause settles a single proposition in statute: tokenization is a delivery method, not a new asset class. That one sentence codifies the regulatory status of tokenized securities in U.S. law for the first time and derives an entire infrastructure specification for boundaries the token crosses.
Oraclizer Core ⋅ May 23, 2026

Show more →

EIP

ERC-8319: A Citable Regulatory Constitution for Tokenized Assets

ERC-8319: A Citable Regulatory Constitution for Tokenized Assets

The ERC-8319 Regulatory Compliance Protocol has entered Ethereum's standards repository. It defines the legal effect of six enforcement actions on tokenized assets, from a reversible freeze to an irreversible confiscation, and compiles 31 requirements from 15 regulators under five principles. A convention, not an interface, under one permanent, citable identifier.
Oraclizer Core ⋅ Jul 14, 2026
ERC-8319: A Citable Regulatory Constitution for Tokenized Assets

ERC-8319: A Citable Regulatory Constitution for Tokenized Assets

The ERC-8319 Regulatory Compliance Protocol has entered Ethereum's standards repository. It defines the legal effect of six enforcement actions on tokenized assets, from a reversible freeze to an irreversible confiscation, and compiles 31 requirements from 15 regulators under five principles. A convention, not an interface, under one permanent, citable identifier.
Oraclizer Core ⋅ Jul 14, 2026

Show more →