Hi everyone,
We’re sharing an initial release from the ILE Labs team: a standalone compatibility kit for applications that consume node RPC and SDK data. The project is still being validated, so we’re posting the current results for technical review before expanding the scope.
What we built
The current MVP provides:
- black-box comparisons between locally run Fiber v0.9.0 and v0.9.1 runtimes;
- a downstream consumer fixture for channel data;
- a small inspection command that can be run against recorded evidence;
- machine-readable compatibility reports;
- sanitized test fixtures;
- CI checks that reproduce the committed sanitized evidence and consumer analysis.
What we found
During the first build, we observed several fields in live channel responses that were not represented in the consumer type surface.
We also tested invoice creation and a negative-path payment attempt. Invoice creation succeeded on both versions, and both negative-path payment attempts returned the same route-failure class in the tested no-liquidity scenario. The current result is better described as a possible consumer-contract gap requiring technical review.
Planned direction
We are considering extending the kit with:
- additional payment and channel-transition scenarios;
- malformed-response and failure-path testing;
- clearer version compatibility reports;
- integration examples for downstream applications;
- a more complete compatibility matrix for SDK consumers.
We would appreciate technical feedback on whether this is a useful direction and whether the current finding is relevant to application developers.
If similar tooling already exists, if the observed fields are intentionally excluded, or if there are more valuable scenarios we should test first, we would appreciate that guidance before expanding the project.
Repository: GitHub - ILE-Labs/fiber-compatibility-kit · GitHub