Reference
Exact surfaces rather than explanation — the client API, the adapter contracts, every importable subpath, the error taxonomy, runtime support, and the security policy.
These pages state what exists. They do not argue for anything, and they assume you already know your goal.
If you must make a design decision, use Build or Learn. A reference page gives you a method signature but does not evaluate its use.
Find a topic
API reference: the curated client surface: createSignalProtocolClient options, every client method by category, properties, hooks, and the standalone modules. Start here if you have an object and need to know what it can do.
Adapter interfaces: the four adapter slots and the guarantees each implementation must provide. Read this before writing an adapter rather than after. Several obligations are load-bearing and none of them are visible in the type signature.
Package subpaths: the complete exports map, every importable subpath, what it exports, and each entry's support status. The answer to "where does this import come from" lives here.
Errors: the complete taxonomy: base classes, every error code, the specialised classes with their type guards, and the retry rules. Pairs with error handling, which covers what to do about them.
Runtime support matrix: which runtimes the SDK supports, which store adapter each one uses, and the exact documented position on Expo Go.
Security and protocol policy: spec revision pins, post-quantum defaults, the deliberate divergence from Signal Messenger, the identity trust model, audit status, and responsibilities. Give this page to a security reviewer.
A note on maturity
The SDK is 0.1.x. Public APIs and persisted formats may change before 1.0. An experimental or development-only label states the current support status; no store adapter is experimental, and the in-memory store and relay are development only. Runtime support and adapter interfaces define these labels.
Migrate from libsignal-protocol-javascript or @privacyresearch/libsignal-protocol-typescript
A re-architecture guide with no wire compatibility, an honest comparison of the packages you are leaving, and a staged cutover that does not require a flag day.
API reference
The curated client surface — createSignalProtocolClient options, every SignalProtocolClient method by category, properties, hooks, and the standalone modules.