Enable presentationHeader bytes to be optionally passed when deriving a BBS proof

[dlongley]

It would also then need to be included in the serialized disclosure proof CBOR.

[Wind4Greg]

How would we specify this? My simple approach would be:

To add the BBS presentation header (octet string) as an optional input to the 3.3.6 Add Derived Proof (bbs-2023), which would pass it to 3.2.3 createDisclosureData where it is used by BBS proofGen, then it needs to be passed into an updated 3.2.6 serializeDerivedProofValue which includes it in the CBOR/base64 encoded thing.

I don't really see adding it as a "proof option". Do you @dlongley?

For those wondering about some of the uses of the BBS presentation header see 6.4. Presentation Header Selection where use is RECOMMENDED in most use-cases.

[dlongley]

+1 to the approach with the name: presentationHeader

[dlongley]

This was my issue and it's been addressed now, closing.