Hi Hans yes to transfer from base aepp address you copy that address to the ledger stick it is same address but after confirming the address was the same on the ledger stick this is when they never showed up. They were transferred to those other addresses which I have no idea where they came from as I only copied the base aepp address an confirmed this was the same address for the ledger.
I’ve not used the base aepp much, and I have not connected it with a Ledger stick so I don’t know anything there, sorry. I’ve been involved in the AE node and protocol, so the transactions I can see and understand but the tools I know less about!
@nikitafuchs.chain do you have any insight in base aepp connected to Ledger?
No unfortunately, but I have seen two people getting their funds stolen from their Ledger with my own eyes two (!) times already, their shabby behaviour is absolutely not surprising here.
@RANDALL given that I fully understand the chain of events you portrayed, it is important to note: If you use a Ledger device for transaction signing, the base aepp cannot redirect your transfers somewhere else than you confirmed to wish to transfer it. The private key needed for signing the transaction is inside the Ledger in that case.
1 Like
I have a problem with the migration.
Error “Something went wrong”
From MEW:
0x932Cf9910672B8a26BD31141Ff8f11e9b7dfa6e2
To my AE address: ak_2kUmKqtvRcYaaRBgnsKf9jcVNei4SSz88iV7LXsuCsheTJW7gz
I need help please!
Thank you.
nobody had time yet to check if the migration app still works after the Iris hardfork. the thing is that the backend of the migration app is currently using an old outdated version of the Go SDK and there might be an update required.
what I can tell you is => you will be able to migrate and you will get help!
somebody will get back to you soon!
1 Like
@JR10 can you check if it works with æternity Token Migration ? @VitalJeevanjot is hosting this service and fixed the app independently back then. but that was also pre-Iris hardfork
1 Like
I hope so. Thank you.
I tried. It’s the same thing, it doesn’t work.
I tried with an Aeternity address from Airgap Vault, also with an address from an Exchange. It didn’t work for me in any way. I tried
Please don’t use an exchange address for migration! This might result in a permanent loss if the exchange is not willing to recover this manually!!!
What AE address did you try to use for migration to the exchange?
1 Like
@marco.chain @JR10 @yassun
There is currently some issue coming with migrations from both astor.network and official website.
However from astor.network, The error logs I can recover looks like.
[ERROR] EncodeCalldata! json: cannot unmarshal array into Go value of type models.Error
From these
2021-07-07 06:03:06.19 UTCaeternity-migration-ui-85f445cd77-brkxddev2021/07/07 06:03:06 IP: 10.8.6.152, Route: /migrate
2021-07-07 06:03:06.41 UTCaeternity-migration-ui-85f445cd77-brkxddev2021/07/07 06:03:06 [ERROR] EncodeCalldata! json: cannot unmarshal array into Go value of type models.Error
2021-07-07 06:08:22.76 UTCaeternity-migration-ui-85f445cd77-brkxddev2021/07/07 06:08:22 IP: 10.8.11.153, Route: /migrate
2021-07-07 06:08:23.43 UTCaeternity-migration-ui-85f445cd77-brkxddev2021/07/07 06:08:23 [ERROR] EncodeCalldata! json: cannot unmarshal array into Go value of type models.Error
2021-07-07 06:08:47.69 UTCaeternity-migration-ui-85f445cd77-brkxddev2021/07/07 06:08:47 IP: 10.8.11.153, Route: /migrate
2021-07-07 06:08:47.89 UTCaeternity-migration-ui-85f445cd77-brkxddev2021/07/07 06:08:47 [ERROR] EncodeCalldata! json: cannot unmarshal array into Go value of type models.Error
2021-07-07 06:18:26.81 UTCaeternity-migration-ui-85f445cd77-brkxddev2021/07/07 06:18:26 IP: 10.8.6.152, Route: /info/0xee300431c25447134633cc5d94b93555b92f7952
2021-07-07 06:19:40.57 UTCaeternity-migration-ui-85f445cd77-brkxddev2021/07/07 06:19:40 IP: 10.8.6.152, Route: /migrate
2021-07-07 06:19:41.14 UTCaeternity-migration-ui-85f445cd77-brkxddev2021/07/07 06:19:41 [ERROR] EncodeCalldata! json: cannot unmarshal array into Go value of type models.Error
2021-07-07 06:22:09.76 UTCaeternity-migration-ui-85f445cd77-brkxddev2021/07/07 06:22:09 IP: 10.8.6.152, Route: /migrate
2021-07-07 06:22:10.39 UTCaeternity-migration-ui-85f445cd77-brkxddev2021/07/07 06:22:10 [ERROR] EncodeCalldata! json: cannot unmarshal array into Go value of type models.Error
1 Like
This is the address of the exchange: ak_BX9SkXMRiatBNb4ENB6AxTpFaMse8EzEFRZLrTunHZSJRH22j
And… what does it mean?
Don’t know sorry, I didn’t coded the backend.
so the good news is that neither the exchange account nor the other account you used has a token balance. this means the migration really failed.
I say this is good news because IF the migration had been successful with the exchange address you might have bigger problems with recovery than you have now 
=> never again try to migrate to an exchange address please!!! everybody!
I will try to get an answer here as soon as possible. there might be a problem that the backend is trying to compile a contract that is outdated to generate calldata for the contract call.
it might take some days but you will get help! enjoy your weekend
1 Like
I understand. Thanks for your time! I hope I can fix it. 
1 Like
@JR10 giving you a small update here. so recently there were some Iris related updates for the compiler which means that the old contract source code cannot be compiled with the latest version of the compiler anymore. this is not a big issue but it just needs to be fixed either for the contract or in the configuration of the backend. see feature: iris compatibilit, fixing & cleanup of tests by marc0olo · Pull Request #1 · aeternity/aepp-token-migration-smart-contract · GitHub for more information about that.
to check the status of your migration you can use this endpoint:
unfortunately I am not 100% sure if this endpoint always delivers accurate data because if there is a problem in the backend it might be the case that the ethereum address isn’t marked as migrated (though the migration could be successful)
you can also take the contract code of the migration contract directly and check if the migration has been performed already. this information will always be correct!
the contract is deployed at ct_eJhrbPPS4V97VLKEVbSCJFpdA4uyXiZujQyLqMFoYV88TzDe6 and the sourcecode can be found here: aepp-token-migration-smart-contract/TokenMigration.aes at master · aeternity/aepp-token-migration-smart-contract · GitHub
you can perform a dry-run for a call of is_migrated by providing your ethereum address in upper-case (!) as follows: 0X932CF9910672B8A26BD31141FF8F11E9B7DFA6E2
Edit
Checking your AE balance is probably the easiest way to see if a migration was successful:
2 Likes
Hi marco.chain. I just tried and it’s the same thing. I tried twice.
Sorry, I don’t know how to do what you mentioned in the previous message about perform a dry-run.
2 Likes