Skip to content

Original hash in callbacks
Compare
Choose a tag to compare
@cmeisl cmeisl released this 08 Jul 22:57
· 24 commits to master since this release
0.9.2
8ec3c30
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

When transactions are sped-up or cancelled, a new transaction is created with the same nonce and higher gas. This new transaction replaces the original in the mempool, effectively dropping the original transaction. This means the original transaction hash is defunct, never to be seen again.

With this update, our API provides the original transaction hash, as originalHash, in the transaction object passed to a handleNotificationEvent callback, allowing the Dapp to handle any additional UI updates that are tied to the original transaction hash. This is especially usefully if the Dapp uses the transaction hash as a key for backed services. The Dapp can now modify that key when receiving txSpeedup and txCancel events.

See https://github.com/blocknative/assist/tree/master#handling-notifications for details on handleNotificationEvent and the contents of the transaction object passed to the callback.

  • Add original hash (#316)
Assets 2
Loading