<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <updated></updated>
  <generator>https://njump.me</generator>

  <title>Nostr notes by </title>
  <author>
    <name></name>
  </author>
  <link rel="self" type="application/atom+xml" href="https://njump.me/npub1k5x0dxvf6xmlfcdtzk9ln5mgae90kuxc27aecwv7f5efxhjk85ks6k0yhu.rss" />
  <link href="https://njump.me/npub1k5x0dxvf6xmlfcdtzk9ln5mgae90kuxc27aecwv7f5efxhjk85ks6k0yhu" />
  <id>https://njump.me/npub1k5x0dxvf6xmlfcdtzk9ln5mgae90kuxc27aecwv7f5efxhjk85ks6k0yhu</id>
  <icon></icon>
  <logo></logo>




  <entry>
    <id>https://njump.me/nevent1qqs99qmq9zdwxrgnmewf3wmwgekyy5fpmf0j4zn5xn8zreug9thal4szyz6sea5e38gm0a8p4v2ch7wndrhy47msmptmh8penexn9y672c7j6gwqn89</id>
    
      <title type="html">Thank you! The initial use-case to me is better wallets, ...</title>
    
    <link rel="alternate" href="https://njump.me/nevent1qqs99qmq9zdwxrgnmewf3wmwgekyy5fpmf0j4zn5xn8zreug9thal4szyz6sea5e38gm0a8p4v2ch7wndrhy47msmptmh8penexn9y672c7j6gwqn89" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsx7pwu30gfxs3s4rvu9cjsjlk88f0ql844q3uedw58kj63whdkeccu08ggl&#39;&gt;nevent1q…8ggl&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;Thank you!&lt;br/&gt;&lt;br/&gt;The initial use-case to me is better wallets, particularly for new or casual users that have historically been defaulted to WoS. Using of balances from Lightning enabled websites I see as an extension of that, to tie the whole Lightning experience together. This has actually been something we&amp;#39;ve seen need for from users of Lightning.Video&lt;br/&gt;&lt;br/&gt;The Lightning.Pub RPC uses Kind 21000, which is covered under the NIP01 definition of an ephemeral range. This allows it to work with existing relays, and as ephemeral events there&amp;#39;s actually not even a database requirement for the relay, making it extremely scalable.  &lt;br/&gt;&lt;br/&gt;Clients are actually autogenerated from a proto, so that the RPC can be used over REST as well.
    </content>
    <updated>2023-12-10T19:07:00Z</updated>
  </entry>

</feed>