Whelo79 wrote: » Axion are almost half way to replenishing the stolen liquidity pool through OTC vesting sales in just 2 days.https://etherscan.io/tokenholdings?a=0xe8B283B606A212d82036F74f88177375125440F6 I have to say the majority of the community involved in this project are absolutely fantastic. It will be 50/50 what way this goes next week and in the short term future. If they can fend off any potential immediate dumps on launch the road will look promising. There seems to be large commitments to hold with many more who can not take part in the OTC sales committing to either buying or adding to the liquidity pool. I believe they are setting the price on launch at .0003 (previous ATH was .00051). The market will dictate where we go from there.
Pdoghue wrote: » I seem to have lost the HEX2T I had. Nothing when I checked etherscan. I had carried out the swap. Had it in my metamask wallet.
Whelo79 wrote: » If you carried out the swap it would have been AXN now, not HEX2T. It's useless anyway, the new token will be airdropped by Wednesday.
Pdoghue wrote: » Yea, I seem to have the AXN now. I did carry out the swap so that would make sense, but I thought I would also retain my HEX2T.
Dohnjoe wrote: » I still have the original Hex2T (I didn't try to swap it) on Metamask. I presume I can claim the new token using the original Hex2T, correct? thanks
Tango One wrote: » If I read that correct I need to swap again?.
Whelo79 wrote: » The contract to add to your wallet for the airdropped tokens is: 0xdc05a13f89006d8a5bac0810b6f735699b010f92 You might not be able to see them in Metamask yet due to the Ethereum outage but you can see them on your etherscan address. Mine arrived about 7 hours ago.
Pdoghue wrote: » Yep, I see them on my Etherscan, but can't add them to my Metamask wallet for the reasons given.
Tango One wrote: » It appears Hex3t is being traded when I look at dextool I can see the trading pair on uniswap any ideas not intending to sell just curious more so
The attack utilized code that was deliberately injected prior to the protocol’s deployment. This incident bears no relation to the audits conducted by CertiK and the party responsible for the attack was a person that seemed to be involved with the deployment of the Axion Network contracts. As an additional degree of security, audit reports should standardise to include deployed smart contract addresses whose source code has been verified to be the same as the one that was audited.