Because the SDK does not include issuer APIs, pre-generated sample data is included for validation purposes.
Issuers create groups and manage group membership. For each group, the issuer creates a group public key simultaneously with the corresponding issuing private key. The issuer uses the issuing private key to create unique member private keys for each group member, and makes the group public key available to verifiers.
All groups have the following:
If a signature based revocation list or private key based revocation list does not exist, it is assumed to be empty.
There are eight members in groupa:
groupa/privrl.bin
)groupa/privrl.bin
)groupa/privrl.bin
)groupa/sigrl.bin
)groupa/sigrl.bin
)groupa/sigrl.bin
)The following are groupa revocation lists:
groupa/privrl.bin
- Private-Key based revocation list. privrevokedmember0, privrevokedmember1 and privrevokedmember2** revoked.groupa/sigrl.bin
- Signature based revocation list. sigrevokedmember0, sigrevokedmember0 and sigrevokedmember0** revoked.There are four members in groupb:
groupb/privrl.bin
)groupb/sigrl.bin
)The following are groupb revocation lists:
groupb/privrl.bin
- Private-Key based revocation list. privrevokedmember0 revoked.groupb/sigrl.bin
- Signature based revocation list. sigrevokedmember0 revoked.If an entire group is no longer valid, the issuer can revoke it using the group based revocation list. Two sample group based revocation lists are provided with the SDK.
grprl_empty.bin
- No entriesgrprl.bin
- One entry in which groupb is revoked.