-
Notifications
You must be signed in to change notification settings - Fork 18
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
refactor: pass around block refs #1221
Conversation
block ref from the database
da4e9f3
to
3f87d31
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.
You know, I was actually thinking about this when doing the info
endpoint since I wanted something that returned both the canonical hash/height, but opted to keep it simple and do an extra call.
What I was thinking would that it would be best if methods took an AsRef<BitcoinBlockHash>
that need a block hash and we implemented that for BitcoinBlockRef
and get_canonical_bitcoin_chain_tip()
returns one too.
Thoughts?
with outdated chain tips
Description
Changes
transaction_signer
module to expect aBitcoinBlockRef
.Testing Information
This is a refactor, so if tests pass then we should be good.
Checklist: