Avatar
RawBTC
df94169263fec6182c66e54b63a8e3a1a5f060b742c4512764aee2fe55fc0191
Unchained QA Engineer. Honolulu BitDevs host.

mcp_agent_mail + nostr relay = networked local and remote agents 🤔

https://github.com/Dicklesworthstone/mcp_agent_mail

Now it's just going to be a constant stream of "Can you add my shitcoin to the crypto reserve next, Trump?" Because we're apparently opening that can of worms and de-legitimizing BTC as the only viable reserve asset, there's no reasonable line to draw now.

The grifters will keep grifting because that's the only chance they have to get rich off meme coins. A constant stream of weak-willed justifications for how PoopCoin is basically the same as Solana, which is basically the same as Ethereum. And they're basically right.

Everything could have been so much simpler if we'd just stuck to common sense principles and formed a BTC-only reserve. 🤷‍♂️ I guess nation states will have to touch the stove like everyone else, but I hate that my tax dollars are funding it.

https://www.nobsbitcoin.com/president-trump-confirms-strategic-crypto-reserve-with-bitcoin-and-altcoins/

I waited too long to buy into the Red Rising hype. Great series so far.

nostr:npub1yfg0d955c2jrj2080ew7pa4xrtj7x7s7umt28wh0zurwmxgpyj9shwv6vg is probably the best music-focused UX for more decentralized distribution/payment.

I appreciate that @RabbitHoleRecap + No Agenda cover all the news I need to care about.

For custodial, River or Strike can serve this purpose better than Coinbase. You don't have to leave funds with the custodian for long but can instead use them as a pretty seamless "swap" service to get in/out of Lightning.

For non-custodial, Aqua is probably the simplest. Requires a couple steps because you have to peg in or out between Liquid <> on-chain BTC. Funds at rest are L-BTC, but you can pay Lightning invoices, which happen via a Boltz swap under the hood.

Blockstream's Green wallet also makes it pretty easy to receive on-chain BTC to automatically open new channels and enable LN payments.

The squirrel shifted the timeline back.

Banana chips in coconut oil sound bomb. Will have to try that. Maybe with a little cinnamon sprinkled on top

I don't have any ad/marketing graphics on hand for a meetup like that, but if you're trying to build a presentation of some sort, I think these resources are pretty good. Might be able to pull some useful stuff.

nostr:npub14hn6p34vegy4ckeklz8jq93mendym9asw8z2ej87x2wuwf8werasc6a32x has some of the best graphics, so check these out:

https://anilsaidso.gumroad.com/

There are also some good graphics, points, and charts in this Fidelity report:

https://fwc.widen.net/s/fkvbv7ph9k/fidelity-digital-assets---revisiting-persisting-bitcoin-criticisms

If you're looking for quick bullet points refuting various FUD lines, this website is pretty good:

https://safehodl.github.io/failure/

Learn Me A Bitcoin also has some nice beginner graphics/diagrams:

https://learnmeabitcoin.com/beginners/

I'm organizing a bitcoin-focused panel discussion at the Honolulu Tech Week conference in mid-September (https://www.honolulutechweek.com) and am looking for 2-3 more bitcoiners to participate.

This will be a great opportunity to expose people to the #bitcoin rabbit hole and inspire them to start adopting it in their daily lives.

If you or someone you know might be interested, please shoot me a DM!

After listening to nostr:npub1dtgg8yk3h23ldlm6jsy79tz723p4sun9mz62tqwxqe7c363szkzqm8up6m and nostr:npub1guh5grefa7vkay4ps6udxg8lrqxg2kgr3qh9n4gduxut64nfxq0q9y6hjy on TFTC, I can't wait for a copy of nostr:npub1zf8p8cdg67hhx46wvdm96yd2jc9z3hen5nf606edwhv26ummf4vssf7888.

We need more second-order #bitcoin content like this. Yes, bitcoin is going to make us all rich, but then what? Today's hodlers have a massive responsibility to reshape the future and be stewards of the virtues we want to see in the world.

I'd love to get one of these or some battle ropes, but I need the space for it first.

I've honestly had a lot of issues with it. I want to like it because I like the roadmap and ethos, but I have payments fail all the time, the fedimint integration hasn't worked once for me, routes constantly fail for the LN Address, etc. I pay for Mutiny+ to support development, but Zeus is my daily driver to self-custodial LN right now. Just works more reliably for me.

