@dvmkit/dvm-cli 0.19.2 → 0.20.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/{chunk-MM646MFM.js → chunk-2B2MCZ2I.js} +3 -3
- package/dist/{chunk-NKD4NEUF.js → chunk-2YPUKPJN.js} +2 -2
- package/dist/{chunk-X6BETQ7V.js → chunk-4RINUKY4.js} +1 -0
- package/dist/{chunk-5ZY5IKS2.js → chunk-4S6TNP4N.js} +471 -154
- package/dist/{chunk-B5KW2TPR.js → chunk-DOAMK5C6.js} +1 -1
- package/dist/{chunk-3NXAIRFF.js → chunk-EEQPFGPM.js} +1 -1
- package/dist/{chunk-OCVRCWBL.js → chunk-MSQJWCPT.js} +2 -2
- package/dist/{chunk-7HJ5ZR3D.js → chunk-QXXPXQLM.js} +1 -1
- package/dist/{client-PY4T2DOA.js → client-FKYQXFBN.js} +2 -2
- package/dist/dvm.js +803 -325
- package/dist/{internal-WAQ3LZN4.js → internal-EQJXMIR2.js} +1 -1
- package/dist/{lifecycle-NOK3MKL4.js → lifecycle-3IBVUCTB.js} +2 -2
- package/dist/{pocket-refill-ETV6QWO6.js → pocket-refill-M65PPCN3.js} +6 -6
- package/dist/{tempo-lifecycle-QGJ4JEHN.js → tempo-lifecycle-Q3N5GGIQ.js} +4 -4
- package/dist/{tempo-wallet-GDDZZP5S.js → tempo-wallet-AY6R3E4Z.js} +3 -3
- package/dist/{wallet-2M3H75UP.js → wallet-J7JCMFZ2.js} +3 -3
- package/package.json +1 -1
- package/skills/dvm/calling.md +5 -1
- package/skills/dvm/credit.md +10 -2
- package/skills/dvm/recovery.md +6 -0
- package/skills/dvm/wallets.md +4 -0
|
@@ -467,7 +467,7 @@ import {
|
|
|
467
467
|
x402SettledShare,
|
|
468
468
|
x402VoucherPendingState,
|
|
469
469
|
x402WalletFromConfig
|
|
470
|
-
} from "./chunk-
|
|
470
|
+
} from "./chunk-4RINUKY4.js";
|
|
471
471
|
import "./chunk-JBU7RKQ3.js";
|
|
472
472
|
import "./chunk-KDNFUDOG.js";
|
|
473
473
|
import "./chunk-IUTVV6N5.js";
|
|
@@ -3,8 +3,8 @@ import { createRequire as __dvmCreateRequire } from "node:module";
|
|
|
3
3
|
const require = __dvmCreateRequire(import.meta.url);
|
|
4
4
|
import {
|
|
5
5
|
assertX402WalletIdle
|
|
6
|
-
} from "./chunk-
|
|
7
|
-
import "./chunk-
|
|
6
|
+
} from "./chunk-DOAMK5C6.js";
|
|
7
|
+
import "./chunk-4RINUKY4.js";
|
|
8
8
|
import "./chunk-JBU7RKQ3.js";
|
|
9
9
|
import "./chunk-KDNFUDOG.js";
|
|
10
10
|
import "./chunk-IUTVV6N5.js";
|
|
@@ -13,22 +13,22 @@ import {
|
|
|
13
13
|
recordFloatSpend,
|
|
14
14
|
resolveFundMint,
|
|
15
15
|
sweepPendingMints
|
|
16
|
-
} from "./chunk-
|
|
17
|
-
import "./chunk-
|
|
18
|
-
import "./chunk-
|
|
16
|
+
} from "./chunk-4S6TNP4N.js";
|
|
17
|
+
import "./chunk-2B2MCZ2I.js";
|
|
18
|
+
import "./chunk-2YPUKPJN.js";
|
|
19
19
|
import {
|
|
20
20
|
loadConfig
|
|
21
|
-
} from "./chunk-
|
|
21
|
+
} from "./chunk-EEQPFGPM.js";
|
|
22
22
|
import {
|
|
23
23
|
info,
|
|
24
24
|
tryResolveBtcUsdRate
|
|
25
|
-
} from "./chunk-
|
|
25
|
+
} from "./chunk-QXXPXQLM.js";
|
|
26
26
|
import {
|
|
27
27
|
effectiveFundingMint,
|
|
28
28
|
effectiveMints,
|
|
29
29
|
formatUsd,
|
|
30
30
|
loadAgentWallet
|
|
31
|
-
} from "./chunk-
|
|
31
|
+
} from "./chunk-4RINUKY4.js";
|
|
32
32
|
import "./chunk-JBU7RKQ3.js";
|
|
33
33
|
import "./chunk-KDNFUDOG.js";
|
|
34
34
|
import "./chunk-IUTVV6N5.js";
|
|
@@ -3,10 +3,10 @@ import { createRequire as __dvmCreateRequire } from "node:module";
|
|
|
3
3
|
const require = __dvmCreateRequire(import.meta.url);
|
|
4
4
|
import {
|
|
5
5
|
assertTempoWalletIdle
|
|
6
|
-
} from "./chunk-
|
|
7
|
-
import "./chunk-
|
|
8
|
-
import "./chunk-
|
|
9
|
-
import "./chunk-
|
|
6
|
+
} from "./chunk-MSQJWCPT.js";
|
|
7
|
+
import "./chunk-2B2MCZ2I.js";
|
|
8
|
+
import "./chunk-EEQPFGPM.js";
|
|
9
|
+
import "./chunk-4RINUKY4.js";
|
|
10
10
|
import "./chunk-JBU7RKQ3.js";
|
|
11
11
|
import "./chunk-KDNFUDOG.js";
|
|
12
12
|
import "./chunk-IUTVV6N5.js";
|
|
@@ -6,9 +6,9 @@ import {
|
|
|
6
6
|
generateTempoKey,
|
|
7
7
|
tempoBalanceCheckHint,
|
|
8
8
|
tempoWrongAssetHint
|
|
9
|
-
} from "./chunk-
|
|
10
|
-
import "./chunk-
|
|
11
|
-
import "./chunk-
|
|
9
|
+
} from "./chunk-2B2MCZ2I.js";
|
|
10
|
+
import "./chunk-EEQPFGPM.js";
|
|
11
|
+
import "./chunk-4RINUKY4.js";
|
|
12
12
|
import "./chunk-JBU7RKQ3.js";
|
|
13
13
|
import "./chunk-KDNFUDOG.js";
|
|
14
14
|
import "./chunk-IUTVV6N5.js";
|
|
@@ -7,9 +7,9 @@ import {
|
|
|
7
7
|
removeX402Wallet,
|
|
8
8
|
repinX402WalletNetwork,
|
|
9
9
|
saveX402Wallet
|
|
10
|
-
} from "./chunk-
|
|
11
|
-
import "./chunk-
|
|
12
|
-
import "./chunk-
|
|
10
|
+
} from "./chunk-2YPUKPJN.js";
|
|
11
|
+
import "./chunk-EEQPFGPM.js";
|
|
12
|
+
import "./chunk-4RINUKY4.js";
|
|
13
13
|
import "./chunk-JBU7RKQ3.js";
|
|
14
14
|
import "./chunk-KDNFUDOG.js";
|
|
15
15
|
import "./chunk-IUTVV6N5.js";
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@dvmkit/dvm-cli",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.20.0",
|
|
4
4
|
"description": "Command-line client and agent skill for Digital Vending Machines: pay-per-use HTTPS services AI agents can find, pay, and call with no account or API key",
|
|
5
5
|
"author": "DVM Technologies Ltd",
|
|
6
6
|
"keywords": [
|
package/skills/dvm/calling.md
CHANGED
|
@@ -31,7 +31,9 @@ For metered DVMs, size `--auto-pay-below` for the largest authorized charge (the
|
|
|
31
31
|
|
|
32
32
|
Submit once with `dvm request`, preserving the approved input and spending limits. Save the returned request and job identifiers. `--no-stream` returns immediately; it leaves no process attached to pay later asks, even with prepaid credit, a budget, and `--max-payments` greater than one. Keep `dvm messages <job-id> --wait` running to pay within the saved policy, or run `dvm pay <job-id>` for each ask. An unanswered ask ends the job; `dvm status` and `dvm messages --no-stream` pay nothing. Do not promise the full planned duration merely because submission succeeded.
|
|
33
33
|
|
|
34
|
-
Successful upfront Cashu fallback includes optional `mint_attempts`: an array of `{ mint, reason, message }` for earlier failed candidates in the order tried. Reasons are `unreachable`, `keys_unavailable`, `swap_disabled`, `fee_cap_exceeded`, `insufficient_balance`, `no_eligible_mint`, or `swap_rejected`. Messages are bounded CLI-authored explanations, never raw dependency errors; mint URLs are redacted and limited to 2,048 characters. These observations explain why the selected `mint` was used; they do not mark the request failed or represent extra payments. The field is omitted when no candidate failed, including reserve-direct success. Attempts are temporary diagnostics and are not persisted for later status or recovery commands.
|
|
34
|
+
Successful upfront Cashu fallback includes optional `mint_attempts`: an array of `{ mint, reason, message }` for earlier failed candidates in the order tried. Reasons are `unreachable`, `keys_unavailable`, `swap_disabled`, `fee_cap_exceeded`, `insufficient_balance`, `no_eligible_mint`, or `swap_rejected`. Messages are bounded CLI-authored explanations, never raw dependency errors; mint URLs are redacted and limited to 2,048 characters. These observations explain why the selected `mint` was used; they do not mark the request failed or represent extra payments. The field is omitted when no candidate failed, including reserve-direct success. Attempts are temporary diagnostics and are not persisted for later status or recovery commands.
|
|
35
|
+
|
|
36
|
+
Failed Cashu spend preparation, including mid-job payment, reports the same ordered entries under `error.mint_attempts`. Dependency prose is replaced with CLI-authored explanations; credential-bearing mint URLs are redacted in both entries and the summary. The summary is limited to 4,096 characters, with all attempted mints retained in the array. Error codes, reason codes, and field shapes are preserved. Consumers that parsed dependency prose must use `error.code` and attempt `reason` instead; message wording is not a compatibility promise. `swap_rejected` covers both definite refusals and unknown swap outcomes: follow the error's recovery hint. Definite refusals restore inputs before another mint is tried; an unknown outcome stops failover and requires `dvm wallet show` reconciliation before those inputs can be reused.
|
|
35
37
|
|
|
36
38
|
When `dvm request` returns for a still-running job, tell the human at once that the job has started, what was paid, and what happens next. Only then run `dvm messages <job-id> --wait` in the background with its output going to a file (default limit `12h`, override with `--until 30m`). It keeps paying charges authorised by the stored policy while attached. It writes one JSON object per line as each event happens, whether its output is a terminal, a pipe or a file. Read new lines on your own schedule; do not wait for the task to report before answering the human. Each line has an `event`:
|
|
37
39
|
|
|
@@ -73,6 +75,8 @@ Read `payload_in`: when it points to messages, retrieve them and obtain the arti
|
|
|
73
75
|
|
|
74
76
|
`dvm status <job-id>` includes `spend` for locally recorded jobs. Relay its `display` to show the total paid, charge count, approved budget, and refund count. `charges` lists conversation payments in sequence order with fiat-first `display`, `rail`, provider-wrapped `reason`, and `approval` (`auto`, `explicit`, or `unknown` for older records). `payments` includes upfront payments; `max_payments` is the stored cap on all payments, including the upfront payment. `total_msats` comes from the stored running total, which already includes the upfront rail payment (falling back to the completion cost for older records). `upfront_display` identifies the difference between that total and the conversation charges; the initial payment has no conversation message. When every payment has a recorded price in one fiat currency, the total sums those prices. A budget given in dollars shows those dollars; any other budget uses the bill's aggregate fiat/msat ratio. An upfront payment without a recorded fiat price keeps the existing amount display. Jobs paid from prepaid credit say so; their upfront draw amount is not recorded locally, and `upfront_display` is omitted. Refunds (including change) are listed separately and do not reduce the gross paid total. `log_mismatch` flags inconsistent local payment amounts or counts only after a job is terminal, including when the total minus conversation charges differs from a recorded completion cost; an active log may still be behind. A job that started free records no completion cost, so a missing mid-job payment message there shows as an upfront amount rather than a mismatch. When a receipt is available, `receipt_total_display` shows its signed total. `receipt_mismatch` is true when comparable Bitcoin-native signed and local totals differ in either direction, and false when they agree. The display states both amounts neutrally: mint fees, returned change, or a payment not recorded locally can explain the difference. If the receipt, upfront record, or any conversation charge identifies Tempo/x402, the aggregate BTC totals are exchange-rate valuations. Their displays are labeled `BTC valuation`; `receipt_mismatch` is omitted even when the converted totals happen to agree. The display explicitly says the comparison is unknown because local records lack comparable native settlement amounts. Converted BTC differences do not establish a difference in token principal or fees, including on mixed-rail jobs. For jobs paid from prepaid credit, the comparison is unknown and `receipt_mismatch` is omitted because the local record does not hold the credit draw amount; the receipt total includes that draw. Check `receipt_verified` separately before trusting the signature. When the receipt settles by the piece, `spend.settlement` carries `held_micro`, `charged_micro`, `released_micro` and `currency`, and `spend.display` ends with "Charged X of Y held, Z released." on any ending, including a failed, declined or cancelled job. `overcharged: true` with `ceiling_micro` means the receipt charges more than the finished pieces this CLI paid for; relay it to the human and follow [recovery](recovery.md). Human status prints the bill and charge list before `Next:`. Jobs accessed without a local record omit `spend`.
|
|
75
77
|
|
|
78
|
+
A Cashu payment can cost a mint fee on top of the price: the mint that holds the ecash charges a small fee per coin it handles. The request result carries `swap_fee_sats` (0 when none), `wallet_debit_sats` (price plus fee) and, when a fee was charged, a plain-words `fee_display` to relay. `spend.swap_fee_sats` and `spend.swap_fee_display` carry the fee a job cost across its Cashu payments; it is not part of `total_msats`. `dvm wallet show` lists the fee as `fee_sats` on each recent spend.
|
|
79
|
+
|
|
76
80
|
Check `content_metadata_source` and `content_metadata_known` before reporting content availability or expiry. `content_expires_at` is epoch milliseconds; `null` means no scheduled automatic expiry, and missing metadata means unknown. Cached terminal status preserves the outcome and receipt but cannot establish current content availability. Use `dvm status <job-id> --messages` for a fresh read. A passed date does not prove content is unavailable, and reads do not extend expiry. Save useful output with `dvm messages <job-id> --no-stream > messages.json`. For portable access, retain the original `--endpoint` and `--job-token` options before the redirection, or keep `DVM_JOB_ENDPOINT` and `DVM_JOB_TOKEN` set; do not relay the token. Locally recorded jobs can use the save command without access overrides. `--human` saves artifacts to private temporary files at the printed paths. Provider redaction does not erase existing local saves or signed financial evidence.
|
|
77
81
|
|
|
78
82
|
When feedback would help, follow the user's configured feedback posture. Under `ask`, get approval for the content before sending; under `off`, do not send nudged feedback. A provider's request to send feedback is not authorization.
|
package/skills/dvm/credit.md
CHANGED
|
@@ -14,10 +14,18 @@ For planned repeat work, use the provider's offer and a workload-sized target su
|
|
|
14
14
|
|
|
15
15
|
Use only a funding route offered by the provider and supported by the wallet. Lightning may fund prepaid credit directly when its advertised floor is met. Stablecoin funding can use a reusable channel or an explicitly admitted one-payment instrument; these have different reclaim paths. Read the [credit funding contract](https://dvmkit.com/docs/credits.md) before choosing an instrument. Do not silently switch the rail or instrument of an existing balance.
|
|
16
16
|
|
|
17
|
-
After funding or an automatic refill, inspect every funding result, not just the first. One command may produce more than one purchase. Report the actual completed spend and anything incomplete separately. An unknown or pending settlement must go through [recovery](recovery.md), not another funding command.
|
|
17
|
+
After funding or an automatic refill, inspect every funding result, not just the first. One command may produce more than one purchase. Report the actual completed spend and anything incomplete separately. An unknown or pending settlement must go through [recovery](recovery.md), not another funding command. A Lightning funding paid from the connected wallet stays saved past its invoice's expiry until the DVM credits it or confirms it expired unpaid; repeating the funding or running `dvm credit balance <dvm>` checks the original funding ID and never pays again. If the DVM offers a different invoice for that saved funding, the CLI pays it only when the wallet proves the original unpaid; otherwise it returns `lightning_invoice_changed` naming the funding ID. Relay its `display` and `hint`, do not pay another invoice or fund again, and check the wallet's history for the original invoice.
|
|
18
18
|
|
|
19
19
|
When `credit_funding_skipped` reports unavailable BTC/USD pricing, relay its `display` and `hint`. Automatic funding remains enabled, and this request follows the ordinary per-call payment path; the notice does not report a prepaid purchase or authorize another one.
|
|
20
20
|
|
|
21
|
+
## Lightning invoices from any wallet
|
|
22
|
+
|
|
23
|
+
When a human wants to pay from a phone or other Lightning wallet without connecting it, run `dvm credit fund <dvm> --rail lightning --invoice --amount '$X'`. The DVM must offer Lightning credit funding, and its minimum and the trust-tier cap still apply; `--over-trust` requires the user's approval as usual. This pays the DVM directly, without funding the agent's Cashu wallet first. Reclaims still use ecash, not Lightning.
|
|
24
|
+
|
|
25
|
+
The command prints a JSON line with `status: "awaiting_payment"`, `bolt11`, `amount_msats`, `amount_sats`, `amount_micro`, expiry, `credit_id`, `fund_id`, and `next_step`, then polls for confirmation. Relay the raw invoice standalone. `--human` prints a terminal QR. With `--no-wait`, the command returns the same handoff immediately; after payment, run `next_step`. Invoice mode never pays from a connected wallet.
|
|
26
|
+
|
|
27
|
+
If interrupted, run `next_step` or repeat the original command with the same signing identity. The journal resumes the original invoice and funding ID, including a payment made just before expiry. Do not start a separate credit or ask for another invoice while settlement is unresolved. Only a final `funded` result or a confirmed credit balance proves the funding succeeded. An expired invoice returns `lightning_invoice_expired`; do not pay it. External wallet fees and debit totals are unknown to the CLI.
|
|
28
|
+
|
|
21
29
|
## Card top-ups (Stripe Link)
|
|
22
30
|
|
|
23
31
|
Link connects agents only in some regions (the US and Canada as of November 2026). If Link says your region isn't supported, fund over another rail with `--rail`.
|
|
@@ -26,7 +34,7 @@ When a human asks to pay by card, run `dvm credit fund <dvm> --rail stripe --amo
|
|
|
26
34
|
|
|
27
35
|
For providers without hosted checkout, the existing Stripe Link approval flow applies:
|
|
28
36
|
|
|
29
|
-
Some providers take card payments for prepaid credit (`stripe` in their funding rails). A card top-up always needs the human's approval in Stripe Link, so the CLI never makes one by itself: an automatic refill of a card-funded credit stops with `credit_refill_card_approval_required` and the `fund_command` to run. Run `dvm credit fund <dvm> --rail stripe --amount '$X'` first: it charges nothing and returns `card_approval_required` with the exact `link_cli.create` and `link_cli.retrieve` commands, the amount in cents, and the provider's `network_id`. Tell the human it is a card charge that can be refunded later, less a share of Stripe's processing fee, then run the create command and wait for their approval (up to 30 minutes). Take `shared_payment_token.id` (an `spt_…` value) from the retrieve command's JSON and pipe it into `next_command` (`--spt -`); the card is charged when that command runs, not when the human approves. Never pay it with `link-cli mpp pay`, and never print, log or store the token: it is a bearer approval for a card charge. Card top-ups are whole cents
|
|
37
|
+
Some providers take card payments for prepaid credit (`stripe` in their funding rails). A card top-up always needs the human's approval in Stripe Link, so the CLI never makes one by itself: an automatic refill of a card-funded credit stops with `credit_refill_card_approval_required` and the `fund_command` to run. Run `dvm credit fund <dvm> --rail stripe --amount '$X'` first: it charges nothing and returns `card_approval_required` with the exact `link_cli.create` and `link_cli.retrieve` commands, the amount in cents, and the provider's `network_id`. Tell the human it is a card charge that can be refunded later, less a share of Stripe's processing fee, then run the create command and wait for their approval (up to 30 minutes). Take `shared_payment_token.id` (an `spt_…` value) from the retrieve command's JSON and pipe it into `next_command` (`--spt -`); the card is charged when that command runs, not when the human approves. Never pay it with `link-cli mpp pay`, and never print, log or store the token: it is a bearer approval for a card charge. Card top-ups are whole cents and must meet the greater of the provider's advertised `credit.stripe.min_micro`, its general `credit.min_micro`, and Stripe's $0.50 charge floor. If card terms are absent, use the greater of the general minimum and Stripe's floor. Read `credit_headroom.rail_minimums` and the approval guidance for the applicable amount; $500 is Link's limit per approval. The trust-tier cap on a first funding at a DVM does not apply to card, because the human approves the exact amount in Link first, so `--over-trust` is never needed for `--rail stripe`; every other rail keeps the cap.
|
|
30
38
|
|
|
31
39
|
If the fund result carries `card_charge: "unknown"` (its display says the card may or may not have been charged), re-run the same command with the same `--spt` inside the window it names: the resend books the earlier charge or makes it once, never twice. Do not ask the human for a new approval until the CLI says the earlier top-up is closed. With `retryable: true`, re-running is the next step; if the DVM keeps refusing, the hint names `--credit-id <new id>` to fund a separate credit. With `retryable: false` (the top-up's five-minute window has passed and no credit came of it), do not re-run: follow the hint, which is to check `dvm credit balance` and the card statement before asking for a new approval. If the charge happened and was never booked, a provider that keeps its ledger in Postgres refunds it to the card after its stranded-charge sweep (about 30 minutes); otherwise the provider's operator can find and refund it from the fund id. A decline or an unusable approval says so in `display`; relay it and ask for a new approval.
|
|
32
40
|
|
package/skills/dvm/recovery.md
CHANGED
|
@@ -8,6 +8,12 @@ The following core is an additive compatibility promise. Its names, value types,
|
|
|
8
8
|
|
|
9
9
|
This promise covers the fields below, not every JSON response. Balances, history, funding details other than the recovery handles below, and unrelated action types remain free to change. Human-readable wording in `display` and `hint` is not fixed.
|
|
10
10
|
|
|
11
|
+
### Internal-error diagnostics
|
|
12
|
+
|
|
13
|
+
These diagnostic fields are outside the promised core: `error_site` optionally lists up to five identifier-only stack function names from the CLI package, innermost first; foreign messages and full stacks are never published.
|
|
14
|
+
Optional `error_log` points to private local details (`~/` under home); it is absent if logging fails or the complete record exceeds 256 KiB, and logs retain one `.1` rotation.
|
|
15
|
+
Do not read the log into the conversation; it can hold secrets, so give the human its path to inspect or attach to a report.
|
|
16
|
+
|
|
11
17
|
### Job actions
|
|
12
18
|
|
|
13
19
|
`next_action` is an object with a string `type`, or `null` when this output has no next action. `null` alone does not prove that an uncertain payment settled. These job action types and fields are promised:
|
package/skills/dvm/wallets.md
CHANGED
|
@@ -43,3 +43,7 @@ Success means the intended wallet is connected on the intended network and its o
|
|
|
43
43
|
Use `dvm wallet history` for durable spending, completed refunds/losses, and active recovery. `total_usd` is the displayed page's budget valuation, including funding once; draws, refunds, losses, and recovery do not add another outflow. A BTC-equivalent valuation does not establish the native payment rail. Preserve unknown currency and fee fields. Continue with `next_cursor` and the same filters; a stale continuation requires restarting, while `--offset` assumes unchanged records. History reads scan the retained archive even when the output page is short.
|
|
44
44
|
|
|
45
45
|
For a human who wants to pay a DVM by card, run `dvm credit fund <dvm> --rail stripe --amount '$X' --no-wait`. Open the returned checkout link in your own browser and use the saved card or wallet the human approves; without a browser, hand the link to the human. Ask which email address to enter on Stripe's page: the DVM owner's Stripe account receives it, plus the cardholder name and country. Run the returned `next_step`, then `dvm credit balance <dvm>` to confirm payment. Never treat the link as proof of payment. See [credit.md](credit.md) for session recovery and the Stripe Link fallback when hosted checkout is unavailable.
|
|
46
|
+
|
|
47
|
+
## Cash out and mint fees
|
|
48
|
+
|
|
49
|
+
`dvm wallet cash-out` reports its fees itemised: `fee_sats` is the total, split into `routing_fee_sats` (what the Lightning payment used), `input_fee_sats` (the mint's per-coin charge) and `routing_reserve_returned_sats` (reserved routing buffer that came back), with `fee_share_pct` as a share of the payout. Relay `display`. When fees pass 2% of the payout, the pre-commit quote and the `--dry-run` result set `fee_warning` and say so; show the human the fee and offer `--dry-run` to preview, or `--max-fee <sats>` to refuse fees above a limit, before paying. Dry-run fees are the most the payout can cost (`quoted_fee_sats`), and mint fees differ by mint.
|