CAIP-312 primary sources
Collected: 2026-05-10 UTC
Primary sources reviewed
- https://standards.chainagnostic.org/CAIPs/caip-312
- Official CAIP draft page for JSON-RPC Method for Retrieving Session Authorizations
- Key points used: status Draft; requires CAIP-25 / 217; retrieval with or without
sessionId; return of currentsessionScopes; generic failure recommendations; recommendation for domain-bound or other 1:1 transports
- https://raw.githubusercontent.com/ChainAgnostic/CAIPs/master/CAIPs/caip-312.md
- Raw source text from the canonical CAIPs repository
- Used to confirm the exact request shape, response payload, and ambiguity rules around no-
sessionIdcalls when only identifier-based sessions exist
- https://raw.githubusercontent.com/ChainAgnostic/CAIPs/master/CAIPs/caip-25.md
- Base wallet-session authorization standard that CAIP-312 extends
- Used to anchor the page in the broader wallet-session stack and confirm that current-state retrieval is part of the same authorization model as session creation
- https://standards.chainagnostic.org/CAIPs/caip-316
- Lifecycle-management companion document for CAIP-25 sessions
- Useful for understanding why CAIP-312 matters especially when the wallet is the durable source of truth for a no-
sessionIdsession
- https://github.com/ChainAgnostic/CAIPs/pull/285/files
- Proposal / diff thread linked from the draft as
Discussions-To - Used as provenance for the lifecycle-method changes moving through the official CAIPs process
- Proposal / diff thread linked from the draft as
Notes
- CAIP-312 is best framed as the pull-based reconciliation method in the wallet-session lifecycle, not just a convenience getter.
- The interesting control surface is who remains authoritative about current permissions after the initial connect flow: the dapp’s cache, or the wallet’s live session state.