@1sat/connect SDK Development

To build a popup-based wallet SDK, establish a messaging protocol and transport layer enabling dApps to communicate securely with wallet popups. This involves defining the API surface, handling errors, and structuring core modules like provider.ts for consistent message passing.

The popup protocol works by establishing a secure transport layer between the dApp and the wallet, exchanging structured messages to request and approve transactions. It relies on a defined API surface and standardized error handling managed by modules like messages.ts.

The best way to structure a TypeScript wallet SDK is to separate concerns into key modules like provider.ts for the API surface, messages.ts for protocol definitions, and errors.ts for error handling. Following strict coding conventions ensures maintainability when extending with new methods.

Yes, you can extend the TypeScript wallet SDK with new methods by updating the core modules and following established architectural patterns. The guide provides conventions for adding features, updating the API surface, and maintaining robust integration with wallet popups.

Handle errors in a popup-based wallet SDK by centralizing error definitions in dedicated modules like errors.ts and standardizing error messaging across the transport layer. This ensures the dApp receives clear, actionable feedback when popup communication or transaction approvals fail.

Messages are lost in the wallet popup transport layer when the messaging protocol lacks proper handshake or event handling logic. Debugging requires verifying structured messages in modules like provider.ts and ensuring the popup window lifecycle is correctly managed by the SDK.