Charlie

The Aztec builder generates typescript classes for Noir contract, as well as Aztec.nr interfaces for calling external functions. It can also be used to update aztec project dependencies.

The Aztec CLI `aztec-cli` is a command-line interface (CLI) tool for interacting with Aztec. It provides various commands for deploying contracts, creating accounts, interacting with contracts, and retrieving blockchain data.

This library package is responsible for simulating function circuits compiled to ACIR / AVM.

A key store is an input component for the [PXE](../pxe/) to manage keys securely. It provides a secure environment and interfaces for users to manage their keys. When the PXE requests keys and signatures from the key store, a well-designed key store shoul

The Aztec KV store is an implementation of a durable key-value database with a pluggable backend. The only supported backend right now is LMDB by using the [`lmdb-js` package](https://github.com/kriszyp/lmdb-js).

Distributed locking and slashing protection for Aztec validators running in high-availability configurations.

The Aztec Node implements a sequencer node in the network, and is currently meant to be used for local development and testing. The Node is the entrypoint for creating and starting a new Sequencer client with default components (a local P2P client, an in-

The sequencer is a module responsible for creating and publishing new rollup blocks. This involves fetching txs from the P2P pool, ordering them, executing any public functions, running them through the rollup circuits, assembling the L2 block, and postin

The slasher module implements validator slashing for the Aztec network. Slashing punishes validators who misbehave or are inactive by reducing their stake. This mechanism ensures network security and liveness.

This package provides configuration and code for common chain operations such as contract deployment etc.

Canonical Noir contracts for the Aztec Network

The goal of this module is to provide a simple place for people to construct benchmarks of witness generation and proving. At the moment it only pertains to UltraHonk recursion in the browser, but we have a similar module in ivc-integration that shows pro

Aztec's SDK is the gateway for developers to access the Aztec network, and benefit from low gas fees and privacy on Ethereum. The SDK connects to our ZkRollup service and can be integrated with one line of code.

A client library for storing and retrieving blob data from various sources.

The Merkle Trees package contains typescript implementations of the various Merkle Trees required by the system.

This package is responsible for smart contract and other blockchain related work.

The primary functions of the world state package are to maintain the collection of Merkle Trees comprising the global state of the system and to offer an interface with which the trees can be queried.

## Responsibilities

`PXE` (pronounced "pixie service") is a server-side software that provides a set of apis for interacting with the Aztec network. It acts as a bridge between the network and client applications by exposing methods to manage accounts, deploy contracts, crea

A HTTP api that losely emulates the https://ethereum.github.io/beacon-APIs/?urls.primaryName=dev#/Beacon/getBlobSidecars API. We do not support all of the possible values of block_id, namely `genesis`, `head`, `finalized`. As we are not using any of these

Prover/verifier library for barretenberg. It bundles support for the following:

The archiver fetches onchain data from L1 and stores it locally in a queryable form. It pulls: - **Checkpoints** (containing L2 blocks) from `CheckpointProposed` events on the Rollup contract - **L1-to-L2 messages** from `MessageSent` events on the Inbox

The validator client handles consensus duties for Aztec validators: validating block proposals, attesting to checkpoints, and detecting slashable some offenses. Validators do NOT attest to individual blocks. Attestations are only created for checkpoint pr

This guide explains how to integrate your wallet with the Aztec Wallet SDK, enabling dApps to discover and interact with your wallet implementation.

Simple bot that connects to a PXE to send txs on a recurring basis.

This module is used to test the IVC integration between mock noir protocol circuits and barretenberg.

The Aztec.nr compiler compiles Aztec.nr contracts using nargo and outputs Aztec formatted contract ABIs. The compiler can also generate typescript classes for each contract, as well as Aztec.nr interfaces for calling external functions.

This package includes the functionality of the P2P networking required by the aztec node. The `P2PClient` provides an interface for the introduction of transactions to the Tx Pool and propagation of those transactions through the network. The `P2PService`

1) Start a local Ethereum node (Anvil) in one terminal:

Implementation of sample contract entrypoints for the Aztec Network

This package provides an implementation of a 'Bootstrap' P2P node. It's purpose is to assist new network participants in acquiring peers.

Aztec.js is a library that provides APIs for managing accounts and interacting with contracts on the Aztec network. It communicates with the [Private eXecution Environment (PXE)](https://docs.aztec.network/developers/foundational-topics/pxe) through a `PX

`AztecRPCServer` is a server-side software that provides a set of apis for interacting with the Aztec network. It acts as a bridge between the network and client applications by exposing methods to manage accounts, deploy contracts, create transactions, a

No description available

Implementation of sample account contracts for Aztec Network

This package includes end-to-end tests that cover Aztec's main milestones. These can be run locally either by starting anvil on a different terminal.

Aztec is a package that allows for a simple development environment on Aztec stack. It creates a Private eXecution Environment (PXE) that listens for HTTP requests on `localhost:8080` by default. When started, it deploys all necessary L1 Aztec contracts a

Compiled Noir mock protocol circuit artifacts, for proving system integration tests.

The slasher module implements validator slashing for the Aztec network. Slashing punishes validators who misbehave or are inactive by reducing their stake. This mechanism ensures network security and liveness.

The Aztec builder generates typescript classes for Noir contract, as well as Aztec.nr interfaces for calling external functions. It can also be used to update aztec project dependencies.

A key store is an input component for the [PXE](../pxe/) to manage keys securely. It provides a secure environment and interfaces for users to manage their keys. When the PXE requests keys and signatures from the key store, a well-designed key store shoul

Distributed locking and slashing protection for Aztec validators running in high-availability configurations.

The Aztec CLI `aztec-cli` is a command-line interface (CLI) tool for interacting with Aztec. It provides various commands for deploying contracts, creating accounts, interacting with contracts, and retrieving blockchain data.

This module is used to test the IVC integration between mock noir protocol circuits and barretenberg.

Simple bot that connects to a PXE to send txs on a recurring basis.

The archiver fetches onchain data from L1 and stores it locally in a queryable form. It pulls: - **Checkpoints** (containing L2 blocks) from `CheckpointProposed` events on the Rollup contract - **L1-to-L2 messages** from `MessageSent` events on the Inbox

1) Start a local Ethereum node (Anvil) in one terminal:

The Aztec Node implements a sequencer node in the network, and is currently meant to be used for local development and testing. The Node is the entrypoint for creating and starting a new Sequencer client with default components (a local P2P client, an in-

Aztec is a package that allows for a simple development environment on Aztec stack. It creates a Private eXecution Environment (PXE) that listens for HTTP requests on `localhost:8080` by default. When started, it deploys all necessary L1 Aztec contracts a

Implementation of sample account contracts for Aztec Network

The Aztec KV store is an implementation of a durable key-value database with a pluggable backend.

The primary functions of the world state package are to maintain the collection of Merkle Trees comprising the global state of the system and to offer an interface with which the trees can be queried.

Aztec.js is a library that provides APIs for managing accounts and interacting with contracts on the Aztec network. It communicates with the [Private eXecution Environment (PXE)](https://docs.aztec.network/developers/foundational-topics/pxe) through a `PX