Oddbean new post about | logout
 
PPE Relay - a paid relay that accepts notes on a pay-per-event basis.

wss://ppe.swarmstr.com

Powered by khatru framework by nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprdmhxue69uhhyetvv9ujuam9wd6x2unwvf6xxtnrdakj7qgnwaehxw309amk7apww468smewdahx2tckuej4c

How it works?

- For storing an event, the relay charges 1 sat per single event.
- The amount is subtracted from the user's balance each time event is accepted.
- To top up your balance, simply zap any note from nostr:nprofile1qqsqsujjc4r3s683cn8nvda0m8s2z70elp65nml3lvcykqm39w8duucpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsjeeaj3 with the desired amount.
- Only kind 1 (note) and 30023 (long-form) events are accepted.
- To view your current balance, tag nostr:nprofile1qqsqsujjc4r3s683cn8nvda0m8s2z70elp65nml3lvcykqm39w8duucpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsjeeaj3 with "balance" command.

Repo: https://github.com/ptrio42/ppe-relay

Feedback/suggestions appreciated.

Note: This is an experimental phase so expect some bugs. 
 Your balance is 0 sats. 
 hey all y'all that have been clamoring for pay per note, nows your moment to shine ✨

nostr:nevent1qqsv2syzceype8flfdg0v5sszf7rccfmtzyuq5fmrmm69y5aclwdpsqpz9mhxue69uhkummnw3ezuamfdejj7q3q78umpxtdflcm7a08nexvs4mu384kx0ngg9w8ltm5eut6q7lcp0vqxpqqqqqqz9v92af 
 Pull request: name change to PPP:pay per post

I don't want a relay for personal protective equipment 
 Really I love this 
I write about this idea a days ago.
nostr:nevent1qqsv2syzceype8flfdg0v5sszf7rccfmtzyuq5fmrmm69y5aclwdpsqpzdmhxue69uhhwmm59e6hg7r09ehkuef0qgs0r7dsn9k5ludlwhneunxg2a7gn6mr8e5yzhrl4a6v79aq00uqhkqrqsqqqqqpme4v9e 
 Niiice! Glad to see it worked. Cheers for building it 🙌

@note1ckek32lspvl85jrvqqhl8vlhm7ymlw3puxg78ytz82s4hrwd432sw4cm7e 
 👀 
 Wild. Could this be used for someone to pay sats to get a note some widespread reach, coming from a burner npub?

Also makes me wonder if this could be the basis for an advertising model. 
 Thanks I will try this out. 
 🫡 
 RELAY เก็บตัง
nostr:nevent1qvzqqqqqqypzpu0ekzvk6nl3ha6708jvepthez0tvvlxss2u07hhfnch5palsz7cqqsv2syzceype8flfdg0v5sszf7rccfmtzyuq5fmrmm69y5aclwdpsqy6ce3q 
 NWC could be used too as an alternative to having to top up first. But zapping the bot is quite easy! 
 moar 
 Awesome!

I need this as a service: 
- for spinning up my own relay (+ blossom server)
- where I can set my own prices **per event kind** (and **per kb** if we're talking media) 
 Zaps are cool, but it would be nice to have an HTML page with a dumb form where we can request an invoice and pay. 
 What happens if I pay and then someone takes my notes from other relays and throws them into this? That will exhaust my credits? The solution is to require AUTH for publishing such that only you can publish your own notes to this relay. That's built into NIP-70 which is enabled by default on khatru, you just have to require all events to have the "-" tag. Then the question becomes about how to properly publish to this relay, and then we will need some specialized clients or some special relay view section within clients with tools for publishing relay-specific notes. 
 Right now when I browse wss://ppe.swarmstr.com/ (by the way, it's just one click on the relay URL to browse on Gossip now) I see a bunch of notes that are replies to other notes that are outside the relay.

But it would be cool to have something like a feed of notes that people paid to publish specifically to that relay, like a privileged billboard, I don't know. Maybe you could even reorder the feed such that highest paying notes are returned first instead of the most recent -- or ranked by a combination of newest+more expensive, I don't know. 
 Could there be a tag that is a 1 sat note (or whatever the charge to publish fee is?). That way the relay does not need to maintain any account. A wallet external to the relay can manage that. 
 You'd be AUTH'ing to publish a signed event, I don't see any issue there. 

Twitter-like clients are not a great fit for this UX.
Community clients are. #workingonit 
 maybe fee is for posting not necessarily for archive or retention - so no need expiry just uptime