caip-341-primary-sources-2026-05-10

CAIP-341 primary sources

Collected: 2026-05-10 UTC

Primary sources reviewed

• https://standards.chainagnostic.org/CAIPs/caip-341
  • Official CAIP draft page for Extension ID Target Type Specification
  • Key points used: status Draft; requires CAIP-294; caip341 target type in WalletData; link to EIP-6963 and Wallet Standard in motivation; mandatory use of externally_connectable when the target is present
• https://raw.githubusercontent.com/ChainAgnostic/CAIPs/master/CAIPs/caip-341.md
  • Raw source text from the canonical CAIPs repository
  • Used to confirm the exact target-array structure, the example payload, and the requirement to route subsequent communication through runtime.connect() / runtime.sendMessage()
• https://github.com/ChainAgnostic/CAIPs/pull/341
  • GitHub proposal history for the spec
  • Used as provenance that the draft moved through the official CAIPs process rather than existing only as an isolated docs page
• https://developer.chrome.com/docs/extensions/reference/manifest/externally-connectable
  • Browser API documentation referenced directly by the spec
  • Useful for understanding that CAIP-341 is not inventing a new transport; it standardizes how wallet discovery metadata points into an existing browser-extension channel

Notes

• CAIP-341 is small, but the control surface is real: once wallet metadata can carry transport targets, discovery libraries and wallet-selection flows gain another layer of influence over which communication path the dapp treats as canonical.
• The best comparison frame is not “another discovery standard”; it is “the routing hint that sits between discovery and session establishment.”