The CIA invented Bitcoin, but lost control of it in the Blocksize War

How much inbound liquidity do you need? I don't expect I have enough on my little node, but that info might help others

Why are there two in Zapstore now? I think you explained this before, but I forget

bitcoin-calendar.org hasn't been responsive for at least the last few days

I've been using since September for 99% of my code, but I haven't really researched how to use it. For example, I don't really know what you mean by subagents So I guess I need to pause hacking (briefly!) and learn how others are using AI

Can't make it. Maybe #40c3

You're being too simplistic Shitting on those kinds of companies sounds similar to the way no-coiners shit on Bitcoin Saylor can borrow money on much better terms than most people can, so it makes sense for people to invest in MSTR

The extreme case of this could be very interesting for game theory, leading to just one notary getting a very large monopoly Imagine a single notary does a deal with all the big mining pools which together control 90% of hashrate That notary could advertise: "give me 10 sats and I'll notarise it as 50 sats". As they control 90% of hashrate, they will on average get 45 sats back from those 50, and hence the real cost to the notary is just 5 sats (on average) compared to the 10 sats that they earn from the creator of the nostr content With CSV, the delay is just about 15 months, and that's short enough that the big notary is happy to wait I think the only solution is to really make sure that today's miners don't see any value from the burning, so either notarizing to an OP_RETURN, or use CLTV to send it very far in the future , is this the right npub for Espen?: I think he had the same idea

Enjoyed this video, just trying to understand hash-based signatures. https://m.youtube.com/watch?v=T9fCCGzwHJc which I discovered via X: https://xcancel.com/willcl_ark/status/2003826095989359085 I read this pdf a few days ago, but didn't really get it 😜. But I think can try again and understand it much better thanks to the video above! https://xcancel.com/n1ckler/status/1998407064213704724

At my parent's place for Christmas, and going through a lot of old computer stuff I had stored there I guess my SCART cables aren't worth keeping any more

Just telling my parents now that I'm into bitcoin. They're more open than I expected Using cashu.me , I got my mum to pay a few sats to the Lightning Cats, and she loved it Now trying to get my dad to bet on sports at Predyx. None of our family are into gambling, but it's an easy way to spend a few sats Happy Cashu-mas everybody https://lightningcats.io/ predyx.com

I'm using Blossom to host videos, specifically using HLS so the video is split into many segments - of varying bitrate and quality - and so a 'dumb' HTTP file server like Blossom works perfectly All the complexity - e.g. adaptive bandwidth use - is client-side, but hls.js is an effective library to make it easy to develop In my use case, I'm developing a 'Cashu payment channel' which allows tiny Bitcoin payments at very high frequency and therefore a streaming video service where you pay per second is a good demo. (I feel like I may have misunderstood you a bit. What do you mean by 'formatted'?) https://hlsjs.video-dev.org/demo/

njal.la , by one of the founders of The Pirate Bay Has VPS hosting too Not super cheap, but I'm very happy with it

So you're saying that miners would delay the notarization transaction until the height specified in the CLTV, so that they can notarize and redeem in the same block Yes, they could in theory, and that would allow the cheating that we discussed before. But they're not going to delay the notarization transaction for decades, if we're sending it decades into the future The end users of the system (I mean the users of nostr clients who are consuming nostr events and want to see which events have burned sats associated with them) are looking for reliable notaries, i.e. notaries that get the notarizing transactions into blocks within hours or days (not years or decades). The end user's software could easily check that the notarization transaction is mined at least N blocks before whichever height is specified/implied by the CLTV or CSV locks