0

Didn't comprehend what a headache MetaMask (android) was going to be. Long story short, gave up trying to stake HEX tokens from my mobile device. I went to my laptop and discovered the android/chrome wallets had no linkage, and I would need to transfer from android to chrome.

On android, my eth to hex conversion was confusing, because the tokens would not show in MetaMask wallet until I finally discovered the wallet had to be associated/linked to the HEX contract; 0x2b591e99afE9f32eAA6214f7B7629768c40Eeb39. Once I (accidently?) accomplished this breakthrough, my tokens where available to transfer to my chrome MetaMask wallet. Several attempts were unsuccessful, returning invalid key string message. I check several times, I was entering the same address I had successfully transferred some eth to earlier. So my confused solution (oops), was to use the HEX contract address to transfer my HEX tokens to; 0x2b591e99afE9f32eAA6214f7B7629768c40Eeb39.

Here is the transaction hash, 0xb3a31cebcecdebab8d521ab38bca3f93e3595615903da16d72573c17b9e72295 so I have plenty of info to prove where the tokens came from, and where they went. Here is a pdf copy of transaction details. https://documentcloud.adobe.com/link/review?uri=urn:aaid:scds:US:83596197-96d1-457c-90e2-d2a69c409dba

I've read that these tokens may or may not be recoverable, depending on the structure of the token contract. Who do I contact, or how can I determine, if I can be reunited with these little asterisks?

(all I wanted to do was experience my 1st airdrop, and ohh what a strange journey it's been)

1
  • Did you contact the hex team? They are the only ones that can help you. – Ismael Apr 22 at 1:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.