Appearance
@keymaster/connect · browser SDK
Capabilities in.
Private keys stay out.
Build browser apps that request identity, cryptography, messaging, storage, and payment capabilities from Keymaster.
$
pnpm add @keymaster/connectPOSTMESSAGE TRANSPORT · EXACT ORIGIN · SESSION-BOUND
01 / CAPABILITIES
One session.
Five capability systems.
Every business request is bound to the identity and origin chosen for the Connect session.
01IdentityAuthenticate users and issue signed claims
identity.get↗02CryptographySign intent and encrypt origin-bound dataintent.sign · cipher.*↗03CommunicationSend private messages and signed broadcastsappmsg.* · broadcast.*↗04StorageWork inside an app-scoped object namespacestorage.*↗05PaymentsRequest controlled BSV transfers and fee-pool operationsp2pkh.* · feepool.*↗02 / CONNECTION MODEL
A window is transport.
A session is authority.
- 01
Connect
Open a reusable Session Window, or adopt the opener in appView mode.
- 02
Authorize
The user chooses an owner identity. The SDK receives a persistent session id.
- 03
Request
Call typed methods. Keymaster owns confirmation, private material, and execution.
03 / BUILD
The API is the SDK.
No documentation adapter in between.
Every reference page is generated directly from the package exports developers install.