Package-level declarations
Types
An external party whose signing key never left the SigningDriver.
The AmuletRules configuration effective at one instant, decoded from scan's /v0/amulet-rules (see ScanClient.amuletRulesConfig).
Bridges the registry's off-ledger JSON (Daml JSON API encoding) and the gRPC Ledger API's proto values.
The custody hook: a SigningDriver whose key operations are delegated to caller-supplied suspend functions. Wrap any external signer — Fireblocks, BitGo, Dfns, an HSM, a remote co-signer — by adapting its SDK calls to the two callbacks; everything above the driver (party onboarding, interactive submission, token-standard writes) works unchanged.
Onboards external parties: parties whose signing keys are held outside the participant node (device enclave, custody provider), so the node cannot act for them unilaterally.
A holding UTXO: one contract implementing the CIP-0056 Holding interface.
Non-durable WalletStore; suitable for tests and previews.
Splice.Api.Token.HoldingV1.InstrumentId — admin party + admin-unique id.
The prepare → sign → execute flow for externally-signed transactions (Interactive Submission Service).
One open mining round from scan's /v0/open-and-issuing-mining-rounds (see ScanClient.openMiningRounds) — carries the USD price of Amulet that fees and taps convert at.
Client-side implementation of Canton's "hashing scheme version 2" for interactive submissions: recomputes prepared_transaction_hash from the raw PreparedTransaction proto so a wallet never signs a hash it did not derive itself (interactive_submission_service.proto: "clients MUST recompute the hash from the raw transaction if the preparing participant is not trusted").
The PreparedTransaction cannot be hashed (or verified) by this client.
The locally recomputed hash does not match what the node asked us to sign.
Read layer over a Super Validator's Scan API (.../api/scan).
A scan call failed (non-2xx status other than 404, or malformed payload).
Produces Canton CryptoOuterClass.Signatures over ledger-provided hashes.
JCA-backed software keys, supporting the two schemes relevant to mobile wallets: Ed25519 (Canton's default) and ECDSA P-256 (the only scheme hardware enclaves sign — Apple Secure Enclave and Android StrongBox are P-256-only). Both are accepted by the Ledger API; see crypto.proto.
Amulet-specific templates from the splice-amulet DAR.
Amulet-specific templates from the splice-wallet DAR — not part of CIP-0056, but required for the Canton Coin flows every wallet needs.
A piecewise fee rate over a USD amount — Splice's Splice.Fees.SteppedRate.
The ledger's completion for an executed submission — the proof that the command was actually committed, not merely accepted for execution.
The synchronizer usage-fee block published in AmuletRules (decentralizedSynchronizer.fees, Splice's SynchronizerFeesConfig) — what traffic costs and how much comes free.
CIP-0056 token standard identifiers and Daml value codecs.
CIP-0056 token standard client: holdings, two-step transfers, and the pending-instruction inbox — the read/write surface a wallet renders.
Splice.Api.Token.TransferInstructionV1.Transfer — the transfer specification.
How one committed update moved value relative to the wallet party — the label a wallet renders next to a history row.
A pure, deterministic preview of the fees a two-output Amulet transfer would be charged — "Fee: ~X CC" before sending. No I/O: feed it ScanClient.amuletRulesConfig and a round price from ScanClient.openMiningRounds.
The transfer-fee schedule published in AmuletRules' transferConfig — denominated in USD and converted to Amulet at the open mining round's price when charged (Splice scales the whole config by 1 / amuletPrice; scaleFees in Splice.AmuletRules).
A pending two-step transfer (contract implementing the TransferInstruction interface).
The three choices on a pending TransferInstruction — accept, reject or withdraw — each carrying its Daml choice name and the path segment the registry's choice-context endpoint uses for it.
Where a TransferInstruction stands, from the interface view's status variant.
Client for a CIP-0056 registry's off-ledger transfer-instruction API (/registry/transfer-instruction/v1/...).
A registry call failed (non-2xx status or malformed payload).
Transfer-level reading of one holdings-history update: direction, counterparty, the signed net effect on the wallet party's balance, and the memo when the transfer carried one.
Client for a validator's user-facing wallet API (.../api/validator) — the onboarding, faucet, and traffic-purchase operations a wallet app drives against its own validator, authenticated as the end user.
A validator API call failed: non-2xx status (see statusCode) or a malformed payload (statusCode is null). Taps in particular fail with 400/404 until the network has an open mining round, and 429/503 under load — all worth retrying.
Persistence for wallet identities across launches. The SDK ships InMemoryWalletStore for tests and composition; apps provide a durable implementation (SQLDelight, Room, DataStore, files) — the surface is deliberately small so that's a page of code.
Functions
The round a submission "now" would execute against — the newest round already open at at, mirroring Splice's latestUsableRound selection. Null when no round has opened yet (right after network bootstrap).
An OkHttpClient honouring the same trust anchors as the Ledger API channel, for the off-ledger REST APIs — ScanClient, ValidatorClient and TransferRegistryClient.
This transfer as the Daml Transfer record a choice argument expects; Transfer.meta becomes a Metadata record.