Repository navigation
v0.17.0
·
73 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Minor Changes
- With prepaid requests and a top-up amount configured,
TempoSessionProvidertops a session channel up in the background once its deposit no longer covers the prepaid balance plus the next request, so the on-chain top-up does not hold up a later request. (by @brendanryan, #630) - Added
MppError::CredentialReplayedandErrorCode::CredentialReplayed: replayed Tempo charge credentials (used transaction hashes and proofs, duplicate submissions, settled transfers whose memo is bound to another challenge) are now answered with a403verification-failedproblem and noWWW-Authenticatechallenge orchallengeId, so clients do not pay again. A transaction credential whose broadcast or settlement failed releases its submission claim, as in mppx, so resending it retries instead of being rejected as a replay. (by @brendanryan, #630) - Add
ChargeMethod::validate_expected_requestso payment methods can compare - selected method-specific fields against a route's expected charge request before
- validation or broadcast. The default accepts additional fields, preserving
- existing methods, and all existing core comparisons and credential checks remain
- in place. (by @brendanryan, #630)
- Exposed the payer verified by charge validation as
payeronChargeValidationandPaymentSuccessContext; Tempo charge validation reports the transaction sender, the proof signer, or the account the matched transfers of a hash credential debited. (by @brendanryan, #630) - Added
ForwardProxybehind theforward-proxyfeature: a local HTTP forward proxy that lets programs that know nothing about MPP, such ascurl, pay for MPP services. It terminates TLS for the origins itsAcceptPaymentPolicyallows with certificates from a per-process certificate authority, pays402challenges with a provider per origin, retries and streams the response back, and tunnels every other host untouched.ForwardProxy::environmentreturns the proxy and trust variables for child processes, anddirectory::service_urlsfetches the services listed in an MPP directory such as mpp.dev's. (by @brendanryan, #630) PaymentResponseContext::funding_currencyreports the token the payer actually spent, through the newPaymentProvider::funding_currency.TempoAccountsProviderreports MACH when it pays a machine-token-enabled charge through the swapper and the autoswap input token when it swaps, so clients can label a charge correctly even when the server's receipt does not say how it was funded. MCP clients can read it from the provider before committing a payment. (by @brendanryan, #630)- Fund machine-token charges with MACH through its canonical swapper, matching mppx; the legacy machineUSD session route keeps its deployment.
TempoAccountsProvider::with_preferred_currencynow selects the first charge or session funded from the preferred currency across intents, including machine-token-enabled charges when the preferred currency is MACH. Addwith_fee_tokenandwith_session_fee_tokenso sessions denominated in a recipient-restricted token, such as MACH channels under TIP-1095, can pay unsponsored gas in another token. AddTempoSessionProvider::acknowledge_acceptedso metered SSE responses, whosepayment-receiptandpayment-need-voucherevents report acceptance in the body rather than aPayment-Receiptheader, can resolve a pending channel open, andTempoAccountsProvider::sessionto reach the session provider that pays its challenges. A pending open whose authorization is already settled on-chain is resolved before the next voucher and on restore.TempoAccountsProviderreuses one settlement RPC client per URL instead of opening a connection for every charge, and machine-token route discovery reads the balance and simulates the route concurrently. (by @brendanryan, #630) - Session channels can be topped up and closed over MCP. A
ManagementTransportdelivers a management credential to the resource that issued its challenge, andPaymentProvider::pay_with_managementpays a challenge with any top-up the payment needs sent through it instead of HTTP. It defaults topay_with_context;TempoSessionProvider,TempoAccountsProviderandMultiProviderimplement it.TempoSessionProvider::close_withcloses a channel through a transport. mcp::client::McpManagementis the MCP transport: it repeats a tool call with the credential in_meta, as mppx's MCP server and Mercator accept top-ups and closes, and returns the receipt of the server's receipt-only result.McpClienttops a channel up this way when its deposit does not cover the call, andMcpClient::managementreturns the transport for closing. Before, an MCP session whose deposit ran out failed withsession cumulative amount exceeds channel deposit.ToolCaller::receipt_from_outputandmcp::extract_receiptread a result's receipt.McpClientpasses the receipt of each paid call to the provider, andMcpPayment::record_receiptdoes so for SDK adapters that run their own retry. (by @brendanryan, #630)- Report what payments cost and where money moves, so clients can show spending without tracking channels themselves:
PaymentResponseContext::amountis what the server charged for the request: a charge's amount, or for a session the change in the channel'sspentfrom the receipt. Providers report session costs through the newPaymentProvider::record_receipt, which defaults toobserve_receiptand no amount.- A new
channel.depositevent (ClientEvent::Deposit,ClientEvents::on_deposit) reports when the server accepts a session channel's open or a top-up, including background top-ups, with the URL, channel, token, amount added and resulting deposit. Enable it withTempoSessionProvider::with_eventsorTempoAccountsProvider::with_session_events. PaymentProvider::stream_eventlets a provider answer payment events in a response stream;TempoSessionProviderandTempoAccountsProvideranswer mppxpayment-need-voucherandpayment-receipt.ForwardProxyuses it for paidtext/event-streamresponses, so a session stream that asks for more vouchers keeps flowing to a client that knows nothing about MPP. (by @brendanryan, #630)- Answer bare
402challenges with an RFC 9457application/problem+json payment-requiredproblem, as mppx does, instead of{"error": "Payment Required"}.- This applies to the axum
PaymentRequiredandPaymentOffersresponses and to HttpTransport::respond_challenge.ChallengeContext::erroris nowOption<&MppError>(wasOption<&str>):HttpTransportsends the error's problem details with its status, andWsTransportsends the problem'sdetail.- A
500problem, sent without a challenge, carries nochallengeId. (by @brendanryan, #630) PaymentResponseContextnow carries the paid request'surland the response's boxedreceipt, sopayment.responsehandlers can show who was paid and the settlement reference (a charge's transaction or a session's channel) without parsing headers. A session receipt is included only when it matches the challenge and the paying channel, as before. (by @brendanryan, #630)- Added prepaid session vouchers.
TempoSessionProvider::with_prepaid_requests(andTempoAccountsProvider::with_session_prepaid_requests) keep a few requests' worth of balance, at the latest request's price, prepaid on the channel, and send the voucher with the next request to the same URL instead of waiting for a402. This needs a server whose session challenges are reusable (mppxreusableChallenges); any402falls back to the normal flow.PaymentProvidergains theprepaid_credentialandobserve_receipthooks the payment flow uses for this. (by @brendanryan, #630) TempoAccountsProvider::preconnectprimes the first prepaid voucher. After restoring a session channel, it asks the server again with aPayment-Sessionheader naming that channel and reads the session snapshot in the challenge.TempoSessionProvider::prime_prepaidsizes the URL's first prepaid voucher from the snapshot'sspent. The first request of a new process then carries its voucher instead of waiting for a402, and when earlier vouchers already cover the server'sspentplus the request, it raises the cumulative amount by one unit instead of by the request's price.TempoSessionProvider::restored_channel_idreports the in-memory channel a challenge would pay from. (by @brendanryan, #630)- Added
send_with_exchangeand madeExchangeandFlowErrorpublic, so the HTTP 402 payment flow can run over a host application's HTTP stack instead of areqwest::Client. Request failures keep the exchange's own error type. (by @brendanryan, #630) - Add
ChargeClientfor explicitly authorized charge payments using either AuthorizationorPayment-Authorization. The SDK owns the HTTP client and- disables redirects for initial requests and paid retries. Session offers are
- filtered before provider preparation, and the prepaid-credential hook is skipped.
- Existing Fetch, middleware, and session management custom-header restrictions
- remain in place. (by @brendanryan, #630)
- Added SDK helpers for session clients.
TempoAccountsProvider::with_sqlite_session_storeopens the shared SQLite channel store namespaced by a service's origin, andTempoAccountsProvider::preconnectsends an unpaid probe and restores the channel it would pay.TempoSessionProvider::spendreports what the server charged for requests paid through the provider and the deposit left, from payment receipts, andTempoSessionProvider::stream_eventhandles mppxpayment-need-voucherandpayment-receiptSSE events. (by @brendanryan, #630) - Added
TempoSessionProvider::restore, which loads the channel a session challenge would pay from the durable store into memory, checked against chain state, without signing, so a client can prepare before its first paid request. (by @brendanryan, #630) TempoAccountsProvider'swith_session_*settings (deposit, top-up, maximum deposit, fee token, prepaid requests, events) no longer depend on the session store: they apply whether they are set before or afterwith_session_store, and survive a store change. A configured wallet'swith_sqlite_session_store(service)is therefore that service's wallet, with the same settings and its own channels, instead of silently dropping settings set earlier. (by @brendanryan, #630)sse::ServeOptionsandws_session::WsSessionOptionstake abefore_chargecheck that runs before each value is charged and delivered, andSessionMethod::stream_checkprovides one that stops the stream when the channel's on-chain escrow has a pending close, was withdrawn, or cannot be read, caching successful reads for five seconds and counting amounts settled on chain above the highest accepted voucher as spent (settling an accepted voucher keeps its unspent credit). The check runs once per value, not on every poll while the stream waits for a voucher. (by @brendanryan, #630)TempoSessionProvider::stream_eventrecords thespentof eachpayment-receiptevent that a streaming response carries. Servers send these events when they charge a request while its output is delivered or settle it at its final usage. Whenspentchanged, the provider adds the change to its spend ledger, sospend()follows the stream, and emits the newClientEvent::PaymentUpdate(payment.update,PaymentUpdateContextwith the URL, channel, newspentand signed change).ClientEvents::on_payment_updatesubscribes to it. (by @brendanryan, #630)- Added
with_currencies,with_max_amountandwith_max_atomic_amounttoTempoProviderso clients skip and refuse charges in other currencies or above a per-charge cap.MultiProvidernow falls through to the next payment method when a provider rejects all of its offers. (by @brendanryan, #630) - Servers verify TIP-1034 channel reserve precompile sessions: when a session's escrow is the precompile, open, voucher, topUp and close credentials must carry a channel descriptor that hashes to the channel id, opens are checked against the descriptor (payer, payee, operator, token, salt, signer, expiringNonceHash), vouchers accept TIP-1020 primitive signatures (so P-256 access keys can pay), state is read with getChannelState, and closes require the cooperative close authorization and capture only what was spent. Legacy escrow sessions are unchanged. (by @brendanryan, #630)
- Add opt-in RFC 9457 JSON bodies to
PaymentLayerandPaymentBodyLayerwith with_problem_details. Applications supply a JSON-bytes-to-body callback while- existing layers retain empty response bodies by default. Payment rejections keep
- their status and retry challenge; internal failures return a generic 500 problem
- without exposing backend details.
- Generated 400 and 413 responses from these layers now carry
Cache-Control: no-store, with or without problem details.- Untyped
PaymentVerifier::verifyerrors, including those fromfrom_fns, are - reported as a generic
verification-failedproblem without the verifier's message. (by @brendanryan, #630)
Patch Changes
- Raised the Authorization credential size limit from 16 KiB to 64 KiB, matching mppx, and applied it to the raw header before scheme extraction. A credential echoes its challenge, so credentials for challenges with a
requestnear its 16 KiB limit or a largeopaquewere rejected even though mppx accepts them.extract_payment_schemenow returnsNonefor headers over 64 KiB instead of tokenizing them. Challengerequestand receipt limits are unchanged. (by @brendanryan, #630) - Reject zero-amount Tempo charge proofs when a payment challenge names a realm other than the requested host. Apply the check to HTTP payments, session bootstrap, MCP payments, and WebSocket clients. Respect a caller-supplied HTTP Host header, and allow a different server realm only when explicitly pinned to its HTTP origin with
with_trusted_tempo_proof_realm. - The Axum extractors can use the HTTP request hostname as the default challenge realm and verify against the same realm, matching mppx when the hostname is configured through
.trusted_hosts([...]). This explicit list prevents a client-controlledHostheader from choosing a victim server's proof realm. An explicit.realm(...)orMPP_REALMstill takes precedence. Unlisted hosts and servers issuing challenges outside an HTTP request (such as directMpp::chargecalls or WebSocket handlers) continue to use their configured or environment-detected realm; those servers must configure a realm matching their public hostname or clients must pin the realm to its HTTP origin. Without that configuration, zero-amount Tempo proofs fail closed. (by @brendanryan, #630) - Bounded each session management request (top-up, voucher and close), including reading an error response's body, to 30 seconds, failing with an unknown payment outcome instead of holding the payment lock while a server stalls. A top-up whose outcome is unknown, including one whose management transport fails with
MppError::Http, blocks further top-ups on that channel until it is reconciled, so a late-applied deposit is not signed again. (by @brendanryan, #630) ws_session::process_vouchersnow rejects inbound WebSocket frames larger than the newMAX_INCOMING_MESSAGE_BYTES(64 KiB) before parsing them: it sends apayment message is too largeerror frame and ends processing with anInvalidPayloaderror. The deprecatedprocess_incoming_vouchersskips such a frame unparsed and keeps reading until the connection ends. (by @brendanryan, #630)- TIP-1034 close credentials carry the cooperative close authorization (
closeSignature), a distinct EIP-712CloseAuthorizationsignature over the channel and amount that mppx servers have required since 0.13.1. Without it,TempoSessionProvider::closeandclose_withwere rejected by mppx 0.13 and 0.14 servers, including tempoxyz/mpp-proxy and Mercator.precompile_close_authorization_signing_hash_with_escrowand thesign_precompile_close_authorization*functions are exported, and the hash matches viem's for mppx's typed data. (by @brendanryan, #630) compose_verify_with_expected_requestsnow dispatches a credential to the route whose handler issued its challenge for that route's expected request when several routes share a payment method, such as two Tempo handlers with different currencies, recipients or scopes, instead of checking it against the first handler for that method. AddedChargeVerifier::issued_credential_for, whichMppimplements with its challenge HMAC and expected-request checks (including every currency it offers). (by @brendanryan, #630)- Sessions now read on-chain channel state concurrently with the stored channel when accepting a voucher; stored-channel errors still take precedence over a failed on-chain read. (by @brendanryan, #630)
- Signed server session close transactions with an expiring nonce instead of the close signer's sequential nonce, so independent server processes sharing a close signer no longer race for the same nonce.
- The pending close records the transaction's
valid_before, and reconciliation releases a channel whose close is still unmined 30 seconds past it (matching mppx's clock-skew margin), so a close that can no longer land does not leave the channel stuck inclosing. For TIP-1034 channels it reads the precompile'sgetChannelStateat a block pastvalid_beforeand releases the channel only while it is still funded with no close request, as mppx does; otherwise the channel stays blocked. (by @brendanryan, #630) - Tempo charge transactions now cap
validBeforeat the second after the challengeexpiresinstead of flooring it, so a fractional or current-instant expiry no longer yields an already-passed deadline. (by @brendanryan, #630) - Background session top-ups read chain state and sign without holding the payment lock, which they now take only to record the new deposit. (by @brendanryan, #630)
- Paid gas for unsponsored charges funded with MACH (a MACH charge or a MACH swapper route) in a funded stablecoin (pathUSD, then the network's default currency), since MACH cannot pay its own fees. Only the chain's canonical MACH deployment triggers this. (by @brendanryan, #630)
McpPayment::prepare,prepare_with_managementandMcpClient::call_toolpay the next supported challenge in preference order when paying the preferred one fails, and return the first failure only when none can be paid. A wallet that cannot fund a session's suggested deposit, such as Mercator's 5 MACH minimum, now pays the server's one-time charge instead of failing the call. (by @brendanryan, #630)- When a paid retry, or a request sent with a prepaid credential, returns a 5xx response or fails to send, the client now emits
payment.failedwithPaymentFailureReason::OutcomeUnknown, carrying the status, the serialized credential and, for Tempohashcharge credentials, the transaction hash, and still returns the response. A 5xx without a receipt now keeps the provider's optimistic payment state, as a lost response does, instead of rolling it back. (by @brendanryan, #630) scrub_response_headersnow strips payment protocol headers an upstream service returns (Accept-Payment,Payment-Authorization,Payment-Receipt,Payment-Required,Payment-Response,Payment-Session,Payment-Session-Snapshot,Payment-Signature), dropsAuthorizationvalues using the Payment scheme, and removes Payment challenges fromWWW-Authenticatewhile keeping other schemes. Proxied requests also stripPayment-SessionandPayment-Session-Snapshot.- A Payment challenge hidden by a quote that opens on one
WWW-Authenticateline and closes on the next is dropped too, and the auth-param tokenizer now reads long comma-separated values in linear time. (by @brendanryan, #630) - Tempo charge receipts now report
fundingCurrency, the token the payer spent, when the payment uses a recognized route: the payment currency for direct transfers, the DEX swap input token, or MACH for the machine-token swapper route. Transaction credentials read it from the signed transaction; final hash credential receipts look the transaction up once. Unrecognized routes, other senders, failed lookups and zero-amount proofs omit it without changing payment acceptance. AddReceipt::with_funding_currencyandReceipt::funding_currency. (by @brendanryan, #630) - Re-check Tempo charge challenge expiry right before broadcasting a transaction credential (and before accepting a proof), and treat an
expiresequal to the current time as expired. (by @brendanryan, #630) - Recover a Tempo charge whose
eth_sendRawTransactionSynccall returns an RPC error after the node included the transaction: the server now looks up the receipt for the broadcast hash and, if it exists, verifies it like a normal reply instead of failing the paid request. Matches mppx. Recovery runs only when a replay store reserved the submission, so a server without one never re-accepts an already-mined transaction; an unrecovered broadcast releases its reservation so a retry can recover the charge once it lands. (by @brendanryan, #630) - Removed the obsolete
mpp_versionandmpp_is_mppmetadata from Stripe charge PaymentIntents, matching mppx. (by @brendanryan, #630) - Serialized session top-ups per payment scope, including background top-ups, and rechecked the deposit after waiting so concurrent requests through one provider no longer fund a channel twice or past
max_deposit. A wait for another top-up ends when the challenge expires, and a background top-up'schannel.depositevent reports only its own increase. (by @brendanryan, #630) TempoAccountsProvidernow applies its expected chain ID to session payments as it does to charges: a session challenge for another chain is rejected withMppError::ChainIdMismatchinstead of being paid with the expected chain's key and RPC. Prepaid session vouchers are checked against the pin too, and clones re-pinned to another chain no longer reuse a session provider built for the previous chain. (by @brendanryan, #630)- Stop charging session channels after the payer requested a forced close, as mppx does.
deduct_from_channelnow rejects a channel with a pending close request, as it already- did for a closing or finalized one, so
sse::serveandws_sessionstop with the final - receipt instead of delivering service the payer can withdraw before it is settled. (by @brendanryan, #630)
- Sessions pay gas for sponsored channel opens and top-ups in the
feeTokenthe server advertises. Clients defaulted to the session currency, so a sponsored MACH channel named MACH as its gas token and the server rejected it. (by @brendanryan, #630) - Session payments and prepaid vouchers raise a channel held in process memory to the cumulative amount and deposit recorded in the channel store before signing. When processes share a store, a process that had not used a channel since another process paid with it no longer signs a voucher that the server rejects as not greater than its highest accepted voucher. (by @brendanryan, #630)
- Sponsored charge transactions that install an access key are now rejected unless the server opts in with
TempoBuilder::fee_payer_allow_key_authorization(true)(orChargeMethod::with_fee_payer_allow_key_authorization(true)), matching mppx. Previously the fee payer sponsored key authorizations by default. (by @brendanryan, #630) - Require at least 15 seconds of remaining validity (
valid_before) before co-signing a fee-sponsored Tempo charge transaction and again before broadcasting it, matching mppx, so the sponsor does not pay for a transaction that can expire in flight. (by @brendanryan, #630) - Enforce the 15-second remaining-validity floor for fee-sponsored charges at issuance: the client refuses to sign a sponsored challenge that expires in under 15 seconds, and the server refuses to issue a sponsored charge challenge whose
expiresis under 15 seconds away (zero-amount proof charges are exempt, since nothing is co-signed). The client's default expiring-noncevalid_beforewindow stays at 25 seconds, matching mppx and Tempo's 30-second expiring-nonce maximum. A sponsormax_validity_window_secondsbelow 15 seconds is now rejected as misconfigured, and the window is counted from the current time rounded up, as in mppx. (by @brendanryan, #630) - Standardized Stripe PaymentIntent analytics metadata to match mppx: every PaymentIntent records
machine_payment, the SDK identifiermpp_sdk(mpp-rs/<version>),mpp_challenge_idandmpp_intent, and no longer recordsmpp_server_idormpp_client_id. ChallengemethodDetails.metadatais applied after these keys. (by @brendanryan, #630) - A Stripe charge credential whose
externalIddoes not match the request-boundexternalId(or omits it) is now rejected with theinvalid-challengeproblem (402), matching mppx'sInvalidChallengeError, instead ofverification-failed. It is still rejected before any PaymentIntent is created. (by @brendanryan, #630) - Background session top-ups hold the payment lock and store lease only while the top-up is signed and recorded, not while it is submitted, so vouchers for concurrent requests are not delayed. Recording a top-up raises the current channel entry's deposit instead of writing back the entry it was signed against. (by @brendanryan, #630)
- The default
ChargeChallenger::verify_payment_for_amount_and_scopeandverify_payment_for_amount_scope_and_bodynow verify framework route binding, as mppx does: instead of rejecting every scoped request, they re-issue the route's challenge withchallenge(orchallenge_with_body) and accept a credential only when its echoed challenge carries the route's_mppx_scopeand the same method, intent, body digest and pinned request fields (amount, currency, recipient and method details, as in mppx), so adescriptionthe re-issued challenge lacks does not reject it, so a credential issued for another route, amount, HTTP method or body is rejected. Custom challengers that bindChallengeOptions::mppx_scopeinto a deterministic challenge request now work with the Axum extractors without overriding these methods; theirverify_paymentmust still authenticate the echoed challenge. (by @brendanryan, #630)
What's Changed
- feat(tempo): MACH sessions and charges, streamed session acceptance, RPC reuse by @gakonst in #581
- fix(tempo): pay sponsored session gas in the advertised fee token by @gakonst in #582
- feat(client): prepaid session vouchers by @gakonst in #583
- feat(client): restore a session channel without paying by @gakonst in #584
- feat(client): top session channels up in the background by @gakonst in #585
- perf(client): sign vouchers while a background top-up is submitted by @gakonst in #586
- perf(client): prepare background top-ups without the payment lock by @gakonst in #587
- feat(client): public payment exchange by @gakonst in #588
- feat(client): SDK helpers for session clients by @gakonst in #589
- feat(client): forward proxy that pays for 402 responses by @gakonst in #590
- feat(client): payment.response carries the URL and receipt by @gakonst in #591
- feat(client): report payment costs, channel deposits and answer stream payments by @gakonst in #592
- chore(client): name the prepaid credential future type by @gakonst in #593
- feat(client): keep session settings across session stores by @gakonst in #594
- feat(client): report the token that funded a payment by @gakonst in #595
- fix(client): sign session vouchers above what other processes recorded by @gakonst in #596
- feat(client): prime the first prepaid voucher from the session snapshot by @gakonst in #597
- chore: pin gh-actions references to 35019557 by @sds in #598
- feat(client): follow in-stream session charges with payment.update by @gakonst in #599
- feat(client): top up and close session channels over MCP by @gakonst in #600
- fix(mcp): pay the next supported challenge when the preferred one fails by @gakonst in #602
- fix(tempo): sign the cooperative close authorization on TIP-1034 closes by @gakonst in #603
- ci: cut PR wall time from ~6.5 to ~2.5 minutes by @brendanjryan in #604
- ci: pin changelogs to the locked install fix by @brendanjryan in #605
- ci: per-partition feature caches, start the localnet early by @gakonst in #606
- fix(fuzz): drop serde_json's reserved keys from generated JSON by @brendanjryan in #607
- chore(ci): replace archived Tempo lints with standard checks by @decofe in #612
- fix(core): bound Authorization values at 64 KiB before extraction (mppx#1034) by @brendanjryan in #611
- fix: Bind Tempo proof realms to HTTP hosts by @decofe in #610
- fix(fuzz): use the 64 KiB authorization limit in fuzz_authorization (mppx#1034) by @brendanjryan in #613
- feat(server): verify TIP-1034 precompile sessions by @gakonst in #637
- feat(tower): add opt-in Problem Details response bodies by @brendanjryan in #638
- feat(server): add method-specific expected-request binding by @brendanjryan in #639
- chore: accept contributions through issues only by @brendanjryan in #640
- fix(tempo): re-check challenge expiry before broadcast (mppx#1078) by @brendanjryan in #636
- fix(stripe): reject unbound externalId as invalid-challenge (mpp-tools#94) by @brendanjryan in #641
- fix(axum): verify framework scope in default ChargeChallenger methods (AGR-2026-110) by @brendanjryan in #614
- fix(tempo): use expiring nonces for session close transactions (mppx#864) by @brendanjryan in #618
- feat(tempo): answer replayed charge credentials with 403 (mppx#1039) by @brendanjryan in #627
- fix(tempo): pay MACH charge gas in a stablecoin (mppx#843) by @brendanjryan in #616
- fix(tempo): stop charging a channel with a pending close request by @brendanjryan in #644
- fix(server): dispatch composed credentials to the issuing route (mppx#936) by @brendanjryan in #619
- feat(server): expose the verified payer on payment success (mppx#1038) by @brendanjryan in #628
- feat(tempo): add currency allowlist and per-charge caps to TempoProvider (mppx#1035) by @brendanjryan in #629
- fix(client): report unknown payment outcome when the paid retry returns 5xx (mppx#1043) by @brendanjryan in #631
- feat(client): add a redirect-safe charge client by @brendanjryan in #645
- feat(tempo): check live escrow before metered stream charges (mppx#1052) by @brendanjryan in #634
- feat(server): answer bare 402 challenges with payment-required problem details by @brendanjryan in #643
- perf(tempo): read on-chain channel concurrently with the stored channel on vouchers (mppx#1061) by @brendanjryan in #635
- fix(tempo): serialize session funding decisions (mppx#1050) by @brendanjryan in #632
- fix(tempo): answer settled hash replays with 403 again by @brendanjryan in #646
- fix(tempo): require remaining validity for sponsored transactions (mppx#1029) by @brendanjryan in #626
- fix(tempo): recover confirmed charges after broadcast RPC errors (mppx#1028) by @brendanjryan in #625
- fix(tempo): bound session management requests (mppx#1053) by @brendanjryan in #633
- feat(tempo): report receipt funding currency (mppx#915) by @brendanjryan in #620
- fix(tempo): apply expected chain pins to Accounts sessions (mppx#961) by @brendanjryan in #622
- ci: release weekly on mondays via scheduled auto-merge by @brendanjryan in #642
- ci: close PRs after 14 days of inactivity by @brendanjryan in #647
- fix(tempo): require opt-in for sponsored access keys (mppx#973) by @brendanjryan in #624
- fix(ws): bound inbound session payment frames (mppx#968) by @brendanjryan in #623
- feat(stripe): standardize PaymentIntent analytics metadata (mppx#860) by @brendanjryan in #617
- fix(proxy): strip payment headers from upstream responses (mppx#947) by @brendanjryan in #621
- fix(stripe): remove obsolete MPP metadata (mppx#816) by @brendanjryan in #615
- fix(tempo): cap charge validBefore at the second after challenge expiry (mppx#1042) by @brendanjryan in #630
- Release
v0.17.0by @tempo-github-sts[bot] in #601
Full Changelog: v0.16.0...v0.17.0