Operate and develop @Oraclizer / @horizenglobal 프라이버시를 지향하는 @Base 의 앱체인 입니다. 한국공식커뮤니티 : https://teapaw.org/t.co/q6RxLXIl2U
대한민국
Joined January 2018
- Tweets1.8K
- Following173
- Followers2.2K
- Likes2.2K
Pinned Tweet
Horizen, Oraclizer, zkVerify 한국 통합 커뮤니티를 공개모드로 전환합니다.
t.me/horizenkorea
👀
RWA issuance gets the headlines. Regulatory enforcement is the real challenge.
15 financial authorities. 31 compliance requirements.
Oraclizer proposed ERC-8319 with @DanSpuller and @robviglione and went further with ERC-TRUST.
Not just another RWA narrative. Actual research and implementation.
youtu.be/3eYexG0jn7U
Horizen Korea retweeted
We didn't just optimize StateSync-GKR. We built our own proving engine.
Less memory. Faster verification. Mathematically verified.
Built from first principles. Proven by mathematics.
While building StateSync-GKR at @Oraclizer, three questions kept coming back.
How far can we take it?
Is there a better way?
Why not prove the prover itself?
So we built our own engine and took it all the way. Less memory, more speed, machine-checked.
There's a new version of this post
Horizen Korea retweeted
📣 Horizen update 📣
TLDR: Horizen is changing. The Horizen L3 is winding down over the next two weeks.
Users should bridge their assets to Base at their soonest possible convenience, including unstaking and withdrawing any funds from ZEN staking on the Horizen chain. A new ZEN staking program will commence on Base soon.
Step-by-step migration guide: blog.horizen.io/changes-for-…
While L3 wind-down has quietly been in preliminary planning phases as part of ongoing roadmap development, migration is being accelerated due to upcoming Base network upgrades that will break compatibility with existing Base L3 chains on the OP (Optimism) stack.
Why this change? As the Horizen L3 on Base has been operational on mainnet for nearly one year, the most compelling projects being built on Horizen today use privacy technologies like zero-knowledge proofs and TEEs that do not require the operation of dedicated block space as an L3 blockchain settling to Base.
With the emergence of Vela as a TEE-based confidential execution environment for private onchain finance – Base will now be utilized as the primary chain for the Horizen ecosystem.
Applications currently in development by independent teams in the Horizen ecosystem will also make this transition. Additionally, we expect the pace of project development to increase in future quarters due to reduced architectural complexities with respect to bridging and cross-chain token mechanics.
As part of this wind-down and migration, ZEN staking on the Horizen L3 will come to an orderly but immediate conclusion. Expect more information in the coming days about ZEN staking on Base.
Horizen chain wind-down and migration will occur over approximately the next two weeks as Base upgrades to its Denim release, with breaking changes to OP-stack chains settling to Base. Please migrate all funds before November 4, 13:00 UTC.
ACTION REQUIRED: Move your assets off the Horizen L3 by November 4, 13:00 UTC
The Horizen L3 is shutting down.
Bridging from the L3 to Base closes at 13:00 UTC on Tuesday, November 4. If you hold ZEN, ETH or other assets on the L3, please move them to Base before that date and time.
What happens if I miss the date to bridge to Base?
Any ZEN or ETH still on the Horizen L3 after the bridge closes will be returned to you on Base by the Horizen DAO after funds are made recoverable. This process is expected to take several weeks. Withdrawing now is the fastest path to returning your assets to Base.
WHAT TO DO
1. If you are staking ZEN: Go to staking.horizen.io. Withdraw your stake first, then claim your rewards. Staking rewards on the L3 end on October 25; there is nothing to wait for.
2. Bridge your ZEN and USDC.e to Base: stargate.finance
3. Bridge your ETH to Base: Withdraw your ETH via the native bridge at bridge.horizen.io. Start this before November 4; the transaction will be finalized for you and completed on Base in approximately two weeks.
USDC.e is operated by Stargate, not Horizen, and is not covered by the DAO return; you must bridge USDC.e out before November 4.
If you need ETH on Horizen for gas to bridge out other assets, bridge a very small amount of ETH from Base to the Horizen L3 using the native bridge at bridge.horizen.io.
L3 gas costs a fraction of a cent, so bridge the minimum the bridge allows and no more; ETH left on the L3 below 0.001 ETH after network wind-down will not be returned.
If you are using a Safe multi-sig or any other vault or smart contract wallet on the L3 and are unable to withdraw assets before Nov 4, contact [email protected] to open coordination for a return of funds.
Bridging ZEN from Base to the Horizen L3 is already disabled. ETH deposits remain open only for users to bridge ETH to Horizen for gas to withdraw other assets.
IF YOU MISS THE DEADLINE
At 13:00 UTC on November 4, a snapshot of every balance and every staking position on the L3 will be taken. The Horizen DAO will recover funds and subsequently send each holder their ZEN, including unclaimed staking rewards, to the same address on Base, after a one-week public review of the snapshot. ETH balances above 0.001 ETH are returned the same way. The anticipated timeframe for return of funds is second half of November. If your Horizen L3 wallet address is a smart contract wallet that does not similarly exist on Base, please contact us at [email protected] before Nov 4 to open coordination for a return of funds.
WHY IS THIS HAPPENING SO QUICKLY?
Earlier this week, Base scheduled its “Denim” upgrade, which moves Base to 200-millisecond blocks, for November 5. OP Stack chains that settle to Base, including the Horizen L3, cannot follow that change: about 40 minutes after activation the L3 can no longer include user transactions, permanently. We identified this, confirmed it on the Base Sepolia testnet where Denim is already live, and our infrastructure provider has confirmed there is no fix. We set the bridging cutoff one day earlier than hard shutdown so that the snapshot is clean and nothing is in flight when the chain stops.
STAKING WILL CONTINUE ON BASE
We expect to redeploy ZEN staking on Base in the coming days. The program remains funded per ZenIP-42408, so staking will resume where ZEN already lives natively, on Base. Details will follow in separate posts to come. Unstaking your ZEN from the L3 today will position you for the start of staking on Base.
WHAT COMES NEXT
Base will become the home chain for the Horizen ecosystem. ZEN already lives on Base natively, and the work ahead – including a compliant privacy pool with staked ZEN-powered nodes and Vela for confidential compute – does not require its own blockspace. A proposed three-year roadmap will be presented to the Horizen DAO Special Council and the larger community for input and governance before execution.
KEY DATES (UTC)
Completed: Bridging ZEN from Base to the Horizen L3 is disabled
Now: Users begin to bridge all assets from Horizen to Base
Nov 4, 13:00: Horizen L3 to Base bridging closes; snapshot taken
Nov 5, 18:00: Base Denim activates; the L3 stops processing transactions
Nov 7 (approximated): snapshot published for review
Nov 15 (approximated) onward: DAO distributes remaining balances on Base
HAVE QUESTIONS?
Horizen Discord: horizen.io/invite/discord
SECURITY REMINDER
Trust Only Official Sources
Website: horizen.io
Discord: horizen.io/invite/discord
Telegram Community Group: t.me/horizencommunity
X / Twitter: teapaw.org/horizenglobal
Never Trust Unsolicited Help
Get help from the official team when you need support.
Horizen team will never DM you first.
We will never ask for private keys or seed phrases.
We will never ask you to send your funds to us.
If you need help, use our official Discord ticketing system.
👀
Don't take our word for it.
Whether a regulatory order ran exactly as the rules say no longer has to rest on anyone's word. The proofs are public, with the commands to replay them.
github.com/Oraclizer/erc-tru…
Horizen Korea retweeted
Don't take our word for it.
Whether a regulatory order ran exactly as the rules say no longer has to rest on anyone's word. The proofs are public, with the commands to replay them.
github.com/Oraclizer/erc-tru…
👀
Tests cover the cases someone wrote down. A proof leaves no case where it fails 👇
Every registered execution is checked on the exact compiled bytecode, and the freeze is proven for every possible input.
Thanks to @Certora, whose prover ran part of our verification.
Horizen Korea retweeted
Tests cover the cases someone wrote down. A proof leaves no case where it fails 👇
Every registered execution is checked on the exact compiled bytecode, and the freeze is proven for every possible input.
Thanks to @Certora, whose prover ran part of our verification.
👀
ERC-TRUST 1.2 is, to our knowledge, the first security-token standard backed by machine-checked proof 🔵
The freeze is proven for every input, so the word guarantee now applies. It builds on ERC-8319, which we co-wrote with @DanSpuller.
research.oraclizer.io/erc-tr…
Horizen Korea retweeted
ERC-TRUST 1.2 is, to our knowledge, the first security-token standard backed by machine-checked proof 🔵
The freeze is proven for every input, so the word guarantee now applies. It builds on ERC-8319, which we co-wrote with @DanSpuller.
research.oraclizer.io/erc-tr…
👀
What happens when a state changes? 👇
We prove just that change, layer by layer, all the way to the new state root, on a path machine-checked in Isabelle/HOL.
Thanks to @muellerberndt for reviewing our challenge generation and sharpening our claims.
Horizen Korea retweeted
What happens when a state changes? 👇
We prove just that change, layer by layer, all the way to the new state root, on a path machine-checked in Isabelle/HOL.
Thanks to @muellerberndt for reviewing our challenge generation and sharpening our claims.
👀
Meet StateSync-GKR 🟢
Proving state changes just got a lot lighter, and a lot faster to check.
Against its own baselines, it keeps 89× less in memory and checks the same proof up to 23.68× faster.
oraclizer.io/ss-gkr
Horizen Korea retweeted
Meet StateSync-GKR 🟢
Proving state changes just got a lot lighter, and a lot faster to check.
Against its own baselines, it keeps 89× less in memory and checks the same proof up to 23.68× faster.
oraclizer.io/ss-gkr
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…
