iotaledger / legacy-wallet-use-trinity-wallet-instead

IOTA Wallet
GNU General Public License v3.0
2.07k stars 414 forks source link

Not enough balance .- Tag/Nonce switched in transaction?, lock funds. #321

Open ghost opened 6 years ago

ghost commented 6 years ago

Good morning I have been looking a little more of the reason why I can not send a token to another account and that it seems that the tag field or nonce is bad, I leave the url: https://iotasear.ch/hash/LQ9DYCFQIJ9ACXE9YYTBCMIURZJKPVEZGHJKRNAZWSGAFAYLHSKRLHHF9AKMMOPMCADDF9TQAQIK99999

the fields are switch, where the field noce is the tag value and in tag there is nothing

It seems that this does not validate the transaction and that pending forever, as it is required that the accounts are validated, I will never be able to send my funds, showing the exception that I leave below(Error: Not enough balance), can you help me? this happened with the version change to 2.5.0

This issue has relation with #320 Good night I write to you because there is an error in code that causes that you can not send funds even after having them.

The precondition is: per seed there must be more than one account and at least one of them with balance 0 and one of them or more with balance o pending transaction.- I tried to rebroadcast and nothing happened.

Captured images https://ibb.co/ext2G5 https://ibb.co/bVesYk

master branch version 2.5.0 in wallet-master\ui\js\ui.transfers.js in function getUnspentInputs that is a recursive method, call iota.api.getInputs(seed, {start: start, threshold: threshold}, (err, res) => {...} line 267 When try counts balance per transaction generate this stacktrace:

This error possibly because there is a pending transaction. This pending transaction originated from the account attachment to the tangle by the migration 2.5.0. The address has 6 transactions, the first is pending and the rest confirmed.

Error: Not enough balance at iota.js:955 at makeRequest.prepareResult (iota.js:4877) at exports.XMLHttpRequest.request.onreadystatechange (iota.js:4749) at exports.XMLHttpRequest.dispatchEvent (iota.js:25648) at setState (iota.js:25667) at exports.IncomingMessage. (iota.js:25504) at exports.IncomingMessage.EventEmitter.emit (iota.js:19660) at endReadableNT (iota.js:22150) at afterTickTwo (iota.js:20063) at Item.run (iota.js:20235)

Thank you so much for your time.

ghost commented 6 years ago

Good afternoon, after several attempts and tests, I finally managed to unblock my account and recover my funds. I feel the noise made. Thank you very much.

chrisdukakis commented 6 years ago

Hey, thanks for posting! Actually problem is that the wrong error is triggered. It should display a key reuse error and not a insufficient balance error. But what's more important, is that your report brought up issue of sending to an input address. This should be prevented. Will push fixes soon. Thanks! ;)

marialuisadk commented 6 years ago

Thanks Wonky for transferring me over!

I am having the same issue as bartolosimpson above however, I have NO clue how to fix it. I need to transfer my funds out ASAP so it would be great if I could get my wallet to cooperate and release my IOTA hostages! :) Thanks for help!

marialuisadk commented 6 years ago

Just incase anyone else with the same problem is looking at this thread, I thought I would update on the problem resolution-Finally!

After many attempts yesterday of resending and hanging on "pending", I let it all sit overnight.

This morning I tried to reattach, it did it first time unlike yesterday and the day before where there were lots of fails etc.

I checked the address on the tangle search and there ware a confirm, then two and finally 3 confirms (but my balance was still in my account-weird). A few minutes after, balance was gone and a few mins after that it was back again (more weird) in my wallet. It had been doing that all morning, one minute showing full balance then a few mins later balance after withdraw.

After a very tense hour, the transfer has shown in my the other wallet (YAY!!) and so far Light wallet seems to have settled on the correct balance-Nope wrong its still fluctuating between balance before transfer and after transfer. This is after two restarts of wallet.