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
Initially, Snaps only had an RPC handler in order to provide any functionality. Since then, we've added other possibilities for Snaps to work, like transaction insights through the onTransaction entry point, and keyrings through the keyring entry point. Both of these entry points require a permission to work. We should do the same thing for the onRpcRequest entry point, requiring a permission in order for a Snap to be able to receive requests.
This also makes it possible for a Snap to specify whether it should be able to receive requests from just dapps, just other Snaps, or both. For example:
Initially, Snaps only had an RPC handler in order to provide any functionality. Since then, we've added other possibilities for Snaps to work, like transaction insights through the
onTransaction
entry point, and keyrings through thekeyring
entry point. Both of these entry points require a permission to work. We should do the same thing for theonRpcRequest
entry point, requiring a permission in order for a Snap to be able to receive requests.This also makes it possible for a Snap to specify whether it should be able to receive requests from just dapps, just other Snaps, or both. For example:
Both values can default to
false
. At least one must betrue
for a valid permission. For example:dapps: true
,snaps: true
- Requests from both other Snaps and dapps.dapps: true
,snaps: false
ORdapps: true
- Only requests from dapps.dapps: false
,snaps: true
ORsnaps: true
- Only requests from other Snaps.dapps: false
,snaps: false
- Invalid. At least one of them must betrue
.The text was updated successfully, but these errors were encountered: