You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[kotlin-sdk] Split build/broadcast with reservation release for BIP70-style deferred submission #4089
Priority: P0 — hard blocker for the BIP70/BIP270 (CTX/DashSpend) send cutover; structurally impossible on sendToAddresses (those protocols sign, POST to a merchant server, and broadcast only on ack). Implementation will be driven by @bfoss765 — this issue tracks design agreement.
Ask: expose the existing internal build/broadcast split with an explicit reservation lifecycle:
The internal new → setFunding → buildSigned already produces exactly this (UTXOs reserved at buildSigned); the manager remains the sole driver so the CoreTransactionBuilder KDoc's safety argument is preserved.
Release path: abandon/release is owner-token-guarded, so a merchant-nack (the BIP70 "signed, POSTed, not acked" case) frees the inputs for an immediate rebuild without being able to free a newer build's reservation.
Field evidence: the wallet's scanned-invoice flow (PaymentProtocolFragment → l1DeferredBuild → merchant ACK → l1DeferredBroadcast) has been running against this surface on the 11.10.x QA line, including a live nack/reservation-release exercise via the local BIP70 test server.
Residual design questions about unifying this with build_signed_payment are tracked separately in #4263, so nothing remains for this issue to hold open.
Activity
feat(kotlin-sdk): split build/broadcast with reservation release for …
feat(kotlin-sdk): split build/broadcast with reservation release for …
feat(kotlin-sdk): split build/broadcast with reservation release for …
feat(kotlin-sdk): split build/broadcast with reservation release for …
bfoss765 commentedon Aug 17, 2026
Closing as shipped. The asked-for surface exists on
v4.2-devand is what the Android BIP70 flow runs in production QA builds today:CoreWalletfinalize produces aSignedCoreTransaction(txid, raw bytes, fee, reservation token + height) without touching the network.core_wallet_signed_payment_broadcastsubmits a previously-finalized payment via theSignedPaymentRegistry, with generation-liveness and reservation-age guards (feat(kotlin-sdk): split build/broadcast with reservation release for BIP70-style deferred submission #4185's successor work, plus the age-guard hardening in fix(platform-wallet): age-guard the finalized-transaction handle broadcast #4309).Field evidence: the wallet's scanned-invoice flow (
PaymentProtocolFragment→l1DeferredBuild→ merchant ACK →l1DeferredBroadcast) has been running against this surface on the 11.10.x QA line, including a live nack/reservation-release exercise via the local BIP70 test server.Residual design questions about unifying this with
build_signed_paymentare tracked separately in #4263, so nothing remains for this issue to hold open.