2026 · W47

16–22 November 2026

Fixes only: 1 release, 2 fixes

  • dvm-cli 0.19.2
1 release
dvm-cli 0.19.2

dvm-cli 0.19.2

Bug Fixes

  • credit: book card-funded credit draws and explain unusable upfront debits

  • wallet: receive Cashu tokens through stdin

View on GitHub
2026 · W46

9–15 November 2026

Card top-ups open a hosted checkout page

  • sdk 0.30.0 → 0.38.0
  • dvm-cli 0.16.0 → 0.19.1
  • dvmctl 0.17.3 → 0.20.1
  • dvm-cli 0.19.0 and sdk 0.36.0 let a caller top up prepaid credit by card through a checkout link the human opens, with no Stripe Link account needed. Breaking in sdk 0.38.0: a service offering that link tells a dvm-cli older than 0.19.0 to upgrade instead.
  • sdk 0.30.0 serves each capability a builder offers on x402 at POST /v1/x402/<capability>, so a standard x402 wallet can pay dollar stablecoins and get the result in one request.
  • Breaking in dvm-cli 0.18.0: dvm messages <job> --wait streams JSON lines instead of printing one JSON document. Act on the next_action of the last line.
  • dvm-cli 0.17.0 can cash out the agent wallet to a Bitcoin Lightning invoice, and dvmctl 0.20.0 lets a builder choose payout rails per service.
18 features
  • sdkfund card credit through a hosted Checkout page
  • dvm-clitop up prepaid credit by card through a hosted checkout link
  • dvmctladd per-service payout rail preferences
  • sdkstart without x402 routes when no x402 rail is configured
  • dvm-clistream --wait events as JSON lines
  • dvmctltell agents how their human signs in, including from another machine
  • sdkexport the diagnostic catalogue and keep span routes, events, and codes it should admit
  • dvm-cliapprove a new total budget for a running job
  • dvmctlcheck x402 routes against Coinbase's validator after deploy
  • sdkanswer 422 on the x402 route when a handler marks a failure as the caller's breaking
  • dvm-clitell the caller what is left in the agent wallet when a job ends
  • sdkoffer a refund_delay on the NUT-24 payment request breaking
  • dvm-clilet cash-out pay a Lightning invoice
  • sdkkeep idle job-message LISTEN connections active with a heartbeat
  • dvm-clihand off funding invoices without waiting
  • sdkdeclare capability channels and x402 Bazaar listings breaking
  • sdkanswer a paid x402 request at POST /v1/x402/<capability> in one response
  • sdklist x402 capabilities in discovery catalogs and own every facilitator payload
22 releases
dvm-cli 0.19.1

dvm-cli 0.19.1

Bug Fixes

  • jobs: explain unattended payment expiry

  • output: preserve command warnings on JSON errors

  • wallet: keep unpaid funding quotes until the mint confirms they are gone

View on GitHub
sdk 0.38.0breaking

sdk 0.38.0

Breaking API changes

  • On servers advertising hosted card Checkout, unpaid Stripe top-ups from identified dvm clients older than 0.19.0 return 426 client_upgrade_required with upgrade instructions instead of a Stripe Link challenge. Completed funding still replays, credential-bearing requests remain accepted, and callers with absent or invalid client headers keep the existing discovery response. See protocol-fixtures/credit-fund-stripe-upgrade-v1.json.

  • clientUpgradeRequired accepts an optional fourth argument { display, hint } for endpoint-specific upgrade instructions. Existing calls retain their default response text; this is an additive signature change. No public exports are added or removed.

Migrations

  • No database or configuration migration from 0.37.0. Agents using dvm older than 0.19.0 must upgrade with npm i -g @dvmkit/dvm-cli@latest before retrying an unpaid card top-up on a Checkout-enabled server. The new client returns a payment link the human opens; no Stripe Link account is needed.

Compatibility requirements

  • Node.js 22 or newer, unchanged. No dependency floor changes from 0.37.0. Servers without hosted Checkout and callers without a valid dvm/<semver> header retain their existing card-funding discovery behavior.

dvmctl and platform prerequisites

  • None added by this release. Existing hosted Checkout prerequisites from 0.36.0 still apply. Deploy this SDK in the DVM for the upgrade notice to reach callers.

⚠ BREAKING CHANGES

  • server: guide older card clients to hosted checkout

Bug Fixes

  • Fix an SSRF bypass in assertSafeUrl and createPinnedFetch: NAT64, IPv4-mapped, IPv4-compatible, 6to4, and Teredo addresses now apply the IPv4 denylist and additional IPv4 policy to embedded addresses. Public IPv4 destinations in the well-known NAT64 prefix remain allowed; the local-use 64:ff9b:1::/48 prefix is refused because its translation layout depends on site configuration.

  • server: block unsafe IPv4 destinations embedded in IPv6

  • server: guide older card clients to hosted checkout

Miscellaneous Chores

  • api: advance the comparison baseline to v0.37.0

View on GitHub
sdk 0.37.0breaking

sdk 0.37.0

⚠ BREAKING CHANGES

  • server: the hostingControl option, the DVMKIT_HOSTING_CONTROL_SECRET

  • server: x402 claim reservations record the presented claim

Bug Fixes

  • server: initialize settlement-report history without hosting control

Code Refactoring

  • server: remove the hosting-control layer

Breaking API changes

  • Settlement-report history no longer requires hosting control. Any host or server boot with a PostgreSQL pool and a DVM ID now creates the history, obligation and reporting-identity tables before its financial stores. A server that delivers platform reports now reserves x402 batch and Tempo session reports before each effect without control, accepts a Tempo close only from the authenticated credit drain, and requires the original reservation for payout reports while history is complete. A session or batch rail that cannot reserve reports keeps its earlier reporting and marks history incomplete; without control, so does an x402 batch rail on a database whose history is already incomplete.

  • Report ownership moves from the hosting-control row to the additive sdk_hosted_settlement_report_identity table, keyed by DVM and scope. An upgraded scope inherits its existing instance, and a boot without hosting control keeps the single scope that already owns the DVM's obligations; boot fails rather than guess when those obligations sit under several scopes or one scope names several instances. Existing databases keep an incomplete or missing history marker.

  • scope is now optional in retryHostedTempoCloseReport and writeOffHostedTempoCloseReport, and the experimental server signatures that carry the report-obligation recorder change with it. See docs/HOSTING.md.

  • A Tempo session close broadcast before the upgrade has no reservation, so recovery reports its payout once through the close intent, as a self-hosted close does. An x402 claim reservation now records the amount the claim presents, which trails the channel's stored charge until the deposit is spent, so a partly spent credit can be claimed under reservation.

  • Remove the hosting-control layer. @dvmkit/sdk/server no longer exports signHostingControl, signHostingClosure, HostingControlConfig, HostingControlCommand, HostingControlStatus, HostingClosureCommand or HostingClosureEvidence. The hostingControl option of createDVMHost and createDVMServer, the DVMKIT_HOSTING_CONTROL_SECRET and DVMKIT_HOSTING_CONTROL_SCOPE variables (now ignored, with no boot error for a partial pair), the /_hosting/control, /_hosting/status, /_hosting/closure and /_hosting/closure-certificate routes, and the drain, lease, admission and closure-certificate behavior are gone. A caller that presented a payment artifact during drain is no longer recovered by artifact hash; ordinary request-id, replay and draw recovery are unchanged. Platform clients that managed hosting through those routes must stop calling them.

  • Remove the cleanup fence from the credit ledger, Postgres job store, x402 channel and exact-settlement stores and the Tempo session and charge stores. The public CreditLedgerLike draw, grow, fund and funding-record arguments lose their hosting* fields, useHostingCleanupFence and the Tempo charge store's reserveHostedCharge and completeHostedCharge are removed, and a Tempo charge is no longer reserved before broadcast; mppx's own replay marker still guards it. A Postgres job store can delete a job and drop failed payment messages at terminal like any other. Payment-replay, request-idempotency, job-ownership, draw-recovery, refund and settlement-report checks are unchanged.

  • Report reservations are engaged only for a server that delivers platform reports (a platform URL and token, without a custom onJobCompleted), and an x402 batch rail on a database whose history is already incomplete never reserves. Initialization no longer creates or reads sdk_hosting_control, sdk_hosting_admissions, sdk_hosting_nonces or sdk_hosted_tempo_charge_intents, nor the credit_invoices admission and database-time columns; existing databases keep them unused, and nothing is dropped. An upgraded scope inherits its reporting instance from its obligations alone. Before upgrading, confirm that no database reported under default and later ran hosting control under another scope: boot fails rather than choose between those scopes. See docs/HOSTING.md.

View on GitHub
dvmctl 0.20.1

dvmctl 0.20.1

Bug Fixes

  • deps: advance runtime and scaffold SDK to 0.37.0

View on GitHub
sdk 0.36.0breaking

sdk 0.36.0

Features

  • server: fund card credit through a hosted Checkout page

  • Add opt-in hosted Stripe Checkout for prepaid card credit. Set DVMKIT_STRIPE_CHECKOUT_SUCCESS_URL to an HTTPS success page and grant the restricted key Checkout Sessions: Write. The menu advertises credit.stripe.checkout: true; signed fund { method: "stripe", via: "checkout", fund_id, amount_micro } requests return a hosted URL with HTTP 202 and poll into normal funded credit. The token path is unchanged. See protocol-fixtures/credit-fund-stripe-checkout-v1.json.

  • Initialize additive stripe_checkout_sessions and stripe_checkout_store_identity tables. Booking and the existing card accounting share one transaction; recovery refunds paid, unbooked sessions after 24 hours. Terminal checkout_expired prevents late booking once refund recovery has claimed a session. Upgrade every process sharing the Checkout store before enabling the new URL; keep Checkout-aware recovery running until all recorded sessions resolve before rolling back.

  • Scope Checkout metadata and idempotency to the server's DVM identity and a durable random store namespace. Remove session adoption; an unshown create expires after 30 minutes without account-wide search or refund. Reject fund ids over 200 characters and return terminal causes for Stripe permission/request failures. Checkout uses the account's API version.

  • Run Stripe outside database connections, reserving create/refund work with short leases and booking with a nonwaiting compare-and-set transaction. Busy polls return retryable errors. Recovery backs off per row and orders work by its next attempt time. Hosting closure now blocks unresolved Checkout sessions and releases terminal unbooked admissions.

Breaking API changes

  • Server declaration fingerprints add optional Checkout configuration, fund.via, and credit.stripe.checkout, plus the Postgres Checkout store factory and its transaction contract. Existing token-only rail implementations remain compatible. Custom Checkout stores must serialize session transitions and supply the same transaction used for booking, payment markers, and deposit outbox writes; the provided Postgres store implements this contract. Checkout stores now also require a durable namespace, lease/scheduling fields, and nonwaiting locks. Resolve sessions created by earlier experimental Checkout implementations before upgrading; their unscoped metadata cannot be safely adopted or booked. Upgrade all processes sharing the store together.

Bug Fixes

  • server: preserve accounting for partial x402 claims

  • skip excluded payment rail initialization

  • Retry internal Checkout bookkeeping on brief row contention without queueing client booking polls. A session-id save failure also releases its create lease when possible. Abandoned Checkout recovery uses dispute status: won refunds, lost retires the unbooked obligation with a durable reason and releases hosting closure, and open disputes back off. Session read 403/404 failures emit distinct catalogued operator diagnostics with the session id; unresolved obligations remain intact.

Miscellaneous Chores

  • api: advance the comparison baseline to v0.35.2

View on GitHub
dvm-cli 0.19.0

dvm-cli 0.19.0

Features

  • credit: top up prepaid credit by card through a hosted checkout link

View on GitHub
dvm-cli 0.18.0breaking

dvm-cli 0.18.0

⚠ BREAKING CHANGES

  • messages: dvm messages <job> --wait no longer prints a single JSON document. Read stdout line by line: act on the next_action of the last line (event: "result"), or handle its error (event: "error"). Collect messages and auto-payments from the message and payment lines instead of the removed messages and auto_payments arrays.

Features

  • messages: stream --wait events as JSON lines

  • pay: approve a new total budget for a running job

Bug Fixes

  • budget: hold a dollar budget to dollar-priced asks in dollars

  • credit: show the prepaid-credit suggestion once a week per DVM, only after a paid request

  • messages: state the true reason in wait, budget and credit next steps

View on GitHub
dvm-cli 0.17.0

dvm-cli 0.17.0

Features

  • tell the caller what is left in the agent wallet when a job ends

  • wallet: let cash-out pay a Lightning invoice

View on GitHub
dvm-cli 0.16.0

dvm-cli 0.16.0

Features

  • wallet: hand off funding invoices without waiting

Bug Fixes

  • compare USD quote limits across payment rails

  • credit: bind x402 settlement state to the paid channel

  • credit: suggest wallet invoices for Lightning funding refusals

  • preserve accepted job access when local saves fail

View on GitHub
sdk 0.35.2

sdk 0.35.2

Bug Fixes

  • server: claim earned x402 vouchers during shutdown

  • Reusable x402 channels make one final earned-draw-capped claim during shutdown, without transferring the claimed funds. DVMKIT_X402_SHUTDOWN_CLAIM_MS bounds the attempt (default 3000 ms); an incomplete claim emits x402_shutdown_claim_incomplete and shutdown continues. A timeout does not establish whether an already submitted transaction landed.

View on GitHub
sdk 0.35.1

sdk 0.35.1

Behavior changes

  • A server whose environment has no DVMKIT_X402_PAY_TO now starts without an x402 rail even when DVMKIT_X402_BATCH_SETTLEMENT=true and the rest of the batch-settlement settings are present; it used to refuse to start with DVMKIT_X402_BATCH_SETTLEMENT requires DVMKIT_X402_PAY_TO. A hosted platform turns x402 off by removing only the payout address, so the stored settings, private keys included, no longer stop the DVM. The server logs one x402_env_ignored warning naming the x402 variables it ignored, never their values, and behaves as any server without a rail: x402 capabilities answer 503 x402_not_offered after the x402_rail_missing warning, and /v1/job serves as usual. A present but malformed DVMKIT_X402_PAY_TO still refuses to start, as does a contradictory bundle such as DVMKIT_X402_SELF_RELAY_KEY without DVMKIT_X402_BATCH_SETTLEMENT=true.

Bug Fixes

  • server: start without x402 when the payout address is missing

Miscellaneous Chores

  • api: advance the comparison baseline to v0.35.0

View on GitHub
sdk 0.35.0breaking

sdk 0.35.0

Breaking API changes

  • StreamableJobStore.getMessages accepts an optional limit for pages in ascending sequence order after deduplication. This is additive: callers that omit it retain full-history reads, and existing custom stores remain compatible. Custom stores can honor the limit to stop durable reads early when an inline result exceeds the message byte cap.

Behavior changes

  • A server whose capabilities are offered on the x402 channel but which has no x402 rail (no x402 option, and none from createDVMHost's options, DVMKIT_X402_PAY_TO or the mounted DVM's DVMConfig.x402) now starts instead of refusing to. It logs one x402_rail_missing warning naming the affected capabilities, answers each POST /v1/x402/<name> with 503 x402_not_offered (retryable: false) and a hint that x402 is not configured for this DVM, never a 402, leaves those capabilities out of /v1/info's x402_capabilities, and drops x402 from the payment methods /v1/info and /v1/quote advertise even when paymentMethods lists it. Its /v1/job capabilities and other payment rails serve as usual, in production and devMode alike. The other x402 boot refusals still stop the server with or without a rail: a paymentMethods list that leaves out "x402", a missing or invalid DVMKIT_PUBLIC_URL outside devMode, a pricing currency other than USD, and a deadline over DVMKIT_X402_RESPONSE_LIMIT_MS (counted with the default facilitator timeout when there is no rail). A descriptor's DVMConfig.x402 that a direct createDVMServer call was not given still refuses to start, and the challenge-size check still runs once a rail is configured.

Features

  • server: start without x402 routes when no x402 rail is configured

Bug Fixes

  • server: bound inline result message reads

Documentation

  • sdk: describe the x402 deadline and env-configured rail accurately

  • server: narrow the claim about a rail configured later

Miscellaneous Chores

  • api: advance the comparison baseline to v0.34.0

View on GitHub
dvmctl 0.20.0

dvmctl 0.20.0

Features

  • add per-service payout rail preferences

View on GitHub
dvmctl 0.19.0

dvmctl 0.19.0

Features

  • auth: tell agents how their human signs in, including from another machine

Bug Fixes

  • admin: support DVM mount prefixes

View on GitHub
dvmctl 0.18.0

dvmctl 0.18.0

Features

  • deploy: check x402 routes against Coinbase's validator after deploy

View on GitHub
sdk 0.34.0breaking

sdk 0.34.0

⚠ BREAKING CHANGES

  • server: answer 422 on the x402 route when a handler marks a failure as the caller's

Features

  • observability: export the diagnostic catalogue and keep span routes, events, and codes it should admit

  • server: answer 422 on the x402 route when a handler marks a failure as the caller's

Miscellaneous Chores

  • api: advance the comparison baseline to v0.33.0

Breaking change details

  • SDKJobContext.fail's options gain one optional field, callerFault, and CancelContent gains the optional caller_fault: true. Both are additive; no migration is needed, and a handler that does not pass callerFault behaves as before.

Release notes

  • @dvmkit/sdk/internal now exports DIAGNOSTIC_CATALOGUE, the deep-frozen diagnostic catalogue span projection reads, with its type DiagnosticCatalogue. It is the list-valued part of what projection admits (route templates, events, error codes and the other lists), so a platform can read those lists instead of keeping its own copy; code-defined rules, such as service names, event-scoped fields and pattern-checked fields, are not included. DIAGNOSTIC_CATALOGUE_VERSION still changes only with the catalogue's format; compare the lists to detect an addition.

  • The diagnostic catalogue now admits the audit event admin.withdrawal_finalize and the error code screenshot_unavailable. Before, span projection stored the event under diagnostic.unknown and the error code as unknown_error.

  • A dvm.request span from a DVM served under a host mount prefix now records http.route relative to the mount, so /feed/v1/job/<id> is stored as /v1/job/:id and a request for the mount itself as /. Before, the span carried the full path, which matched no route template, so every route of a mounted DVM was stored without one. A mounted DVM also now skips the span for /health, /healthz and internal /_ paths under its mount, as a DVM served at the root does; before, those requests each produced a dvm.request span. A DVM served at the root records the same spans as before.

  • A dvm.request span for the x402 route, POST /v1/x402/<capability>, now keeps its http.route as the template /v1/x402/:capability when the span is stored. Before, the diagnostic catalogue had no template for the route, so the projection dropped the attribute and stored x402 requests could not be counted by route.

  • A handler can now mark a failure as the caller's with ctx.fail(reason, { callerFault: true }), for a request the service could not serve because of what it asked for, such as a URL the fetcher refuses or a page that does not exist. On the x402 route, POST /v1/x402/<capability>, such a failure answers 422 instead of 500, with the same body (status: "failed", reason, display, hint, charge_outcome: "not_charged") and no PAYMENT-RESPONSE, so the caller sees a 4xx instead of a 5xx. 422 rather than 400, because the x402 v2 HTTP transport reserves 400 for an invalid or malformed payment payload. The mark is stored on the job's final cancel message as caller_fault: true, so the route reads it from the job record on any machine and a /v1/job reader sees it in the messages. Without the mark nothing changes: a failed handler still answers 500, a runtime-bound failure 503, and /v1/job responses keep their status. The option moves no money on any rail. { refund: true } was documented as a caller-fault annotation, but the server never read it; the documentation now says it has no effect on the job and is not recorded on it. The test context still exposes it as refundRequested. See docs/PROTOCOL-NOTES.md#the-x402-channel-route and the callerFault row of protocol-fixtures/x402-route-v1.json.

View on GitHub
sdk 0.33.0breaking

sdk 0.33.0

⚠ BREAKING CHANGES

  • server: offer a refund_delay on the NUT-24 payment request

Features

  • server: offer a refund_delay on the NUT-24 payment request

Miscellaneous Chores

  • api: advance the comparison baseline to v0.32.0

Breaking change details

  • CashuConfig and ResolvedCashuConfig gain one optional field, advertiseRefundDelay, off by default. The type changes are additive; no migration is needed.

  • For every DVM, with or without the option: a Cashu proof secret longer than 1024 characters is now refused as lock_not_exclusive, where it was not_p2pk_locked, and the lock_not_exclusive hint now names refund_delay among the allowed tags and the 1024-character limit. A client that matches on either should expect the new values.

Release notes

  • A NUT-24 payment request can now invite the wallet to add a refund path. With cashu.advertiseRefundDelay: true, the X-Cashu request on an unpaid 402 carries ["refund_delay", "<seconds>"] in nut10.t, where <seconds> is the lock floor the DVM enforces on the paid retry plus 600 seconds for the round trip. A wallet that honours the tag can lock with a locktime that far ahead and a refund key of its own, so a payment the DVM never redeems returns to the payer. The option is off by default, and with it off the request is byte-for-byte unchanged. Independently of the option, a proof whose secret carries a copied refund_delay tag is now accepted and judged as if the tag were absent; any other tag outside NUT-11's list is still refused, as is a repeated tag. A proof secret longer than 1024 characters, the default limit a Nutshell mint redeems, is now refused as lock_not_exclusive with a message naming its length; before, the cashu-ts parser refused it as not_p2pk_locked. The lock_not_exclusive hint now names refund_delay among the allowed tags and the 1024-character limit. See docs/PROTOCOL-NOTES.md#nut-24-payment-requests.

View on GitHub
sdk 0.32.0

sdk 0.32.0

Features

  • server: keep idle job-message LISTEN connections active with a heartbeat

Bug Fixes

  • server: catch up job subscriptions after reconnect

  • server: preserve mount paths in schema hints

Miscellaneous Chores

  • api: advance the comparison baseline to v0.31.1

Release notes

  • The Postgres job-message LISTEN connection now sends SELECT 1 on itself every five minutes while idle, so a database proxy that closes connections after 30 minutes without queries no longer recycles it on a routine schedule. A failed heartbeat reconnects and catches up like any other lost connection; the heartbeat does not replace that catch-up, which still covers failovers, deploys and network interruptions. ListenChannel gains an opt-in heartbeat option (true for five minutes, or { intervalMs }); callers that do not set it behave as before.

  • Postgres job-message subscribers catch up after the LISTEN connection reconnects, and notification subscribers wake to recheck payments and cancellation. Reconnects log their downtime; connection-loss, failed-connect and pool-error diagnostics retain approved Postgres and socket error codes without logging error text or credentials.

View on GitHub
dvmctl 0.17.3

dvmctl 0.17.3

Bug Fixes

  • deploy: report missing handlers as handled errors

View on GitHub
sdk 0.31.1

sdk 0.31.1

Bug Fixes

  • server: allow host-supplied x402 rails for capability channels

Miscellaneous Chores

  • api: advance the comparison baseline to v0.31.0

Release notes

  • Builders can offer capabilities on the x402 channel without setting DVMConfig.x402 when the host supplies the rail through its x402 option or DVMKIT_X402_PAY_TO and related environment variables. The server still refuses to start without an x402 rail and checks the challenge size with its resolved configuration at boot.

View on GitHub
sdk 0.31.0breaking

sdk 0.31.0

⚠ BREAKING CHANGES

  • server: LightningReceive gains ensureFresh(), and the railHealth option of LightningReceiveConfig gains an optional ensureFresh(). Both are additive; declarations that reference these types change signature with them.

Bug Fixes

  • server: keep Lightning in the credit funding menu after the DVM has been idle

Breaking change details

  • LightningReceive (experimental, @dvmkit/sdk/server) gains ensureFresh(), which a custom host that builds its own funding menu can await before reading available(). The railHealth object accepted by LightningReceiveConfig gains an optional ensureFresh(), returning a promise to wait on or undefined when there is nothing to wait for; existing implementations without it keep working and are never waited on. Both are additive.

Release notes

  • Lightning no longer drops out of credit.funding on the first request after a DVM has been idle. Building a funding menu (/v1/info, /v1/quote, a 402's credit block and /v1/credit) now waits up to 2 seconds, shared by concurrent requests, for a refresh of Lightning health that would otherwise withhold the rail on old evidence: a platform rail-health observation past its staleness ceiling, a platform routable: false older than its 5-minute pull interval, or an unreachable receive wallet whose last probe is past its 60-second cache. A refresh that takes longer leaves the menu answering from the cached state, as before, and lands for the next request. A healthy receive wallet now stays listed through one failed background get_info probe, which logs lightning_receive_probe_failed; the next request sends a confirming probe, and a second consecutive transport failure marks the wallet unreachable. A transport failure while issuing or checking an invoice still marks it unreachable at once, and permission refusals are unchanged. A stale but healthy observation is still answered without waiting and revalidated in the background. Each platform rail-health pull attempt is now abandoned after 2 seconds, so a hung pull no longer stops later refreshes.

View on GitHub
sdk 0.30.0breaking

sdk 0.30.0

⚠ BREAKING CHANGES

  • declare capability channels and x402 Bazaar listings

  • server: a name or channels key on a capability entry, previously ignored, now takes effect, so it either changes the capability's published name or fails configuration with a message naming the field.

  • x402: bound every caller-facing settle response and cap the x402 deadline at the gateway's limit

  • server: processX402BatchResponseForWallet requires channelId, and processX402BatchResponse drops the answer's channel state when no channel was passed or recorded by createX402BatchPayment.

Features

  • declare capability channels and x402 Bazaar listings

  • server: answer a paid x402 request at POST /v1/x402/<capability> in one response

  • server: list x402 capabilities in discovery catalogs and own every facilitator payload

Bug Fixes

  • server: refuse interactive asks on deferred x402 jobs and reserve x402d credit ids

  • x402: bound every caller-facing settle response and cap the x402 deadline at the gateway's limit

Miscellaneous Chores

  • api: record the job type's handler deadline in the declaration surface

Breaking change details

  • processX402BatchResponseForWallet (unstable @dvmkit/sdk/internal caller entry) now requires channelId, the pending funding's channel, and persists the answer's channel state only for that channel. processX402BatchResponse and the cooperative refund likewise drop a channel state they cannot bind to a known channel, and drop one whose amounts are not uint256 values, instead of storing it unchecked. Pass channelId from the journalled pending funding.

  • A name or channels key on a capability entry now takes effect. JavaScript builders who left either key on an entry, where it was previously ignored, either change the capability's published name or fail configuration with a message naming the field.

Release notes

  • Every PAYMENT-RESPONSE and X-PAYMENT-RESPONSE the server sends now carries only success, transaction, network, payer and an errorReason of at most 128 characters from the facilitator's settle answer, as the x402 route's already did: upfront exact payment on /v1/job, a payment recovered from a stored settlement, prepaid-credit funding and the reusable-channel drain on /v1/credit previously sent the facilitator's whole answer, so its errorMessage, extensions or padding reached the caller and could push the header past what a proxy accepts. A reusable-channel answer on /v1/credit keeps extra.channelState, reduced to channelId, balance, totalClaimed and chargedCumulativeAmount, which the payer's client reads; one that names a channel other than the payment's voucher, carries an amount above the uint256 maximum, or is otherwise malformed is dropped and logged as x402_settle_channel_state_dropped, because the client keys its channel records by that id and would otherwise rewrite another channel's balance. encodeSettleResponseHeader applies the same projection; pass the voucher's channelId to keep the channel state. On the paying side, processX402BatchResponse and the cooperative refund persist an answer's channel state only for the channel the payment was for: the one createX402BatchPayment signed, or the channelId passed to processX402BatchResponse or (now required) processX402BatchResponseForWallet; with no known channel the answer's channel state is dropped. See docs/PROTOCOL-NOTES.md#the-x402-channel-route.

  • New server variable DVMKIT_X402_RESPONSE_LIMIT_MS: the longest the gateway in front of the server waits for response headers, less any margin. When it is set, the server refuses to start if any x402 capability's maxRuntimeSeconds × 1000 plus its facilitator timeout exceeds it, because the gateway would answer 504 while the job could still finish and settle, leaving the caller charged without the result; devMode logs x402_route_response_limit_exceeded instead. A value that is not a positive whole number refuses to start. Unset, nothing changes. See the x402 route.

  • An x402 listing's schema may not use $ref or $id as a property name, a dependency name, or a key inside const or enum data; the catalog's validator reads any such key as an external reference, so the server keeps refusing to start with such a listing. This is now documented.

  • A capability offered on the x402 channel with a listing now declares it on its route's v2 PAYMENT-REQUIRED: a resource with the listing's description, mimeType, serviceName, tags and iconUrl, and an extensions.bazaar for a POST with a JSON body that upstream's discovery validation accepts. The resource URL is the route's own address, including the host's mount prefix, or listing.resourceUrl when set; payment stays bound to the route's own address. The v1 body carries no listing, and an unlisted capability declares none. Every payload the server forwards to a facilitator on verify or settle now carries the server's own resource and extensions in place of whatever the caller sent, because catalogs list from that payload: on the route, on /v1/job (deferred and upfront exact), on /v1/credit and mid-job top-ups, and on reusable-channel payments, whose recorded settlements now store and resend resource.url /v1/credit with no extensions. A settlement recorded before this release is read the same way, so the caller's identical retry still recovers it and every resend carries the server's values. A v1 payload carries neither field. The route's PAYMENT-RESPONSE, and the one GET /v1/job/:id repeats for a deferred x402 job, now carry only success, transaction, network, payer and an errorReason of at most 128 characters; a facilitator's errorMessage, extensions, amount and any other field stay server-side. The route's address drops one trailing slash from a mount prefix, matching where the route is served. A facilitator's EXTENSION-RESPONSES header is logged per extension as x402_facilitator_extension_response, every status including processing, with a rejection's reason, up to eight per answer and a count of the rest on x402_facilitator_extension_responses_truncated, and is never returned to callers. A facilitator refusal reported as facilitator_status_<code> also logs x402_facilitator_request_refused with the facilitator's errorMessage, capped at 256 printable characters and never sent to callers. /v1/info adds x402_capabilities, which lists each capability offered on x402 with its route url (including the mount prefix), its flat body schema and its price, apart from the unchanged capabilities map, so an x402 fetch is not mistaken for a /v1/job fetch. A host now tells each server its mount prefix at creation, so the route's resource, the listing's default resourceUrl and the boot-time PAYMENT-REQUIRED size check all include it. The server now refuses to start, or in devMode starts with a warning, when a capability is offered on x402 but no paid route request could succeed: no durable x402 settlement store (x402_route_settlement_store_missing), a pricing currency other than USD (x402_route_currency_unsupported), or x402.dualServe: false (x402_route_dual_serve_off). Diagnostics now attribute capabilities offered only on x402 by name, and request spans carry channel (job or x402). See docs/PROTOCOL-NOTES.md#the-x402-channel-route, protocol-fixtures/x402-listing-v1.json and protocol-fixtures/x402-info-v1.json.

  • POST /v1/x402/<capability> now serves each capability offered on the x402 channel to stock x402 clients, which pay and get the result in one unsigned request. The body is the definition's input. An unpaid request gets a 402 quoted from its body; on a listed capability an empty or invalid unpaid body, such as the {} a discovery validator sends, is quoted from listing.example and runs nothing. A paid request with an invalid body, a body carrying pubkey, signature, timestamp, nonce or auth_statement, or a Cashu or Tempo payment answers 400 before anything is verified or run, and ctx.auth is never set on this channel. The 402's resource is DVMKIT_PUBLIC_URL's origin, then the host's mount prefix, if any, then /v1/x402/<capability>, whatever query string or path spelling the request used. A paid request runs through the unsigned deferred-x402 path and answers once, within the capability's maxRuntimeSeconds plus x402.facilitatorTimeoutMs from its arrival; the handler is stopped once maxRuntimeSeconds from arrival has passed, so verification time counts against it, and a request whose verification used the whole bound runs nothing: 200 with the result, charge_outcome: "charged" and the settlement headers; 500 or 503 with charge_outcome: "not_charged" when the job failed, ran out of time, or finished with no time left to settle; 402 with a PAYMENT-RESPONSE of success: false when the payment did not go through; or 202 with the job token, charge_outcome: "unknown", Retry-After and a hint not to pay again when the settlement outcome is still unknown. A settlement starts only while a full facilitator timeout remains: an authorization not yet sent by then is released unspent, while one already sent is retried by the next read of the job. Results up to 1 MiB of messages come inline. x402_payer_busy gains Retry-After and a hint. The route's CORS exposes PAYMENT-REQUIRED, PAYMENT-RESPONSE, X-PAYMENT-RESPONSE and Retry-After, and every response naming a job carries DVM-Job-Identity-V1. A name not offered on x402 answers 404, and /v1/job keeps refusing x402-only names. The server now refuses to start when its x402 route could not be served: no x402 configuration, a paymentMethods list (including a host-level override) without "x402", a PAYMENT-REQUIRED header over 7 KiB at the real DVMKIT_PUBLIC_URL, or, outside devMode, no valid DVMKIT_PUBLIC_URL, since the caller's Host header would otherwise name the payment resource; devMode uses the request's origin and logs x402_route_origin_from_request once. Jobs record the channel they were created on, so an x402 fetch and a dvmkit-protocol fetch each run their own definition, including after a restart, and terminal, revenue, cost and paid-death reports carry channel: "x402" for x402 jobs. JobRecord gains an optional channel, and Postgres initialization adds the nullable jobs.channel column; existing rows read as dvmkit-protocol jobs. A custom JobStore must persist channel: one that drops it runs a restarted x402 job through the dvmkit-protocol definition of the same name, or fails it when there is none. Upgrade every instance that shares a database before any of them serves x402 channel jobs, because an older instance ignores jobs.channel when it reactivates a job and does the same. The payment_authorization_too_short message now repeats the authorization's validBefore only when it is at most 16 digits. See docs/PROTOCOL-NOTES.md#the-x402-channel-route and protocol-fixtures/x402-route-v1.json.

  • ctx.prompt now rejects, and ctx.sendMessage("prompt", ...) and ctx.sendMessage("payment-request", ...) throw immediately on unsigned x402 jobs whose authorization settles only on success, matching the existing ctx.requestPayment guard. An uncaught error in onJob fails the job and releases the authorization without settlement; a throw in an event callback returns an error to that message request. Caller-chosen credit ids starting x402d: are refused like other reserved credit ids, so a prepaid draw cannot be mistaken for a deferred authorization. Signed jobs and unsigned Cashu jobs retain their interactive asks.

  • Capabilities can now declare the channels they are offered on with channels. Leaving it unset keeps today's behaviour: the dvmkit protocol (/v1/info, /v1/quote, /v1/job) only. channels: { job: false, x402: {} } offers a definition only to stock x402 clients, which will pay and call it in one unsigned POST /v1/x402/<name>; channels: { job: true, x402: {} } offers one definition on both. Declaring x402 requires job to be stated as true or false, so adding x402 never silently takes a capability off /v1/job. A capability on the x402 channel must set maxRuntimeSeconds and a fixed price or an onQuote (the 402 names its amount before the handler runs, so a free capability or one priced only by rates is refused), the DVM must configure x402, and an explicit paymentMethods list must include "x402". A DVM may offer every capability on x402 alone, which leaves DVMDescriptor.capabilities empty. Names are unique within a channel, and a capability entry's new name field (default: its key) lets a dvmkit-protocol fetch and a separate, bounded x402-only fetch with its own input, handler and price coexist; configuration errors name the entry key when it differs from the published name. channels.x402.listing optionally publishes the capability in x402 Bazaar discovery catalogs, and is frozen at configuration. The listing's body schema is the capability's input converted to JSON Schema, or listing.inputSchema when set, which also stands in for an input Zod cannot convert; its local $refs are moved onto the schema's nested location in the discovery extension so upstream validation resolves them. The server refuses to start when a listing's description exceeds 500 characters, its serviceName, tags or iconUrl exceed the facilitator's limits, its schema has any $id, a non-local $ref, or a $ref that names nothing, its example fails the input schema, or its encoded PAYMENT-REQUIRED header would exceed 7 KiB (8 KiB less 1 KiB for the paid retry's PAYMENT-SIGNATURE echo). x402 reserves the signed-request field names for unsigned callers, so the configuration-time signed-envelope check applies only to dvmkit-protocol definitions, an x402 definition may declare those fields only when it is also on /v1/job under auth, and there they must be optional or preserved as unknown fields. DVMDescriptor.capabilities lists only dvmkit-protocol definitions, and DVMDescriptor.x402Capabilities lists x402-channel ones. @dvmkit/sdk adds the CapabilityChannels, X402ChannelConfig and X402Listing types. Listings are not yet emitted on the route's 402.

View on GitHub
2026 · W45

2–8 November 2026

Prepaid credit can be bought with a card

  • sdk 0.21.1 → 0.29.0
  • dvm-cli 0.12.1 → 0.15.3
  • dvmctl 0.15.0 → 0.17.2
  • dvm-cli 0.13.0 and sdk 0.22.0 let a caller fund prepaid credit by card through Stripe Link. Unused card credit is refunded to the card, less a share of Stripe's fee in proportion to the refund.
  • Breaking in sdk 0.25.0: the card top-up minimum defaults to $5 instead of $0.50. A builder can set another minimum with DVMKIT_STRIPE_MIN_USD.
  • Breaking in sdk 0.23.0: work a service asks to be paid for mid-job is charged by the piece. Each payment buys the next piece, and a caller's cancel pays for the piece in progress.
  • dvm-cli 0.14.0 hands unpaid payment requests to the agent to decide, and adds dvm decline to turn one down.
21 features
  • sdkallow an opt-in spend-capable Lightning receive connection
  • dvm-cliexempt card top-ups from the first-contact trust cap
  • dvmctladd DVM discovery visibility controls
  • sdkadd Fly keepalive during handler execution
  • dvm-clienforce CLI error-code compatibility
  • dvmctloffer deployment after a paid service works locally
  • sdkenforce public signature release disclosures
  • dvm-clistabilize core job recovery contracts
  • dvmctlsupport explicit refund park capability
  • sdkinclude paid-piece totals in terminal evidence
  • dvm-clihand unpaid asks to the agent and add dvm decline
  • dvmctlPin the CLI runtime and new scaffolds to SDK 0.21.1. Separately installed project dependencies are not upgraded automatically.
  • sdksupport handler replay tests and typed capabilities
  • dvm-clifund and refund prepaid credit by card through Stripe Link
  • dvmctlpoint builders to the Discord from errors and the build-dvm skill
  • sdkdefault the card top-up minimum to $5 and let builders set it breaking
  • sdkattribute card-credit charges to the server identity
  • sdkcharge mid-job work by the piece
  • sdksettle part of a credit draw
  • sdkfund prepaid credit by card through Stripe shared payment tokens
  • sdkrefund card-funded credit to the card
23 releases
sdk 0.29.0breaking

sdk 0.29.0

⚠ BREAKING CHANGES

  • auth: configureDVM now rejects, at configuration time, an authenticated capability whose object input schema omits the signed-envelope fields. A DVM with such a schema stops booting instead of answering callers with a signature error. Wrapped schemas that strip supplied fields return a builder-facing HTTP 500 auth_error.

  • The public signature gate also flags these optional additions; existing code compiles unchanged: lightning.allowSpend on the Lightning receive configuration (default false, also read from DVMKIT_NWC_RECEIVE_ALLOW_SPEND) and the LightningReceive.allowSpend getter, which reach DVMConfig, configureDVM, DVMDescriptor, isConfiguredDVMDescriptor, serve, createDVMHost, DVMHost, DVMHostOpts, JobManager, JobManagerOpts, handleCreditRequest, CreditRouteDeps, LightningReceive and LightningReceiveConfig. The x402 settlement names the gate also lists (createX402BatchSettlementServer, CreateX402BatchSettlementServerOpts, MemoryX402ExactSettlementStore, PostgresX402ExactSettlementStore, X402ExactSettlementAttempt, X402ExactSettlementEvidenceReader, X402ExactSettlementServer, X402ExactSettlementServerOpts, X402ExactSettlementStore and X402SettlementEvidenceReader) carry the 0.28.0 changes disclosed there; 0.29.0 does not change them.

Migrations

None. No schema change.

Compatibility requirements

Unchanged: Node range and dependency floors are the same as 0.28.0.

dvmctl and platform prerequisites

None. A spend-capable receive connection is refused at boot unless the builder sets DVMKIT_NWC_RECEIVE_ALLOW_SPEND=true.

Features

  • server: allow an opt-in spend-capable Lightning receive connection

Bug Fixes

  • auth: validate signed envelope preservation

Release notes

  • Authenticated capabilities now reject object input schemas that omit signed-envelope fields at configuration time. Wrapped schemas that remove supplied fields return a builder-facing HTTP 500 auth_error instead of blaming the caller's signature. Declare pubkey, signature, timestamp and nonce or preserve unknown fields; genuine signature failures retain their HTTP 401 response. See protocol-fixtures/auth-schema-invalid-v1.json.

View on GitHub
dvmctl 0.17.2

dvmctl 0.17.2

Bug Fixes

  • auth: align browser sign-in guidance and session labels

View on GitHub
sdk 0.28.0breaking

sdk 0.28.0

⚠ BREAKING CHANGES

  • x402: X402ExactSettlementAttempt["outcome"] (@dvmkit/sdk/server) gains "pending", recorded when a facilitator answers settlement_pending. Code that switches exhaustively over that union must handle the new value. No other public signature loses or narrows anything.

  • The public signature gate also flags these optional additions; existing code compiles unchanged: x402.facilitatorTimeoutMs on the x402 configuration (default 10000), which reaches DVMConfig, configureDVM, DVMDescriptor, isConfiguredDVMDescriptor, serve, createDVMHost, DVMHost, DVMHostOpts, JobManager, JobManagerOpts, handleCreditRequest, CreditRouteDeps and the x402 settlement server options; optional X402ExactSettlementStore.expireUnused, implemented by MemoryX402ExactSettlementStore and PostgresX402ExactSettlementStore; optional isExactAuthorizationUnused on the x402 settlement evidence readers; and optional getBlock on the evidence client. A custom store or evidence reader without the new methods leaves an expired, unused authorization unresolved rather than ending it unpaid.

Migrations

None. No schema change; the new "pending" outcome and the rejected status written by expireUnused use existing text columns.

Compatibility requirements

Unchanged: Node range and dependency floors are the same as 0.27.0.

dvmctl and platform prerequisites

None. The Fly keepalive is active only when FLY_APP_NAME and FLY_MACHINE_ID are set and needs a resolvable Flycast address for the app; elsewhere it does nothing.

Features

  • server: add Fly keepalive during handler execution

Bug Fixes

  • handle signed-request errors across SDK installations

  • x402: keep an unsigned job's settlement unknown until evidence resolves it

Miscellaneous Chores

  • api: advance the comparison baseline to v0.27.0

Release notes

  • Fly deployments now send a pinned Flycast keepalive every 15 seconds while at least one handler invocation is running, stopping after the last invocation settles or the server closes. Requests are bounded, share one timer across mounts, and warn once on failure without changing job outcomes. This best-effort protection requires a resolvable Flycast address and applies only when the job's Machine is the only one awake; see docs/OPERATING.md#fly-machine-autostop.

View on GitHub
dvm-cli 0.15.3

dvm-cli 0.15.3

Bug Fixes

  • credit: report already drained for a repeat tempo drain

  • drain verification diagnostics before exiting

  • make reserve release swaps recoverable

  • retry job storage locks and preserve accepted outcomes

View on GitHub
dvm-cli 0.15.2

dvm-cli 0.15.2

Bug Fixes

  • reconcile job read actions with local payment state

  • reflect credit posture in drawability reports

  • report live implicit balances as released credit

  • request: preserve definitive refusals with request IDs

  • request: report requests refused before sending as not submitted

  • surface finished artifacts on ended jobs

  • wallet: persist reclaim swap outputs before the mint call

View on GitHub
dvmctl 0.17.1

dvmctl 0.17.1

Bug Fixes

  • dev: handle signed auth errors across SDK installations

View on GitHub
sdk 0.27.0breaking

sdk 0.27.0

⚠ BREAKING CHANGES

  • kv: a directly constructed PostgresKVStore runs a sweep timer from init() and must be closed with close() before its pool ends; otherwise each later sweep logs kv_expiry_sweep_failed.

Bug Fixes

  • kv: delete expired rows from the Postgres KV store

Miscellaneous Chores

  • api: advance the comparison baseline to v0.26.1

Breaking change details

  • A directly constructed PostgresKVStore now runs an expiry sweep timer from init() and must be stopped with close() before its pool ends. A store whose pool ends without close() logs kv_expiry_sweep_failed every minute. Stores the host creates are closed on shutdown.

Release notes

  • KV TTLs now mean deletion. The Postgres KV store deletes expired kv_store rows within one minute of expiry while a host is running; a stopped or suspended service deletes them within one minute of its next start. It sweeps at startup and every minute in bounded batches of 1,000 rows, up to 100,000 rows per sweep, safely across hosts sharing a database. Previously expired rows were hidden from reads but kept forever. A failed sweep logs kv_expiry_sweep_failed and never fails a read or write. PostgresKVStore gains close(), sweepExpired() and an optional PostgresKVStoreOpts (sweepIntervalMs), and PostgresKVStoreOpts is a new export from @dvmkit/sdk/server; the host closes its own store on shutdown. The in-memory store also drops expired entries on a periodic write-triggered sweep. See KV storage retention.

View on GitHub
dvm-cli 0.15.1

dvm-cli 0.15.1

Bug Fixes

  • payments: never pay an open ask twice after a lost delivery

View on GitHub
dvm-cli 0.15.0

dvm-cli 0.15.0

Features

  • credit: exempt card top-ups from the first-contact trust cap

  • enforce CLI error-code compatibility

  • stabilize core job recovery contracts

Bug Fixes

  • credit: show card funding minimum and approval guidance

  • credit: stop false funding warnings and explain the real ones

  • discovery: preserve job access after timeouts

  • receipts: show charges in fiat and explain every unlabelled amount

View on GitHub
dvmctl 0.17.0

dvmctl 0.17.0

Features

  • add DVM discovery visibility controls

Bug Fixes

  • create: typecheck every scaffold source file and document work-shaped DVMs

  • deps: advance builder SDK to 0.25.0

View on GitHub
sdk 0.26.1

sdk 0.26.1

Bug Fixes

  • pieces: quote the lowered finished-piece charge in charged_if_declined_micro

Miscellaneous Chores

  • api: advance the comparison baseline to v0.26.0

Release notes

  • A payment-request's charged_if_declined_micro now quotes the finished pieces at their charge, including a piece the DVM lowered with finishedChargeMicro. It used to sum their full prices, so an ask that lowered the finishing piece told the caller a decline would cost more than the decline then settled. The quote now equals what a decline settles; jobs that lower no piece quote the same as before.

View on GitHub
sdk 0.26.0breaking

sdk 0.26.0

⚠ BREAKING CHANGES

  • sdk: Test contexts cache successful step results by default. Use a fresh context and cache for independent executions, and reuse a cache only for replay of the same job.

Features

  • api: enforce public signature release disclosures

  • reports: include paid-piece totals in terminal evidence

  • sdk: support handler replay tests and typed capabilities

Bug Fixes

  • credit: book revenue for a credit-backed job that ends without completing

  • credit: recover permanently refused card refunds

Breaking change details

  • Test contexts now cache successful ctx.step results by exact step ID, including undefined, instead of rerunning every call. Tests that need independent executions must create a fresh context with a fresh cache; reuse StepCache only for replay of the same job. TestContextOpts also gains optional auth and stepCache fields, and the public capability declarations accept an optional quote-data type parameter.

Release notes

  • A credit-backed job that ended without completing, through idle expiry, a caller's cancel or decline, a handler throw, or the stale-job reaper, now books its settled draw as revenue. Those stored-terminal paths settled the finished pieces and sent the terminal and cost reports, but never handed the revenue report to onJobCompleted, so a metered job cancelled by idle timeout showed no revenue for the pieces it charged. Each terminal job that carries a draw and books nothing now logs why (revenue_skipped_released_draw, revenue_skipped_unsettled_draw, revenue_skipped_no_rail, revenue_skipped_unbookable_draw, revenue_skipped_no_ledger, revenue_skipped_no_reporter). With the Postgres job store, terminal-cost reconciliation also books draw-backed terminal jobs whose revenue never reached the outbox, including ones left by earlier versions, with a report identical to the in-line one; a booking that carried the job's cost marks that cost revision reported. Postgres initialization adds jobs.revenue_report_enqueued; existing completed jobs are marked, and existing failed and cancelled jobs with settled draws are booked once on upgrade.

  • Handler tests can supply auth and replay completed ctx.step work with createTestContext({ stepCache }) and StepCache from @dvmkit/sdk/testing. Each context now caches successful steps by default; reuse a cache for the same job across recreated contexts, supplying the next response or payment, to test re-entry. Cached steps replay their cost declarations, while failed steps run again. This simulates completed-step replay, not crash durability or exactly-once side effects.

  • defineCapability and the CapabilityConfig type are now exported from @dvmkit/sdk. Wrap individual capabilities entries in defineCapability({ input, onJob, onQuote, ... }) to infer each handler's input, state, and quote data from its own schemas. Existing capability maps remain supported; CapabilityConfig gains an optional third type parameter for quote data. Capability maps also accept whole-schema quote transforms that produce scalar data.

  • Add a single compatibility policy, per-entry-point stability levels, and a public signature gate requiring breaking-change release notes. Root and testing exports are stable; server exports are experimental. The post-trigger deprecation window spans two minor-version increments.

  • Terminal reports now include heldMicro, the original draw hold including paid mid-job pieces, and finishedPieceCount, which excludes a piece stopped by cancellation. Both fields are optional for compatibility with older reports; historical jobs without piece accounting omit the count. See protocol-fixtures/piece-settlement-v1.json.

  • Terminally refused card refunds now enter refund_blocked and stop consuming sweep retry slots. Signed admin routes close-card-drain and replan-card-drain require a decision id and reason; closing records the unpaid remainder as written_off, while replanning retains successful refunds and immediately retries only the remainder. Unknown or processing refunds refuse recovery. Postgres adds nullable credit_drains.card_recovery; the financial export retains structured refund/write-off amounts without operator free text. Custom card ledgers must implement serialized recovery and honor the supplied query connection. Clients must handle the two new drain states; see protocol-fixtures/credit-drain-stripe-v1.json.

View on GitHub
sdk 0.25.0breaking

sdk 0.25.0

Breaking API changes

Card top-ups now default to $5 instead of $0.50. Set DVMKIT_STRIPE_MIN_USD or createStripeCreditRail({ minUsd: ... }) to choose a card-only minimum. Explicit settings must be at least $0.50 and no greater than credit.max; invalid settings fail boot. The effective minimum respects credit.min and Stripe's $0.50 floor, and the default is capped at credit.max so menus below $5 can still offer cards. Other rails and credit.min are unchanged. CreditTerms.stripe now preserves validated card terms when parsing a credit menu; no public export is removed or renamed.

Migrations

To retain the previous card floor, set DVMKIT_STRIPE_MIN_USD=0.50 before upgrading, or pass minUsd: 0.50 to createStripeCreditRail. Otherwise existing card-enabled DVMs advertise the new $5 default, capped by their credit maximum. No database or wire-format migration is required.

Compatibility requirements

Node.js 22 or newer. No dependency floor changes from 0.24.0.

dvmctl and platform prerequisites

None. This release introduces no new minimum CLI version or platform capability requirement for the supported builder APIs.

⚠ BREAKING CHANGES

  • stripe: default the card top-up minimum to $5 and let builders set it

Features

  • stripe: default the card top-up minimum to $5 and let builders set it

Bug Fixes

  • credit: preserve card terms in caller parsing

Breaking change details

  • The card top-up minimum now defaults to $5 instead of $0.50, so an existing card DVM's credit.stripe.min_micro rises from 500000 to 5000000 on upgrade and smaller card top-ups return 400 below_rail_minimum. Builders set another minimum for card alone with DVMKIT_STRIPE_MIN_USD or the minUsd option of createStripeCreditRail (at least 0.50; set 0.50 to keep the old behaviour). It is raised to credit.min when that is higher and capped at credit.max, so card stays offered on a DVM whose credit maximum is under $5; a setting above credit.max fails boot. Other rails' minimums are unchanged. See docs/OPERATING.md#card-top-up-minimum.

Release notes

  • Caller-side credit parsing now preserves the card funding profile, minimum, and USD currency. Malformed stripe blocks reject the terms or menu, matching Tempo and x402 validation; unknown fields remain stripped. Operating guidance states Link's supported payer regions.

View on GitHub
sdk 0.24.0

sdk 0.24.0

Features

  • stripe: attribute card-credit charges to the server identity

Bug Fixes

  • nwc: survive a relay that never completes the WebSocket handshake

Release notes

  • Card-credit PaymentIntents now include server-owned Stripe metadata dvmkit_dvm_id from the server's canonical identity (falling back to its DVM id), including declined confirmations. Environment-created and explicit rails share this behavior; standalone servers without identity omit the field. StripeCreditRail.charge accepts optional server-side canonicalDvmId. A Stripe parameter mismatch triggers one retry without the new metadata under the same idempotency key, preserving recovery of pre-upgrade charges; existing PaymentIntents keep their original metadata. MPP challenge and idempotency formats are unchanged; no storage migration is required. See protocol-fixtures/credit-fund-stripe-v1.json.

  • A DVM no longer crashes at startup when one of its NWC relays accepts the TCP connection but never completes the WebSocket handshake. The connection timeout used to close the still-connecting socket after its error listener had been removed, so the socket's error went unhandled and terminated the process. The relay now counts as unreachable, and the other relays carry the request.

View on GitHub
sdk 0.23.0breaking

sdk 0.23.0

⚠ BREAKING CHANGES

  • credit: a caller's cancel charges the paid pieces including the one in progress, and an ask is never covered by the upfront payment. CreditLedgerLike.resolveDraw is required. StreamableJobStore.appendOutgoing refuses an ask on a terminal job with JobEndedError and finishes the running piece on a payment-request; verifyAndCredit appends PaymentCreditDelta.piece; terminal writes freeze JobRecord.settlement, which the built-in stores own after insert. Postgres initialization adds jobs.pieces and jobs.settlement. A second open ask rejects with ask_already_open, and receipt credit.amount is the charged amount.

  • payment: StreamableJobStore.verifyAndCredit takes landing options and may report creditRefused; job_messages gains the balance row status; custom job stores must implement payment intents.

Features

  • credit: charge mid-job work by the piece

  • credit: settle part of a credit draw

Bug Fixes

  • credit: release a draw held on a closed x402 channel in both ledgers

  • payment: decide what a mid-job payment pays for when it arrives

  • x402: withhold an unsigned job's output until its payment settles

Breaking change details

  • Mid-job work is charged by the piece. Each payment buys the next piece of work: the upfront payment the first, each paid ctx.requestPayment ask the one after it, and a piece finishes when the DVM sends its next ask or completes. Every ending charges the finished pieces and releases the piece in progress, except a caller's cancel, which stops the work as before and now charges the piece in progress too; a failure no longer gives back the upfront payment for work already delivered. Every ask is new money: the upfront payment never covers an ask, so a handler that relied on that now suspends for a payment. One payment request may be open at a time (ask_already_open), and ctx.complete with one open withdraws it. ctx.requestPayment and ctx.complete take finishedChargeMicro to charge the finishing piece less than its price. Callers can end a job at an open ask or prompt with a new decline message (HTTP 409 no_open_ask when nothing is open). A payment-request carries charged_if_declined_micro; receipts stay v: 1 and gain an optional settlement block, and credit.amount is now the charged amount, 0 on a draw released whole. The terminal report gains chargedMicro, currency and stoppedPiece. CreditLedgerLike.resolveDraw is required; StreamableJobStore.appendOutgoing refuses an ask on a terminal job with JobEndedError, which @dvmkit/sdk/server exports with the JobPiece, JobSettlement, PieceEnding, PieceState and DeclineOutcome types. A custom job store that saves snapshots as given settles from the settlement the SDK freezes on the terminal snapshot. Postgres initialization adds jobs.pieces and jobs.settlement; a job in flight at upgrade settles as one piece. Unsigned x402 jobs remain one piece settled only on completion. See docs/PROTOCOL-NOTES.md#charging-by-the-piece and protocol-fixtures/piece-settlement-v1.json.

Security fixes

  • An unsigned x402 job's output is now withheld until its payment settles. Previously a caller could read the summary, artifacts and streamed messages, then cancel the authorization or move the funds before the settlement ran, and keep the result unpaid. Reads now show content_available: false with content_withheld until the facilitator settles, a refused settlement reads as failed with no content, and mid-run streaming is unavailable on these jobs. A settled-as-unpaid job's receipt reports nothing paid and onJobTerminal reports paid: false. A payer is limited to one outstanding authorization (HTTP 429 x402_payer_busy), and X402ExactSettlementStore.claim takes an optional maxOutstandingPerPayer; Postgres adds the index idx_x402_exact_settlement_payer. See docs/PROTOCOL-NOTES.md#unsigned-x402-payments.

Release notes

  • An ask that withheld x402 because the job's credit holds another rail used to clear the job's x402 binding, so an x402 payment sent anyway settled and landed as balance. The job now keeps a nonce nobody was shown and the payment is refused before it settles. On hosts without a database, an x402 payment bound to another job's nonce is now refused before the facilitator is called, rather than after it settled.

  • applyReceiptCredit now checks a receipt whose settlement.charged is positive on every ending, not only completions, against the caller's prior balance plus verified draw funding.

View on GitHub
dvm-cli 0.14.0

dvm-cli 0.14.0

Features

  • hand unpaid asks to the agent and add dvm decline

View on GitHub
sdk 0.22.0

sdk 0.22.0

Features

  • credit: fund prepaid credit by card through Stripe shared payment tokens

  • credit: refund card-funded credit to the card

Release notes

  • Prepaid credit can be funded with a card. A DVM with DVMKIT_STRIPE_SECRET_KEY and DVMKIT_STRIPE_NETWORK_ID (or stripeCredit: createStripeCreditRail(...)) lists stripe in credit.funding with credit.stripe: { network_id, min_micro, currency } on a USD menu. A signed fund with method: "stripe" gets an MPP method="stripe" charge challenge; a credential built from a Stripe Shared Payment Token is charged once and booked as a funding lot keyed by the PaymentIntent id. Top-ups start at $0.50. Declines, unusable tokens, commitment mismatches and replays book nothing, and refusals carry Stripe's error codes but never its message text. When Stripe's answer is lost or the booking fails after a charge, the DVM returns a retryable 503; resending the same credential within five minutes books that charge instead of charging again. Card credit requires DVMKIT_TEMPO_SECRET_KEY as the MPP challenge-binding secret and honours its previous-key rotation window. Card-funded credit drains only back to the card, and the expiry sweep leaves expired card credit unreleased, so it is never reported as builder revenue. /v1/job never offers card payment. No storage migration: card lots reuse credit_funding_lots with rail = "stripe". Receipts and the deposit report may now carry rail: "stripe" for card-funded draws and deposits. See protocol-fixtures/credit-fund-stripe-v1.json.

  • Unused card credit is refunded to the card. A drain with method: "stripe" (no payout) refunds the balance as partial refunds of the funding PaymentIntents, oldest first, and returns refund_ids plus a card_refund block. The caller bears Stripe's fee in proportion to what is refunded: per PaymentIntent, refund = gross − round(fee × gross ÷ charged), so a $2.00 top-up with $0.30 used refunds $1.39 and keeps $0.31 of Stripe's $0.36 fee. The fee share is not builder revenue; the platform drain report carries the whole drained balance. Card credit drained by any other method, and stripe on non-card credit, are refused. A card refund sweep on the expiry cadence refunds expired card credit (the credit closes with the new status refunded), freezes credit whose funding payment is disputed (new status disputed), retries pending refunds without refunding twice, and refunds in full a charge that never reached a credit. Closed and frozen credits, and top-ups of expired card credit, answer 409 credit_closed. A won dispute unfreezes the credit once Stripe shows no open or lost dispute on any of its top-ups; a lost one keeps it frozen. One card refund runs per credit at a time (409 drain_conflict with blocking_drain_id), and stripe drain ids are capped at 128 characters with the expiry- prefix reserved. Each sweep step fails on its own without stopping the pass. docs/OPERATING.md lists the Stripe permissions a restricted key needs. mark-drain-sent on a stripe drain retries the refund instead of recording an operator payout, and pending-drains shows each refund's state. Postgres gains credit_drains.card_refund (JSONB) and the card_charge_attempts journal, both created on init. Stripe is called over plain HTTPS, with no new dependency. See protocol-fixtures/credit-drain-stripe-v1.json.

View on GitHub
sdk 0.21.2

sdk 0.21.2

Bug Fixes

  • auth: distinguish missing request signatures

Release notes

  • Requests with no signing envelope now receive HTTP 401 auth_error with signature_required and instructions for signing through the CLI or protocol. Malformed envelopes and wrong signatures retain signature_invalid; eligible unsigned paid calls retain their 402 challenge. Clients that enumerate auth sub-reasons must accept the new value. See protocol-fixtures/signature-required-v1.json.

View on GitHub
sdk 0.21.1

sdk 0.21.1

Bug Fixes

  • park JIT refunds without enabling Cashu receiving

View on GitHub
dvm-cli 0.13.0

dvm-cli 0.13.0

Features

  • credit: fund and refund prepaid credit by card through Stripe Link

View on GitHub
dvm-cli 0.12.1

dvm-cli 0.12.1

Bug Fixes

  • credit: scope draw price checks to capabilities

  • distinguish provider failures from caller cancellations

  • include accepted job recovery in payment errors

  • payments: keep stablecoin receipt comparisons unknown

  • report terminal job settlement outcomes

  • resolve capability URLs against provider endpoints

View on GitHub
dvmctl 0.16.0

dvmctl 0.16.0

Features

  • offer deployment after a paid service works locally

  • support explicit refund park capability

  • Pin the CLI runtime and new scaffolds to SDK 0.21.1. Separately installed project dependencies are not upgraded automatically.

View on GitHub
dvmctl 0.15.0

dvmctl 0.15.0

Features

  • point builders to the Discord from errors and the build-dvm skill

Bug Fixes

  • guard refund purchases before payment

View on GitHub
2026 · W44

26 October – 1 November 2026

Services can take payment from callers that do not sign requests

  • sdk 0.16.1 → 0.21.0
  • dvm-cli 0.11.1 → 0.12.0
  • dvmctl 0.13.1 → 0.14.0
  • sdk 0.17.0 lets a builder opt in, with secp256k1Auth({ allowUnsignedPaid: true }), to serve paid per-call jobs to a caller that pays but does not sign its request, starting with Cashu (Bitcoin ecash).
  • sdk 0.17.0 asks for Cashu payment as a NUT-24 payment request, the Cashu standard for charging an HTTP client, and accepts NUT-24 payments.
  • sdk 0.19.0 adds x402 dollar stablecoins to unsigned paid calls: the payment is authorized before the job runs and settled only if the job succeeds.
  • sdk 0.20.0 and 0.21.0 return short results and artifacts inline on a paid NUT-24 retry.
8 features
  • sdkinline artifact messages on paid NUT-24 retries
  • dvm-cliexplain metered auto-pay limits
  • dvmctladd identity import and refuse keys the account will reject
  • sdkreturn short NUT-24 job results inline
  • sdksettle unsigned x402 payments only after the job succeeds
  • sdklet builders set the Cashu refund-locktime floor
  • sdkadvertise Cashu payment as a NUT-24 payment request and accept NUT-24 payments
  • sdkserve unsigned paid per-call jobs behind secp256k1Auth({ allowUnsignedPaid: true })
19 releases
sdk 0.21.0

sdk 0.21.0

Features

  • inline artifact messages on paid NUT-24 retries

View on GitHub
sdk 0.20.0

sdk 0.20.0

Features

  • return short NUT-24 job results inline

View on GitHub
sdk 0.19.1

sdk 0.19.1

Bug Fixes

  • contain closed NWC relay publish failures

  • persist terminal output before settling credit

Terminal result durability

  • Retry failed outgoing appends and terminal snapshots for up to 30 seconds before settling a completed credit draw. Exhausted completion retries fail the job with terminal_persistence_failed and release its draw when storage is reachable; refusal receipts retain their own reason after failed step writes.

  • Deduplicate outgoing append retries across lost acknowledgements, including payment counters and terminal log cleanup. Postgres initialization adds job_outgoing_appends; custom streaming stores must honor stable appendId values. Existing receipt bytes remain write-once.

  • Receipt persistence may lag settlement after the full result is durable. Terminal responses with receipt support expose receipt_pending: true until a signed receipt is stored. Later reads after restart rebuild missing receipts from the stored result and resolved draw, reuse the receipt sequence, and do not settle an already settled draw again. Historical missing output is not reconstructed.

Release notes

  • NWC requests now return a transport error when a relay socket closes between connection and publication, instead of leaving an unhandled rejection that can terminate the process. The pinned nostr-tools dependency is updated to 2.25.4, whose publish path handles send failures; Lightning invoice funding returns its existing unavailable response.

View on GitHub
dvmctl 0.14.0

dvmctl 0.14.0

Features

  • identity: add identity import and refuse keys the account will reject

Bug Fixes

  • cashu: isolate unusable proofs during pending melts

  • isolate builder recovery state in explicit directories

  • melt: match quote costs and close confirmed empty quarantines

  • service refunds without a Cashu accumulator

View on GitHub
sdk 0.19.0

sdk 0.19.0

Features

  • settle unsigned x402 payments only after the job succeeds

Bug Fixes

  • align terminal job reads with durable receipts

  • enable browser wallet access on public routes

  • return retryable errors for temporary job-read outages

Release notes

  • Unsigned callers can pay a capability with x402 when it sets the new maxRuntimeSeconds (1 to 600) on a DVM with allowUnsignedPaid and Postgres. The authorization is verified before the job and settled only if the job succeeds; a failed, cancelled or timed-out job is never settled, and a replayed authorization neither runs a job nor settles twice. Authorizations that would lapse before the job's bound are refused with payment_authorization_too_short before verification, and the 402 advertises a longer maxTimeoutSeconds. Exact settlement intents gain a released status (no DDL; the status column is unconstrained text). Tempo stays signed-only. See docs/PROTOCOL-NOTES.md#unsigned-x402-payments.

View on GitHub
dvm-cli 0.12.0

dvm-cli 0.12.0

Features

  • explain metered auto-pay limits

View on GitHub
dvmctl 0.13.5

dvmctl 0.13.5

Bug Fixes

  • normalize foreign SDK multi-capability descriptors

View on GitHub
sdk 0.18.0

sdk 0.18.0

Features

  • let builders set the Cashu refund-locktime floor

Bug Fixes

  • recover stale Postgres pools on ordinary requests

Release notes

  • Shared Postgres pools now recover through a full pool of stale idle connections after suspend/resume, including admin, job, and credit queries. Direct checkouts pass a bounded read-only probe before callers receive them, evicting detected stale connections before transaction or advisory-lock work. Recovery limits attempts by pool size and stops starting retries when the connection-timeout window expires; request-specific recovery deadlines remain supported. No API or storage migration is required.

View on GitHub
sdk 0.17.1

sdk 0.17.1

Bug Fixes

  • book a Cashu payment after a paid ask as credit balance

View on GitHub
sdk 0.17.0

sdk 0.17.0

Features

  • advertise Cashu payment as a NUT-24 payment request and accept NUT-24 payments

  • serve unsigned paid per-call jobs behind secp256k1Auth({ allowUnsignedPaid: true })

Bug Fixes

  • accept unsigned paid calls on Cashu only

  • honor explicit payment methods in discovery and credit menus

  • recover a replayed Cashu job only under the request id its proofs were accepted with

Release notes

  • Explicit paymentMethods overrides now suppress excluded x402 and Tempo discovery blocks and prepaid-credit funding terms, including x402 batch funding. Omitted overrides retain derived defaults, and Lightning funding stays independent. A cashu_not_advertised boot warning identifies why configured mints do not result in a Cashu payment method. No storage migration is required; see protocol-fixtures/payment-method-discovery-v1.json.

View on GitHub
dvmctl 0.13.4

dvmctl 0.13.4

Bug Fixes

  • runtime: show the serving SDK and flag project mismatches

View on GitHub
dvmctl 0.13.3

dvmctl 0.13.3

Bug Fixes

  • deploy: upload only the DVM folder unless buildContext widens it

  • melt: acknowledge paid melts whose change cannot be reconciled

  • scaffold: update SDK and check generated projects

View on GitHub
sdk 0.16.2

sdk 0.16.2

Bug Fixes

  • accept only Cashu locks the DVM alone can spend and melt

View on GitHub
dvm-cli 0.11.3

dvm-cli 0.11.3

Bug Fixes

  • preserve mint diagnostics after successful Cashu fallback

View on GitHub
dvmctl 0.13.2

dvmctl 0.13.2

Bug Fixes

  • billing: allow one-dollar hosting top-ups

  • deploy: package only git-visible files and name an oversized context

  • melt: keep custody of melt change across crashes

View on GitHub
sdk 0.16.1

sdk 0.16.1

Bug Fixes

  • deps: move Hono, Undici, and Zod to patched releases

View on GitHub
dvm-cli 0.11.2

dvm-cli 0.11.2

Bug Fixes

  • discovery: keep operator ownership in search and browse output

  • output: mark provider provenance on the remaining provider-supplied fields

View on GitHub
dvm-cli 0.11.1

dvm-cli 0.11.1

Bug Fixes

  • mark provider prose in prompt choices and schemas

View on GitHub
dvmctl 0.13.1

dvmctl 0.13.1

Bug Fixes

  • melt: keep reconciling melts whose outcome is uncertain

View on GitHub
2026 · W43

19–25 October 2026

Prepaid credit covers mid-job requests and lasts 90 days

  • sdk 0.11.0-rc.1 → 0.16.0
  • dvm-cli 0.8.2 → 0.11.0
  • dvmctl 0.11.0 → 0.13.0
  • dvm-cli 0.9.0 and sdk 0.12.0 let a service's payment requests during a job draw on prepaid credit instead of needing a fresh payment.
  • Breaking in sdk 0.13.0: prepaid credit now expires after 90 days by default instead of 30. A builder who wants 30 days sets credit: { ttl: 2_592_000 }.
  • dvmctl 0.12.0 lets a builder refund a completed job that was paid from prepaid credit.
  • dvm-cli 0.11.0 shows itemized spending in job status and checks downloaded files against the job's signed receipt.
17 features
  • sdkadd trusted no-DVM span resolution marks
  • dvm-clirelay caller deadlines with SDK 0.14.2
  • dvmctladd held Tempo drain decisions
  • sdkexpose accepted upfront payments on job responses
  • dvm-clishow itemized job spending in status
  • dvmctlrefund completed credit jobs
  • sdksign mid-job funding evidence and reconcile funded draws
  • dvm-clishow next steps in human job output
  • dvmctladd billing and trial recovery commands
  • sdkextend default prepaid credit lifetime to 90 days
  • dvm-cliverify downloaded files against signed receipts
  • sdkpay mid-job requests from prepaid balance
  • dvm-cliwait for long jobs within stored payment policy
  • sdkadd operator decisions for held Tempo drains
  • dvm-clirelay prompt choices in respond actions
  • sdksupport completed credit draw refunds
  • dvm-clipay mid-job requests from prepaid balance
21 releases
sdk 0.16.0

sdk 0.16.0

Features

  • add trusted no-DVM span resolution marks

View on GitHub
dvm-cli 0.11.0

dvm-cli 0.11.0

Features

  • relay caller deadlines with SDK 0.14.2

  • show itemized job spending in status

  • show next steps in human job output

  • verify downloaded files against signed receipts

  • wait for long jobs within stored payment policy

Bug Fixes

  • delay retries for uncertain job payments

  • payments: count upfront credit draws toward job limits

  • payments: restore upfront rail accounting during recovery

  • refresh pending payment requests before paying

View on GitHub
sdk 0.15.0

sdk 0.15.0

Features

  • expose accepted upfront payments on job responses

Bug Fixes

  • publish payment history only after acceptance

Release notes

  • Accepted job responses and request recovery now expose optional upfront_payment metadata with the original credit hold or rail payment, exact recorded amounts and credit/draw correlation. The snapshot survives later payments, draw growth and exchange-rate changes; historical jobs remain unknown and explicit zero stays distinct. Job stores gain an optional, insert-only upfrontPayment fact backed by a nullable Postgres column. See protocol-fixtures/upfront-payment-v1.json.

View on GitHub
sdk 0.14.2

sdk 0.14.2

Bug Fixes

  • limit idle timeouts to caller response windows

  • persist completed steps before returning to handlers

  • preserve locally running jobs during stale sweeps

Continuous Integration

  • upgrade artifact downloads to Node 24

Release notes

  • idleTimeout now limits only outstanding caller prompts and payment requests, starting at emission rather than job creation or the last caller message. Each request carries optional expires_at_ms in Unix milliseconds; unrelated messages do not extend it, and recovery preserves the original deadline. Processing uses the existing liveness watchdog. Configuration now rejects timeout values outside integer seconds 1–604800; the default remains 3600. See protocol-fixtures/caller-deadline-v1.json.

View on GitHub
sdk 0.14.1

sdk 0.14.1

Bug Fixes

  • bound streamed upload memory in pinned fetch

Documentation

  • clarify message acknowledgement cursor semantics

Continuous Integration

  • upgrade artifact uploads to Node 24

View on GitHub
dvm-cli 0.10.0

dvm-cli 0.10.0

Features

  • relay prompt choices in respond actions

Bug Fixes

  • credit: reconcile delayed receipts during job reads

  • credit: reconcile signed mid-job funding

  • preserve caller state on Windows and verify runtime compatibility

View on GitHub
dvmctl 0.13.0

dvmctl 0.13.0

Features

  • credit: add held Tempo drain decisions

Bug Fixes

  • billing: render actionable payment and recovery prose

View on GitHub
sdk 0.14.0

sdk 0.14.0

Features

  • sign mid-job funding evidence and reconcile funded draws

Bug Fixes

  • ignore older receipt replay under the credit lock

  • keep pending prompts awaiting input after duplicate rail payments

  • preserve pending prompts during development payments

Release notes

  • Mid-job rail payments that fund a job's credit against its pending draw now leave signed evidence. The server fixes a credit_fundings row (with new nullable job_id, draw_id, payment_seq columns) inside the rail transaction and issues a credit_draw_funding receipt from it: returned as draw_funding_receipt on the payment 201, on the 503 snapshot-failure and 500 unapplied bodies, on a 409 replay_rejected for the same payment, and as draw_funding_receipts on every authenticated job read, including after a restart. The caller credit store admits verified evidence with recordDrawFunding (or inline on applyReceiptCredit) and compares a completed draw as prior remaining plus eligible funding minus the draw, so a self-funded grown draw no longer raises a false balance warning while a contradictory terminal balance still does. CreditLedgerLike gains optional listDrawFundings and optional recordFunding bindings; FundingRecord.receipt and saveFundingReceipt now carry CreditFundingEvidence, the union of opening and draw funding receipts discriminated by kind. The portable contract is protocol-fixtures/credit-draw-funding-v1.json.

  • Replaying an older job receipt no longer changes a newer stored credit projection. The comparison now happens inside the credit-store lock that applies the receipt, so last price, receipt attribution, flags, and update time stay with the newest settled draw, including when another process settles it mid-recovery.

View on GitHub
dvm-cli 0.9.2

dvm-cli 0.9.2

Bug Fixes

  • preserve refused ecash funding for recovery

View on GitHub
sdk 0.13.0breaking

sdk 0.13.0

⚠ BREAKING CHANGES

  • Default prepaid and implicit credit lifetimes increase from 30 to 90 days. Set credit.ttl to 2592000 seconds to retain 30 days.

Features

  • extend default prepaid credit lifetime to 90 days

Breaking change details

  • Prepaid and implicit per-call credits now default to 90 days instead of 30 days. Builders hold unspent balances longer before expiry release. Existing credits retain their stored expiry until their next top-up; funding extends expiry to the later of its current value and funding time plus the configured TTL. Set credit: { ttl: 2_592_000 } to keep a 30-day lifetime. Explicit TTL overrides remain supported; no database migration is required.

View on GitHub
sdk 0.12.0

sdk 0.12.0

Documentation

  • document stable release graduation

View on GitHub
sdk 0.12.0-rc.1

sdk 0.12.0-rc.1

Features

  • pay mid-job requests from prepaid balance

View on GitHub
dvm-cli 0.9.1

dvm-cli 0.9.1

Bug Fixes

  • skill: describe the dvm skill by the jobs it serves

View on GitHub
dvm-cli 0.9.0

dvm-cli 0.9.0

Bug Fixes

  • deps: use the stable SDK runtime

View on GitHub
dvm-cli 0.9.0-rc.1

dvm-cli 0.9.0-rc.1

Features

  • pay mid-job requests from prepaid balance

View on GitHub
dvm-cli 0.8.2

dvm-cli 0.8.2

Bug Fixes

  • sign authenticated discovery requests

View on GitHub
dvmctl 0.12.1

dvmctl 0.12.1

Bug Fixes

  • deps: use the stable SDK release

View on GitHub
dvmctl 0.12.0

dvmctl 0.12.0

Features

  • refund completed credit jobs

View on GitHub
sdk 0.11.0-rc.1breaking

sdk 0.11.0-rc.1

⚠ BREAKING CHANGES

  • Custom CreditLedgerLike stores must implement transactional refundDraw accounting and report enqueueing.

Features

  • add operator decisions for held Tempo drains

  • support completed credit draw refunds

Bug Fixes

  • classify finalized Tempo backing loss from close evidence

  • keep pre-1.0 releases on the development line

View on GitHub
sdk 1.0.0-rc.1 withdrawn

sdk 1.0.0-rc.1

This candidate was withdrawn before the publish step ran and was never published to npm. Its immutable signed tag is retained as history. These notes retain the candidate's feature and breaking-change information; they do not describe a published package or GitHub release.

⚠ BREAKING CHANGES

  • Custom CreditLedgerLike stores must implement transactional refundDraw accounting and report enqueueing.

Features

  • add operator decisions for held Tempo drains

  • support completed credit draw refunds

Bug Fixes

  • classify finalized Tempo backing loss from close evidence

View in the changelog
dvmctl 0.11.0

dvmctl 0.11.0

Features

  • add billing and trial recovery commands

View on GitHub
2026 · W42

12–18 October 2026

All three packages reach npm's stable channel

  • sdk 0.7.0-rc.10 → 0.10.1
  • dvm-cli 0.8.0 → 0.8.1
  • dvmctl 0.8.0 → 0.10.0
  • sdk 0.8.0, dvm-cli 0.8.0, and dvmctl 0.8.0 are the first releases on npm's latest channel. All three are still pre-1.0 alpha: the stable channel is not a 1.0 compatibility promise, and breaking changes are announced in the release notes.
  • dvm-cli 0.8.0 installs with npm install --global @dvmkit/dvm-cli followed by dvm init. Setup does not fund a wallet.
  • dvm-cli 0.8.0 bundles a skills/dvm directory that tells an agent how to call services, use the wallet and prepaid credit, and recover from failures.
  • dvmctl 0.9.0 lets dvmctl melt-pending acknowledge a stuck Bitcoin Lightning payout, and fits payouts to the ecash mint's limits.
5 features
  • sdkadd admin routes for hosted Tempo close reports
  • dvmctladd Tempo close-report commands
  • sdksummarize pending implicit credit draws
  • dvmctllet melt-pending acknowledge a stuck melt quote
  • sdkterminalize hosted Tempo close obligations
11 releases
sdk 0.10.1

sdk 0.10.1

Bug Fixes

  • make concurrent job snapshots safe

Continuous Integration

  • validate workflows on Ubuntu 26.04

Miscellaneous Chores

  • claude: block Claude attribution in commits and PRs

View on GitHub
sdk 0.10.0

sdk 0.10.0

Features

  • add admin routes for hosted Tempo close reports

  • summarize pending implicit credit draws

Bug Fixes

  • prevent duplicate Tempo settlements from stale reads

  • recommend latest caller release in credential hint

  • require Tempo drain proof and share close searches

  • tempo: honour proven charges when replay marking fails

View on GitHub
dvm-cli 0.8.1

dvm-cli 0.8.1

Bug Fixes

  • stop polling drains that require a timed exit

View on GitHub
dvmctl 0.10.0

dvmctl 0.10.0

Features

  • add Tempo close-report commands

View on GitHub
dvmctl 0.9.0

dvmctl 0.9.0

Features

  • let melt-pending acknowledge a stuck melt quote

Bug Fixes

  • adapt payout melts to mint proof limits

  • decouple serve receipt attestation from Cashu recovery

View on GitHub
sdk 0.9.0

sdk 0.9.0

Features

  • terminalize hosted Tempo close obligations

View on GitHub
sdk 0.8.1

sdk 0.8.1

Bug Fixes

  • bring every hosted Tempo close obligation to a terminal state

View on GitHub
dvm-cli 0.8.0

dvm-cli 0.8.0

This is the first stable-channel (latest) release from the new standalone repository. The CLI remains pre-1.0 alpha software: use small balances and review spending regularly.

Included

  • The dvm CLI discovers pay-per-use services, submits jobs, manages payments, and retrieves results. Commands return structured JSON by default; --human enables direct terminal reading.

  • The complete bundled skills/dvm directory provides calling, wallet, prepaid-credit, and recovery procedures for agents.

Compatibility and upgrade

Requires Node.js 22 or later and uses exactly @dvmkit/sdk 0.8.0. The stable channel does not imply a 1.0 compatibility guarantee; breaking changes will be announced in these release notes.

Update an existing global installation with npm update --global @dvmkit/dvm-cli. Then recopy the complete bundled skills/dvm directory, including its procedure files, into your agent's skill directory so the skill and CLI stay on the same package version. For a first installation, run npm install --global @dvmkit/dvm-cli, then dvm init; setup does not fund a wallet.

View on GitHub
dvmctl 0.8.0

dvmctl 0.8.0

This is the first release on npm's latest channel from this new repository. dvmctl remains a pre-1.0 alpha.

The CLI uses the exact registry dependency @dvmkit/sdk 0.8.0, and newly created projects declare the same SDK version. Existing projects keep their declared SDK dependency until you update it.

Upgrade the globally installed CLI with npm update --global @dvmkit/dvmctl, then copy the complete bundled build-dvm skill directory again using the README instructions.

View on GitHub
sdk 0.8.0

sdk 0.8.0

This is the first stable-channel release of @dvmkit/sdk, based on 0.7.0-rc.10. It carries the prerelease runtime and supported API into 0.8.0; the capabilities below are a summary of what this snapshot ships, not a claim that they were all added after rc.10. This remains pre-1.0 alpha software: pin exact versions and review future release notes before upgrading.

Breaking API changes

None relative to 0.7.0-rc.10. The three supported entry points (@dvmkit/sdk, @dvmkit/sdk/server, and @dvmkit/sdk/testing) retain the same 285 declaration names and API baseline.

Migrations

None required when upgrading from 0.7.0-rc.10: this stable preparation adds no configuration, database schema, stored-data, or wire-contract migration. Upgrading from older prereleases still requires the migrations documented in their historical entries. In particular, Bitcoin liability consumers must use currency-grouped balances, diagnostic consumers must use retained structured fields, and hosting controllers must understand finite admission leases and the terminal closed state. Upgrading cannot recreate credit recovery descriptors already lost by an older version.

Compatibility requirements

Node.js 22 or later is required (engines.node: >=22). Dependency versions are unchanged from rc.10, including Hono 4.13.5 and the optional pg 8.20.0 and viem 2.55.11 packages. There are no declared peer dependencies. The default production stores and hosted control require PostgreSQL; a free standalone development server can run without it. Development mode verifies every configured payment rail rather than accepting unusable configured rails as synthetic payments.

dvmctl and platform prerequisites

Standalone SDK use requires neither dvmctl nor a platform account. No new minimum CLI version or platform requirement is introduced relative to rc.10. The documented scaffold route targets the planned stable pairing with @dvmkit/dvmctl@0.8.0 and its build-dvm skill. No older CLI compatibility minimum is specified here.

Opt-in hosted control requires durable PostgreSQL storage, a dedicated management secret of at least 32 bytes, a shared deployment scope, and a controller that signs version-two resumes with finite leaseExpiresAtMs and deadlineMs. Admission starts closed until resumed; draining refuses new jobs before payment. Active jobs without scoped ownership need explicit migration before shutdown. Deadline cancellation does not roll back external effects from a handler that ignores abort.

Hosted terminal reporting is enabled when platform URL, token, DVM identity, and durable database are configured. Deploy the platform's /_internal/job-terminal endpoint before enabling those report-emitting servers: a 404 is a permanent 4xx failure, not a retried delivery. Unmanaged servers do not need hosting control or that report endpoint.

Included in the first stable snapshot

  • Capability rate cards are published as builder-declared pricing.rates in /v1/info. Clients that do not read them are unaffected; server validation limits are documented in protocol-fixtures/capability-rates.json.

  • Shared caller credit storage retains unresolved drain descriptors and recovery credentials, including those on replaced credits, until explicit terminal retirement. Existing stored formats remain compatible. Same-origin credit receipts must match the authenticated live DVM identity and builder key before increasing credit caps or authorizing automatic opens; offline fallback and matching history across hostnames remain supported.

  • Diagnostic spans, SDK logger output, and runtime diagnostics use catalogue version 1 before stdout or transport delivery. Unapproved prose, errors, stacks, attributes, and event names are removed or normalized. Routes retain registered templates; validated DNS origins omit credentials, ports, paths, queries, and fragments, while localhost and IP origins are omitted. Capability fields require a configured definition and are omitted from direct logger rows. Consumers should read retained structured fields rather than parse prose.

  • Opt-in hosted control provides durable scoped admission, bounded drain, resume, and terminal closure. Closed admission rejects direct submissions before payment; scoped jobs remain readable and reclaimable. Unfinished scoped jobs are cancelled as provider initiated at the deadline, with no guarantee of rolling back external handler effects.

  • Bitcoin liability reads preserve uncovered and basisless balances by ledger currency. /admin/credit/bitcoin-liability uses uncovered_by_currency and unbacked_by_currency; ledger consumers use the corresponding ByCurrency arrays. Each entry contains currency, micro, and credits. Exact satoshi totals and aggregate gap counts retain their meanings; display or price each currency separately.

  • Hono 4.13.5 includes the query-parsing fix that prevents URL fragment text from changing query parameters.

  • Schema-version-1 job receipts support optional signed lifecycle timing and SDK-derived failure/cancellation attribution. Existing receipts remain valid, and published compatible verifiers accept the optional fields.

  • Configured hosted servers report every terminal job through the durable outbox without caller identity, payment references, amounts, input, or output. Deploy /_internal/job-terminal first; transport/5xx failures retry under the existing policy, while 4xx responses become permanently stale.

View on GitHub
sdk 0.7.0-rc.10

sdk 0.7.0-rc.10

Bug Fixes

  • tempo: complete hosted session closes and report their payout

Miscellaneous Chores

  • merge reviewed changes

View on GitHub
2026 · W41

5–11 October 2026

Callers check who ran a job and never pay twice on a mismatch

  • sdk 0.7.0-rc.5 → 0.7.0-rc.9
  • dvm-cli 0.7.0-rc.3 → 0.7.0
  • dvmctl 0.5.0-rc.5
  • dvm-cli 0.7.0-rc.3 checks that a job came from the service it paid, and never pays again when that check fails.
  • sdk 0.7.0-rc.8 states each job's identity in a response header, so a caller can check it.
  • sdk 0.7.0-rc.7 lets a service publish its rate card, the prices a caller can read before paying, in /v1/info.
5 features
  • sdkstate job identity in a response-head field
  • dvm-cligive credit-funded paid submits a generated request id
  • sdklet a capability publish its rate card in /v1/info
  • dvm-cliverify provider job identity and never re-pay on an identity failure
  • sdkkeep sanctions refusal details in diagnostics
8 releases
sdk 0.7.0-rc.9

sdk 0.7.0-rc.9

Bug Fixes

  • observability: keep router identity and funded hosting fields

View on GitHub
dvm-cli 0.7.0

dvm-cli 0.7.0

Features

  • give credit-funded paid submits a generated request id

Documentation

  • document promoting a release-candidate line to stable

View on GitHub
dvm-cli 0.7.0-rc.3

dvm-cli 0.7.0-rc.3

Features

  • verify provider job identity and never re-pay on an identity failure

View on GitHub
sdk 0.7.0-rc.8

sdk 0.7.0-rc.8

Features

  • jobs: state job identity in a response-head field

Miscellaneous Chores

  • merge reviewed changes

  • merge reviewed changes

View on GitHub
sdk 0.7.0-rc.7

sdk 0.7.0-rc.7

Features

  • pricing: let a capability publish its rate card in /v1/info

Miscellaneous Chores

  • merge reviewed changes

View on GitHub
dvmctl 0.5.0-rc.5

dvmctl 0.5.0-rc.5

Bug Fixes

  • deps: scaffold builder projects on SDK 0.7.0-rc.7

View on GitHub
sdk 0.7.0-rc.6

sdk 0.7.0-rc.6

Bug Fixes

  • x402: report only earned, unclaimed channel value as pending

View on GitHub
sdk 0.7.0-rc.5

sdk 0.7.0-rc.5

Features

  • observability: keep sanctions refusal details in diagnostics

Miscellaneous Chores

  • merge reviewed changes

View on GitHub
2026 · W40

28 September – 4 October 2026

Spending history and pending refunds now survive in dvm-cli

  • sdk 0.3.0-rc.9 → 0.7.0-rc.4
  • dvm-cli 0.4.1 → 0.7.0-rc.2
  • dvmctl 0.3.5-rc.1 → 0.5.0-rc.4
  • dvm-cli 0.6.0 keeps the wallet's spending history and the record of completed recoveries.
  • dvm-cli 0.4.2 keeps every unresolved refund recoverable when prepaid credit rolls over, with no limit on how many.
  • dvm-cli 0.5.0 tells you when a service's results expire and whether they are still available.
  • dvmctl 0.4.0-rc.2 adds dvmctl feedback send, so a builder can send notes from the command line.
13 features
  • sdkexpose safe exchange-rate failure observations
  • dvm-clipreserve spending and completed recovery history
  • dvmctladopt trimmed shared SDK runtime
  • sdkallow shorter testnet withdrawal delays
  • dvm-clireport provider content expiry and availability
  • dvmctlmanage scoped job content holds and financial export guidance
  • sdkexpose existing migration bindings
  • dvmctladd builder feedback and recover missed dev edits
  • sdkexpose shared channel refusal contracts
  • sdkretain job content with scoped admin holds
  • sdkpreserve completed credit history
  • sdkpreserve hosted obligations through terminal cleanup
  • sdkadd durable hosting admission and draining
25 releases
sdk 0.7.0-rc.4

sdk 0.7.0-rc.4

Features

  • pricing: expose safe exchange-rate failure observations

View on GitHub
sdk 0.7.0-rc.3

sdk 0.7.0-rc.3

Features

  • x402: allow shorter testnet withdrawal delays

View on GitHub
dvm-cli 0.7.0-rc.2

dvm-cli 0.7.0-rc.2

Bug Fixes

  • deps: align caller with testnet withdrawal SDK

View on GitHub
dvmctl 0.5.0-rc.4

dvmctl 0.5.0-rc.4

Bug Fixes

  • deps: align builder recipes with testnet withdrawal SDK

View on GitHub
sdk 0.7.0-rc.2

sdk 0.7.0-rc.2

This release candidate preserves the supported builder API and shared payment, storage, signing, and recovery contracts. Builders using the supported exports can upgrade from 0.7.0-rc.1 without application changes. Provider-bound credit recovery, credit history retention, and safe diagnostics remain supported. Upgrading cannot restore records already lost by an older version.

Breaking API changes

None. The supported @dvmkit/sdk, @dvmkit/sdk/server, and @dvmkit/sdk/testing exports are unchanged.

Migrations

None. No configuration, database schema, stored data format, or wire contract migration or reset is required.

Compatibility requirements

Node.js >=22 remains required. Dependency versions are unchanged, including optional pg 8.20.0 and viem 2.55.11. No peer dependencies are declared.

dvmctl and platform prerequisites

None. This candidate introduces no new minimum dvmctl version or platform capability requirement for the supported builder APIs.

Bug Fixes

  • release: bound npm processing and consumer waits

Miscellaneous Chores

  • merge reviewed changes

  • merge reviewed changes

Code Refactoring

  • internal: remove caller workflows from shared runtime

View on GitHub
dvm-cli 0.7.0-rc.1

dvm-cli 0.7.0-rc.1

Bug Fixes

  • bind installed history fixture to shared ledger APIs

Code Refactoring

  • own caller orchestration and presentation

View on GitHub
dvmctl 0.5.0-rc.3

dvmctl 0.5.0-rc.3

Features

  • adopt trimmed shared SDK runtime

View on GitHub
sdk 0.7.0-rc.1

sdk 0.7.0-rc.1

This release candidate preserves the supported builder API. Builders can upgrade from 0.6.0-rc.1 without application changes. Caller credit storage now keeps separate credits and pending recovery records for distinct authenticated providers even when their caller and credit IDs match. Authenticated provider aliases and compatible legacy identity upgrades remain supported. Upgrading cannot restore records already lost by an older version.

Breaking API changes

None. The supported @dvmkit/sdk, @dvmkit/sdk/server, and @dvmkit/sdk/testing exports are unchanged.

Migrations

None. Configuration, database schemas, stored data formats, and wire contracts are unchanged.

Compatibility requirements

Node.js >=22 remains required. Dependency versions are unchanged.

dvmctl and platform prerequisites

None. This candidate introduces no new minimum dvmctl version or platform capability requirement.

Features

  • internal: expose existing migration bindings

  • internal: expose shared channel refusal contracts

View on GitHub
sdk 0.6.0-rc.1

sdk 0.6.0-rc.1

Features

  • server: retain job content with scoped admin holds

Bug Fixes

  • observability: advertise 730-day diagnostic retention

View on GitHub
sdk 0.5.0-rc.1

sdk 0.5.0-rc.1

Features

  • preserve completed credit history

Bug Fixes

  • preserve caller spending history

View on GitHub
dvm-cli 0.6.0

dvm-cli 0.6.0

Features

  • wallet: preserve spending and completed recovery history

View on GitHub
dvm-cli 0.5.0

dvm-cli 0.5.0

Features

  • report provider content expiry and availability

View on GitHub
dvmctl 0.5.0-rc.2

dvmctl 0.5.0-rc.2

This candidate also removes unused internal credit-notice state; supported command output and feedback behavior are unchanged.

Features

  • manage scoped job content holds and financial export guidance

View on GitHub
sdk 0.4.0-rc.1breaking

sdk 0.4.0-rc.1

⚠ BREAKING CHANGES

  • HostingControlStatus.state now includes "closed". Consumers with exhaustive state handling must accept the terminal value.

Features

  • preserve hosted obligations through terminal cleanup

View on GitHub
sdk 0.3.4-rc.10

sdk 0.3.4-rc.10

Bug Fixes

  • observability: expose trusted span authority

Miscellaneous Chores

  • merge reviewed changes

View on GitHub
sdk 0.3.3-rc.10

sdk 0.3.3-rc.10

Bug Fixes

  • observability: preserve safe route and origin metadata

View on GitHub
sdk 0.3.2-rc.10

sdk 0.3.2-rc.10

Bug Fixes

  • observability: project safe diagnostic fields at every sink

Miscellaneous Chores

  • merge reviewed changes

View on GitHub
dvm-cli 0.4.2

dvm-cli 0.4.2

  • Update the SDK to 0.3.2-rc.10 so unresolved refund descriptors remain recoverable across credit rollovers without a count limit. Credit storage and recovery output remain compatible; previously evicted descriptors cannot be reconstructed by upgrading. Package and publication checks now exercise ten unresolved refunds through the installed caller.

  • Explain when automatic credit funding is skipped because the service does not publish Bitcoin pricing.

View on GitHub
sdk 0.3.1-rc.10

sdk 0.3.1-rc.10

Bug Fixes

  • deps: patch undici security advisories

Miscellaneous Chores

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

View on GitHub
sdk 0.3.0-rc.10

sdk 0.3.0-rc.10

Configured hosting control starts closed and requires a version-two signed, finite admission lease on every resume. Existing unleased accepting scopes close on upgrade while retaining pending payment and job recovery; unmanaged servers are unchanged. Management clients must send leaseExpiresAtMs and deadlineMs and reserve the completion window before resuming. The exported HostingControlCommand gains optional version and leaseExpiresAtMs, while HostingControlStatus gains a required leaseExpiresAtMs; update typed status values and management clients. A legacy unbounded resume returns HTTP 409.

Bug Fixes

  • require expiring hosted admission leases

View on GitHub
dvmctl 0.4.0-rc.2

dvmctl 0.4.0-rc.2

  • Add dvmctl feedback send for builder notes and dvmctl feedback posture to control local feedback invitations.

  • Include the installed SDK version from generated projects in feedback, and retain known first-deploy context when the trace and project match.

  • Recover dvmctl dev edits made while a native file watcher is registering, so a save just after startup still reloads the handler.

View on GitHub
dvmctl 0.4.0-rc.1

dvmctl 0.4.0-rc.1

Features

  • add builder feedback and recover missed dev edits

Bug Fixes

  • cashu: defer pending melt quotes

View on GitHub
sdk 0.3.0-rc.9

sdk 0.3.0-rc.9

Features

  • add durable hosting admission and draining

View on GitHub
dvm-cli 0.4.1

dvm-cli 0.4.1

Bug Fixes

  • skill: load caller procedures on demand

View on GitHub
dvmctl 0.3.5-rc.1

dvmctl 0.3.5-rc.1

Builder guidance

  • Cover building, testing, deployment, operation, recovery, and retirement through selectively loaded skill modules.

  • Document Lightning-funded credit acceptance and separate receiving, refund, and payout credentials.

  • Use published references for SDK and command contracts; keep executable payment recipes in the package.

  • Isolate test caller installations and preserve recovery state when a paid test fails.

View on GitHub
2026 · W39

21–27 September 2026

Test a paid service end to end on your own machine

  • sdk 0.1.5-rc.7 → 0.2.1-rc.9
  • dvm-cli 0.3.0 → 0.4.0
  • dvmctl 0.2.0-rc.2 → 0.3.4-rc.1
  • dvmctl 0.3.0-rc.1 checks your handler, diagnoses missing prerequisites, and reports which payment rails it verified and what your paid test jobs totalled.
  • sdk 0.1.5-rc.7 lets a development server take test payments on every configured rail: Cashu (Bitcoin ecash), x402, and Tempo (both dollar stablecoins).
  • Breaking in dvmctl 0.3.4-rc.1: cloud deploys default to containers, so an existing project without a Dockerfile must copy one from a fresh dvmctl create scaffold.
  • dvm-cli 0.4.0 shows trust and capability rows when you search for services, and lets you send a verdict on a job backed by its receipt.
8 features
  • sdkadd signed terminal timing and hosted reports
  • dvm-clirender trust and capability rows
  • dvmctlcomplete the local builder journey
  • sdkverify local test payments across all rails
  • dvm-clisubmit receipt-backed job verdicts
  • dvmctlenable verified local test payments
  • dvm-cliadd network-aware Tempo test wallets
  • dvmctlrefresh the builder scaffold and bundled skill
15 releases
sdk 0.2.1-rc.9

sdk 0.2.1-rc.9

Bug Fixes

  • resolve release pull requests by tag ancestry

  • update Hono query parsing

Miscellaneous Chores

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

View on GitHub
dvmctl 0.3.4-rc.1

dvmctl 0.3.4-rc.1

Compatibility

  • Cloud deployment and deploy dry runs now default to containers. Existing projects without a Dockerfile must add the Dockerfile from a current dvmctl create scaffold before deploying. --runtime isolate is restricted to operators.

  • The CLI and new scaffolds use @dvmkit/sdk 0.2.1-rc.9. Liability warnings retain each currency separately; older endpoints without denominations report the affected amounts as unknown.

Bug Fixes

  • auth: explain closed beta access during sign-in

Code Refactoring

  • own builder source and behavioral verification

View on GitHub
sdk 0.2.0-rc.9

sdk 0.2.0-rc.9

Features

  • add signed terminal timing and hosted reports

Bug Fixes

  • isolate host configuration and strengthen verification

Documentation

  • clarify comments and test guidance

Miscellaneous Chores

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

View on GitHub
dvm-cli 0.4.0

dvm-cli 0.4.0

Features

  • discovery: render trust and capability rows

  • feedback: submit receipt-backed job verdicts

Bug Fixes

  • discovery: accept unbounded trust history windows

View on GitHub
dvmctl 0.3.3-rc.1

dvmctl 0.3.3-rc.1

Bug Fixes

  • retain local paid test results

  • scaffold: allow compatible Vitest updates

View on GitHub
sdk 0.1.5-rc.9

sdk 0.1.5-rc.9

  • Tempo challenges for USD-priced jobs now charge the builder's exact six-decimal price instead of converting the rounded millisatoshi quote back through BTC/USD. Legacy millisatoshi and non-USD pricing keep their existing conversion behavior.

Bug Fixes

  • preserve exact USD Tempo prices

View on GitHub
sdk 0.1.5-rc.8

sdk 0.1.5-rc.8

  • Tempo Moderato servers now verify returned payment credentials against the same testnet route binding advertised in their HTTP 402 challenge. Unsupported Tempo chain IDs now fail at boot before the server can issue an unpayable challenge; explicit mainnet and Moderato selection and token overrides remain supported.

Bug Fixes

  • bind Tempo verification to the selected network

View on GitHub
dvmctl 0.3.2-rc.1

dvmctl 0.3.2-rc.1

Bug Fixes

  • reload dev when a local handler dependency changes

View on GitHub
dvmctl 0.3.1-rc.1

dvmctl 0.3.1-rc.1

Bug Fixes

  • release-tag: pass effective signing identity into the probe clone

  • share project environment loading

View on GitHub
dvmctl 0.3.0-rc.1

dvmctl 0.3.0-rc.1

  • Local builder workflows now validate the actual handler, diagnose prerequisites, report configured payment-rail verification and paid-job totals, and require explicit identity creation with backup guidance.

  • The bundled builder skill includes isolated Cashu, Tempo, and x402 test recipes using caller CLI 0.3.0; generated DVMs include a valid input example for immediate validation.

Features

  • complete the local builder journey

View on GitHub
dvmctl 0.2.1-rc.2

dvmctl 0.2.1-rc.2

Generated DVMs and the builder runtime now use SDK 0.1.5-rc.9, so Tempo USD charges preserve the exact advertised six-decimal price.

Bug Fixes

  • preserve exact advertised Tempo prices

View on GitHub
dvmctl 0.2.1-rc.1

dvmctl 0.2.1-rc.1

Generated DVMs pin SDK 0.1.5-rc.8 and document the Moderato testnet switch for local test payments. Cashu drain preparation uses the current locked-output API and rejects mixed-keyset output metadata before persisting a refund batch.

Features

  • enable verified local test payments

View on GitHub
sdk 0.1.5-rc.7

sdk 0.1.5-rc.7

  • Development hosts now verify every configured Cashu, x402, and Tempo rail, expose their effective payment mode, and can report settled paid completions.

  • Cashu accumulator acceptance now requires valid mint-provided NUT-12 DLEQ evidence on every proof for both memory and PostgreSQL storage. Tokens from callers or mints that omit DLEQ are rejected and must be replaced with fresh compatible tokens.

  • Development Cashu can use a typed, process-local atomic backend with known test or loopback mints; its identity and state are discarded on restart.

Features

  • verify local test payments across all rails

Miscellaneous Chores

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

View on GitHub
dvm-cli 0.3.0

dvm-cli 0.3.0

Features

  • add network-aware Tempo test wallets

Bug Fixes

  • wait through npm release processing

View on GitHub
dvmctl 0.2.0-rc.2

dvmctl 0.2.0-rc.2

Features

  • refresh the builder scaffold and bundled skill

Bug Fixes

  • align the local paid test with caller output

  • complete the local Cashu test guide

  • create: pin the scaffold's vitest to 5.0.1 so npm 10 can install it

  • release: retry registry propagation

  • send structured data in the unpaid probe

View on GitHub
2026 · W38

14–20 September 2026

The dvm-cli wallet recovers from interrupted funding and cash-outs

  • sdk 0.1.3-rc.7 → 0.1.4-rc.7
  • dvm-cli 0.2.1
  • dvm-cli 0.2.1 recovers wallet funding and cash-outs after interruptions, expired invoices, ecash mint outages, and rate limits.
  • When the outcome of a wallet operation is unknown, dvm-cli 0.2.1 keeps it visible and says how to retry.
  • dvm-cli 0.2.1 keeps JSON output free of progress messages when it runs without a terminal, so an agent can parse it.
3 releases
dvm-cli 0.2.1

dvm-cli 0.2.1

Bug Fixes

  • bound capability expansion probes

  • keep pending wallet operations visible with clear retry guidance when their outcome is unknown

  • keep non-interactive JSON output free of progress messages while retaining interactive and human-mode notices

  • preserve saved providers during concurrent CLI use and report unreadable data without overwriting it

  • recover wallet funding and cash-out operations after interruptions, expired invoices, mint outages, and rate limits

  • release: retry consumer registry propagation

  • retain polling messages across repeated reads, including anonymous jobs

  • validate discovery numeric options

Maintenance

  • share search and browse job handling while preserving their distinct output formats

  • update the DVM SDK and Cashu dependencies and support Node.js 22 or newer

View on GitHub
sdk 0.1.4-rc.7

sdk 0.1.4-rc.7

Dependencies

  • upgrade cashu-ts for keyset rotation

Miscellaneous Chores

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

View on GitHub
sdk 0.1.3-rc.7

sdk 0.1.3-rc.7

Bug Fixes

  • release: retry registry propagation

Miscellaneous Chores

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

View on GitHub
2026 · W37

7–13 September 2026

First release candidate of dvmctl, the builder's CLI

  • sdk 0.1.0-rc.7 → 0.1.2-rc.7
  • dvm-cli 0.2.0
  • dvmctl 0.1.0-rc.1 → 0.1.0-rc.2
  • dvmctl 0.1.0-rc.1 is the first release candidate of the standalone command-line tool for building a DVM, a pay-per-use service.
  • dvm-cli 0.2.0 adds exact controls for payments a service asks for while a job is running.
2 features
  • dvm-cliadd exact mid-job payment controls
  • dvmctlintroduce standalone builder CLI
6 releases
dvm-cli 0.2.0

dvm-cli 0.2.0

Features

  • add exact mid-job payment controls

Bug Fixes

  • release: retry registry propagation

View on GitHub
sdk 0.1.2-rc.7

sdk 0.1.2-rc.7

Miscellaneous Chores

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

View on GitHub
sdk 0.1.1-rc.7

sdk 0.1.1-rc.7

Miscellaneous Chores

  • merge reviewed changes

  • merge reviewed changes

  • merge reviewed changes

View on GitHub
sdk 0.1.0-rc.7

sdk 0.1.0-rc.7

Bug Fixes

  • update Hono CORS parser

View on GitHub
dvmctl 0.1.0-rc.2

dvmctl 0.1.0-rc.2

Bug Fixes

  • run pinned npm shim in commonjs scope

View on GitHub
dvmctl 0.1.0-rc.1

dvmctl 0.1.0-rc.1

Features

  • introduce standalone builder CLI

Bug Fixes

  • repair base-owned release policy shell syntax

Continuous Integration

  • establish verification and guarded release candidates

View on GitHub
2026 · W36

31 August – 6 September 2026

First releases of dvm-cli and sdk

  • sdk 0.1.0-rc.1 → 0.1.0-rc.6
  • dvm-cli 0.1.0-rc.1 → 0.1.5
  • dvm-cli 0.1.4 publishes the caller CLI on npm as @dvmkit/dvm-cli, and 0.1.5 runs it on the published sdk package.
  • sdk 0.1.0-rc.1 is the first release candidate of the library a DVM, a pay-per-use service, is built on.
  • sdk 0.1.0-rc.2 lets a server report payouts, clear out expired prepaid credit, and keep an emptied x402 channel (a stablecoin balance a service draws from) open for a refill.
7 features
  • sdkexport the caller's shared modules through the internal entry point
  • dvm-clidepend on the published SDK package and retire the vendored modules
  • sdkexport the caller credit store through the internal entry point
  • dvm-cliadd client compatibility and standalone verification
  • sdkexport the remaining platform-shared symbols through the internal entry point
  • sdkexpose the platform-shared modules through an internal entry point
  • sdkreport payouts, sweep expired credits and keep emptied x402 channels refillable
13 releases
sdk 0.1.0-rc.6

sdk 0.1.0-rc.6

Features

  • export the caller's shared modules through the internal entry point

View on GitHub
sdk 0.1.0-rc.5

sdk 0.1.0-rc.5

Features

  • export the caller credit store through the internal entry point

View on GitHub
sdk 0.1.0-rc.4

sdk 0.1.0-rc.4

Features

  • export the remaining platform-shared symbols through the internal entry point

View on GitHub
sdk 0.1.0-rc.3

sdk 0.1.0-rc.3

Features

  • expose the platform-shared modules through an internal entry point

View on GitHub
dvm-cli 0.1.5

dvm-cli 0.1.5

Features

  • depend on the published SDK package and retire the vendored modules

View on GitHub
sdk 0.1.0-rc.2

sdk 0.1.0-rc.2

Features

  • server: report payouts, sweep expired credits and keep emptied x402 channels refillable

View on GitHub
dvm-cli 0.1.4

dvm-cli 0.1.4

Bug Fixes

  • publish the caller as @dvmkit/dvm-cli

View on GitHub
dvm-cli 0.1.3

dvm-cli 0.1.3

Bug Fixes

  • compare Tempo dollar limits in native units

View on GitHub
dvm-cli 0.1.2

dvm-cli 0.1.2

Bug Fixes

  • cli: await asynchronous command actions

View on GitHub
sdk 0.1.0-rc.1

sdk 0.1.0-rc.1

Documentation

  • establish the licence and contribution policy

Continuous Integration

  • allow the published contact addresses in the public-safety scan

  • verify and release the package from hosted runners

Miscellaneous Chores

  • initialize dvmkit SDK

  • prepare the first release candidate

View on GitHub
dvm-cli 0.1.1

dvm-cli 0.1.1

Bug Fixes

  • release: recover release bookkeeping

  • restore inherited credit posture

View on GitHub
dvm-cli 0.1.0

dvm-cli 0.1.0

Bug Fixes

  • preserve release candidate metadata

Miscellaneous Chores

  • release: prepare stable CLI release

View on GitHub
dvm-cli 0.1.0-rc.1

dvm-cli 0.1.0-rc.1

Features

  • add client compatibility and standalone verification

Bug Fixes

  • allow public GitHub squash identities

Continuous Integration

  • complete the release candidate lifecycle

View on GitHub