Category: hosted Lightning wallet service / Nostr Wallet Connect payment control plane / Nostr-onboarding infrastructure
Summary: Rizful is best cataloged as a hosted Lightning wallet and Nostr Wallet Connect control plane rather than as a simple Nostr zapping wallet or beginner tip jar. In this pass, the clearest first-party evidence came from the official site, the Rizful onboarding guides in Megalith Lightning Docs, the receive-only NWC guide, and the Rails integration guide. Together those materials describe a hosted Lightning wallet that gives users a branded @rizful.com Lightning address, helps them connect Nostr clients for zap-based social payments, and exposes NWC connection strings—including receive-only codes that can safely be handed to untrusted apps for checkout and payment-receive workflows. The key distinction is that Rizful is packaging a hosted wallet-and-integration layer for Lightning and Nostr applications rather than only offering a consumer wallet front end.
What it does:
Provides hosted Lightning wallet accounts with user-chosen @rizful.com Lightning addresses for receiving sats and Nostr zaps
Onboards users into Lightning and Nostr by documenting account setup, Lightning-address selection, and client connections for apps like Jumble, YakiHonne, Primal, Damus, Alby, and Amethyst
Exposes Nostr Wallet Connect (NWC) connection strings, including receive-only codes that can accept payments without granting spend authority
Encourages use of receive-only NWC codes in e-commerce, gaming, social, and other app integrations where a service only needs to receive Lightning payments
Supports server-side developer integrations where applications create invoices and subscribe to payment notifications through NWC without running their own Lightning node
Emphasizes conventional account security with email/password and optional two-factor authentication instead of asking users to log into the wallet itself with their Nostr private key
Key claims:
The homepage says Rizful was designed for security, does not allow login via Nostr, does not ask for a user’s Nostr private key, and instead relies on email/password plus optional two-factor authentication
The “Rizful First Steps” guide says Rizful is the easiest way to get started with Lightning payments and Nostr zaps
That same onboarding guide walks users through choosing a Lightning address, connecting Nostr clients, and even requesting a test zap, which makes the product look like an onboarding and wallet-control surface rather than just a static receive address
The read-only NWC guide says a receive-only NWC code is safe to share with untrusted apps because it can receive payments but cannot send them
The read-only guide explicitly lists e-commerce platforms, gaming platforms, and social zap receivers as intended downstream uses for Rizful’s NWC connectivity
The Rails integration guide says Rizful is a hosted Lightning wallet that exposes an NWC API, and it emphasizes that developers can create invoices and react to payments without running a Lightning node or payment processor
The same Rails guide argues that NWC reduces vendor lock-in because a developer can swap Rizful for Alby Hub or a self-hosted node by changing one environment variable, which reinforces that Rizful is operating at the open-standard wallet-service layer rather than inventing a closed proprietary integration model
Whitepaper: No canonical standalone Rizful whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site and the first-party Megalith Lightning Docs covering onboarding, NWC permissions, and server-side checkout integration; see ../whitepapers/rizful-primary-sources-2026-05-03.md.