Inability to sign staking transaction

[filippos47]

Version: v0.8.0

Tx gets pre-approved on bbn:

time="2024-10-17T07:52:57Z" level=debug msg="Received not enough covenant unbonding signatures on babylon" numSignatures=0 required=3 stakingTxHash=35a92bbe7c50bfa4421d8781bfd0f377b4562fc71a4ab3ec72c427a08b2f6c56
time="2024-10-17T07:53:17Z" level=debug msg="Received enough covenant unbonding signatures on babylon" numSignatures=5 stakingTxHash=35a92bbe7c50bfa4421d8781bfd0f377b4562fc71a4ab3ec72c427a08b2f6c56
time="2024-10-17T07:53:17Z" level=debug msg="Received staking event" event=UNBONDING_TX_SIGNATURES_CONFIRMED_ON_BABYLON eventId=35a92bbe7c50bfa4421d8781bfd0f377b4562fc71a4ab3ec72c427a08b2f6c56
time="2024-10-17T07:53:18Z" level=debug msg="Processed staking event" event=UNBONDING_TX_SIGNATURES_CONFIRMED_ON_BABYLON eventId=35a92bbe7c50bfa4421d8781bfd0f377b4562fc71a4ab3ec72c427a08b2f6c56

Fails to be signed by BTC node due to mempool error (appears 5 times, one time per minute)

time="2024-10-17T07:54:18Z" level=error msg="failed to send staking transaction to btc chain to activate verified delegation" err="-26: txn-mempool-conflict" stakingTxHash=35a92bbe7c50bfa4421d8781bfd0f377b4562fc71a4ab3ec72c427a08b2f6c56

Finally, this log now appears every 1 min:

time="2024-10-17T07:59:18Z" level=debug msg="cannot sign staking transction with configured wallet" stakingTxHash=35a92bbe7c50bfa4421d8781bfd0f377b4562fc71a4ab3ec72c427a08b2f6c56

I suggested whether this could be related to selecting an already-used UTXO and could be resolved by marking a UTXO as unspendable before starting to consruct the staking tx.

[filippos47]

This is due to multiple BTC staker daemons using the same BTC wallet.
We've discussed offline that btc-staker doesn't support this atm, and each staker requires its own wallet.
We should document this in the upcoming BTC staker doc.