IOTA manual claims tracker (UNOFFICIAL)

[degraff]

when we can get those coins?

[1714176096]

1714176096

[1714176096]

1714176096

[nexter]

First, logged into the client with new seed and tried the reclaim tool. After 6 hours I decided to try the process without logging in.

It's been sending all night, likely 12 hours. I don't think it's working.

Any other approaches to try?

This is a David Manual Claim, perhaps it doesn't apply?

I would try with a different host node (supposing you are in light mode).

I just tried several and the client has a new twist. Seconds after the reclaim process starts the entire screen goes black and the cpu indicator vanishes.

[redecision]

I just tried several and the client has a new twist. Seconds after the reclaim process starts the entire screen goes black and the cpu indicator vanishes.

A few weeks ago, I was unable to attach an address to the tangle. I have tried on another computer (Windows10 instead of Windows 8.1) and it worked. Perhaps you could try on another machine.

[shazam12]

My addresses are all in Group 2, and derives from the same seed.

I have used reclaimed tool and got "Invalid Old Seed" (it was short, and has now invalid characters such us 1,2,3... for example).

Then I've tried again converting my original "now invalid format" Old Seed to a "compatible format" Old Seed: changing any digit diferent from 9 to 9, lowercase to uppcase, and filling with 9's at the end in otder to get a 81 characters long seed.

It has given me a transaction tag and a "proof of transaction confirmed message"

Now enter to my IotaWallet and have 0 iotas. And when looking for the transaction hash on https://iotasear.ch I find it, but the amount on that transaction is 0.

Is there any problem?. Did I something wrong?.

Thanks  in advance.

[ozboom]

Is there any problem?. Did I something wrong?.

Hi Shazam, this is just the first stage of the automatic reclaiming process (linking your old key to a new key). The actual fund transfer will happen next week with wallet v2.5.3. Dom's post says:

In this version [wallet v2.5.2], the user will be publishing a proof of ownership of their seed to the Tangle. After successfully completing the reclaim process (once your transaction gets confirmed), make sure to keep your old and new seed safe, as you will need it for stage 2 which will go live next week with the new wallet release.

https://blog.iota.org/gui-v2-5-2-latest-release-with-iota-reclaim-tool-32d364d6241a

Dom also says this on the Github release page:

v2.5.2: IOTA Recovery Tool
@domschiener released this 3 days ago · 3 commits to master since this release

This release brings with it the recovery tool needed for people that have missed out on the previous transition phase, or users that were vulnerable due to continuous key re-use, to reclaim their tokens. This is a two stage claim phase, whereby in the first phase you submit the proof to the Tangle, and in the second one the address to which the tokens will be automatically sent to. This release is currently being scheduled for next week.

https://github.com/iotaledger/wallet/releases

[nexter]

I just tried several and the client has a new twist. Seconds after the reclaim process starts the entire screen goes black and the cpu indicator vanishes.

A few weeks ago, I was unable to attach an address to the tangle. I have tried on another computer (Windows10 instead of Windows 8.1) and it worked. Perhaps you could try on another machine.

Great suggestion! Worked on my Win7 box in less than a minute to get proof transaction confirmation!

[k_day]

Can someone confirm that converting your lower case seed (from unclaimed round 1) to uppercase is the right thing to do when doing step 1 of the claiming process? The transaction confirms, I just want to be sure that this will work when it comes time to do part 2.

[ozboom]

Can someone confirm that converting your lower case seed (from unclaimed round 1) to uppercase is the right thing to do when doing step 1 of the claiming process? The transaction confirms, I just want to be sure that this will work when it comes time to do part 2.

Good question K, I seem to remember this was standard procedure back in 2016...

[ozboom]

My machines run Linux, trying to build a .deb package but not so easy, hopefully a .deb version of wallet v2.5.2 will be released today (?)
Hesitating to borrow a Win machine to do the reclaiming...

have you now made a working .deb?
thx

Hi ewibit, 'just saw your question, sorry for the late reaction... And nope, I ran into problems when building the v2.5.2 .deb package and was feeling too much in a hurry for securing phase 1 to delay this any longer, 'did the first stage on my brother's Win10 machine  

'Just installed the v2.5.3 .deb package, 'went straightforward, it looks exactly like v2.5.2 to me, and there is no mention of a second (reveal) phase.
I ran the Reclaim Tool again in v2.5.3 with my old seed + a new seed I just made up, and it got confirmed. 'Pity that an old seed can be linked to several new seeds, even if only the first match should prevail. So we don't really know if our seed has been claimed by someone else previously...

