The problem is how you are thinking about the problem. Proof of storage is impossible, only proof of delivery is possible. Delivery can be monetised, and so can submission, via the same mechanism. In addition, because it is designed to be programmable, and the relays are dumb and just process commands so long as there is balance on the relay sessions, it can be used for anonymisation of traffic, both client and bidirectional, to charge for access to content (paywalling), and is designed so that any way you can think of prepaid sessions for forwarding traffic around can be easily implemented without any change to the relay software, just by creating a new client.
It is inspired by the genius of nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qyv8wumn8ghj7un9d3shjtnwdaehgunpw35jucm0d5q3vamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmnyv0c7x9 's nostr protocol, to be as simple and open ended as possible.
Your project is a good solution for authenticating complex data types, probably better than IPFS in some ways - IPNS is so poorly supported and clunky to work with, but that's all it does, and that means that if it turns out later it restricts usage in some critical way your protocol will not survive.
Also, I didn't notice who started this thread, and now I get why your posts sound like marketing. I'm gonna butt right out of this for now, because I don't believe in him being what he claims to be any more than Alex Jones not having strings attached.
Bitstream provides both monetized delivery and storage, but mainly focuses on delivery. The Lightning payment can only be claimed if the server delivers the correct file: https://www.hornetstorage.com/bitstream
Paid Storage works by randomly requesting a random leaf/chunk of the file you want stored once a day/week/month — if the relay can’t deliver the leaf(s), then they don’t have your data and you quit streaming your sats.⚡️🍃