Package-level declarations
Types
The accounts a wallet could offer a dApp.
One thing a dApp did or tried to do, as the wallet's owner should see it.
Receives every DappActivity a session produces, synchronously on the session's path. Implementations must be quick and must not throw; the session swallows observer exceptions, because a broken log must never break a payment. Hosts persist and render; a local notification for the kinds that never reach the approver (auto-approved, refused, rate-limited) is what keeps the policy honest.
The user's answer. Anything other than Approved becomes a 4001.
The wallet UI, from the engine's point of view.
What the user is being asked to approve.
Recognises the Canton Token Standard transfer inside a dApp submission so an approver can show what moves where instead of an opaque "a transaction".
Signs an arbitrary message on behalf of an approved account.
The network a session operates on, and how to reach its JSON Ledger API.
Who is asking. Built by the transport from what it can actually attest — a WalletConnect session's peer metadata, a LAN pairing's certificate, the host app itself for the in-process case.
One dApp's session with the wallet: the CIP-0103 provider side.
Per-peer limits a wallet enforces on a dApp's transactions, checked before anything reaches the approver.
ledgerApi backed by JsonLedgerApiClient.
A process-lifetime SpendLedger, the default when a host wires a policy without persistence. Fine for tests and demos; a real wallet must persist, or every restart resets the daily cap.
Binds a DappClient straight to a DappSession in the same process.
A minimal client for Canton's JSON Ledger API, used by the dApp provider for the two things that must go over JSON rather than gRPC: interactive-submission/prepare (see JsonPrepareExecutePipeline) and the ledgerApi proxy method.
The prepareExecute pipeline: JSON prepare → verify → sign → gRPC execute.
Which ledgerApi resources a dApp may reach through the wallet.
Performs an authenticated call against the JSON Ledger API.
Everything the prepare→verify→sign→execute pipeline needs for one submission.
Prepares, verifies, signs and executes one submission.
signMessage backed by a SigningDriver.
The policy's verdict on one transaction request.
Where a wallet persists SpendReceipts.
One approved, executed spend by one peer. The ledger's receipts are the source of truth for the rolling daily cap and for the app's receipts UI, which is why they are written only after execution succeeds.