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

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

Unable to send Miota to my bitfinix account #619

Open zinnyko opened 6 years ago

zinnyko commented 6 years ago

I have been trying since yesterday but i am unable to send my miota to my bitfinix account, plz hep Here the hash for the transaction: https://iotasear.ch/address/NMBAZXHAFRQXUZNRPNLSLWRBZEYECNDNUJY9QIBC9FVJYRFBWWLY9C9IVDPFIRHKTHZYWASXTZSAKZAVDPASLJOLKC

i reattached multiple times as i thought that it is the only way but even thats not working.

mnori commented 6 years ago

I'm having the same problem. Yesterday I made a test transaction to a different wallet. I reattached multiple times but the thing is still stuck on pending. Also thanks to my test transaction, it's impossible to make any more transactions until the original one confirms. Maybe there's some issue with the network?

Doesn't inspire much confidence anyway. I'll probably be dumping most of my coins as soon as I can get them out of the wallet.

My theory about the massive price increase? People are unable to dump their coins because they are trapped in the wallet. This inbalance is greatly skewing the market and very likely to end in tears.

1ddV commented 6 years ago

Similar issue: I get a "Request error' when attempting to send to my Bitfinex account. I'm running Iota light wallet 2.5.4 on Win 10. Tried with different nodes.

Questions: 1) do I really need to attach the receiving address to tangle even if I'm sending? I tried with different nodes, but always get "Request Error" 2) Shoul I try any particular node (I tried a few from iota.dance/nodes). 3) could this be a general issue with the tangle?

Thank you for any help!

1ddV commented 6 years ago

I was eventually able to attach the receiving address to tangle using node02.iotatoken.nl:14265 with CCurl Implementation.

But sending iota to Bitfinex still fails with "Request error". What is wrong with this thing???

tozo07 commented 6 years ago

I have same problem. I tried many times:

mnori commented 6 years ago

My transaction eventually confirmed after around 20 hours of waiting. It clearly takes way too long though, compared to older coins like Bitcoin, Litecoin and Doge. Maybe it will be quicker once the network grows in size?

prodigydefender commented 6 years ago

I tested sending 1 Miota to Bitfinex, got a confirmation screen on my IOTA wallet, but it hasn't gotten to my Bitfinex wallet yet, and it has been almost 48 hrs.

prodigydefender commented 6 years ago

Additional comment on sending Miota to Bitfinex is that you have to edit node config to iota.bitfinex.com:80

tozo07 commented 6 years ago

I have a 6 day old Pending. https://iotasear.ch/address/VLLOKT9WGIMNMIUPMFQ9KXZ9CDSSNUP9TVODKJPVAF9HGZFMGVWHDMJNEBFKNTHXJUYXUYGIZPZCGQPOXKIZBUYVHY

Kshysiek commented 6 years ago

The same problem here. Reattaching does not help.

gitdisrupt commented 6 years ago

Any luck here? I believe my account was HACKED in an attempt to send a small amount to bitfinex. INCREDIBLY upset.

1ddV commented 6 years ago

No news on my side. Still getting "Request Error" when attempting to send few IOTAs to bitfinex. The transaction is not even being sent in my case as I don't see it in my wallet's history. Tried also to uninstall/reinstall the wallet. I think today I'll generate a new wallet and try to send something to it, just to make sure the issue is not related to the bitfinex addreess.

1ddV commented 6 years ago

Just an update on the "Request Error" when attempting to send IOTA: I was eventually able to perform the transaction installing the wallet on a different PC. Still don't know why it doesn't work on mine.

Anyway I'm good now, just waiting for the transaction to be confirmed (it has been pending for 2 hours now!).

gitdisrupt commented 6 years ago

I am in the same situation ... i THINK my account is OK, but i wont know till all the TXs have confirmed ... i have been waiting 6+ hours now.

kons233 commented 6 years ago

