Hey Everyone, we really appreciate your patience as we work diligently to fix the existing issues with the airdrop claim for ledger + @keplrwallet users. It is not our intention to exclude these users and here's a quick 🧵 on what happened and how we are bringing you a solution👇
First: The Problem
While most all cosmos chains have historically used the same Cosmos key type, Evmos uses the Ethereum key type to stay compatible with the ETH tooling that you know and love (MetaMask, Remix IDE, Truffle, Hardhat, etc.)
This results in a different address being generated than would be generated had Evmos used the Cosmos key type.
Notice how the string <prefix1>dtwarh8... is the same for both Cosmos Hub and Osmosis addresses, but NOT for Evmos? This is the result of using different key types.
The reason this affects Keplr users is because Keplr defaults to using the Cosmos app which uses the Cosmos key type, and therefore generates the wrong address.
This results in users funds appearing to be "stuck" as well as users incorrectly showing no eligible RektDrop balance.
Now: The Solution
First off, all funds are SAFE! No users funds will be permanently affected by this error.
We do however need to create a way for users to access their funds using the original Cosmos keys.
The best part is that a solution is underway to allow users to send funds from the Cosmos-generated address to the Ethereum-generated address and you can track the progress here: github.com/tharsis/evmos/…
We realize we need to do a better job of communicating these issues and we are sorry for the frustration this has caused many of you.
We will be slow to respond to individual questions as we focus on building this solution but will update you on further developments.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Rektdroppers, devs are working through several issues
👉 Keplr has a problem making transactions
👉 Keplr has issues generating ledger addresses, DO NOT SEND FUNDS TO LEDGER ADDRESSES ON KEPLR
👉 MetaMask freezes intermittently
👉 MetaMask doesn't let users make EVM transactions
All of the above issues are known and are being addressed by the team. The devs are doing something as we speak!
Claims are indeed operational, but a lot of things have been breaking in the background.
As we said, Osmosis and Cosmos Hub users rely on IBC to claim so gotrekt.com will have support for this to do it safely
But, if you're following these guides that involve IBC, please keep the following in mind:
Earlier this year we announced that we are working closely with @nomadxyz_ and @ConnextNetwork to bridge Ethereum assets to Evmos. We have been in talks with other bridges for the past couple months and wanted to share more about how we are working closely with Nomad 🧵
First, our goal like many other chains is to reduce fragmentation of assets to avoid scenarios like @sunnya97 pointed out:
We are excited about the value that Nomad and Connext bring because they are focused on security before revenue and their solution offers a seamless user experience to go along with it. We hope to abstract the bridge away from users so they can just focus on their dApp of choice.
1/ Hello Evmosians, it is with a heavy heart that we announce that we will need an additional couple of days to guarantee a smooth launch for the network.
As such, we have made the difficult decision to delay launch until Wednesday, 6 pm UTC / 10 am PST.
2/ We know many of you have come together in the last few days to rally around the #Evmos launch and we appreciate your enthusiasm and dedication to the shared success of the network. By holding off for an extra few days, we will be able to ensure the best experience possible.
3/ For those of you who have been with us since the beginning, you’ll know that the launch of the #Ethermint project has been a long-anticipated event, and a milestone in the Cosmos timeline. We aim to deliver on the original promise of #Ethermint and much more.
1. We made a mistake here since this is the only validator option we've introduced on the blog.
We have corrected the language as it came off as an endorsement for a specific validator and that was not our intention.
The devs will not endorse a specific validator over others.
2. A lot of people in the comments have been throwing shade at the use of dedicated node providers and have been suggesting that we commit resources to @akashnet_