P0 means we shall complete before Mainnet announcement.
| Task No | Tasks | Priorities | Status | DRI | Notes / Updates |
|---|---|---|---|---|---|
| Legal | |||||
| Legal 2 | finalize the naming of this new legal entity (Non Profit Org NPO) | P0 | Done | @Ming Jiang Ken | Ming Ken to sync on Wednesday |
| Legal 1 | Complete the full search of Telescope and Mantis | P0 | Done | @Ming Jiang | |
| Legal 3 | Work with Messari to legal to agree on types of new entity and kick off legal entity application | P0 | Done | @Ming Jiang | |
| Legal 7 | New entity member list (do we allow entity to join or individual only) and appointment | P0 | @Leo Liang @Ming Jiang | We only need a few roles in the entity (registration) | |
| Legal 8 | CB exception to use 3P communication channel for this project | P0 | @Ming Jiang | ||
| Legal 9 | Application for Ming/Leo to join new entity | P0 | @Ming Jiang | Ming will first come up with a version . Now in legal/management review | |
| Contents | Priorities | Status | DRI | Notes/Updates | |
| Contents 1 | label taxonomy finalized for the launch version | ||||
| (including documents for definitions and examples for each category) | P0 | @TY | comments | ||
| Contents 2 | First set of data to be available for public by launch date reviewed and ready | P0 | @Yi Zhang | ||
| Contents 3 | Documents for User Tutorials and Use Cases | P3 | |||
| Contents 4 | Dashboard (total label number, distribution per categories/networks etc) | P1 | @Yi Zhang | on hold, for the launch event, we will refrain from advertising it. | |
| Contents 5 | Do we want to register ENS etc? | P1 | After legal 1 | ||
| Marketing and PR | Priorities | Status | DRI | Notes/Updates | |
| M 1 | website design and implementation | P0 | @Yi Zhang | Had discussed with Ming regarding improvements. Working on the content for FAQ sections. |
Waiting for final name of our project to update the design and register domain name | | M 2 | website legal review | P0 | | @Ming Jiang | | | M 3 | Contributor statement legal review | P0 | | @Ming Jiang Ken | | | M 4 | Media outreach. (CoinGecko etc) | P1 | | @Ming Jiang | | | M 5 | Medium post | P1 | | | | | M 6 | Form design and implementation so potential contributors or partners can fill out to engage | P1 | | @Yi Zhang | | | | | | | | | | Contributor | | Priorities | Status | DRI | Notes/Updates | | C 1 | Dune | P2 | | | | | C 2 | ChainLink | P1 | | @Ming Jiang | | | C 3 | Flipside | P2 | | | | | C 4 | Etherscan | P2 | | | | | | | | | | | | User | | Priorities | Status | DRI | Notes/Updates | | U 1 | user feedback loop design and set up (discord, invite, review and validate, summary/analysis, survey, from 3d Party channels etc) | P2 | | | | | | | | | | | | Partner | | Priorities | Status | DRI | Notes/Updates | | P 1 | Snowflake to draft contract with OpenChainMeta and Sign off | P2 | | @Ming Jiang | won’t make it before launch | | P2 | Have the first dataset available on Snowflake | P2 | | @Ming Jiang | won’t make it before launch | | P3 | ChainLink draft and sign off (serve label onto Chain) | P1 | | @Ming Jiang | | | P4 | ChainLink Oracle Implementation | P2 | | | | | P5 | TiDB contract and first data available | P0 | | @Ming Jiang @Yi Zhang | Serve ready and Chaintool will fund the related service cost | | P6 | Base Partnership | P2 | | | | | | | | | | | | Funding | | Priorities | Status | DRI | Notes/Updates | | F 1 | Discuss with Snowflake for Donation | P1 | | @Ming Jiang | | | F 2 | ChainLink | P1 | | @Ming Jiang | | | F 3 | Coinbase | P1 | | @Ming Jiang | | | F 4 | Messari | P1 | | Ken | | | F 5 | ChainTool | P1 | | @Yi Zhang | | | F 6 | TiDB | P1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Background: When we approach a potential partner, they have a bunch of common questions (e.g. whether the project is profitable? whether you will form a DAO?) before determining if they can join us. We focus on answering those key questions commonly raised by them. And, those information we will used to present in our project official website to accompany our launch event in Mainnet Conference.
Questions: