Pinned Tweet
In this blog post I introduce a useful concept for reasoning about rollups, sharding, light clients and bridges, called State Commitments Arguments.
pep.wtf/posts/sca-and-light-…
big pep retweeted
An example of the problems EU Inc will face by keeping "notarial control" in EU Inc article 14.
Official response from the German Chamber of Notaries: If you're not German or not European living in Germany, you can't use online digital tools.
Oh, and you can't use the digital tools you want: we also want a monopoly on software.
How come the @EU_Commission authorizes a monopoly on software to notaries?
How come EU Inc would reenforce and strengthen the notary monopoly and enable a huge company creation bottleneck by forcing a numerus clausus cartel to review EU Inc creations? Not on our watch
Repost. We hope @EP_Legal cancels the "notarial control" in the final EU Inc text.
PS: We believe MEPs and EU Commission are doing a great work on EU Inc. Yet this part of the draft is the one that needs to be fixed in the final voted law. We want them to open their eyes on all the issues this creates.
big pep retweeted
End of an era… 💔 After 14 years and 1.7 billion views, YouTube removed the original Rick Roll. 😢
youtu.be/dQw4w9WgXcQ?si=c9DW…
Let your friends know.
big pep retweeted
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.
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...)
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.
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 🧵!
No.
Cycle counts for compilation starts at billions.
Clang is low trillions.
Chromium is hundreds of trillions.
The first blockchain SDK that integrated NOMT!
big pep retweeted
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).
👀
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!
big pep retweeted
any database is just a WAL with indexes
then it’s down to tradeoffs in guarantees, storage and indexes
big pep retweeted
$1.4B and counting.
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 been upgraded.
Thank you to @alignedlayer, @class_lambda, @3miLabs, @levs57, and @kiliconu for responsible disclosure of these issues and working with us to resolve them.
We have shared more details on the issues on our blog
and also updated our release notes for SP1 Turbo.
We take security seriously at Succinct. We have undergone multiple audits for SP1 (github.com/succinctlabs/sp1/…), hosted an external audit competition (cantina.xyz/competitions/b92…), employed an internal auditor to thoroughly review all security-critical components of our codebase, and work closely with all our partners to ensure that production systems we deploy have necessary fail-safes.
In addition, we maintain several continuously updated resources that clearly define our security policy (github.com/succinctlabs/sp1/…) and security model (docs.succinct.xyz/docs/secur…).
Overall, while auditors provide valuable insights, they are not infallible, and we remain committed to continuously improving and working hard to ensure our systems are safe and secure for everyone.
Blog: blog.succinct.xyz/sp1-securi…
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.
