-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forest OpenRPC FIPs #4038
Labels
Comments
This was referenced Mar 15, 2024
Closed
End goal
Current status
Outstanding work
|
5 tasks
lemmih
added
Priority: 2 - High
Very important and should be addressed ASAP
Type: Feature
labels
Aug 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Forest's 2024 roadmap includes the following:
The proposed timeline includes the following:
Q2
Q3
Forest has attempted to use the results of calling the
rpc.discover
JSON-RPC method on Lotus to generate a compatible API, but failed1:We have therefore manually implemented our RPC API from scratch.
The interface definition language for JSON-RPC interfaces is OpenRPC: https://open-rpc.org/, which can be the basis for a FIP.
We should not maintain a separate OpenRPC document for our API - it can be generated from our existing code.
This issue tracks
Footnotes
Lotus' OpenRPC definitions are inaccurate #3668
We also tried codegen from go:
https://github.com/ChainSafe/forest/tree/5a05dd184a6e8f9eaeb21c8f122b3f9a0b89b974/codegen ↩
The text was updated successfully, but these errors were encountered: