Newsletters
»
Weekly 12
Week 45
Hello everyone, happy to share a new edition of the Fairgate Weekly with you. Hope you enjoy it and as always, please recommend it to help spread the word!
Happy reading 📚
A new article by Martín Jonas from Fairgate Labs explores Zero-Knowledge proof verification on Bitcoin using the BitVMX protocol, enabling two parties to execute a program off-chain and verify correct execution through on-chain challenges.
bitvmx.org/knowledge
🔗
Zero Knowledge Proof Verification On Bitcoin
A key advantage of ZKPs is that they allow the prover to convince the verifier they have the correct input for a program—without revealing that input. Beyond input privacy, a significant benefit is that some algorithms, particularly Groth16, produce proofs of constant size, around only 300 bytes.”
A Citrea podcast featuring Orkun Kılıç, co-founder of Chainway Labs, introduces Citrea—an ambitious initiative leveraging BitVM’s verification capabilities to inscribe ZK rollups on the Bitcoin blockchain.
bitcoin-takeover.com
🔗
Orkun Kılıç on Citrea, The First ZK Rollups on Bitcoin
Citrea is not just another project; it’s the first implementation of zero-knowledge roll-ups on Bitcoin. This means we can now build a plethora of applications on Bitcoin without altering the network’s consensus rules. The promise of Citrea is a world where Bitcoin can handle a multitude of transactions, smart contracts, and decentralized applications with the same level of security but at a fraction of the cost and time.
A new paper by Ethan Heilman , Victor Kolobov, Avihu Levy and Andrew Poelstra introduces a method to enforce Bitcoin covenants without protocol changes by using hash collision-based checks to enable signature evaluation within covenant scripts, allowing for introspection and enhanced transaction control.
colliderscript.co
🔗
ColliderScript: Covenants in Bitcoin via 160-bit hash collisions
The most direct way to enable covenants would be to extend the Bitcoin Script language to include transaction introspection opcodes, which directly copy transaction data onto the stack to be processed by other opcodes. A less direct way would be to heal the split between Big Script and Small script, e.g. by enabling the OP CAT concatenation opcode. However, any changes to Bitcoin must have consensus across all economic stakeholders, and because of the controversy around covenants in particular, consensus on any changes may not be achieved quickly.
That's a wrap for this week's edition.
Let's meet again in a week!
Keep on building 🚀