This is a cross-chain messaging demo between Cosmos and Ethereum using IBC and LCP (Light Client Proxy).
High verification (or gas) costs on Ethereum make it challenging to implement IBC. For example, light client verification for Tendermint Consensus requires over 10 million gas costs on Ethereum1.
Datachain has developed LCP (Light Client Proxy), a middleware embedded with TEE, to overcome this challenge. LCP can solve the gas cost problem while minimizing the trust assumption, by replacing light client verification in cryptographically secure areas on memory.
To enable IBC on Ethereum using LCP, we primarily need the following modules:
- ELC, a light client implemented within the LCP enclave, for Ethereum and Tendermint
- ibc-solidity, IBC implementation in Solidity
- yui-relayer, a relayer that supports EVMs
- LCP Clients for Ethereum and Tendermint, clients to verify proofs submitted from the LCP node.
We have implemented the modules mentioned above and have built a demo, as described below.
The packet relaying flow from one of the Cosmos appchains to Ethereum proceeds as follows:
- The Cosmos appchain submits a packet, and the relayer queries it.
- The relayer sends it to the LCP node.
- The LCP node verifies the packet and creates a proof using the key generated in the enclave.
- The relayer submits the packet, along with the proof, to the LCP client on Ethereum.
- The LCP client on Ethereum then verifies the proof, incurring a reduced gas cost.
This demo sets up a network in your local environment. Please read the instructions below to learn how to build and run the demo.
This repository contains multiple modules:
- An enclave contains ethereum and tendermint ELC
- A relayer between ethereum and tendermint
- MockApp(IBC-App) implementation in Go and Solidity
- ibc-solidity v0.3.38
- lcp v0.2.11
- ethereum-elc v0.0.20
- lcp-go v0.2.10
- lcp-solidity v0.1.15
- yui-relayer v0.5.8
- ethereum-ibc-relay-chain v0.3.10
- ethereum-ibc-relay-prover v0.3.4
You need to install the Intel SGX SDK for your environment:
$ curl -LO https://download.01.org/intel-sgx/sgx-linux/2.19/distro/ubuntu22.04-server/sgx_linux_x64_sdk_2.19.100.3.bin
$ chmod +x ./sgx_linux_x64_sdk_2.19.100.3.bin
$ echo -e 'no\n/opt' | ./sgx_linux_x64_sdk_2.19.100.3.bin
$ source /opt/sgxsdk/environment$ make yrly prepare-contracts build-images
$ make e2e-test
This mode is for non-SGX supported environment. This doesn't require SGX hardware and driver, but the enclave is not secure.
$ export SGX_MODE=SW
$ make yrly prepare-contracts build-images
$ make e2e-test
# NOTE: the following command requires sgx-sdk to be installed in the environment
$ make
If succeeded, a signed enclave binary is created at ./bin/enclave.signed.so.
$ make yrly
$ make -C ./tests/e2e/chains/tendermint image
The following command launches both tendermint and ethereum chains. It also deploys the solidity contract on the ethereum's execution chain.
$ make -C ./tests/e2e/cases/tm2eth network
First, generate an Enclave Key
$ /path/to/lcp enclave generate-key --enclave=/path/to/enclave.signed.so
0x8b76f939e238a54c7a1ba46ed4c027dc21993cc3
# set ENCLAVE_KEY environment variable for the following steps
$ export ENCLAVE_KEY=0x8b76f939e238a54c7a1ba46ed4c027dc21993cc3
Next, execute the remote attestation with the IAS and get an AVR that contains the public key of the Enclave Key from the IAS
$ /path/to/lcp enclave ias-remote-attestation --enclave_key=${ENCLAVE_KEY} --enclave=/path/to/enclave.signed.so
You probably need to edit the mrenclave, ibc_address values in the some files under ./tests/e2e/cases/tm2eth/configs with your own.
$ /path/to/lcp service start --enclave=/path/to/enclave.signed.so --address=127.0.0.1:50051 --threads=2
$ make -C ./tests/e2e/cases/tm2eth test
$ make -C ./tests/e2e/cases/tm2eth network-down