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.
Nomad is a strong supporter of the Evmos community by bringing projects and market makers to Evmos to kickstart the ecosystem as well as joining every community call we’ve had since our public announcement last month answering the community’s questions: evmos.blog/bridging-asset…
In order to support Nomad and Connext, we have helped facilitate introductions to projects deploying on Evmos. After all, in order to reduce fragmentation for users, users need to rely on being able to use their version of a bridged asset such as $USDC on any app of their choice.
As such, we wanted to be transparent with the community and share the following message that the team has sent to other projects as our goal is to create the best UX possible for our users:
“We would like to introduce you to Nomad who we believe will be the dominant EVM bridge on Evmos. While there will be other bridges in the future, Nomad and Connext offer an optimal balance between security and UX as well as bring value in other ways to the network.
Of course, Evmos is a permissionless network allowing users and devs to choose their bridge provider on Evmos based on their differentiators: security, speed, fragmentation, etc.
With that said, the team is focussed on simplifying bridging UX by closely collaborating with Nomad and Connext at launch to reduce fragmentation”.
As the entire @cosmos ecosystem works through different solutions to reduce fragmentation, we hope our proposal resonates with the need to balance fragmentation reduction during the early days of Evmos while still promoting an open and transparent ecosystem.
Please let us know your thoughts and feedback. We are excited for the upcoming launch of Evmos and this is part of our goal of bringing the best user experience possible to Evmos.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
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_