Oraclizer @Oraclizer

Another bridge hack. Another reminder that this industry still asks users to trust systems that cannot prove their own correctness. Finance runs on guarantees. Not vibes. Not audits alone. Not marketing language. And guarantees come from proof you can check, not promises you take on faith. That is why Oraclizer is built on formal verification. Our core cross-domain state preservation is mathematically proven and machine-checked in Isabelle/HOL, with no proof gaps, and the proofs are public. Anyone can verify them, not take our word for it. We are extending that same standard across the protocol, in the open. So for every system asking for your capital, the question stays simple: What exactly are you trusting?

Oraclizer @Oraclizer

2 months ago

Property 1 complete. Property 2 complete. Next: Property 3. Our Isabelle/HOL formal verification of safety and Byzantine-tolerant liveness is now public on arXiv. The next milestone is end-to-end formal assurance. @CantonFdn @DanSpuller @digitalasset @HorizenLabs @YuvalRooz

1 6 9 604 0

Moving fast — but taking the necessary moments to look back, verify, decide, and close every detail properly. Some milestones deserve speed. Others deserve precision. Next week is one of them.

Big day for @BlockchainAssn and our members. National security, intelligence, and law enforcement professionals are joining us on Capitol Hill today to urge the Senate to pass the CLARITY Act. Regulatory clarity is a national security priority!

keyboard_arrow_left Previous keyboard_arrow_right Next

Oraclizer’s research on atomic cross-domain state synchronization is now live on Ethereum Research. This work provides mechanized Isabelle/HOL proofs for the state synchronization layer underlying our earlier RCP framework and EIP-RCP direction. ethresear.ch/t/mechanized-p…

June ☄️

Finally

Property 1 proved safety. Property 2 proved liveness under Byzantine faults. Now comes Property 3: compositional verification. The next milestone is combining both into end-to-end convergence and full system assurance. Formal verification is moving from isolated proofs to complete guarantees. research.oraclizer.io/prelude-to-com…

The only

Under the standard Byzantine threshold f < n/3, Oraclizer’s Isabelle/HOL proofs now establish determinism, deadlock freedom, and starvation freedom — with no "sorry", no "oops". More importantly, Property 2 discharges the honest-node assumption carried by Property 1, lifting conditional safety into an unconditional safety + liveness guarantee. research.oraclizer.io/byzantine-faul…

Property 1 complete. Property 2 complete. Next: Property 3. Our Isabelle/HOL formal verification of safety and Byzantine-tolerant liveness is now public on arXiv. The next milestone is end-to-end formal assurance. @CantonFdn @DanSpuller @digitalasset @HorizenLabs @YuvalRooz @ShaulKfir @VitalikButerin research.oraclizer.io/formal-verific…

Proving D-quencer Liveness under Byzantine Faults: The Journey All 5 remaining “sorry” in Property 2’s Isabelle/HOL liveness proof have now been eliminated in Priority_Resolution.thy. The process also exposed and fixed 3 latent bugs, reinforcing a key lesson of formal verification: the hardest part is not always the math itself, but often the proof tooling, library details, and proof structure. combined_safety_liveness and the full 4-file build are still ahead. research.oraclizer.io/isabelle-hol-l…

A Regulatory Compliance Protocol for Asset Interoperability Between Traditional and Decentralized Finance in Tokenized Capital Markets arxiv.org/abs/2603.29278

We did it. Oraclizer's state synchronization theory has been formally proven and submitted to the Archive of Formal Proofs (AFP), the world's most prestigious archive of machine-checked mathematical proofs, maintained by TU München and University of Cambridge. State synchronization is a first-of-its-kind concept in blockchain. With this proof, the theory is now mathematically guaranteed to work. This means our core claim is no longer a promise. It is a mathematical fact: when a regulatory action happens on one chain, every connected chain is guaranteed to reflect the exact same state. Not in most cases. Not in tested cases. In every possible case. Verified by the Isabelle/HOL proof kernel, a machine that cannot be lobbied, bribed, or mistaken. No other oracle project has done this. No cross-chain infrastructure has this level of assurance. We didn't just build it. We proved it. The proof is universal. Any team building cross-chain infrastructure can import our framework and verify their own system against the same standard. We didn't just prove our protocol. We created the standard. Proof files will be open-sourced on GitHub. Anyone can re-verify everything.

Oraclizer @Oraclizer

3 months ago

Oraclizer’s official GitHub repository is now live: github.com/Oraclizer/form… FV Property 1 has been pushed — a formal proof of cross-domain state preservation (homomorphism). This milestone mathematically guarantees the core thesis of state synchronization across domains. –

0 7 9 2K 0

Oraclizer’s official GitHub repository is now live: github.com/Oraclizer/form… FV Property 1 has been pushed — a formal proof of cross-domain state preservation (homomorphism). This milestone mathematically guarantees the core thesis of state synchronization across domains. – Detailed review & interpretation: research.oraclizer.io/cross-domain-s… – Announcement of the successful proof: research.oraclizer.io/state-preserva…

Oraclizer has published a 3-part research series on FV1: Cross-Domain State Preservation. We define what it means, formalize it, and prove it. From concept → formal model → verification. This is not just theory — it’s the foundation for verifiable state synchronization. 1/ research.oraclizer.io/defining-cross… 2/ research.oraclizer.io/formalizing-cr… 3/ research.oraclizer.io/proving-cross-… 1/ What are we proving? A state transition on one domain must be preserved identically across all linked domains. 2/ How do we formalize it? We define regulatory states, actions, and a cross-domain preservation functor. 3/ What did we achieve? Core property verification of cross-domain state preservation (FV1). State Oracle is no longer a narrative — it's becoming provable. @CantonFdn @Damldriven @DanSpuller @HorizenLabs @digitalasset @ShaulKfir @YuvalRooz @HorizenLabs @robviglione @ethereum @VitalikButerin

At the end of the day, there’s no alternative but us. 🤐

Whatever you imagine, we will become even more than that. 😉