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 →

Me today: write BDHKE scheme in Zig (https://github.com/AbdelStark/coconut). Benchmark it: Oh wow it's super fast, 1 millisecond for the end to end scheme. Find the Rust implementation (https://github.com/ngutech21/moksha) and benchmark it: it's about 10 times faster than my Zig implementation 😭 Gg Moksha folks! 🦀 is blazingly fast damn. I suspect there might be a gap in terms of performance between the Secp256k1 implementation of the Zig std lib and the C implementation (the secp256k1 crate being a Rust wrapper library for Pieter Wuille's libsecp256k1 in C). Zig benchmark: Rut benchmark:

Yo #nostr fam, anyone going to Surfin Bitcoin this year ? I will be there and giving a talk about Scaling Bitcoin using STARKs. Bring back OP_CAT.

What about Zkfying Cashu guys ? https://hackmd.io/@abdelhamid/starknut-zkfying-cashu

Implemented step 1 of the Blind Diffie-Hellmann Key Exchange (BDHKE) in Cairo. This scheme is used in Cashu (ecash protocol for #Bitcoin). Tested against the Nutshell reference implementation and got same results for blinding of secret messages. Would be cool to implement the other steps to have a version of Cashu protocol that is provable with STARK proofs.

GitHub

GitHub - AbdelStark/cashu-zk-engine: Cashu Protocol ZK engine. Blind Diffie-Hellmann Key Exchange (BDHKE) implementation in Cairo.

Cashu Protocol ZK engine. Blind Diffie-Hellmann Key Exchange (BDHKE) implementation in Cairo. - AbdelStark/cashu-zk-engine

Macro is horrible, risks of escalation of war, Asian Stock Markets crashing like never, capitulation from large funds. Nayib Bukele knows it well, Printer is coming. That's why he was smart enough to bet the future of El Salvador on #Bitcoin, and history will prove him right. No doubt about this.

X (formerly Twitter)

Nayib Bukele (@nayibbukele) on X

Brrrrrrr…

👀

#Nostr #FreedomOfSpeech Protocol

Provable Bitcoin Script VM is moving forward nicely, we implemented more than half of the opcodes in a week 🤯

GitHub

GitHub - starkware-bitcoin/shinigami: Bitcoin Script VM in Cairo

Bitcoin Script VM in Cairo. Contribute to starkware-bitcoin/shinigami development by creating an account on GitHub.

Of course in the remaining ones there are some that are much more complex to implement, but this is very promising.

Powering Verifiable Computation for the Nostr Revolution: https://hackmd.io/@abdelhamid/nostr-dvm-verifiable-computation #Nostr #FreedomOfSpeech #Integrity

Verifiable computation for Nostr Data Vending Machines. Nostr DVMs are the future: - free market - censorship resistant - standardised What if we could bring ZKPs to make the computations of DVMs provable ? Here you, with Askeladd : - NIP-90 compliant. - Uses STWO prover to generate Circle STARK proofs. - In-browser proof verification using Web assembly STWO verifier. For the user it's very simple: - Submit the job via a web page signing a Nostr message (with any NIP-07 compatible extension) - Get the result and verify the proof in the browser directly Try it yourself:

Askeladd DVM Marketplace

A decentralized marketplace for Zero-Knowledge Proofs

Bonus side effect of building this POC: I was able to catch and report a bug in the Nostr Rust SDK. Shout ouf to the maintainers who fixed it few hours later. I may be the one who implemented the first NIP-90 compatible DVM in Rust 😜

GitHub

NIP-90 Job Result compliance: Missing ability to set `content` field in DVM job result · Issue #512 · rust-nostr/nostr

Description According to NIP-90, the result of a Data Vending Machine (DVM) Job should be placed in the content field of the Nostr event. However, ...

View quoted note →