You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently staker program tracks state of managed transactions only in important points of their lifecycle.
This can lead to local view of state of transaction diverging from the state which transaction really have on btc chain. Examples:
if staking transaction was send and confirmed on btc chain but later its timelock would expire, and staker would spend transaction using different means than staker program, then staker program would not know about it
if transaction is slashed, and slashing transaction is send to btc, staker program does not know about it
better usage of rpc api exposed by wallet - api exposed by bitcoind https://developer.bitcoin.org/reference/rpc/ is pretty complete, and it would be possible to do most logic by wallet. Problem is, most of those methods are not implemented by btcdwallet, or are not exposed by rpcclient provided by btcd, so we would need to probably ditch btcdwallet support and add missing methods to rpc client.
some how grown solution - with each incoming blocks check status of our request on btc chain and adjust state of our staking request accordingly.
The text was updated successfully, but these errors were encountered:
Currently staker program tracks state of managed transactions only in important points of their lifecycle.
This can lead to local view of state of transaction diverging from the state which transaction really have on btc chain. Examples:
This can lead to confusion on behalf of the user.
Potential solutions:
The text was updated successfully, but these errors were encountered: