bsv-blockchain · BraydenLangley · Aug 11, 2026 · Aug 11, 2026 · Aug 11, 2026 · Aug 11, 2026
@@ -25,11 +25,12 @@ can resume a soft-expired workspace using its exact persisted inputs.
 `endpointURL` after production bundlers minify class names, so backup selection
 and make-primary flows remain stable.
 Immediate browser actions can chain wallet-managed change from a delayed
-parent; the child broadcast includes the parent BEEF so background delivery
-cannot temporarily strand the wallet balance.
-Durable permission grants finish broadcasting their internal token transaction
-before the waiting browser request resumes, keeping the grant's funding change
-available to the following wallet action.
+parent only after completed and unproven liquidity is exhausted or exact
+serialized-cost comparison proves that a pathological settled plan is larger.
+Pending funds are never hidden. IndexedDB wallets migrate exact untouched
+144-output / 32-satoshi defaults to a progressive 5,000-satoshi preference.
+Durable permission tokens retain delayed broadcast so permission approval does
+not inherit network latency.
 Opt-in remote-storage timing spans retain trace and parent-span correlation in
 the telemetry sink without adding headers to authenticated requests.
 Browser authentication accepts one verified matching UMP token as an existing

@@ -25,11 +25,12 @@ can resume a soft-expired workspace using its exact persisted inputs.
 `endpointURL` after production bundlers minify class names, so backup selection
 and make-primary flows remain stable.
 Immediate mobile actions can chain wallet-managed change from a delayed parent;
-the child broadcast includes the parent BEEF so background delivery cannot
-temporarily strand the wallet balance.
-Durable permission grants finish broadcasting their internal token transaction
-before the waiting mobile request resumes, keeping the grant's funding change
-available to the following wallet action.
+the wallet first exhausts completed and unproven liquidity and uses exact
+serialized-cost comparison only for pathological settled plans. Pending funds
+are never hidden. New and migrated wallets progressively prefer useful
+5,000-satoshi liquidity units without gathering inputs merely to create them.
+Durable permission tokens retain delayed broadcast so permission approval does
+not inherit network latency.
 Opt-in remote-storage timing spans retain trace and parent-span correlation in
 the telemetry sink without adding headers to authenticated requests.
 Mobile authentication accepts one verified matching UMP token as an existing

@@ -25,14 +25,15 @@ workspaces can resume an expired soft lease by reacquiring only their exact
 persisted inputs under the provider's advertised reservation bound.
 
 Immediate actions may use wallet-managed change from a transaction awaiting
-background broadcast. The child broadcast recursively carries the delayed
-parent BEEF, preventing queued work from temporarily hiding most of the
-wallet's spendable balance.
+background broadcast, but only after completed and unproven liquidity is
+exhausted or an over-16-input settled plan is larger by exact serialized
+transaction-plus-BEEF cost. Queued funds are never hidden.
 
-Durable permission grants finish broadcasting their internal token transaction
-before the waiting application request resumes. A broadcast failure rejects the
-grant, so the application can surface the existing error and safely retry
-without planning against temporarily reserved funding inputs.
+Durable permission grants retain delayed broadcast, avoiding network latency in
+the permission path. New and existing wallets progressively target 144 useful
+5,000-satoshi change outputs, create no more than eight outputs per action, and
+migrate no more than four fee-positive legacy fragments per action. Optional
+shaping cannot make a formerly fundable action fail.
 
 Completed `createAction` and `signAction` results expose Atomic BEEF as a
 numeric array at the public wallet boundary. The historical shape survives
@@ -208,3 +209,4 @@ See `packages/wallet/wallet-toolbox-examples/src/p2pkh.ts`, `brc29.ts`, `pushdro
 - [Wallet domain overview](./index.md)
 - [Wallet toolbox examples](./wallet-toolbox-examples.md)
 - [Conformance vectors](../../conformance/vectors.md#wallet-brc-100)
+- [Managed-change liquidity policy](https://github.com/bsv-blockchain/ts-stack/blob/main/packages/wallet/wallet-toolbox/docs/managed-change-liquidity.md)
@@ -287,7 +287,7 @@ Incident handling follows this evidence-preserving sequence:
 ### wallet-infra
 
 - Configuration: required `BSV_NETWORK`, `KNEX_DB_CONNECTION`, `SERVER_PRIVATE_KEY`; optional
-  `COMMISSION_FEE`, `COMMISSION_PUBLIC_KEY`, `ENABLE_NGINX`, `FEE_MODEL`, `HTTP_PORT`, `TAAL_API_KEY`, `WALLET_STORAGE_BIND_HOST`, `WALLET_STORAGE_MONITOR_START_TASKS`, `WALLET_STORAGE_MONITOR_STARTUP_TASK_MODE`, `WALLET_STORAGE_MONITOR_ADMIN_ENABLED`, `WALLET_STORAGE_MONITOR_ADMIN_HOST`, `WALLET_STORAGE_MONITOR_ADMIN_PORT`, `WALLET_STORAGE_MONITOR_ADMIN_ALLOWED_ORIGINS`, `WALLET_STORAGE_MONITOR_ADMIN_PRIVATE_KEY`, `WALLET_STORAGE_ADMIN_IDENTITY_KEYS`, `WALLET_STORAGE_TRUST_PROXY_HOPS`; secret-bearing
+  `COMMISSION_FEE`, `COMMISSION_PUBLIC_KEY`, `ENABLE_NGINX`, `FEE_MODEL`, `HTTP_PORT`, `TAAL_API_KEY`, `WALLET_STORAGE_BIND_HOST`, `WALLET_STORAGE_MONITOR_START_TASKS`, `WALLET_STORAGE_MONITOR_STARTUP_TASK_MODE`, `WALLET_STORAGE_MONITOR_ADMIN_ENABLED`, `WALLET_STORAGE_MONITOR_ADMIN_HOST`, `WALLET_STORAGE_MONITOR_ADMIN_PORT`, `WALLET_STORAGE_MONITOR_ADMIN_ALLOWED_ORIGINS`, `WALLET_STORAGE_MONITOR_ADMIN_PRIVATE_KEY`, `WALLET_STORAGE_ADMIN_IDENTITY_KEYS`, `WALLET_STORAGE_MANAGED_CHANGE_MAX_OUTPUTS_PER_ACTION`, `WALLET_STORAGE_MANAGED_CHANGE_MIGRATION_INPUTS_PER_ACTION`, `WALLET_STORAGE_MANAGED_CHANGE_PENDING_COMPARISON_INPUTS`, `WALLET_STORAGE_TRUST_PROXY_HOPS`; secret-bearing
   `KNEX_DB_CONNECTION`, `OTEL_EXPORTER_OTLP_HEADERS`, `SERVER_PRIVATE_KEY`, `TAAL_API_KEY`, `WALLET_STORAGE_MONITOR_ADMIN_PRIVATE_KEY`.
 - Telemetry: ESM bootstrap
   `src/telemetry.ts`, logger