Encrypt metadata and supporting documents for multiple parties

[sichen1234]

Right now the supporting document for an emissions token is encrypted for one party, the emissions auditor, using their key. The metadata is not encrypted.

Could the documents be encrypted for multiple parties, for example, the contract owner, the recipient of the emissions audit, and the auditors.

Could the metadata be encrypted the same way.

Could the data be encrypted and distributed to parties on demand, for example by the contract owner and the recipient of the emissions audit?

[brioux]

n-of-m multisig can solve the multi party problem by supplying all of the authorized public keys during encryption. Where does the encryption currently take place?

[sichen1234]

Interesting. Do you have any examples of this? Encryption is currently done during the

npm run supply-chain:cli -- -processrequests

step. When an auditor is chosen, the document is encrypted with their public key and placed on IPFS.

---

Si Chen Open Source Strategies, Inc.

Why open source and blockchain for carbon accounting? Video https://www.youtube.com/watch?v=eNM7V8vQCg4 and Blog Post https://www.opensourcestrategies.com/2022/06/01/why-open-source-carbon-accounting/

On Thu, Jul 14, 2022 at 12:22 PM Bertrand Rioux @.***> wrote:

n-of-m multisig can solve the multi party problem by supplying all of the authorized public keys during encryption. Where does the encryption currently take place?

— Reply to this email directly, view it on GitHub https://github.com/hyperledger-labs/blockchain-carbon-accounting/issues/578#issuecomment-1184812181, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANAS4LHXYLQMBY2CKQG6ZDVUBSHNANCNFSM53QHI4NQ . You are receiving this because you authored the thread.Message ID: <hyperledger-labs/blockchain-carbon-accounting/issues/578/1184812181@ github.com>