Key Takeaways
- “Our service is no longer necessary, and other alternatives exist today that did not exist when we got started”, the announcement reads.
- As per the blog, a robust remote procedure call provider in the market currently offers access to archive data, making the project obsolete.
Ethereum mainnet archive node service ArchiveNode.io has announced its shutdown, stating they are “not needed anymore”.
On April 4, ArchiveNode.io took to Twitter to announce its closure while adding that it has been over three years of providing a free Ethereum Mainnet Archive Node service to developers, students, and researchers, and they have collectively decided to end the ArchiveNode.io project.
“Our service is no longer necessary, and other alternatives exist today that did not exist when we got started’, the announcement reads.
An Ethereum archive node is defined as an instance of an Ethereum client configured to build an archive of all historical states.
This type of node is useful when querying historical blockchain data that is not accessible on Full nodes. Further, Archive nodes are also not required to participate in block validation and can be built from scratch by replaying the blocks from genesis.
According to DeFi dude, who wrote the blog post making the official announcement, the goal of ArchiveNode.io was to “get archive data into the hands of developers, students, and researchers who wanted to build cool shit, but didn’t have the time, money, or resources available to run their own archive node.”
He added that the project was never to “make money or profit.” DeFi dude further claimed that along with the team behind Turbo-Geth (now called Erigon), the group played a major role in changing the landscape of the RPC provider market for archive data access forever.
He also noted that there currently exists a robust remote procedure call provider in the market offering access to archive data making the project obsolete. Further in the blog, the project thanked Ethereum Foundation for the initial grant of $10,000 in AWS credits, which helped take off the project.
