This checklist helps us start useful conversations with potential DIN partners and make sure everyone knows what happens next. It supports OPS-1’s goal of finding 2–3 validator partners, while also helping us follow up with people interested in training models or contributing in other ways.
- Read the partner introduction, including what is settled and what is still being decided, so we share a consistent explanation of DIN.
- Check with the technical onboarding lead what the partner can try today, which network and version to use, and which guide to share.
- Start with a trial small enough for the team to support.
Be clear about what is still being decided. Participation does not guarantee income or a future token allocation. Validators can lose staked test tokens for certain missed duties or for results that differ from the agreed outcome; confirm the rules for their trial before they stake. Testnet balances, stakes, models, and participation records should be treated as temporary.
If a question needs an answer we do not have yet, note it and arrange a follow-up.
Use these as conversation prompts:
- What interests you about DIN? Would you like to help run the network as a validator, train a model, or contribute in another way?
- What would you like to try? What model or task do you have in mind, what kind and approximate amount of data would you use, and what would make the trial worthwhile?
- Who would take part? Roughly how many people are involved, and who would coordinate on your side?
- What resources do you have? Discuss available computers, storage, internet access, time, and any setup help needed.
- What needs to stay private? Understand what can be shared and bring unresolved questions to the technical team. Keeping raw data on someone’s computer does not by itself guarantee privacy.
For partners bringing a training project, share What can I train on DIN?.
The first conversation should give us enough information to suggest a useful next step. Detailed technical questions can follow during onboarding.
Before wrapping up, confirm:
- Who follows up with the partner.
- Who leads the onboarding call.
- Who helps with setup, including a wallet, test ETH, staking where needed, and IPFS storage.
- What happens next, who will do it, and by when.
One person may cover several responsibilities. OPS-1 identifies Umer for technical onboarding calls and Operations/Interns for outreach; confirm availability for each partner.
How could we keep one shared record of partner conversations so we know who is following up and what happens next? One option could be a GitHub Discussion with a short entry for each partner. Would that work for the team, or would another approach be easier to maintain?