# Creating an Aztec Account Contract - [Github Repo to follow along](https://github.com/critesjosh/aztec-account-abstraction-workshop) - [Aztec Docs: Quickstart](https://docs.aztec.network/dev_docs/getting_started/quickstart) - Example [Schnorr Signer account contract](https://github.com/AztecProtocol/aztec-packages/tree/master/yarn-project/noir-contracts/src/contracts/schnorr_account_contract) ## Setup **Docker** - start Docker - Install the sandbox and CLI ```bash DEBUG=aztec:simulator:oracle /bin/bash -c "$(curl -fsSL 'https://sandbox.aztec.network')" ``` **NPM** 1. start an Eth node ```bash anvil ``` 2. Start the sandbox ```bash npx @aztec/aztec-sandbox ``` 3. Install the CLI ```bash npm i -g @aztec/cli ``` ### Contract Syntax Highlighting *Optional, but recommended* This is achieved with the Noir Language Server (LSP). 1. Install `noirup`: ```bash curl -L https://raw.githubusercontent.com/noir-lang/noirup/main/install | bash ``` 2. Install Aztec-Noir: ```bash noirup -v v0.18.0-aztec.5 ```
Last changed by  
 
Josh
109

Read more

Aztec Handbook

This is going to focused on the aspects of building–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.

3/20/2024
Aztec Contracts - Common Patterns

How to handle private escrows between two parties…?

10/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's possible. The multisig and voting use cases explored at the bottom of this document are improved greatly when using recursive proofs for aggregation.

6/14/2023
zk Voting with ECDSA sig verification and storage proofs

WIP circuit here Membership inclusion Storage Proofs verifying token ownership requires storage proofssnapshot at a given block w/ specific block header zk program verifies a storage proof on that header struct Proposal { uint snapshotBlock; bytes32 blockHeader;

5/25/2023
Read more from Josh
Published on HackMD