Developers
Embed Warren in your app
A reference engine in Rust, thin wrappers for your language, and a wire contract locked by test vectors. All open source.
One engine, thin wrappers
The Rust engine is the reference implementation. Every SDK either embeds it through FFI or reimplements the protocol clean-room against the same test vectors. One source of truth for the wire, one idiomatic API surface per language.
Golden vectors, the wire contract
Every wire format (identity, signatures, exit roster, multi-hop sealing) is frozen in warren-vectors: reference bytes every implementation must reproduce exactly. An SDK that drifts breaks in CI.
What the SDK can do
- Non-custodial identity: BIP39 mnemonic, Ed25519 key derived locally, SS58 address starting with wb…
- API requests signed with the account key, no bearer token, and verification of the signed exit roster.
- Full WarrenGuard tunnel: QUIC, TLS 1.3 Raw Public Keys, obfuscation by default.
- HPKE sealed multi-hop through a blind relay.
- Unprivileged proxy datapath: SOCKS5, HTTP CONNECT, DNS over the tunnel, dual-stack IPv6.
- Port forwarding: request and release public ports on an exit node.
Licenses and repositories
The SDKs and the engine are released under AGPL-3.0, the app under GPL-3.0. The same vectors validate any third-party implementation.