Skip to content

Part of the Linea stack responsible for extracting data from the execution of an EVM client in order to construct large matrices called execution traces.

License

Notifications You must be signed in to change notification settings

Consensys/linea-tracer

Folders and files

NameName
Last commit message
Last commit date

Latest commit

1f3d4ca · Oct 22, 2024
Oct 22, 2024
Jun 14, 2023
Oct 22, 2024
Oct 17, 2024
Sep 4, 2024
Oct 18, 2024
Jun 13, 2024
Oct 17, 2024
Sep 16, 2024
Oct 22, 2024
Sep 22, 2024
Oct 22, 2024
Aug 16, 2024
Jul 24, 2023
Sep 4, 2024
Oct 10, 2024
Oct 7, 2024
Jul 31, 2024
Sep 4, 2024
Sep 23, 2024
Sep 17, 2024
Sep 23, 2024
Feb 20, 2024
Oct 7, 2024
Jun 13, 2024
Jun 13, 2024
Aug 16, 2024
Aug 23, 2023

Repository files navigation

Linea tracer (zkEVM)

This repository hosts a Linea tracing implementation for Besu based on an implementation in Go.

Tracing refers to the process of extracting data from the execution of an EVM client in order to construct large matrices known as execution traces. Execution traces are subject to the constraint system specified in the linea-specification repo and implemented in the linea-constraints repo.

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 Get Started 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-tracer: Linea-Besu plugin which produces the traces that the constraint system applies and that serve as inputs to the prover

This repository contains the elements of the Linea stack responsible for this process.

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

... and more.

How to contribute

Contributions of any kind are welcome!

  1. Create an issue.

If the proposed update is non-trivial, 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