The blockchain system is designed to store the association between a public key and a username in Ethereum (L1), while processing social connections and relationships within the L2 layer. Potential L2 implementations may include HLF (Hyperledger Fabric) or COSMOS.

Bridge Between ETH and L2

To ensure secure and reliable communication between the Ethereum blockchain and the L2 blockchain, the system implements a bidirectional bridge consisting of multiple server components. Each server component has a unique key used for signing transactions processed by the bridge.

When a token is transferred from Ethereum to L2, the token remains on the Ethereum bridge and is emitted in L2. Conversely, when transferring back, the token is burned in L2, and a corresponding token is released from the bridge in Ethereum.

Heimdall Bridge Analogy

Similar to the Heimdall bridge, the Ethereum network employs a mechanism for collecting and verifying signatures. This ensures that all transaction signatures are gathered using keys that have been pre-approved and included in the list of trusted addresses. This process guarantees the authenticity of transactions within the bridge system.

Achieving Consensus

For executing methods that facilitate the interaction between the two blockchains, the system requires reaching a consensus among a set of permitted addresses. These addresses belong to the bridges and act as validators, thereby enhancing the security of the ecosystem.

Creating this structure with multiple nodes and a consensus system ensures high transaction reliability and increases the overall security of the blockchain solution.

Process Overview

The schematic process of how the bridge operates can be envisioned as follows:

ETH to L2 Bridge

1. When a token is transferred from ETH to L2, the token remains on the ETH bridge.

2. A corresponding token is emitted in the L2 network.

L2 to ETH Bridge

1. When transferring a token from L2 back to ETH, the token is burned in L2.

2. The corresponding token is released from the ETH bridge.

Technical Specifics

The bridge leverages multiple nodes, each responsible for verifying transactions. This multi-signature requirement ensures that no single entity has control over the bridge, which adds a layer of security and prevents unauthorized actions.

Security and Reliability

By implementing such a robust architecture, the blockchain system ensures the integrity and reliability of transactions between the L1 and L2 layers. This setup also minimizes the risk of hostile interference and maintains the seamless functioning of the interconnected blockchains.

Last updated