Interface: DeployContractParams

DeployerCallbacks — the seam between this browser SDK and whatever backend / wallet / hosted-relay produces signed Soroban transactions.

The kit itself NEVER holds, asks for, or persists a Stellar signing key. Callers wire their preferred signing path:

A backend service (most common): the kit ships unsigned operation descriptors over the wire; the backend signs + submits via @stellar/stellar-sdk and returns the result.
Launchtube (Stellar's hosted relay): callbacks just hit Launchtube; the user holds a Launchtube token instead of a Stellar seed.
Freighter / browser wallet: callbacks build the transaction in-page and hand it to window.freighter (or any SEP-43 wallet) for signing.
Test harness: callbacks shell out to stellar contract deploy using stellar-cli's keystore (used by test/e2e/create.test.ts).

Implementations are responsible for waiting until each operation reaches a terminal state (success / failure) before resolving.

Properties

readonly salt: Uint8Array

32-byte salt; the new contract's C-address is derived from (deployer, salt, wasm_hash).

readonly walletWasmHash: Uint8Array

32-byte SHA-256 of the wallet WASM (uploaded once via PSK-013 / YK-244).