Operate and develop @Oraclizer / @horizenglobal 프라이버시를 지향하는 @Base 의 앱체인 입니다. 한국공식커뮤니티 : https://xitter.cf/t.co/q6RxLXIl2U
대한민국
Joined January 2018
- Tweets1.8K
- Following173
- Followers2.2K
- Likes2.2K
Pinned Tweet
Horizen, Oraclizer, zkVerify 한국 통합 커뮤니티를 공개모드로 전환합니다.
t.me/horizenkorea
Horizen Korea retweeted
👀
On compliance: no existing token standard specifies regulatory enforcement (freeze/seize/confiscate, multi-authority, terminal states). So we wrote one — ERC-8319, co-authored with @DanSpuller and @robviglione , now in the Ethereum standards process: github.com/ethereum/ERCs/pul…
Horizen Korea retweeted
Some names in tokenized RWAs are skipping public blockchains in favor of their own private trading networks.
Public transparency is a liability for institutional strategy, but are siloed networks trading the benefits of interoperability for privacy?
Horizen delivers private-execution outcomes without asking anyone to leave blockchain behind. EVM-native, compliance-forward, still onchain.
Horizen Korea retweeted
👀
Thanks! We highly appreciate the contributions.
OPH requires specialist knowledge across many disciplines. The simulator hardware and consensus protocol layers are entirely foreign to Physicists while most CS people struggle with the Physics aspects.
I'm not even starting to talk about applied Physics, engineering, neuroscience, biology, philosophy etc. as we're still working on the fundamentals.
Horizen Korea retweeted
Thanks! We highly appreciate the contributions.
OPH requires specialist knowledge across many disciplines. The simulator hardware and consensus protocol layers are entirely foreign to Physicists while most CS people struggle with the Physics aspects.
I'm not even starting to talk about applied Physics, engineering, neuroscience, biology, philosophy etc. as we're still working on the fundamentals.
Honored to join @muellerberndt on three OPH papers. It was genuinely fun.
The path was hard and complex. Using Oraclizer’s preserve/reflect discipline, I pulled a general layer from one auction fixture and kept pushing until Lean separated four different ways protected behavior can fail.
Bernhard’s willingness to let outside work meet OPH on its own terms stayed with me. I’m grateful for that trust.
The next question feels clear: can the repair process supply the assumptions the proofs need, and what remains impossible under any scheduler? I think that is the path.
github.com/FloatingPragma/ob…
Horizen Korea retweeted
[Oraclizer Joins @muellerberndt as Co-Author on Three OPH Research Papers]
Oraclizer Labs CPTO @jay_oraclizer has been officially listed as a co-author, representing Oraclizer Labs, on three research papers within Bernhard Müller’s Observer Patch Holography (OPH) program.
The contribution is technical and directly implemented in Lean 4.
Oraclizer’s existing Formal Verification work has primarily used Isabelle/HOL, while OPH is developed in Lean 4. The proofs were therefore not transferred from an existing environment. The relevant definitions and theorems were reconstructed for the OPH codebase and proved again within its own verification framework.
Oraclizer’s contribution focused on formally separating the failure conditions of state repair.
The work distinguishes between cases where a valid state does not exist, where it exists but cannot be reached, where it is reachable but convergence is not guaranteed, and where convergence occurs without a unique final state.
These cases were formalized and checked in Lean 4, together with countermodels and a finite-model checker designed to reject invalid constructions.
This maps directly to Oraclizer’s core work in State Synchronization.
When multiple systems process the same event, receiving the same instruction does not guarantee that they end in the same state. An instruction may fail to reach one domain, may reach all domains without convergence, or may complete while still producing different terminal states.
That distinction matters once blockchains, oracle networks, AI agents, databases, custodians, and institutional ledgers begin acting on the same underlying asset or event.
Oraclizer treats these cases as separate formal failure modes rather than collapsing them into a generic synchronization error. The objective is to identify exactly which condition failed and under what conditions the system can return to a consistent state.
This methodology has now been implemented outside Oraclizer’s own Isabelle/HOL environment, inside Müller’s OPH research stack and Lean 4 codebase, and published through joint authorship.
The three papers are:
Finite Observer Consensus as a Reconstruction Principle
Observation-Determined Normal Forms: Stability, Obstructions, and Refinement in Constraint and Rewrite Systems
Reality as a Consensus Protocol: The Fixed-Point Computation That Implements Physics
Bernhard Müller is the creator of Mythril, a former lead and author of the OWASP Mobile Application Security Testing Guide, and currently AI Research Lead at Sherlock.
Oraclizer and Müller are now working at the level of shared proofs, shared code, and shared authorship.
The subject of these papers is not a specific RWA product or a single blockchain implementation. The work concerns the broader formal structure behind State Synchronization and verifiable convergence across independent state domains.
Oraclizer’s model is no longer confined to its own prover or internal research environment.
It is being rebuilt, checked, and published inside a separate formal research program with one of the most recognized researchers in Ethereum security and formal methods.
research.oraclizer.io/observ…
Horizen Korea retweeted
👀
I contributed a domain-neutral kernel (Lean) and Harberger-auction model to @muellerberndt’s OPH.
The hard part was keeping two policy readings apart, observation separate from strategy, and fixture assumptions replaceable.
Bernhard committed the docstrings and merged the PR. He called it an independent second instance for OPH’s substrate-neutrality claim.
Oraclizer has the adapter problem. S3 (Atomic state binding) binds domains atomically; OPH applies machinery to another domain. I trust cross-domain claims only when their adapters are public and replaceable. It was good work to have done.
github.com/FloatingPragma/ob…
👀
[Oraclizer Official Website Relaunch]
The Oraclizer official website has been fully redesigned.
The new website presents Oraclizer’s technology, research, standards work, and practical applications as one connected system.
At the center is the Oracle State Machine and state synchronization architecture, explaining how asset states and regulatory states can be maintained consistently across multiple domains in financial and RWA environments.
The website also explains the distinct roles of ERC-8319 and ERC-TRUST, how Formal Verification is used to examine regulatory actions and state-transition rules, and how each area of research connects to the wider Oraclizer architecture.
Oraclizer is not limited to delivering price data.
It is building an architecture designed to preserve and verify critical asset states—including ownership, restrictions, freezes, and seizures—as assets move across different chains and systems without those states being lost or interpreted inconsistently.
The website now organizes Oraclizer’s architecture, core technologies, use cases, standards work, and published research into dedicated sections.
Public technical resources, including Oraclizer Research, developer documentation, GitHub repositories, Ethereum Research publications, and the ERC-8319 public discussion, can also be accessed directly from the website.
Visit the new website to explore the problems Oraclizer is addressing and how its technologies, standards, and research fit together within a single system.
oraclizer.io/
Horizen Korea retweeted
$ZEN staking rewards are now live on Horizen! ✨
The rewards pool is active and flowing to stakers.
If you staked ahead of today, you are already earning. If not, you can stake and join anytime.
Stake Now → staking.horizen.io/
Horizen Korea retweeted
Everyone is looking for the standard that makes compliant tokenized assets work.
Most already know its name.
ERC-8319, by @jay_oraclizer of Oraclizer, @DanSpuller and @robviglione.
ethereum-magicians.org/t/erc…
Horizen Korea retweeted
The recent wave of DeFi incidents can no longer be viewed simply as smart contract bugs. The attack surface is moving beyond the code itself and toward the state that the code reads, trusts, and turns into final outcomes.
In the Ostium incident, price-reporting infrastructure was reportedly abused through future-dated oracle data, resulting in artificial trading profit and roughly $18M in payouts. In the Balance / 42DAO incident, a manipulated BTC price oracle triggered improper liquidations, causing around $910K in losses and sending BLC into a near-total collapse. In the Summer.fi incident, the issue was not a pure OEV case, but the manipulation of vault share-price / accounting state, which led to millions of dollars in depositor value being extracted in a single atomic transaction.
Different incidents. Same structural warning.
When the wrong price state enters the system, the wrong liquidation can be executed. When accounting state is manipulated, the wrong payout can be finalized. When an oracle update becomes visible before its consequence is committed, that short gap becomes an opportunity for extraction.
DeFi has been trying to patch this problem from the outside. More oracle feeds, more keepers, more monitoring, more circuit breakers, more auctions, and more recapture mechanisms. But as long as the value is seen first and the liquidation, payout, or settlement result is confirmed later, the attack surface remains.
This is exactly the problem Oraclizer was built to solve.
Oraclizer does not treat the oracle as just another price feed. Oraclizer defines the problem as a state synchronization problem. The question is not only what value was delivered. The real question is what consequence that value is committed with.
“Update visible, consequence uncommitted.”
That is the condition OEV, oracle-based extraction, and liquidation timing attacks depend on. Oraclizer’s synchronization model is designed so that this state does not arise inside a bound transition.
In plain terms, Oraclizer does not try to make the race more efficient. It does not auction the race. It does not simply redistribute the value created by the race.
It removes the short gap that makes the race possible.
Recent DeFi incidents show exactly why this matters. The next phase of DeFi security will not be solved only by auditing contracts or replacing price feeds. It must address when state becomes visible, when it becomes final, and whether it is committed together with the liquidation, payout, settlement, or enforcement action that depends on it.
The market is still trying to manage the race.
Oraclizer removes the gap that creates it.
OEV was one of blockchain’s hardest unsolved structural problems.
Not because no one could price it.
Because pricing the race still leaves the race alive.
Oraclizer changes the state machine.
Inside the bound transition, the OEV window is not captured.
It is unreachable.
ethresear.ch/t/structural-oe…
Horizen Korea retweeted
OEV was one of blockchain’s hardest unsolved structural problems.
Not because no one could price it.
Because pricing the race still leaves the race alive.
Oraclizer changes the state machine.
Inside the bound transition, the OEV window is not captured.
It is unreachable.
ethresear.ch/t/structural-oe…
Horizen Korea retweeted
👀
OEV is a hard blockchain problem. Most solutions price the race. We remove its enabling state.
Commit an oracle update and a bound action as one atomic transition. Its OEV window is absent by construction.
Atomicity machine-checked at model level.
ethresear.ch/t/structural-oe…
Horizen Korea retweeted
Pragma Research found H¹=45 in LayerZero V2: 45 independent failure modes. It makes the problem behind @Oraclizer's Cross-Domain State Preservation Functor concrete. @muellerberndt's team maps failures; we formalize how a transition's meaning and effect persist across domains.
Horizen Korea retweeted
5/5
Why it matters now: a shared vocabulary only coordinates when it has a permanent, citable home, kept under the same process and license as the standards that cite it. The number ERC-8319 is now that identifier.
Built with @robviglione and the @HorizenLabs team, and @DanSpuller, EVP of Industry Affairs at the @BlockchainAssn, bringing the policy and due-process perspective.
Full walkthrough: research.oraclizer.io/erc-83…
The proposal (ERC-8319): github.com/jay-oraclizer/ERC…
Horizen Korea retweeted
We've submitted the Regulatory Compliance Protocol (RCP) to Ethereum as ERC-8319, now under editor review.
RCP gives regulatory enforcement on tokenized assets one shared, citable definition: what a freeze, a seizure, or a confiscation actually means on-chain, whether it can be undone, and what happens to ownership.
A reference we'd prepared over a long stretch of research now sits in the same repository as standards like ERC-20 and ERC-721, under a permanent, citable number.
The full proposal and the discussion are open on Ethereum Magicians. We'd welcome your review and feedback there.
ethereum-magicians.org/t/erc…