Skip to content

Commit 6d19ba5

Browse files
committed
wip
1 parent 12bff16 commit 6d19ba5

1 file changed

Lines changed: 10 additions & 7 deletions

File tree

noir-projects/aztec-nr/aztec/src/event/event_interface.nr

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -43,15 +43,18 @@ use dep::protocol_types::{
4343
///
4444
///
4545
/// # Message authenticity
46-
/// Note that we always commit to the plaintext and the recipient is therefore always able to verify the authenticity
47-
/// of the message no matter the delivery mechanism.
46+
/// Note that we always commit to the plaintext and the recipient is therefore always able to verify
47+
/// the authenticity of the message no matter the delivery mechanism.
4848
///
4949
///
5050
/// # Message Delivery Variants and Their Use Cases
5151
///
5252
/// The following section outlines the recommended delivery variants and when to use each one.
53-
/// Each variant represents a different tradeoff between security guarantees, gas costs, and trust assumptions.
54-
/// - We are currently still exploring the design space but it seems that there are only 2 meaningful combinations:
53+
/// Each variant represents a different tradeoff between security guarantees, gas costs, and trust
54+
/// assumptions.
55+
///
56+
/// We are currently still exploring the design space but it seems that there are only 2 meaningful
57+
/// combinations:
5558
///
5659
/// +--------------------------------------------------------------------------------------------------------+
5760
/// | 1. Constrained encryption, constrained tagging, private log stream |
@@ -79,9 +82,9 @@ use dep::protocol_types::{
7982
/// +--------------------------------------------------------------------------------------------------------+
8083
///
8184
///
82-
/// Other combinations like unconstrained encryption, unconstrained tagging, private log stream don't seem to be
83-
/// meaningful because they are way costlier that combination 2 above while providing no meaningful additional
84-
/// guarantees.
85+
/// Other combinations like unconstrained encryption, unconstrained tagging, private log stream don't seem
86+
/// to be meaningful because they are costlier than combination 2 above while providing no meaningful
87+
/// additional guarantees.
8588
pub struct MessageDeliveryEnum {
8689
/// Constrained encryption + constrained tagging + private log stream
8790
///

0 commit comments

Comments
 (0)