Skip to content

Replacement Transaction Payloads
Compare
Choose a tag to compare
@lnbc1QWFyb24 lnbc1QWFyb24 released this 26 Jan 21:10
· 88 commits to master since this release
4.0.0
8202a07
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

This is a breaking change to fix replacement transaction payloads to match our Webhook API

Previously if you received a replacement transaction status ('speedup' or 'cancel'), the hash parameter would refer to the new transaction hash and the replaceHash would refer to the original transaction hash that was replaced (flipped the wrong way around!). There rest of the payload would refer to the original transaction. So there was a major mismatch here that needed to be fixed.

The new behavior is that a replacement status is received, and the payload will refer to the original transaction that is being replaced. The hash will match the original hash. The replaceHash parameter now refers to the transaction hash that has replaced the original transaction. This allows for linking the original transaction to the new pending status notification that will be received for that new hash.

Changelog:

  • 3.7.1-1.0.0: [fix] - Replacement Transactions (#168)
Assets 2
Loading