Jesse de Wit

@callebtc Nice. I like that it touches only the signer.

I might have just built the first ever multisig Bitcoin Lightning wallet. Runs on Spark L2. It's a federated Lightning wallet demo with multiple signers, a 2-of-3 for example. Uses FROST. Keyshares generated with chill-dkg.

🚨🚨 My Telegram has been compromised today. If you receive messages from me (t.me/starnold), don't reply. And if you do, please send screenshots to me, so I can investigate futher.

@PalazzoVincenzo @Breez_Tech @dannystagg Very cool! Can the SDK detect a *wink* so you can wink-to-pay?

How I paid with Bitcoin using my Meta glasses built by @Breez_Tech Thanks to @dannystagg, for pushing me to implement this idea x.com/PalazzoVincenz…

@paoloardoino When open source?

Linux ❤️ Keet is available on Flathub flathub.org/en/apps/io.kee…

@Idoumou_B Wait, there's more.

@Du_Bi_Bo Just stop yelling at the cloud please sir.

@WitDeJesse Haha, I'm only worried about people trying to improve on bitcoin. Do yo want to improve it? If not, I'm willing to verify your documentation and help out. Easy.

Dear bitcoin core developers, When cluster mempool is done, it would be great if we could have package relay for ancestor chains as well. This would help with unilaterally exiting a Spark a great deal.

@Du_Bi_Bo How can you guess so loudly? You don't know what you're talking about. I'm building a client-side Spark implementation. The problem I face is a real-world problem. It's open source. Read it. For example: btctranscripts.com/bitcoin-core-d…

@WitDeJesse I don't know where you got your info from. It's open source. Read it. It's open by design, but restrictive only when rules are not followed. No L2 is forbidden upfront. Make a TX, connect your L2 via OP_RETURN, by design for a little uncensored data. Do it correct: it just works.

@Du_Bi_Bo This request is about bitcoin core not relaying the transaction structure of such separate L2, even though it is perfectly consensus-valid and also incentive-compatible.

@WitDeJesse Bitcoin L1 does not need more features. You can build anything you want or need on a separate L2, merkle tree your hashes in OP_RETURN (32 bytes) to tie your L2 to the most secure network we invented without harming it. If your featured L2 is useful, it markets itself.

@Du_Bi_Bo Why would this feature allow for more centralization? If anything it would reduce centralization, right? If you cannot transmit a package over p2p, you would call a miner api directly instead. Mempool would look more like what miners want to mine too.

@WitDeJesse Worst idea ever. It's decentralised for many reasons. It would be another clusterf*ck. Bitcoin needs trimming of features that allow for more centralization. Abusing a fixed target is easy. I'm a thinking dev. You think like a lazy dev: 'please core devs...' DIY, FAAFO

🚨 Important: If you use the LN+ app within Umbrel, please delete it until further notice. I'm investigating a security incident related to the github repo for the Umbrel app. I will give an update soon. The web version of LN+ is not affected. CC: @umbrel

@callebtc I believe @lexeapp knows how to run the lightning node in an enclave.

Running mints in enclaves is funny and hard. It's like setting up the mint blindfolded. All key generation, storage, and setup happens inside. Keeping it running is a whole other challenge: database can't grow infinitely because you have no access to it, Lightning pure is basically impossible because of channel management, and Ecash keyset rotations etc must all happen fully automatic. It's like doing it all in full self driving mode while also being blind at the same time.

Huge progress update. We will soon have Cashu Ecash mints in secure enclaves that the mint operator can't steal the Bitcoin from, not can they inflate or manipulate the Ecash supply. The operator has no access to the private keys of the mint. This is amazing news for users and operators alike. It allows us to build tools for communities that allow them to run mints without being afraid of malicious actors, internally or externally, such as security threats from hackers. We're building this for the Bitcoin community first but we're planning to expand this also for local currency communities outside of the crypto space that exist in pockets all around the world. Especially the local currency tech stack is old and antiquated. We're going to give them the most advanced ecash protocol they could ever dream of. For free! Lots of moving parts here: servers, libraries, backend, wallets, and protocol extensions. Incredible work by the entire Cashu team.

Three days in Tuscany, invite-only, with the founders and decision-makers behind most of the companies building Bitcoin and Layer 2 solutions. The Tuscany Summit is quietly becoming the room you want to be in if you're serious about this industry.

@hack4_freedom One of the participants asked me whether I was not afraid of losing money when doing this on mainnet. I'm quite proud to say there's no way you'll lose anyone's money with Breez SDK as long as you have your mnemonic.

Decided to single prompt vibe code an app in the middle of a 1-hour workshop for @hack4_freedom. You can write a user-facing app handling money too in minutes using Breez SDK.

Another great @tuscanysummit ⚡️ We loved spending time with so many of the brightest builders in Bitcoin, sharing ideas and talking about what comes next. Now back to work. It’s time to build.

@growthlimits @w_s_bitcoin @_DannyKnowles @davidmarcus There's a private option now. If enabled, none of your payments or history are visible to anyone other than you or the operator. This is enabled by default in Breez SDK.

@w_s_bitcoin @_DannyKnowles @davidmarcus @WitDeJesse i believe we talked about this last year. I'm not sure if I remember the rational correct. Is what I said correct?

I wish @_DannyKnowles would’ve pushed back on this and asked why anyone can look up anyone else’s entire history if they’re using Wallet of Satoshi or the Tether wallet and their LNURL is known. @davidmarcus, any comment?

Our first annual report is out! 📄 2025, our inaugural year was full of progress, challenges and lessons learned. 🛠️ We believe in building in the open. This is our story so far. 📖 Read it here on our brand new substack: 2140blog.substack.com/p/our-first-an…

@callebtc Very nice

@WitDeJesse yep