Decentralized storage (IPFS/IPNS or similar) as DDO metadata storage

[georgevlada]

Storage Specifications - Updates
https://docs.oceanprotocol.com/developers/storage

Additions for Encrypted Content
Two new keys have been introduced to specify encryption details for stored content. These keys are optional and indicate whether the content is encrypted:

encryptedBy: The public node address that encrypted the file.
encryptMethod: Specifies the encryption method used by the entity referenced in encryptedBy. Acceptable values are "ecies" or "aes".

Example for Encrypted URL Type:

{
  "remote": {
    "type": "url",
    "url": "https://file.com/ddo.json",
    "method": "get",
    "encryptedBy": "[node_id]",
    "encryptedMethod": "AES/ECIES"
  }
}

Metadata - Updates
https://docs.oceanprotocol.com/developers/metadata

Creating or Updating Metadata
Metadata can be created or updated using the setMetadata function at the contract level. The Decentralized Data Object (DDO) can be directly sent to this function, adhering to the specifications outlined at DDO Specification (https://docs.oceanprotocol.com/developers/ddo-specification). Alternatively, a structured format can be used for the DDO to be downloaded from the specified storage type and subsequently stored in the Indexer (Aquarius).

Example - URL Type Unencrypted:

{
  "remote": {
    "type": "url",
    "url": "https://file.com/ddo.json",
    "method": "get"
  }
}

Example - URL Type Encrypted:

{
  "remote": {
    "type": "url",
    "url": "https://file.com/ddo.json",
    "method": "get",
    "encryptedBy": "[node_address]",
    "encryptedMethod": "AES/ECIES"
  }
}