Refactor RPC implementation
koushiro opened this issue · 4 comments
koushiro commented
Motivation
I am not very satisfied with the current RPC implementation (due to some unreadable implementation and some compatibility issues), so I plan to refactor this part.
Suggested Solution
- Refactor the rpc parameter and return value types, which will be fully compatible with the ethereum standard (non-standard RPC will be compatible with geth) #1427
- Refactor rpc api according to the namespace. #1427
- Refactor rpc implementation.
Additional Information
eip-4844 is not currently planned to be supported (need evm to support it first)
boundless-forest commented
We need evm to support EIP-4844 first
We'd better to upgrade the frontier evm version to the latest of evm crates, 1.0.
koushiro commented
I have completed rewriting the RPC types and API parts (#1427), but the specific implementation of RPC still depends on other client components, whose implementation is not satisfactory to me.
Therefore, before implementing RPC, I will likely rewrite these components, like db, mapping-sync...