Skip to content

Latest commit

 

History

History
66 lines (43 loc) · 3.91 KB

README.md

File metadata and controls

66 lines (43 loc) · 3.91 KB
Raw

Besu Plugins related to tracer and sequencer functionality

This repository hosts the implementation of the sequencer, the component of the Linea stack responsible for ordering transactions and building blocks, as well as executing them. It provides a set of Besu:Linea plugins.

It serves developers by making the Linea tech stack open source under the Apache 2.0 license.

What is Linea?

Linea is a developer-ready layer 2 network scaling Ethereum. It's secured with a zero-knowledge rollup, built on lattice-based cryptography, and powered by Consensys.

Get started

If you already have an understanding of the tech stack, use our Quickstart guide.

Looking for Plugins?

Discover existing plugins and understand the plugin release process.

Looking for the Linea code?

Linea's stack is made up of multiple repositories, these include:

  • This repo, linea-sequencer: A set of Linea-Besu plugins for the sequencer and RPC nodes
  • linea-monorepo: The main repository for the Linea stack & network
  • linea-besu: Fork of Besu to implement the Linea-Besu client
  • linea-tracer: Linea-Besu plugin which produces the traces that the constraint system applies and that serve as inputs to the prover
  • linea-constraints: Implementation of the constraint system from the specification
  • linea-specification: Specification of the constraint system defining Linea's zkEVM

Linea abstracts away the complexity of this technical architecture to allow developers to:

... and more.

How to contribute

Contributions are welcome!

Guidelines for Non-Code and other Trivial Contributions

Please keep in mind that we do not accept non-code contributions like fixing comments, typos or some other trivial fixes. Although we appreciate the extra help, managing lots of these small contributions is unfeasible, and puts extra pressure in our continuous delivery systems (running all tests, etc). Feel free to open an issue pointing any of those errors, and we will batch them into a single change.

  1. Create an issue.

If the proposed update requires input, also tag us for discussion.

  1. Submit the update as a pull request from your fork of this repo, and tag us for review.

Include the issue number in the pull request description and (optionally) in the branch name.

Consider starting with a "good first issue".

Before contributing, ensure you're familiar with:

Useful links