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] Core send should return the signed raw transaction, fee, and change address #4079
Priority: P1 — smallest change with the largest unlock for the dash-wallet send-path cutover (Phase 5c). App-side workaround exists (poll the SDK Room transactions row for the bytes) but is timing-fragile with no contract.
ManagedPlatformWallet.sendToAddresses returns only the txid hex. The signed consensus bytes, fee, and change address all exist Rust-side at broadcast time (the FFI box owns the tx bytes; they later land asynchronously in Room transactions.transactionData).
Ask:
data classBroadcastCoreTransaction(
valtxidHex:String,
valrawTxBytes:ByteArray, // consensus-encoded signed tx, exactly what was broadcastvalfeeDuffs:Long,
valchangeAddress:String?
)
suspendfun ManagedPlatformWallet.sendToAddressesEx(...): BroadcastCoreTransaction
One new FFI accessor (e.g. coreTransactionGetBytes) before coreTransactionFree; identical build/broadcast pipeline. With the raw bytes the wallet reconstructs a dashj Transaction and commits it locally, which makes confidence listeners, output locking, memo/exchange-rate persistence and result-screen states work unchanged across the cutover ("bridge" strategy, wallet plan Phase 5c).
Fixed by #4308. buildSignedPayment returns a SignedCoreTransaction with txidHex, rawTxBytes and feeDuffs, and broadcastSigned broadcasts it. There is no separate change-address field; it can be read from rawTxBytes. Closing.
Activity
HashEngineering commentedon Nov 9, 2026
Fixed by #4308.
buildSignedPaymentreturns aSignedCoreTransactionwithtxidHex,rawTxBytesandfeeDuffs, andbroadcastSignedbroadcasts it. There is no separate change-address field; it can be read fromrawTxBytes. Closing.