Skip to content
You are reading ConsenSys Rollups development version documentation and some displayed features may not be available in the stable release. You can switch to stable version using the version box at screen bottom.

Updated on October 16, 2021

ConsenSys Rollups architecture

The following diagram outlines the ConsenSys Rollups high-level architecture.

Architecture

The following steps describe the communication between the manager and engine components, which is asynchronous due to the nature of interactions with the blockchain:

  1. The manager accepts a request from a dapp and does some preliminary validation.
  2. The manager computes the operation hash using a cryptographic library.
  3. The manager saves the pending operation on its local database.
  4. The engine registers the request from the manager if it passes some initial validation.
  5. After executing operations, the engine submits the batch to the blockchain.
  6. When a request is submitted to a blockchain, and a “Batch Submitted” event is received, the engine sends batch information to a Kafka topic. Each operation in the batch data contains an operation hash, so the manager can map it to particular request from the user.
  7. When the engine receives a “Batch Finalized” event, it sends a message to a Kafka topic, which includes the batch height.
  8. When the manager receives a “Batch Finalized” message from Kafka, it updates its local database.

For more information about the ConsenSys Rollups architecture, contact us on ConsenSys Rollups Discord channel.

Questions or feedback? You can discuss and obtain free support on ConsenSys Rollups Discord channel.