I was trying to test out Mutiny's LN address, but I guess it's not working. Swapped to a different one, so I think it'll work now.

meat sweats🫃

* nostr:npub1cwneqlnjgs3rdtk97c2ffy2df9dm5zycgj3dsg8c3z00hchxjmfqtvraju

If you go the BTCPay route, I'd probably do it through nostr:npub15klkdfx9sh3y096a5jf895rcvkmkzvly2fm9dgxq6huqhp9576jsav4m73 to reduce a lot of the friction.

The Feds don't want you to know this, but you can just add scrambled eggs to whatever meal you want. It doesn't have to belong.

Japan was beautiful

Replying to Avatar Mal Gifson

+1 on Arc. Mobile and desktop are great. The summarize and "browse for me" features are actually really useful.

Replying to Avatar Gigi

I'm really excited about this. Blossom is deceivingly simple, which is why it is powerful and why it has a chance of working.

What #nostr got right (and Bitcoin, for that matter) is that duplication is a feature, not a bug. "It takes advantage of the nature of information being easy to spread but hard to stifle," to quote Satoshi. De-duplication is a fools' errand, as it assumes a God's-eye-view. A global state is required to properly understand what to delete and what to keep. The second problem is of course indexing and discovery, which is indeed a hard problem if a global state is to be avoided. It's hard, but solvable. Especially if you already know what you're looking for, and especially especially if you have a common and purple-coloured discoverability layer.

Blossom is basically copying what nostr did for notes and applies it to arbitrary files. Instead of relays handling events, there's simple HTTP servers handling files. Like relays, servers are interchangeable as they share the same interface, encouraging duplication and redundancy. Instead of uploading something to a single server, you might upload it to five different servers. Popular and/or important files will be on many servers, which is how the online world works today already. Files that you need often might even be served by a #blossom server that is geographically close to you, just like we now have local cache relays packaged with some clients (or that you can self-host on your home server).

In the best case, Blossom will organically mirror what YouTube et al's content delivery networks already do well today, which is to provide file hosting that is high in availability and proximity. The neat thing about it all is that you can provide monetary incentives as it is nostr-native, and you get web-of-trust characteristics for free, as you can use only your servers, or those who are trusted by your friends, etc. And in the future, we'll probably have paid servers that whitelist npubs, just like we have paid relays now.

So why is all of that awesome? Well, here's the thing: as the user, you actually don't care where a file is hosted; you just care about the file itself. The current iteration of image (and other) hosts is incredibly stupid. Images are uploaded, downloaded, and re-uploaded without end, often with massive loss-of-quality as the same image is compressed and re-compressed a hundred times. It's always the same image, or at least it *should* be. With Blossom, it actually is.

Gone are the days of finding a thing and uploading again. You just need the hash, and the thing will appear. You could even insert images directly in notes with something like a blossom:ef1c26172f55017c9d9d6afa7cf22605b237b0fe92425e81e3b5e24d46c95448 and each client can choose how (HTTP, torrent, I2P, etc.) and where (public servers, private servers, etc.) to retrieve it from.

But wait, there's more. Remember the monetary incentives we talked about? It is what allows for the emergence of a proverbial "assassination market" for files: you provide the hash, along with a bounty of 21k sats to anyone who can provide the file most readily. Servers could provide cryptographic proof that they have the file, and you could escrow the money until delivery is done and you verify the file on your side. The building blocks are already there, we just need to put them together in the right way.

Blossom is one of the most exciting projects that came out of the first nostr:npub1s0veng2gvfwr62acrxhnqexq76sj6ldg3a5t935jy8e6w3shr5vsnwrmq5 cohort, aka #SEC-01. I'll have more to say about all the other amazing #SovEng projects that came out of the discussions and collaborations we had, but now I'll have to go and upload some files.

nostr:nevent1qqs9pgpsdel6ejqrh4nrlj6p8j0d09w0frlhhuyajfy3wn8ugzzfjfgpzpmhxue69uhkummnw3ezuamfdejsygpxdq27pjfppharynrvhg6h8v2taeya5ssf49zkl9yyu5gxe4qg55psgqqqqqqst9390z

Great explanation. Thanks for demystifying it a bit.