Try   HackMD

Aztec Handbook

This handbook is focused on the aspects of building on Aztec.network–no high level explainers of how to do things.

High level explanations should link back to docs pages. Much of this content is already written. For content that is already exists, link to it–for content that does not exist yet, create an issue and maybe write it.

The goal is to reduce the on-boarding time to Aztec to <1 week.

Before wave 3 we need to create a handbook of existing repos and research on the design space

  • Includes Forum posts, github repos, and relevant public info aggregate info from previous notes/ discord discussions
  • Dont want new partners to reinvent anything
  • Complete this by the end of Q1
  • Can be a list of references
  • Can be a single page document that lives in docs.aztec.network

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →
The Aztec protocol is under rapid development. We typically do releases of updated software at least once a week. Releases are often not backwards compatible. Libraries, compiler and sandbox must all be the same version to work.

As a result design patterns and suggestions linked here may change, but this is a great place to start.

Installation

Prerequisites

  • Node.js >= 18. Recommended to use nvm
  • Docker

Sandbox

bash -i <(curl -s install.aztec.network)

Once this is installed, update by running aztec-up.

Doc

Write your first contract

Aztec.nr

Compile

Deploy

Testing

Starter boxes

Debugging

Understanding the PXE

Oracles

Common Patterns

Authorization Witnesses (Authwit)

Portal contracts

Note lifecycle info

Transaction lifecycle

Accounts

Intro to account abstraction
writing account contracts

Last changed by 
 
Josh
0
154

Read more

Aztec Monorepo setup

Here are the commands to get the monorepo set up on a linux machine.

Nov 21, 2024
Creating an Aztec Account Contract

https://github.com/critesjosh/aztec-account-abstraction-workshop

Nov 14, 2023
Aztec Contracts - Common Patterns

How to handle private escrows between two parties…?

Oct 30, 2023
Minimal arbitrarily generic attestations (MAGA)

MAGA is a simple on-chain, privacy preserving attestations protocol. Attestations are associated with an ECDSA signature hash that a user can verify ownership of with a zk proof. Github repo here. This may be best for off chain applications. consider making the time a Public input that invalidates it after X seconds. the solidity contract could be adapted for specific onchain applications, to make it resistant to front-running the proof public inputs must include any inputs to other solidity functions in the transaction. so for access control, the proof must include inputs for the action to be taken. eg, if its for a vote, the proof must include the vote (for, against), the proposal id and contract, otherwise those could be manipulated by a front runner. Recursive proofs greatly expand the design space of what&apos;s possible. The multisig and voting use cases explored at the bottom of this document are improved greatly when using recursive proofs for aggregation.

Jun 14, 2023
Read more from Josh
Published on HackMD