Trustless *and* convenient secret sharing, via new DT template via (a) Sapphire OR (b) threshold cryptography

[trentmc]

This is a possible future feature. Not planned yet.

Use cases

There are many possible applications where the user just wants to share a (small) secret. Including:

• Web2-style data sharing, where the secret = Oauth2 tokens, that combines with a public url. Like we see with all REST APIs
• sharing passwords, LastPass style
• Predict-ETH / challenge DF results sharing . Right now we need to use data NFTs & encrypting with judges' public keys. It's sloppy
• small AI models
• sharing urls, Ocean-style. Caveat: only for applications where DDOS is not a problem. Currently Ocean solves this by using Provider to stream.

Status quo

Right now Ocean offers either trustless, or convenient, but not both

• convenient: Provider run by 3rd party (OPF or other) using DT template 1 or 2. You need to trust the Provider runner because they see the decrypted url
• trustless: Provider run by you "". Inconvenient because you have to run it.

What we want

• trustless and convenient
• but for many possible use cases, not just sharing urls
• bonus: shouldn't need Provider at all. This makes it more reliable / web3-native (and that counts for a lot!)

How

• A new DT template
• That uses either (a) Sapphire , (b) threshold cryptography via Lit Protocol or Keep Network, or (c) Emblem Vault or maybe EIP6551
• With appropriate support in ocean.py, then ocean.js. Putting it in ocean.py first (this github issue) because we can prototype it here