MDIP Protocol - Non-Functional Launch Action Plan

[Flaxscrip]

GOAL: to explore and document activities required & desired for maturing MDIP governance and readiness for its next release.

As the protocol engages with its first 3rd party players, we are receiving new requirements and expectations with regards to the maturity and production-readiness of our MDIP protocol implementation.

Out of this discussion, I will open either:

• MDIP issues for action by protocol team or,
• Confluence action items that will likely become SELFID requirements

Proposed Launch Action Plan and Discussion Points

1. Define desired level of Community Development, Support and associated budgets
2. Post IP filing MDIP brand and website review, vision, goals, and associated budgets definition
3. Need simple protocol-level wallets (cli and webui) with support for seed key encryption (functional - selfid?)
4. Define desired Keymaster packaging systems (ex: npm, sdks, kubernetes, gcloud, aws, digital ocean, etc - selfid?)
5. 3rd party MDIP protocol code audit and quality certification
6. Launch support for first wave of Mainnet registries (BTC & FTC?) (functional - protocol)
7. Engagement and registration with DID industry standards organizations (W3C/WoT, DIF, etc)
8. Define post-launch protocol Governance model