Use our own structs for handling btc-staking state. This is needed so that we can add fields to these underlying structs. This also removes the use of Binary from state structs (related to #17).
Now we have our own state::staking structs:
BtcDelegation (converted from btc_staking_api::ActiveBtcDelegation).
BtcUndelegationInfo (converted from btc_staking_api::BtcUndelegationInfo).
CovenantAdaptorSignatures (converted from btc_staking_api::CovenantAdaptorSignatures).
SignatureInfo (converted from btc_staking_api::SignatureInfo)
This PR also removes optional from btc_undelegation, for simplicity / clarity.
Take into account that these changes are API-breaking for the delegations queries. Likely the structs on the Go side will need to be adapted as well.
Use our own structs for handling
btc-staking
state. This is needed so that we can add fields to these underlying structs. This also removes the use ofBinary
from state structs (related to #17).Now we have our own
state::staking
structs:BtcDelegation
(converted frombtc_staking_api::ActiveBtcDelegation
).BtcUndelegationInfo
(converted frombtc_staking_api::BtcUndelegationInfo
).CovenantAdaptorSignatures
(converted frombtc_staking_api::CovenantAdaptorSignatures
).SignatureInfo
(converted frombtc_staking_api::SignatureInfo
)This PR also removes optional from
btc_undelegation
, for simplicity / clarity.Take into account that these changes are API-breaking for the delegations queries. Likely the structs on the Go side will need to be adapted as well.