Announcing https://t.co/qYiMdHjH0X! 𝟘 𝟙 ❒ 🔨
Strengthen cryptography with AI.
Cryptography—both current and post-quantum cryptography—depends on hashes. SHA-256? SHA-3? BLAKE3? Nobody knows if they are secure. We're going to find out!
Come help accelerate scientific research!
HashSmash is an open science-acceleration project in collaboration with @yukonresearch, @eigenlabs, @projecteleven, and @ShieldedLabs.
It is difficult to explain just how impressive this is. The Tachyon Project (@TachyonZcash) and @zksecurityXYZ have raised the bar for high-assurance software.
https://t.co/FWxwbBhWVL
Who verifies the formal verification?
Read about how we audited @TachyonZcash's Ironwood formalization and about common pitfalls for formal verification in general.
https://t.co/UYEFx4I2x5
@kobigurk@leonardoalt You can use a compiler with a correctness theorem https://t.co/12oCW1iVSK and for memory safety use separation logic on the source (not yet implemented)
not sure I get the “rust is not needed anymore”, it should be more like “rust and memory safe code is easier to write now, so that’s why we’ll have less memory bugs”, same with formal verification and cryptography, etc
this is cool, making things like cache explicit could be really useful for high performance
in modern zk you’re sometimes bottlenecked by memory bandwidth and managing these boundaries can help a lot
anyone friends with @adityazero_? id love if he made a talk on Vx at frontiers - would be down to rearrange the schedule to make it work, the project seems actually extremely interesting and relevant to us from the Rust community
Two years ago I argued we needed an autoformalizer.
Now the time has come to formalize all of mathematics.
We need to unite behind a single Mathematics Autoformalization Project that turns all known mathematics into one Lean library.
@jdlichtman@patrickshafto
I cannot agree more. Kevin Buzzard made so many points I agree with. But the best one is this
"I thus believe that in the future we will reach a new “natural boundary” in mathematics, beyond (and perhaps way beyond) where we are now, but where machines are going to get stuck and where it is not viable to expend any more resources to make the next big leap. (...) I believe that the optimal thing to do (...) is to let the machines loose, see what happens, and then begin the journey to where they have stopped."
https://t.co/6J55GjyaST
We are very happy to announce that we have formally verified the techniques of Liam Eagen's https://t.co/X97yM76Ck1 in Lean 4, using only the standard axioms:
https://t.co/OJG1rz21pQ
https://t.co/5hqcVzjVPq
🧵1/6