pull down to refresh

I think that the best payment model for this protocol would be a scheme where you pay for bytes/time. The node could then also notify you in-protocol of impending expiring balance to prompt a top up. When expired it would purge the data when its storage requirements dictate. The subscription could also specify a voluntary expiry age for data so old events could be purged and pay less overall but keep current stuff live.
I think the innovation would be using the power of micropayments. You can charge per:
  • bytes/time
  • bytes used for storage
  • notes uploaded
  • What else?🤔
reply