New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started
n

nchamo

npm

361.75K

total weekly downloads

Packages

Current Co-maintainers

Former Co-maintainers

76 packages

@aztec-labs/accounts

Implementation of sample account contracts for Aztec Network

@aztec-labs/archiver

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

@aztec-labs/aztec

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

@aztec-labs/aztec.js

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

@aztec-labs/aztec-node

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-labs/bb-prover

@aztec-labs/blob-client

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

@aztec-labs/blob-lib

@aztec-labs/bot

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

@aztec-labs/builder

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.

@aztec-labs/cli

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.

@aztec-labs/cli-wallet

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

@aztec-labs/constants

@aztec-labs/docs

To generate docs. Go to the root of `yarn-project` and run:

@aztec-labs/end-to-end

This package holds Aztec's end-to-end (e2e) tests: full-stack scenarios that spin up an Aztec node (or several), a PXE, and an L1 (anvil) and exercise the system the way a real deployment would. It is the integration layer above the per-package unit tests

@aztec-labs/entrypoints

Implementation of sample contract entrypoints for the Aztec Network

@aztec-labs/epoch-cache

Caches validator committee information per epoch to reduce L1 RPC traffic. Provides the current committee, proposer selection, and escape hatch status for any given slot or epoch, used by the sequencer, validator client, and other node components that nee

@aztec-labs/ethereum

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

@aztec-labs/foundation

@aztec-labs/ivc-integration

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

@aztec-labs/key-store

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

@aztec-labs/kvdb

@aztec-labs/kvdb-darwin-arm64

Native NAPI addon for @aztec-labs/kvdb (darwin-arm64)

@aztec-labs/kvdb-darwin-x64

Native NAPI addon for @aztec-labs/kvdb (darwin-x64)

@aztec-labs/kvdb-linux-arm64

Native NAPI addon for @aztec-labs/kvdb (linux-arm64)