From 2d4f4fcd7071ccde8462f82d79e0f5365deb8bb6 Mon Sep 17 00:00:00 2001 From: Suyash Bagad Date: Fri, 8 Sep 2023 11:39:19 +0000 Subject: [PATCH 1/2] init --- docs/docs/dev_docs/limitations/main.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/docs/dev_docs/limitations/main.md b/docs/docs/dev_docs/limitations/main.md index b1b68edad2c..424fa88b25d 100644 --- a/docs/docs/dev_docs/limitations/main.md +++ b/docs/docs/dev_docs/limitations/main.md @@ -247,6 +247,10 @@ A note which is created and nullified during the very same transaction is called For the time being, such chopped notes are still emitted through encrypted logs (which is the communication channel to transmit notes). When a log containing a chopped note is processed, a warning will be logged about a decrypted note which does not exist in data tree. We [improved](https://github.com/AztecProtocol/aztec-packages/issues/1603) error logging to help identify such an occurence. However, this might be a source of confusion. This issue is tracked in ticket [#1641](https://github.com/AztecProtocol/aztec-packages/issues/1641). +### Note Terminology: Note Commitments and Note Hashes + +The notes or UTXOs in aztec need to be compressed before they are added to the trees. To do so, we need to hash all the data inside a note using a collision-resistant hash function. Currently, we use Pedersen hash (using lookup tables) to compress note data. The compressed note data is referred to as "note commitments" in our architecture. However, note commitments are referred to as "note hashes" in aztec-noir code. Be mindful of that fact that note commitments and note hashes mean the same thing. + ## There's more See the [GitHub issues](https://github.com/AztecProtocol/aztec-packages/issues) for all known bugs fixes and features currently being worked on. \ No newline at end of file From 92c08ccdd711323c357f3857ea0a6e1d78c7a6b9 Mon Sep 17 00:00:00 2001 From: Suyash Bagad Date: Fri, 8 Sep 2023 12:24:15 +0000 Subject: [PATCH 2/2] jean. --- docs/docs/dev_docs/limitations/main.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/dev_docs/limitations/main.md b/docs/docs/dev_docs/limitations/main.md index 424fa88b25d..d4198b7327e 100644 --- a/docs/docs/dev_docs/limitations/main.md +++ b/docs/docs/dev_docs/limitations/main.md @@ -249,7 +249,7 @@ This issue is tracked in ticket [#1641](https://github.com/AztecProtocol/aztec-p ### Note Terminology: Note Commitments and Note Hashes -The notes or UTXOs in aztec need to be compressed before they are added to the trees. To do so, we need to hash all the data inside a note using a collision-resistant hash function. Currently, we use Pedersen hash (using lookup tables) to compress note data. The compressed note data is referred to as "note commitments" in our architecture. However, note commitments are referred to as "note hashes" in aztec-noir code. Be mindful of that fact that note commitments and note hashes mean the same thing. +The notes or UTXOs in Aztec need to be compressed before they are added to the trees. To do so, we need to hash all the data inside a note using a collision-resistant hash function. Currently, we use Pedersen hash (using lookup tables) to compress note data. The compressed note data is referred to as "note commitments" in our architecture. However, note commitments are referred to as "note hashes" in aztec-noir code. Be mindful of that fact that note commitments and note hashes mean the same thing. Note that we only mean to talk about terminology here and in no way one should infer security/cryptographic properties (e.g., hiding, binding) based on the name. Namely, notes come with different flavours of security properties depending on the use case. ## There's more