e.g: "my account value is superior to 5" (non strict claim)
or "my account value is strictly equal to 5" (strict claim)
They correctly generated a userTicket (aka nullifierHash) by hashing the ticketIdentifier (a.k.a externalNullifier) with the secret from the source account (a.k.a IdNullifier)
The user ticket (a.k.a nullifierHash) can be stored by the verifier to make sure that a user cannot use two ZKPs for the same ticket identifier (a.k.a externalNullifier)
The Hydra-S1 ZK Proving Scheme is used by the Hydra S1 Attesters of the Sismo Protocol.
In the Hydra S1 Simple Attester, we use the Hydra S1 proving scheme to let a user:
Prove they own a source account that's part of a specific Group of accounts identified by a group identifier. (the accounts tree value in the registry tree = groupIdentifier)
Prove they own a destination account (that will receive the destination)
Make a claim about the value of the account inside the Group.
generate a userTicket that will be saved on-chain inside the attester.
The ticketIdentifier is defined as being the group identifier. This makes sure a user cannot generate two attestations per groups.
All these steps are executed inside the hydra-s1 circom circuit which is available here.