ChainAgnostic
CAIP-282 - Browser Wallet Messaging Interface
Just sharing here some developments on this CAIP... after discussing it with several teams who gave very valuable feedback
- The interfaces have been changed to follow a JSON-RPC structure to make it more agnostic and easier to use with multiple transports
- Enforcing window.postMessage makes this CAIP not very future-proof as Chrome Extensions are slowly migrating to externally_connectable
- This CAIP is more useful if it does NOT describe the actual transport and instead focuses on the discovery interfaces
- The usage of window.postMessage without mentions of targetOrigin creates huge security concerns
What are the next steps?
a. Separate window.postMessage from discovery interface into two CAIPs b. Create a new CAIP which uses the discovery interface with externally_connectable c. Create a new CAIP which uses the discovery interface with window.dispatchEvent
What is the end goal?
This CAIP intends to provide the most agnostic and interoperable interface for wallet discovery and consequentally handshake and signing.
Since CAIP-25 and CAIP-27 already describe handshake and signing then CAIP-282 will focus purely on discovery
Why create separate CAIPs for each transport?
These additional CAIPs are important for Apps and Libraries to support multiple wallet transports... most importantly the following:
- window.postMessage for embedded wallets with iframes
- window.dispatchEvent for legacy browser extension support
- externally_connectable for newer browser extension support
The combination of all JSON-RPC interfaces and different transport specs will any wallet to be discoverable, connect and sign with a decentralized application for all CAIP compatible chains
This PR now includes 3 proposals:
- CAIP-282 -> Browser Wallet Discovery Interface
- CAIP-294-> Browser Wallet Messaging for Extensions (window.dispatchEvent)
- CAIP-295 -> Browser Wallet Messaging for Iframes (window.postMessage)
Still missing another standard to be included in this PR:
- CAIP-296 -> Browser Wallet Messaging for Extensions (externally_connectable)
apologies, pedro, my june comments were sitting in github UI limbo waiting to be batched to a complete review 🙄
are we discussing this in person in Bangkok, btw, @adonesky1 @pedrouid ?
Mostly Approved but there are still a few nits I couldn't fix myself and a few threads that it felt wrong to "resolve"... @pedrouid another 10min should get this over the line for me and on to ligi or al or obstropolous for final approval
@pedrouid bump
