The coins were not returned after the transaction was cancelled.
1 Like
I did it, nothing changed
2 Likes
how come peeps keep getting flagged?
Discourse automatic spam detection sees patterns associated to spammers and flags the post.
I removed the flag.
1 Like
You can check a block explorer to see if your transaction got posted on chain before you canceled it. Just put in the kernel of the transaction I think. https://explorer.grinminer.net/
There also the “restore” option. Button just below the repair wallet button.
2 Likes
Link to the solution of a Gate user who had the same problem:
1 Like
I have done restore, but it’s not helping. And explorer can’t fine the kernel
085ce11945d82e05c5dfef1f7c75293f8f6de57a734246c5467d425e6d6a53e0f4
1 Like
Umm well if it’s not on block explorer I think it means it should still be in your wallet, is your node fully synced? Make sure you have your recovery phrase written down accurately before doing the final option which would be to delete the wallet and restore it via the recovery phrase.
but let’s see if anyone smarter can help you hear before you resort to that, I’m basically a newb so hopefully someone with brains can lead you in the right direction
1 Like
To my knowledge there are two scenarios in which your wallet would not see your coins returned after a cancel.
Scenario 1 Running two instances of the same wallet (same recovery phrase):
-
Wallet instance A creates a transaction (kernel A). Wallet B creates another transaction using the same output as wallet A but it will have a different kernel (kernel B).
-
If the transaction from wallet B gets published on the chain and you would go to wallet A, it will not know the output is already spend by wallet instance B. Neither can you find it on the chain by searching for kernel A since the transaction that happened has kernel B.
Cancelling the transaction will not return your funds since the output was already spend. Restoring your wallet or running repair in wallet A will not show the funds nor the transaction. Only wallet B will know the funds were spend and will know if the transaction.
Why can wallet A not see the transaction you might ask? Because of cut-through all spend outputs are forgotten by your node and will not be scanned. Grin is unique in its great scaling by forgetting spend outputs but it does mean the history of transactions your wallet has performed cannot be restored by scanning the blockchain. Similarly, payment proofs are only locally stored in your wallet, not on-chain. Making a regular backup and only running one wallet instances is advisable for Grin.
Scenario 2 Unsafely cancelling a transaction:
If you receive an invoice and would sign it and send the signed slate (kernel A) to the receiver and you would cancel the transaction (unsafe cancel since there is no self spend of the outputs). The receiver has your partial signature an can still finish the transaction after you would have cancelled. In this scenario you would be able to find the transaction using kernel A.
But wait, what if your node would not be synced and you would make another transaction using the same output (kernel B) before the receiver broadcasts the transaction. In this case you would probably try to search for the transaction using kernel B. You would not be able to find it because the previous transaction with kernel A is the one that is on-chain.
3 Likes
Those kinds of issue when cancelling transaction reminds me that never cancel transaction 
If not sure, send 0.1 grin to the target wallet first.
Anyways, try to clean the wallet files then restore from seed to see? or the bug can be somewhere else.
1 Like
I really had 2 wallets. 1 on my PC and 2 grim android. I never think that if I send coins from 1 of them it’s not synchronized
2 Likes
Ok that explains it then, means one of your other wallets sent the coins and should have the tx kernel. So even though you hit cancel on one wallet, the other wallet still sent the coins.
Wow gotta hand it to @Anynomous! He nailed this one. 
Like he said: “only running one wallet instances is advisable for Grin.”
Hello, no I’m still trying. I installed new wallet on my pc. Restored with seed phrase. But nothing changed. My 9000 coins disappeared. I contacted support gate.io , but they can’t help me, because the kernel not found grinexplorer.net. Grim wallet support band me. I really don’t know what to do.
I’ve seen others who’s had funds disappear when sending to gate .io. If you don’t mind me asking, why did you cancel the transaction?
I’m surprised the coins didn’t show up in your gate io wallet. Do your other wallet instances have the tx kernel for the send transaction?
I sent to gate several times, but this time it stop and asked me to confirm the transaction, so I cancelled. There is no tx on second wallet, and during that transaction it wasn’t working, because node wasn’t synchronized.
1 Like
Maybe if you sync and then repair the second wallet instance it will show up now that it’s synced? I hope someone smarter can help you I’m just giving me two cents. i wonder why gateio asked you to “confirm it” maybe you still need to confirm it so it’s held by gate io but not in your gateio wallet.
1 Like
Gate accepts deposits via listener, not slatepack, which begs the question how can you cancel a transaction sent in this way? I can understand cancelling a slatepack before finalization, but cancelling a txn which has already propagated through the network seems like it should be impossible.
And this thing where scammers are DM’ing users with fake support channels etc is outta control. Mods here should maybe change rules so that users must reach some minimum trust level before they can send DM’s at all.
2 Likes
