if you are familiar with both @NoirLang and bitcoin signatures, and want to review something we're cooking (paid), please dm 😊

BIP448 is a softfork that brings (re)bindable signatures to bitcoin here’s how it can improve statechains: (private, instant, self-custodial bitcoin transactions btw) bip448.cash by @lxdev_ + w0xlt of @lclhostresearch, first of his name, rebinder of signatures

Privacy on Bitcoin is a constant battle, but what if statechains were part of the answer? In this clip from Chat_176, Talip and I explore how statechains can enable private Bitcoin activity without exposing your moves on L1. We get into amount-hiding sidechains, dark pools, and why designs that auto-return funds to you if a custodian disappears are so powerful. This one’s a technical nerd-snipe into the future of private Bitcoin markets and smarter custody.

MFTV #14: Bitcoin Privacy Done Right | with @januszg_ of @lxdev_ 🔗 YouTube: piped.video/kLRQI9Em8SM 🔗 Spotify: open.spotify.com/episode/59Q… CEO of LX and former founder of Bitcoin Layers, Janusz, joins Head of MARA Foundation @isabelfoxenduke to discuss how private payments could work on Bitcoin through zero-knowledge proofs, what the recent Zcash bug reveals about the risks, and why he sees avoiding KYC as the true starting point for privacy. MORE ON MFTV WITH JANUSZ → - How zero-knowledge proofs could bring private payments to Bitcoin, and the trade-offs they require - Why he argues blockchain privacy starts with avoiding KYC - What the recent Zcash bug reveals about the risks of these systems - The state of the Bitcoin L2 ecosystem after the hype TIMESTAMPS: 00:00 — Intro 00:18 — From Zcash to building Bitcoin privacy 04:26 — Privacy vs scalability for ZK on Bitcoin 12:35 — Why Zcash’s supply is a blackbox 22:35 — The deeper failure: Zcash's centralized fork 25:12 — Can these bugs be prevented? Formal verification 27:16 — Why privacy starts with avoiding KYC 38:30 — The regulatory and software hurdles to shipping privacy 42:54 — Privacy across Bitcoin L2s 49:39 — Bitcoin L2s after the hype 59:54 — Zcash's resurgence, premines, and token narratives

Are conspiracy theories in Bitcoin actually true? Our guest Talip gave an insider's perspective on the BIP 110 spam war that I wasn't expecting. We then got straight to the reality of AI-driven red teaming, statechains privacy, and ended up debating why now might be the most important time for Bitcoin to return to its cypherpunk roots.

we're taking this offline next week 🙂 as far as we can tell, no one deposited through the bridge contract and we turned off LN receive in the wallet application so no one should've been able to deposit their own funds but if we gave you some free sats to test, and they're still sitting around, withdraw to your LN wallet! thanks to everyone who tested this experiment with us 🧡

.@lxdev_ is proud to be sponsoring @_julian256_'s work related to Script Restoration you can learn more about the proposal, and its progress, below

we built a bitcoin dark pools prototype 🪄 tl;dr - we built a privacy-preserving, bitcoin exchange using @mercurylayer, nostr, and a zk-execution network. the bitcoin transfer is completed offchain via a blind co-signer. the stablecoin network only reveals hashes of inputs and outputs, no amounts or user addresses. orders are matched peer-to-peer using nostr identities. exchange is atomic & privacy-preserving. deets: this protocol is built on the following: - statechains, a way to transfer ownership for bitcoin utxos offchain by reassigning spending keys - private stablecoin network with flexible zk-circuits/contracts that lock funds to a specific sha256 hash - a blind co-signer that facilitates ownership transfer for bitcoin utxos offchain per a specific order the exchange builds upon mercury layers’ latch protocol. the seller locks their offchain "utxo" into an order that they create. the order specifies that an offchain transfer to the buyer’s offchain address should occur after buyer & seller commit to it. an order with a hash is created. the order hash is then used to lock stablecoins on the zk network. meaning, the buyer must lock their funds into an escrow contract where the funds are only claimable by revealing the preimage for the order’s sha256 hash (or they refund the buyer after a timelock). after these stables (or any other shitcoin, tbh) are locked on the zk side, the buyer submits the tx hash to the seller. after verifying that stables are locked in escrow, the seller calls the co-signer to unlock the transfer to the buyer. after verifying that the seller has committed this, the buyer also calls the co-signer to unlock the transfer. the co-signer reassigns the statechain multisig spending key to the buyer and tweaks their keyshare. the co-signer then deletes their key with the seller. after the statechain transfer, the co-signer then reveals the preimage for the order to the seller. the seller uses that to claim the stables on the zk network out of the escrow contract. swap completed. buyer trusts signer deleted their keyshare up until the point the exit the statechain back to bitcoin. we’ve taken this swap protocol and developed an RFQ protocol using nostr identities. in the exchange application, users create a nostr identity and submit buy and sell orders. only their npub, and the amount of their respective order, is revealed. no bitcoin addresses or other pii is exposed. when a user finds an suitable offer in the orderbook, they submit an encrypted firm quote with exact amounts and prices. only the counterparty in the trade can decrypt this message. from an onchain perspective, there is no onchain bitcoin transaction. on the stablecoin side, zk magic only see hashes of inputs and outputs publicly available. you can’t even discern which token was involved in the trade. the co-signer is blind and dumb. validation is done peer-to-peer between countparties. co-signer only signs when its told to. this is a demo and opinionated design. in our view, it’s extremely privacy-preserving and makes nice tradeoffs wrt user self-custody. we’ll building more optimized versions that make different tradeoffs, but wanted to share this example. all code will be open-sourced in the future. 🪄

ACQUIRED: Bitcoin developer @stutxo announces his next gig at @lxdev_

We made a bit of history at @BTCPrague. The first bitcoin payments using zero-knowledge proofs were sent over Lightning. Discussed by Satoshi 2010, ZK can improve bitcoin privacy. Our experiment was the first real-world demo to showcase how:

i joined @lxdev_, time to build private cash on the internet ⚡️🛡️

hi - we launched a bitcoin-denominated payments network that uses zero-knowledge proofs for improved privacy

.@lxdev_ has raised a pre-seed round from @DraperVC, @DraperDragon, and Peer VC to work on bitcoin privacy updates on our work are coming soon

icymi: we sponsored research report from @gusgutoski on shielded csv, a proposal that improves scalability and privacy for bitcoin payments you can read the report here: ggutoski.github.io/shielded-…

in nyc for @OPNEXT2026? join us at @PubKey for the official op_next after party and have a beer on us (or 5)