-
Notifications
You must be signed in to change notification settings - Fork 87
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
state : Cancel timelock is expired #709
Comments
ERROR The cancel transaction cannot be published yet, because the timelock has not expired. Please try again later |
2021-08-30 21:13:41 INFO Received new confirmation for Monero lock tx txid= seen_confirmations=7 needed_confirmations=10 Caused by: |
Hi I am having the same issue. Transaction was working properly and failed. Error: Failed to broadcast Bitcoin cancel transaction ae3a078c9a626a3299d641fd98148a8ac07d0c6ba321ddea8b2b2e28942b49db Caused by: Says I can't cancel because timelock hasn't expired? I can't resume the swap either. my swap history shows |
Check this out : You can refund between 72 and 128 of your first bitcoin transaction @fbion @kirtspaulding |
Yep great, I need to wakeup at in the middle of the night to ensure I don't lose my money. |
Not necessarily, a 72 confirmation is about ~12hours. |
swaptool> ./swap.exe resume --swap-id 4a6bbdec-341b-4d18-bfef-b460a3050717 Error: Failed to broadcast Bitcoin cancel transaction ae3a078c9a626a3299d641fd98148a8ac07d0c6ba321ddea8b2b2e28942b49db Caused by: Other details that may be relevant:
|
Maybe it is related to this ? |
@devbordecraft this is a great comment. I can't say if it's the right answer, but if clicking the session or clicking away causes issues... should be high priority for devs to investigate. |
Afaik this is a bug (or a feature ?) related to windows PowerShell, not the tool. PowerShell suspend any process in the console when the user select or highlight something in it |
We think we have the error causing this and have a fix coming shortly #705 |
./swap --debug cancel --swap-id ** ./swap --debug refund --swap-id ** |
I guess we can remove the loss-of-funds tag now. It's not a powershell issue. I've experienced the same exact problem on both Windows and Ubuntu. |
Our intention was for the swap cli to wait until block 72 and do this for you but it is broken due a bug (which should be fixed with #705). Then you should be able to resume a swap (using cli args) and it should handle swap execution for you. Manual cancel/refund is a temp fix until #705 is merged. |
Just tried this morning, cancel failed without force tag, but worked after force applied. Refund success. ./swap.exe cancel --swap-id 4a6bbdec-341b-4d18-bfef-b460a3050717 ./swap.exe cancel --force --swap-id 4a6bbdec-341b-4d18-bfef-b460a3050717 ./swap.exe refund --swap-id 4a6bbdec-341b-4d18-bfef-b460a3050717 |
Error: Failed to broadcast Bitcoin cancel transaction
Caused by:
Electrum(Protocol(String("sendrawtransaction RPC error: {"code":-26,"message":"non-BIP68-final"}")))
The text was updated successfully, but these errors were encountered: