Build a comprehensive list of public EVM Blockchain RPC endpoints
Budget: $250 – $750 USD
We analyze blockchain activity. This requires connections from our software to blockchain nodes. We have built a framework for ingesting data from Ethereum-based (EVM) blockchains via its JSON-RPC APIs. We are currently analyze over 40 EVM-based chains and want to expand to ALL EVM-based chains.
The scope of this project is:
1) Build a list of all known RPC endpoints for EVM blockchains
2) Identify whether the blockchain is a mainnet or testnet
3) Identify whether the RPC endpoint includes archive (historic) data
4) Build a Postman collection with an eth_getBlockByNumber call to each endpoint, confirming that archive data is available
5) Document all endpoints in a spreadsheet (we'll provide the spreadsheet template)
We will provide the steps needed to perform these tasks promptly. Essentially, this project is just busy-work validating all of the RPC endpoints.
In a nutshell, the steps are:
1) Go to https://chainlist.org and https://www.coincarp.com/chainlist and find all EVM networks, both mainnet and testnet (NOTE: there are probably over 500 chains as this point)
2) For each network, view the list of known RPC endpoints
3) Find a block explorer for that network and figure out a very old block # that has at least 1 transaction in it. Some RPC endpoints purge old (archive) data. We want to discover whether the RPC endpoint includes archive data.
4) In Postman, create a request to that endpoint and call eth_getBlockByNumber for that old block #. If the response includes details in the "transactions" array, then this is an archive node. If not, then it is a purged (non-archive) node
This is simple, straightforward work. But it may take a few days to compile the full list since there are hundreds of networks with 1 or more RPC endpoints each.
The scope of this project is:
1) Build a list of all known RPC endpoints for EVM blockchains
2) Identify whether the blockchain is a mainnet or testnet
3) Identify whether the RPC endpoint includes archive (historic) data
4) Build a Postman collection with an eth_getBlockByNumber call to each endpoint, confirming that archive data is available
5) Document all endpoints in a spreadsheet (we'll provide the spreadsheet template)
We will provide the steps needed to perform these tasks promptly. Essentially, this project is just busy-work validating all of the RPC endpoints.
In a nutshell, the steps are:
1) Go to https://chainlist.org and https://www.coincarp.com/chainlist and find all EVM networks, both mainnet and testnet (NOTE: there are probably over 500 chains as this point)
2) For each network, view the list of known RPC endpoints
3) Find a block explorer for that network and figure out a very old block # that has at least 1 transaction in it. Some RPC endpoints purge old (archive) data. We want to discover whether the RPC endpoint includes archive data.
4) In Postman, create a request to that endpoint and call eth_getBlockByNumber for that old block #. If the response includes details in the "transactions" array, then this is an archive node. If not, then it is a purged (non-archive) node
This is simple, straightforward work. But it may take a few days to compile the full list since there are hundreds of networks with 1 or more RPC endpoints each.