Of course, and an SPV like Neutrino also.
Also just want to remark, that the 10-60 minute latency of on-chain confirmations of such data is still better than the 3-24 hours that you get with DNS. But why be satisfied with that when updates to the state can happen at the speed of Lightning???
sounds good indeed! But you'll need to trade the simplicity of the timechain vs lightning management. I love using lightning but most people even IT people (myself included) rely on 3rd service providers for it. Lightning would need to get better tooling for people to be zen using sovereign lightning. can't be zeus and the buddha at the same time :p or maybe i'm too much of a pussy, just run that hot wallet jeeez!
reply
Yeah, while payments for registrations make sense on LN, I'm not sure that registrations don't require the timechain. I think the secret sauce would be in the gap between paying for the update and propagating it to the users.
That might be where the problem of accounting for bandwidth costs comes in - perhaps it would be better if name resolutions came with a fee, and then propagating really current data becomes profitable.
Or maybe the fees could be paid to Indranet nodes providing this service, it is already in the plan that Indranet relays advertise services with per-service fee rates for exit traffic.
I really do think that when Indranet is fully realised it will form the layer 3, the first fully qualified L3 on top of the L2 of Lightning. If we can roll this little project out as soon as possible we might just manage to get that first mover advantage with a "good enough" solution that then becomes the foundation of further application systems that need incentives for hosting.
Proof of storage is a very difficult problem, many projects have aimed at it and failed (chia, storj, maidsafe). But proof of delivery is a less thorny problem, and amounts to the same thing as payment for delivery can fund storage and thus rewarded indirectly.
reply