zooko🛡🦓🦓🦓 ⓩ
142.9K posts

zooko🛡🦓🦓🦓 ⓩ
@zooko
Freedom maximalist. Good vibes only.





@jimouris Sure! Pull up a chair for more Story Time With Grandpa! BLAKE was designed by some excellent cryptographers (Jean-Philippe Aumasson, Luca Henzen, Willi Meier, and Raphael Phan), for the SHA3 competition, at a time when hash function design was in somewhat of a crisis. ⤵️

“We were not aware that civilisation was a thin and precarious crust . . . only maintained by rules and conventions skilfully put across and guilefully preserved.” Keynes on the limitations of the philosophy held by himself and his friends prior to WWI




Coinholder-Directed Grants Program (Q1 Round) has opened! Time to vote with your orchard shielded $ZEC ⤵️ Click for tutorials and more info below: forum.zcashcommunity.com/t/polling-open…




1/ If your business model is “our software refuses to talk to theirs,” I have some bad news about lobsters. 🦞 OpenClaw is brute-force interoperability for a stubbornly incompatible ecosystem.

@ViktorBunin Etc etc. You can see where this is going, right? You’ll ask it to live deepfake video of being you, call your phone company, and sit there chatting with their customer support person until they fix your service. You’ll remind him to make sure they can’t tell it’s not you.





This is exciting work from @powdr_labs: ~1.5x speedup & a 5x-6x reduction in memory from ZK proving WASM instead of RISC-V 🔥 (and this is without circuit optimizations, autoprecompiles, etc) While most zkVMs currently prove the RISC-V ISA because of advantages like a limited instruction set, it is far from obvious RISC-V will continue to be the winner in the long term. It’s worth keeping in mind how new the field of zkVMs is: @RiscZero released the first production grade zkVM only in 2022, and commercially viable real-time mainnet EVM proving was only just achieved earlier in 2025 by @SuccinctLabs This is why we at @Offchain proposed that @ethereum L1 should use WASM as the delivery ISA instead of RISC-V. WASM is designed as intermediate abstraction layer rather than the final execution target. WASM as a dISA can allow smart contract proving (including proving on RISC-V or WASM or other more ZK friendly ISAs), programming, and execution to evolve freely, rather than constraining each other. This is separation of a delivery ISA from a proving ISA is what we already do today for ZK proving @Arbitrum with Succinct’s SP1 Hypercube. By compiling WASM code into RISC-V code, we are able to ZK-prove not only the core Arbitrum STF, but also user-supplied Arbitrum Stylus smart contracts written for WASM (including Rust, C/C++, Move, AssemblyScript based programs)




