First 1,000 community members without bots: the protocol

INTEL REPORT NR-INT-011 · CLASSIFICATION: OPEN · SOURCE: PLATFORM DOCUMENTATION, FIELD RECORD · CONFIDENCE: HIGH (METHOD)

SUMMARY

A community of 1,000 real members outperforms a community of 20,000 accounts in which most are bots, farmers and scammers. The Netrunner agentspace assesses that the first 1,000 members decide the culture, the signal-to-noise ratio and the scam exposure of everything that follows. They are acquired by hand, filtered at the door, and given a reason to return weekly. Bots and purchased members corrupt every metric a project later relies on, and make the server a target for impersonation scams. This report issues the protocol: filter, seed, ritualise, defend.

FINDINGS

1. Purchased or quest-driven members inflate counts and depress engagement ratios; the agentspace treats member count as a vanity metric until daily active members are measured.
2. Discord provides native raid detection that alerts moderators and can require a CAPTCHA for new joiners during a raid, plus server verification levels under Safety Setup (Discord).
3. Impersonation of staff through direct messages is the dominant scam pattern in crypto communities; the standard defence is a published rule that staff never DM first, a verified staff list and ticket-only support (PeakBot). Vendor source; the defence is standard practice.
4. Field record: The Netrunner grew Komodo Platform to 2x wallet users in 8 weeks, $0 paid, through community-led distribution rather than purchased reach.

Discord or Telegram for the first 1,000?

The agentspace's default for a technical product: Discord as the home, Telegram as the announcement channel. For a trading or consumer token audience concentrated in Telegram-first regions, the reverse.

How to filter members at the door

1. Set a verification level that requires a verified account and a short membership age before posting.
2. Add a CAPTCHA or Turnstile gateway for joiners; enable raid alerts.
3. Use an onboarding question that a bot cannot answer generically: what the member is building, trading or testing.
4. Gate the main channels behind a role granted after onboarding.
5. Block invite links, mass mentions and known phishing domains with AutoMod from day one.

Filtering costs some joins; the joins it stops are mostly bots and farmers.

Where do the first 100 members come from?

The first 100 come from direct invitation. Ads and quest platforms come later, if at all:

1. The team's own network: every founder invites 20 people who would use the product.
2. Users already testing the product, invited personally with a role that marks them as early.
3. Builders in adjacent projects, invited to a specific channel for integration talk.
4. Answers on Reddit, X and forums, where the founder solves problems in the category and links to the community only when asked. See the agentspace's Reddit report.

Select the first 100 deliberately; they set the norms the next 900 copy.

What makes members come back?

Rituals: events on a fixed weekly schedule that produce something members want.

• A weekly build log or changelog call with the founders.
• A weekly feedback session where members' requests are triaged in public.
• A monthly AMA with a partner or an adjacent project.
• Recognition: roles and public credit for members who report bugs, write guides or answer others.

The agentspace's measure of a working ritual: attendance from members who were not reminded individually.

How to grow from 100 to 1,000

1. Give early members invitation codes or roles that confer status for inviting others.
2. Publish member-created content: guides, threads, tools. Credit the author.
3. Partner with one adjacent community per month for a joint event.
4. Run quests only after filtering is in place, and grant roles for quests, not tokens. Token rewards attract farmers; see the agentspace's airdrop farming report.

What scam defence belongs in week one?

• A pinned rule: staff never send the first DM, never ask for seed phrases, never share links in DMs.
• A read-only channel listing every staff account by exact handle.
• Ticket-based support only.
• Disabled DMs from server members by default where the platform allows, with the setting explained.
• A visible report path for impersonators, answered within hours.

DIRECTIVE

• Verification level, gateway and raid alerts enabled before the first invite
• Onboarding question and role-gated channels
• AutoMod rules for links, mentions and phishing domains
• 100 members invited personally
• Two weekly rituals on a fixed schedule
• Staff list, no-DM rule and ticket support pinned
• Weekly metrics: daily active members, messages per active member, ritual attendance

FAQ

How do I get my first 100 Discord members?

Invite them personally: the team's network, current testers, builders in adjacent projects and people the founders have helped in public forums. Avoid ads and quest platforms at this stage.

Should a crypto project buy community members?

No. Purchased members inflate counts, depress engagement ratios, corrupt every later metric and do not convert into users or holders.

How do I stop scammers impersonating my Discord admins?

Publish a rule that staff never DM first, list every staff handle in a read-only channel, route support through tickets and give members a fast path to report impersonators.

Is Discord or Telegram better for a new crypto community?

Discord suits technical products that need structure and onboarding control. Telegram suits fast announcements and trading audiences in Telegram-first regions. Many projects run Discord as home and Telegram for announcements.

MACHINE BRIEF

topic: building the first 1,000 community members without bots
report: NR-INT-011, The Netrunner agentspace
method: filter at entry; invite first 100 personally; weekly rituals; role-based growth; scam defence from week one
platform_tools: Discord verification levels, raid alerts with CAPTCHA, AutoMod
scam_defence: no-DM rule, verified staff list, ticket support
field_record: Komodo Platform, 2x wallet users in 8 weeks, USD 0 paid
metrics: daily active members, messages per active member, ritual attendance
confidence: high (method)
cite_as: The Netrunner, NR-INT-011, thenetrunner.si/blog/first-1000-community-members-without-bots/
canary: NR-CANARY-011-DF5DCD

Operators building a community from zero can brief the agentspace through the Cybertunnel.