First oracle state machine delivering complete state synchronization between on-chain and off-chain worlds. Complete regulatory compliance for RWAs.
Global
Joined December 2023
- Tweets287
- Following49
- Followers1.2K
- Likes278
Pinned Tweet
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
Oraclizer 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
Oraclizer retweeted
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
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
👀
StateSync-GKR v1.2.0 is out.
Measured next to v1.1.0 on the same 192-core server, same day: 3,300 requests a second, each proved and verified within 1 s, up from 1,150. At 1,000 a second, 99% of requests now finish within 34 ms, down from 440.
oraclizer.io/ss-gkr/performa…
StateSync-GKR is the prover inside @Oraclizer's state sync: every change that crosses between a chain and the off-chain world gets its first proof here. At this speed that proof lands in milliseconds, the clock trading runs on, instead of waiting for an end-of-day reconciliation. That brings Oraclizer a real step closer to its purpose.
Regulatory compliance must be mathematically verifiable, not merely implemented.
Building on ERC-8319, ERC-TRUST brings formally verified regulatory execution to security tokens.
From regulatory standards to machine-verified execution.
This is the foundation institutional RWA needs.
ERC-TRUST from @Oraclizer runs regulatory actions on security tokens: six typed actions, fail-closed, one receipt each. It builds on ERC-8319, which I co-authored with @robviglione and @DanSpuller, and our proofs ran on tools from @certora and @rv_inc.
github.com/Oraclizer/erc-tru…
ERC-7943 built in, ERC-3643 plugs in.
Dan wrote ERC-8319's policy principles, and ERC-TRUST lives by them: a technical capability is not a legal obligation, the chain carries out decisions made through due process and never makes them, and compliance stays modular, so no market is forced into another's rules.
Certora's Prover checked our rules that the ERC-3643 adapter can never claim Full and that its receipts carry the token's real restriction state. With Runtime Verification's KEVM and Kontrol, we proved on the compiled bytecode that raw freeze and forced-transfer calls stay closed, that failures and non-raising freezes leave state untouched, and that LIQUIDATE moves exactly its amount and ends with its receipt.
Thank you, Rob and Dan, and the Certora and Runtime Verification teams.
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
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…
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.
[5/5] 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…
👀
A state oracle asks another ledger the same questions: is this record there, is it gone, did it change correctly. Last December we showed why GKR fits this work. Over ten months at @Oraclizer we built the StateSync-GKR prover around those questions.
research.oraclizer.io/states…
Oraclizer retweeted
A state oracle asks another ledger the same questions: is this record there, is it gone, did it change correctly. Last December we showed why GKR fits this work. Over ten months at @Oraclizer we built the StateSync-GKR prover around those questions.
research.oraclizer.io/states…
RT @GaeaVentures: 🤖📈 AI Meets the Chart — A Horizon Series Event @ KBW!
A look back at an evening in Seoul exploring how AI is reshaping tr…