数据完整性 BBS 密码套件 v1.0

摘要

本规范描述了一种用于生成采用 BBS 签名方案的数字签名时使用的数据完整性密码套件。该签名套件利用 BBS 签名提供选择性披露和不可关联的派生证明。

以下算法描述了如何将可验证凭证与 BBS 签名方案 [CFRG-BBS-SIGNATURE] 一起使用。使用 BBS 签名方案时，应该使用 SHA-256 变体。

在添加或验证证明时，实现应该尽早获取并缓存验证方法信息。本节中传递给函数的参数使用来自验证方法的信息（例如公钥大小）来确定函数参数（例如密码哈希算法）。

使用 RDF 数据集规范化算法 [RDF-CANON] 时，该算法的实现默认会检测数据集投毒，并在检测到后中止处理。

此算法用于配置一个密码套件，供可验证凭证数据完整性 1.1中的添加证明和验证证明函数使用。该算法接受一个选项对象（映射 options）作为输入，并返回一个密码套件实例（结构体 cryptosuite）。

将 cryptosuite 初始化为空结构体。
如果 options.type 不等于 DataIntegrityProof，返回 cryptosuite。
如果 options.cryptosuite 为 bbs-2023，则：
1. 将 cryptosuite.createProof 设置为第 3.3.1 创建基础证明 (bbs-2023)节中的算法。
2. 将 cryptosuite.verifyProof 设置为第 3.3.5 验证派生证明 (bbs-2023)节中的算法。
返回 cryptosuite。

以下算法序列化基础证明值，其中包括 BBS 签名、HMAC 密钥和强制指针。必需的输入为基础签名 bbsSignature、bbsHeader、 publicKey、HMAC 密钥 hmacKey、一个 mandatoryPointers 数组、featureOption，以及根据 featureOption 的值，可能还包括 signer_nym_entropy 值。输出会生成单个基础证明字符串值。

根据 featureOption 的值，按如下方式设置 proofValue。
如果 featureOption 等于 "baseline"：
1. 初始化一个字节数组 proofValue，其起始内容为 BBS 基础证明头字节 0xd9、0x5d 和 0x02。
2. 将 components 初始化为包含以下五个元素值的数组： bbsSignature、bbsHeader、publicKey、hmacKey 和 mandatoryPointers。
如果 featureOption 等于 "anonymous_holder_binding"：
1. 初始化一个字节数组 proofValue，其起始内容为 BBS 基础证明头字节 0xd9、0x5d 和 0x04。
2. 将 components 初始化为包含以下六个元素值的数组： bbsSignature、bbsHeader、publicKey、hmacKey 和 mandatoryPointers。
如果 featureOption 等于 "pseudonym"：
1. 初始化一个字节数组 proofValue，其起始内容为 BBS 基础证明头字节 0xd9、0x5d 和 0x06。
2. 将 components 初始化为包含以下六个元素值的数组： bbsSignature、bbsHeader、publicKey、hmacKey、 mandatoryPointers 和 signer_nym_entropy。
如果 featureOption 等于 "holder_binding_pseudonym"：
1. 初始化一个字节数组 proofValue，其起始内容为 BBS 基础证明头字节 0xd9、0x5d 和 0x08。
2. 将 components 初始化为包含以下六个元素值的数组： bbsSignature、bbsHeader、publicKey、hmacKey、 mandatoryPointers 和 signer_nym_entropy。
按照 [RFC8949] 对 components 进行 CBOR 编码，其中对任何 components 不得使用 CBOR 标记。将生成的编码值附加到 proofValue。
将 baseProof 初始化为使用 proofValue 的 multibase-base64url-no-pad 编码得到的字符串。也就是说，返回一个以“u”开头并以 proofValue 的 base64url-no-pad 编码值结尾的字符串。
将 baseProof 作为基础证明返回。

以下算法解析 bbs-2023 选择性披露基础证明值的各个组成部分。必需的输入是一个证明值（proofValue）。输出会生成单个对象已解析基础证明，其中包含六个或七个元素，名称分别为 "bbsSignature"、"bbsHeader"、 "publicKey"、 "hmacKey"、"mandatoryPointers"、"featureOption"，以及可能存在的可选功能参数 "signer_nym_entropy"。

如果 proofValue 字符串不是以 u （U+0075 LATIN SMALL LETTER U）开头，表明它不是一个 multibase-base64url-no-pad-encoded 值，则必须引发错误，并且应该传达 PROOF_VERIFICATION_ERROR 错误类型。
将 decodedProofValue 初始化为对 proofValue 中前导 u 之后的子字符串进行 base64url-no-pad 解码的结果。
检查 BBS 基础证明是否以允许的头值开头，并按如下方式设置 featureOption 变量：
1. 如果 decodedProofValue 以字节 0xd9、 0x5d 和 0x02 开头，则将 featureOption 设置为 "baseline"。
2. 如果 decodedProofValue 以字节 0xd9、 0x5d 和 0x04 开头，则将 featureOption 设置为 "anonymous_holder_binding"。
3. 如果 decodedProofValue 以字节 0xd9、 0x5d 和 0x06 开头，则将 featureOption 设置为 "pseudonym"。
4. 如果 decodedProofValue 以字节 0xd9、 0x5d 和 0x08 开头，则将 featureOption 设置为 "holder_binding_pseudonym"。
5. 如果 decodedProofValue 以任何其他三字节序列开头，则必须引发错误，并且应该传达 PROOF_VERIFICATION_ERROR 错误类型。
将 components 初始化为一个数组，该数组是对三字节 BBS 基础证明头之后的字节进行 CBOR 解码的结果。
根据 featureOption 的值，基于 components 返回一个对象，如下所示：
1. 如果 featureOption 等于 "baseline"，则按顺序将基于 components 的对象属性名设置为 "bbsSignature"、"bbsHeader"、"publicKey"、"hmacKey" 和 "mandatoryPointers"，并添加 featureOption 作为属性。
2. 如果 featureOption 等于 "anonymous_holder_binding"，则将基于 components 的对象属性名按顺序设置为 "bbsSignature"、"bbsHeader"、 "publicKey"、"hmacKey" 和 "mandatoryPointers"，并添加 featureOption 作为属性。
3. 如果 featureOption 等于 "pseudonym"，则将基于 components 的对象属性名按顺序设置为 "bbsSignature"、"bbsHeader"、 "publicKey"、"hmacKey"、"mandatoryPointers" 和 "signer_nym_entropy"，并添加 featureOption 作为属性。
4. 如果 featureOption 等于 "holder_binding_pseudonym"，则将基于 components 的对象属性名按顺序设置为 "bbsSignature"、"bbsHeader"、 "publicKey"、"hmacKey"、"mandatoryPointers" 和 "signer_nym_entropy"，并添加 featureOption 作为属性。

以下算法序列化派生证明值。必需的输入为 BBS 证明（bbsProof）、标签映射（labelMap）、一个强制索引数组（mandatoryIndexes）、一个选择性索引数组（selectiveIndexes）、BBS 呈现头（presentationHeader）、featureOption 指示符，以及根据 featureOption 的值，一个 nym_domain、pseudonym 和/或 lengthBBSMessages 值。输出会生成单个派生证明 值，并将其序列化为字节字符串。

将 compressedLabelMap 初始化为调用第节中的算法并将 labelMap 作为参数传入所得的结果。
根据 featureOption 的值执行以下操作：
1. 如果 featureOption 等于 "baseline"：
  1. 将 proofValue 初始化为以披露证明头字节 0xd9、0x5d 和 0x03 开头。
  2. 将 components 初始化为包含以下值的元素数组： bbsProof、compressedLabelMap、mandatoryIndexes、 selectiveIndexes 和 presentationHeader。
2. 如果 featureOption 等于 "anonymous_holder_binding"：
  1. 将 proofValue 初始化为以披露证明头字节 0xd9、0x5d 和 0x05 开头。
  2. 将 components 初始化为包含以下值的元素数组： bbsProof、compressedLabelMap、mandatoryIndexes、 selectiveIndexes、 presentationHeader 和 lengthBBSMessages。
3. 如果 featureOption 等于 "pseudonym"：
  1. 将 proofValue 初始化为以披露证明头字节 0xd9、0x5d 和 0x07 开头。
  2. 将 components 初始化为包含以下值的元素数组： bbsProof、compressedLabelMap、mandatoryIndexes、 selectiveIndexes、 presentationHeader、nym_domain、pseudonym 和 lengthBBSMessages。
4. 如果 featureOption 等于 "holder_binding_pseudonym"：
  1. 将 proofValue 初始化为以披露证明头字节 0xd9、0x5d 和 0x09 开头。
  2. 将 components 初始化为包含以下值的元素数组： bbsProof、compressedLabelMap、mandatoryIndexes、 selectiveIndexes、 presentationHeader、nym_domain、pseudonym 和 lengthBBSMessages。
按照 [RFC8949] 对 components 进行 CBOR 编码，其中对任何 components 不得使用 CBOR 标记。将生成的编码值附加到 proofValue。
将派生证明作为使用 proofValue 的 multibase-base64url-no-pad 编码得到的字符串返回。也就是说，返回一个以“u”开头并以 proofValue 的 base64url-no-pad 编码值结尾的字符串。

以下算法解析派生证明值的各个组成部分。必需的输入是一个派生证明值（proofValue）。输出会生成单个派生证明值对象，其中包含六至九个元素，名称为 "bbsProof"、 "labelMap"、"mandatoryIndexes"、"selectiveIndexes"、"presentationHeader"、 "featureOption"，并且根据 featureOption 参数的值，还包括 "nym_domain"、"pseudonym" 和/或 "lengthBBSMessages"。

如果 proofValue 字符串不是以 u （U+0075， LATIN SMALL LETTER U）开头，表明它不是一个 multibase-base64url-no-pad-encoded 值，则必须引发错误，并且应该传达 PROOF_VERIFICATION_ERROR 错误类型。
将 decodedProofValue 初始化为对 proofValue 中前导 u 之后的子字符串进行 base64url-no-pad 解码的结果。
检查 BBS 披露证明是否以允许的头值开头，并按如下方式设置 featureOption 变量：
1. 如果 decodedProofValue 以头字节 0xd9、 0x5d 和 0x03 开头，则将 featureOption 设置为 "baseline"。
2. 如果 decodedProofValue 以头字节 0xd9、 0x5d 和 0x05 开头，则将 featureOption 设置为 "anonymous_holder_binding"。
3. 如果 decodedProofValue 以头字节 0xd9、 0x5d 和 0x07 开头，则将 featureOption 设置为 "pseudonym"。
4. 如果 decodedProofValue 以头字节 0xd9、 0x5d 和 0x09 开头，则将 featureOption 设置为 "holder_binding_pseudonym"。
将 components 初始化为一个数组，该数组是对三字节 BBS 披露证明头之后的字节进行 CBOR 解码的结果。如果该结果不是包含五个、六个、七个或八个元素的数组，则必须引发错误，并且应该传达 PROOF_VERIFICATION_ERROR 错误类型。
使用调用第节中的算法所得的结果替换 components 中的第二个元素，将 components 中现有的第二个元素作为 compressedLabelMap 传入。
将派生证明值作为一个对象返回，其属性分别设置为这五个、六个、七个或八个元素，并使用名称 "bbsProof"、"labelMap"、 "mandatoryIndexes"、"selectiveIndexes"、"presentationHeader"，以及可选的 "nym_domain"、"pseudonym" 和/或 "lengthBBSMessages"。此外，将 featureOption 及其值添加到该对象。

bbs-2023 密码套件接受一个输入文档，并使用 RDF 数据集规范化算法 [RDF-CANON] 对文档进行规范化，然后应用一系列转换和密码学操作，最终生成数据完整性证明。本节中的算法还包括对此类数据完整性证明的验证。

以下算法规定了在给定未保护数据文档的情况下如何创建数据完整性证明。必需的输入为一个未保护数据文档（映射 unsecuredDocument）、一组证明选项（映射 options）、一个强制 JSON 指针数组（mandatoryPointers）、一个 featureOption 指示符参数，以及根据 featureOption，一个 commitment_with_proof 字节数组。输出会生成一个数据完整性证明（映射）或一个错误。

featureOption 参数用于指示正在使用哪项可选功能（如果有）。它可以采用以下值之一："baseline"、 "anonymous_holder_binding"、"pseudonym" 或 "holder_binding_pseudonym"。请注意，"baseline" 用于表示不使用任何可选功能的情况。如果 featureOption 设置为 "anonymous_holder_binding"、"pseudonym" 或 "holder_binding_pseudonym"，则必须提供 commitment_with_proof 输入。如果 featureOption 设置为 "pseudonym" 或 "holder_binding_pseudonym"，则必须提供 signer_nym_entropy 输入。

令 proof 为证明选项 options 的克隆。
令 proofConfig 为运行 § 4.2.4.2 证明配置节中的算法并将 options 作为参数传入所得的结果。
令 transformedData 为运行 § 4.4.1 TransformSD 中的算法并将 unsecuredDocument、 proofConfig 和 options 作为参数传入所得的结果。
令 hashData 为运行 § 4.4.2 HashSD 中的算法并将 transformedData 和 proofConfig 作为参数传入所得的结果。
令 proofBytes 为运行第 3.3.2 基础证明序列化 (bbs-2023)节中的算法并将 hashData、 options、featureOption，以及在需要时将 commitment_with_proof 作为参数传入所得的结果。
令 proof.proofValue 为 proofBytes 的 base64url 编码的 Multibase 值。
将 proof 作为数据完整性证明返回。

以下算法由受 BBS 保护的可验证凭证的发行者调用，规定了如何创建基础证明。该基础证明只会提供给持有者，由持有者负责从中生成派生证明，并仅向验证者公开证明中选择性披露的详细信息。此算法设计为与数据完整性 [VC-DATA-INTEGRITY-1.1] 规范第 4 节：算法中定义的算法结合使用。必需的输入为密码哈希数据（hashData）、 featureOption，以及在需要时提供的 commitment_with_proof。如果 featureOption 设置为 "anonymous_holder_binding"、 "pseudonym" 或 "holder_binding_pseudonym"，则必须提供 commitment_with_proof 输入；如果未提供，则必须引发错误，并且应该传达 PROOF_GENERATION_ERROR 错误类型。如果 featureOption 设置为 "pseudonym" 或 "holder_binding_pseudonym"，则必须提供 signer_nym_entropy 输入；如果未提供，则必须引发错误，并且应该传达 PROOF_GENERATION_ERROR 错误类型。输出会生成一个以一系列字节表示的数字证明值。

将 proofHash、mandatoryPointers、mandatoryHash、 nonMandatory 和 hmacKey 初始化为 hashData 中与其属性名关联的值。
将 bbsHeader 初始化为依次连接 proofHash 和 mandatoryHash 所得的结果。
将 bbsMessages 初始化为一个字节数组的数组，其中包含使用 UTF-8 字符编码编码的 nonMandatory 字符串数组中的值。
根据 featureOption 的值，使用以下过程计算 bbsSignature。
1. 如果 featureOption 等于 "baseline"，则使用 [CFRG-BBS-Signature] 的 Sign 过程计算 bbsSignature，使用适当的密钥材料，将 bbsHeader 作为 header，并将 bbsMessages 作为 messages。
2. 如果 featureOption 等于 "anonymous_holder_binding"，则使用 [CFRG-Blind-BBS-Signature] 的 BlindSign 过程计算 bbsSignature，使用适当的密钥材料，将 commitment_with_proof 作为 commitment_with_proof，将 bbsHeader 作为 header，并将 bbsMessages 作为 messages。这提供匿名持有者绑定功能。
3. 如果 featureOption 等于 "pseudonym" 或 "holder_binding_pseudonym"，发行者会为 signer_nym_entropy 生成一个密码学随机值，并使用 [CFRG-Pseudonym-BBS-Signature] 中的 "Blind Issuance" 操作计算 bbsSignature，使用适当的密钥材料，将 bbsHeader 作为 header，将 bbsMessages 作为 messages，将 commitment_with_proof 作为 commitment_with_proof，以及 signer_nym_entropy 值。如果发行者将来可能需要向此持有者重新发行绑定到相同 nym_secret 的凭证，则应该保留 signer_nym_entropy 值；否则，可以丢弃该值。
  
  这提供凭证绑定的假名或持有者绑定和假名功能。
