filecoin-project
Common Node API
A work-in-progress to establish a common API for all node implementations.
Many todos remain at this point, most notably:
- Further discussion on which methods are included and the associated rationale
- Sufficient conformance testing to validate implementations are adherent to the specification
IMO, this should go under the FRC section instead of the FIP section as it's not a consensus critical change (and therefore doesn't have to go through the entire FIP process).
I am supportive of the motivation and direction of this proposal. Will give a more thorough review once the methods list are proposed
IMO, this should go under the FRC section instead of the FIP section as it's not a consensus critical change (and therefore doesn't have to go through the entire FIP process).
@Stebalien We chose to be a technical FIP based on this guidance: https://github.com/filecoin-project/FIPs/blob/020bcb412ee20a2879b4a710337959c51b938d3b/FIPS/fip-0001.md?plain=1#L30
Happy to move to FRC if that fits better - maybe the above could be amended?
I am supportive of the motivation and direction of this proposal. Will give a more thorough review once the methods list are proposed
🙏 @jennijuju
We have a working doc with all the methods here: https://docs.google.com/spreadsheets/d/1fFkQuEjvFAd2s1dGX5zGmhxsEMLMUZ4uQFnIXgSZA5w/edit?usp=sharing
A few methods we're still unsure of, but we've taken a stance of most of them. Rationale is included for those that are excluded, and those that are included should fit into one of the categories we describe
Since GitHub didn't backlink it, the accompanying discussion for this PR is https://github.com/filecoin-project/FIPs/discussions/1032
2025-05-12 conversation with FilOz and Chainsafe:
- Need to add OpenAPI json spec
- Chainsafe will open a new PR
The Forest team is going to open this PR fresh since the original authors are no longer around. We're 95% of the way with this PR and just want to get something merged at this stage.
I'm assigning number 0104 to this FRC. @AlexeyKrasnoperov @LesnyRumcajs please use that number in your new PR.
