@Rizful.com Apologies, due to an error on our end inbound zaps to Rizful users were not working for about 30 minutes yesterday, and also for about 30 minutes today, during the last 30 minutes. The issue has now been resolved. Thanks for your patience.

... I have some geriatric ramblings to transmit. As follows: The "Graduated Wallet" for BTC, Lightning and Nostr. Elegant concept. Here it is: For the first, say, 100k satoshis that a user receives... The user is on Layer #1. On Layer #1, inbound payments are converted by an API provider like LightSpark, or Arkade, or Breez, or Boltz.... from Lightning..... to an L2 like Spark, or Ark, Liquid, or other fancy thing...... things continue on like this for a while.. but...... BUT.... at the point that the user gets above 100k satoshis... .... the user enters Layer #2. ..... ... The user then sees a button "Switch To Your Own Channel"..and the user's balance is converted into funds in a running instance of LDK on the user's phone. This LDK instance can open and close channels, send on-chain transactions, etc. Fully self-custodial and cool. Nice, right? Layer #1 | Spark, Ark, something like that. Layer #2 | LDK: Self-custodial and decentralized, without compromise. But. Here's the problem: Layer #1 has a dark side: Spark or Ark or (perish the thought), APIs like Breez, all involve depending on ONE trusted intermediary, to keep an API up-and-running. Also, these APIs are mutually incompatible! To support more than one would be insanely complicated! And, like, when LightSpark or Breez goes down, your user is fucked! Not cool. ... also....each Layer #1 depends on a SINGLE network endpoint. This is just dangerous in so many ways... fundamentally uncool.... and not something that bitcoiners should get involved with. So. POTENTIAL SOLUTION: 💡 What if, instead.. instead of Spark or Ark or Breez, a wallet simply allowed users to CHOOSE ANY NWC STRING -- and switch between those NWC strings at any time? 💡 Layer #1 | Multi-NWC-string switcher. Simple React component (or other easy UI.) Allows user to quickly switch between different NWC string. Simple. Decentralized. Highly convenient. Tested in production for 3+ years by orgs like Zeus, Alby, CoinOs, Wallet Of Satoshi, Megalith, Amboss, FlashSats, Rizful, MiniBits, Yakihonne, Primal, Damus, Amethyst, Coracle, and more... Fully featured for Lightning payments, balances, invoices, etc. Layer #2 | LDK: Self-custodial and decentralized, without compromise. Here is the simple scenario: At the time that the user's NWC balance reaches 100k, the user sees a simple button "Switch To Your Own Channel" -- which triggers a standards-compliant LSPS1 or LSPS2 channel opening, using a standard BOLT11 or BOLT12 invoice. The user's funds go into the channel... and at that point, the user has full control, with a full LDK instance, access to on-chain operations, etc. So....Why would you NOT, in 2026, just go with this? 💡 Layer #1 | Multi-NWC-string switcher. 💡 Layer #2 | LDK It's simple, it's tested, and it's decentralized.

Who else was awake from 2 AM to 4 AM PST because of the AWS outage? Fun!

Today marks DAY THIRTY of Rizful’s “30 Days, 30 Devs” initiative. From September 21st through October 20th, 2025, we highlighted one Nostr developer each day, and sent a zap of 100,000 sats to that developer. Today, by popular demand, we are zapping @balas , developer of the rather cool site:

alphaama

Thanks @balas ..... Your 100k zap is sent! -- Thanks for all of your suggestions over the last month..... There are dozens of awesome Nostr devs that we didn't get to in these 30 days, apologies to all, hopefully we will do this again soon and get to you!

@aljaz Can't zap you currently, "could not generate a lightning invoice for this project". Might be related to the AWS outage?

@balas Trying to zap you, getting "invalid lightning address". I wonder if WoS is down or something.

@ZapTok Trying this out. On desktop I see this on every page:

continued AWS problems: https://health.aws.amazon.com/health/status

Opening new channels with Megalith LSP is currently not possible due to the AWS outage impacting some of our infrastructure. Payments and other activity should not be impacted.

@Rizful.com is now back up. Considering about 1/2 the internet is down, we can't guarantee it will stay up, but it's looking OK right now.

@Rizful.com is currently down: https://news.google.com/search?q=aws%20outage -- It's 3 AM here so we're trying to get Bezos out of bed to deal with it, will report back shortly.

Yep, rizful.com is currently down, along with likely a huge portion of the internet, seems to be a large-scale AWS outage: https://health.aws.amazon.com/health/status

Today marks DAY TWENTY-NINE of Rizful’s “30 Days, 30 Devs” initiative. From September 21st through October 20th, 2025, we are highlighting one Nostr developer each day, and sending a zap of 100,000 sats to that developer. Today we are zapping @Cameri🐦‍🔥 .... creator of the NoStream relay.... Thanks @Cameri🐦‍🔥 ... Your 100k zap is sent! -- Please help us with the “30 Days, 30 Devs” initiative... simply reply to this note with the pubkeys of any devs you would like to see zapped. Don't be shy, we've got 30 days!

Today marks DAY TWENTY-EIGHT of Rizful’s “30 Days, 30 Devs” initiative. From September 21st through October 20th, 2025, we are highlighting one Nostr developer each day, and sending a zap of 100,000 sats to that developer. Today we are zapping @Russell ... author of many interesting Nostr projects at

GitHub

nogringo - Overview

Nostr enjoyer. nogringo has 47 repositories available. Follow their code on GitHub.

Thanks @Russell .... Your 100k zap is sent! -- Please help us with the “30 Days, 30 Devs” initiative... simply reply to this note with the pubkeys of any devs you would like to see zapped. Don't be shy, we've got 30 days!

@Cameri🐦‍🔥 small zaps work, probably you don't have enough inbound to get big zaps

@Cameri🐦‍🔥 tried to zap you, got "route not found"

Today marks DAY TWENTY-SEVEN of Rizful’s “30 Days, 30 Devs” initiative. From September 21st through October 20th, 2025, we are highlighting one Nostr developer each day, and sending a zap of 100,000 sats to that developer. Today we are zapping @BitBetBot .... actually, we have no idea who the developer of this is... but we want to highlight this project as 1) Simple 2) Fun 3) Potentially interesting for Normies 4) Uses NWC in a smart way Thanks @BitBetBot Your 100k zap is sent! -- Please help us with the “30 Days, 30 Devs” initiative... simply reply to this note with the pubkeys of any devs you would like to see zapped. Don't be shy, we've got 30 days!

Legit double standard.... a16z funding Lightspark: "Totally OK" Bitcoin VCs funding Lightspark: "WTF is wrong with you"

Today marks DAY TWENTY-SIX of Rizful’s “30 Days, 30 Devs” initiative. From September 21st through October 20th, 2025, we are highlighting one Nostr developer each day, and sending a zap of 100,000 sats to that developer. Today we are zapping @Jona , developer of various Nostr projects at

La Crypta

La Crypta is an Argentine organization dedicated to the development, education, and sharing of knowledge within the Bitcoin and Nostr ecosystems.

Thanks @Jona ... Your 100k zap is sent! -- Please help us with the “30 Days, 30 Devs” initiative... simply reply to this note with the pubkeys of any devs you would like to see zapped. Don't be shy, we've got 30 days!