same problem with the pending, hey @mnori how many times did you reatach and rebroadcast? how often and how far apart in time till you got it to work? since I see others are waiting days and you say 20 hours you must have done something right

mnori commented 6 years ago

@kons233 I was only sending to a test wallet, not Bitfinex. I attached in the evening and then clicked it a few times in the morning the following day, both from the wallet that was sending the coins

I've recently sent a test transaction to Bitfinex and this one's taking longer. I'm also unable to connect to the Bitfinex node, every time I try to log in with it selected, it stalls for a few minutes and then says "connection refused"

mnori commented 6 years ago

Update: My test transaction to Bitfinex is now confirmed, according to the wallet. But it's not showing up in Bitfinex.

1ddV commented 6 years ago

@mnori: same for me. I've finally been able to confirm the transaction by reattaching it but it doesn't show up in Bitfinex.

mnori commented 6 years ago

@CryptoIOTA My confirmed IOTA transaction is still invisible on Bitfinex.

Interestingly though, I just made another test transaction to Binance and it was confirmed and visible in my account panel after a mere 1 hour. Something wrong on Bitfinex's end perhaps?

EDIT: ... AND I just send a much bigger transaction to Binance. Confirmed in an astonishing 10 minutes! I did mash the reattach button a bit.

kons233 commented 6 years ago

@mnori how many times would you say you mashed the reattach button, cuz I sent to binance as well about 18 hours ago, and again 9 hours ago everything is still pending, and ive reatached a couple times too but maybe not enough? idk. Also it wouldnt send at all until i switched to regular curl, and also im on a lite node. are you using lite or full? also are you willing to tell me what a bigger transaction is? i have been sending 5, 4, 3, 2 iota at a time i wonder if the bigger the faster?

mnori commented 6 years ago

@kons233 Here's some params you might find useful

I hit reattach 4 times in the first 5 minutes Host: node01.iotatoken.nl (I also tried the other numbers in the series) Light wallet Using CCurl My test transactions were between 1-4 Mi

Good luck!

kons233 commented 6 years ago

Thanks @mnori Just did exactly that hopefully it gets trough!

prodigydefender commented 6 years ago

sent IOTA to bitfinex, been 3 days, still haven't received

On Thu, Dec 7, 2017 at 10:08 AM, kons233 notifications@github.com wrote:

Thanks @mnori https://github.com/mnori Just did exactly that hopefully it gets trough!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/iotaledger/wallet/issues/619#issuecomment-349805536, or mute the thread https://github.com/notifications/unsubscribe-auth/AcIrqlSW86jo8O7D3TXt3glFPMlRytJyks5s9x6AgaJpZM4Q2BnO .

1ddV commented 6 years ago

Today transaction got confirmed within 10/15 minutes and I saw my iotas in Bitfinex after 3 hours. Also I had to disable my windows firewall to fix all the issue I was experiencing the previous day. Not 100% sure this was the root cause though.

prodigydefender commented 6 years ago

had to disable my windows firewall - wouldn't that leave you with vulnerability on cyber security?

On Thu, Dec 7, 2017 at 11:47 PM, CryptoIOTA notifications@github.com wrote:

Today transaction got confirmed within 10/15 minutes and I saw my iotas in Bitfinex after 3 hours. Also I had to disable my windows firewall to fix all the issue I was experiencing the previous day. Not 100% sure this was the root cause though.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/iotaledger/wallet/issues/619#issuecomment-349957247, or mute the thread https://github.com/notifications/unsubscribe-auth/AcIrqg53zPFQXAGwRG65XhLP02VV1O9jks5s995ZgaJpZM4Q2BnO .

1ddV commented 6 years ago

Yes, I was vulnerable for 15 mins, but it's really unlikely to have someone expliting any open port on that short timeframe. That said, my seed is anyway encrypted in a password manager installed on a USB key.

Next time I'll try to keep the firewall on as I'm not 100% sure it was the root cause of the issue I had the previous day.