RPC 2.0 will be a major refactor of the existing RPC, targeted for V22. The refactor will be a breaking change, and RPC 1.0 will be deprecated but usable for a few more versions. The goals of RPC 2.0 are as follows:
- Remove unused RPCs, make changes that require breaking the existing functionality, and add new RPC functionality
- Improve performance, both internally and in the endpoint
- Consistent input and output handling
This topic will outline the proposed, accepted and rejected RPC changes from the point of view of the user, i.e., internal changes are out of scope.