Token Holder Community

A community server for holders: project updates, verified holder rooms, an open questions channel and no price talk.

4 categories
16 channels
7 roles
Small

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

UPDATES

community-rules
No price talk, no financial advice, no direct-message support.
project-updates
On a stated cadence. Check the topic for when the next one is due.
ask-the-team
Answered in public. One answer serves everyone.
community-calls
Recordings and notes, so the call is not the only record.

HOLDERS

holders-chat
Verified holders.
holder-questions
Answered by the team.
feedback
The team asks here rather than announces.
Holders Call

TRANSPARENCY

addresses-and-contracts
Verify these yourself rather than trusting a moderator.
what-we-shipped
A running record, not a promise.
known-issues
What is currently wrong. Almost nobody publishes this.
how-verification-works
Public and predictable, so impersonators have no cover.

COMMUNITY

general
Everything else.
introductions
Say hello.
memes-and-fun
Keep it here.
Community Room

Roles

TeamAdministrator
ModeratorModerator
Holder
Community
Update Ping
Muted

Overview

The general community server around a project, built to stay useful rather than becoming a price channel. #project-updates is read-only and written by the team on a stated cadence, so members know when to expect news instead of asking daily whether anything is happening. #ask-the-team is the counterpart and is answered in public, because the same question arrives from twenty people and one visible answer serves all of them. #community-calls carries recordings and notes so the call is not the only record. Holders is verified and modest: #holders-chat, #holder-questions and #feedback, where the team asks holders things rather than announcing at them. #how-verification-works is public and explains the process, because impersonators rely on verification being mysterious. Transparency is the category that earns trust: #addresses-and-contracts for what anyone can verify themselves, #what-we-shipped as a running record rather than a promise, and #known-issues, which almost no project publishes and which does more for credibility than any announcement. Community keeps #general, #introductions and #memes-and-fun. #community-rules states the boundary this server depends on: no price discussion, no financial advice, no direct-message support, and no trading talk of any kind. That rule is why the other channels stay readable.

When to use it

Project communities collapse into price speculation, after which the team stops posting because every update is judged against a chart, and impersonators harvest the members who are left. This layout sets an update cadence so members are not refreshing, answers questions publicly once, publishes what anyone can verify on-chain, and draws a hard boundary against price and advice so the server stays a place the team wants to be in.

What makes it different

Updates arrive on a stated cadence, so nobody is refreshing the server for news.
Questions are answered once in public, which is how one answer serves twenty askers.
A published known-issues channel, which does more for credibility than any announcement.
A hard no-price, no-advice boundary, which is the reason the rest stays readable.

Recommended Vetox setup

Auto Roles
Assign the Community role on arrival so holder channels stay closed until verification has actually happened.
Auto-Mod
Run Auto-Mod link filtering everywhere, since a project community is a permanent target for lookalike links.
Anti-Raid
Enable Anti-Raid, because coordinated joins before an impersonation wave are the standard pattern here.
Suggestions
Run Suggestions on #feedback so the team sees what holders actually want rather than who is loudest.

Questions

Does banning price talk not empty the server?

It removes the members who were only there for it, which is the intent. What remains is a community the team can post in honestly, where a difficult update can be given without being priced in real time, and where a new member asking a genuine question is not buried. Projects that keep this boundary tend to have quieter servers and far better ones.

What cadence should updates follow?

Whatever you can hold in a bad month, stated in the channel topic. Fortnightly kept reliably beats weekly kept for two months. The cadence matters more than the frequency, because the failure mode is not slowness but unpredictability: a community that does not know when the next update is due fills the gap with speculation, and that speculation is what the moderators then have to manage.

Common mistakes

Allowing price talk, after which every team post is read as a signal and the team stops posting.
Handling verification privately, which teaches members that a stranger offering help might be genuine.
Publishing only good news, so members learn nothing from the server and rely on rumour instead.

Consider instead

DAO Governance Hub The community votes on proposals and funds work, and needs a governance pipeline rather than updates.
Community Safety Desk Safety is the whole problem and you need a dedicated desk rather than one category.

Do you have any doubts?

Our team is there for you

0.0k

Servers

Commands

Users

Languages