nostrrecap on Nostr: ================== 🌱 Ecosystem Growth ================== Nostr is growing fast! ...
==================
🌱 Ecosystem Growth
==================
Nostr is growing fast! There are now over 45 Nostr clients, and relays are running in more than 40 countries around the globe.
According to https://nostrapps.com, there are overall 75 Nostr apps for now.
During this week:
Total zaps: 56,298, compared to 68,468 zaps the week before
- Total zap amount: 9,890,973, compared to 12,329,801 sats the week before
Note: You can see some inconsistency with comparing this recap with the last few recaps’ total zap amounts. The reason is that zaps to Primal wallets were considered "invalid" by brugeman (npub1xdt…ntxy) code, and when the issue was pointed out they decided to relax their code. So all numbers were adjusted to include Primal zaps too.
More info:
Total events: 5,052,189, compared to 5,768,028 events the week before
Many thanks to https://stats.nostr.band/ by brugeman (npub1xdt…ntxy) for providing these insights.
🌱 Ecosystem Growth
==================
Nostr is growing fast! There are now over 45 Nostr clients, and relays are running in more than 40 countries around the globe.
According to https://nostrapps.com, there are overall 75 Nostr apps for now.
During this week:
Total zaps: 56,298, compared to 68,468 zaps the week before
- Total zap amount: 9,890,973, compared to 12,329,801 sats the week before
Note: You can see some inconsistency with comparing this recap with the last few recaps’ total zap amounts. The reason is that zaps to Primal wallets were considered "invalid" by brugeman (npub1xdt…ntxy) code, and when the issue was pointed out they decided to relax their code. So all numbers were adjusted to include Primal zaps too.
More info:
quoting nevent1q…hvyzSeems like LN invoices included by Primal in zap receipts have empty payment_hash field. The invoice parser I use discards those invoices as invalid. I guess I'll have to patch it, as this is an optional field for zap verification purposes - they generate a proper invoice for the actual payment.
They also strip the description/commit hash from the invoice in zap receipts, which seems to go against nip57: "SHA256(description) MUST match the description hash in the bolt11 invoice." It looks like I will have to strip this verification logic on my end since in practice many wallets violate nip57 anyway and everyone is just trusting the wallets.
cc miljan (nprofile…u6d7)
Total events: 5,052,189, compared to 5,768,028 events the week before
Many thanks to https://stats.nostr.band/ by brugeman (npub1xdt…ntxy) for providing these insights.