Full history node distributed system standard. This is a challenge for the EOS mainnet since it requires expensive hardware.
I propose a different way to attack the problem of “full history” and have a collection of servers with different filters on them that will each have a complete history of a subset of the EOS data.
These can be created for specific developer’s requests and will be orders of magnitude smaller and cheaper to spin up. They will be useful only for the developer who created them since they will concentrate on their specific use case.
This can be either a Saas (Software as a service) with an income stream shareable between the operator of such a service and Eden, with perhaps a freemium tier or just an open source project that developers can use on their own infrastructure if it is thoroughly documented.