Add EVM-compatible JSON RPC wrapper to Paima #407
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this change, you can now query the current block number of a Paima rollup using EVM JSON RPC queries
I've only implemented a few of the endpoints (some of them can't be implemented), but hopefully we can implement the few required to improve interoperability of Paima-based apps with existing tools
In the same PR, I also introduced a new typed
getPaimaNodeRestClient
so you can call@paima/rest
endpoints with automatically generated type definitions instead of having to manually copy the types in the middleware everytimeTODO
InternalRpcError
swallows the internal error which makes it not show up anywhere. It seems internal errors need a specific shape to work (seeRpcError
)@paima/rest
Blockers
See #411