You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the merge of SIP-26, we should implement an RPC router and the onProtocolRequest endowment/export as per the agreed specification: https://metamask.github.io/SIPs/SIPS/sip-26
The text was updated successfully, but these errors were encountered:
…2875)
This PR adds a `MultichainRouter` that can handle routing of non-EVM
requests received via the multichain API. The multichain API should
integrate this by calling `MultichainRouter.handleRequest` for any
requests that are not understood by our existing JSON-RPC stack.
Additionally this PR implements `onProtocolRequest`, a new handler that
Snaps can choose to register if they want to service protocol (non
signing) requests for a given set of methods for one or more chains. The
endowment is registered as follows:
```json5
"initialPermissions": {
"endowment:protocol": {
"scopes": {
"<caip2_chainId>": {
"methods": [
// List of supported methods
],
"notifications": [
// List of supported notifications
]
}
}
}
}
```
This implementation follows https://metamask.github.io/SIPs/SIPS/sip-26Closes#2898
---------
Co-authored-by: Maarten Zuidhoorn <maarten@zuidhoorn.com>
Following the merge of SIP-26, we should implement an RPC router and the
onProtocolRequest
endowment/export as per the agreed specification: https://metamask.github.io/SIPs/SIPS/sip-26The text was updated successfully, but these errors were encountered: