Skip to content

Commit

Permalink
Typo 003-action-views.md (#1993)
Browse files Browse the repository at this point in the history
  • Loading branch information
dedyshkaPexto authored Jan 24, 2025
1 parent cc9b871 commit 0c9e1ea
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/adrs/003-action-views.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ This specification is intended to inform what information should be comprehended
- `BatchSwapOutputData`: <u>**_opaque_**</u> field since the BSOD in the TxP does not leak any information about the specific output notes that the view service computes for the swap using the BSOD. Computing the output notes already assumes decrypting the swap ciphertext. The BSOD contains the results of the batch swap and is emitted in an event.
- `ValueView`: <u>**_opaque_**</u> field since the swap values are in the clear.
- `Metadata`: <u>**_opaque_**</u> field and the metadata is reported on-chain.
- `SwapPlaintext`: <u>**_visible_**</u> field since the decrypted swap ciphertext enables, alongside the BSOD, to retrieve output notes, which amonst other fields includes the private address controlling the note.
- `SwapPlaintext`: <u>**_visible_**</u> field since the decrypted swap ciphertext enables, alongside the BSOD, to retrieve output notes, which amongst other fields includes the private address controlling the note.
- `TransactionId`: <u>**_visible_**</u> field since it's associated with a commitment that will eventually be nullified, and since nullifiers are public, revealing the transaction ID creates a link between the commitment and the nullifier that commitment nullifies.
- `NoteView`: <u>**_visible_**</u> field since it consists of sensitive fields like the claim address which should not be leaked.

Expand Down

0 comments on commit 0c9e1ea

Please sign in to comment.