Help update this page

🌏

There’s a new version of this page but it’s only in English right now. Help us translate the latest version.

No bugs here!🐛

This page is not being translated. We've intentionally left this page in English for now.

Shard chains

  • Sharding is a multi-phase upgrade to improve Ethereum’s scalability and capacity.
  • Shard chains provide extra, cheaper, storage layers for applications and rollups to store data.
  • They enable layer 2 solutions to offer low transaction fees while leveraging the security of Ethereum.
  • This upgrade is planned to follow The Merge of Mainnet with the Beacon Chain.

Page last updated: May 26, 2022

When's it shipping?

~2023

Shard chains should ship sometime in 2023, depending on how quickly work progresses after The Merge. These shards will give Ethereum more capacity to store and access data, but they won’t be used for executing code.

What is sharding?

Sharding is the process of splitting a database horizontally to spread the load – it’s a common concept in computer science. In an Ethereum context, sharding will reduce network congestion and increase transactions per second by creating new chains, known as “shards”.

This is important for reasons other than scalability.

Features of sharding

Everyone can run a node

Sharding is a good way to scale if you want to keep things decentralized as the alternative is to scale by increasing the size of the existing database. This would make Ethereum less accessible for network validators because they'd need powerful and expensive computers. With shard chains, validators only need to store/run data for the shard they're validating, not the entire network (like what happens today). This speeds things up and drastically reduces hardware requirements.

More network participation

Sharding will eventually let you run Ethereum on a personal laptop or phone. So more people should be able to participate, or run clients, in a sharded Ethereum. This will increase security because the more decentralized the network, the smaller the attack surface area.

With lower hardware requirements, sharding will make it easier to run clients on your own, without relying on any intermediary services at all. And if you can, consider running multiple clients. This can help network health by further reducing points of failure. Run a Beacon Chain client


At first, you'll need to run a Mainnet client at the same time as your Beacon Chain client. The launchpad will walk you through the hardware requirements and process. Alternatively you can use a backend API.

Shard chains version 1: data availability

When the first shard chains are shipped they will just provide extra data to the network. They won’t handle transactions or smart contracts. But they’ll still offer incredible improvements to transactions per second when combined with rollups.

Rollups are a "layer 2" technology that exists today. They allow dapps to bundle or “roll up” transactions into a single transaction off-chain, generate a cryptographic proof and then submit it to the chain. This reduces the data needed for a transaction. Combine this with all the extra data availability provided by shards and you get 100,000 transactions per second.

Given recent progress in layer 2 scaling solution research and development, this has prompted the prioritization of The Merge upgrade ahead of shard chains. These will be the focus following Mainnet transition to proof-of-stake.

More on rollups

Shard chains version 2: code execution

The plan was always to add extra functionality to shards, to make them more like the Ethereum Mainnet today. This would allow them to store and execute code and handle transactions, as each shard would contain its unique set of smart contracts and account balances. Cross-shard communication would allow for transactions between shards.

Considering the transactions per second boost that version 1 shards provide though, does this still need to happen? This is still being debated in the community and it seems like there are a few options.

Do shards need code execution?

Vitalik Buterin, when talking to Bankless podcast, presented 3 potential options that are worth discussing.

1. State execution not needed

This would mean we don’t give shards the capability to handle smart contracts and leave them as data depots.

2. Have some execution shards

Perhaps there’s a compromise where we don’t need all shards (64 are planned right now) to be smarter. We could just add this functionality to a few and leave the rest. This could speed the delivery up.

3. Wait until we can do Zero Knowledge (ZK) snarks

Finally, perhaps we should revisit this debate when ZK snarks are firmed up. This is a technology that could help bring truly private transactions to the network. It’s likely that they’ll require smarter shards, but they’re still in research and development.

Other sources

Here's some more thinking along the same lines:

This is still an active discussion point. We’ll update these pages once we know more.

Relationship between upgrades

The Ethereum upgrades are all somewhat interrelated. So let’s recap how the shard chains relate the other upgrades.

Shards and the beacon chain

The Beacon Chain contains all the logic for keeping shards secure and synced up. The Beacon Chain will coordinate the stakers in the network, assigning them to shards they need to work on. And it will also facilitate communication between shards by receiving and storing shard transaction data that is accessible by other shards. This will give shards a snapshot of Ethereum’s state to keep everything up-to-date.

The Beacon Chain

Shards and The Merge

By the time additional shards are added, Ethereum Mainnet will already be secured by the Beacon Chain using proof-of-stake. This enables a fertile Mainnet to build shard chains off of, powered by layer 2 solutions that supercharge the scalability.

It remains to be seen whether Mainnet will exist as the only “smart” shard that can handle code execution – but either way, the decision to expand shards can be revisited as needed.

The Merge

Read more