Create canonical place for ETH RPC API support status

[BigLep]

Done Criteria

There is a public linkable place that lists:

Each Eth RPC API

• If it's implemented in Geth
• If it's implemented in Lotus
• If it is implemented in Lotus
  • are there any limitations
  • impact of those limitations
  • tracking item(s) for improving the limitations
• If it isn't implemented in Lotus
  • impact of not having the API (e.g., collection of usecases that are being blocked, customers who have asked for it)
  • tracking item(s) for doing the work

Why Important

• Maintainers get messages that there is some problem on some API. They are often missing the importance or how many/who are impacted and what usecases are impacted.
• Consumers don't know in advance what "gotchas" they're going to run into.

User/Customer

• ETH RPC API consumers so they can know the level of quality they can expect and whether their ETH RPC-using plans will work.
• Maintainers so they can get a gage on the importance of APIs to support/fix based on the accumulated usecases

Notes

• This will likely be created in Filecoin Dev Notion and linked to from Lotus repo.

[BigLep]

I plan to take the first-stab here this week.

[trruckerfling]

FIP repo? Docs? There is this on Pectra and @snissn can update on cancun cc: @rjan90 thanks for flag!

[BigLep]

I plan to take the first-stab here this week.

Doh. I didn't get to it before vacation/travel and then outside-of-work commitments ramping up. I don't know when I'll squeeze this in yet.

FIP repo? Docs?

I was thinking to create this in Filecoin Dev Notion and link to it from Lotus repo, but happy to consider something else.

[BigLep]

@rvagg move this forward significantly with https://www.notion.so/filecoindev/Lotus-Ethereum-API-Compatibility-1d0dc41950c180cc8c3ecc9033d56cc7

[BigLep]

@rvagg : https://www.notion.so/filecoindev/Lotus-Ethereum-API-Compatibility-1d0dc41950c180cc8c3ecc9033d56cc7#1d0dc41950c180409987ef5a1cc4e6d4 is phenomenal. Awesome work! The top things coming to mind are:

1. How we'll account for changes with Lotus /v2. I assume we would name the current column Lotus /v1 and add a Lotus /v2 column.
2. Where we should link this from to improve visibility.
   • Ideas:
     • https://lotus.filecoin.io/tutorials/lotus/build-with-lotus-api/
     • https://lotus.filecoin.io/reference/basics/api-access/
     • https://lotus.filecoin.io/reference/lotus/eth/ (if @rjan90 does work to pull in https://github.com/filecoin-project/lotus/blob/master/documentation/en/api-v1-unstable-methods.md like docs.filecoin.io does)
     • https://docs.filecoin.io/reference/json-rpc/eth (which is just pulling from https://github.com/filecoin-project/lotus/blob/master/documentation/en/api-v1-unstable-methods.md)
   • Other locations? Lotus README?
   • Note: I can see us linking to other in-flight API docs as well like https://www.notion.so/filecoindev/Lotus-F3-aware-APIs-1cfdc41950c180ae97fef580e79427d5