I don’t have more than lots of observation, however I don’t think blastr reliability hits more than around 30-50 relays total. Often less.

The 300 numbers gets thrown around a lot, however I suspect the relays being offline/shutdown, rate limiting, now requiring payment, Ip blocking, or whatever else (without stateful retry publishing on failure) doesn’t match the common outcome.

I think generally relay payment support is developing along side - but we have limitations in client UI, subscription payments, being lightning only, etc. I don’t think we even have solid open source relay payment gateways that track pubkeys days until expiry or whatever.

Reply to this note

Please Login to reply.

Discussion

It's a lot to develop but I think this should happen rather sooner than later as now a lot of resources is going int defining arbitrary limits leading to good and bad actors working around those limits in a cycle that eats up resources, delaying the inevitable: clients have to pay for what they want to get in return.