Account Contract
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.
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.
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.
Developer Documentation to use Authentication Witness for authentication actions on Aztec.
This guide explains how to create a new account using Aztec.js.
This guide explains how to rotate nullifer secret and public keys using Aztec.js. To learn more about key rotation, read the concepts section
This page assumes you have authwit set up correctly in your contract. To learn how to do that, go here.
Prerequisite reading
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.