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

When Regulatory Actions Do Not Commute: Order, Outcome, and Sixty Normal Forms

When Regulatory Actions Do Not Commute: Order, Outcome, and Sixty Normal Forms

Enforcement standards define what a freeze or a confiscation does, and say nothing about what happens when two commands overlap. Regulatory action composition closes that gap in Isabelle/HOL: twenty-one action pairs split into twelve commuting and nine not, each non-commuting pair with a witness, and exactly sixty state transformations behind unbounded sequences.
Oraclizer Core ⋅ Jul 31, 2026
When Regulatory Actions Do Not Commute: Order, Outcome, and Sixty Normal Forms

When Regulatory Actions Do Not Commute: Order, Outcome, and Sixty Normal Forms

Enforcement standards define what a freeze or a confiscation does, and say nothing about what happens when two commands overlap. Regulatory action composition closes that gap in Isabelle/HOL: twenty-one action pairs split into twelve commuting and nine not, each non-commuting pair with a witness, and exactly sixty state transformations behind unbounded sequences.
Oraclizer Core ⋅ Jul 31, 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

Defining the Sync Unit: Oracle Usage Metering for State Synchronization

Defining the Sync Unit: Oracle Usage Metering for State Synchronization

The State Subscription economy has quoted ten Sync Units for a dollar without ever fixing what one Sync Unit counts, leaving three conflicting conversion rates inside one body of work. This study anchors the unit to a single committed state binding and derives its weight from the sync degree hierarchy. Applying it inverts the existing frequency bands.
Oraclizer Core ⋅ Jul 25, 2026
Defining the Sync Unit: Oracle Usage Metering for State Synchronization

Defining the Sync Unit: Oracle Usage Metering for State Synchronization

The State Subscription economy has quoted ten Sync Units for a dollar without ever fixing what one Sync Unit counts, leaving three conflicting conversion rates inside one body of work. This study anchors the unit to a single committed state binding and derives its weight from the sync degree hierarchy. Applying it inverts the existing frequency bands.
Oraclizer Core ⋅ Jul 25, 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

Formalizing ERC-TRUST from Normative Rules to Executable Semantics

Formalizing ERC-TRUST from Normative Rules to Executable Semantics

Discharging a proof obligation does not mean it constrains anything. If no reachable state satisfies its premise, the obligation passes vacuously and the checker stays silent. This is how ERC-TRUST lowered its normative sentences into machine-checkable state transitions, built an execution for every rule, and drew the line at legal fact.
Oraclizer Core ⋅ Aug 11, 2026
Formalizing ERC-TRUST from Normative Rules to Executable Semantics

Formalizing ERC-TRUST from Normative Rules to Executable Semantics

Discharging a proof obligation does not mean it constrains anything. If no reachable state satisfies its premise, the obligation passes vacuously and the checker stays silent. This is how ERC-TRUST lowered its normative sentences into machine-checkable state transitions, built an execution for every rule, and drew the line at legal fact.
Oraclizer Core ⋅ Aug 11, 2026

Show more →