Status: Draft/RFC

Key dates:

Sept 1:

Step 1:

Sept 15: mainnet announcement of Openmeta protocol

around Sept/Oct:

• consumption Interface:
  • 1. batch access (
  • 2. single-query item
• standardized onboarding process

Technologies

1. P0 - Build an identity system to secure contributor identities from impersonation and ensure the integrity of uploaded content.
   1. We need a way for each contributor to cryptographically identify themselves and ensure the integrity and authenticity of their uploaded payloads.
   2. We can use Ethereum-based keypair
2. P0 - Maintain transparent and diverse metrics for contribution
   1. Quality is NOT everything.
   2. Diversity on category of labels are very important.
   3. May need to have metrics like this
      1. Month, Category, # Label, organization
3. P1 - All payloads need to have a way to prove ownership.
   1. Option A: Out-of-band payload signing (a sidecar .sig file to prove the owner)
   2. Option B: add a special structure (aka a field in the metadata to indicate the ownership of the payload)
   3. Option C: use the private key to encode the payload and the public key - which is available in our repo to decode.
4. P1 - All payload uploaded must be stored permanently with

Organization: