Archival data access

Building with the long-term vision.

With the development of blockchain networks and the move toward decentralization, there is a big change in ecostystems. This change is driven by the need to lower system requirements for those interested in hosting nodes. Until recently, historical data in virtually every network was available to anyone interested. With the growth of data, however, this has begun to change. Let's look at the Ethereum network, as an example. Ethereum right now is scaling due to rollups and multiple protocol improvements, where some of them are:

• Danksharding - allowing for the creation of data blobs available only for about 18 days. More here: https://ethereum.org/en/roadmap/danksharding/
• State expiry - which moves the responsibility of providing historical data outside the core Ethereum protocol. More here https://ethereum.org/en/roadmap/statelessness/

It can be assumed with a high degree of confidence that protocol improvements that are adopted and implemented within Ethereum will be similarly or identically implemented in other Ethereum-compatible networks or not.

With these developments, it is apparent that developers of protocols such as Ethereum want to shift the responsibility for storing and providing historical data to third parties. Such an entity that provides data in a secure, fast, modular and ultimately decentralized manner is Api-Verse.