-
Notifications
You must be signed in to change notification settings - Fork 94
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
Disappearing funds from xbridge(reward for fixing in BTC - more details on discord) #603
Comments
reproduce hint stepscompile blocknet wallet with debug symbols
download litecoin wallet
download dogecoin wallet
update blocknet config ~/.blocknet/blocknet.conf with
update litecoin config ~/.litecoin/litecoin.conf with
update dogecoin config ~/.dogecoin/dogecoin.conf with
update xbridge configuration ~/.blocknet/xbridge.conf with
setup dxmakerbot for more easy to reproduce bug
to check if bug occurred you need to compare values
When bug hit and there are no orders are created, |
Encountered this while testing SYS v4.3. Got inaccessible UTXOS for TBLOCK:
|
And comparing |
Most easy way explained, wallets has UTXO funds sitting on addresses, but Xbridge itself who is the only responsible for reserving/releasing UTXOs for orders, thinks some/all UTXOs are reserved but is not able to say what order UTXOs reserved for.
Bug impact/what is causing:
(like which coins ? Is is only DOGE ? Are you creating exact or partial orders? etc. - anything you think might help)
summary:
ideally also provide the xbridge log from a day when it occurred
What behavior did you expect?
How reliably can you reproduce the issue, what are the steps to do so?
What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)?
What type of machine are you observing the error on (OS/CPU and disk type)?
Any extra information that might be useful in the debugging process.
maybe also some debug in case when order is accepted... maybe we hit some corner case .... order been accepted but error happen and i missed that error in logs so some specific debug for this would be also good.
The text was updated successfully, but these errors were encountered: