-
Notifications
You must be signed in to change notification settings - Fork 71
feat: add id_from_pos support
#155
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
Conversation
87e1cca to
ff8e4ac
Compare
evanlinjin
left a comment
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.
Looks good to me. I would just change naming to be a bit more "conventional". I.e. transaction_id should be txid.
ff8e4ac to
76f7fc8
Compare
oleonardolima
left a comment
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 76f7fc8
76f7fc8 to
a871b08
Compare
oleonardolima
left a comment
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 a871b08
ValuedMammal
left a comment
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.
ACK a871b08
evanlinjin
left a comment
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.
ACK a871b08
… support
a871b084ec04b86d8c326a44f817038c5afe1c8e feat: add `id_from_pos` support (Wei Chen)
Pull request description:
This PR introduces the `blockchain.transaction.id_from_pos` feature from Electrum. This functionality is essential for an ongoing implementation in `bdk_electrum`, which requires retrieving the coinbase transaction from a block at a specified `height`. Currently, there is no straightforward method to achieve this. By implementing the `id_from_pos` feature, we will effectively address this gap.
ACKs for top commit:
oleonardolima:
utACK a871b084ec04b86d8c326a44f817038c5afe1c8e
ValuedMammal:
ACK a871b084ec04b86d8c326a44f817038c5afe1c8e
evanlinjin:
ACK a871b084ec04b86d8c326a44f817038c5afe1c8e
Tree-SHA512: e8f1ab44473f67030b4f19e766fcee472b7cfc1dac6df8c9f0e08d966e0ed48289de03768771623b9fc7e7ef15dacdb7e3b26c04f9b0de7566d67cc7585a7fa6
This PR introduces the
blockchain.transaction.id_from_posfeature from Electrum. This functionality is essential for an ongoing implementation inbdk_electrum, which requires retrieving the coinbase transaction from a block at a specifiedheight. Currently, there is no straightforward method to achieve this. By implementing theid_from_posfeature, we will effectively address this gap.