MyHush / hush

Hush is a fork of Zcash focused on secure communications
https://myhush.org
Other
67 stars 37 forks source link

reverse a payment sent to No Outputs after mined blocks #126

Closed EvilRedHorse closed 6 years ago

EvilRedHorse commented 6 years ago

When I say wallet I am talking hushd

Describe the issue

I mined two blocks (a z-nomp based pool): Block# 305226 & 305446 they were gone a day later, sent to No Outputs on transaction# e8436cf63cbb6a1805456d692cd122ec245db86ccb2ae70f447bd5731d7f2137 I am trying to get the blocks back in the wallet and cannot find documentation.

steps

mine block to t-address keep wallet synced

Expected behaviour

money was to stay in wallet

Actual behaviour + errors

Crashed hours after 2 mined blocks which were over 100 confirmations. After hushd was synced money was there. Later it had been sent to No Outputs

The version of Hush you were using:

Hush Daemon version v1.0.13-e44f3022

Machine specs:

Any extra information that might be useful in the debugging process.

the wallet.dat and blockchain info are stored on a RAID5 BTRFS Array.

Do you have a back up of ~/.hush directory and/or take a VM snapshot?

'~/.hush' only contains my hush.conf file

leto commented 6 years ago

@EvilRedHorse "No Outputs" should really say "No public outputs" at

https://explorer.myhush.org/tx/e8436cf63cbb6a1805456d692cd122ec245db86ccb2ae70f447bd5731d7f2137

That means your funds were send to a zaddr.

Can you show us a screenshot of your transaction history? Are you using the SWING wallet? Please include version numbers, if so.

EvilRedHorse commented 6 years ago

Yes, I did eventually see the blocks received but that was after 24h with hushd synced. I am not using a swing wallet, I prefer hush-cli which I can wrap a simple GUI around, this problem could be moved to Z-NOMP git since the hush-coin-mining-payout was a shielded transaction by default causing a synced wallet to have a zero balance for 24h+ until the transaction completed. Thank you very much for your help.