smart-account-kit-bindings

Generated TypeScript client and contract types for the OpenZeppelin smart account contract on Stellar.

Most applications should install smart-account-kit, which wraps these bindings with passkey, signer, policy, discovery, and transaction workflows. Use this package directly when you need the generated contract client or exact contract types.

[!WARNING] These bindings can build state-changing transactions. This integration package has not undergone an independent security audit. Review each transaction before signing or submitting it. See the project security status.

Install

pnpm add smart-account-kit-bindings @stellar/stellar-sdk

Use the generated client

import { Client } from 'smart-account-kit-bindings';

const client = new Client({
  contractId: 'C...',
  networkPassphrase: 'Test SDF Network ; September 2015',
  rpcUrl: 'https://soroban-testnet.stellar.org',
});

const transaction = await client.get_context_rule({ context_rule_id: 0 });
console.log(transaction.result);

Contract calls return AssembledTransaction values from @stellar/stellar-sdk/contract. Read-only simulations expose their decoded return value on .result; state-changing calls can be signed and submitted through the assembled-transaction API.

Regenerate in this repository

The repository wrapper preserves package metadata, formatting, and this README after invoking Stellar CLI:

ACCOUNT_WASM=/path/to/multisig_account_example.wasm \
BINDINGS_VERSION=0.3.0 \
pnpm build:bindings

You can also configure a deployed WASM hash or contract ID in demo/.env. build:bindings prefers explicit env/args, falls back to demo/.env.example, and prints the source and hash it binds against. See the repository's release guide for the optimized contract build and publish sequence.

The underlying Stellar CLI command is stellar contract bindings typescript; the older soroban contract bindings ts spelling is no longer used.

Verify against the deployed contract

These bindings are generated from the canonical deployed WASM and must stay byte-compatible with it. From the repository root:

pnpm verify:bindings

This regenerates from the canonical testnet WASM hash recorded in docs/deployments-protocol-27-2026-07-09.md, diffs the result against the checked-in src/index.ts, and exits nonzero on drift. Never hand-edit the generated sources to resolve drift — fix it on the contract side (redeploy) and regenerate, or the next verify:bindings will flag it again.