CAIP-319 primary sources
Collected: 2026-05-14 UTC
Primary sources reviewed
- https://standards.chainagnostic.org/CAIPs/caip-319
- Official CAIP draft page for Wallet Notification JSON-RPC Method
- Key points used:
wallet_notifyenvelope; required scoped target plus nested notification object; optionalsessionId; validation rules for scope and notification method; no-response JSON-RPC notification semantics; motivation around concurrent multi-chain connections
- https://raw.githubusercontent.com/ChainAgnostic/CAIPs/master/CAIPs/caip-319.md
- Raw source text from the canonical CAIPs repository
- Used to confirm the exact payload shape, the requirement that notifications be previously authorized within a CAIP-25 session, and the fire-and-forget delivery semantics
- https://standards.chainagnostic.org/CAIPs/caip-25
- Adjacent standard for session creation and authorization scopes
- Used to anchor CAIP-319 as a post-authorization notification layer rather than as a standalone event system
- https://standards.chainagnostic.org/CAIPs/caip-311
- Adjacent standard for
wallet_sessionChanged - Used to separate CAIP-319’s generic authorized-notification rail from CAIP-311’s narrower authorization-update event path
- Adjacent standard for
- https://standards.chainagnostic.org/CAIPs/caip-316
- Lifecycle-management companion for sessions with and without identifiers
- Used to interpret why
sessionIdis optional and how notifications fit both identifier-based and no-identifier session models
Notes
- CAIP-319 is more interesting as a control-surface document than as a generic event wrapper. The key question is whether wallet-originated push traffic remains wallet-specific middleware behavior or becomes a scoped, auditable part of standardized session authority.
- The analytically important move is that notifications are not only tagged with a session; they are also bound to a target scope and validated against previously authorized methods, which keeps the push path from silently becoming an unrestricted callback channel.