-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(rpc): gettxchainlocks
should return mempool=false
when tx not in mempool
#5742
feat(rpc): gettxchainlocks
should return mempool=false
when tx not in mempool
#5742
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a breaking change and cannot be merged until v21
gettxchainlocks
should return null when tx not in mempoolgettxchainlocks
should return null when tx not in mempool
gettxchainlocks
should return null when tx not in mempoolgettxchainlocks
should return mempool=false when tx not in mempool
Updated this for backward compatibility. |
gettxchainlocks
should return mempool=false when tx not in mempoolgettxchainlocks
should return mempool=false
when tx not in mempool
gettxchainlocks
should return mempool=false
when tx not in mempoolgettxchainlocks
should return mempool=false
when tx not in mempool
3c71b99
to
fdfa815
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Help text (description and RPCResult
) should be updated accordingly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs release notes; otherwise looks good :)
Applied suggestions + added func test case for |
Co-authored-by: Konstantin Akimov <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
Co-authored-by: UdjinM6 <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
Fixed CI. |
ah, right, node1 is isolated, can't use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK for squash merge
Issue being fixed or feature implemented
Platform (in the scope of Withdrawals) need to be aware if a tx isn't in mempool when requesting status of a tx using RPC
gettxchainlocks
.cc @markin-io
What was done?
GetTransaction
and saving the result for checking latter.Example:
tx1
is mined and chainlocked,tx2
is in mempool andtx3
doesn't exist.The result now is:
[ { "height": 830, "chainlock": false, "mempool": true }, { "height": -1, "chainlock": false, "mempool": true }, { "height": -1, "chainlock": false, "mempool": false } ]
How Has This Been Tested?
Breaking Changes
Checklist: