Skip links

We Joined Observer Patch Holography: Proving Outside Our Own Stack

Oraclizer Update

Jay Kim, CPTO of Oraclizer (publishing under his legal name Jinwook Kim), has been listed as a co-author on three papers from the Observer Patch Holography (OPH) research program, under the affiliation Oraclizer Labs. The work behind the listing is formal verification carried out in the program’s own theorem prover. All three papers are publicly available.

Where Observer Patch Holography Meets a Problem We Already Had

Observer Patch Holography is an open research program built on a single premise: observers are primary, and objective reality is emergent. Rather than assuming spacetime and fields, it begins with finite systems that hold local state, read only part of what their neighbors hold, and repair the disagreements between them, then asks how much physical structure can be reconstructed from there. The program is led by Bernhard Mueller, who wrote Mythril, the symbolic-execution security analyzer for EVM bytecode, authored and formerly led the OWASP Mobile Application Security Testing Guide, and now serves as AI Research Lead at the smart contract auditing platform Sherlock.

We joined because the central question is shaped like ours. Observer Patch Holography asks whether the disagreements among participants who each observe only a fragment can be repaired into one shared state. Oraclizer asks whether two domains that move independently, on-chain and off-chain, can be held to a single consistent state. The domain differs, a physical model on one side and a regulated asset on the other, but the question is the same: how far can a divergent state be brought back, and what stands in the way. Our Cross-Domain State Preservation Functor, proved in Isabelle/HOL, answered a question from that same family.

Separating the Four Ways Repair Fails

The Observer Patch Holography repository runs on Lean 4. Our own formal verification is written in Isabelle/HOL, so this work meant designing and proving the theorems in Lean from scratch rather than porting existing proofs across.

What we proved is a separation of the four ways repair fails. When a state must be preserved, there is more than one reason it may not be reached. The state may not exist at all; it may exist but stay unreachable from any starting point; it may be reachable without being reached with certainty; or it may be reached while the endpoint remains ambiguous. Under machine checking we closed that these four layers are mutually disjoint and jointly exhaustive, that each layer is inhabited by a concrete case and a countermodel, and that the separation survives transport to another model. Alongside the proofs we contributed a deterministic checker that enumerates finite models exhaustively, so a deliberately broken variant does not pass.

The same distinction carries over to Oraclizer. A regulatory freeze that reaches one domain but not the other, and a freeze that reaches both while the final states diverge, have different causes and call for different responses.

What Carries Back to Our Own Work

The collaboration settled something we could not have settled alone. The verification discipline we built for regulated assets transfers. The same way of asking a question, what must hold, under which assumptions, and what would break it, produced a usable result in a domain with no tokens and no ledgers in it. An internal review cannot establish that. A maintainer applying their own standards on their own repository can.

So the standard carries in both directions. What held up in someone else’s repository is the standard we hold our own system to, and every result Oraclizer stands behind stays where anyone can rebuild it. Our formal verification is public at github.com/Oraclizer/formal-verification, and the Observer Patch Holography repository, where these papers and the Lean sources both live, is at github.com/FloatingPragma/observer-patch-holography.

Read Next

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.
Jay Kim ⋅ Aug 11, 2026
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.
Jay Kim ⋅ Jul 31, 2026
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.
Jay Kim ⋅ Jul 25, 2026
Designing the ERC-TRUST Enforceability Architecture
A regulator's freeze and a court's confiscation are legally opposite, yet on today's token standards they compile to the same call. This ERC-7943 conformance extension makes each of the six regulatory actions a typed, distinct object whose legal effect is verifiable on-chain, and carries that meaning from the abstract model down to deployed bytecode as evidence.
Jay Kim ⋅ Jul 23, 2026
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.
Jay Kim ⋅ Jul 21, 2026