Leap protocol

Inspiration

The Leap protocol is built with the support of Skip and Eisen protocols to enable seamless cross-chain trading within the Cosmos ecosystem. We saw the potential of IBC and EVM compatibility and aimed to bridge these worlds for DeFi users.

What it does

Leap is a revolutionary protocol that enables both IBC-based- and EVM-based swaps, allowing users to trade assets across different networks effortlessly. It offers IBC integration, EVM compatibility with Cosmos-friendly wallets ( like Keplr )

How we built it

We built on the ibc-dot-fun repository and integrated Eisen API for swaps. By using evmos proto, we applied a Ethereum transaction type to evmos js. By using evmos js and Keplr wallet signEthereum methods, we could make signed Msg.EthereumTx.

Challenges we ran into

There were few docs to study signing EVM transactions using Keplr wallets and evmos js didn't fully support the transaction type for executing. It was hard to get EVM-based configurations like nonce, v, r, s, gasPrice, etc.

Accomplishments that we're proud of

We gained valuable insights into interoperability with the mechanisms of ethermint and how to make signs using different wallets.

What we learned

We gained valuable insights into interoperability with the mechanisms of ethermint and how to make signs using different wallets. We could fully understand how the cosmos and evm chains work differently. The biggest challenge was to invoke MsgEthereumTx in evmos, which had many undocumented changes on their side. We struggled signing the ethereum transaction from cosmos compatible wallet, and luckily we found a undocumented signEthereum() api call in keplr wallet. The next challenge was to correctly compose a protobuf, where we discovered from the hints that we had to include "/ethermint.evm.v1.ExtensionOptionsEthereumTx" to the TxBody. We would like to suggest evmos to upload their reference implementation on working with their ethermint x/evm module. Most of their dapps are using native ethereum rpc calls, and in order to expand their target customers to the developers in cosmos ecosystem, we need more support from their side. It was a great opportunity to learn what cosmos actually is and what it can do, however we also felt that the diversity of appchains incurred too much fragmentation protocols. The ecosystem largely depends on how diligently the team is working on integration libraries, and we see it as a legit concern to the ecosystem. I hope the cosmos ecosystem collaborates much more together to develop one common goal as a team.

What's next for Leap protocol

Leap's future includes enhancing features, by expanding its ecosystem, deeper DeFi integration in EVM-compatible chains, and providing the combinations of functions like ibc-transfer, ERC20 token swaps, and Native tokens swaps.

Built With

• eisen
• evmosjs
• go
• keplr
• next
• skip
• typescript