Hi all, I habe big problem.
I have done succesfully Migration from EVM to Fuel in October
EVM ID: 0x173547b2dD66880854101B28F474E05ccAed98Fa
ETH-Wallet ID: 0x8d29a9040Bf7505F00C1745aB3b521c9EF3a9563DC34644a3C841A660B471bEC
a)I could succcesfully claim my Drop (on same wallet-ID´s)
What is the issues.
I am going to Phase 2 Points | Fuel Points Program and see following message and I see system is connecting from ETH-WALLET-ID:
This is new ETH-Wallet ID: 0xF26F2f40cBc6DD8bE0DC97418d0CbCBde94B6932Ae3c20dE3623FB8E912c53D6, which system is showing and it has nothing to do with my migration/claim.
If I go with this EVM-Wallet-ID and this wrong ETH-Wallet-ID under my account to see my drop + my Asset, logically I see nothing becuase of wrong assignemnt between EVM and ETH-Wallet .
So my migration was done correctly, my claim was succesful on same migration andres!
Please help me to get my Asset back. Thank you
guys be careful, scam link!
Hey @cryptoBender, it looks like you had created your account 0x8d29a9040Bf7505F00C1745aB3b521c9EF3a9563DC34644a3C841A660B471bEC using the evm connectors Fuel Ignition is Live!. I would suggest you connect using the evm wallet address and see if its the same address.
ALso, 0xF26F2f40cBc6DD8bE0DC97418d0CbCBde94B6932Ae3c20dE3623FB8E912c53D6 is certainly not an EVM-generated address, and is an account generated using native Fuel wallets.
1 Like
Hi, I am just connecting my Rabby. Than 2nd request is coming and I am asked to connect my non-native (ETH) Wallet, which I am ding.
Claim Site/Migration site, is checking correctly the connection. If it comes to this link Fuel Ecosystem, wehre I would like t osee my asset/drop via “my account”, tha I a mgettign this wrong Non-EVM Wallet, assigned to my Rabby.
If the case is so easy, can we have quick call via Discord? I would like please to have my money back. I have checked the issue with all moderators in discord no one can help me till today!
thank you
I also tried to connect EVM, if I go t oFuel Wallet. but it is the same issue. My Asset is not visible!
I will take this to the team and will get back to you. Meanwhile, could you please confirm that you didn’t connect to any other evm address?
1 Like
confirming! thank you and I am waiting!
Hello. Any updates from the team please?
Hey @Igorek_Gent, i have updated the team, will keep you posted
Ok, because meanwhile I have the issue with 2 more wallets. waiting for your update!
1 Like
Hey @Igorek_Gent
I’ve reviewed your transactions, and here’s what I found:
1. Oct 19, 2024 (10:00:23 AM UTC)
2. Oct 19, 2024 (10:05:59 AM UTC)
From your screenshots, I can confirm you’re currently connected to the second EVM account (0x173547b2dD66880854101B28F474E05ccAed98Fa).
The Issue:
The predicate address you’re referring to (0x8d29…471bEC) is linked to the first EVM account (0x83221250EcC3d56c1961eFbb17637758b3C41639).
However, the EVM account you’re connected to right now (0x173547b2…E05ccAed98Fa) has no connection to this predicate.
How to Fix:
To proceed, you’ll need to switch to the correct EVM account (0x83221250…C3C41639) — the one associated with the predicate.
Let me know if you have any other questions!
Hi, i just checked.
Important, I don´t have any issues with: 0x83221250EcC3d56c…1639
I have problem with 
0x173547b2d…E05ccAed98Fa
The logic sounds fantastic, but it is exactly the problem, looks like for 2 different EVM-Wallets, same fuel-predicate was generated and migration was done with 2 assets, from 2 different evm-wallets to the same fuel predicate, but only 1st one recognizes it i nthe system:
I just switched to the (0x83221250…C3C41639 ) and again under “my account” I don´t see my asset, I don´ see my drop but I see same wrond predicate.
Thanks for the clarification, @Igorek_Gent.
Let me address your concern step-by-step:
Key Facts
- An EVM address cannot generate the same predicate address as another EVM address. That’s technically impossible.
- However, multiple EVM addresses can migrate assets to the same predicate address, which is what happened here.
- Both of your migrations (from different EVM wallets) migrated pre-deposited assets into the same predicate address (0x8d29…471bEC) – see below screenshots for confirmation.
Event Logs
1. Migrated Oct 19, 2024 (10:00:23 AM UTC) See EventLog here
Search for 8d29a9040bf7505f00c1745ab3b521c9ef3a9563dc34644a3c841a660b471bec on decoded data to confirm the recipient.
And then your predicate received on Fuel Network: 0x106459672201ad69e442f29c4f46fc6aa1d20b7103466c08c926d6ae874ed256
2. Migrated Oct 19, 2024 (10:05:59 AM UTC) See EventLog here
Search for 8d29a9040bf7505f00c1745ab3b521c9ef3a9563dc34644a3c841a660b471bec on decoded data to confirm the recipient.
And then your predicate received on Fuel Network: 0xbc942a82ddd87fb5fe78806b008f91d7114f9600eeacc831962423d89fc11d9c
3. Airdrop Claimed Dec 19, 2024
Fuel Transaction Hash: 0x64172a295a4385a26ec6a5f6dbe9801b3153b0bec3fde808dea8d21c437e5e31
2,997.645232343 FUEL
Your airdrop claim transaction accounted for both migrations into this predicate.
4. Last transactions
2,997.645232343 FUEL has been sent to 0x0a1a...8167 in transaction 0x48a...a500.093760389 pzETH has been sent to 0xf47F...9D67 in transaction 0xcf4d...d490.249017452 rstETH has been sent to 0xf47F...9D67 in transaction 0x997...f47
Note that 0x0a1ad9d4a8fcf606f455ce7dc0c4eb82a7fd049208855ebbffce8bebc6ad8167 is a Fuel Native Account.
Note that 0xf47f6e49d1a3f1615c4272dfe80c20e8f4db1c3ee1950181223b59c5d6fc9d67 is a predicate associated with the EVM address 0x3a01f32fd0fb01023e1c442a2a127aa5a3d60ff2.
At the time I wrote this comment, all assets are on those accounts mentioned right above – because they have been sent a few days ago.
I hope this breakdown clears up the situation and provides the clarity you need regarding the migrations and your airdrop.
I’m here to help troubleshoot further if needed.
TL;DR
Your migrated assets and airdrop are accounted for and currently are in the following accounts:
-
2,997.645232343 FUEL — Sent to Fuel Native Account: 0x0a1a…8167
-
0.093760389 pzETH — Sent to Predicate Address: 0xf47F…9D67
-
0.249017452 rstETH — Sent to Same Above Predicate Address
Both accounts are linked to your migrations. Use the provided links to double-check balances and transaction histories.
To access 0xf47F…9D67 funds, you’ll need to connect with this EVM address: 0x3a01f32fd0fb01023e1c442a2a127aa5a3d60ff2