[websioux]

I did the same but in reverse order

I first used v2.5.3 since 2.5.2 .deb was missing (it stil is). With old seed conversion to uppercase (necessary since lower case not accepted by client). It worked well.

Then scared a bit because of the pre-release terminology, failed to compile 2.5.2.deb, then found a windows10, installed 2.5.2.exe - reduced minWeightMagnitude from 18 to 14 and it woked well too.

Now I believe I have two proofs. This is no proof of who owns what, it is only you who can prove that you waved hand on 2.5.2 Step 1

For autorecovery, I guess it can not be 100% safe if the tool knows nothing about the email your originally send to David. But if it can send an email to the same email address you previously used, for mailbox owner to confirm the iota destination, it should be fine.

But this is not of my business as I'm in #round1 waiting for KYC (part of protocol there was to remind the email address).

[superresistant]

 
I found a bug in the recovery tool.
4 days ago I did successfully publish and confirm the proof but today it wasn't confirmed on the tangle.
So I tried again with the same old seed/new seed and this time, the transaction was made and confirmed to an address that isn't on the new seed. I did it a second time and an other transaction was made and confirmed to this unknown address a second time.
I am checking my seed and I cannot find that address.

[Come-from-Beyond]

I found a bug in the recovery tool.
4 days ago I did successfully publish and confirm the proof but today it wasn't confirmed on the tangle.
So I tried again with the same old seed/new seed and this time, the transaction was made and confirmed to an address that isn't on the new seed. I did it a second time and an other transaction was made and confirmed to this unknown address a second time.
I am checking my seed and I cannot find that address.

The devs said that address shouldn't belong to your seed.

[cascrypto]

back from vakation, what version do i need to run to start the claiming , list 2
2.5.3 or 2.5.2 ?

[ewibit]

Hi ewibit, 'just saw your question, sorry for the late reaction... And nope, I ran into problems when building the v2.5.2 .deb package and was feeling too much in a hurry for securing phase 1 to delay this any longer, 'did the first stage on my brother's Win10 machine  

'Just installed the v2.5.3 .deb package, 'went straightforward, it looks exactly like v2.5.2 to me, and there is no mention of a second (reveal) phase.
I ran the Reclaim Tool again in v2.5.3 with my old seed + a new seed I just made up, and it got confirmed. 'Pity that an old seed can be linked to several new seeds, even if only the first match should prevail. So we don't really know if our seed has been claimed by someone else previously...

because of no v2.5.2 .deb I tried on another Win7 PC

after ~24 hours nothing happened
and
I closed the program



 

[JamieLeblond]

So does it matter if you used the recovery tool in 2.5.2 or 2.5.3? Or it's all the same?

[ozboom]

the transaction was made and confirmed to an address that isn't on the new seed.

Hi Superresistant, I understand this is not a claim address but just a confirmation hash of the transaction that linked the old & new seeds. Now you have two hashes for two different transactions (same seeds but at different times). Only the first confirmed transaction will be useful for phase 2.

So that is all perfectly OK imho.

[ozboom]

after ~24 hours nothing happened
and
I closed the program
 

Cheers Ewibit, I would say just try again with v2.5.3. If it takes too long to confirm, try again with another node. You must get your old seed linked to your new seed with a confirmed transaction in order to finalize the claim.

[superresistant]

I found a bug in the recovery tool.
...

The devs said that address shouldn't belong to your seed.

the transaction was made and confirmed to an address that isn't on the new seed.

Hi Superresistant, I understand this is not a claim address but just a confirmation hash of the transaction that linked the old & new seeds. Now you have two hashes for two different transactions (same seeds but at different times). Only the first confirmed transaction will be useful for phase 2.
So that is all perfectly OK imho.

Alright then.

[websioux]

because of no v2.5.2 .deb I tried on another Win7 PC

after ~24 hours nothing happened
and
I closed the program

https://i.imgur.com/RLMq50e.png

 

I had the same, read above, .exe comes with minWeightMagnitue=18, I changed it to 14, then it was a lot faster.

[ozboom]

So does it matter if you used the recovery tool in 2.5.2 or 2.5.3? Or it's all the same?

Hi Jamie, my guess is that you can do phase#1 claiming with both versions indifferently (2.5.2 & 2.5.3). I got a recovery transaction confirmed in both versions (same old seed, different new seeds) and didn't notice any obvious difference. Cheers.