Shuttle SDK
Wallet creation, signing, transfers, policies and signed events — one business contract across TypeScript, React, Python and Go. Compiled losslessly from 25 canonical source documents.
Status and source boundary
Proposed SDK surface for product review, compiled losslessly from the 25 canonical source documents. It is not an installable library, accepted implementation specification, or production-readiness claim.
Start here#
embedded or server control mode.
getOperation
Every mutation is durable and recoverable by its request
identity. This is how you resolve an unknown outcome — never by retrying.
Wallet lifecycle#
Signing#
Transfers & balances#
Custody & recovery#
Policies & authority#
Events & operations#
Catalogs#
Conventions#
Every method page follows the same shape, so you can scan for the part you need.
| Section | What it answers |
|---|---|
| Status | How much of this is verified source fact versus proposed design. |
| Business action | The one thing the call does, in business terms. |
| Proposed call | Signature in TypeScript, Python and Go, plus required input. |
| Result | What comes back, and what is deliberately never returned. |
| Authorization and effects | Who may authorize, and exactly what changes on success. |
| Acceptance | Positive and negative criteria the implementation must meet. |
Code blocks with language tabs remember your choice: pick Go once and every block on every page follows. Press ⌘K or / to search.
Naming across runtimes
One shared business contract, one set of stable JSON field names, native naming per
language: requestId in TypeScript, request_id in Python,
RequestID in Go — all encoding to request_id on the wire.
Exact monetary quantities are canonical unsigned base-10 JSON strings; the codec rejects
JavaScript number, floating point, signs, fractions, exponent notation and
non-canonical leading zeroes.