add rpc router section to SIP-26 #151
Open
+516
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Gustavo Antunes <[email protected]>
Co-authored-by: Charly Chevalier <[email protected]>
adonesky1
force-pushed
the
ad/sip-26/add-rpc-router-details
branch
from
e50d6cb
to
051318f
Compare
adonesky1
force-pushed
the
ad/sip-26/add-rpc-router-details
branch
from
051318f
to
2e1d94c
Compare
adonesky1
force-pushed
the
ad/sip-26/add-rpc-router-details
branch
from
953910b
to
e084b41
Compare
adonesky1
force-pushed
the
ad/sip-26/add-rpc-router-details
branch
from
7557007
to
8eca4a6
Compare
…ent method signatures
adonesky1
force-pushed
the
ad/sip-26/add-rpc-router-details
branch
from
8eca4a6
to
9b69ce1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds further detail to the RPC Router:
RPC Router
The RPC Router is a native wallet component responsible for routing RPC requests made via the Multichain API to either a Protocol Snap or the Account Router, depending on whether the requested method is registered as a signing method or not.
Role and Functioning
Initial Request Handling: Receives all incoming RPC requests made via the Multichain API that do not have an
eip155namespace. For now,eip155scoped requests will continue to be handled by the native wallet, though we will need to consider how to allow users to decide whether to route these requests to snaps as well in the future.Method Registration: Provides entry points for the Account Router and Protocol Snaps to register their methods, method signatures, and scopes, and maintains a registry of these RPC methods and their respective handlers.
Request Routing: Uses the internal registry to determine the correct handler for each incoming RPC request based on the method name, method signatures, and scope strings, forwarding the request to either the Account Router or the appropriate Protocol Snap.
See the diff for more!