Introduction
Signing proves that an authorized wallet member approves a prepared operation. Use this step after preparation and before submission. Your application owns user approval, signer selection, and key custody; the hosted API key stays on your server. TypeScript’s/signers entrypoint and Python’s helpers use application callbacks.
Rust’s native signers hold local keys through Arc. These helpers make no hosted
API calls. Inspect transaction intent, permissions, and freshness before signing.
SDK examples
Ed25519 and application-defined signers
TypeScript/Python callbacks receive the base64 transaction and prepared record, and return signed base64. Rust adds a signature to the correct native slot. Useprepared.transaction after resolving participant and embedded signatures.
Repeat for each required application-owned Ed25519 signer.
Secp256r1 and passkeys
TypeScript runs the passkey ceremony in a WebAuthn environment. Python uses your assertion callback. Rust signs raw P-256 authority requests with a local key; it does not run a browser passkey ceremony.Secp256k1 and EVM wallets
TypeScript/Python use an application-supplied EIP-1193 provider’spersonal_sign.
eip1193Provider / eip1193_provider is the connected wallet provider. Rust uses raw
secp256k1 authority signing, which differs from the EIP-191 format used by a
participant signer.
Sign an ordered preparation plan
Resolve the embedded requests in every transaction using the same registered signer callbacks. The helper preserves order and stops on failure.Flow
Input
An empty
signatureRequests / signature_requests list does not mean the
transaction is fully signed. Embedded secp256k1/secp256r1 requests are separate
from native Ed25519 requirements in the serialized transaction.
Rust’s TransactionSigner consumes a PreparedTransaction and returns a
VersionedTransaction. All embedded requests must match that signer.

