- From: Steve Capell <steve.capell@gmail.com>
- Date: Wed, 9 Mar 2022 18:11:12 +1100
- To: Joe Andrieu <joe@legreq.com>
- Cc: Credentials Community Group <public-credentials@w3.org>
Received on Wednesday, 9 March 2022 07:11:28 UTC
“If you need correlatable identifiers for particular points in the transaction, put that in a VC (with a unique nonce), put a hash of the VC on chain, and send the VC separately.” Could you unpack that a bit? It’s the exporter (did) that needs to prove their identity using a VC issued by a trusted authority (eg a trust anchor such a government) that confirms the DID == public identity. Then the exporter DID issues a trae document such as an invoice If the exporter DID is ephemeral then the authority issued VC is equally ephemeral because you need a new one for every ephemeral DID. I’m not sure that the trust anchor will be keen to support that volume of VCs. Or am I missing something in your flow ? Steven Capell Mob: 0410 437854 > On 9 Mar 2022, at 1:26 pm, Joe Andrieu <joe@legreq.com> wrote: > > . If you need correlatable identifiers for particular points in the transaction, put that in a VC (with a unique nonce), put a hash of the VC on chain, and send the VC separately.
Received on Wednesday, 9 March 2022 07:11:28 UTC