Skip links
Safety and Liveness of Cross-Domain State Preservation: Now on arXiv
Oraclizer's combined Property 1+2 formal verification paper is now on arXiv. The Isabelle/HOL proof unifies cross-domain state preservation (safety) with BFT consensus liveness under Byzantine faults (f<n/3) into a single unified result, published with full source code, a 46-page proof PDF, and seven reusable domain-independent locales.
Oraclizer Core ⋅ Apr 07, 2026
Safety and Liveness of Cross-Domain State Preservation: Now on arXiv
Oraclizer's combined Property 1+2 formal verification paper is now on arXiv. The Isabelle/HOL proof unifies cross-domain state preservation (safety) with BFT consensus liveness under Byzantine faults (f<n/3) into a single unified result, published with full source code, a 46-page proof PDF, and seven reusable domain-independent locales.
Oraclizer Core ⋅ Apr 07, 2026
Sync Degree Hierarchy: Classifying What Assets Demand from State Synchronization
Sync degree hierarchy turns sync requirement strength into a four-level classification axis for RWA assets. S₀ static through S₃ atomic state binding form a reduction relation where causal consistency separates S₁ from S₂. Existing oracles, structurally two independent channels, are capped at S₁ by definition. Regulatory action forces S₃.
Oraclizer Core ⋅ May 20, 2026
Sync Degree Hierarchy: Classifying What Assets Demand from State Synchronization
Sync degree hierarchy turns sync requirement strength into a four-level classification axis for RWA assets. S₀ static through S₃ atomic state binding form a reduction relation where causal consistency separates S₁ from S₂. Existing oracles, structurally two independent channels, are capped at S₁ by definition. Regulatory action forces S₃.
Oraclizer Core ⋅ May 20, 2026
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 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
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
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

RWA

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
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

EIP

EIP-RCP: Why Tokenized Capital Markets Need a Regulatory
The EIP-RCP Informational EIP draft is now complete. This protocol provides a common vocabulary and framework for regulatory compliance interoperability in tokenized capital markets. This article explains the motivation, rationale, and significance of the proposal for the Ethereum ecosystem.
Oraclizer Core ⋅ Dec 20, 2025
EIP-RCP: Why Tokenized Capital Markets Need a Regulatory
The EIP-RCP Informational EIP draft is now complete. This protocol provides a common vocabulary and framework for regulatory compliance interoperability in tokenized capital markets. This article explains the motivation, rationale, and significance of the proposal for the Ethereum ecosystem.
Oraclizer Core ⋅ Dec 20, 2025