-
Notifications
You must be signed in to change notification settings - Fork 413
iota did not arrive in wallet, transaction confirmed, address not attached to tangle #843
Comments
HELLO Same problem for me. Transaction with bitifinex confirmed wallet still empty. Try to find solution |
@fredercik32 , please try not to spam and correct your post with more details e.g. did you attach the address with the tangle? Your Transaction Hash? It will confuse the devs when every post is full of trash. This could be just a bug which the team of the wallet can fix - or a incorrect use ourselves of the wallet. We will see :) |
Hello,
Really thank you to answering me....i'm a little bit tired of the situation. Ok please take not that i m french and my english is not perfect...
No ididn't attach the adress with tje tangle ( work for new adress ) because see on tuto that is not necessary ( maybe a mistake !!)
the hash transaction is YLQ999RZFQSHKIQLXAT9TMOJSMVDNZSQRAXLCOQCWSICKJWIJJIBCAFOCWBVTKT9ZECRXZEDYSVAA9999
tk you for helping me !!!
This is the Withdrawal from bitifinex
Le Vendredi 22 décembre 2017 9h32, Mario Deubler <notifications@github.com> a écrit :
@fredercik32 , please try not to spam and correct your post with more details e.g. did you attach the address with the tangle? Your Transaction Hash? - this could be just a bug which the team of the wallet can fix - or a incorrect use ourselves of the wallet. We will see :)—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Ok thanks @fredercik32 . It seems that we both have the same problem. If i understand it right, than attaching a address to the tangle means also attaching the address to the index of your wallet. So if you now sending IOTA to your wallet - your wallet is only searching for new Hashes for the addresses attached in your index. This would mean, our iota is not lost - it is just not visible in the wallet. A possible solution could be to generate new addresses by clicking --> Receive --> Generate Address --> Attach to Tangle. Repeat that process till the address is generated, which you used to send it to your wallet. Then the Iotas should appear. I am on address 90 at the moment, still not there. @chrisdukakis @wonkytonky are my thoughts to this issue right? Is it possible to manually attach the address to the wallet? |
OK, I understand what you say....but it's impossible to reattach the adress which was used to this first transaction in my wallet ( can't forced it manually )....when i generatingnew adress it's never the same. Don't you think ?
Le Vendredi 22 décembre 2017 12h03, Mario Deubler <notifications@github.com> a écrit :
Ok thanks. It seems that we both have the same problem. If i understand it right, than attaching a address to the tangle means also attaching the address to the index of your wallet. So if you now sending IOTA to your wallet - your wallet is only searching for new Hashes for the addresses attached in your index. This would mean, our iota is not lost - it is just not visible in the wallet. A possible solution could be to generate new addresses by clicking --> Receive --> Generate Address --> Attach to Tangle. Repeat that process till the address is generated, which you used to send it to your wallet. Then the Iotas should appear. I am on address 90 at the moment, still not there. @chrisdukakis are my thoughts to this issue right?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Yes, that could be a hard part - i do not now exactly how to the addresses are generated from the api yet.The wallet source code there is calling the iota.api as far as i can see (makes sense ;)) But there seems to be an API Endpoint to attach addresses to the tangle.
https://iota.readme.io/v1.2.0/reference#gettransactionstoapprove I will try that after lunch with my local node, and keep you updated @fredercik32 . |
HO men....i'm not able to use code source by myself ...my knowledge about this is really little !!!
Le Vendredi 22 décembre 2017 12h32, Mario Deubler <notifications@github.com> a écrit :
Yes, that could be a hard part - i do not now exactly how to the addresses are generated from the api yet.The wallet source code there is calling the iota.api as far as i can see (makes sense ;)) But there seems to be an API Endpoint to attach addresses to the tangle.curl http://localhost:14265 \ -X POST \ -H 'Content-Type: application/json' \ -H 'X-IOTA-API-Version: 1' \ -d '{"command": "attachToTangle", "trunkTransaction": "JVMTDGDPDFYHMZPMWEKKANBQSLSDTIIHAYQUMZOKHXXXGJHJDQPOMDOMNRDKYCZRUFZROZDADTHZC9999", "branchTransaction": "P9KFSJVGSPLXAEBJSHWFZLGP9GGJTIO9YITDEHATDTGAFLPLBZ9FOFWWTKMAZXZHFGQHUOXLXUALY9999", "minWeightMagnitude": 18, "trytes": ["TRYTVALUEHERE"]}'https://iota.readme.io/v1.2.0/reference#gettransactionstoapproveI will try that after lunch with my local node, and keep you updated @fredercik32 .—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@fredercik32 , i setup the code with your hashdata and requested the trytes for it. Sadly i was running into another error - i posted it as issue on the reference implementation repo: IRI Repo: 433 |
i´ve got the same problem since 2 weeks. |
I ask myself....
If i send from my wallet some iota using this adres which pose problem ( if it spossible ) do you think it could beresolve the situation ?
Le Vendredi 22 décembre 2017 14h44, fips1988 <notifications@github.com> a écrit :
i´ve got the same problem since 2 weeks.
Also didn´t attach the address to the tangle, used the address for transfering the iota from bitfinex to my wallet.
The transfer is confirmed in the tangle, but still missing the Iota in my wallet.
I created about 60 new addresses since that, but this address doesn´t appear in my wallet.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
ok update: I got the api calls prepared but the attachToTange Api call seems to work only on on private full nodes and is disabled on the public ones. I will now start to setup my own full node, @fips1988 if you send me your transaction hash, i will attach yours also than @fredercik32 ´s . The only problem i have is that i do not have neigbours yet. can someone invite me to the slack channel? |
ok and tk you for help....y re super nice !!
this is my transaction hash
YLQ999RZFQSHKIQLXAT9TMOJSMVDNZSQRAXLCOQCWSICKJWIJJIBCAFOCWBVTKT9ZECRXZEDYSVAA9999
Le Vendredi 22 décembre 2017 15h33, Mario Deubler <notifications@github.com> a écrit :
ok update: I got the api calls prepared but the attachToTange Api call seems to work only on on private full nodes and is disabled on the public ones. I will now start to setup my own full node, @fips1988 if you send me your transaction hash, i will attach yours also than @fredercik32 ´s . The only problem i have is that i do not have neigbours yet. can someone invite me to the slack channel?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
my transaction hash is |
We are a little bit totaly alone with this problem...IS THERE ANYBODY WHO IS DIRECTLY IMPLICATED WITH IOTA TECHNOLOGIE WHO CAN HELP US ????? We are talking about lost money....it's not a little thing and i give us not good proof off the fiability of the iota...
Le Vendredi 22 décembre 2017 16h21, fips1988 <notifications@github.com> a écrit :
my transaction hash is
WYNDJMOTDYSITZOZHXAWZMZUOFGJZPX99KHPAYQVTYBETMFVIXAQHZVWCUPHWSOQLYKUVREV9EXU99999—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Ho mario...i'm not said this for you. But you're just a iota customer...not directly implicated in iota developement, no ?
Le Vendredi 22 décembre 2017 9h32, Mario Deubler <notifications@github.com> a écrit :
@fredercik32 , please try not to spam and correct your post with more details e.g. did you attach the address with the tangle? Your Transaction Hash? - this could be just a bug which the team of the wallet can fix - or a incorrect use ourselves of the wallet. We will see :)—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@fredercik32 - you have invested in high risk technology on the bleeding edge, its not like opening a depot and trading gold options. Also this wallet is open source and has 450+ open issues, so chill out and do not spam ;) - i checked your hashes, if you did not generate the address in the wrong seed, we will be able to add the address to your wallet index :). I am just a developer, did not work with the iota api before. |
Ok mario....sorry don't want be annoying.Y're probably right maybe i'm not enough easy with this technology....but here i mand try to find solution. Tk for your help one more time.
Le Vendredi 22 décembre 2017 16h59, Mario Deubler <notifications@github.com> a écrit :
@fredercik32 - you have invested in high risk technology on the bleeding edge, its not like opening a depot and trading gold options. Also this wallet is open source and has 450+ open issues, so chill out and do not spam ;) - i checked your hashes, if you did not send it to the wrong seed, we will be able to add the address to your wallet index :). I am just a developer, did not work with the iota api before.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@mario589736 i have the same problem |
Same here, IOTAs sent from binance.com, confirmed there, but my wallet is empty. |
If the transaction is confirmed in the explorer and not showing in the wallet you are probably using an out of sync node. Make sure the two sync numbers are the same. Using a synced node will allow you to see your balance. |
They're the same. Transaction is confirmed: |
I have the same problem. I'm a newbie and I did not provide the "proof of work" prior to using the address. I sent IOTA from Binance to my wallet, confirmed the email, but the IOTA did not arrive. It has been over a week and I don't know how to get it back. Is it completely lost or can I get this back out of the tangle. Any help is appreciated. |
Hi!
Do you have the traction hex or any other info?
…On Jan 3, 2018 5:54 PM, "alyons824" ***@***.***> wrote:
I have the same problem. I'm a newbie and I did not provide the "proof of
work" prior to using the address. I sent IOTA from Binance to my wallet,
confirmed the email, but the IOTA did not arrive. It has been over a week
and I don't know how to get it back. Is it completely lost or can I get
this back out of the tangle. Any help is appreciated.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#843 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AbaF5JYf2-wT3-wXmKfNLKn86dc0sIQUks5tHC9HgaJpZM4RKYPk>
.
|
Yes, I have the transaction id, I'm guessing that is what you mean by the hex. I have screen shots from the tangle and from my Binance account too. |
OK. Have you tried promoting the transaction from you iota wallet?
…On Jan 3, 2018 7:07 PM, "alyons824" ***@***.***> wrote:
Yes, I have the transaction id, I'm guessing that is what you mean by the
hex. I have screen shots from the tangle and from my Binance account too.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#843 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AbaF5HyqwCutH7hb7Az-ED8nmAz8N_pyks5tHEB2gaJpZM4RKYPk>
.
|
I’m not certain of the term “promoting”. I have tried additional addresses. Rebroadcasting and reattaching these addresses. I have tried the Reclaim Tool twice. Unfortunately, the address I used for the transfer is not in my History for me to rebroadcast or to reattach. I did not press the “Attach to Tangle” button before I did the transfer. |
Attach to tangle now then.
…On Jan 4, 2018 7:47 AM, "alyons824" ***@***.***> wrote:
I’m not certain of the term “promoting”. I have tried additional
addresses. Rebroadcasting and reattaching these addresses. I have tried the
Reclaim Tool twice. Unfortunately, the address I used for the transfer is
not in my History for me to rebroadcast or to reattach. I did not press the
“Attach to Tangle” button before I did the transfer.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#843 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AbaF5LFtFjD-H0mrnhGbdA2uVHUDEMnEks5tHPKggaJpZM4RKYPk>
.
|
I don't know how. I cannot input the address in my "receive" address? The transaction and the address are in the tangle but not attached to my wallet. I would love it if someone could tell me how to correct this! Otherwise, I'm lost. |
@alyons824 & @Guar1 - i gave up attaching my transaction to the tangle. when i understood it right, it does not matter if you attach it, as long it is the receiver address. every address gets automatically attached when a transaction is on its way. correct me if i am wrong. I am at a point now where i think that:
|
Mario and Alfons,
You have your private key yes? 81 characters.
Log into your iota wallet with this and ss TX history. Don't send your
Private seed, but that goes without saying.
…On Jan 4, 2018 1:02 PM, "Mario Deubler" ***@***.***> wrote:
@alyons824 <https://github.com/alyons824> & @Guar1
<https://github.com/guar1> - i gave up attaching my transaction to the
tangle. when i understand right it does not matter if you attach it, as
long it is the receiver address. every address gets automatically attached
when a transaction is on its way. correct me if i am wrong.
I am at a point now where i think that:
1.
There was a wired address in my clipboard when i pasted the address -
so the iotas are in the wrong seed (i tried every thing which could have
been in my clipboard - no chance)
2.
Something really strange happened there which nobody understands
yet....
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#843 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AbaF5A5c3xRov_MxHpVxyaxKEtO-qhubks5tHTxggaJpZM4RKYPk>
.
|
thanks @Guar1 - yes 81 chars. |
Hi, it looks like I have the same problem, still unsolved afetr 2 weeks. I am sure that I tipped the correct seed the first time and later (same check sum), so the address with 100 MIOTAs belongs to the seed I am actually using. Many thanks in advance for your help. |
This appears to be the same wallet "bug" that I ran into Dec. 22 with ver. 2.5.5 and 2.5.6 wallets. I generated my "Send to" address, but did not attach it to the Tangle. I entered it in the Binance GUI and submitted the withdrawal. That was during a window of time when Binance was processing IOTA withdrawals (not always the case). The transfer was completed and after an hour or so it was marked confirmed in the Binance history. However the 99.5 IOTA never reached my wallet balance or history. Three Other transfers from my old paper wallet worked fine and made it to the balance and history. The missing transaction appears on the Tangle, marked confirmed , but the address used is not in the wallet address list. I know it's the correct address because I cut and pasted it into an intermediate spreadsheet, which I keep, and from there to Binance. Here is the transaction Id: AJUMCAHBEYRKXDXMJUO9PEKKSPWUUPODLKMIEQQNSC99NCUJSLUKPPZ9ECEBV9YOCJQCO9DZHYQLA9999 |
It looks like I have the same problem. Yesterday evening I tranfrerred a reasonable amount of IOTA to my wallet, the transaction is confirmed, but there is still no currency on my IOTA wallet. Neither there is anyting in the History of the wallet. In addition its not possible to attach to tangle. I hope we will be noticed and there is a way to save the lost money. This is extremely frustrating. |
Did yesterday's snapshot solve your problem ? In my case, unfortunately not : I cannot get my very first reception address generated again... And I am sure that I am using the same and right seed, I'm really getting mad. XAAOJNXFQFEQZTW9E9LGHTCEDQIPWZOHI9REEGYLBZPAGLIITAZLSNQWTNNVANDTWPUBOYYJCEFWJZDEDEWVOKIWZW Any idea why I cannot get it into my wallet ? Many thx in advance for your help |
ok i setup a small test repo to attach the address to the tangle (sendTransaction(address, 0) api call (with the help of thedewpoint/iota-basic). my transactions are not confirmed yet: https://iotasear.ch/address/SAZCSWSCRYJBQTPRPNJUGZOKQZ9PHNNECFMPMODILWMKXFILLDFMDMTJHVZYLVPEGHVGKVXZFGEBSFMHCMZNMQFGQX, if it works i will setup a tutorial how to do it. |
Mario it's been 7 days; did your test work? I count 10 persons with this problem on this thread alone and others on different threads describing the same problem. Instead of hacking some kind of solution, we need to keep this alive, front and center find the correct person who can take the problem to the official IOTA development team for a problem resolution in a future release. How to do that from Github? |
I'm having the same problem. Here is what has happened to this point:
here is the address: Can someone please help me recover my funds? |
@mb-deihl , no sadly not. my transactions are not getting confirmed. i will still play arround with it, but you are completely right. so many people seem to have this problem, probably we should retry to get some help from a iota dev. i send out some emails, but did not get a reply yet. |
can anybody help me? I have 3Gi in pending transaction ... And it does not appear in the wallet or the hash ... Someone could help me by favorrrr I'm desperate to pay the loan kkkk (laughs of nervous kk)... Adress: OLQEIRKRTPJQRHVANRUZGHVSKFYKMCNHAUBSJDQLNBZHLBUJTJJDKQMTHYTRYRYGZLJOO99MTOWXTLAY9 I managed to make a withdrawal of less than 902 Miotas, to 3 months but the 3Gi never arrived ... |
I have two seeds set up and wanted to transfer 99.5 Miotas from one to the other. After creating the transaction, it was pending for about 3 hours and i published it to the network 3 more times. Now one is confirmed, the other 2 are "Persistenz: A reattachment confirmed". No Miota arrived in my other wallet. I did not attach the address to the tangle.
Any idea whats happening there? Could it be possible that the receiving wallet does not see the transaction, because it is not attached to the tangle?
The text was updated successfully, but these errors were encountered: