Ph.D. studies in cryptology at @AaltoUniversity, crypto/mobile consulting, @reactnavigation // @usecapsule @rainbowdotme @swmansion @meta šŸ³ļøā€šŸŒˆ

Helsinki, Suomi
Joined July 2018
osdnk retweeted
Post-quantum proofs need practical proving times. How much faster can we make a lattice-based prover? We have launched labini.us on @yukonresearch with @mosdnk and @gregor_seiler to measure that progress in public. Optimize a packed-binary commitment opening over a 2³¹-bit table; every proof must pass the same reference verifier. Five fresh-seed runs. Median prover time. Lower wins. Walkthrough below
4
6
1
33
1,259
osdnk retweeted
one day you wrote console.log("here") for the last time and didn't even know it
213
1,730
268
17,896
597,863
Very excited to see how much we can squeeze out of lattice-based arithmetic! We’ve made huge strides over the years, and there’s still so much to look forward to!
NEW CHALLENGE LIVE: labini.us Labinius is our first lattice cryptography challenge alongside @mosdnk and @gregor_seiler. Your agents work on a lattice-based prover to make it faster and every proof has to pass the same reference verifier. Lattices already protect connections in Chrome and Firefox. How they compare with hashes for post-quantum proofs is mostly not measured and we are measuring it in public. Bring your agents.
1
1
13
706
This project is not only something I truly believe belongs to the next generation of lattice-based arguments, but also a wonderful way to round off my PhD.
83
1/ Today we’re releasing Aerie: fast post-quantum signature aggregation, using lattice-based SNARKs for lattice-based Falcon signatures. On a laptop (CPU only), it aggregates roughly a full Ethereum slot’s worth of signatures (32,768) in 0.65 seconds.
43
82
16
519
49,405
I was the biggest stickler for ā€œcode qualityā€ and ease of editing. I have two blog posts ranting about semicolons, but the code doesn’t really matter as much anymore. Before TypeScript the JavaScript code in a function mattered a lot because you’d need to follow it and confirm it was right while reading, after TypeScript you could just trust the input and output types, after AI we’re trying to go up a layer, where we have many e2e tests, fuzz testing, visual regression tests, benchmarking, and if those are right we don’t care so much about the code anymore, and we can even easily rewrite it or optimize performance. We can actually make the code higher quality than ever, it’s not that the code looks right, it’s that the output a user sees looks right, and we can validate that. This could be done before but it was prohibitively expensive, automating things, dealing with flakes, writing new cases for new code, it was hard, and now it’s easy, and we can create better results than ever before.
2
6
554
The massive game-changer would be if AI could read a paper and jump on a call to discuss or give me an interactive seminar presentation.
1
1
282
osdnk retweeted
ā€œthere aren’t any cryptography resultsā€ ā€œthere aren’t any cryptography resultsā€
30
338
28
6,419
227,424
Drop the ego and then curiosity, exploration, and discovery emerge. The best part of technology. "What if?" It's better now than ever before.
10
9
154
31,350
LaBinius: Lattice-based Polynomial Commitment Scheme over a Binary Field. Excited to present LaBinius, my recent work with @gregor_seiler. We show how to instantiate an Ajtai commitment over extremely efficient cyclotomic power-of-three rings and then connect it with a polynomial opening mod 2, so that R/2R is a binary field. Such a PCS is bridged with SOTA frontends, including Flock and Binius, to obtain end-to-end proofs of standard hashes with throughput of tens of thousands per second. osdnk.me/blog/labinius
3
33
2
128
13,737
šŸ—£ļø Can we evaluate the process of intellectual production rather than just the final text? Can we creatively design approaches to filter unaccountable research and nudge researchers and students toward genuine ownership of their work? Yes. 1/11 🧵
20
24
6
121
19,851
Many papers these days acknowledge that chatGPT-6 found the proof, but the authors later simplified the argument. Wondering whether this was through an additional prompt: "make sure the proof is as simple as possible". This is actually quite effective, from what I can see.
4
7
87
7,402
I don't think people realize just how much AI's latest breakthroughs in math have shocked mathematicians, myself included. The main thing that leaves me and many mathematicians shocked is what AI is solving: Early on – till about 4 months ago – AI was good at: (i) solving problems that humans already solved, like Math Olympiad problems (ii) finding out that a problem in field A was already solved by an obscure work in field B, using a different terminology (or language). But starting with the shocking work on the Erdos Unit Distance Problem, and up till the recent advance on Navier–Stokes, a totally different AI is seen. It is innovating. It's bringing a new set of tools to the problem, and then proceeding to using those tools very delicately and accurately to achieve the result. It's a bit like how a brain surgeon delicately operates on the exact region that needs fixing. This is absolutely shocking and unexpected. It raises the question of what exactly constitutes mathematical intuition and brilliance. Many a mathematician have written about it (I love Henri Poincare's treatise "Mathematical Creation"). But we don't understand how mathematicians reach their breakthroughs. Now, it's the same with AI, we don't understand how it goes about reaching these proofs but the end result is objectively new, and powerful. This creativity, insight, ingenuity, is what's shocking to me.
71
107
18
738
58,187
RoKoko works with regular SIS! RoKoko is a succinct lattice-based SNARK/PCS obtaining state-of-the-art runtime efficiency across all metrics šŸŽ with small proof sizes (ePrint 2026/575). Originally, it was instantiated with a vSIS-based commitment, which particularly benefited verifier runtime. This places our protocol in the world of non-standard assumptions, which may not be acceptable in some applications. In my recent blog post, I show how to instantiate Rokoko with standard assumptions with only little efficiency loss! osdnk.me/blog/rokoko-standar… Thanks to my co-authors ✨ for their work on the original paper: @russell_wf_lai, @KhanhCrypto, Michael & Lorenzo!
1
8
22
1,629
Thanks to my amazing co-authors ✨ for their efforts on the original paper: @russell_wf_lai, @KhanhCrypto, Michael & Lorenzo!
68
I wrote some thoughts about AI, research and crypto. osdnk.me/blog/personal-knowl…
5
1,108
šŸ”„šŸ”„šŸ”„ Get ready for #ZKProof 2026! Speaker: Michał Osadnik @mosdnk from @AaltoUniversity Join us in Rome, May 9-10 to discuss the latest in ZKPs and applications, the Quantum threat, formal verification in ArkLib, IOPs & more. For more details - link in the first comment.
1
1
6
391
Introducing Zinc+, where we tackle the problem of arithmetizing and proving computations unfriendly to finite fields. Examples: classic hashes, hash + signature, lattice ops., etc. We prove 7 SHA-256 compressions followed by the ECDSA MSM with:
12
32
5
156
18,119
I published a blog post on how to design a more efficient lattice-based folding scheme based on LatticeFold+ and SNARKs-inspired tricks. osdnk.me/blog/l2-folding-sch… I relied on the work of @Charles_Chen533, @danboneh, @russell_wf_lai ,@KhanhCrypto & myself (& authors w/o x account)
4
12
1,376
Have you tried React Navigation 7's static API yet? It aims to solve 2 major pain points: šŸ¤– Simpler TypeScript types šŸ”— Easier deep linking To try it, install next tag of the React Navigation packages: yarn add @react-navigation/native@next @react-navigation/native-stack@next
3
11
1
64
5,279