Default avatar
npub1hr6v...2e29
npub1hr6v...2e29
Hear me out, PONS: Proof Of Non-Spam for Bitcoin! I was discussing with @Luke Dashjr about various usage of ZKP for Bitcoin, and he came with this intriguing idea to use Zero Knowledge Proofs to fight spam on Bitcoin (without breaking some designs such as BitVM). Initially I was sceptical, but the more I think about it, the more I am convinced that it could be a very interesting idea to explore. Just to be concrete, here are some examples of valid / non spam materials that could be theoretically proven via a system like PONS: - Schnorr public keys: Prove knowledge of corresponding private key - Hash preimages: Prove knowledge of data hashing to claimed values - Taproot scripts: Prove leaf scripts are valid Bitcoin Script, not arbitrary bytes - Merkle roots: Prove correspondence to actual Merkle trees of valid elements As usual, I like to experiment and play with ideas, so I started to implement a proof of concept of this idea, for the minimalistic simplest example here that is: prove that a public key is "real" and not a "fake" public key. You can see in the demo video below the following flow: - Generate a Schnorr public key and its corresponding private key - Create a digital signature of an arbitrary message - Run a Cairo program that verify the signature against the public key - Generate a STARK proof of the Cairo program execution using STWO prover - Verify the STARK proof using STWO verifier Sorry Luke Dashjr I know that you consider Rust as a woke language haha, but for now we have the STWO prover and verifier only implemented in Rust, so I used it for the demo. We can easily integrate the STWO verifier in Bitcoin Core or Knots via ffi though (as we already did in another POC). So of course here it's completely overkill to use a STARK proof for this and you could do it much more efficiently without a ZKP, but it is to show how the architecture could look like end to end. There are many interesting design questions, like how to make nodes / miners play nicely and prioritise transactions with valid proofs, how to incentivise the generation of proofs, how to make it efficient and not bloated, etc. I am curious to hear your thoughts on this idea, and if you think it could be a good idea to explore further. image
Breaking news coming from El Salvador today, let me introduce you the first Starknet powered Bitcoin ATM in the world! Edgar did the first ever Bitcoin purchase from a K1 ATM where the funding is coming from a Starknet wallet via an atomic swap to Lightning!
Spending some time with the great folks at @My First Bitcoin working on such an important mission: Bitcoin education in El Salvador and all over the world. As I was told here: Mi Primer Bitcoin is a MOVEMENT!
Yosh Nostriches, I am in San Salvador this week. Any recommendations for Bitcoiners to meet there or cool places for Bitcoiners in general.
I was chatting with the Alby wallet team about their Lightning MCP server using Nostr Wallet Connect. Forked it to integrate Lightning <> Starknet atomic swaps via Atomiq Labs SDK. In the demo, I fired up Claude Code (also did it with Goose) and asked it to handle an end-to-end swap: "swap 311 sats to STRK". It executed perfectly, pulling from my Primal wallet via NWC connection string and performing the swap. Fully trustless (HTLC reverse submarine swap). Exciting times for building Bitcoin apps with AI. 🧡 #Bitcoin #BitcoinAI #ClaudeCode #Goose
Hey, any Bitcoiner in Prague tomorrow? I won’t be there but have few colleagues from StarkWare who will be there and would love to meet more Bitcoiners. If you wanna hang out with them and chat about Bitcoin in general and / or zero knowledge proofs let me know.
Posting here for more visibility on Nostr. CTV + CSFS: a letter to the technical bitcoin community from 43 engineers Full text at ctv-csfs.com Let’s accelerate and improve Bitcoin as money and as a tool that people can use to take back their sovereignty. CTV and CSFS can improve significantly Lightning network and have many other benefits. Study them, discuss them, share your opinions, debate. Hyperbitcoinization intensifies. image
Stateful computation on Bitcoin mainnet without Fraud Proofs has been achieved internally with ColliderVM . It's a toy implementation to demonstrate the concepts. We can already do covenants on Bitcoin, now we are simply negotiating the price 😘 What are the interesting properties that ColliderVM could bring on the table: - Capital efficient: no fraud proof windows - 1-of-n security model for safety and liveness - No protocol upgrades / soft fork required - Immediate settlement without challenges The problem: Bitcoin's scripting language is intentionally limited, making stateful computation challenging. In particular: - No native statefulness: Bitcoin Script lacks loops, has size restrictions, and can't persist data across transactions - Capital inefficiency: Existing solutions like BitVM2 require operators to lock capital during fraud proof windows - Trust assumptions: Current approaches often require trusted setups or weaker security models In short, what you need to achieve stateful computation on Bitcoin is really those 2 properties: - Logic persistence (the code of the program / computation must remain consistent across transactions) - Data persistence (otherwise you are vulnerable to the inconsistent input problem) ColliderVM is an attempt to overcome those challenges in a different manner than BitVM. But before going deeper, let's be clear on the current status of ColliderVM: ColliderVM is currently a research project and should not be used in production environments. The protocol is in active development and exploration phase. While the theoretical foundations are promising, it remains unclear whether ColliderVM will prove practical for meaningful real-world use cases. Significant research and development work is still required to determine its viability. Ok, now that this important disclaimer is done, let's explore more the context of this demo on mainnet. In short, ColliderVM combines presigned transactions with hash collision puzzles to enable stateful computation without fraud proofs. - Presigned flows: Create 2^L parallel transaction flows during offline setup phase, each corresponding to a unique flow identifier. - Hash Collision Puzzle: Operators find nonce r such that H(x,r)|_B matches a flow ID, ensuring input consistency across transactions. - Immediate Settlement: No fraud proof windows or capital lock-up. So, what did we do for this Mainnet demo ? Real Bitcoin transactions demonstrating a ColliderVM's two-step range check computation: verifying that 100 < x < 200 across separate onchain transactions. The range check computation was split in 2 functions (F1: x > 100, F2: x < 200). The onchain hash function used is blake3 (BitVM implementation). Here is the transaction flow of the demo: - Funding transaction: Initial funding transaction that provides the UTXO for the ColliderVM computation sequence.( - F1 transaction: validates that the input value (114) is greater than the lower bound (100) ( - F2 transaction: validates that the input value (114) is less than the upper bound (200). Larger due to hash collision verification. ( - Spending transaction: Final transaction that releases the funds after successful verification of the range check computation. ( ColliderVM parameters used for the demo (very low security): - L: 4 bits, set size of 16 possible flows - B: 16 bits, hash prefix length for collision puzzle - Security gap: 6 bits (B - L/2 = 16 - 2 = 14 vs honest 12 bits) Total transaction fees: 172,126 sats (~$179 at demo time). ~136 kB of total onchain data. ColliderVM toy code: ColliderVM paper: image
Just run a node anon. And yeah you can choose whatever implementation you want. That’s good. Personally I prefer running Core and I don’t consider Knots being a production grade serious alternative on par with Core in terms of open source and software best practices (and there are obvious reasons for this to be the case, and it does not mean it could not change), but the choice is yours and it’s fine if you switch to Knots as a voice of protest. I think client diversity is a healthy debate to have at the end of the day, so maybe the filters drama was a good excuse to put it on the table I don’t know. I think there is a lot of bad faith arguments from some people pushing users to switch to Knots but that’s fine, Bitcoin is resilient and does not care about those drama. But yeah, just run a node, it really matters.
IT ALL COMES BACK TO BITCOIN. STARKNET IS EXPANDING TO BITCOIN, STARTING TODAY! THERE IS NO "IF" ANYMORE—IT’S HAPPENING, AND IT’S NOT CONDITIONAL ON OP_CAT OR ANY SOFT FORK. WE HAVE A PATH FOR OUR BITCOIN EXPANSION THAT IS NOT DEPENDENT ON ANY CHANGES TO BITCOIN. MULTISIG => BITVM => VALIDITY ROLLUP (IF / WHEN EFFICIENT STARK PROOF VERIFICATION BECOMES POSSIBLE). CHECK OUT MORE IN THE OFFICIAL ANNOUNCEMENTS: PARTNERSHIPS WITH BITCOIN ECOSYSTEM PLAYERS, STARKWARE ESTABLISHING A STRATEGIC BITCOIN RESERVE, THE BTCFI SEASON PROGRAM, AND MORE. I AM BEYOND EXCITED ABOUT THIS EXPANSION. FREEDOM TECH IS THE MOST IMPORTANT BATTLE OF OUR GENERATION. BITCOIN IS THE REPRESENTATION OF THIS FIGHT. IT IS THE HOPE TO BUILD A BETTER WORLD BY FIXING THE ASYMMETRY OF POWER. WE MUST RESTORE SOVEREIGNTY TO INDIVIDUALS. IT ALL COMES BACK TO BITCOIN. FIX THE MONEY, FIX THE WORLD!
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. image