RaidzATTENTION, WITH PROOF.
Open app

Community, brand, and communication

Raidz presents itself as a live signal network: high-contrast data, radar motion, trace paths, lock/verify/release states, and dominant numbers. The system should feel operational without implying activity that has not occurred.

Identity

The working name is RAIDZ and the proposed ticker is $RAIDZ. The logo combines R, Z, and signal geometry. The primary palette uses Void/Graphite surfaces, Raidz Signal lime, Network Cyan, Target Amber, Alert red, and Data White.

Name, ticker, domain, and handle clearance remain a professional pre-launch task. Brand consistency is not evidence of trademark clearance, protocol affiliation, or token deployment.

Voice

Raidz language is compact and action-oriented: Connect, Score, Signal, Lock, Verify, Release, Rank. Public copy should be specific about the actor, action, evidence, and state. It must avoid fabricated urgency, guaranteed outcomes, return language, trading pressure, and vague claims of verification.

Good:

Demo Signal · not funded · creator reward model shown for product preview.

Bad:

Buy now before the network explodes.

Official channel roles

  • Website: canonical product, utility, safety, and deployment status.
  • Application: identity, creator/project workflows, and marketplace state.
  • X @Raidz_web3: evidence-rich product updates, creator education, and verified announcements.
  • Telegram @Raidz_fun: community onboarding, structured information, rules, safety, and support.
  • Telegram bot @RaidzFun_bot: commands, notifications, and links back to the HTTPS application.

The bot is regular Telegram infrastructure, not a Robinhood Chain Mini App. It must not take custody, automate engagement, or present unverified token trading.

Telegram information system

The community has branded responses for welcome, about, how it works, Raider, Radar, Market, proof, settlement, token, links, safety, support, and buy. Token and buy routes fail closed until a verified contract and purchase path exist. Visuals avoid generic coins, candlesticks, rockets, or return imagery.

Content pillars

  • Earn: explain real creator work and verified settlement.
  • Data: teach Score, proof, attribution, and integrity limits.
  • Projects: show how teams define and measure work.
  • Build: publish implementation evidence, decisions, and gates.

Community content must distinguish operator/build activity from authentic participant demand in analytics.