-
Notifications
You must be signed in to change notification settings - Fork 55
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
Use Bitcoin types everywhere #262
Comments
IMO, I have covered all basic structs , though I will add new subtasks in case if found any. |
Hey @KnowWhoami I would like to work on this issue. Can I be assigned to it ? |
Go ahead. |
@KnowWhoami , Do we need to make these type changes across all the files ? |
Yes this should be applied across all modules in the lib wherever applicable. |
Can you please tell me whether the fee_rate is in satoshi per virtual byte (sat_per_vb) or per kilo virtual byte (sat_per_kvb) ? |
|
No, |
Yes, but the FreeRate struct offers two methods: sat per vbyte and other sat per kilo vbyte. Should i go with per kilo vbyte? |
Any one of them works. I would go for sat per vbyte as thats the defacto unit used in most places. And we will use that or our apps too. |
Can you please review the pr#342 and notify the changes that need to be made ? |
looking into #342 |
I think i can start working on this issue again. Should i open independent pr for updating types of amount, feeRate, locktime or just a single pr after making all the changes? |
Single pr works. |
rust-bitcoin
dependency, we attempted to replace all primitive types with the alternativerust-bitcoin
types in update bitcoin to v0.32 #182.But there are many places still left to apply these changes , thus created subtasks for them.
Use
Amount
type for denoting Bitcoin amounts instead of plainu64
.coinswap/src/protocol/contract.rs
Line 57 in 57bf238
Use
FeeRate
type for fee-rate.Use
locktime::relative::LockTime
for denoting relative locktime instead ofu16
.Use
BlockHeight
for denoting the height of a block.The text was updated successfully, but these errors were encountered: