CoinDock Community · Resource
Community Resources — Templates and Checklists
Copy these into your own notes. Each comes from a guide in this pillar where the reasoning is explained.
Publish-first checklist
Before recruiting a single community member, publish on a domain you control:
- Contract address, exactly, with the chain stated
- Official channels, listed authoritatively so members can verify
- "We will never DM first"
- "Nobody will ever ask for your seed phrase"
- "We never run giveaways requiring you to send funds"
The highest-value hour of work in the whole exercise. Impersonation begins as soon as you are visible.
Community rules template
- No financial advice. Explain mechanics; do not tell people what to buy, sell, or when.
- Disclose paid promotion, in the post, every time — not once in a bio.
- Disclose holdings when discussing a token you hold.
- No coordinated buying or selling, however casually framed.
- No misrepresentation of partnerships, audits, listings, or identity.
- Substantiate factual claims — be able to point at where they can be verified.
- Criticism is welcome; personal abuse is not.
Moderation posture: hard on fraud, impersonation, manipulation and abuse. Light on opinion, criticism and hard questions.
Project update structure
1. Since last time — what actually shipped
2. Did not happen — what slipped, and why
3. Next period — what you are working on
4. Numbers — verifiable metrics, same ones each time
5. Open questions — what you do not yet know
Section 2 is the one that builds credibility, and almost nobody includes it.
Pick a cadence you can sustain during a bad month, not an enthusiastic one.
Incident update format
- What happened, factually
- Impact — who is affected, and how
- What we are doing now
- What we do not yet know
- When the next update will come — then publish it on time
Rules: publish before you have all the answers; do not minimise; "we do not know yet" is a complete answer; say what changes so it does not recur.
Transparency disclosure list
| Item | Must include |
|---|---|
| Contract | Address, chain, verified source |
| Supply | Total, circulating with date measured |
| Allocation | Percentages and absolute counts |
| Vesting | Table of dates and amounts, lock contract addresses |
| Near-term unlocks | Anything in the next 90 days, flagged |
| Treasury | Addresses, purpose, who can move it |
| Contract powers | Every privileged function, its controller, key type |
| Accountability | Named roles, decision authority, monitored contact |
| Audit | Report, auditor name, version audited, findings resolution |
The test for every item: could someone verify this without contacting us?
Promotion checklist
- Every paid relationship disclosed, in the promotion, every time
- No price, return, or performance claim
- Every factual claim backed by something verifiable
- Audit claims match what the report actually says
- Partnerships agreed in writing and known to the other party
- No purchased followers, engagement, volume, or holders
- Contract address included
- "We will never DM first" included
- Promoters contractually required to disclose
The test: could someone act on this, lose money, and reasonably say I told them to?
AMA checklist
- Questions collected in advance, publicly visible
- Hardest questions identified and answers prepared
- Hard questions answered first
- "I do not know" used where true, with a follow-up commitment
- No price commentary
- No unconfirmed announcements
- Hostile questions answered on substance, not tone
- Transcript published within a day
- Commitments tracked and followed up
Metrics worth tracking
Ignore (all purchasable): follower count, member count, message volume, engagement rate, impressions, giveaway participation.
Track instead:
- Unprompted substantive questions
- Members answering each other without the team
- Retention through quiet periods
- Bug reports and criticism received
- Independent content nobody paid for
- Holders reporting impersonation before you notice
- Repeated support questions declining over time
- Preventable losses among holders — the one that matters
Launch-week checklist
- Contract address published before the announcement
- Community warned that impersonators will appear
- Someone monitoring replies during and after
- No giveaway running alongside (it gives fake ones cover)
- Liquidity live before announcing
- Spokesperson decided for the first incident
- Follow-up update planned regardless of how it goes
Guides
Concepts
- Build a Healthy Token Community
- CoinDock Community Guidelines
- Project Transparency Guide
- Token Announcement Strategy
- Holder Education
How-to
- How to Launch a Token Community
- How to Write Project Updates
- How to Host a Project AMA
- How to Promote a Token Responsibly
- How to Educate Token Holders
Reference
Related on CoinDock Community
-
How to Write Project Updates
The update that determines your credibility is the one reporting something going wrong. Most projects have not planned h...
-
Listing Resources
Working templates you can copy into your own application preparation.
-
Build a Healthy Token Community
Almost all content on this subject is written by agencies selling growth services. This is not, and the advice differs s...
-
CoinDock Community Guidelines
The rules for CoinDock community spaces, and the reasoning behind each one.
-
How to Launch a Token Community
Set up the security rules before the members arrive. Retrofitting them after an impersonation incident is much harder.
Build Your Coin Community
Continue your CoinDock journey.
Go