Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove incorrect content from the index page. #60

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Remove incorrect content from the index page. #60

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,14 +9,15 @@ title: ConsenSys Rollups
ConsenSys Rollups is a framework for implementing [rollups](Concepts/Rollups/Overview.md) for the Ethereum blockchain.
Rollups are layer 2 scaling solutions that improve the scalability of Ethereum networks by performing mass transaction
validation offchain.
ConsenSys Rollups supports any EVM-based protocol, including proof of work (PoW) and proof of authority (PoA) protocols.

ConsenSys Rollups currently implements [partially anonymous rollups](Concepts/Rollups/Partially-Anonymous-Rollups.md),
with plans to add support for other types of rollups (consensus-rollups and optimistic-rollups).
ConsenSys Rollups is an application-specific rollup with [partial anonymity](Concepts/Rollups/Partially-Anonymous-Rollups.md),
and is designed for private transfers at scale.

In the long term ConsenSys Rollups plans to add support for ZK-EVM programmable rollups.

![Architecture](Images/ConsenSys-Rollups-Overview.png)

ConsenSys Rollups introduces a centralized actor called an operator which consists of a manager and engine.
ConsenSys Rollups introduces an actor called an operator which consists of a manager and engine.
The operator receives and executes transactions, manages the state, and submits batch transactions
to the Ethereum network. The blockchain nodes do not re-execute the transactions.

Expand Down