Special case: A distinct namespace for offline/wallet capabilities?

[bumblefudge]

1.) DIDs and VCs are examples of very blockchain-like capabilities that a blockchain wallet might want to support, without requiring any communications with nodes. Currently, CAIP-169 tries to update some work done by Mircea and Oliver at Veramo/Mesh to bring VC protocols into the toolkit of Wallet-Connect wallets. These are namespace-independent, and entirely node-free. So where do dapps put these methods when calling CAIP-25 on the wallet? A scope object called wallet, I'm thinking.

2.) I'm presuming there are other offchain capabilities (PassKey comes to mind, or FIDO, or on-device biometrics) that it might behoove us to abstract and standardize some day! These would also go in the wallet scope space, right?

3.) Note, in the evolution of the EVM RPC methods, wallet_changeEthereumChain and a few other wallet_-prefixed methods have been defined by EIPs. These should probably live in eip155, confusingly enough, since wallet::changeEthereumChain doesn't make much sense for the non-EVM world!

Please chime in if you have objections, or if you have other use-cases, or if you just want to bikeshed the name of the scope:

• wallet
• offchain
• nodefree

[bumblefudge]

https://github.com/ChainAgnostic/namespaces/pull/107 was merged, which partially addresses this issue as a one-time namespace-specific affordance. Other solutions may be possible, so leaving this open to catch other use-cases and solutions