将 `proofValue 初始化为调用第 3.2.1 serializeBaseProofValue节中的算法所得的结果，将 bbsSignature、 bbsHeader、 publicKey、hmacKey、mandatoryPointers、 featureOption，以及根据 featureOption 的值将 signer_nym_entropy 作为参数传入。

注意：publicKey 是公钥的字节数组，按照 [CFRG-BBS-SIGNATURE] 进行编码。
将 proofValue 作为数字证明返回。

以下算法由受 bbs-2023 保护的可验证凭证的持有者调用，用于创建选择性披露派生证明。该派生证明将提供给验证者。输入包括一个 JSON-LD 文档（document）、一个 BBS 基础证明（proof）、一个用于选择性披露语句的 JSON 指针数组（selectivePointers）、一个可选的 BBS presentationHeader（字节数组）、一个 featureOption 参数、支持所选 featureOption 的附加参数（见下文），以及任何自定义 JSON-LD API 选项，例如文档加载器。输出会生成单个选择性公开的文档 值，以对象表示。

如果 featureOption 等于 "anonymous_holder_binding"， 必需的附加输入为 holderSecret 和 proverBlind。这些值应当已由持有者预先计算。有关背景信息，请参见匿名持有者绑定。

如果 featureOption 等于 "pseudonym"，必需的 附加输入为 prover_nym 和 proverBlind，两者均为持有者所知，以及 nym_dofmain，后者由持有者设置或由验证者传达给持有者。有关背景信息，请参见凭证绑定的假名。

如果 featureOption 等于 "holder_binding_pseudonym"，必需的 附加输入为 holder_secret、prover_nym 和 proverBlind，这些值均为持有者所知，以及 nym_dofmain，后者由持有者设置或由验证者传达给持有者。有关背景信息，请参见持有者绑定和假名。

令 proofData 对象为第 3.2.2 parseBaseProofValue节中的算法返回的结果。 proofData 对象至少会包含字段 bbsSignature、 bbsHeader、publicKey、hmacKey、mandatoryPointers 和 featureOption。根据 featureOption 的值，可能还会存在其他字段。
将 disclosureData 初始化为调用 § 4.4.3 CreateDisclosureData中的算法并传入 document、proofData、 selectivePointers 以及任何自定义 JSON-LD API 选项（例如文档加载器）时返回的对象。disclosureData 对象将包含以下字段： revealDocument、mandatoryIndexes、selectiveIndexes、 verifierLabelMap mandatory 和 nonMandatory。
将 newProof 初始化为 proof 的浅拷贝。
将 newProof 中的 proofValue 替换为调用第 3.3.4 派生证明序列化节中的算法，并将 proofData 和 disclosureData 作为参数传入所得的结果。
将 revealDocument 中 "proof" 属性的值设置为 newProof。
将 revealDocument 作为选择性公开的文档返回。

以下算法生成派生证明。输入为 proofData 和 disclosureData 对象。

将 bbsMessages 初始化为一个字节数组的数组，其中包含使用 UTF-8 字符编码编码的 nonMandatory 字符串数组中的值。
根据 featureOption 参数的值，将 bbsProof 设置为通过下面相应过程计算得到的值。
1. 如果 featureOption 等于 "baseline"，将 bbsProof 设置为通过 [CFRG-BBS-SIGNATURE] 中的 ProofGen 过程计算得到的值，即 ProofGen(PK, signature, header, ph, messages, disclosed_indexes)，其中 PK 是原始发行者的公钥，signature 是 bbsSignature，header 是 bbsHeader， ph 是 presentationHeader messages 是 bbsMessages，disclosed_indexes 是 selectiveIndexes。
2. 如果 featureOption 等于 "anonymous_holder_binding"，将 bbsProof 设置为通过 [CFRG-Blind-BBS-Signature] 中的 BlindProofGen 过程计算得到的值，其中 PK 是原始发行者的公钥， signature 是 bbsSignature，header 是 bbsHeader，ph 是 presentationHeader， messages 是 bbsMessages，disclosed_indexes 是 selectiveIndexes，以及 commitment_with_proof。持有者还将提供其 holder_secret，以及用于计算 commitment_with_proof 的 proverBlind。这是匿名持有者绑定功能选项。将在 IETF API 最终确定后更新。
3. 如果 featureOption 等于 "pseudonym"，使用 [CFRG-Pseudonym-BBS-Signature] 中的 "Verification and Finalization" 操作，并使用空的 committed_messages 数组，以同时验证 bbsSignature 并计算 nym_secret 值。此操作使用 prover_nym、 signer_nym_entropy 和 secret_prover_blind。
  
  确定 nym_domain。根据使用场景，它可能由验证者指定，也可能由持有者设置。使用 [CFRG-Pseudonym-BBS-Signature] 中的 "Proof Generation with Pseudonym" 操作来生成派生证明。此操作接受以下输入：将原始发行者的公钥作为 PK，将 bbsSignature 作为 signature，将 bbsHeader 作为 header，将 presentationHeader 作为 ph，将 bbsMessages 作为 messages，将 selectiveIndexes 作为 disclosed_indexes，一个 nym_secret，一个 nym_domain，一个用于 committed_messages 的空数组，以及一个 secret_prover_blind。除提供分配给 bbsProof 的原始密码证明值外，它还会返回 pseudonym。
  
  这是用于凭证绑定的假名功能选项。将在 IETF API 最终确定后更新。
4. 如果 featureOption 等于 "holder_binding_pseudonym"，使用 [CFRG-Pseudonym-BBS-Signature] 中的 "Verification and Finalization" 操作，并使用仅包含 holder_secret 作为其唯一值的 committed_messages 数组，以同时验证 bbsSignature 并计算 nym_secret 值。此操作使用 prover_nym、 signer_nym_entropy 和 secret_prover_blind。
  
  确定 nym_domain。根据使用场景，它可能由验证者指定或由持有者设置。使用 [CFRG-Pseudonym-BBS-Signature] 中的 "Proof Generation with Pseudonym" 操作来生成派生证明。此操作接受以下输入： PK，即原始发行者的公钥， signature，即 bbsSignature，header 是 bbsHeader， ph 是 presentationHeader， messages 是 bbsMessages，disclosed_indexes 是 selectiveIndexes，此操作接受以下输入：将原始发行者的公钥作为 PK，将 bbsSignature 作为 signature，将 bbsHeader 作为 header，将 presentationHeader 作为 ph，将 bbsMessages 作为 messages，将 selectiveIndexes 作为 disclosed_indexes，一个 nym_secret，一个 nym_domain，将 committed_messages 数组的唯一值作为 holder_secret，以及一个 secret_prover_blind。除提供分配给 bbsProof 的原始密码证明值外，它还会返回 pseudonym。这是用于持有者绑定和假名功能选项。将在 IETF API 最终确定后更新。
如果 featureOption 等于 "anonymous_holder_binding"、 "pseudonym" 或 "holder_binding_pseudonym"，则将 lengthBBSMessages 参数设置为 bbsMessages 数组的长度。
返回调用 3.2.3 serializeDerivedProofValue 算法所得的值，其参数分别对应 bbsProof、将 "verifierLabelMap" 作为 labelMap、 mandatoryIndexes、selectiveIndexes、revealDocument、 pseudonym，以及在已计算时传入 lengthBBSMessages。

以下算法规定了在给定受保护数据文档的情况下如何验证数据完整性证明。必需的输入为一个受保护数据文档（映射 securedDocument）。此算法返回一个验证结果，它是一个结构体，其项目为：

已验证: true 或 false
已验证文档: 如果已验证为 false，则为 Null；否则为一个未保护数据文档

要验证派生证明，请执行以下步骤：

令 unsecuredDocument 为移除 proof 值后的 document 副本。
将 proofData 对象初始化为 3.2.4 parseDerivedProofValue 算法返回的结果。 proofData 对象至少会包含字段 bbsProof、labelMap、mandatoryIndexes、 selectiveIndexes、 presentationHeader 和 featureOption。根据 featureOption 的值，它还可能包含字段 nym_domain、|pseudonym 和/或 lengthBBSMessages。"，分别如此。
将 verifyData 对象初始化为调用 § 4.4.4 CreateVerifyData节中的算法，并传入 document、proofData 以及任何自定义 JSON-LD API 选项（例如文档加载器）后返回的值。 verifyData 对象将包含以下字段：proofHash、 mandatoryHash 和 nonMandatory。
令 publicKeyBytes 为按照数据完整性 [VC-DATA-INTEGRITY-1.1] 规范第 4 节：检索验证方法中所述方式，检索与 proof.verificationMethod 值关联的公钥字节所得的结果。
将 bbsHeader 初始化为依次连接 proofHash 和 mandatoryHash 所得的结果。将 disclosedMessages 初始化为一个字节数组的数组，这些字节数组通过对 nonMandatory 数组中的元素进行 UTF-8 编码获得。
根据 featureOption 的值，将 verified 初始化为应用以下验证算法所得的结果。
1. 如果 featureOption 等于 "baseline"，则将 verified 初始化为应用 [CFRG-BBS-SIGNATURE] 的验证算法 ProofVerify(PK, proof, header, ph, disclosed_messages, disclosed_indexes)所得的结果，其中 PK 设置为原始发行者的公钥，proof 设置为 bbsProof，header 设置为 bbsHeader，disclosed_messages 设置为 disclosedMessages，ph 设置为 presentationHeader，并且 disclosed_indexes 设置为 selectiveIndexes。
2. 如果 featureOption 等于 "anonymous_holder_binding"，将 verified 初始化为应用 [CFRG-Blind-BBS-Signature] 的 ProofVerify 验证算法所得的结果，并将 lengthBBSMessages 用作 "L" 参数。将在 IETF API 最终确定后更新。
3. 如果 featureOption 等于 "pseudonym" 或 "holder_binding_pseudonym"，将 verified 初始化为应用 [CFRG-Pseudonym-BBS-Signature] 中的 "Proof Verification with Pseudonym" 操作所得的结果，将 lengthBBSMessages 用作 "L" 参数，并使用空的 committed_messages 数组。将在 IETF API 最终确定后更新。
返回一个验证结果，其中包含以下项目：

已验证

verified

已验证文档

如果 verified 为 true，则为 unsecuredDocument，否则为 Null

表 1 *颁发者创建基础证明：输入等。*
名称	任务	输入	签名算法
基线 BBS	baseline：根据 VC 生成 BBS 签名	baseline：文档、证明选项、密钥材料、强制指针	BBS
匿名持有者绑定	baseline	baseline + 来自持有者的带证明承诺	盲 BBS
凭据绑定假名	baseline + 生成 `signer_nym_entropy`	baseline + `signer_nym_entropy`、来自持有者的带证明承诺	假名 BBS
持有者绑定和假名	baseline + 生成 `signer_nym_entropy`	baseline + `signer_nym_entropy`、来自持有者的带证明承诺	假名 BBS

表 2 *颁发者创建基础证明：头和序列化。*
名称	证明头字节	序列化输出
基线 BBS	`0xd9`、`0x5d` 和 `0x02`	baseline：bbsSignature、bbsHeader、publicKey、hmacKey 和 mandatoryPointers
匿名持有者绑定	`0xd9`、`0x5d` 和 `0x04`	baseline
凭据绑定假名	`0xd9`、`0x5d` 和 `0x06`	baseline + `signer_nym_entropy`
持有者绑定和假名	`0xd9`、`0x5d` 和 `0x08`	baseline + `signer_nym_entropy`

表 3 *持有者添加派生证明：输入等。*
名称	任务	输入	证明生成算法
基线 BBS	根据带基础证明的 VC 生成 BBS 派生证明	baseline：（来自基础证明序列化） bbsSignature、bbsHeader、publicKey、hmacKey 和 mandatoryPointers；selectivePointers（持有者的选择）	BBS
匿名持有者绑定	baseline	baseline + `holder_secret`、`prover_blind`（二者均为持有者所知）	盲 BBS
凭据绑定假名	baseline + 计算 `nym_secret`、计算 `pseudonym`	baseline + `prover_nym`、 `prover_blind`（均为持有者所知）、`signer_nym_entropy` （包含在颁发者提供的基础证明中）、`nym_domain`	假名 BBS
持有者绑定和假名	baseline + 计算 `nym_secret`、计算 `pseudonym`	baseline + `holder_secret`、`prover_nym`、 `prover_blind`（均为持有者所知）、`signer_nym_entropy` （包含在颁发者提供的基础证明中）、`nym_domain`	假名 BBS

表 4 *持有者添加派生证明：头和序列化。*
名称	证明头字节	序列化输出
基线 BBS	`0xd9`、`0x5d` 和 `0x03`	baseline：bbsProof、compressedLabelMap、 mandatoryIndexes、selectiveIndexes、presentationHeader
匿名持有者绑定	`0xd9`、`0x5d` 和 `0x05`	baseline
凭据绑定假名	`0xd9`、`0x5d` 和 `0x07`	baseline + `pseudonym`、`nym_domain`
持有者绑定和假名	`0xd9`、`0x5d` 和 `0x09`	baseline + `pseudonym`、`nym_domain`

表 5 *验证派生证明：输入和算法。*
名称	输入	证明验证算法
BBS 基线	baseline：（来自派生证明序列化） bbsProof、compressedLabelMap、mandatoryIndexes、 selectiveIndexes、presentationHeader	BBS
匿名持有者绑定	baseline	盲 BBS
凭据绑定假名	baseline + `pseudonym`（包含在派生证明中）、 `nym_domain`	假名 BBS
持有者绑定和假名	baseline + `pseudonym`（包含在派生证明中）、 `nym_domain`	假名 BBS

本节为非规范性内容。

文档测试向量基于一张完全虚构的永久居民卡，并分为两组——由颁发者生成的那些（“基础证明”），以及由持有者生成的那些（“派生证明”）。

要向文档添加选择性披露基础证明，颁发者需要以下密码学密钥材料：

颁发者的私钥/公钥对，即与将成为证明一部分的验证方法相对应的密钥对。
一个 HMAC 密钥。它用于随机化空白节点 ID 的顺序，以避免通过空白节点 ID 顺序造成潜在的信息泄露。它仅使用一次，并由颁发者和持有者共享。在这种情况下，HMAC 充当伪随机函数（PRF）。

用于生成测试添加基础证明的测试向量所使用的密钥材料如下所示。BBS 密钥对和 HMAC 密钥使用十六进制表示。

示例 7：用于签名的私钥和公钥

{
  "publicKeyHex": "a4ef1afa3da575496f122b9b78b8c24761531a8a093206ae7c45b80759c168ba4f7a260f9c3367b6c019b4677841104b10665edbe70ba3ebe7d9cfbffbf71eb016f70abfbb163317f372697dc63efd21fc55764f63926a8f02eaea325a2a888f",
  "privateKeyHex": "66d36e118832af4c5e28b2dfe1b9577857e57b042a33e06bdea37b811ed09ee0",
  "hmacKeyString": "00112233445566778899AABBCCDDEEFF00112233445566778899AABBCCDDEEFF"
}

在我们的场景中，正在颁发永久居民凭证。未签名的永久居民文档如下所示。

示例 8：不含证明的凭证

{
    "@context": [
      "https://www.w3.org/ns/credentials/v2",
      "https://w3id.org/citizenship/v4rc1"
    ],
    "type": [
      "VerifiableCredential",
      "PermanentResidentCardCredential"
    ],
    "issuer": {
      "id": "did:key:zDnaeTHxNEBZoKaEo6PdA83fq98ebiFvo3X273Ydu4YmV96rg",
      "image": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVQIW2P4z/DiPwAG0ALnwgz64QAAAABJRU5ErkJggg=="
       },
    "name": "Permanent Resident Card",
    "description": "Government of Utopia Permanent Resident Card.",
    "credentialSubject": {
      "type": [
        "PermanentResident",
        "Person"
      ],
      "givenName": "JANE",
      "familyName": "SMITH",
      "gender": "Female",
      "image": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVQIW2P4v43hPwAHIgK1v4tX6wAAAABJRU5ErkJggg==",
      "residentSince": "2015-01-01",
      "commuterClassification": "C1",
      "birthCountry": "Arcadia",
      "birthDate": "1978-07-17",
      "permanentResidentCard": {
        "type": [
          "PermanentResidentCard"
        ],
        "identifier": "83627465",
        "lprCategory": "C09",
        "lprNumber": "999-999-999"
      }
    },
    "validFrom": "2024-12-16T00:00:00Z",
    "validUntil": "2025-12-16T23:59:59Z"
}

此强制信息通过 JSON 指针数组指定，如下所示。

示例 9：强制指针

["/issuer"]

将上述 JSON 指针应用于文档的结果如下所示。

示例 10：JSON 指针和值

[
  {
    "pointer": "/issuer",
    "value": {
      "id": "did:key:zDnaeTHxNEBZoKaEo6PdA83fq98ebiFvo3X273Ydu4YmV96rg",
      "image": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVQIW2P4z/DiPwAG0ALnwgz64QAAAABJRU5ErkJggg=="
    }
  }
]

未签名文档的转换从规范化文档开始，如下所示。

示例 11：规范文档

[
  "<did:key:zDnaeTHxNEBZoKaEo6PdA83fq98ebiFvo3X273Ydu4YmV96rg> <https://schema.org/image> <data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVQIW2P4z/DiPwAG0ALnwgz64QAAAABJRU5ErkJggg==> .\n",
  "_:c14n0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/citizenship#PermanentResidentCard> .\n",
  "_:c14n0 <https://schema.org/identifier> \"83627465\" .\n",
  "_:c14n0 <https://w3id.org/citizenship#lprCategory> \"C09\" .\n",
  "_:c14n0 <https://w3id.org/citizenship#lprNumber> \"999-999-999\" .\n",
  "_:c14n1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://schema.org/Person> .\n",
  "_:c14n1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/citizenship#PermanentResident> .\n",
  "_:c14n1 <https://schema.org/birthDate> \"1978-07-17\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:c14n1 <https://schema.org/familyName> \"SMITH\" .\n",
  "_:c14n1 <https://schema.org/gender> \"Female\" .\n",
  "_:c14n1 <https://schema.org/givenName> \"JANE\" .\n",
  "_:c14n1 <https://schema.org/image> <data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVQIW2P4v43hPwAHIgK1v4tX6wAAAABJRU5ErkJggg==> .\n",
  "_:c14n1 <https://w3id.org/citizenship#birthCountry> \"Arcadia\" .\n",
  "_:c14n1 <https://w3id.org/citizenship#commuterClassification> \"C1\" .\n",
  "_:c14n1 <https://w3id.org/citizenship#permanentResidentCard> _:c14n0 .\n",
  "_:c14n1 <https://w3id.org/citizenship#residentSince> \"2015-01-01\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:c14n2 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/citizenship#PermanentResidentCardCredential> .\n",
  "_:c14n2 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://www.w3.org/2018/credentials#VerifiableCredential> .\n",
  "_:c14n2 <https://schema.org/description> \"Permanent Resident Card from Government of Utopia.\" .\n",
  "_:c14n2 <https://schema.org/name> \"Permanent Resident Card\" .\n",
  "_:c14n2 <https://www.w3.org/2018/credentials#credentialSubject> _:c14n1 .\n",
  "_:c14n2 <https://www.w3.org/2018/credentials#issuer> <did:key:zDnaeTHxNEBZoKaEo6PdA83fq98ebiFvo3X273Ydu4YmV96rg> .\n",
  "_:c14n2 <https://www.w3.org/2018/credentials#validFrom> \"2024-12-16T00:00:00Z\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:c14n2 <https://www.w3.org/2018/credentials#validUntil> \"2025-12-16T23:59:59Z\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n"
]

为防止空白节点 ID 的顺序可能造成信息泄露，这些 ID 会通过 PRF（即 HMAC）处理，从而得到如下所示的规范化 HMAC 文档。这表示一个有序的语句列表，这些语句将接受“强制”和“选择性”（或“非强制”）披露，即当这些语句根据其披露要求进行分组时，它们仍将按照此列表中的顺序排列。

示例 12：规范 HMAC 文档

[
  "<did:key:zDnaeTHxNEBZoKaEo6PdA83fq98ebiFvo3X273Ydu4YmV96rg> <https://schema.org/image> <data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVQIW2P4z/DiPwAG0ALnwgz64QAAAABJRU5ErkJggg==> .\n",
  "_:b0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://schema.org/Person> .\n",
  "_:b0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/citizenship#PermanentResident> .\n",
  "_:b0 <https://schema.org/birthDate> \"1978-07-17\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:b0 <https://schema.org/familyName> \"SMITH\" .\n",
  "_:b0 <https://schema.org/gender> \"Female\" .\n",
  "_:b0 <https://schema.org/givenName> \"JANE\" .\n",
  "_:b0 <https://schema.org/image> <data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVQIW2P4v43hPwAHIgK1v4tX6wAAAABJRU5ErkJggg==> .\n",
  "_:b0 <https://w3id.org/citizenship#birthCountry> \"Arcadia\" .\n",
  "_:b0 <https://w3id.org/citizenship#commuterClassification> \"C1\" .\n",
  "_:b0 <https://w3id.org/citizenship#permanentResidentCard> _:b1 .\n",
  "_:b0 <https://w3id.org/citizenship#residentSince> \"2015-01-01\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:b1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/citizenship#PermanentResidentCard> .\n",
  "_:b1 <https://schema.org/identifier> \"83627465\" .\n",
  "_:b1 <https://w3id.org/citizenship#lprCategory> \"C09\" .\n",
  "_:b1 <https://w3id.org/citizenship#lprNumber> \"999-999-999\" .\n",
  "_:b2 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/citizenship#PermanentResidentCardCredential> .\n",
  "_:b2 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://www.w3.org/2018/credentials#VerifiableCredential> .\n",
  "_:b2 <https://schema.org/description> \"Permanent Resident Card from Government of Utopia.\" .\n",
  "_:b2 <https://schema.org/name> \"Permanent Resident Card\" .\n",
  "_:b2 <https://www.w3.org/2018/credentials#credentialSubject> _:b0 .\n",
  "_:b2 <https://www.w3.org/2018/credentials#issuer> <did:key:zDnaeTHxNEBZoKaEo6PdA83fq98ebiFvo3X273Ydu4YmV96rg> .\n",
  "_:b2 <https://www.w3.org/2018/credentials#validFrom> \"2024-12-16T00:00:00Z\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:b2 <https://www.w3.org/2018/credentials#validUntil> \"2025-12-16T23:59:59Z\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n"
]

上述规范文档中的列表会被分为强制和非强制语句。选择性披露转换过程的最终输出如下所示。请注意，这些语句现在被分组为强制披露或非强制披露，并且每条语句在前一列表中的索引都会被保留。

示例 13：添加基础证明转换

{
  "mandatoryPointers": [
    "/issuer"
  ],
  "mandatory": {
    "dataType": "Map",
    "value": [
      [
        0,
        "<did:key:zDnaeTHxNEBZoKaEo6PdA83fq98ebiFvo3X273Ydu4YmV96rg> <https://schema.org/image> <data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVQIW2P4z/DiPwAG0ALnwgz64QAAAABJRU5ErkJggg==> .\n"
      ],
      [
        16,
        "_:b2 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/citizenship#PermanentResidentCardCredential> .\n"
      ],
      [
        17,
        "_:b2 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://www.w3.org/2018/credentials#VerifiableCredential> .\n"
      ],
      [
        21,
        "_:b2 <https://www.w3.org/2018/credentials#issuer> <did:key:zDnaeTHxNEBZoKaEo6PdA83fq98ebiFvo3X273Ydu4YmV96rg> .\n"
      ]
    ]
  },
  "nonMandatory": {
    "dataType": "Map",
    "value": [
      [
        1,
        "_:b0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://schema.org/Person> .\n"
      ],
      [
        2,
        "_:b0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/citizenship#PermanentResident> .\n"
      ],
      [
        3,
        "_:b0 <https://schema.org/birthDate> \"1978-07-17\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n"
      ],
      [
        4,
        "_:b0 <https://schema.org/familyName> \"SMITH\" .\n"
      ],
      [
        5,
        "_:b0 <https://schema.org/gender> \"Female\" .\n"
      ],
      [
        6,
        "_:b0 <https://schema.org/givenName> \"JANE\" .\n"
      ],
      [
        7,
        "_:b0 <https://schema.org/image> <data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVQIW2P4v43hPwAHIgK1v4tX6wAAAABJRU5ErkJggg==> .\n"
      ],
      [
        8,
        "_:b0 <https://w3id.org/citizenship#birthCountry> \"Arcadia\" .\n"
      ],
      [
        9,
        "_:b0 <https://w3id.org/citizenship#commuterClassification> \"C1\" .\n"
      ],
      [
        10,
        "_:b0 <https://w3id.org/citizenship#permanentResidentCard> _:b1 .\n"
      ],
      [
        11,
        "_:b0 <https://w3id.org/citizenship#residentSince> \"2015-01-01\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n"
      ],
      [
        12,
        "_:b1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/citizenship#PermanentResidentCard> .\n"
      ],
      [
        13,
        "_:b1 <https://schema.org/identifier> \"83627465\" .\n"
      ],
      [
        14,
        "_:b1 <https://w3id.org/citizenship#lprCategory> \"C09\" .\n"
      ],
      [
        15,
        "_:b1 <https://w3id.org/citizenship#lprNumber> \"999-999-999\" .\n"
      ],
      [
        18,
        "_:b2 <https://schema.org/description> \"Permanent Resident Card from Government of Utopia.\" .\n"
      ],
      [
        19,
        "_:b2 <https://schema.org/name> \"Permanent Resident Card\" .\n"
      ],
      [
        20,
        "_:b2 <https://www.w3.org/2018/credentials#credentialSubject> _:b0 .\n"
      ],
      [
        22,
        "_:b2 <https://www.w3.org/2018/credentials#validFrom> \"2024-12-16T00:00:00Z\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n"
      ],
      [
        23,
        "_:b2 <https://www.w3.org/2018/credentials#validUntil> \"2025-12-16T23:59:59Z\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n"
      ]
    ]
  },
  "hmacKeyString": "00112233445566778899AABBCCDDEEFF00112233445566778899AABBCCDDEEFF"
}

下一步是创建基础证明配置并对其进行规范化。以下两个示例展示了这一过程。

示例 14：基础证明配置

{
  "type": "DataIntegrityProof",
  "cryptosuite": "bbs-2023",
  "created": "2023-08-15T23:36:38Z",
  "verificationMethod": "did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ",
  "proofPurpose": "assertionMethod",
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    "https://w3id.org/citizenship/v4rc1"
  ]
}

示例 15：规范基础证明配置

_:c14n0 <http://purl.org/dc/terms/created> "2023-08-15T23:36:38Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> .
_:c14n0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/security#DataIntegrityProof> .
_:c14n0 <https://w3id.org/security#cryptosuite> "bbs-2023"^^<https://w3id.org/security#cryptosuiteString> .
_:c14n0 <https://w3id.org/security#proofPurpose> <https://w3id.org/security#assertionMethod> .
_:c14n0 <https://w3id.org/security#verificationMethod> <did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ> .

在哈希步骤中，我们计算规范化证明选项的 SHA-256 哈希以生成 proofHash，并计算所有强制 N-Quads 的 JOIN 的 SHA-256 哈希以生成 mandatoryHash。它们以十六进制格式显示如下。

示例 16：添加基础证明哈希

{
  "proofHash": "3a5bbf25d34d90b18c35cd2357be6a6f42301e94fc9e52f77e93b773c5614bdf",
  "mandatoryHash": "8e7cc22c318dd2094e02d0bf06c5d73a5dba717611a40f6d1bedc5ea7c300fd6"
}

下面显示的是计算得到的十六进制 bbsSignature，以及 mandatoryPointers。它们与 hmacKey 一起提供给最终序列化步骤。

示例 17：添加基础证明签名

{
  "bbsSignature": "86168dd2b5d0c7c6a56a30f4212ed116a53def05d0d6708207d483c7ff2053aefa22d24ba7659d60852694f8d85be0fa2adc3974c7dc4cc68b3db17b2423975047104162c24502b41591879ac24f1bb1",
  "mandatoryPointers": [
    "/issuer"
  ]
}

最后，将上述值通过第 3.2.1 serializeBaseProofValue节的算法运行，以生成签名基础文档中使用的 proofValue，如下所示。

示例 18：已签名基础文档

{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    "https://w3id.org/citizenship/v4rc1"
  ],
  "type": [
    "VerifiableCredential",
    "PermanentResidentCardCredential"
  ],
  "issuer": {
    "id": "did:key:zDnaeTHxNEBZoKaEo6PdA83fq98ebiFvo3X273Ydu4YmV96rg",
    "image": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVQIW2P4z/DiPwAG0ALnwgz64QAAAABJRU5ErkJggg=="
  },
  "name": "Permanent Resident Card",
  "description": "Permanent Resident Card from Government of Utopia.",
  "credentialSubject": {
    "type": [
      "PermanentResident",
      "Person"
    ],
    "givenName": "JANE",
    "familyName": "SMITH",
    "gender": "Female",
    "image": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVQIW2P4v43hPwAHIgK1v4tX6wAAAABJRU5ErkJggg==",
    "residentSince": "2015-01-01",
    "commuterClassification": "C1",
    "birthCountry": "Arcadia",
    "birthDate": "1978-07-17",
    "permanentResidentCard": {
      "type": [
        "PermanentResidentCard"
      ],
      "identifier": "83627465",
      "lprCategory": "C09",
      "lprNumber": "999-999-999"
    }
  },
  "validFrom": "2024-12-16T00:00:00Z",
  "validUntil": "2025-12-16T23:59:59Z",
  "proof": {
    "type": "DataIntegrityProof",
    "cryptosuite": "bbs-2023",
    "created": "2023-08-15T23:36:38Z",
    "verificationMethod": "did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ",
    "proofPurpose": "assertionMethod",
    "proofValue": "u2V0ChVhQhhaN0rXQx8alajD0IS7RFqU97wXQ1nCCB9SDx_8gU676ItJLp2WdYIUmlPjYW-D6Ktw5dMfcTMaLPbF7JCOXUEcQQWLCRQK0FZGHmsJPG7FYQDpbvyXTTZCxjDXNI1e-am9CMB6U_J5S936Tt3PFYUvfjnzCLDGN0glOAtC_BsXXOl26cXYRpA9tG-3F6nwwD9ZYYKTvGvo9pXVJbxIrm3i4wkdhUxqKCTIGrnxFuAdZwWi6T3omD5wzZ7bAGbRneEEQSxBmXtvnC6Pr59nPv_v3HrAW9wq_uxYzF_NyaX3GPv0h_FV2T2OSao8C6uoyWiqIj1ggABEiM0RVZneImaq7zN3u_wARIjNEVWZ3iJmqu8zd7v-BZy9pc3N1ZXI"
  }
}

创建 BBS 证明时会使用随机数，并且可选的 presentationHeader 可以作为额外输入。为了提供一组确定性的测试向量，我们使用了 [CFRG-BBS-SIGNATURE] 中的模拟随机标量过程。我们用于生成派生证明测试向量的 seed 和 presentationHeader 值以十六进制给出如下。

示例 19：seed 和出示头值

{
  "presentationHeaderHex": "113377aa",
  "pseudoRandSeedHex": "332e313431353932363533353839373933323338343632363433333833323739"
}

要创建派生证明，持有者从一个包含基础证明的已签名文档开始。我们用于这些测试向量的基础文档是上面第 A.1.1 基础证明节中的最后一个示例。第一步是运行第 3.2.2 parseBaseProofValue节的算法，以恢复 bbsSignature、hmacKey 和 mandatoryPointers，如下所示。

示例 20：恢复的基础签名数据

{
  "bbsSignature": "86168dd2b5d0c7c6a56a30f4212ed116a53def05d0d6708207d483c7ff2053aefa22d24ba7659d60852694f8d85be0fa2adc3974c7dc4cc68b3db17b2423975047104162c24502b41591879ac24f1bb1",
  "hmacKey": "00112233445566778899aabbccddeeff00112233445566778899aabbccddeeff",
  "mandatoryPointers": [
    "/issuer"
  ]
}

接下来，持有者需要通过指定用于选择性披露的 JSON 指针，指明他们希望向验证者披露哪些非强制语句（如果有）。这些指针如下所示。

示例 21：选择性披露指针

["/validFrom", "/validUntil", "/credentialSubject/birthCountry"]

为生成 revealDocument（即最终将被签名并发送给验证者的未签名文档），我们将选择性指针追加到强制指针，并将这些组合指针连同不带证明的文档输入 [DI-ECDSA] 的 selectJsonLd 算法。得到如下结果。

示例 22：未签名披露文档

{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    "https://w3id.org/citizenship/v4rc1"
  ],
  "type": [
    "VerifiableCredential",
    "PermanentResidentCardCredential"
  ],
  "issuer": {
    "id": "did:key:zDnaeTHxNEBZoKaEo6PdA83fq98ebiFvo3X273Ydu4YmV96rg",
    "image": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVQIW2P4z/DiPwAG0ALnwgz64QAAAABJRU5ErkJggg=="
  },
  "validFrom": "2024-12-16T00:00:00Z",
  "validUntil": "2025-12-16T23:59:59Z",
  "credentialSubject": {
    "type": [
      "PermanentResident",
      "Person"
    ],
    "birthCountry": "Arcadia"
  }
}

既然我们已经知道了公开文档是什么样子，接下来就需要向验证者提供适当更新的信息，说明哪些语句是强制的，以及所选非强制语句的索引。运行 § 4.4.3 CreateDisclosureData 会生成大量关于相对于原始文档的各种语句组的信息。下面，我们展示这些组的一部分索引。

示例 23：派生组索引

{"combinedIndexes":[0,1,2,8,16,17,20,21,22,23],"mandatoryIndexes":[0,16,17,21],"nonMandatoryIndexes":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,18,19,20,22,23],"selectiveIndexes":[1,2,8,16,17,20,22,23]}

验证者需要能够聚合并哈希强制语句。为了实现这一点，我们向其提供强制语句的索引列表，并将其调整为这些语句在披露文档中的位置（即相对于 combinedIndexes），而 selectiveIndexes 则相对于它们在 nonMandatoryIndexes 中的位置进行调整。这些“调整后的”索引如下所示。

示例 24：调整后的强制和选择性索引

{"adjMandatoryIndexes":[0,4,5,7],"adjSelectiveIndexes":[0,1,7,17,18,19]}

最后一项重要的披露数据是 labelMap，它是从规范化空白节点 ID 到基于 HMAC 的打乱 ID 的映射，按照 § 4.4.3 CreateDisclosureData 计算得出。如下所示，同时还展示了除公开文档之外的其余披露数据。

示例 25：披露数据

{"bbsProof":"96ac5ff7b89bf2d8b0f3cc51c547f1a22b01e24e246579d212362cdf6bf0fabe18be0c9d1f84c904bb4c6c613fd0ecabb7ad92e615341da97a45a918721626cc859c455b473a36e39572561d5fc483c637424717a43dcffb3b130d8fe11f88a8802f3b231efe2444f8b47feded0b621e3d5cd22cb3ec23ebc4f6dca745b5c1ce2f42a710b92510a71225a7d39e00e0c26da2fae242cdf154e93de42017270b99023fe95b42c42a461a2eab19e04aa44839af39aa71f830162cb424a5aa0acc046dc7e7b8bdfc73cf3641c76aeeb7fbb56cd936776050dbd632bf7fc80d33c621dc6b837184ade619630f72bd25d8aea626ba994d15a65def1b0dc8af09c54a0cf5e5b54d1b1b28047aa2dbf63805fec9533bab46d12349ca47dfd83ff30454cedacd23da4eb9a3ebe198c80ac1992e2a203ffcf46afaa3482a63b7b00033df1a2da361d600a1cfd5139be010ca302e082af7ee34a5ff3d24cc7062f57fa36d47846edd5219e59bd438576bff709bfd7920d6bad8367b0fe8c749318ef8726beda9c1d9095bed738e4fd1c38333a27f4f2071a21a863671b43fe521f737444be865e887cbf33caa39226fb8013003721e37c6d949867befba1c8b7bf641bd647851ad92aed3da91af52f17d058a9f74eb30744304c05813840be6a528f54cd5a24b73ae2f42dec1bfc2e1354fb061a96c0df3ab96ddc9ada96cb882571cccb89774fcf0326e1c8b2b87cc4cf4eafbd75632518919cbe58a9f86ade12b0f6989c0886e358d801b99b1dd32c7e6e56a653c0e264a84b51d2d23679c75e282451af3bcaa6f19ec7bc3aa603fec87db5a57d42961e2907d899a8fd5d1ce17dde8a75cd1192494cd93b112da7774c2bb2f679f5b4b404dabe485d78a017b2be81e5ff8bacf90d5f24b2e83ab4169f8f55ca6f703141f91565abbec7445e6cf4663f5e34b9188283d57cedf36c586b18a130b83652436bf6862673ddeebd9aefdc2fbfc97dde80e36483491c4357ccd2fc131fb","labelMap":{"dataType":"Map","value":[["c14n0","b0"],["c14n1","b2"]]},"mandatoryIndexes":[0,4,5,7],"adjSelectiveIndexes":[0,1,7,17,18,19],"presentationHeader":{"0":17,"1":51,"2":119,"3":170}}

最后，将上述披露数据用于第 3.2.3 serializeDerivedProofValue节中的算法，我们将得到如下所示的已签名派生（公开）文档。

示例 26：已签名派生文档

{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    "https://w3id.org/citizenship/v4rc1"
  ],
  "type": [
    "VerifiableCredential",
    "PermanentResidentCardCredential"
  ],
  "issuer": {
    "id": "did:key:zDnaeTHxNEBZoKaEo6PdA83fq98ebiFvo3X273Ydu4YmV96rg",
    "image": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVQIW2P4z/DiPwAG0ALnwgz64QAAAABJRU5ErkJggg=="
  },
  "validFrom": "2024-12-16T00:00:00Z",
  "validUntil": "2025-12-16T23:59:59Z",
  "credentialSubject": {
    "type": [
      "PermanentResident",
      "Person"
    ],
    "birthCountry": "Arcadia"
  },
  "proof": {
    "type": "DataIntegrityProof",
    "cryptosuite": "bbs-2023",
    "created": "2023-08-15T23:36:38Z",
    "verificationMethod": "did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ",
    "proofPurpose": "assertionMethod",
    "proofValue": "u2V0DhVkC0JasX_e4m_LYsPPMUcVH8aIrAeJOJGV50hI2LN9r8Pq-GL4MnR-EyQS7TGxhP9Dsq7etkuYVNB2pekWpGHIWJsyFnEVbRzo245VyVh1fxIPGN0JHF6Q9z_s7Ew2P4R-IqIAvOyMe_iRE-LR_7e0LYh49XNIss-wj68T23KdFtcHOL0KnELklEKcSJafTngDgwm2i-uJCzfFU6T3kIBcnC5kCP-lbQsQqRhouqxngSqRIOa85qnH4MBYstCSlqgrMBG3H57i9_HPPNkHHau63-7Vs2TZ3YFDb1jK_f8gNM8Yh3GuDcYSt5hljD3K9Jdiupia6mU0Vpl3vGw3IrwnFSgz15bVNGxsoBHqi2_Y4Bf7JUzurRtEjScpH39g_8wRUztrNI9pOuaPr4ZjICsGZLiogP_z0avqjSCpjt7AAM98aLaNh1gChz9UTm-AQyjAuCCr37jSl_z0kzHBi9X-jbUeEbt1SGeWb1DhXa_9wm_15INa62DZ7D-jHSTGO-HJr7anB2Qlb7XOOT9HDgzOif08gcaIahjZxtD_lIfc3REvoZeiHy_M8qjkib7gBMANyHjfG2UmGe--6HIt79kG9ZHhRrZKu09qRr1LxfQWKn3TrMHRDBMBYE4QL5qUo9UzVoktzri9C3sG_wuE1T7BhqWwN86uW3cmtqWy4glcczLiXdPzwMm4ciyuHzEz06vvXVjJRiRnL5Yqfhq3hKw9picCIbjWNgBuZsd0yx-blamU8DiZKhLUdLSNnnHXigkUa87yqbxnse8OqYD_sh9taV9QpYeKQfYmaj9XRzhfd6Kdc0RkklM2TsRLad3TCuy9nn1tLQE2r5IXXigF7K-geX_i6z5DV8ksug6tBafj1XKb3AxQfkVZau-x0RebPRmP140uRiCg9V87fNsWGsYoTC4NlJDa_aGJnPd7r2a79wvv8l93oDjZINJHENXzNL8Ex-6IAAAEChAAEBQeGAAEHERITRBEzd6o"
  }
}

演示包括强制披露、选择性披露及二者重叠在内的选择性披露功能，需要一个比之前测试向量包含更多内容的输入凭证文档。为避免测试向量过长，起始文档测试向量基于一个完全虚构的风帆冲浪（帆船）比赛场景。此外，我们将测试向量分为两组，分别对应由颁发者生成的那些（基础证明）和由持有者生成的那些（派生证明）。

要向文档添加选择性披露基础证明，颁发者需要以下密码学密钥材料：

颁发者的私钥/公钥对，即与将成为证明一部分的验证方法相对应的密钥对。
一个 HMAC 密钥。它用于随机化空白节点 ID 的顺序，以避免通过空白节点 ID 顺序造成潜在的信息泄露。它仅使用一次，并由颁发者和持有者共享。在这种情况下，HMAC 充当伪随机函数（PRF）。

用于生成测试添加基础证明的测试向量所使用的密钥材料如下所示。BBS 密钥对和 HMAC 密钥使用十六进制表示。

示例 27：用于签名的私钥和公钥

{
  "publicKeyHex": "a4ef1afa3da575496f122b9b78b8c24761531a8a093206ae7c45b80759c168ba4f7a260f9c3367b6c019b4677841104b10665edbe70ba3ebe7d9cfbffbf71eb016f70abfbb163317f372697dc63efd21fc55764f63926a8f02eaea325a2a888f",
  "privateKeyHex": "66d36e118832af4c5e28b2dfe1b9577857e57b042a33e06bdea37b811ed09ee0",
  "hmacKeyString": "00112233445566778899AABBCCDDEEFF00112233445566778899AABBCCDDEEFF"
}

在我们的场景中，一名帆船运动员正在向赛事组织者报名参加将在毛伊岛连续多天举行的一系列风帆冲浪比赛。组织者将检查该运动员的装备，以证明其申报内容准确无误。该运动员未签名的装备清单如下所示。

示例 28：不含证明的凭证

{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    {
      "@vocab": "https://windsurf.grotto-networking.com/selective#"
    }
  ],
  "type": [
    "VerifiableCredential"
  ],
  "issuer": "https://vc.example/windsurf/racecommittee",
  "credentialSubject": {
    "sailNumber": "Earth101",
    "sails": [
      {
        "size": 5.5,
        "sailName": "Kihei",
        "year": 2023
      },
      {
        "size": 6.1,
        "sailName": "Lahaina",
        "year": 2023
      },
      {
        "size": 7.0,
        "sailName": "Lahaina",
        "year": 2020
      },
      {
        "size": 7.8,
        "sailName": "Lahaina",
        "year": 2023
      }
    ],
    "boards": [
      {
        "boardName": "CompFoil170",
        "brand": "Wailea",
        "year": 2022
      },
      {
        "boardName": "Kanaha Custom",
        "brand": "Wailea",
        "year": 2019
      }
    ]
  }
}

除了让其他运动员了解竞争对手可能使用何种装备之外，每位运动员还必须披露其最新风帆冲浪板的年份以及其中两张帆的完整详情。请注意，所有运动员均通过印在其所有装备上的帆号进行标识。此强制信息通过 JSON 指针数组指定，如下所示。

示例 29：强制指针

["/issuer", "/credentialSubject/sailNumber", "/credentialSubject/sails/1", "/credentialSubject/boards/0/year", "/credentialSubject/sails/2"]

将上述 JSON 指针应用于该运动员装备文档的结果如下所示。

示例 30：JSON 指针和值

[
  {
    "pointer": "/sailNumber",
    "value": "Earth101"
  },
  {
    "pointer": "/sails/1",
    "value": {
      "size": 6.1,
      "sailName": "Lahaina",
      "year": 2023
    }
  },
  {
    "pointer": "/boards/0/year",
    "value": 2022
  },
  {
    "pointer": "/sails/2",
    "value": {
      "size": 7,
      "sailName": "Lahaina",
      "year": 2020
    }
  }
]

未签名文档的转换从规范化文档开始，如下所示。

示例 31：规范文档

[
  "_:c14n0 <https://windsurf.grotto-networking.com/selective#boardName> \"CompFoil170\" .\n",
  "_:c14n0 <https://windsurf.grotto-networking.com/selective#brand> \"Wailea\" .\n",
  "_:c14n0 <https://windsurf.grotto-networking.com/selective#year> \"2022\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n",
  "_:c14n1 <https://windsurf.grotto-networking.com/selective#sailName> \"Lahaina\" .\n",
  "_:c14n1 <https://windsurf.grotto-networking.com/selective#size> \"7.8E0\"^^<http://www.w3.org/2001/XMLSchema#double> .\n",
  "_:c14n1 <https://windsurf.grotto-networking.com/selective#year> \"2023\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n",
  "_:c14n2 <https://windsurf.grotto-networking.com/selective#boardName> \"Kanaha Custom\" .\n",
  "_:c14n2 <https://windsurf.grotto-networking.com/selective#brand> \"Wailea\" .\n",
  "_:c14n2 <https://windsurf.grotto-networking.com/selective#year> \"2019\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n",
  "_:c14n3 <https://windsurf.grotto-networking.com/selective#sailName> \"Lahaina\" .\n",
  "_:c14n3 <https://windsurf.grotto-networking.com/selective#size> \"7\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n",
  "_:c14n3 <https://windsurf.grotto-networking.com/selective#year> \"2020\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n",
  "_:c14n4 <https://windsurf.grotto-networking.com/selective#sailName> \"Kihei\" .\n",
  "_:c14n4 <https://windsurf.grotto-networking.com/selective#size> \"5.5E0\"^^<http://www.w3.org/2001/XMLSchema#double> .\n",
  "_:c14n4 <https://windsurf.grotto-networking.com/selective#year> \"2023\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n",
  "_:c14n5 <https://windsurf.grotto-networking.com/selective#boards> _:c14n0 .\n",
  "_:c14n5 <https://windsurf.grotto-networking.com/selective#boards> _:c14n2 .\n",
  "_:c14n5 <https://windsurf.grotto-networking.com/selective#sailNumber> \"Earth101\" .\n",
  "_:c14n5 <https://windsurf.grotto-networking.com/selective#sails> _:c14n1 .\n",
  "_:c14n5 <https://windsurf.grotto-networking.com/selective#sails> _:c14n3 .\n",
  "_:c14n5 <https://windsurf.grotto-networking.com/selective#sails> _:c14n4 .\n",
  "_:c14n5 <https://windsurf.grotto-networking.com/selective#sails> _:c14n6 .\n",
  "_:c14n6 <https://windsurf.grotto-networking.com/selective#sailName> \"Lahaina\" .\n",
  "_:c14n6 <https://windsurf.grotto-networking.com/selective#size> \"6.1E0\"^^<http://www.w3.org/2001/XMLSchema#double> .\n",
  "_:c14n6 <https://windsurf.grotto-networking.com/selective#year> \"2023\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n",
  "_:c14n7 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://www.w3.org/2018/credentials#VerifiableCredential> .\n",
  "_:c14n7 <https://www.w3.org/2018/credentials#credentialSubject> _:c14n5 .\n",
  "_:c14n7 <https://www.w3.org/2018/credentials#issuer> <https://vc.example/windsurf/racecommittee> .\n"
]

为防止空白节点 ID 的顺序可能造成信息泄露，这些 ID 会通过 PRF（即 HMAC）处理，从而得到如下所示的规范化 HMAC 文档。这表示一个将接受强制和选择性披露的有序语句列表，即语句会从此列表中进行分组。

示例 32：规范 HMAC 文档

[
  "_:b0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://www.w3.org/2018/credentials#VerifiableCredential> .\n",
  "_:b0 <https://www.w3.org/2018/credentials#credentialSubject> _:b3 .\n",
  "_:b0 <https://www.w3.org/2018/credentials#issuer> <https://vc.example/windsurf/racecommittee> .\n",
  "_:b1 <https://windsurf.grotto-networking.com/selective#sailName> \"Lahaina\" .\n",
  "_:b1 <https://windsurf.grotto-networking.com/selective#size> \"7.8E0\"^^<http://www.w3.org/2001/XMLSchema#double> .\n",
  "_:b1 <https://windsurf.grotto-networking.com/selective#year> \"2023\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n",
  "_:b2 <https://windsurf.grotto-networking.com/selective#boardName> \"CompFoil170\" .\n",
  "_:b2 <https://windsurf.grotto-networking.com/selective#brand> \"Wailea\" .\n",
  "_:b2 <https://windsurf.grotto-networking.com/selective#year> \"2022\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n",
  "_:b3 <https://windsurf.grotto-networking.com/selective#boards> _:b2 .\n",
  "_:b3 <https://windsurf.grotto-networking.com/selective#boards> _:b4 .\n",
  "_:b3 <https://windsurf.grotto-networking.com/selective#sailNumber> \"Earth101\" .\n",
  "_:b3 <https://windsurf.grotto-networking.com/selective#sails> _:b1 .\n",
  "_:b3 <https://windsurf.grotto-networking.com/selective#sails> _:b5 .\n",
  "_:b3 <https://windsurf.grotto-networking.com/selective#sails> _:b6 .\n",
  "_:b3 <https://windsurf.grotto-networking.com/selective#sails> _:b7 .\n",
  "_:b4 <https://windsurf.grotto-networking.com/selective#boardName> \"Kanaha Custom\" .\n",
  "_:b4 <https://windsurf.grotto-networking.com/selective#brand> \"Wailea\" .\n",
  "_:b4 <https://windsurf.grotto-networking.com/selective#year> \"2019\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n",
  "_:b5 <https://windsurf.grotto-networking.com/selective#sailName> \"Kihei\" .\n",
  "_:b5 <https://windsurf.grotto-networking.com/selective#size> \"5.5E0\"^^<http://www.w3.org/2001/XMLSchema#double> .\n",
  "_:b5 <https://windsurf.grotto-networking.com/selective#year> \"2023\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n",
  "_:b6 <https://windsurf.grotto-networking.com/selective#sailName> \"Lahaina\" .\n",
  "_:b6 <https://windsurf.grotto-networking.com/selective#size> \"6.1E0\"^^<http://www.w3.org/2001/XMLSchema#double> .\n",
  "_:b6 <https://windsurf.grotto-networking.com/selective#year> \"2023\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n",
  "_:b7 <https://windsurf.grotto-networking.com/selective#sailName> \"Lahaina\" .\n",
  "_:b7 <https://windsurf.grotto-networking.com/selective#size> \"7\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n",
  "_:b7 <https://windsurf.grotto-networking.com/selective#year> \"2020\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n"
]

上述规范文档会被分为强制和非强制语句。选择性披露转换过程的最终输出如下所示。现在每条语句都被分组为强制或非强制，并且其在前一个语句列表中的索引都会被保留。

示例 33：添加基础证明转换

{
  "mandatoryPointers": [
    "/issuer",
    "/credentialSubject/sailNumber",
    "/credentialSubject/sails/1",
    "/credentialSubject/boards/0/year",
    "/credentialSubject/sails/2"
  ],
  "mandatory": {
    "dataType": "Map",
    "value": [
      [
        0,
        "_:b0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://www.w3.org/2018/credentials#VerifiableCredential> .\n"
      ],
      [
        1,
        "_:b0 <https://www.w3.org/2018/credentials#credentialSubject> _:b3 .\n"
      ],
      [
        2,
        "_:b0 <https://www.w3.org/2018/credentials#issuer> <https://vc.example/windsurf/racecommittee> .\n"
      ],
      [
        8,
        "_:b2 <https://windsurf.grotto-networking.com/selective#year> \"2022\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n"
      ],
      [
        9,
        "_:b3 <https://windsurf.grotto-networking.com/selective#boards> _:b2 .\n"
      ],
      [
        11,
        "_:b3 <https://windsurf.grotto-networking.com/selective#sailNumber> \"Earth101\" .\n"
      ],
      [
        14,
        "_:b3 <https://windsurf.grotto-networking.com/selective#sails> _:b6 .\n"
      ],
      [
        15,
        "_:b3 <https://windsurf.grotto-networking.com/selective#sails> _:b7 .\n"
      ],
      [
        22,
        "_:b6 <https://windsurf.grotto-networking.com/selective#sailName> \"Lahaina\" .\n"
      ],
      [
        23,
        "_:b6 <https://windsurf.grotto-networking.com/selective#size> \"6.1E0\"^^<http://www.w3.org/2001/XMLSchema#double> .\n"
      ],
      [
        24,
        "_:b6 <https://windsurf.grotto-networking.com/selective#year> \"2023\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n"
      ],
      [
        25,
        "_:b7 <https://windsurf.grotto-networking.com/selective#sailName> \"Lahaina\" .\n"
      ],
      [
        26,
        "_:b7 <https://windsurf.grotto-networking.com/selective#size> \"7\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n"
      ],
      [
        27,
        "_:b7 <https://windsurf.grotto-networking.com/selective#year> \"2020\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n"
      ]
    ]
  },
  "nonMandatory": {
    "dataType": "Map",
    "value": [
      [
        3,
        "_:b1 <https://windsurf.grotto-networking.com/selective#sailName> \"Lahaina\" .\n"
      ],
      [
        4,
        "_:b1 <https://windsurf.grotto-networking.com/selective#size> \"7.8E0\"^^<http://www.w3.org/2001/XMLSchema#double> .\n"
      ],
      [
        5,
        "_:b1 <https://windsurf.grotto-networking.com/selective#year> \"2023\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n"
      ],
      [
        6,
        "_:b2 <https://windsurf.grotto-networking.com/selective#boardName> \"CompFoil170\" .\n"
      ],
      [
        7,
        "_:b2 <https://windsurf.grotto-networking.com/selective#brand> \"Wailea\" .\n"
      ],
      [
        10,
        "_:b3 <https://windsurf.grotto-networking.com/selective#boards> _:b4 .\n"
      ],
      [
        12,
        "_:b3 <https://windsurf.grotto-networking.com/selective#sails> _:b1 .\n"
      ],
      [
        13,
        "_:b3 <https://windsurf.grotto-networking.com/selective#sails> _:b5 .\n"
      ],
      [
        16,
        "_:b4 <https://windsurf.grotto-networking.com/selective#boardName> \"Kanaha Custom\" .\n"
      ],
      [
        17,
        "_:b4 <https://windsurf.grotto-networking.com/selective#brand> \"Wailea\" .\n"
      ],
      [
        18,
        "_:b4 <https://windsurf.grotto-networking.com/selective#year> \"2019\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n"
      ],
      [
        19,
        "_:b5 <https://windsurf.grotto-networking.com/selective#sailName> \"Kihei\" .\n"
      ],
      [
        20,
        "_:b5 <https://windsurf.grotto-networking.com/selective#size> \"5.5E0\"^^<http://www.w3.org/2001/XMLSchema#double> .\n"
      ],
      [
        21,
        "_:b5 <https://windsurf.grotto-networking.com/selective#year> \"2023\"^^<http://www.w3.org/2001/XMLSchema#integer> .\n"
      ]
    ]
  },
  "hmacKeyString": "00112233445566778899AABBCCDDEEFF00112233445566778899AABBCCDDEEFF"
}

下一步是创建基础证明配置并对其进行规范化。以下两个示例展示了这一过程。

示例 34：基础证明配置

{
  "type": "DataIntegrityProof",
  "cryptosuite": "bbs-2023",
  "created": "2023-08-15T23:36:38Z",
  "verificationMethod": "did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ",
  "proofPurpose": "assertionMethod",
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    {
      "@vocab": "https://windsurf.grotto-networking.com/selective#"
    }
  ]
}

示例 35：规范基础证明配置

_:c14n0 <http://purl.org/dc/terms/created> "2023-08-15T23:36:38Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> .
_:c14n0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/security#DataIntegrityProof> .
_:c14n0 <https://w3id.org/security#cryptosuite> "bbs-2023"^^<https://w3id.org/security#cryptosuiteString> .
_:c14n0 <https://w3id.org/security#proofPurpose> <https://w3id.org/security#assertionMethod> .
_:c14n0 <https://w3id.org/security#verificationMethod> <did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ> .

在哈希步骤中，我们计算规范化证明选项的 SHA-256 哈希以生成 proofHash，并计算所有强制 N-Quads 拼接结果的 SHA-256 哈希以生成 mandatoryHash。它们以十六进制格式显示如下。

示例 36：添加基础证明哈希

{
  "proofHash": "3a5bbf25d34d90b18c35cd2357be6a6f42301e94fc9e52f77e93b773c5614bdf",
  "mandatoryHash": "555de05f898817e31301bac187d0c3ff2b03e2cbdb4adb4d568c17de961f9a18"
}

下面显示的是计算得到的十六进制 bbsSignature，以及 mandatoryPointers。它们与 hmacKey 一起提供给最终序列化步骤。

示例 37：添加基础证明签名

{
  "bbsSignature": "8331f55ad458fe5c322420b2cb806f9a20ea6b2b8a29d51710026d71ace5da080064b488818efc75a439525bd031450822a6a332da781926e19360b90166431124efcf3d060fbc750c6122c714c07f71",
  "mandatoryPointers": [
    "/issuer",
    "/credentialSubject/sailNumber",
    "/credentialSubject/sails/1",
    "/credentialSubject/boards/0/year",
    "/credentialSubject/sails/2"
  ]
}

最后，将上述值通过第 3.2.1 serializeBaseProofValue节的算法运行，以生成如下所示的签名基础文档中使用的 proofValue。

示例 38：已签名基础文档

{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    {
      "@vocab": "https://windsurf.grotto-networking.com/selective#"
    }
  ],
  "type": [
    "VerifiableCredential"
  ],
  "issuer": "https://vc.example/windsurf/racecommittee",
  "credentialSubject": {
    "sailNumber": "Earth101",
    "sails": [
      {
        "size": 5.5,
        "sailName": "Kihei",
        "year": 2023
      },
      {
        "size": 6.1,
        "sailName": "Lahaina",
        "year": 2023
      },
      {
        "size": 7,
        "sailName": "Lahaina",
        "year": 2020
      },
      {
        "size": 7.8,
        "sailName": "Lahaina",
        "year": 2023
      }
    ],
    "boards": [
      {
        "boardName": "CompFoil170",
        "brand": "Wailea",
        "year": 2022
      },
      {
        "boardName": "Kanaha Custom",
        "brand": "Wailea",
        "year": 2019
      }
    ]
  },
  "proof": {
    "type": "DataIntegrityProof",
    "cryptosuite": "bbs-2023",
    "created": "2023-08-15T23:36:38Z",
    "verificationMethod": "did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ",
    "proofPurpose": "assertionMethod",
    "proofValue": "u2V0ChVhQgzH1WtRY_lwyJCCyy4BvmiDqayuKKdUXEAJtcazl2ggAZLSIgY78daQ5UlvQMUUIIqajMtp4GSbhk2C5AWZDESTvzz0GD7x1DGEixxTAf3FYQDpbvyXTTZCxjDXNI1e-am9CMB6U_J5S936Tt3PFYUvfVV3gX4mIF-MTAbrBh9DD_ysD4svbSttNVowX3pYfmhhYYKTvGvo9pXVJbxIrm3i4wkdhUxqKCTIGrnxFuAdZwWi6T3omD5wzZ7bAGbRneEEQSxBmXtvnC6Pr59nPv_v3HrAW9wq_uxYzF_NyaX3GPv0h_FV2T2OSao8C6uoyWiqIj1ggABEiM0RVZneImaq7zN3u_wARIjNEVWZ3iJmqu8zd7v-FZy9pc3N1ZXJ4HS9jcmVkZW50aWFsU3ViamVjdC9zYWlsTnVtYmVyeBovY3JlZGVudGlhbFN1YmplY3Qvc2FpbHMvMXggL2NyZWRlbnRpYWxTdWJqZWN0L2JvYXJkcy8wL3llYXJ4Gi9jcmVkZW50aWFsU3ViamVjdC9zYWlscy8y"
  }
}

创建 BBS 证明时会使用随机数，并且可选的 presentationHeader 可以作为输入。为了提供一组确定性的测试向量，我们使用了 [CFRG-BBS-SIGNATURE] 中的模拟随机标量过程。我们用于生成派生证明测试向量的 seed 和 presentationHeader 值以十六进制给出如下。

示例 39：seed 和出示头值

{
  "presentationHeaderHex": "113377aa",
  "pseudoRandSeedHex": "332e313431353932363533353839373933323338343632363433333833323739"
}

示例 40：恢复的基础签名数据

{
  "bbsSignature": "8331f55ad458fe5c322420b2cb806f9a20ea6b2b8a29d51710026d71ace5da080064b488818efc75a439525bd031450822a6a332da781926e19360b90166431124efcf3d060fbc750c6122c714c07f71",
  "hmacKey": "00112233445566778899aabbccddeeff00112233445566778899aabbccddeeff",
  "mandatoryPointers": [
    "/issuer",
    "/credentialSubject/sailNumber",
    "/credentialSubject/sails/1",
    "/credentialSubject/boards/0/year",
    "/credentialSubject/sails/2"
  ]
}

接下来，持有者需要通过指定用于选择性披露的 JSON 指针，指明还希望向验证者披露哪些内容（如果有）。在我们的风帆冲浪比赛场景中，一名运动员（持有者）刚刚完成第一天的比赛，并希望向公众（验证者）披露其在比赛中使用的所有风帆冲浪板的详细信息。这些如下所示。请注意，这与强制披露信息略有重叠，后者只包含其最新冲浪板的年份。

示例 41：选择性披露指针

["/credentialSubject/boards/0", "/credentialSubject/boards/1"]

为生成 revealDocument（即最终将被签名并发送给验证者的未签名文档），我们将选择性指针追加到强制指针，并将这些组合指针连同不带证明的文档输入 [DI-ECDSA] 的 selectJsonLd 算法，得到如下结果。

示例 42：未签名披露文档

{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    {
      "@vocab": "https://windsurf.grotto-networking.com/selective#"
    }
  ],
  "type": [
    "VerifiableCredential"
  ],
  "issuer": "https://vc.example/windsurf/racecommittee",
  "credentialSubject": {
    "sailNumber": "Earth101",
    "sails": [
      {
        "size": 6.1,
        "sailName": "Lahaina",
        "year": 2023
      },
      {
        "size": 7,
        "sailName": "Lahaina",
        "year": 2020
      }
    ],
    "boards": [
      {
        "year": 2022,
        "boardName": "CompFoil170",
        "brand": "Wailea"
      },
      {
        "boardName": "Kanaha Custom",
        "brand": "Wailea",
        "year": 2019
      }
    ]
  }
}

既然我们已经知道了公开文档是什么样子，就需要向验证者提供适当更新的信息，说明哪些语句是强制的，以及所选非强制语句的索引。运行 § 4.4.3 CreateDisclosureData 会生成大量关于相对于原始文档的各种语句组的信息。下面我们展示这些组的一部分索引。

示例 43：派生组索引

{
    "combinedIndexes":[0,1,2,6,7,8,9,10,11,14,15,16,17,18,22,23,24,25,26,27],
    "mandatoryIndexes":[0,1,2,8,9,11,14,15,22,23,24,25,26,27],
    "nonMandatoryIndexes":[3,4,5,6,7,10,12,13,16,17,18,19,20,21],
    "selectiveIndexes":[0,1,6,7,8,9,10,16,17,18]
}

验证者需要能够聚合并哈希强制语句。为了实现这一点，我们向其提供强制语句的索引列表，并将其调整为这些语句在披露文档中的位置（即相对于 combinedIndexes），而 selectiveIndexes 需要相对于它们在 nonMandatoryIndexes 中的位置进行调整。这些“调整后的”索引如下所示。

示例 44：调整后的强制和选择性索引

{
    "adjMandatoryIndexes":[0,1,2,5,6,8,9,10,14,15,16,17,18,19],
    "adjSelectiveIndexes":[3,4,5,8,9,10]
}

最后一项重要的披露数据是从规范空白节点 ID 到基于 HMAC 的打乱 ID 的映射，即 labelMap，它按照第 § 4.4.3 CreateDisclosureData节计算得出。如下所示，同时还展示了除公开文档之外的其余披露数据。

示例 45：披露数据

{
    "bbsProof":"9831ba06852694fb44eb56cd9f66581330d9493671a3ad5ed28610c2550c5bfda6cada7cbaf37e9af0c873a4ec6813bf857d539543bc45ba1349fe3233b446f6c46190c40aa8456d98312ed7535c3003e3a77af752ed6f7ee162df4e38a268ad87cc5a10ff38dcc6633810e08ac5a80dacfe6e7dec3ca65fb1dab8d1b0da22b8f26040238c700b8310de92c9c2ec118b2de6b0ccdc72fbdd3329ccf7bc729829e8492d0a796f6e09131884f6fdd0df8028d5ef8f05d9aa9817872598c56421526dbe5db40586cd2b83a454652f71637e57917abd22f45bb67d48fcebdf5464671aec2e845f87f87c1d0eb934db3fb9e2310d483d67110b5f64127827888e8cd9259ea78f6683184ca4e71845b803d93a3554f4577716f939bd36f26eb740771bd5c35247ef4abc2b0e701721a6e8edf62a63af3a032df895cde06d0b15ca8c1a7507249118f9d096fcc5a3f9a39ec1a870ef619efa6af61fd93b74b82b24317def59f981fc8ec2b5633d8eb8711b108552b7b6e748648503fecdf52ac0a76eca89306361262cc4767bbb84e904d1a7523bc19d67bc501c78949616bef65470b067f81759d9a29f9c2775c0888a4617b57018ece111e62cd8365b4783fbe53bcec846bf724bdddc196fced05c59c35ebb735aea9a83f0e5233cdb9fbb8fd2e3b007ee7f69cafc37c4993ddfc747d7793b48ea48213154b459260c29da6dd41de9539a3352855afa398b2bafd47d07d765",
    "labelMap":{"dataType":"Map","value":[["c14n0","b2"],["c14n1","b4"],["c14n2","b3"],["c14n3","b7"],["c14n4","b6"],["c14n5","b0"]]},
    "mandatoryIndexes":[0,1,2,5,6,8,9,10,14,15,16,17,18,19],
    "adjSelectiveIndexes":[3,4,5,8,9,10],
    "presentationHeader":{"0":17,"1":51,"2":119,"3":170}
}

最后，将上述披露数据用于第 3.2.3 serializeDerivedProofValue节中的算法，我们将得到如下所示的已签名派生（公开）文档。

示例 46：已签名派生文档

{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    {
      "@vocab": "https://windsurf.grotto-networking.com/selective#"
    }
  ],
  "type": [
    "VerifiableCredential"
  ],
  "issuer": "https://vc.example/windsurf/racecommittee",
  "credentialSubject": {
    "sailNumber": "Earth101",
    "sails": [
      {
        "size": 6.1,
        "sailName": "Lahaina",
        "year": 2023
      },
      {
        "size": 7,
        "sailName": "Lahaina",
        "year": 2020
      }
    ],
    "boards": [
      {
        "year": 2022,
        "boardName": "CompFoil170",
        "brand": "Wailea"
      },
      {
        "boardName": "Kanaha Custom",
        "brand": "Wailea",
        "year": 2019
      }
    ]
  },
  "proof": {
    "type": "DataIntegrityProof",
    "cryptosuite": "bbs-2023",
    "created": "2023-08-15T23:36:38Z",
    "verificationMethod": "did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ",
    "proofPurpose": "assertionMethod",
    "proofValue": "u2V0DhVkCEJgxugaFJpT7ROtWzZ9mWBMw2Uk2caOtXtKGEMJVDFv9psrafLrzfprwyHOk7GgTv4V9U5VDvEW6E0n-MjO0RvbEYZDECqhFbZgxLtdTXDAD46d691Ltb37hYt9OOKJorYfMWhD_ONzGYzgQ4IrFqA2s_m597DymX7HauNGw2iK48mBAI4xwC4MQ3pLJwuwRiy3msMzccvvdMynM97xymCnoSS0KeW9uCRMYhPb90N-AKNXvjwXZqpgXhyWYxWQhUm2-XbQFhs0rg6RUZS9xY35XkXq9IvRbtn1I_OvfVGRnGuwuhF-H-HwdDrk02z-54jENSD1nEQtfZBJ4J4iOjNklnqePZoMYTKTnGEW4A9k6NVT0V3cW-Tm9NvJut0B3G9XDUkfvSrwrDnAXIabo7fYqY686Ay34lc3gbQsVyowadQckkRj50Jb8xaP5o57BqHDvYZ76avYf2Tt0uCskMX3vWfmB_I7CtWM9jrhxGxCFUre250hkhQP-zfUqwKduyokwY2EmLMR2e7uE6QTRp1I7wZ1nvFAceJSWFr72VHCwZ_gXWdmin5wndcCIikYXtXAY7OER5izYNltHg_vlO87IRr9yS93cGW_O0FxZw167c1rqmoPw5SM825-7j9LjsAfuf2nK_DfEmT3fx0fXeTtI6kghMVS0WSYMKdpt1B3pU5ozUoVa-jmLK6_UfQfXZaYAAgEEAgMDBwQGBQCOAAECBQYICQoODxAREhOGAwQFCAkKRBEzd6o"
  }
}

使用匿名持有者绑定功能的第一步是由持有者生成其 holderSecret 值，然后按照 [CFRG-Blind-BBS-Signature] 的承诺计算过程为该值计算带证明的承诺。该过程的示例值和输出如下所示。

示例 47：持有者的秘密

{
    "holderSecretHex": "8fc6cc3f65db4ba5e3ed63fe9d2bd57a9c7df9c7f6bf2b898b308d5493b07eb6"
}

示例 48：持有者的秘密承诺信息

{
  "secretProverBlind": "12901a77b3906af68d9e4214dce887d127b2a51d6311bbe7d087d45737acd2db",
  "commitmentWithProof": "ab77a14fddfafc7ae6ea82b0ef6048059225f96c9206903a34c6ec6beba702652e9d64fac1917e372853867d944e4a8059e0c26bc871cac14736e73685cd3006299539b93df64cdf661af2bc6300976528c5092c6dc842abaaa624f2184d3d5b75be0ede9c4822161149ef51a965ddda260e10b9246ecaea020ef952e3b3ed6e724bcb5d1a9c4004f0aea2cba030c27c"
}

holderSecret 和 secretProverBlind 应由持有者保留并保持秘密。 commitmentWithProof 值应传达给颁发者。

在匿名持有者绑定选项下添加基础证明的过程始于颁发者从持有者接收 commitmentWithProof 值，然后使用 [CFRG-Blind-BBS-Signature] 的承诺验证过程验证该值。基础证明一节中说明并使用的密码学密钥材料也将在此处使用，并在下面再次列出。

示例 49：用于签名的私钥和公钥

{
  "publicKeyHex": "a4ef1afa3da575496f122b9b78b8c24761531a8a093206ae7c45b80759c168ba4f7a260f9c3367b6c019b4677841104b10665edbe70ba3ebe7d9cfbffbf71eb016f70abfbb163317f372697dc63efd21fc55764f63926a8f02eaea325a2a888f",
  "privateKeyHex": "66d36e118832af4c5e28b2dfe1b9577857e57b042a33e06bdea37b811ed09ee0",
  "hmacKeyString": "00112233445566778899AABBCCDDEEFF00112233445566778899AABBCCDDEEFF"
}

在此场景中，我们考虑驾驶执照的电子版本。

示例 50：用于功能测试的不含证明的凭证

{
    "@context": [
        "https://www.w3.org/2018/credentials/v1",
        "https://w3id.org/security/data-integrity/v2",
        "https://w3id.org/vdl/v1",
        "https://w3id.org/vdl/aamva/v1"
    ],
    "type": [
        "VerifiableCredential",
        "Iso18013DriversLicenseCredential"
    ],
    "issuer": {
        "id": "did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5",
        "name": "Utopia Department of Motor Vehicles",
        "url": "https://dmv.utopia.example/",
        "image": "https://dmv.utopia.example/logo.png"
    },
    "issuanceDate": "2023-11-15T10:00:00-07:00",
    "expirationDate": "2028-11-15T12:00:00-06:00",
    "name": "Utopia Driver's License",
    "image": "data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUg...kSuQmCC",
    "description": "A license granting driving privileges in Utopia.",
    "credentialSubject": {
        "type": "LicensedDriver",
        "driversLicense": {
            "type": "Iso18013DriversLicense",
            "document_number": "542426814",
            "family_name": "TURNER",
            "given_name": "SUSAN",
            "portrait": "data:image/jpeg;base64,/9j/4AAQSkZJR...RSClooooP/2Q==",
            "birth_date": "1998-08-28",
            "issue_date": "2023-01-15T10:00:00-07:00",
            "expiry_date": "2028-08-27T12:00:00-06:00",
            "issuing_country": "UA",
            "issuing_authority": "UADMV",
            "driving_privileges": [
                {
                    "codes": [
                        {
                            "code": "D"
                        }
                    ],
                    "vehicle_category_code": "D",
                    "issue_date": "2019-01-01",
                    "expiry_date": "2027-01-01"
                },
                {
                    "codes": [
                        {
                            "code": "C"
                        }
                    ],
                    "vehicle_category_code": "C",
                    "issue_date": "2019-01-01",
                    "expiry_date": "2017-01-01"
                }
            ],
            "un_distinguishing_sign": "UTA",
            "aamva_aka_suffix": "1ST",
            "sex": 2,
            "aamva_family_name_truncation": "N",
            "aamva_given_name_truncation": "N"
        }
    }
}

为保护持有者的隐私，唯一的强制字段是 "issuer" 和 "expirationDate"，通过下面给出的强制指针实现。

示例 51：功能的强制指针

["/issuer", "/expirationDate"]

未签名文档的转换从规范化文档开始，如下所示。

示例 52：功能的规范文档

[
  "<did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5> <https://schema.org/image> <https://dmv.utopia.example/logo.png> .\n",
  "<did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5> <https://schema.org/name> \"Utopia Department of Motor Vehicles\" .\n",
  "<did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5> <https://schema.org/url> <https://dmv.utopia.example/> .\n",
  "_:c14n0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/vdl#Iso18013DriversLicenseCredential> .\n",
  "_:c14n0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://www.w3.org/2018/credentials#VerifiableCredential> .\n",
  "_:c14n0 <https://schema.org/description> \"A license granting driving privileges in Utopia.\" .\n",
  "_:c14n0 <https://schema.org/image> <data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUg...kSuQmCC> .\n",
  "_:c14n0 <https://schema.org/name> \"Utopia Driver's License\" .\n",
  "_:c14n0 <https://www.w3.org/2018/credentials#credentialSubject> _:c14n1 .\n",
  "_:c14n0 <https://www.w3.org/2018/credentials#expirationDate> \"2028-11-15T12:00:00-06:00\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:c14n0 <https://www.w3.org/2018/credentials#issuanceDate> \"2023-11-15T10:00:00-07:00\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:c14n0 <https://www.w3.org/2018/credentials#issuer> <did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5> .\n",
  "_:c14n1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/vdl#LicensedDriver> .\n",
  "_:c14n1 <https://w3id.org/vdl#license> _:c14n2 .\n",
  "_:c14n2 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/vdl#Iso18013DriversLicense> .\n",
  "_:c14n2 <https://w3id.org/vdl#birthDate> \"1998-08-28\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:c14n2 <https://w3id.org/vdl#documentNumber> \"542426814\" .\n",
  "_:c14n2 <https://w3id.org/vdl#drivingPrivileges> \"[{\\\"codes\\\":[{\\\"code\\\":\\\"D\\\"}],\\\"expiry_date\\\":\\\"2027-01-01\\\",\\\"issue_date\\\":\\\"2019-01-01\\\",\\\"vehicle_category_code\\\":\\\"D\\\"},{\\\"codes\\\":[{\\\"code\\\":\\\"C\\\"}],\\\"expiry_date\\\":\\\"2017-01-01\\\",\\\"issue_date\\\":\\\"2019-01-01\\\",\\\"vehicle_category_code\\\":\\\"C\\\"}]\"^^<http://www.w3.org/1999/02/22-rdf-syntax-ns#JSON> .\n",
  "_:c14n2 <https://w3id.org/vdl#expiryDate> \"2028-08-27T12:00:00-06:00\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:c14n2 <https://w3id.org/vdl#familyName> \"TURNER\" .\n",
  "_:c14n2 <https://w3id.org/vdl#givenName> \"SUSAN\" .\n",
  "_:c14n2 <https://w3id.org/vdl#issueDate> \"2023-01-15T10:00:00-07:00\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:c14n2 <https://w3id.org/vdl#issuingAuthority> \"UADMV\" .\n",
  "_:c14n2 <https://w3id.org/vdl#issuingCountry> \"UA\" .\n",
  "_:c14n2 <https://w3id.org/vdl#portrait> <data:image/jpeg;base64,/9j/4AAQSkZJR...RSClooooP/2Q==> .\n",
  "_:c14n2 <https://w3id.org/vdl#sex> \"2\"^^<http://www.w3.org/2001/XMLSchema#unsignedInt> .\n",
  "_:c14n2 <https://w3id.org/vdl#unDistinguishingSign> \"UTA\" .\n",
  "_:c14n2 <https://w3id.org/vdl/aamva#akaSuffix> \"1ST\" .\n",
  "_:c14n2 <https://w3id.org/vdl/aamva#familyNameTruncation> \"N\" .\n",
  "_:c14n2 <https://w3id.org/vdl/aamva#givenNameTruncation> \"N\" .\n"
]

为防止空白节点 ID 的顺序可能导致信息泄露，会通过 PRF（即 HMAC）对这些 ID 进行处理，从而得到如下所示的规范化 HMAC 文档。这表示一个将接受强制和选择性披露的有序语句列表，即语句会从该列表中进行分组。

示例 53：功能的规范 HMAC 文档

[
  "<did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5> <https://schema.org/image> <https://dmv.utopia.example/logo.png> .\n",
  "<did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5> <https://schema.org/name> \"Utopia Department of Motor Vehicles\" .\n",
  "<did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5> <https://schema.org/url> <https://dmv.utopia.example/> .\n",
  "_:b0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/vdl#LicensedDriver> .\n",
  "_:b0 <https://w3id.org/vdl#license> _:b2 .\n",
  "_:b1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/vdl#Iso18013DriversLicenseCredential> .\n",
  "_:b1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://www.w3.org/2018/credentials#VerifiableCredential> .\n",
  "_:b1 <https://schema.org/description> \"A license granting driving privileges in Utopia.\" .\n",
  "_:b1 <https://schema.org/image> <data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUg...kSuQmCC> .\n",
  "_:b1 <https://schema.org/name> \"Utopia Driver's License\" .\n",
  "_:b1 <https://www.w3.org/2018/credentials#credentialSubject> _:b0 .\n",
  "_:b1 <https://www.w3.org/2018/credentials#expirationDate> \"2028-11-15T12:00:00-06:00\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:b1 <https://www.w3.org/2018/credentials#issuanceDate> \"2023-11-15T10:00:00-07:00\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:b1 <https://www.w3.org/2018/credentials#issuer> <did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5> .\n",
  "_:b2 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/vdl#Iso18013DriversLicense> .\n",
  "_:b2 <https://w3id.org/vdl#birthDate> \"1998-08-28\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:b2 <https://w3id.org/vdl#documentNumber> \"542426814\" .\n",
  "_:b2 <https://w3id.org/vdl#drivingPrivileges> \"[{\\\"codes\\\":[{\\\"code\\\":\\\"D\\\"}],\\\"expiry_date\\\":\\\"2027-01-01\\\",\\\"issue_date\\\":\\\"2019-01-01\\\",\\\"vehicle_category_code\\\":\\\"D\\\"},{\\\"codes\\\":[{\\\"code\\\":\\\"C\\\"}],\\\"expiry_date\\\":\\\"2017-01-01\\\",\\\"issue_date\\\":\\\"2019-01-01\\\",\\\"vehicle_category_code\\\":\\\"C\\\"}]\"^^<http://www.w3.org/1999/02/22-rdf-syntax-ns#JSON> .\n",
  "_:b2 <https://w3id.org/vdl#expiryDate> \"2028-08-27T12:00:00-06:00\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:b2 <https://w3id.org/vdl#familyName> \"TURNER\" .\n",
  "_:b2 <https://w3id.org/vdl#givenName> \"SUSAN\" .\n",
  "_:b2 <https://w3id.org/vdl#issueDate> \"2023-01-15T10:00:00-07:00\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n",
  "_:b2 <https://w3id.org/vdl#issuingAuthority> \"UADMV\" .\n",
  "_:b2 <https://w3id.org/vdl#issuingCountry> \"UA\" .\n",
  "_:b2 <https://w3id.org/vdl#portrait> <data:image/jpeg;base64,/9j/4AAQSkZJR...RSClooooP/2Q==> .\n",
  "_:b2 <https://w3id.org/vdl#sex> \"2\"^^<http://www.w3.org/2001/XMLSchema#unsignedInt> .\n",
  "_:b2 <https://w3id.org/vdl#unDistinguishingSign> \"UTA\" .\n",
  "_:b2 <https://w3id.org/vdl/aamva#akaSuffix> \"1ST\" .\n",
  "_:b2 <https://w3id.org/vdl/aamva#familyNameTruncation> \"N\" .\n",
  "_:b2 <https://w3id.org/vdl/aamva#givenNameTruncation> \"N\" .\n"
]

上述规范文档会被分组为强制和非强制语句。选择性披露转换过程的最终输出如下所示。现在每条语句都被分组为强制或非强制，并且会记住其在前一个语句列表中的索引。

示例 54：为功能添加基础证明转换

{
  "mandatoryPointers": [
    "/issuer",
    "/expirationDate"
  ],
  "mandatory": {
    "dataType": "Map",
    "value": [
      [
        0,
        "<did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5> <https://schema.org/image> <https://dmv.utopia.example/logo.png> .\n"
      ],
      [
        1,
        "<did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5> <https://schema.org/name> \"Utopia Department of Motor Vehicles\" .\n"
      ],
      [
        2,
        "<did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5> <https://schema.org/url> <https://dmv.utopia.example/> .\n"
      ],
      [
        5,
        "_:b1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/vdl#Iso18013DriversLicenseCredential> .\n"
      ],
      [
        6,
        "_:b1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://www.w3.org/2018/credentials#VerifiableCredential> .\n"
      ],
      [
        11,
        "_:b1 <https://www.w3.org/2018/credentials#expirationDate> \"2028-11-15T12:00:00-06:00\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n"
      ],
      [
        13,
        "_:b1 <https://www.w3.org/2018/credentials#issuer> <did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5> .\n"
      ]
    ]
  },
  "nonMandatory": {
    "dataType": "Map",
    "value": [
      [
        3,
        "_:b0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/vdl#LicensedDriver> .\n"
      ],
      [
        4,
        "_:b0 <https://w3id.org/vdl#license> _:b2 .\n"
      ],
      [
        7,
        "_:b1 <https://schema.org/description> \"A license granting driving privileges in Utopia.\" .\n"
      ],
      [
        8,
        "_:b1 <https://schema.org/image> <data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUg...kSuQmCC> .\n"
      ],
      [
        9,
        "_:b1 <https://schema.org/name> \"Utopia Driver's License\" .\n"
      ],
      [
        10,
        "_:b1 <https://www.w3.org/2018/credentials#credentialSubject> _:b0 .\n"
      ],
      [
        12,
        "_:b1 <https://www.w3.org/2018/credentials#issuanceDate> \"2023-11-15T10:00:00-07:00\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n"
      ],
      [
        14,
        "_:b2 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/vdl#Iso18013DriversLicense> .\n"
      ],
      [
        15,
        "_:b2 <https://w3id.org/vdl#birthDate> \"1998-08-28\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n"
      ],
      [
        16,
        "_:b2 <https://w3id.org/vdl#documentNumber> \"542426814\" .\n"
      ],
      [
        17,
        "_:b2 <https://w3id.org/vdl#drivingPrivileges> \"[{\\\"codes\\\":[{\\\"code\\\":\\\"D\\\"}],\\\"expiry_date\\\":\\\"2027-01-01\\\",\\\"issue_date\\\":\\\"2019-01-01\\\",\\\"vehicle_category_code\\\":\\\"D\\\"},{\\\"codes\\\":[{\\\"code\\\":\\\"C\\\"}],\\\"expiry_date\\\":\\\"2017-01-01\\\",\\\"issue_date\\\":\\\"2019-01-01\\\",\\\"vehicle_category_code\\\":\\\"C\\\"}]\"^^<http://www.w3.org/1999/02/22-rdf-syntax-ns#JSON> .\n"
      ],
      [
        18,
        "_:b2 <https://w3id.org/vdl#expiryDate> \"2028-08-27T12:00:00-06:00\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n"
      ],
      [
        19,
        "_:b2 <https://w3id.org/vdl#familyName> \"TURNER\" .\n"
      ],
      [
        20,
        "_:b2 <https://w3id.org/vdl#givenName> \"SUSAN\" .\n"
      ],
      [
        21,
        "_:b2 <https://w3id.org/vdl#issueDate> \"2023-01-15T10:00:00-07:00\"^^<http://www.w3.org/2001/XMLSchema#dateTime> .\n"
      ],
      [
        22,
        "_:b2 <https://w3id.org/vdl#issuingAuthority> \"UADMV\" .\n"
      ],
      [
        23,
        "_:b2 <https://w3id.org/vdl#issuingCountry> \"UA\" .\n"
      ],
      [
        24,
        "_:b2 <https://w3id.org/vdl#portrait> <data:image/jpeg;base64,/9j/4AAQSkZJR...RSClooooP/2Q==> .\n"
      ],
      [
        25,
        "_:b2 <https://w3id.org/vdl#sex> \"2\"^^<http://www.w3.org/2001/XMLSchema#unsignedInt> .\n"
      ],
      [
        26,
        "_:b2 <https://w3id.org/vdl#unDistinguishingSign> \"UTA\" .\n"
      ],
      [
        27,
        "_:b2 <https://w3id.org/vdl/aamva#akaSuffix> \"1ST\" .\n"
      ],
      [
        28,
        "_:b2 <https://w3id.org/vdl/aamva#familyNameTruncation> \"N\" .\n"
      ],
      [
        29,
        "_:b2 <https://w3id.org/vdl/aamva#givenNameTruncation> \"N\" .\n"
      ]
    ]
  },
  "hmacKeyString": "00112233445566778899AABBCCDDEEFF00112233445566778899AABBCCDDEEFF"
}

接下来的步骤是创建基础证明配置并对其进行规范化。以下两个示例展示了这一过程。

示例 55：功能的基础证明配置

{
  "type": "DataIntegrityProof",
  "cryptosuite": "bbs-2023",
  "created": "2023-08-15T23:36:38Z",
  "verificationMethod": "did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ",
  "proofPurpose": "assertionMethod",
  "@context": [
    "https://www.w3.org/2018/credentials/v1",
    "https://w3id.org/security/data-integrity/v2",
    "https://w3id.org/vdl/v1",
    "https://w3id.org/vdl/aamva/v1"
  ]
}

示例 56：功能的规范基础证明配置

_:c14n0 <http://purl.org/dc/terms/created> "2023-08-15T23:36:38Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> .
_:c14n0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/security#DataIntegrityProof> .
_:c14n0 <https://w3id.org/security#cryptosuite> "bbs-2023"^^<https://w3id.org/security#cryptosuiteString> .
_:c14n0 <https://w3id.org/security#proofPurpose> <https://w3id.org/security#assertionMethod> .
_:c14n0 <https://w3id.org/security#verificationMethod> <did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ> .

在哈希步骤中，我们计算规范化证明选项的 SHA-256 哈希以生成 proofHash，并计算所有强制 N-Quads 拼接结果的 SHA-256 哈希以生成 mandatoryHash。这些值以十六进制格式显示如下。

示例 57：为功能添加基础证明哈希

{
  "proofHash": "3a5bbf25d34d90b18c35cd2357be6a6f42301e94fc9e52f77e93b773c5614bdf",
  "mandatoryHash": "8eea112c04d89e133880f96766ebae73693f75f1bbcbbaa473dc06254bdec4fb"
}

现在，我们在 3.3.2 基础证明序列化 (bbs-2023) 过程中使用 [CFRG-Blind-BBS-Signature] 的盲签名生成过程。下面显示计算得到的 bbsSignature、bbsHeader、publicKey、 hmacKey、mandatoryPointers 和 featureOption，其中字节数据以十六进制显示。

示例 58：为持有者绑定添加基础证明签名

{
  "bbsSignature": "90eadd70a16661f3d596f3560fc485f7c23ba969eb7c237d481b3596b2f66279bd5a62fa523777eb73b5cfa361885f1a00864b960baf1b92d2b55c0652ebe39024f88e1377911c40bf14cb5fbc808ee1",
  "bbsHeader": "3a5bbf25d34d90b18c35cd2357be6a6f42301e94fc9e52f77e93b773c5614bdf8eea112c04d89e133880f96766ebae73693f75f1bbcbbaa473dc06254bdec4fb",
  "publicKey": "a4ef1afa3da575496f122b9b78b8c24761531a8a093206ae7c45b80759c168ba4f7a260f9c3367b6c019b4677841104b10665edbe70ba3ebe7d9cfbffbf71eb016f70abfbb163317f372697dc63efd21fc55764f63926a8f02eaea325a2a888f",
  "hmacKey": "00112233445566778899aabbccddeeff00112233445566778899aabbccddeeff",
  "mandatoryPointers": [
    "/issuer",
    "/expirationDate"
  ],
  "featureOption": "anonymous_holder_binding"
}

最后，将上述值通过第 3.2.1 serializeBaseProofValue节的算法运行，以生成如下所示的已签名基础文档中使用的 proofValue。

示例 59：用于持有者绑定的已签名基础文档

{
  "@context": [
    "https://www.w3.org/2018/credentials/v1",
    "https://w3id.org/security/data-integrity/v2",
    "https://w3id.org/vdl/v1",
    "https://w3id.org/vdl/aamva/v1"
  ],
  "type": [
    "VerifiableCredential",
    "Iso18013DriversLicenseCredential"
  ],
  "issuer": {
    "id": "did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5",
    "name": "Utopia Department of Motor Vehicles",
    "url": "https://dmv.utopia.example/",
    "image": "https://dmv.utopia.example/logo.png"
  },
  "issuanceDate": "2023-11-15T10:00:00-07:00",
  "expirationDate": "2028-11-15T12:00:00-06:00",
  "name": "Utopia Driver's License",
  "image": "data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUg...kSuQmCC",
  "description": "A license granting driving privileges in Utopia.",
  "credentialSubject": {
    "type": "LicensedDriver",
    "driversLicense": {
      "type": "Iso18013DriversLicense",
      "document_number": "542426814",
      "family_name": "TURNER",
      "given_name": "SUSAN",
      "portrait": "data:image/jpeg;base64,/9j/4AAQSkZJR...RSClooooP/2Q==",
      "birth_date": "1998-08-28",
      "issue_date": "2023-01-15T10:00:00-07:00",
      "expiry_date": "2028-08-27T12:00:00-06:00",
      "issuing_country": "UA",
      "issuing_authority": "UADMV",
      "driving_privileges": [
        {
          "codes": [
            {
              "code": "D"
            }
          ],
          "vehicle_category_code": "D",
          "issue_date": "2019-01-01",
          "expiry_date": "2027-01-01"
        },
        {
          "codes": [
            {
              "code": "C"
            }
          ],
          "vehicle_category_code": "C",
          "issue_date": "2019-01-01",
          "expiry_date": "2017-01-01"
        }
      ],
      "un_distinguishing_sign": "UTA",
      "aamva_aka_suffix": "1ST",
      "sex": 2,
      "aamva_family_name_truncation": "N",
      "aamva_given_name_truncation": "N"
    }
  },
  "proof": {
    "type": "DataIntegrityProof",
    "cryptosuite": "bbs-2023",
    "created": "2023-08-15T23:36:38Z",
    "verificationMethod": "did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ",
    "proofPurpose": "assertionMethod",
    "proofValue": "u2V0EhVhQkOrdcKFmYfPVlvNWD8SF98I7qWnrfCN9SBs1lrL2Ynm9WmL6Ujd363O1z6NhiF8aAIZLlguvG5LStVwGUuvjkCT4jhN3kRxAvxTLX7yAjuFYQDpbvyXTTZCxjDXNI1e-am9CMB6U_J5S936Tt3PFYUvfjuoRLATYnhM4gPlnZuuuc2k_dfG7y7qkc9wGJUvexPtYYKTvGvo9pXVJbxIrm3i4wkdhUxqKCTIGrnxFuAdZwWi6T3omD5wzZ7bAGbRneEEQSxBmXtvnC6Pr59nPv_v3HrAW9wq_uxYzF_NyaX3GPv0h_FV2T2OSao8C6uoyWiqIj1ggABEiM0RVZneImaq7zN3u_wARIjNEVWZ3iJmqu8zd7v-CZy9pc3N1ZXJvL2V4cGlyYXRpb25EYXRl"
  }
}

如一节中所述，我们使用模拟随机数生成过程，并演示 presentationHeader 的使用。此处使用相同的 seed 和 presentationHeader，并在下面再次列出。

示例 60：seed 和出示头值

{
  "presentationHeaderHex": "113377aa",
  "pseudoRandSeedHex": "332e313431353932363533353839373933323338343632363433333833323739"
}

要创建派生证明，持有者从包含基础证明的已签名文档开始。我们用于这些测试向量的基础文档是上面第 A.3.2 持有者绑定基础证明节中的最后一个示例。第一步是运行第 3.2.2 parseBaseProofValue节的算法，以恢复 bbsSignature、bbsHeader、publicKey、hmacKey、 mandatoryPointers 和 featureOption，如下所示。

示例 61：为持有者绑定恢复的基础签名数据

{
  "bbsSignature": "90eadd70a16661f3d596f3560fc485f7c23ba969eb7c237d481b3596b2f66279bd5a62fa523777eb73b5cfa361885f1a00864b960baf1b92d2b55c0652ebe39024f88e1377911c40bf14cb5fbc808ee1",
  "bbsHeader": "3a5bbf25d34d90b18c35cd2357be6a6f42301e94fc9e52f77e93b773c5614bdf8eea112c04d89e133880f96766ebae73693f75f1bbcbbaa473dc06254bdec4fb",
  "publicKey": "a4ef1afa3da575496f122b9b78b8c24761531a8a093206ae7c45b80759c168ba4f7a260f9c3367b6c019b4677841104b10665edbe70ba3ebe7d9cfbffbf71eb016f70abfbb163317f372697dc63efd21fc55764f63926a8f02eaea325a2a888f",
  "hmacKey": "00112233445566778899aabbccddeeff00112233445566778899aabbccddeeff",
  "mandatoryPointers": [
    "/issuer",
    "/expirationDate"
  ],
  "featureOption": "anonymous_holder_binding"
}

接下来，持有者需要通过指定用于选择性披露的 JSON 指针，指明还希望向验证者披露哪些内容（如果有）。在这种情况下，持有者只希望披露其驾驶权限。

示例 62：功能的选择性披露指针

["/credentialSubject/driversLicense/issuing_country", "/credentialSubject/driversLicense/driving_privileges"]

示例 63：功能的未签名披露文档

{
  "@context": [
    "https://www.w3.org/2018/credentials/v1",
    "https://w3id.org/security/data-integrity/v2",
    "https://w3id.org/vdl/v1",
    "https://w3id.org/vdl/aamva/v1"
  ],
  "type": [
    "VerifiableCredential",
    "Iso18013DriversLicenseCredential"
  ],
  "issuer": {
    "id": "did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5",
    "name": "Utopia Department of Motor Vehicles",
    "url": "https://dmv.utopia.example/",
    "image": "https://dmv.utopia.example/logo.png"
  },
  "expirationDate": "2028-11-15T12:00:00-06:00",
  "credentialSubject": {
    "type": "LicensedDriver",
    "driversLicense": {
      "type": "Iso18013DriversLicense",
      "issuing_country": "UA",
      "driving_privileges": [
        {
          "codes": [
            {
              "code": "D"
            }
          ],
          "vehicle_category_code": "D",
          "issue_date": "2019-01-01",
          "expiry_date": "2027-01-01"
        },
        {
          "codes": [
            {
              "code": "C"
            }
          ],
          "vehicle_category_code": "C",
          "issue_date": "2019-01-01",
          "expiry_date": "2017-01-01"
        }
      ]
    }
  }
}

既然我们已经知道了公开文档是什么样子，就需要向验证者提供适当更新的信息，说明哪些语句是强制的，以及所选非强制语句的索引。运行 § 4.4.3 CreateDisclosureData 会生成大量关于相对于原始文档的各种语句组的信息。下面，我们展示这些组的一部分索引。

示例 64：功能的派生组索引

{"combinedIndexes":[0,1,2,3,4,5,6,10,11,13,14,17,23],"mandatoryIndexes":[0,1,2,5,6,11,13],"nonMandatoryIndexes":[3,4,7,8,9,10,12,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29],"selectiveIndexes":[3,4,5,6,10,14,17,23]}

验证者需要能够聚合并哈希强制语句。为了实现这一点，我们向其提供强制语句的索引列表，并将其调整为这些语句在披露文档中的位置（即相对于 combinedIndexes），而 selectiveIndexes 则需要相对于它们在 nonMandatoryIndexes 中的位置进行调整。这些“调整后的”索引如下所示。

示例 65：功能的调整后强制和选择性索引

{"adjMandatoryIndexes":[0,1,2,5,6,8,9],"adjSelectiveIndexes":[0,1,5,7,10,16]}

最后一项重要的披露数据是从规范空白节点 ID 到基于 HMAC 的打乱 ID 的映射，即 labelMap，它按照第 § 4.4.3 CreateDisclosureData节计算得出。如下所示，同时还展示了除公开文档之外的其余披露数据。请注意，这里我们展示的是适用于 featureOption 等于 "anonymous_holder_binding" 时的结果，该选项使用 [CFRG-Blind-BBS-Signature] 的盲证明生成 过程。请注意， blindAdjDisclosedIdxs 是证明序列化过程中使用的最终 BBS 选择性索引集，它来自以 adjSelectiveIndexes 作为输入的盲 BBS 证明生成函数。

示例 66：用于持有者绑定的披露数据

{"bbsProof":"a19db05cca1237d9965b0bb3197c4962a7fb49c97af131c80ea2d8f949078ff5642acdb33d27d06b97f87ff906a2a23bb0c3dd778572b892785faefdc25811318b0b46e25b8863898b0600701a71c256ee9a7347a1a577fe2e3793b1c0390e4d8f9fff9161074eebba852bcca8089eed76416ac9f178b850e7688c26cfbdee344fa75d9ba2cf22417e3c70be7891f6de040928d4a665005ddbe3b7372ecb87baad726f1535d4600a0198d3a36a17ad673160f8ef5e5fd74f2542b214cc4534ee82b0a90c0501ca9749c8327afcb97e14220f2e516dfc3cb2ed2ffdd3845a25cb64e1a2aa9987bbc122755158d787a2356e28f2affff31b83a2cdff26d5ac1aa72f4d6c40fe96ad230ce09fd4e9b8998357c2964da031e59c3b8c2241da00bc66a6216af7cd02b535577fa3b54bf9a0d230183b03aa145dbabc7fed3710d879c6b8d4273e6e377bed382de985f561ff9b2b3445f29957655600cbd1b29714f52c55ff05bc204203e65bdf6f818e976c690becfed9284b27c2dead96803efad949ffb519b7024530b08b5ed4c8e7472ed20c3866b79658e1b2d2c5b88a60da07614afa4906c73a6e5ad9113282288173e265236fa57d72c97f85c86b43349516f8e2f52f756d43cd2d9cf8c673db404d14007706ebbd4f7b5bbd19cdce9f48b2dac2db7f0f0c3fb18bd8e66e28fe46dafc3961e5945779faf5407190a33ce00efd07222cc142d40cab9b9d591589a30d056dae47d376d3ac5fab3201bbada604dd8e5e292185f38e2bcd58e81b2fec1e7b5754b7b28bd127abc929e950cb75100e94695f1ad13c09c1d394664029b66bdd49304df3ae1e2a90a6309f07c47555ccaea9cd17d80eaad6b7c29e9335a69338446ff666ac5802cfe36057c449d392bda99d2657fb8b6cf02d7ce4d9dccd8e97033accc5c10f092ec7bf0b3c0b2afc64a1a429d81cc485388f6f390dd97f648c3712ee0b93a7e96b268437e6e3537fb7918cee2a4ac3f895c7945988d7d3880238b8cf6062da171aa87545cf62072b20e698eb4ac12450c0b95a77e946fada8d46102abfa9a5a12d2a71380dedb51e2a57c97514813c17ea93e6ca19077c2a2511bf8fd158c4ed7361590b040915a3cb76f323300111303d8dd31c55474d514209bf01ed6639d4d81a1b30be54444e523e2ddef9a0a6bfe792d3037944aec29154c02bb79d09bd53856797dceb6c599f4103ff7f13dfdb8b2d18477832e5fe21","labelMap":{"dataType":"Map","value":[["c14n0","b1"],["c14n1","b2"],["c14n2","b0"]]},"mandatoryIndexes":[0,1,2,5,6,8,9],"adjSelectiveIndexes":[0,1,5,7,10,16],"presentationHeader":{"0":17,"1":51,"2":119,"3":170},"featureOption":"anonymous_holder_binding","lengthBBSMessages":23}

最后，将上述披露数据用于第 3.2.3 serializeDerivedProofValue节中的算法，我们将得到如下所示的已签名派生（公开）文档。

示例 67：用于持有者绑定的已签名派生文档

{
  "@context": [
    "https://www.w3.org/2018/credentials/v1",
    "https://w3id.org/security/data-integrity/v2",
    "https://w3id.org/vdl/v1",
    "https://w3id.org/vdl/aamva/v1"
  ],
  "type": [
    "VerifiableCredential",
    "Iso18013DriversLicenseCredential"
  ],
  "issuer": {
    "id": "did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5",
    "name": "Utopia Department of Motor Vehicles",
    "url": "https://dmv.utopia.example/",
    "image": "https://dmv.utopia.example/logo.png"
  },
  "expirationDate": "2028-11-15T12:00:00-06:00",
  "credentialSubject": {
    "type": "LicensedDriver",
    "driversLicense": {
      "type": "Iso18013DriversLicense",
      "issuing_country": "UA",
      "driving_privileges": [
        {
          "codes": [
            {
              "code": "D"
            }
          ],
          "vehicle_category_code": "D",
          "issue_date": "2019-01-01",
          "expiry_date": "2027-01-01"
        },
        {
          "codes": [
            {
              "code": "C"
            }
          ],
          "vehicle_category_code": "C",
          "issue_date": "2019-01-01",
          "expiry_date": "2017-01-01"
        }
      ]
    }
  },
  "proof": {
    "type": "DataIntegrityProof",
    "cryptosuite": "bbs-2023",
    "created": "2023-08-15T23:36:38Z",
    "verificationMethod": "did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ",
    "proofPurpose": "assertionMethod",
    "proofValue": "u2V0FhlkDcKGdsFzKEjfZllsLsxl8SWKn-0nJevExyA6i2PlJB4_1ZCrNsz0n0GuX-H_5BqKiO7DD3XeFcriSeF-u_cJYETGLC0biW4hjiYsGAHAaccJW7ppzR6Gld_4uN5OxwDkOTY-f_5FhB07ruoUrzKgInu12QWrJ8Xi4UOdojCbPve40T6ddm6LPIkF-PHC-eJH23gQJKNSmZQBd2-O3Ny7Lh7qtcm8VNdRgCgGY06NqF61nMWD4715f108lQrIUzEU07oKwqQwFAcqXScgyevy5fhQiDy5Rbfw8su0v_dOEWiXLZOGiqpmHu8EidVFY14eiNW4o8q__8xuDos3_JtWsGqcvTWxA_patIwzgn9TpuJmDV8KWTaAx5Zw7jCJB2gC8ZqYhavfNArU1V3-jtUv5oNIwGDsDqhRdurx_7TcQ2HnGuNQnPm43e-04LemF9WH_mys0RfKZV2VWAMvRspcU9SxV_wW8IEID5lvfb4GOl2xpC-z-2ShLJ8LerZaAPvrZSf-1GbcCRTCwi17UyOdHLtIMOGa3lljhstLFuIpg2gdhSvpJBsc6blrZETKCKIFz4mUjb6V9csl_hchrQzSVFvji9S91bUPNLZz4xnPbQE0UAHcG671Pe1u9Gc3On0iy2sLbfw8MP7GL2OZuKP5G2vw5YeWUV3n69UBxkKM84A79ByIswULUDKubnVkViaMNBW2uR9N206xfqzIBu62mBN2OXikhhfOOK81Y6Bsv7B57V1S3sovRJ6vJKelQy3UQDpRpXxrRPAnB05RmQCm2a91JME3zrh4qkKYwnwfEdVXMrqnNF9gOqta3wp6TNaaTOERv9masWALP42BXxEnTkr2pnSZX-4ts8C185NnczY6XAzrMxcEPCS7Hvws8Cyr8ZKGkKdgcxIU4j285Ddl_ZIw3Eu4Lk6fpayaEN-bjU3-3kYzuKkrD-JXHlFmI19OIAji4z2Bi2hcaqHVFz2IHKyDmmOtKwSRQwLlad-lG-tqNRhAqv6mloS0qcTgN7bUeKlfJdRSBPBfqk-bKGQd8KiURv4_RWMTtc2FZCwQJFaPLdvMjMAERMD2N0xxVR01RQgm_Ae1mOdTYGhswvlRETlI-Ld75oKa_55LTA3lErsKRVMArt50JvVOFZ5fc62xZn0ED_38T39uLLRhHeDLl_iGjAAEBAgIAhwABAgUGCAmGAAEFBwoQRBEzd6oX"
  }
}

使用凭据绑定假名功能的第一步是让持有者生成其秘密 prover_nym 值，然后按照 [CFRG-Pseudonym-BBS-Signature] 中的“Commitment”操作为该值计算带证明的承诺。该过程的示例值和输出如下所示。

示例 68：证明者 Nym

{
    "proverNymHex": "5e2087638f71057ef108f83923189a71cea1f7c4b4ef69afb473c9a7074ddf49"
}

示例 69：证明者 Nym 承诺信息

{
  "secretProverBlind": "2df3cd3d451b21069b72269f9984df449219c41273b19b1a8487d836fbb8baa1",
  "commitmentWithProof": "a80f61f9470cb8ab88644fbef3616eaf5d3b147c4dc1dcad810148a5f2e73186cb3ffa27ea55728a6df470d0c3928be1408b95f5d261cee4d66992ecacf5ca2d6348c33bb7f90c2cef513cdc88be536550e9701d9a466320f49ce097551f8097317c530e2b80710748362b03f5a74280669c00eb29145eb3ec51975d8189fdf2c810d7fadefe36f93b0d2068a494175c"
}

prover_nym 和 secretProverBlind 应由持有者保留并保持秘密。 commitmentWithProof 值应传达给颁发者。

在假名功能选项下添加基础证明的过程始于颁发者从持有者接收 commitmentWithProof 值，并为 signer_nym_entropy 生成密码学随机值。

示例 70：签名者 Nym 熵

{
    "signerNymEntropyHex": "25555cf635188a1c33989056f5129e6ab4be0e7c5cc588c48d308e0254eed140"
}

此示例将使用示例 27中所示的相同密钥材料、示例 50中所示的相同未签名文档，以及示例 51中所示的相同强制指针。这会产生与示例 52中所示相同的规范文档、与示例 53中所示相同的规范 HMAC 文档，以及与示例 54中所示相同的“添加基础证明转换”。

此示例使用与示例 55相同的证明配置。这会产生与示例 56中相同的规范基础证明。将其与上述假设结合，会得到与示例 57相同的基础哈希。

由于 featureOption 等于 "pseudonym"，第 3.3.2 基础证明序列化 (bbs-2023)节中的过程将产生如下所示的输出。这里使用了 [CFRG-Pseudonym-BBS-Signature] 的签名生成算法。请注意其中包含 signer_nym_entropy 和 featureOption 值，因为这些值需要传达给持有者。

示例 71：为假名添加基础证明签名

{
  "bbsSignature": "b9389149bab1b5a6032c20781732105a5cbc209592e712e182eec5c055f2072877683dee2949af32290d350ed9e9ffa246f65b8c3f6f199c4d29009d2ce6dff374ed4f22f2f9a7e12dc3c342e8c18107",
  "bbsHeader": "3a5bbf25d34d90b18c35cd2357be6a6f42301e94fc9e52f77e93b773c5614bdf8eea112c04d89e133880f96766ebae73693f75f1bbcbbaa473dc06254bdec4fb",
  "publicKey": "a4ef1afa3da575496f122b9b78b8c24761531a8a093206ae7c45b80759c168ba4f7a260f9c3367b6c019b4677841104b10665edbe70ba3ebe7d9cfbffbf71eb016f70abfbb163317f372697dc63efd21fc55764f63926a8f02eaea325a2a888f",
  "hmacKey": "00112233445566778899aabbccddeeff00112233445566778899aabbccddeeff",
  "mandatoryPointers": [
    "/issuer",
    "/expirationDate"
  ],
  "signerNymEntropyHex": "25555cf635188a1c33989056f5129e6ab4be0e7c5cc588c48d308e0254eed140",
  "featureOption": "pseudonym"
}

最后，将上述值通过第 3.2.1 serializeBaseProofValue节的算法运行，生成如下所示的已签名基础文档中使用的 proofValue。

示例 72：用于假名的已签名基础文档

{
  "@context": [
    "https://www.w3.org/2018/credentials/v1",
    "https://w3id.org/security/data-integrity/v2",
    "https://w3id.org/vdl/v1",
    "https://w3id.org/vdl/aamva/v1"
  ],
  "type": [
    "VerifiableCredential",
    "Iso18013DriversLicenseCredential"
  ],
  "issuer": {
    "id": "did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5",
    "name": "Utopia Department of Motor Vehicles",
    "url": "https://dmv.utopia.example/",
    "image": "https://dmv.utopia.example/logo.png"
  },
  "issuanceDate": "2023-11-15T10:00:00-07:00",
  "expirationDate": "2028-11-15T12:00:00-06:00",
  "name": "Utopia Driver's License",
  "image": "data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUg...kSuQmCC",
  "description": "A license granting driving privileges in Utopia.",
  "credentialSubject": {
    "type": "LicensedDriver",
    "driversLicense": {
      "type": "Iso18013DriversLicense",
      "document_number": "542426814",
      "family_name": "TURNER",
      "given_name": "SUSAN",
      "portrait": "data:image/jpeg;base64,/9j/4AAQSkZJR...RSClooooP/2Q==",
      "birth_date": "1998-08-28",
      "issue_date": "2023-01-15T10:00:00-07:00",
      "expiry_date": "2028-08-27T12:00:00-06:00",
      "issuing_country": "UA",
      "issuing_authority": "UADMV",
      "driving_privileges": [
        {
          "codes": [
            {
              "code": "D"
            }
          ],
          "vehicle_category_code": "D",
          "issue_date": "2019-01-01",
          "expiry_date": "2027-01-01"
        },
        {
          "codes": [
            {
              "code": "C"
            }
          ],
          "vehicle_category_code": "C",
          "issue_date": "2019-01-01",
          "expiry_date": "2017-01-01"
        }
      ],
      "un_distinguishing_sign": "UTA",
      "aamva_aka_suffix": "1ST",
      "sex": 2,
      "aamva_family_name_truncation": "N",
      "aamva_given_name_truncation": "N"
    }
  },
  "proof": {
    "type": "DataIntegrityProof",
    "cryptosuite": "bbs-2023",
    "created": "2023-08-15T23:36:38Z",
    "verificationMethod": "did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ",
    "proofPurpose": "assertionMethod",
    "proofValue": "u2V0IhlhQuTiRSbqxtaYDLCB4FzIQWly8IJWS5xLhgu7FwFXyByh3aD3uKUmvMikNNQ7Z6f-iRvZbjD9vGZxNKQCdLObf83TtTyLy-afhLcPDQujBgQdYQDpbvyXTTZCxjDXNI1e-am9CMB6U_J5S936Tt3PFYUvfjuoRLATYnhM4gPlnZuuuc2k_dfG7y7qkc9wGJUvexPtYYKTvGvo9pXVJbxIrm3i4wkdhUxqKCTIGrnxFuAdZwWi6T3omD5wzZ7bAGbRneEEQSxBmXtvnC6Pr59nPv_v3HrAW9wq_uxYzF_NyaX3GPv0h_FV2T2OSao8C6uoyWiqIj1ggABEiM0RVZneImaq7zN3u_wARIjNEVWZ3iJmqu8zd7v-CZy9pc3N1ZXJvL2V4cGlyYXRpb25EYXRlwlggJVVc9jUYihwzmJBW9RKearS-DnxcxYjEjTCOAlTu0UA"
  }
}

如第 A.1.2 派生证明节中所述，我们使用模拟随机数生成过程来演示 presentationHeader 的使用。此处使用示例 19中给出的相同 seed 和 presentationHeader。

要创建派生证明，持有者从包含基础证明的已签名文档开始。我们用于这些测试向量的基础文档来自上面的示例 72。第一步是运行第 3.2.2 parseBaseProofValue节的算法，以恢复 bbsSignature、bbsHeader、publicKey、hmacKey、 mandatoryPointers、signer_nym_entropy 和 featureOption，如下所示。

示例 73：为假名恢复的基础签名数据

{
  "bbsSignature": "b9389149bab1b5a6032c20781732105a5cbc209592e712e182eec5c055f2072877683dee2949af32290d350ed9e9ffa246f65b8c3f6f199c4d29009d2ce6dff374ed4f22f2f9a7e12dc3c342e8c18107",
  "bbsHeader": "3a5bbf25d34d90b18c35cd2357be6a6f42301e94fc9e52f77e93b773c5614bdf8eea112c04d89e133880f96766ebae73693f75f1bbcbbaa473dc06254bdec4fb",
  "publicKey": "a4ef1afa3da575496f122b9b78b8c24761531a8a093206ae7c45b80759c168ba4f7a260f9c3367b6c019b4677841104b10665edbe70ba3ebe7d9cfbffbf71eb016f70abfbb163317f372697dc63efd21fc55764f63926a8f02eaea325a2a888f",
  "hmacKey": "00112233445566778899aabbccddeeff00112233445566778899aabbccddeeff",
  "mandatoryPointers": [
    "/issuer",
    "/expirationDate"
  ],
  "signerNymEntropy": "25555cf635188a1c33989056f5129e6ab4be0e7c5cc588c48d308e0254eed140",
  "featureOption": "pseudonym"
}

接下来，持有者使用 [CFRG-Pseudonym-BBS-Signature] 中的“验证和最终确定”操作，以同时验证签名并计算 nym_secret 值。此操作会使用 prover_nym、 signer_nym_entropy 和 secret_prover_blind 等值。

示例 74：计算得到的 Nym 秘密

{
    "nymSecretHex": "f883d069aec1252f167b0880e8960d72fa2623e11b6967541a457aa5c3cb088"
}

接下来，持有者需要通过指定用于选择性披露的 JSON 指针，指明希望向验证者披露哪些非强制语句（如果有）。在这种情况下，持有者披露与示例 62中给出的相同信息。这会产生与示例 63中所示相同的 revealDocument。

运行 § 4.4.3 CreateDisclosureData 会生成与示例 64中所示相同的派生组索引信息，以及与示例 65中所示相同的调整后强制索引和选择性索引。

在 3.2.3 serializeDerivedProofValue 中，我们基于中所示的相同 verfifier_id 计算 pseudonym。 § 4.4.3 CreateDisclosureData 的最终输出如下所示。请注意其中包含 featureOption 和计算得到的 pseudonym 值。

示例 75：假名的披露数据

{
    "bbsProof":"b394693d54d67937aae0e4175ecf4331200c23470171188ac5513b30d27d9bd2e06173d44e1aca7c743ba30b3f59af0595965bf8256437bce6bef824fe243183af6aa14a1e8224ed7e4eeb16445594df13a46e75d8dfbae0a3e2e1e0871260e68f71de7be4309eb53523a446b8189446b8d5c60892bdd855b5067e0433b46d5b9ffc4dc54b712ff97ec9d7c44cff648929d826bf9e3a7f873c9bcd07c6a3747fc6befceaf892c4d8d38d385c19c399ab342a76c000a3ff9050fa9223e20acfdf4404f43605a24c44622ebcaaf144b161226a6cbe7c08474f9fb80a736be3a818e4e62aa738e701007871859bea36e062324ff3afd8670a5de8b69911fae58aa40e48e29a046c37b9f9cc3868c30482d2339746955c3deaf6f1d4c8cf8be8e503f3ea4715d11e385eb7ed9de6379b7de8436a4e89cf4427d53358b1882e27c6e1e3ba2e81cf10fbc792cf3461a0fdd63f35a151b8c8350505a9b6d612e9adc1dca11b2698a3d0a9f0df6e9bc0ece7aa462afab02d93a87fd5bebb0eee058770c81c5f2fe6eeefcb0a657d9f116b96e2b04b4cc7f4baad4fe784bd9563aea20272138f2dbe94a5e25d30633b5f83eac4b42af25f144bddb631738bf3d54206e8d8b5172c8d52d3c272f799b782c73d480e1289e262ddbb70ab29491cf85a8428c4672437677407524a6dacb53332565dab5d056dbc5451becb123f91d173f6a7c785b7d9f19c43864a785bd941db248322539a097e9ac06244308a3b8df88b5213724cf09715b09e06425448c400680b943ba4711f14a719920b06ec2c6aff908ecf4f5793afd233d270a5ef92131606035517a89e4118dc65dbeb9051f92797036f54f8400910fa56cdd7b87b122e39e41233ea493239fab55c4c836a0a38732a68e6a9f9e11d32b991599e19edbb386f0d364b91e10dd9bf82898f79e90045a0c4987a0cf365d37d8380539a794284841c50c83f2bc3ee9cf7432f44dbfca897ff99feabf224e51137313630c5000d39429d9ea69a2a8237fe3a1857121c14ebb00d57b90db39e2e11bfa37858187d183027c45e317a72e5334681de26788e3176bd48d5761d54c1f2af0a6c3549a0de05b21d0a066c732a540072ae7676b867027b18323e08fcbfaf38ec22aeccd3375bb7b6965d9f6ab3ac4adc2a0700a4bc82fe58afbdd035af48fb85fcd8bf14f81d5ca3f2626be8962cbea13da31ff3cc6c6ebfeeef42f25708af872a14019f83",
    "labelMap":{"dataType":"Map","value":[["c14n0","b1"],["c14n1","b2"],["c14n2","b0"]]},
    "mandatoryIndexes":[0,1,2,5,6,8,9],
    "adjSelectiveIndexes":[0,1,5,7,10,16],
    "presentationHeader":{"0":17,"1":51,"2":119,"3":170},
    "pseudonym":"838607ff2c8dcb2a0740ef13c2c87418efb57559243232a69daf1e294dd092af833ad4df1e99e0034c737b932916f378",
    "featureOption":"pseudonym",
    "lengthBBSMessages":23
}

最后，将上述披露数据用于第 3.2.3 serializeDerivedProofValue节中的算法，我们将得到如下所示的已签名派生（公开）文档。

示例 76：用于假名的已签名派生文档

{
  "@context": [
    "https://www.w3.org/2018/credentials/v1",
    "https://w3id.org/security/data-integrity/v2",
    "https://w3id.org/vdl/v1",
    "https://w3id.org/vdl/aamva/v1"
  ],
  "type": [
    "VerifiableCredential",
    "Iso18013DriversLicenseCredential"
  ],
  "issuer": {
    "id": "did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5",
    "name": "Utopia Department of Motor Vehicles",
    "url": "https://dmv.utopia.example/",
    "image": "https://dmv.utopia.example/logo.png"
  },
  "expirationDate": "2028-11-15T12:00:00-06:00",
  "credentialSubject": {
    "type": "LicensedDriver",
    "driversLicense": {
      "type": "Iso18013DriversLicense",
      "issuing_country": "UA",
      "driving_privileges": [
        {
          "codes": [
            {
              "code": "D"
            }
          ],
          "vehicle_category_code": "D",
          "issue_date": "2019-01-01",
          "expiry_date": "2027-01-01"
        },
        {
          "codes": [
            {
              "code": "C"
            }
          ],
          "vehicle_category_code": "C",
          "issue_date": "2019-01-01",
          "expiry_date": "2017-01-01"
        }
      ]
    }
  },
  "proof": {
    "type": "DataIntegrityProof",
    "cryptosuite": "bbs-2023",
    "created": "2023-08-15T23:36:38Z",
    "verificationMethod": "did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ",
    "proofPurpose": "assertionMethod",
    "proofValue": "u2V0Jh1kDcLOUaT1U1nk3quDkF17PQzEgDCNHAXEYisVROzDSfZvS4GFz1E4aynx0O6MLP1mvBZWWW_glZDe85r74JP4kMYOvaqFKHoIk7X5O6xZEVZTfE6RuddjfuuCj4uHghxJg5o9x3nvkMJ61NSOkRrgYlEa41cYIkr3YVbUGfgQztG1bn_xNxUtxL_l-ydfETP9kiSnYJr-eOn-HPJvNB8ajdH_Gvvzq-JLE2NONOFwZw5mrNCp2wACj_5BQ-pIj4grP30QE9DYFokxEYi68qvFEsWEiamy-fAhHT5-4CnNr46gY5OYqpzjnAQB4cYWb6jbgYjJP86_YZwpd6LaZEfrliqQOSOKaBGw3ufnMOGjDBILSM5dGlVw96vbx1MjPi-jlA_PqRxXRHjhet-2d5jebfehDak6Jz0Qn1TNYsYguJ8bh47ougc8Q-8eSzzRhoP3WPzWhUbjINQUFqbbWEumtwdyhGyaYo9Cp8N9um8Ds56pGKvqwLZOof9W-uw7uBYdwyBxfL-bu78sKZX2fEWuW4rBLTMf0uq1P54S9lWOuogJyE48tvpSl4l0wYztfg-rEtCryXxRL3bYxc4vz1UIG6Ni1FyyNUtPCcveZt4LHPUgOEoniYt27cKspSRz4WoQoxGckN2d0B1JKbay1MzJWXatdBW28VFG-yxI_kdFz9qfHhbfZ8ZxDhkp4W9lB2ySDIlOaCX6awGJEMIo7jfiLUhNyTPCXFbCeBkJUSMQAaAuUO6RxHxSnGZILBuwsav-Qjs9PV5Ov0jPScKXvkhMWBgNVF6ieQRjcZdvrkFH5J5cDb1T4QAkQ-lbN17h7Ei455BIz6kkyOfq1XEyDago4cypo5qn54R0yuZFZnhntuzhvDTZLkeEN2b-CiY956QBFoMSYegzzZdN9g4BTmnlChIQcUMg_K8PunPdDL0Tb_KiX_5n-q_Ik5RE3MTYwxQANOUKdnqaaKoI3_joYVxIcFOuwDVe5DbOeLhG_o3hYGH0YMCfEXjF6cuUzRoHeJniOMXa9SNV2HVTB8q8KbDVJoN4Fsh0KBmxzKlQAcq52drhnAnsYMj4I_L-vOOwirszTN1u3tpZdn2qzrErcKgcApLyC_livvdA1r0j7hfzYvxT4HVyj8mJr6JYsvqE9ox_zzGxuv-7vQvJXCK-HKhQBn4OjAAEBAgIAhwABAgUGCAmGAAEFBwoQRBEzd6pYMIOGB_8sjcsqB0DvE8LIdBjvtXVZJDIypp2vHilN0JKvgzrU3x6Z4ANMc3uTKRbzeBc"
  }
}

使用持有者绑定和假名功能的第一步是让持有者生成其 holder_secret 和 prover_nym 值，然后根据 [CFRG-Pseudonym-BBS-Signature] 中的“承诺”操作为这些值计算带证明的承诺。该过程的示例值和输出如下所示。

示例 77：持有者的秘密

{
    "holderSecretHex": "8fc6cc3f65db4ba5e3ed63fe9d2bd57a9c7df9c7f6bf2b898b308d5493b07eb6"
}

示例 78：证明者 Nym

{
    "proverNymHex": "5e2087638f71057ef108f83923189a71cea1f7c4b4ef69afb473c9a7074ddf49"
}

示例 79：持有者秘密和证明者 Nym 承诺信息

{
  "secretProverBlind": "0d215067232c77c94a7572eb80794592090da8aff35cca53d2d528d059e70fce",
  "commitmentWithProof": "ab72f3e6d7a4185d100ede6ce7dde1c69db9a2128ad11d1b6991a018c340ca2672d7be636f153398be50f44ee434edf14322dd115f7527e770a0f0c41d8aeb2088d004f2703548db6ce15e2505368a1f686f20702aa9ff46bce301330ea0c4c16ef4d8bbf624064a60df3a563142d7b236cad6cf6bcf1f3694d0bf4c2b5ffce55bb26abc05e31f9aaf8b60674fefe02666f89c150c479694f4a89a9088b28a1e6e2cf0c2caaa01810d2e3a52853f3a2a"
}

holder_secret、prover_nym 和 secretProverBlind 需要由持有者保留并保持秘密。commitmentWithProof 值需要传达给颁发者。

在假名功能选项下添加基础证明的过程始于颁发者从持有者接收 commitmentWithProof 值，并为 signer_nym_entropy 生成一个密码学随机值。

示例 80：签名者 Nym 熵

{
    "signerNymEntropyHex": "25555cf635188a1c33989056f5129e6ab4be0e7c5cc588c48d308e0254eed140"
}

此示例将使用示例 27中所示的相同密钥材料，以及示例 50中所示的相同未签名文档，以及示例 51中所示的相同强制指针。这会产生与示例 52中所示相同的规范文档、与示例 53中所示相同的规范 HMAC 文档，以及与示例 54中所示相同的“添加基础证明转换”。

此示例使用与示例 55中相同的证明配置。这会产生与示例 56中相同的规范基础证明。将其与上述假设结合，会得到与示例 57中相同的基础哈希。

由于 featureOption 等于 "holder_binding_pseudonym"，第 3.3.2 基础证明序列化 (bbs-2023)节中的过程将产生如下所示的输出。这里使用了 [CFRG-Pseudonym-BBS-Signature] 的签名生成算法。请注意其中包含 signer_nym_entropy 和 featureOption 值，因为这些值需要传达给持有者。

示例 81：为持有者绑定和假名添加基础证明签名

{
  "bbsSignature": "9251f497cb002c19f959a760fa24c5e961df9cb8ff5fbaaef14f2b7f1f41649990c30bd8c1d373e878a5d120123d658a326141275eee7833352d611cc1c05175c9c0f0ddeb0fdec09ad1bfad8796e410",
  "bbsHeader": "3a5bbf25d34d90b18c35cd2357be6a6f42301e94fc9e52f77e93b773c5614bdf8eea112c04d89e133880f96766ebae73693f75f1bbcbbaa473dc06254bdec4fb",
  "publicKey": "a4ef1afa3da575496f122b9b78b8c24761531a8a093206ae7c45b80759c168ba4f7a260f9c3367b6c019b4677841104b10665edbe70ba3ebe7d9cfbffbf71eb016f70abfbb163317f372697dc63efd21fc55764f63926a8f02eaea325a2a888f",
  "hmacKey": "00112233445566778899aabbccddeeff00112233445566778899aabbccddeeff",
  "mandatoryPointers": [
    "/issuer",
    "/expirationDate"
  ],
  "signerNymEntropyHex": "25555cf635188a1c33989056f5129e6ab4be0e7c5cc588c48d308e0254eed140",
  "featureOption": "holder_binding_pseudonym"
}

最后，将上述值通过第 3.2.1 serializeBaseProofValue节的算法运行，生成如下所示的已签名基础文档中使用的 proofValue。

示例 82：用于持有者绑定和假名的已签名基础文档

{
  "@context": [
    "https://www.w3.org/2018/credentials/v1",
    "https://w3id.org/security/data-integrity/v2",
    "https://w3id.org/vdl/v1",
    "https://w3id.org/vdl/aamva/v1"
  ],
  "type": [
    "VerifiableCredential",
    "Iso18013DriversLicenseCredential"
  ],
  "issuer": {
    "id": "did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5",
    "name": "Utopia Department of Motor Vehicles",
    "url": "https://dmv.utopia.example/",
    "image": "https://dmv.utopia.example/logo.png"
  },
  "issuanceDate": "2023-11-15T10:00:00-07:00",
  "expirationDate": "2028-11-15T12:00:00-06:00",
  "name": "Utopia Driver's License",
  "image": "data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUg...kSuQmCC",
  "description": "A license granting driving privileges in Utopia.",
  "credentialSubject": {
    "type": "LicensedDriver",
    "driversLicense": {
      "type": "Iso18013DriversLicense",
      "document_number": "542426814",
      "family_name": "TURNER",
      "given_name": "SUSAN",
      "portrait": "data:image/jpeg;base64,/9j/4AAQSkZJR...RSClooooP/2Q==",
      "birth_date": "1998-08-28",
      "issue_date": "2023-01-15T10:00:00-07:00",
      "expiry_date": "2028-08-27T12:00:00-06:00",
      "issuing_country": "UA",
      "issuing_authority": "UADMV",
      "driving_privileges": [
        {
          "codes": [
            {
              "code": "D"
            }
          ],
          "vehicle_category_code": "D",
          "issue_date": "2019-01-01",
          "expiry_date": "2027-01-01"
        },
        {
          "codes": [
            {
              "code": "C"
            }
          ],
          "vehicle_category_code": "C",
          "issue_date": "2019-01-01",
          "expiry_date": "2017-01-01"
        }
      ],
      "un_distinguishing_sign": "UTA",
      "aamva_aka_suffix": "1ST",
      "sex": 2,
      "aamva_family_name_truncation": "N",
      "aamva_given_name_truncation": "N"
    }
  },
  "proof": {
    "type": "DataIntegrityProof",
    "cryptosuite": "bbs-2023",
    "created": "2023-08-15T23:36:38Z",
    "verificationMethod": "did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ",
    "proofPurpose": "assertionMethod",
    "proofValue": "u2V0IhlhQklH0l8sALBn5Wadg-iTF6WHfnLj_X7qu8U8rfx9BZJmQwwvYwdNz6Hil0SASPWWKMmFBJ17ueDM1LWEcwcBRdcnA8N3rD97AmtG_rYeW5BBYQDpbvyXTTZCxjDXNI1e-am9CMB6U_J5S936Tt3PFYUvfjuoRLATYnhM4gPlnZuuuc2k_dfG7y7qkc9wGJUvexPtYYKTvGvo9pXVJbxIrm3i4wkdhUxqKCTIGrnxFuAdZwWi6T3omD5wzZ7bAGbRneEEQSxBmXtvnC6Pr59nPv_v3HrAW9wq_uxYzF_NyaX3GPv0h_FV2T2OSao8C6uoyWiqIj1ggABEiM0RVZneImaq7zN3u_wARIjNEVWZ3iJmqu8zd7v-CZy9pc3N1ZXJvL2V4cGlyYXRpb25EYXRlwlggJVVc9jUYihwzmJBW9RKearS-DnxcxYjEjTCOAlTu0UA"
  }
}

如第 A.1.2 派生证明节中所述，我们使用模拟随机数生成过程，并演示 presentationHeader 的使用。此处使用示例 19中给出的相同 seed 和 presentationHeader。

要创建派生证明，持有者从一个包含基础证明的已签名文档开始。我们用于这些测试向量的基础文档来自上面的示例 72。第一步是运行第 3.2.2 parseBaseProofValue节的算法，以恢复 bbsSignature、bbsHeader、publicKey、hmacKey、 mandatoryPointers、signer_nym_entropy 和 featureOption，如下所示。

示例 83：为持有者绑定和假名恢复的基础签名数据

{
  "bbsSignature": "9251f497cb002c19f959a760fa24c5e961df9cb8ff5fbaaef14f2b7f1f41649990c30bd8c1d373e878a5d120123d658a326141275eee7833352d611cc1c05175c9c0f0ddeb0fdec09ad1bfad8796e410",
  "bbsHeader": "3a5bbf25d34d90b18c35cd2357be6a6f42301e94fc9e52f77e93b773c5614bdf8eea112c04d89e133880f96766ebae73693f75f1bbcbbaa473dc06254bdec4fb",
  "publicKey": "a4ef1afa3da575496f122b9b78b8c24761531a8a093206ae7c45b80759c168ba4f7a260f9c3367b6c019b4677841104b10665edbe70ba3ebe7d9cfbffbf71eb016f70abfbb163317f372697dc63efd21fc55764f63926a8f02eaea325a2a888f",
  "hmacKey": "00112233445566778899aabbccddeeff00112233445566778899aabbccddeeff",
  "mandatoryPointers": [
    "/issuer",
    "/expirationDate"
  ],
  "signerNymEntropy": "25555cf635188a1c33989056f5129e6ab4be0e7c5cc588c48d308e0254eed140",
  "featureOption": "holder_binding_pseudonym"
}

接下来，持有者使用 [CFRG-Pseudonym-BBS-Signature] 中的“验证和最终确定”操作，以同时验证签名并计算 nym_secret 值。此操作会使用 holder_secret、 prover_nym、 signer_nym_entropy 和 secret_prover_blind 等值。

示例 84：计算得到的 Nym 秘密

{"nymSecretHex":"f883d069aec1252f167b0880e8960d72fa2623e11b6967541a457aa5c3cb088"}

接下来，持有者需要指明希望向验证者披露哪些非强制语句（如果有），方法是指定用于选择性披露的 JSON 指针。在这种情况下，持有者披露与示例 62中给出的相同信息。这会产生与示例 63中所示相同的 revealDocument。

运行 § 4.4.3 CreateDisclosureData 会生成与示例 64中所示相同的派生组索引信息，以及与示例 65中所示相同的调整后强制索引和选择性索引。

在 3.2.3 serializeDerivedProofValue 中，我们基于中所示的相同 verfifier_id 计算 pseudonym。 3.2.3 serializeDerivedProofValue 的最终输出如下所示。请注意其中包含 featureOption 和计算得到的 pseudonym 值。

示例 85：用于持有者绑定和假名的披露数据

{
  "bbsProof":"94752c678297191b42617aca412377d4a5b3d7872779ffea31e0b418f50e95056d923a97e8dc156edc2a3a3a54e7b27cafa26a989fc3e8a8bc7a08b84e706a1863bd06c396b973b1af0da4f6c20ea463e124d2ad97060a25ccc3ff695c71977ba2e83a6468205d9e0bfb756089ad40dededab480eeb13cf00265f49824c5f89e23ac48d07fa3164823741df5c066bdc31a231a7d4fecb75c912adb800b1efe8da3cd26805ffa56775b1c32da34e36e9716a4da909fa6803ca0aa2df2d82f697229ccb210503274d4d61c7386a44e9fb459c020fbcd62c7f437da8ffd5ea7e56d2c4e7d9c3f593b2a964346f24f71bec30a2c3ededa0bd3707e2e06cac2dddb66762135a229dc09b67fa61d690d33be78150bc60f3655ac1063f96d6fe95a260004c7bf9e924cc7439c6426f951d0cee963985557097788d2387b72c9aeb390f9a4fa4b519bc11ca81dfca8a4fd3c77805e1a0ef5c165b16c3cdc564e7a5593f0ddd0560f3514393c1b305d3950c29fbb72cc8b58979843cec768e9a77b14f70704771f877c49fc0d0d4ffbe3f0aaf8e472a83b14e32e46207d5012e79b9bcfc6197c858eb18ad97f589dddb5dc45e9ef65f482d3c07fbcbfef92bf293643539fffc94a8bc98b3b4dd3335bb8b248aa606a751330516f148211d5f2d513e02d45ec5a51add1f878948a673a0349d7cb4417b1f9c16945e1f607bdecf6ca3b96a64fb14ee1fc5dbecf751be23041df32842367285f2b3b02c13512c28c0e7671874699b9ff169e35f91debc796fd487d3e41dcc5f12949558f2705be3e8195d4c93a6c149dcb5f63e62d3ce0bf51034021251b74ed2a1186fd77741ce3bf51f57f19a9d4a9e6315a88024062269a9fec426a73199882113168573da451ca38aeacf28f7eef3892181f0bc511562fba00d035f608c4f85579fc9614618763fa4e6c2210184e12f83e1c22078dd4ca488de41dbf2c146a2e0c47137be7f006c6810f44746a819229349b50ca59a51f7c51bb62cacc1a1cc4a6f089680514d41800da57470ef275f390eb4a08db78789e71bd32bd8929961c9f79d1ca071a2608a393f162c2f644584473f11b41cc35c838f11fbd2adf47051829d378ac9dc151e64bc70cd21b2ea6bca3f77b9c2b35abcebb0ecbf1c09365a8e372a2fce74b97088c9e9505c5c0272a4d6959bec54911a99b6c8a1654395f0cd4e7d38d695ab45875ecc535439dde3fb3d4658d9ff9427d8e36d7bd19ea53fb875c4b138f6ffc06bfd496b1a744a63283ebc0fa34ea828d98",
  "labelMap":{"dataType":"Map","value":[["c14n0","b1"],["c14n1","b2"],["c14n2","b0"]]},
  "mandatoryIndexes":[0,1,2,5,6,8,9],"adjSelectiveIndexes":[0,1,5,7,10,16],
  "presentationHeader":{"0":17,"1":51,"2":119,"3":170},
  "pseudonym":"838607ff2c8dcb2a0740ef13c2c87418efb57559243232a69daf1e294dd092af833ad4df1e99e0034c737b932916f378",
  "featureOption":"holder_binding_pseudonym",
  "lengthBBSMessages":23
}

最后，将上述披露数据用于第 3.2.3 serializeDerivedProofValue节中的算法，我们将得到如下所示的已签名派生（公开）文档。

示例 86：用于持有者绑定和假名的已签名派生文档

{
  "@context": [
    "https://www.w3.org/2018/credentials/v1",
    "https://w3id.org/security/data-integrity/v2",
    "https://w3id.org/vdl/v1",
    "https://w3id.org/vdl/aamva/v1"
  ],
  "type": [
    "VerifiableCredential",
    "Iso18013DriversLicenseCredential"
  ],
  "issuer": {
    "id": "did:key:z6MkjxvA4FNrQUhr8f7xhdQuP1VPzErkcnfxsRaU5oFgy2E5",
    "name": "Utopia Department of Motor Vehicles",
    "url": "https://dmv.utopia.example/",
    "image": "https://dmv.utopia.example/logo.png"
  },
  "expirationDate": "2028-11-15T12:00:00-06:00",
  "credentialSubject": {
    "type": "LicensedDriver",
    "driversLicense": {
      "type": "Iso18013DriversLicense",
      "issuing_country": "UA",
      "driving_privileges": [
        {
          "codes": [
            {
              "code": "D"
            }
          ],
          "vehicle_category_code": "D",
          "issue_date": "2019-01-01",
          "expiry_date": "2027-01-01"
        },
        {
          "codes": [
            {
              "code": "C"
            }
          ],
          "vehicle_category_code": "C",
          "issue_date": "2019-01-01",
          "expiry_date": "2017-01-01"
        }
      ]
    }
  },
  "proof": {
    "type": "DataIntegrityProof",
    "cryptosuite": "bbs-2023",
    "created": "2023-08-15T23:36:38Z",
    "verificationMethod": "did:key:zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ#zUC7DerdEmfZ8f4pFajXgGwJoMkV1ofMTmEG5UoNvnWiPiLuGKNeqgRpLH2TV4Xe5mJ2cXV76gRN7LFQwapF1VFu6x2yrr5ci1mXqC1WNUrnHnLgvfZfMH7h6xP6qsf9EKRQrPQ",
    "proofPurpose": "assertionMethod",
    "proofValue": "u2V0Jh1kDkJR1LGeClxkbQmF6ykEjd9Sls9eHJ3n_6jHgtBj1DpUFbZI6l-jcFW7cKjo6VOeyfK-iapifw-iovHoIuE5wahhjvQbDlrlzsa8NpPbCDqRj4STSrZcGCiXMw_9pXHGXe6LoOmRoIF2eC_t1YImtQN7e2rSA7rE88AJl9JgkxfieI6xI0H-jFkgjdB31wGa9wxojGn1P7LdckSrbgAse_o2jzSaAX_pWd1scMto0426XFqTakJ-mgDygqi3y2C9pcinMshBQMnTU1hxzhqROn7RZwCD7zWLH9Dfaj_1ep-VtLE59nD9ZOyqWQ0byT3G-wwosPt7aC9Nwfi4GysLd22Z2ITWiKdwJtn-mHWkNM754FQvGDzZVrBBj-W1v6VomAATHv56STMdDnGQm-VHQzuljmFVXCXeI0jh7csmus5D5pPpLUZvBHKgd_Kik_Tx3gF4aDvXBZbFsPNxWTnpVk_Dd0FYPNRQ5PBswXTlQwp-7csyLWJeYQ87HaOmnexT3BwR3H4d8SfwNDU_74_Cq-ORyqDsU4y5GIH1QEuebm8_GGXyFjrGK2X9Ynd213EXp72X0gtPAf7y_75K_KTZDU5__yUqLyYs7TdMzW7iySKpganUTMFFvFIIR1fLVE-AtRexaUa3R-HiUimc6A0nXy0QXsfnBaUXh9ge97PbKO5amT7FO4fxdvs91G-IwQd8yhCNnKF8rOwLBNRLCjA52cYdGmbn_Fp41-R3rx5b9SH0-QdzF8SlJVY8nBb4-gZXUyTpsFJ3LX2PmLTzgv1EDQCElG3TtKhGG_Xd0HOO_UfV_GanUqeYxWogCQGImmp_sQmpzGZiCETFoVz2kUco4rqzyj37vOJIYHwvFEVYvugDQNfYIxPhVefyWFGGHY_pObCIQGE4S-D4cIgeN1MpIjeQdvywUai4MRxN75_AGxoEPRHRqgZIpNJtQylmlH3xRu2LKzBocxKbwiWgFFNQYANpXRw7ydfOQ60oI23h4nnG9Mr2JKZYcn3nRygcaJgijk_FiwvZEWERz8RtBzDXIOPEfvSrfRwUYKdN4rJ3BUeZLxwzSGy6mvKP3e5wrNavOuw7L8cCTZajjcqL850uXCIyelQXFwCcqTWlZvsVJEambbIoWVDlfDNTn041pWrRYdezFNUOd3j-z1GWNn_lCfY42170Z6lP7h1xLE49v_Aa_1Jaxp0SmMoPrwPo06oKNmKMAAQECAgCHAAECBQYICYYAAQUHChBEETN3qlgwg4YH_yyNyyoHQO8Twsh0GO-1dVkkMjKmna8eKU3Qkq-DOtTfHpngA0xze5MpFvN4Fw"
  }
}

数据完整性 BBS 密码套件 v1.0

使用基于配对的密码学实现不可关联的数据完整性

摘要

本文档的状态

1. 简介

1.1 术语

1.2 一致性

2. 数据模型

2.1 验证方法

2.1.1 Multikey

2.2 证明表示

2.2.1 DataIntegrityProof

3. 算法

3.1 实例化密码套件

3.2 bbs-2023 函数

3.2.1 serializeBaseProofValue

3.2.2 parseBaseProofValue

3.2.3 serializeDerivedProofValue

3.2.4 parseDerivedProofValue

3.3 bbs-2023

3.3.1 创建基础证明 (bbs-2023)

3.3.2 基础证明 序列化 (bbs-2023)

3.3.3 添加派生证明 (bbs-2023)

3.3.4 派生证明 序列化

3.3.5 验证派生证明 (bbs-2023)

4. 可选功能

4.1 匿名持有者绑定

4.2 凭据绑定假名

4.3 持有者绑定和假名

4.4 可选功能摘要

5. 安全注意事项

5.1 基础证明的安全属性

5.2 派生证明的安全 属性

6. 隐私注意事项

6.1 选择性披露 和数据泄露

6.2 选择性披露 和不可关联性

6.2.1 通过 密码学制品进行关联

6.2.2 通过 VC 处理进行关联

6.2.3 通过 JSON-LD 节点标识符进行关联

6.2.4 通过证明选项和强制披露进行关联

6.2.5 通过 持有者选择性披露进行关联

6.2.6 基于外部 VC 系统 的关联

A. 测试向量

A.1 基线基本示例

A.1.1 基础证明

A.1.2 派生证明

A.2 基线增强示例

A.2.1 基础证明

A.2.2 派生证明

A.3 匿名持有者绑定 功能

A.3.1 持有者绑定 承诺生成

A.3.2 持有者绑定基础证明

A.3.3 持有者绑定派生 证明

A.4 凭据绑定假名 功能

A.4.1 证明者 Nym 承诺 生成

A.4.2 假名基础证明

A.4.3 假名派生证明

A.5 持有者绑定和 假名功能

A.5.1 持有者秘密和证明者 Nym 承诺生成

A.5.2 持有者绑定 和假名基础证明

A.5.3 持有者 绑定和假名派生证明

B. 致谢

C. 参考文献

C.1 规范性参考文献

C.2 信息性参考文献

3.3.2 基础证明序列化 (bbs-2023)

3.3.4 派生证明序列化

5.2 派生证明的安全属性

6.1 选择性披露和数据泄露

6.2 选择性披露和不可关联性

6.2.1 通过密码学制品进行关联

6.2.5 通过持有者选择性披露进行关联

6.2.6 基于外部 VC 系统的关联

A.3 匿名持有者绑定功能

A.3.1 持有者绑定承诺生成

A.3.3 持有者绑定派生证明

A.4 凭据绑定假名功能

A.4.1 证明者 Nym 承诺生成

A.5 持有者绑定和假名功能

A.5.2 持有者绑定和假名基础证明

A.5.3 持有者绑定和假名派生证明