Module notes

Functions

• check_nullifier_exists
  Returns true if the nullifier exists. Note that a true value can be constrained by proving existence of the nullifier, but a false value should not be relied upon since other transactions may emit this nullifier before the current transaction is included in a block. While this might seem of little use at first, certain design patterns benefit from this abstraction (see e.g. PrivateMutable).
• get_app_tag_as_sender
  Returns the derived app tagging secret ready to be included in a log for a given sender and recipient pair, siloed for the current contract address.
• get_notes
• get_sender_for_tags
  Gets the sender for tags.
• increment_app_tagging_secret_index_as_sender
  Notifies the simulator that a tag has been used in a note, and to therefore increment the associated index so that future notes get a different tag and can be discovered by the recipient. This change should only be persisted in a non-volatile database if the tagged log is found in an actual block - otherwise e.g. a reverting transaction can cause the sender to accidentally skip indices and later produce notes that are not found by the recipient.
• notify_created_note
  Notifies the simulator that a note has been created, so that it can be returned in future read requests in the same transaction. This note should only be added to the non-volatile database if found in an actual block.
• notify_created_nullifier
  Notifies the simulator that a non-note nullifier has been created, so that it can be used for note nonces.
• notify_nullified_note
  Notifies the simulator that a note has been nullified, so that it is no longer returned in future read requests in the same transaction. This note should only be removed to the non-volatile database if its nullifier is found in an actual block.
• set_sender_for_tags
  Sets the sender for tags.