timo (@timofeyfey) header
timo (@timofeyfey) profile picture

research engineer @ChainSafeth / open-source dev https://xitter.cf/t.co/ZNz3fPKBjm / sharing findings about zk • mpc • ethereum • privacy • rust

Berlin
Joined September 2020
A photo walk in Taipei with my friend Tim. We talk AI, cryptography, trust on the internet, personal passions, travel, and more..
Zero-knowledge proofs are the privacy layer of crypto. That's the pitch. So I asked a ZK researcher @timofeyfey of @chainsafeth a simple question: what happens to your data when you delegate proof generation to a prover network? His answer: "Every prover network out there right now is not actually privacy preserving." 😬 1/
1
2
11
1,231
Big shoutout to @haochizzle for the top-notch production and epic edit. Loved working on this together!
1
1
2
97
(1/🧩) I just published a new blog post: Capture Hidden Trends - Use Cases for Private & Decentralized ML Training. What if we can uncover patterns hidden in private datasets without ever revealing the data itself? yuriko.io/posts/capture-hidd…
1
9
4
39
4,092
I was reading the "Intro to ProgCrypto" book by @0xPARC. To understand the examples and algos better, I translated them line-by-line to Jupyter notebooks. I plan to add exercises and use it as a base to learn advanced topics for each chapter github.com/flyingnobita/0xpa… ⬇️
4
9
1
87
4,864
On top of being a post quantum poly commitment scheme with high verification speeds, I was surprised by how gas efficient WHIR can be! We compiled results in an eth research post with @GiacomoFenzi (and the verifier is MIT licensed) ethresear.ch/t/on-the-gas-ef…
3
11
3
63
5,141
2
3
1
27
2,369
As part of our exploration at @NPLabs_ into plonky3 and recursive proofs, we've been working on an implementation of hybrid-hash Merkle Trees. We have a technical primer for you: np.engineering/posts/hybrid-… and a high-level summary in this 🧵:
2
11
1
40
3,080
Try it out here: keccak.binius.iosis.tech/ Repo: github.com/Okm165/binius-web… This is Binius Keccak256 circuit with logic to prove & verify its trace, all wrapped in WASM. Also some quick UI in Next to present it ofc ;)
3
3
1
21
5,086
🥈 Second Prize: Spectre-R&D Spectre, a ZK light client developed by ChainSafe, integrates with Aligned in this proof of concept to demonstrate how Aligned enhances fast and secure light client bridging as part of Sprinter's interoperability solution. Team: github.com/jonas089 from @sprinter_ux & @ChainSafeth Project: devfolio.co/projects/spectre…
1
1
2
9
2,220
introducing @commitwtf — an onchain accountability protocol aiming to make people accountable by adding crypto stakes. If someone doesn't deliver, their stake is shared among those who do.
73
53
32
515
81,532
*The* decentralized protocol and infrastructure conference is back! Announcing: 𝐏𝐫𝐨𝐭𝐨𝐜𝐨𝐥 𝐁𝐞𝐫𝐠 𝐯𝟐 June 12-13, 2025, Prenzlauer Berg, Berlin.
11
34
25
205
38,372
𝗔𝗻𝗻𝗼𝘂𝗻𝗰𝗶𝗻𝗴 𝗽𝗼𝘄𝗱𝗿𝗩𝗠 𝟬.𝟭! powdrVM combines multi-prover support, std Rust, modularity, and high performance, setting the stage for future-proof ZK applications. Read the details on our blog or follow this thread for a tl;dr 👇 powdr.org/blog/powdrvm
7
30
8
115
17,799
Last year, @Istvan_A_Seres, @cryptonoemi and @josephbonneau published the Naysayer Proofs paper, proposing optimistic verification of SNARKs. We present the first instantiation of Naysayer proofs for Ligero & Brakedown polynomial commitment schemes: np.engineering/posts/naysaye…
2
5
2
26
2,368
nayuki.io/ -- this site is a treasure! and those tiny illustration icons author made for each post are the cherry on top of the cake
1
4
265
Thrilled to see that the Circle STARKs article I posted earlier was translated into Chinese by @kurtpan666 and @ZKPunk_org -- thanks for spreading the word! mp.weixin.qq.com/s/ay3RO9T3_…
1
1
3
364
don't be a crypto script kiddie. for a long time, just doing smart contract work and being able to write smart contracts bytecode by bytecode was the equivalent of being god in the community. we rallied and circlejerked around these creatures, while other disciplines like being a core dev remained more obscure. now, we've moved on, and competition is tougher than ever. we've realized it's not enough to just be a solidity savant—the rise of ZK has shown that you must learn the math behind it, or be left behind. the sophistication of MEV taught a lot of people the fundamentals of optimizations in computer programs, networking and the fundamentals of different consensus systems (and how nasty these games can get, if you remember MEV on Avalanche in 2021). most importantly, we forgot to actually use our software, to feel the pain our users feel—from the infra to actual apps. hence our current mess. but as an engineer, your duty is to always be able to move faster, build better, while maintaining correctness. learning your fundamentals is worth it—there is no excuse to not know your tools. all the software is open source, and no permission is needed to hack together a feature and throw in a PR. do not do it for the fame, but for the love of the craft. it is never too late, no matter how obsessed with young wunderkinds we are. before you know, the engineering gods you worshipped could become peers, friends, or even foes in competing startups. but this can only happen if you put in the work. don't be a crypto script kiddie.
4
5
92
3,833