C2D Provider Identity and T&Cs

[MBadea17]

To be able to assess the compliance and terms of a Compute-provider, selected for Compute-to-Data, the terms and conditions and the identity of the compute provider must be documented and accessible to the end user. At least terms and conditions and proof of identity must be accessible through the node / compute-environment API and should become visible in the market, especially if the data provider is NOT the compute provider.
Solution: Add the fields / information to the provider/node APIs.

[MBadea17]

1. Add one endpoint that will deliver the following

• Imprint
• T&Cs
• Privacy Policy

Either provided as a JSON document or as an attachment (similar to license documents). Or the JSON could include the link to the document.

2. Add one endpoint to deliver the signed VC in the form of a signed JWT.
   The VC will be added through an env var.

[MBadea17]

Requires an update to ocean.js, too.

[AdriGeorge]

we won't update ocean js, just the node in rootEnpoint

[AdriGeorge]

We can use this types:

type NodeInfoType = 'text' | 'url'

type NodeInfoEntry = {
  type: NodeInfoType
  value: string
}

type NodeOwnerInfo = {
  NODE_IMPRINT?: NodeInfoEntry
  NODE_TC?: NodeInfoEntry
  NODE_PRIVACY_POLICY?: NodeInfoEntry
  NODE_PROOF_OF_IDENTITY?: NodeInfoEntry
}

and example will be:
NODE_OWNER_INFO={
  "NODE_IMPRINT": {
    "type": "text",
    "value": "Ocean Node Inc, Berlin"
  },
  "NODE_TC": {
    "type": "url",
    "value": "https://example.com/terms"
  },
  "NODE_PRIVACY_POLICY": {
    "type": "url",
    "value": "https://example.com/privacy"
  },
  "NODE_PROOF_OF_IDENTITY": {
    "type": "url",
    "value": "https://example.com/proof.json"
  }
}

[AdriGeorge]

#85