Skip to main content
Version: Next

note

Standalone Functions

assert_note_exists

assert_note_exists(context, note_hash_counter);

TODO: it feels like this existence check is in the wrong place. In fact, why is it needed at all? Under what circumstances have we found a non-existent note being emitted accidentally?

Parameters

NameType
contextPrivateContext
note_hash_counteru32

compute_note_log

compute_note_log(note, storage_slot, recipient, sender, );

Parameters

NameType
noteNote
storage_slotField
recipientAztecAddress
senderAztecAddress

compute_partial_note_log

compute_partial_note_log(note, storage_slot, recipient, sender, );

Parameters

NameType
noteNote
storage_slotField
recipientAztecAddress
senderAztecAddress

compute_log

compute_log(note, storage_slot, recipient, sender, msg_type, );

Parameters

NameType
noteNote
storage_slotField
recipientAztecAddress
senderAztecAddress
msg_typeu64

compute_note_log_unconstrained

compute_note_log_unconstrained(note, storage_slot, recipient, sender, );

Parameters

NameType
noteNote
storage_slotField
recipientAztecAddress
senderAztecAddress

encode_and_encrypt_note

encode_and_encrypt_note(context, recipient, // We need this because to compute a tagging secret, we require a sender, );

/ private logs.

Parameters

NameType
context&mut PrivateContext
recipientAztecAddress
// We need this because to compute a tagging secret
we require a sendersender

encode_and_encrypt_note_unconstrained

encode_and_encrypt_note_unconstrained(context, recipient, // We need this because to compute a tagging secret, we require a sender, );

/// Only use this function in scenarios where the recipient not receiving the note is an acceptable outcome.

Parameters

NameType
context&mut PrivateContext
recipientAztecAddress
// We need this because to compute a tagging secret
we require a sendersender