Skip to content

Commit 836ac12

Browse files
committed
update README
Signed-off-by: Jun Kimura <[email protected]>
1 parent bfd7f1e commit 836ac12

File tree

2 files changed

+19
-1
lines changed

2 files changed

+19
-1
lines changed

.github/logo.png

38.6 KB
Loading

README.md

+19-1
Original file line numberDiff line numberDiff line change
@@ -1 +1,19 @@
1-
# LCP (Light Client Proxy)
1+
# LCP (Light Client Proxy)
2+
3+
<div align="center">
4+
<img alt="LCP" src="./.github/logo.png" />
5+
</div>
6+
7+
LCP is a proxy for light client verification executed in TEE.
8+
9+
LCP uses Intel SGX, a representative TEE implementation, to provide light clients implemented in enclave. It also provides an on-chain client(called LCP Client) that verifies commitments indicating the results of verification by the light clients. In addition, LCP Client is compatible with [ICS-02](https://github.com/cosmos/ibc/tree/main/spec/core/ics-002-client-semantics), so LCP can be integrated with [IBC](https://github.com/cosmos/ibc).
10+
11+
The design of LCP is based on the following principles:
12+
13+
- Minimum trust assumptions: In addition to the trust assumptions of the Light Client scheme, which is the most secure verification scheme, LCP needs to add as little trust as possible, the TEE trust.
14+
- Ultra efficient on-chain verification: A client on the downstream verifies a single signature on a resulting commitment generated in the Enclave instead of verifying the upstream. It will reduce the verification cost and the size of verification transactions (e.g., no need to include validators' info in the upstream).
15+
- Extensible: No need for an on-chain light client implementation for each chain combination, only a light client implementation per chain that the Enclave can execute.
16+
17+
## Documentation
18+
19+
For the details, please see here: https://docs.lcp.network

0 commit comments

Comments
 (0)