10 docs tagged with "accounts"

This tutorial will take you through the process of writing your own account contract in Aztec.nr, along with the Typescript glue code required for using it within a wallet.

Every account in Aztec is a smart contract which defines the rules for whether a transaction is or is not valid. This allows implementing different schemes for transaction signing, nonce management, and fee payments. However, encryption and nullifying keys, which are specific to private blockchains, are still enshrined at the protocol level.

Developer Documentation to use Authentication Witness for authentication actions on Aztec.

Authentication Witness is a scheme for authenticating actions on Aztec, so users can allow third-parties (eg protocols or other users) to execute an action on their behalf.

You can use the npx aztec-app command to clone a ready-to-go "aztec box" with a sample contract or frontend. Assuming you have node installed, run:

This guide explains how to create a new account using Aztec.js.

This page assumes you have authwit set up correctly in your contract. To learn how to do that, go here.

The goal of this section is to give app developer a good idea what keys there are used in the system.

This page talks about the architecture of a wallet in Aztec. Wallets expose to dapps an interface that allows them to act on behalf of the user, such as querying private state or sending transactions. Bear mind that, as in Ethereum, wallets should require user confirmation whenever carrying out a potentially sensitive action requested by a dapp.

In this page we will cover the main responsibilities of a wallet in the Aztec network.