caip-27-primary-sources-2026-05-14

CAIP-27 primary sources

Collected: 2026-05-14 UTC

Primary sources reviewed

• https://standards.chainagnostic.org/CAIPs/caip-27
  • Official CAIP draft page for Wallet Invoke Method JSON-RPC Method
  • Key points used: wallet_invokeMethod envelope; required chainId plus nested request; optional sessionId; optional capabilities; response-envelope structure; top-level versus nested error separation; explicit target-network routing motivation
• https://raw.githubusercontent.com/ChainAgnostic/CAIPs/master/CAIPs/caip-27.md
  • Raw source text from the canonical CAIPs repository
  • Used to confirm the exact wording around conditional sessionId usage, the nested request/response examples, and the backward-compatibility note that older drafts allowed broader scopeString targeting before tightening to CAIP-2 chainIds
• https://standards.chainagnostic.org/CAIPs/caip-25
  • Adjacent standard for session creation and authorization scopes
  • Used to anchor CAIP-27 as a post-authorization invocation layer rather than as a standalone connect-wallet handshake
• https://standards.chainagnostic.org/CAIPs/caip-316
  • Lifecycle-management companion for sessions with and without identifiers
  • Used to interpret why sessionId is conditional rather than always required in the invocation envelope
• https://namespaces.chainagnostic.org/
  • CASA RPC namespace registry referenced by the CAIP text
  • Used as evidence that response and error semantics can still vary below the generic envelope depending on namespace-level RPC conventions

Notes

• CAIP-27 is most valuable as a routing and control-surface document, not as a generic provider-call wrapper. The important question is who decides which already-authorized chain or namespace a later request is actually targeting.
• The analytically important move is not only multi-chain disambiguation; it is that authorization, execution routing, and capability invocation stay separable layers after session creation.