Gm to the believers who want to change the world.

I can’t wait. Who is coming to Bitcoin++ next week ? Would love to meet as many Bitcoiners as possible. Time to go nuts 🥜 View quoted note →

Bitcoin for peace. You have no enemies. View quoted note →

Thorfinn’s evolution is truly inspirational. Breaking the circle of hate is not easy. In order to become a genuine warrior, it is necessary to forgive oneself and others. I have no enemies.

Did we prove with a STARK proof the execution of the First ever transaction from Satoshi to Hal Finney ? Yes absolutely. In less than 2 months, we implemented the Bitcoin Script VM in Cairo. (check code: https://github.com/keep-starknet-strange/shinigami) Another showcase on how powerful it is to have a specialised high level DSL optimised for ZK. Proving integrity of arbitrary computation is extremely powerful, and it can benefit widely to the Bitcoin ecosystem, and the good news: even without any soft fork! Yes, there are use cases and things than can be improved using STARK proofs, completely offchain. Stay tuned, it's only the start!

Any Zig dev over there ? #Zig #Bitcoin

Starting Zig Bitcoin Community effort:

GitHub

Zig Bitcoin Community

Bitcoin libraries and tooling in Zig. Zig Bitcoin Community has 7 repositories available. Follow their code on GitHub.

Zig language is still very much underrated IMO. One thing that is awesome is the way you can use it progressively: - First as a toolchain. You can replace a complex build system for your C/C++ with a simple build.zig that gives you easy portability and other great things. - Then, you can seamlessly build new parts of your projects in Zig, and connect it natively with the rest of your codebase. So you don't have to engage in a big and complex migration. I love how Zig is (similar to Go) idiomatic by default. Don't forget the fact that we read code more than 10x more than we write code. So the ability to read and understand code is extremely important. Put it simply, in Rust, for one problem / thing, depending on the Rust dev who will work on it, you can have a lot of different possibilities / style / practices to solve it. On Zig, this is drastically reduced, usually there is one obvious way to do one thing. Rust is getting more and more complex, and there are so many ways of doing the same thing. So even Rust senior devs can be lost when working on a new code base. I like the simplicity of Zig, communicate intent precisely, no macro and magic code. Zig has to catchup the Rust ecosystem in terms of tooling and libraries but clearly this language has a very strong potential. Those are some reasons why I want to start a Bitcoin Zig Community initiative. The goal is to build primitives, libraries and tooling in Zig for Bitcoin ecosystem. It can be great educational content and way to onboard to Bitcoin ecosystem as a developer. Also, it can help increase diversity of implementations. For instance, similarly to what Roasbeef is doing with btcd, which I think is great. We start by those projects: - bitcoin-zig: Core Bitcoin primitives implemented in Zig, including base58, bech32, and more. - btczee: A full Bitcoin protocol implementation in Zig, including a node, wallet, and miner. - coconut: A Cashu wallet and mint implementation in Zig - libsecp256k1-zig: Zig bindings for the libsecp256k1 library, essential for Bitcoin cryptography. So if you are a developer and you like Bitcoin and you are fan of Zig (or you don't know it yet), come and contribute to this open source initiative.

Was great spending time with a lot of Bitcoiners at Surfin Bitcoin in Biarritz. One thing I realized is that sometimes it’s not easy to debate the idea themselves and that there is a more and more natural tendency to judge an idea based on who emit it. Which is a clear paradox when we want to build trustless (or at least trust minimized systems ). This is somewhat inevitable in the sense that not everyone can understand and participate in highly technical and complex discussions, so the trust by delegation is pretty natural to some extent. But still I think it’s important to keep this in mind and try to focus as much as possible on debating the ideas themselves.

Ready for Surfin Bitcoin starting today.

Kinda feel sad for those two folks I saw on the street, wearing guns and bulletproof vests, risking their lives to transport worthless FIAT money that central banks and governments can print out of thin air. If only there could be a way to transport unstoppable value simply with a cryptographic signature gossiped over a P2P network. #Bitcoin fixes this. Bitcoin is for peace.

何も知らずに一生壁の中で過ごすなんて嫌だ！ I don’t want to spend my entire life inside these walls without knowing anything!

Summary of my fun week playing with Cashu, that I discovered recently. This week I did: - try and tested Cashu.me wallet and loved the UX from the user perspective (sending some sats to my Cashu wallet directly from my Nostr client was also very fun) - read the Cashu docs - implemented first step of BDHKE in Cairo and wrote an article about potentially ZKfying Cashu using STARK proofs - implemented the full BDHKE in Zig - contributed to Moksha Rust implementation to add criterion benchmarks - realised that my Zig implementation was 10x slower - moved to using the libsecp256k1 in C instead of Secp256k1 from the Zig std lib - managed to have better perf than the Rust version - contributed to CDK to add criterion benchmarks

Managed to beat the Rust implementation with a Zig implementation ⚡️ Initially it was slower, but, moving to use the same libsec256k1 C implementation for operations on SECP256k1 curve, now the Zig version is slightly faster. 113 micro seconds for the End to End BDHKE! Zig is fast ⚡ View quoted note →