feat: add support for Curios's confirmedTxHash - #912
Merged
Conversation
Member
|
can you fix the lint errors in ci please |
hugomrdias
requested changes
Aug 18, 2026
hugomrdias
left a comment
hugomrdias
left a comment
Member
There was a problem hiding this comment.
LGTM minus the hasher.ts changes
hugomrdias
approved these changes
Aug 20, 2026
github-project-automation
Bot
moved this from ⌨️ In Progress
to ✔️ Approved by reviewer
in FOC
hugomrdias
changed the title
This was referenced Aug 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the minimal compatibility layer for Curio's Replace-by-fee feature:
New:
confirmedTxHash will actually be queryable on chain if it exists, otherwise the previous hash will work.
Compat:
This change will break consumers of txHash.
Curio disabled Replace-by-fee until we decide it's time to do a rollout due to sufficient Synapse uptake that it's worth breaking the remaining txHash consumers.