Related: OPS-1, OPS-3, BL-18, discussion #132
Why this would help
As we invite communities and organizations to try DIN, it would help to have a short introduction we can share. The conversations we have each had with interested ecosystems are a useful starting point, but we still need a common explanation of what participation involves and what we can offer.
This would give anyone starting a conversation a consistent starting point and help potential partners decide whether DIN is a good fit.
Suggested next step
Agree on an owner and reviewer, then draft a short partner-facing document covering:
- What DIN is and why a community might want to take part.
- Ways to contribute: running nodes, bringing datasets or training projects, or helping with development.
- What participants need, including hardware, time, and any costs.
- What support is available and the limitations of an experimental testnet.
- What is confirmed or still undecided about fees, rewards, future token distribution, and testnet resets.
We could build the first draft from the conversations already under way, rather than inventing a process from scratch. Open policy questions should be clearly marked and reviewed before the document is shared externally.
Expected outcome
A reviewed introduction with a clear contact or next step for interested partners. Any internal outreach checklist can be a separate follow-up.
This task documents the team's agreed position; it does not decide partnership terms or reward policies.
Related: OPS-1, OPS-3, BL-18, discussion #132
Why this would help
As we invite communities and organizations to try DIN, it would help to have a short introduction we can share. The conversations we have each had with interested ecosystems are a useful starting point, but we still need a common explanation of what participation involves and what we can offer.
This would give anyone starting a conversation a consistent starting point and help potential partners decide whether DIN is a good fit.
Suggested next step
Agree on an owner and reviewer, then draft a short partner-facing document covering:
We could build the first draft from the conversations already under way, rather than inventing a process from scratch. Open policy questions should be clearly marked and reviewed before the document is shared externally.
Expected outcome
A reviewed introduction with a clear contact or next step for interested partners. Any internal outreach checklist can be a separate follow-up.
This task documents the team's agreed position; it does not decide partnership terms or reward policies.