From 8c708450002b41f6fcd54c96aa2f91fb2e427978 Mon Sep 17 00:00:00 2001 From: Santiago Palladino Date: Wed, 1 Nov 2023 09:34:06 -0300 Subject: [PATCH] docs: Fix in nullifier secrets doc (#3167) Credit to @skeletor-spaceman for the find Co-authored-by: Skeletor Spaceman --- docs/docs/concepts/foundation/accounts/keys.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/concepts/foundation/accounts/keys.md b/docs/docs/concepts/foundation/accounts/keys.md index 401db05cae7..b3a49ffbe93 100644 --- a/docs/docs/concepts/foundation/accounts/keys.md +++ b/docs/docs/concepts/foundation/accounts/keys.md @@ -82,7 +82,7 @@ Note that any accounts you own that have been added to the PXE are automatically In addition to deriving encryption keys, the privacy master key is used for deriving nullifier secrets. Whenever a private note is consumed, a nullifier deterministically derived from it is emitted. This mechanisms prevents double-spends, since nullifiers are checked by the protocol to be unique. Now, in order to preserve privacy, a third party should not be able to link a note commitment to its nullifier - this link is enforced by the note implementation. Therefore, calculating the nullifier for a note requires a secret from its owner. -An application in Aztec.nr can request a nullifier from the current user for computing the nullifier of a note via the `get_secret_key` oracle call: +An application in Aztec.nr can request a secret from the current user for computing the nullifier of a note via the `get_secret_key` oracle call: #include_code nullifier /yarn-project/aztec-nr/value-note/src/value_note.nr rust