Skip to content

Commit

Permalink
feat: generic key validation request
Browse files Browse the repository at this point in the history
  • Loading branch information
benesjan committed May 16, 2024
1 parent 74e98d4 commit 67baefd
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions docs/docs/aztec/aztec/concepts/accounts/keys.md
Original file line number Diff line number Diff line change
Expand Up @@ -119,10 +119,9 @@ This is a snippet of our Schnorr Account contract implementation, which uses Sch
Still, different accounts may use different signing schemes, may require multi-factor authentication, or _may not even use signing keys_ and instead rely on other authentication mechanisms. Read [how to write an account contract](/tutorials/tutorials/write_accounts_contract.md) for a full example of how to manage authentication.

Furthermore, and since signatures are fully abstracted, how the key is stored in the contract is abstracted as well and left to the developer of the account contract.
Below are a few ideas on how to store them, each with their pros and cons.
In the following section we describe a few ways how an account contract could be architected to store signing keys.

### Ways to store signing keys
Below we described a few ways how an account contract could be architected to obtain signing keys.
### Storing signing keys

#### Using a private note

Expand Down

0 comments on commit 67baefd

Please sign in to comment.