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.

By CoinDock Editorial Published Last reviewed

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

  1. No financial advice. Explain mechanics; do not tell people what to buy, sell, or when.
  2. Disclose paid promotion, in the post, every time — not once in a bio.
  3. Disclose holdings when discussing a token you hold.
  4. No coordinated buying or selling, however casually framed.
  5. No misrepresentation of partnerships, audits, listings, or identity.
  6. Substantiate factual claims — be able to point at where they can be verified.
  7. 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

  1. What happened, factually
  2. Impact — who is affected, and how
  3. What we are doing now
  4. What we do not yet know
  5. 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

How-to

Reference

Related on CoinDock Community

Build Your Coin Community

Continue your CoinDock journey.

Go