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…

🇰🇷 AI Meets the Chart is coming to Seoul for #KBW! On September 28, @GaeaVentures × @K1_Research bring together AI builders, quant researchers, traders, and Web3 innovators to explore how AI is reshaping real-world trading. As AI agents begin to analyze markets, execute strategies, and place orders autonomously, one question becomes increasingly important: When automation becomes accessible to everyone, where does the real trading edge come from? Join us for an evening exploring AI Quant Trading, Agentic Trading, automated execution, and the evolving role of human judgment in the market. 🎙 Keynotes & Roundtable 🤝 Networking Party 🎁 Gift Card Giveaways 🥇 Gold Bar Lucky Draw 📅 Sep 28｜17:00–21:00 📍 ALVER, Seoul Co-Hosts @D_Network_Ai @UniKey_EN @OriginsNetwork_ @Travix_fi Special thanks to our sponsors @Oraclizer @flapdotsh @ZestProtocol @AiTok_io @skydaogroup @XPINNetwork @BeckerVentures @KeyFlow_EN 🔗 Register now: luma.com/5mgf0u76 See you in Seoul.

🇰🇷 Becker Ventures is proud to support AI Meets the Chart during #KBW! On September 28, AI builders, quant researchers, traders, and Web3 innovators will come together in Seoul to explore how AI is reshaping the future of trading. From AI Quant Trading and Agentic Trading to automated execution and human decision-making, the event will dive into where the next real edge in the market may come from. 🎙 Keynotes & Roundtable 🤝 Networking Party 🎁 Gift Card Giveaways 🥇 Gold Bar Lucky Draw 📅 Sep 28｜17:00–21:00 📍 ALVER, Seoul Hosted by @GaeaVentures × @K1_Research Co-Hosts @D_Network_Ai @UniKey_EN @OriginsNetwork_ @Travix_fi Proud to join fellow sponsors: @Oraclizer @flapdotsh @ZestProtocol @AiTok_io @skydaogroup @XPINNetwork @KeyFlow_EN 🔗 Register now: luma.com/5mgf0u76 See you in Seoul! 🇰🇷 #KBW #AI #Web3 #AIAgent

[Oraclizer August Achievements] Starting this August, we are sharing a monthly summary of Oraclizer’s key achievements. This month, our work on regulatory standardization and formal verification around ERC-8319 became more concrete. We structured the meanings of six regulatory actions and organized 31 requirements from 15 regulatory authorities into a unified framework. We also formalized the normative rules of ERC-TRUST into executable semantics, further connecting regulatory meaning to the system level. On August 18, we announced that Oraclizer CPTO Jay Kim had been listed as a co-author on three public manuscripts from the Observer Patch Holography (OPH) research program. On August 29, “Mechanizing Typed Regulatory Actions for Security Tokens” was published on arXiv. Since then, the research has been indexed on PhilPapers, and Jinwook Kim has also been listed as a co-author on a Pragma Research core paper. Public discussion around ERC-8319 is also continuing on Ethereum Magicians. This month marked a clearer progression from regulatory meaning → formal verification → executable semantics → external research visibility State should move as one.

👀

👀

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.

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

👀

Bubbles reward narratives. Their collapse exposes who built something real—and who built nothing at all.

What DAML/Canton has that Solidity/EVM structurally doesn't? 1. Privacy as a language primitive 2. Authorization as a type, not a runtime check 3. Granular three-tier permissions, not just onlyOwner 4. Multi-party authorization required to create a contract 5. UTXO-style immutability, so reentrancy doesn't exist 6. Cross-domain atomic transactions with preserved privacy 7. signatory != msg.sender

Stop slapping “RWA” and “tokenization” onto products you barely understand. If you cannot explain what is being tokenized, who holds the enforceable rights, how ownership changes, and what happens in a freeze, seizure, default, redemption, or dispute, you are not building RWA infrastructure. You are borrowing institutional language for marketing. Soon. 😏

[The Order of Regulatory Actions Changes the Outcome] Oraclizer has published a new Formal Verification study. Tokenized assets may be subject to regulatory actions such as FREEZE, SEIZE, CONFISCATE, and RESTRICT. When multiple actions are issued for the same asset, the order in which they are processed can change both the asset’s final state and whether a specific action is successfully applied. Consider an asset that is already in the RESTRICTED state. If FREEZE is processed before SEIZE, both actions are applied and the asset ultimately reaches the SEIZED state. If SEIZE is processed first, it is rejected because the transition is not permitted from the current state. FREEZE is then applied, leaving the asset in the FROZEN state. Oraclizer analyzed all 21 distinct pairs that can be formed from seven regulatory state-transition actions. Twelve pairs produced the same result regardless of order, while nine produced different results depending on execution order. For each of the nine order-sensitive pairs, a starting state demonstrating the difference was formally proven in Isabelle/HOL. Longer sequences of regulatory actions were also examined. Although the number of possible command sequences is infinite, their effects on asset states reduce to exactly 60 distinct forms. The verification proves that every sequence resolves to one of these 60 forms, that each form is distinct, and that every form can be produced by an actual sequence of actions. Execution outcomes are classified as Applied, Rejected, or Operational Failure. This separates actions that successfully change the state, actions that are not permitted from the current state, and actions that cannot be completed because of system-level failures. Repeated actions do not incorrectly alter the asset state, while each action remains recorded as a separate audit event. ERC-8319 defines the meaning of regulatory actions. This research verifies how those actions must be processed within an actual state machine, including their ordering and outcomes. It establishes the regulatory action-processing rules that ERC-TRUST is intended to follow through Formal Verification. Research research.oraclizer.io/regula… Formal Verification github.com/Oraclizer/formal-…

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

🫣

Knowledge determines what you’re capable of seeing. 👀

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…

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…

👀