Module nullifiers

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).
• is_nullifier_pending
  Returns true if the nullifier has been emitted in the same transaction, i.e. if notify_created_nullifier has been called for this inner nullifier from the contract with the specified address.
• notify_created_nullifier
  Notifies the simulator that a nullifier has been created, so that its correct status (pending or settled) can be determined when reading nullifiers in subsequent private function calls. The first non-revertible nullifier emitted is also used to compute note nonces.