Tweet

Evmos

Mar 4 • 6 tweets • 2 min read

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:

its EXTREMELY important that the tokens from the IBC transfer are received in
- an evmos address that uses the ethereum keys (as opposed to cosmos)
- the user MUST be the owner of the recipient address

Failure to do this correctly could result in sending funds to the wrong place

We'll be publishing our own guide to help enable people claim through the alternative routes because we understand that some people really want access to their rektdrop sooner than later

@Disperze_

We're very thankful that tools like evmos.disperze.network enable Keplr users to sign payloads and MetaMask users to make Cosmos transactions. Thank you @Disperze_!

Once they have EIP712 support MetaMask should not show warnings while signing.

• • •

Missing some Tweet in this thread? You can try to force a refresh

This Thread may be Removed Anytime!

Twitter may remove this content at anytime! Save it as PDF for later use!

More from @EvmosOrg

Evmos

@EvmosOrg

Mar 5

@keplrwallet

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.

Read 7 tweets

Evmos

@EvmosOrg

Feb 28

@nomadxyz_

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 🧵

@sunnya97

First, our goal like many other chains is to reduce fragmentation of assets to avoid scenarios like @sunnya97 pointed out:

https://twitter.com/sunnya97/status/1487325691544625153?s=20&t=JyLFZHzwnHYv68_qT6Bv2w

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.

Read 11 tweets

Evmos

@EvmosOrg

Feb 28

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.

Read 6 tweets

Evmos

@EvmosOrg

Feb 4

https://twitter.com/EvmosOrg/status/1489282541836124163

Frens, this announcement got some critical feedback, and it is good feedback:

1. We shouldn't endorse a validator for delegation
2. We should be pushing for more decentralized node and validator operations in general

We're making it right, here's how:

https://twitter.com/EvmosOrg/status/1489282541836124163

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.

@akashnet_

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_

We hear you, and we'll follow through on that.

We want to give options, and here's why:

Read 6 tweets

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Share this page!

Evmos

People who liked this thread also liked...

Try unrolling a thread yourself!

More from @EvmosOrg

Evmos

Evmos

Evmos

Evmos

Did Thread Reader help you today?

Don't want to be a Premium member but still want to support us?

Like this author's thread?