Transaction awaiting finalization

Tech Support
#1

Hi,

I tried to sent some Grin from Tradeogre to my local wallet:

~: grin-wallet receive
Please paste your encoded slatepack message:
BEGINSLATEPACK [...] ENDSLATEPACK
zsh: killed     grin-wallet receive

So grin-wallet got killed after I pasted the encoded slatepack message and hit enter.

Now when I type “grin-wallet info”, I see that the amount of Grin attempted to send are now “Awaiting Finalization”. Is there a way to finalize the transaction? I tried “grin-wallet finalize”, which also asks me for the encoded slatepack message, but when I paste it and hit enter, I get:

Wallet command failed: LibWallet Error: Wallet store error: DB Not Found Error: Slate id: [ ... ]
#2

I’ve never used tradeogre, but since everyone uses SRS, then if you’re withdrawing you’re not the one who should finalize the transaction. I’m guessing tradeogre asks you for amount you want to withdraw, then it gives you slatepack which you pasted to the grin-wallet receive and then it crashed. If you don’t use -m flag when doing the receive part, then it will first try to communicate through tor (so it will generate new slatepack and try to send it over tor to tradeogre, if it doesn’t go through then it should give you a slatepack as an output of the receive command). I don’t know why your receive command failed, but if you have this transaction listed under grin-wallet txs then you can get its Shared Transaction Id (lets call it txid). To cancel this transaction you can run grin-wallet cancel -t <txid> (without <> ofc). However i’m not sure what happens if you try to use the receive command with the same slatepack, maybe it will tell you that it’s already canceled

#3

Is your crash reproducible?
Does your grin-wallet.log (probably residing in ~/.grin/main/ ) show anything of interest?

#4

Thank you! Cancelling the transaction and receiving again with the same slatepack worked for me. This time I passed the “–manual” option to the receive command.

1 Like
#5

Is your crash reproducible?

I couldn’t reproduce it. After successfully finishing the original transaction using the “–manual” switch, I did another test transaction the same way as the failed one, and this time it worked.

Does your grin-wallet.log (probably residing in ~/.grin/main/ ) show anything of interest?

I don’t think so. This is the log of the failed command:

20210522 13:55:17.142 INFO grin_util::logger - log4rs is initialized, file level: Info, stdout level: Warn, min. level: Info
20210522 13:55:17.142 INFO grin_wallet - Using wallet configuration file at /home/jan/.grin/main/grin-wallet.toml
20210522 13:55:17.142 INFO grin_wallet - This is Grin Wallet version 5.0.3 (git v5.0.3), built for x86_64-unknown-linux-gnu by rustc 1.49.0 (e1884a8e3 2020-12-29).
20210522 13:56:24.936 WARN grin_wallet_api::owner - Attempting to send transaction via TOR
20210522 13:56:24.936 INFO grin_wallet_impls::adapters::http - Starting TOR Process for send at Some(127.0.0.1:59050)

And this is the log of the successful command (for the test transaction trying to reproduce the crash):

20210522 18:14:52.135 INFO grin_util::logger - log4rs is initialized, file level: Info, stdout level: Warn, min. level: Info
20210522 18:14:52.135 INFO grin_wallet - Using wallet configuration file at /home/jan/.grin/main/grin-wallet.toml
20210522 18:14:52.135 INFO grin_wallet - This is Grin Wallet version 5.0.3 (git v5.0.3), built for x86_64-unknown-linux-gnu by rustc 1.49.0 (e1884a8e3 2020-12-29).
20210522 18:14:54.916 WARN grin_wallet_api::owner - Attempting to send transaction via TOR
20210522 18:14:54.916 INFO grin_wallet_impls::adapters::http - Starting TOR Process for send at Some(127.0.0.1:59050)
20210522 18:15:22.632 WARN grin_wallet_api::owner - Unable to send transaction via TOR
1 Like
#6

So it looks like it crashed somewhere between “Starting TOR” and “Unable to send transaction”.