big pep
@pepyakin
Followers
1K
Following
13K
Media
50
Statuses
1K
Building binary SNARKs at Irreducible. Protocols, databases, execution (wasm, RISC-V). Ex NOMT, Polkadot.
Berlin
Joined November 2012
In this blog post I introduce a useful concept for reasoning about rollups, sharding, light clients and bridges, called State Commitments Arguments. https://t.co/m8P3IkE73h
pep.wtf
I discuss the notion of state commitment arguments and how they are used to build light clients.
3
13
45
Irreducible's time has come to an end. Long story short, @radi_cojbasic and I ultimately came to the realization that we couldn't sustainably build the kind of deep tech business in ZK that motivated us.
40
14
215
Last nail into our beautiful fairy tale.
Since y'all spammed my timeline full of #Ethereum existential crises, here's a letter I sent to EF leadership in a year and half ago 😬. (link in next post because Twitter...)
1
0
5
What this announcement fails to convey is how easy it is to write circuits. Binius64 feels more like writing digital logic circuits writing than ZK arithmetic circuits.
1/ Today marks the beginning of a new chapter for Irreducible. We started as a custom-hardware company, and now we are fully focused on high-performance software. Read below about our pivot and our new proof system, Binius64 👇
0
5
28
AGI is upon us, bro behaves like a typical senior developer already.
0
0
8
It's so amusing when you ask claude to provide a plan for some change and it be like: Week 1: Base Infrastructure Week 2: Basic cases working Week 3: All test cases passing Week 4: Performance optimization & documentation and then it's done in like 10 minutes.
3
1
10
It seems to be possible to do better than just running a compiler within the zkvm, but the problem with that is you have to be smart.
0
0
2
No. Cycle counts for compilation starts at billions. Clang is low trillions. Chromium is hundreds of trillions.
1
0
2
Can we get apt-get repo but with SNARK proofs that the binaries actually come from the claimed commit and compiler? Especially now with the recent breakthroughs in zkvms like Jolt? Check out the 🧵!
Potentially, compilation could be skipped altogether and machine code for selected platforms could be posted along with a proof of correctness. There are some caveats and more research is needed, but it's nuts it's possible! Opens big design space.
1
0
8
The first blockchain SDK that integrated NOMT!
Introducing Sovereign SDK -- the first rollup framework that executes 99% of transactions under 10 ms, fast enough to bring price discovery fully onchain. Now even solo devs can build efficient, global financial apps. Production-ready today. Go build the next Hyperliquid.
2
6
51
@GldnCalf @GehrleinJonas Yes, we've been organizing this with Robert K., @pierreaubert from Parity & have started our planning phase. Not signed yet with Parity, hopefully will be executed this week, waiting on Parity Legal).
3
4
34
👀
Can't keep up with all the new zkVM announcements? Here's one you don't wont to miss. Today we are introducing a preview of PetraVM, a Binius-based verifiable VM built in collaboration with @0xPolygon!
0
0
4
ETH has a psyops problem
Eth L1 does not have a supply problem. Eth L1 has a demand problem. Gas price is <1gwei and at the lowest since EIP1559. Scaling L1 gas limit by 100x is moot if demand doesn't come back to L1.
17
49
454
any database is just a WAL with indexes then it’s down to tradeoffs in guarantees, storage and indexes
8
13
315
It's 2025 and people are still blind signing.
It's 2023 and people are still blind signing because no effort was put into solving this problem. These problems will keep happening, not on Polkadot though.
1
1
14
$1.4B and counting.
It's 2023 and people are still blind signing because no effort was put into solving this problem. These problems will keep happening, not on Polkadot though.
6
4
35
It's a shame that both SP1 and @RiscZero security model doesn't not allow untrusted code. The logic being: if the code can shoot itself in the knee then we can give up soundness. However, this logic is flawed in the presence of untrusted code execution, e.g. Smart-Contracts.
SP1 SECURITY DISCLOSURE Two weeks ago, we publicly disclosed security issues in a previous version of SP1 (V3) on our Github Security Advisory and developer TG. We have thoroughly investigated all reported issues and resolved them in SP1 Turbo (V4). All production customers have
0
0
2
That's basically the same approach as powdr describes but scaled to the entire program. I am not sure if that makes a lot of sense though, I am not a ZK guru.
1
0
0
This reminds me one of my ideas, I shared them in some channels (eg. w/ zkLLVM folks) but never on X: Split your program to BBs, number them. PC is now a BB index. Terminators are basically setting PC to the target BB. Then you optimize the shit out of each BBs.
We’re excited to share our latest research & experimental feature: automatically generated custom precompiles! 🤯 Read the detailed report in the article or check out this thread (1/8) 👇
1
0
2
If Native Rollups succeed then EF pull off the greatest rugpull (of the existing generation of rollups) ever.
Wrote my own take on the @drakefjustin's Native Rollups proposal. IMO native rollups are not worth as they presented and outline ways on how to improve them. 🧵
2
0
2