📄️ Connection Model
The wallet-gateway uses WebSocket as its sole transport. This document explains how connections are established, managed, and closed — and what wallet clients should expect at each stage.
📄️ Message Authentication
Every message sent to the wallet-gateway must be signed by the private key of the wallet address it claims to be from. There are no sessions, tokens, or cookies. The signature on the message is the credential.
📄️ Subscription Model
The wallet-gateway can push real-time notifications to connected clients without polling. This document explains how the subscription model works and what clients should expect.