Event JSON
{
"id": "3a84c7e1fe5fbdb1db0f29a682cf2826f93c6b7b64d32c4e15f6178b2816d511",
"pubkey": "3356de61b39647931ce8b2140b2bab837e0810c0ef515bbe92de0248040b8bdd",
"created_at": 1673284915,
"kind": 1,
"tags": [
[
"p",
"8c0da4862130283ff9e67d889df264177a508974e2feb96de139804ea66d6168",
"wss://relay.realsearch.cc"
],
[
"p",
"46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d",
"wss://relay.realsearch.cc"
],
[
"p",
"52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd",
"wss://nostr-pub.wellorder.net"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245",
"wss://relay.realsearch.cc"
],
[
"e",
"db1cb9e77fab98fa1d0370fa86bed52efc96d7d845bf61fef069f6307f297673",
"wss://nostr-pub.wellorder.net",
"root"
],
[
"e",
"e8172f065da95e9e3584802f19deec24014d80a21a86a8f1200e78eda2b98ee5",
"wss://nostr-pub.semisol.dev",
"reply"
]
],
"content": "I think every relay should protect itself, thus require a payment, even for reads. Having a trusted token issuer is just a return to what we had before nostr, IMO.\n\nHow clients make this user-friendly is another problem - #[3] already talks about adding a custodial wallet to Damus for tips, so streaming some portion of those sats to relays seems doable. On the web, getAlby with pre-set budget could in theory achieve roughly the same seamless experience.\n\nAlso we could start with per-relay monthly subscriptions - your client checks your relay list, requests monthly subs invoices from each relay, confirms with the user, pays, and uses the tokens issued by each relay in return for the payment. \n\nWhat do you think?",
"sig": "a62c22373fee4496242b95e35990ac44e397190af66da7385a6889b21147aae271a59f78045dd0eaa7de99c1b117118f6c52dd58782402f52484639fda81469c"
}