Skip to main content

SDKs: choose an integration layer

SDKs expose composable cryptographic and protocol capabilities. Your application selects accounts, protects keys, presents authorizations, authenticates decryption and submits transactions. The SDK does not replace your wallet or payment backend.

OptionSuitable forBehavior
TypeScriptWeb, Node.js, wallets and DAppsNative/WASM local proving and browser/server sessions
GoBackend services, tools and self-hosted paymentsIndependently selected modules, chain capabilities and local prover
RustNative applications and controlled runtimesSeparate crates, explicit proving and optional persistence
Stateless preparationSystems that manage their own credential inventoryExplicit inputs; caller owns selection, reservations and recovery
WalletSessionManaged wallet inventorySynchronization, selection, reservations, journals and recovery

Select capabilities​

  • @invisi-labs/primitives: addresses, credentials, hashes and delivery codecs; no network or proving runtime.
  • @invisi-labs/protocol: ABI, public types, signing messages and codecs.
  • @invisi-labs/rpc: Protocol RPC, Broadcaster and Provenance transport.
  • @invisi-labs/prover: explicit local proving and authenticated resources.
  • @invisi-labs/sdk: stateless preparation, external authorization and transaction export.
  • @invisi-labs/session: durable operations and managed inventory.

Use packages from one compatible release cohort, with matching ABI and proof resources. Examples use the 1.3.2 API. Confirm that your selected distribution includes these methods and that matching proof resources are available. Read compatibility before installing.

Amounts and authorization​

SDK amounts are token-base-unit integers: TypeScript bigint, Go big.Int, Rust U256. The merchant API instead uses currency-unit decimal strings. Convert using the token’s actual decimals: 10n does not mean 10 USDC.

Freeze the final fee quote before authorization and proving. Changes to amounts, fees, recipients, deadlines or execution mode require reviewing the affected authorization again.

First verifiable flow​

Construct an output offline, prepare public funding, then use a session to discover and spend confirmed Notes. Local proving explains runtime and resource requirements.