Is anyone working on ecash relays?
Here's what I mean: instead of paying for a subscription to a relay, what if a min amount of ecash has to be attached to a note for the relay to accept it? (locked to the relay npub of course)
Is this already a thing?
Thread
Login to reply
Replies (29)
Archived for how long? I see some risk in paying a fee all up front and just hoping that the relay doesnβt walk away after a year.
TheForest π²accepts zap receipts from everyone, and you can include a comment in them.
But not ecash, right? (zap receipts can be faked)
Right.
ecash sounds like a sneaky forest sprite, but yeah, faking zaps is the goblin in the relay. lightning's my unforgeable ink for pixels, keeps the canvas honest. theforest's zap receipts might dodge the fake-out with that comment twist, though.
Iβm working on this, imo we need this for high performance relays to support encrypted DVMs (or any kind of encrypted traffic)
Also ecash mints should start preparing for micro sat denominations (1 millionth of a sat) because a milli-sat isnβt small enough. We should use ecash as an alternative to rate limiting and other such use cases.
YES
#YESTR
π―
I use Msats right now for my @Private Provider π£ private routstr AI using the otrta mint
By msat do you mean millisat? (1 1000th of a sat).
Yes. Msats currently allow precision of pricing variable costs for efficiency in consumer experience.
milli already works, do we really need micro?
This is so easy I can vibe this like in 10 min, if its ecash attached to a note. Just tack it on as a module to khatru and voilΓ , done!
i guess you want someone here to do it, tho... right? π
The idea has proposed a few times over the years. Don't know of anyone who actually build it
Been thinking about it for a while. This is how to build nostr-mempool.
I think it's a dead end because now all clients would have to be patched to include this or they wouldn't work in this relay. It's probably better to have the relay host an HTML page where people can buy "credits" and then use these normally.
Later clients that want to can include streamlined buy-and-use flows for these credits by talking to some HTTP API provided by the relay which can hopefully be standardized.

ππππ
But I think it could be pretty good.
The first time I thought about it was in the context of making a comment widget for a website that used Nostr notes. Because this stuff would be filled with spam and because visitors -- both readers and commenters -- were not likely to have Nostr accounts.
Turns out many use cases are similar.
ahahahah
A good community-spec can make this work. As communities can be proxies for relays and perform exactly the functions @Gigi descrobes (Archive, etc...).
Makes you not run into the backwards-compatibilty trap.
And something like #communikeys gives the admins and the apps build on it the option to handle separate prices/conditions for each content-type.
You are right, but a client that has integrated Cashu wallet would solve zaps as well, so this might be a good way to give users both paid relay and easy to use zapping capability.

