Yes, we control the node. (BTW, many of the supposed "non-custodial" options, like Wallet Of Satotoshis "spark" wallet -- are in our opinion actually not "non-custodial" at all -- they're dependent on LightSpark not grabbing your funds...)

for full self-custody we recommend your own node like described here ( https://docs.megalithic.me/category/set-up-a-lightning-node ) -- or alby hub is good too!

vault stuff is explained here: https://docs.megalithic.me/category/using-rizfulcom

cheers!

Great, looks like you've set up a Lightning Address with Rizful. You're 1/2 of the way there! Please follow the tutorial for your Nostr app here to learn how to connect your app to Rizful: https://docs.megalithic.me/category/using-rizfulcom

Once you've finished, please ping us back here so we can try to zap you!

interesting test case! your granular data is below.... interesting that it was #3 where we saw the zap receipt... this can sometimes happen due flakiness on whatever server you have producing your zap receipts -- or could possibly be whatever relays you are sending zap receipts to... or could be something else...

Individual Zap Attempts:

1. Attempted at: 2025-12-28 04:52:07 UTC

LNURL: 1710ms

Callback/Invoice Generate: 1040ms

Attempt ➡ Lightning Confirmation: 2602ms

Lightning Confirmation ➡ Zap Receipt: N/A

---

2. Attempted at: 2025-12-28 05:49:51 UTC

LNURL: 1605ms

Callback/Invoice Generate: 1071ms

Attempt ➡ Lightning Confirmation: 1058ms

Lightning Confirmation ➡ Zap Receipt: N/A

---

3. Attempted at: 2025-12-28 06:38:14 UTC

LNURL: 552ms

Callback/Invoice Generate: 921ms

Attempt ➡ Lightning Confirmation: 5153ms

Lightning Confirmation ➡ Zap Receipt: 4049ms

---

4. Attempted at: 2025-12-28 07:01:14 UTC

LNURL: 1794ms

Callback/Invoice Generate: 1083ms

Attempt ➡ Lightning Confirmation: 1038ms

Lightning Confirmation ➡ Zap Receipt: N/A

---

5. Attempted at: 2025-12-28 07:36:26 UTC

LNURL: 1929ms

Callback/Invoice Generate: 1100ms

Attempt ➡ Lightning Confirmation: 1171ms

Lightning Confirmation ➡ Zap Receipt: N/A

---

6. Attempted at: 2025-12-28 08:18:20 UTC

LNURL: 547ms

Callback/Invoice Generate: 1074ms

Attempt ➡ Lightning Confirmation: 1013ms

Lightning Confirmation ➡ Zap Receipt: N/A

---

So far, the number of Rizful users who have contacted us and said "I've lost access to my Rizful node or vault, can you help me get back in?".... is zero. ZERO.

Why? Because to make a Rizful account, you need to provide an email address, and confirm that email address.

If we start allowing nostr-only sign-in, without an email backup, this number will start going up fast, and we won't be able to help these users, because all we have is their nostr public key.

I just don't understand how you can offer something that can store real funds and NOT provide some way to "recover" access.... an email address is a very useful and well-established way to allow someone to reset their password....

It depends what you are working on. If you are working on Bitcoin, I think you can't touch 95% of that stuff because of the risks involved. You have to know what every line of your code does.

But yes, for websites and apps, this is probably true. But not the parts that touch BTC or Lightning.

Do any Rizful users have suggestions for features to add to Rizful that would be useful, for our 2026 roadmap? Thanks!

just tried manually in jumble.social "invalid zap request" .. pls ask some others to try to zap you

Bypass Gemini's SynthID watermark: https://github.com/00quebec/Synthid-Bypass

looks like you have not set you lightning address so we can't zap you

ok good, so u are trying to set your nip 05 to a rizful address right?

if you go through each of these steps... https://docs.megalithic.me/using-rizful/use-primal .. it should all work.. pls let us know thanks

Great, looks like you've set up a Lightning Address with Rizful. You're 1/2 of the way there! Please follow the tutorial for your Nostr app here to learn how to connect your app to Rizful: https://docs.megalithic.me/category/using-rizfulcom

Once you've finished, please ping us back here so we can try to zap you!

Great, looks like you've set up a Lightning Address with Rizful. You're 1/2 of the way there! Please follow the tutorial for your Nostr app here to learn how to connect your app to Rizful: https://docs.megalithic.me/category/using-rizfulcom

Once you've finished, please ping us back here so we can try to zap you!

nostr:npub1v60thnx0gz0wq3n6xdnq46y069l9x70xgmjp6lprdl6fv0eux6mqgjj4rp Hi, do you run the Lightning Node "⚡Lightning Goats CLN⚡" ? If so, when you get a chance you could you please drop us a line by Signal or Telegram, here: https://megalithic.me/contact .. thanks

Great, looks like you've set up a Lightning Address with Rizful. You're 1/2 of the way there! Please follow the tutorial for your Nostr app here to learn how to connect your app to Rizful: https://docs.megalithic.me/category/using-rizfulcom

Once you've finished, please ping us back here so we can try to zap you!

looks like you are set up correctly now!

Hi, looks like you have not yet updated your lightning address

Please see tutorials here: https://docs.megalithic.me/category/using-rizfulcom

Happy to help you troubleshoot if you can find a reproducible error.

90% sure that if the receiver switched to a nostr:npub1jluy3twvf338v6zlujzzdhjkzjy8ezj34ksydr8vw8a6jwp89ygshpp2kq address it would work. My memory is that this is some specific issue with the interaction between anmythest and primal.

hi, can you please get us on telegram or signal so we can help you troubleshoot: https://megalithic.me/contact

. https://www.compactmag.com/article/the-lost-generation/ This is pretty interesting. I think ironically what he is describing is a world where white men are getting a huge advantage because they are being told immediately after college that they should not attempt to become academics or screenwriters or journalists. Everyone else isn’t told this and is going to suffer horribly if they make a decision to do one of these things.

"can’t get the zapping function to work across clients" -- just to be clear, each client needs to be set up separately with an NWC string.. so u could follow the relevant tutorial for each client... https://docs.megalithic.me/category/using-rizfulcom

These might be helpful. https://docs.megalithic.me/category/using-rizfulcom

I read this message twice and I think understand about 20% of what you wrote. if you have any specific test cases that involve Rizful and that are failing, if you could lay them out in extreme detail, like exactly what steps you take to reach the failure, then we would like to try to reproduce them.

Thanks. This looks to be specific to some kind of interaction between Amythest and Primal.. you can see it is failing at the "callback" stage of the zap, which is before Rizful gets involved... also, I just tried zapping @profk from Yakihonne and Jumble.social on the web, and it succeeded both times... this also points to some kind of Amythest/Primal Wallet issue.

Is this a Damus issue or a Rizful issue? If it’s Rizful, can u please try to zap from yakihonne and if there is a user who u consistently cannot zap, would you please provide the profile link to this user here? Thanks.

nostr:npub1mtuzjsdkc6c9ydac0am4dkdefcfszsr3cjx3kly5t4zasq626zhqpvvxl7 nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 Oh, it's this issue: https://github.com/damus-io/damus/issues/3262

Seems like it's not fixed yet, it's only 2 months old so if you inquire with Damus they might fix it and include it in the next release.

I know it's this issue because it's indicated here:

Failed to decode NWC Wallet response JSON. Error: typeMismatch(damus.WalletConnect.Response.Result.ResultType, Swift.DecodingError.Context(codingPath: [], debugDescription: "result_type get_info is unknown", underlyingError: nil))

nostr:npub1mtuzjsdkc6c9ydac0am4dkdefcfszsr3cjx3kly5t4zasq626zhqpvvxl7 you could also try with Yakihonne, which doesn't show any error messages when using Rizful NWC.

nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 did something change recently with Damus NWC implementation? I'm seeing this error also with a Rizful NWC code... also finding that the Copy Technical Information button isn't working as far as I can tell

Today marks DAY FOUR of the "Rizful 300" awards initiative.

Each day, starting October 30th 2025, we are highlighting 10 Nostr OGs, and sending each a zap of 10,000 sats, for a total of 3,000,000 satoshis, over 30 days.

Today's "Rizful 300" award winners are: nostr:nprofile1qqsd9pqnwyshrse7z975h5ynptq9ktz3kv8txqs7lr20zgelqtys52cpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq32amnwvaz7tmsw4e8qmr9wfjkccte9e3k7mgpzemhxue69uhkymmnw3ezuumeda3x7m3wdejhgqguwaehxw309ahx7um5wgknqvfw09skk6tgdahxuefwvdhk6qgkwaehxw309aex2mrp0yhxummnw3ezucnpdejqzrthwden5te0dehhxtnvdakqz9thwden5te0v4jx2m3wdehhxarj9ekxzmnyqyg8wumn8ghj7mn0wd68ytnhd9hx2pysqjp, nostr:nprofile1qqs0yadtxlty76lqx7dgtnjhxcrqu9jtzd4q33l3u7x75ce6htvyhlsprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqy2hwumn8ghj7etyv4hzumn0wd68ytnvv9hxgqg5waehxw309amk7apwva5hy6twduhx7un8qyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqpr3mhxue69uhkymmnw3ezucnfw33k76tww3ux76m09e3k7mgpzpmhxue69uhkummnw3ezumrpdejqzxrhwden5te0wajkccm0d4jjumn0wd68ytnhd9hx2qgkwaehxw309aex2mrp0yhxummn9eek7cmfv9kqwds0lt, nostr:nprofile1qqsd5xd462g7qmksnwj5t0znveqgmjpt4ry7n7taxt4gafs0raktl2spr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qyt8wumn8ghj7cn0wd68ytnn09hkymmw9ehx2aqpz4mhxue69uhkummnw3ezummcw3ezuer9wchsz9nhwden5te0wfjkccte9ehx7um5wghxyctwvsq3wamnwvaz7tmjv4kxz7fwd3jhgumxduhxxmmd9uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uq3camnwvaz7tmwdaehgu3dxqcju7tpdd5ksmmwdejjucm0d56vqtu0, nostr:nprofile1qqsqdqc0dj6eyk7c9n99n0dgfrcq2enxmlcyd3fc9936n9azxndyp3gpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgmwaehxw309aex2mrp0yhxummnw3ex7mt09eek7cmfv9kqzgrhwden5te0wfjkccte9ekx27rfdenhgmmwvf5hgcm0d9hzummjvuq32amnwvaz7tm9v3jkutnwdaehgu3wd3skueqpyfmhxue69uhkummnw3ez6an9wf5kv6t9vsh8wetvd3hhyer9wghxuet5qyw8wumn8ghj7mn0wd68yttkv4exje3wwdkx7arg0yh8w6twqyf8wumn8ghj7mmxve3ksctfdch8qatzqy2hwumn8ghj7un9d3shjtnwdaehgu3wwejhg8dp6wl, nostr:nprofile1qqsw2gmsywjupy570tsw2y5dgx5zzvfcgq8vzyxma8v29ync7g4hcycpr3mhxue69uhkymmnw3ezucnfw33k76tww3ux76m09e3k7mgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg0waehxw309ahx7um5wghx6mmdqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsz9nhwden5te0wfjkccte9ehx7uewwdhkx6tpdsq3vamnwvaz7tmzdaehgu3wwduk7cn0dchxuet5qyg8wumn8ghj7cn0wd68ytnndphhqqgmwaehxw309aex2mrp0yhxx6rpddsku7fwwduhxar9d4esa7l2vd, nostr:nprofile1qqsptpha27kgrdnpw7cqs7ascrayvheshxy4jjwgjd5rdmz7dngnzvspzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg5waehxw309aex2mrp0yhxummnw3ezucn8qyt8wumn8ghj7un9d3shjtnwdaejuum0vd5kzmqpp3mhxue69uhkyunz9e5k7qg0waehxw309ahx7um5wghx6mmdqy2hwumn8ghj7ur4wfcxcetjv4kxz7fwvdhk6qgswaehxw309ahx7um5wgh8w6twv5q3vamnwvaz7tmjv4kxz7fwdehhxarj9e5kuen0wk6yzx, nostr:nprofile1qqspgz966pym4w9r3wtkqad0leqncdfph0h0vtxyec6422vlf9cl9jspzpmhxue69uhkymmnw3ezuumgdacqz8rhwden5te0dehhxarj95crztnev94kj6r0dehx2tnrdakszgnhwden5te0dehhxarj94mx2unfve5k2epwwajkcmr0wfjx2u3wdejhgqgdwaehxw309ahx7uewd3hkcqgkwaehxw309aex2mrp0yhxummnw3ezucnpdejqz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqprpmhxue69uhhyetvv9uju6nddahhxefwwfhkx6mnnppg8j, nostr:nprofile1qqsfepkhw5m6vwqvudc78fyxp0r7r7e2mwegyxl34rcu6n5vuq3ypjgprdmhxue69uhhyetvv9ujucmgv94kzmne9eehjum5v4khxqg7waehxw309anx2etywvhxummnw3ezucnpdejz7ur0wp6kcctjqyw8wumn8ghj7mn0wd68yttsw43zuum9d45hxmmv9ejx2a30qydhwumn8ghj7mn0wd68ytn0wfskuem9wp5kcmpwv3jhvtcprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszgmhwden5te0dehhxarj94mx2unfve5k2epwwajkcmr0wfjx2u3wdejhgtcprdmhxue69uhhyetvv9ujummjv9hxwetsd9kxctnyv4mz7qgkwaehxw309a3x7um5wgh8x7t0vfhkutnwv46qpf2k8z, nostr:nprofile1qqs07t6v67rwg26ryd6fey230mrm4u3dl5p4k7ssr04g8dhzhjav69gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsq35amnwvaz7tmjv4kxz7fwd45ku6tzdak8gtnfdenx7tcpr3mhxue69uhkummnw3ez6vp39eukz6mfdphkumn99e3k7mgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgewaehxw309aex2mrp0yh8wetvd3hhyer9wghxuet5qyt8wumn8ghj7cn0wd68ytnn09hkymmw9ehx2aqpydmhxue69uhkummnw3ez6an9wf5kv6t9vsh8wetvd3hhyer9wghxuet59u797rpa, and nostr:nprofile1qqsr88dk9jgu3nag7zzl38c3tuddjh03pnn5jucz8xmq2nfy2vejjzqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3uamnwvaz7tmzdaehgu3wd35kw6r5de5kuemnwphhyefwvdhk6qguwaehxw309a3x7um5wghxy6t5vdhkjmn50phkkmewvdhk6qgmwaehxw309aex2mrp0yhxx6rpddsku7fwwduhxar9d4esz9rhwden5te0wfjkccte9ehx7um5wghxyecpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qzxnhwden5te0wfjkccte9ehx7um5wfcxcetzwvhxxmmdqythwumn8ghj7enfd36x2u3wdehhxarj9emkjmn9yt99qj

Thank you all for your service to Nostr!

Around minute 40 there is a great discussion of “auditability vs privacy” tradeoffs: https://fountain.fm/episode/1FaKA0B4a6wSn7fITcOn

...... something I hadn't fully conceptualized, but when it's explained like this, makes a lot of sense. Basically the L1 can't be fully private if you want anyone with limited storage and compute power to be able to audit it.

Privacy is a good job for L2, which is yet another great reason we should resist bad actors trying to centralize L2s like Lightning.

Today marks DAY TWENTY 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 nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk , developer of the https://iris.to/ client

Thanks nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk 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!

Not only public -- but Lightspark has the IP address and user-agent of this user, which they can granularly associate with each transaction. Crazy.

oh, trying this now, I think actually the button overflow is only happening because of the emulator.... I saw it also in the emulator when I switched to Pixel 7, but then if I refresh the page it seems to be ok

Always fun to spend the period between 2 AM and 4 AM PST debugging Lightning issues.

Great, looks like you've set up a Lightning Address with Rizful. You're 1/2 of the way there! Please follow the tutorial for your Nostr app here to learn how to connect your app to Rizful: https://docs.megalithic.me/category/using-rizfulcom

Once you've finished, please ping us back here so we can try to zap you!

Looking at the spec and our implementation.

Starting from here --

https://github.com/nostr-protocol/nips/blob/master/47.md#nostr-wallet-connect-uri

"The wallet service generates this connection URI with protocol nostr+walletconnect:// and base path its 32-byte hex-encoded pubkey, which SHOULD be unique per client connection."

So our understanding is that for each NWC connection (a user or wallet can have multiple of these), we generate a new, arbitrary nostr npub/sec pair for the NWC connection.

This pubkey doesn't match any other pubkey -- either of the user or as the service "as a whole".

Therefore, the pubkey you get from the "get_info" response is not really useful information and can be ignored.

It would be great if nostr:npub1zk6u7mxlflguqteghn8q7xtu47hyerruv6379c36l8lxzzr4x90q0gl6ef or nostr:npub19hg5pj5qmd3teumh6ld7drfz49d65sw3n3d5jud8sgz27avkq5dqm7yv9p nostr:npub1wl3cs46hek62jm4j3x3k5etut3dkghlqfq6satsxa8q5s3tngcps22kjnr can look at my explanation above, and tell me if I am wrong.

This is what I got to by clicking the Source link on the upper right of https://web.nostr.technology/components/nostr-name

The other issue is this -- I am technically savvy, and when I FIRST joined Nostr, I mistakenly set up multiple separate private keys on different apps, and got fully confused, and then had to start over again.

If I had started my journey by ALSO locking my satoshis to the first private key I ever generated... I would have been very sad.

Sure, I will agree, for technically savvy users -- developers, etc., that a private key might be a better approach.

The issue is Normies -- people who have never touched a private key, and don't really even have "a place to put it".

The issue isn't just "security" -- the real issue is "I have this account with sats somewhere and I can't remember what the website is called or how I get back to it or what my password is." This is EXTREMELY common. Everyone knows the solution to this is to search their email for the right keyword and BAM -- there is the confirmation email from the service. Then you go to the service, do a "password reset" -- and you are back in.

If the user has not enabled 2FA, then you are completely right, a user can be hacked by someone gaining control of their email.

But I submit to you that this is not the usual problem. The usual problem is "how do i get back to the website where my sats are stored, I can't even remember the name of it."

I expect that 75% of Nostr developers and Linux users will vehemently disagree with me on this issue.

Planets are known scam and an obvious front for the real activity we know is going on in our solar system. Please be cautious with ANYONE who tries to get you involved in any planet-related activity.

nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac The more you talk smack about nostr:npub1jluy3twvf338v6zlujzzdhjkzjy8ezj34ksydr8vw8a6jwp89ygshpp2kq , the more BTC goes up. Thank you for your service.