=nil

Ethereum L2 with zkSharding

Basics

• Based in:
• Started in / Announced on:
• Testnet release:
• Mainnet release:

Audits & Exploits

• Bug bounty program can be found [insert here].

Technology

• Whitepaper or docs can be found [insert here].
• Code can be viewed [insert here].
• Consensus mechanism:
• Algorithm:
• Virtual Machine:
• Development language used:

Transaction Details

• Capacity (TPS):
• Latency:

How it works

• From their announcement (29-4-2024):

"So, what does a network that uses zkSharding look like?

For example, the =nil; L2 splits the work between the main shard and the execution shards. All shards are interconnected and function as a whole: execution shards process transactions in parallel and generate ZKPs while the main shard verifies data, communicates with Ethereum, and synchronizes the state of the network across all validators. The main shard also manages the distribution of validators and accounts across the execution shards.

The =nil; L2 is run by a validator set that’s split into subsets (i.e. committees). All validator full nodes participate in the global consensus protocol run by the main shard. Additionally, at every validator-rotation-epoch, validator full nodes are randomly sampled and assigned to participate in an execution shard's committee.

zkSharding has a three-tier approach to security.

On the first level, validator committees run a local consensus (HotStuff-2 based) to build blocks in each execution shard.

On the second level, the execution shard committees generate a ZKP for the last N blocks they built. All committees send their proof to the main shard, where they are verified for correctness via a global consensus protocol (HotStuff-2 based).

Finally, the main shard aggregates all the execution shard proofs into a master ZKP and sends it to Ethereum for verification, after which the global state of the =nil; network is verified and reaches finality.

The main shard employs Ethereum for DA, while the execution shards use in-protocol DA from validators."

Interoperability

• From their announcement (29-4-2024):

"The =nil; L2 has cross-shard communication baked into the protocol from the start. Cross-shard messages are validated as transactions by each shard’s validator committee.

However, there might be some applications that require two contracts to call each other without any latency that comes with cross-shard communication. Contract co-location allows developers the flexibility to pay for contracts to live on the same execution shard, thus mitigating this overhead if necessary."

Roadmap

• Can be found [Insert link here].

Team, Funding and Partners

Team

• Full team can be found [here].

(:

Knowledge empowers all and will help us get closer to the decentralized world we all want to live in!

Making these free wiki pages is fun but takes a lot of effort and time.

If you have enjoyed reading, tips are appreciated :) This will help us to keep expanding this archive of information.

ETH tip address: 0x83460bE5F218b1520B69D702cE60A1DE37dD8E31