Accept caller-managed trusted Cashu wallets #2

New issue

Closed

opened 2026-10-09 11:19:43 +00:00 by thesimplekid · 0 comments

thesimplekid commented

2026-10-09 11:19:43 +00:00

Owner

Problem

The library currently constructs its trusted Cashu receiving wallets and chooses their seed storage and SQLite databases. Applications that already own a CDK wallet cannot pass that wallet into satsettle, resulting in additional wallet lifecycle and storage management.

Proposed improvement

Add an Engine configuration path that accepts a caller-owned Arc<Wallet> for a configured trusted mint. The caller chooses the wallet database, seed, and other wallet configuration. Retain the managed-wallet setup as a convenient default.

A CDK wallet is configured for a particular mint and unit. Validate that a supplied wallet matches the requested trusted destination and sat-denominated payment terms. If multiple trusted mints are configured, define explicit routing rather than treating one wallet as covering every mint.

Acceptance criteria

Trusted Cashu receive, trusted-mint settlement, balance, and payout paths can use the supplied wallet.
Injected wallets do not cause Engine to create replacement wallet databases or seeds.
Recovery and idempotency continue to work across restarts with the same caller-managed wallet.
Document concurrency and ownership requirements: accepting an Arc does not by itself make concurrent use outside satsettle safe.
Tests cover mismatched mint/unit configuration and interrupted receive/payout operations.

Payment coordination storage is addressed separately by the storage-interface issue. Arbitrary untrusted source mints require the separate wallet-provider improvement; a single trusted wallet does not cover them.

This is a post-first-release improvement; no change to the current first-release persistence model is required now.

## Problem The library currently constructs its trusted Cashu receiving wallets and chooses their seed storage and SQLite databases. Applications that already own a CDK wallet cannot pass that wallet into satsettle, resulting in additional wallet lifecycle and storage management. ## Proposed improvement Add an Engine configuration path that accepts a caller-owned `Arc<Wallet>` for a configured trusted mint. The caller chooses the wallet database, seed, and other wallet configuration. Retain the managed-wallet setup as a convenient default. A CDK wallet is configured for a particular mint and unit. Validate that a supplied wallet matches the requested trusted destination and sat-denominated payment terms. If multiple trusted mints are configured, define explicit routing rather than treating one wallet as covering every mint. ## Acceptance criteria - Trusted Cashu receive, trusted-mint settlement, balance, and payout paths can use the supplied wallet. - Injected wallets do not cause Engine to create replacement wallet databases or seeds. - Recovery and idempotency continue to work across restarts with the same caller-managed wallet. - Document concurrency and ownership requirements: accepting an Arc does not by itself make concurrent use outside satsettle safe. - Tests cover mismatched mint/unit configuration and interrupted receive/payout operations. Payment coordination storage is addressed separately by the storage-interface issue. Arbitrary untrusted source mints require the separate wallet-provider improvement; a single trusted wallet does not cover them. This is a post-first-release improvement; no change to the current first-release persistence model is required now.

~~thesimplekid referenced this issue 2026-10-09 11:20:33 +00:00~~

Signet and regtest support for L402 and manual capture #8

thesimplekid referenced this issue

2026-10-09 11:20:54 +00:00

Pluggable storage, so services on PostgreSQL or with several instances can embed satsettle #6

thesimplekid referenced this issue

2026-10-09 11:20:55 +00:00

Embedding compatibility: CDK version pin and MSRV #9

thesimplekid referenced this issue from a commit

2026-10-09 12:51:43 +00:00

feat: accept caller-managed trusted Cashu wallets

thesimplekid referenced this issue from a pull request that will close it,