Voice Guide

How Husher writes. Australian English, no em dashes, sober anti-shill tone.

All docs

Voice Guide

Spelling

Australian English. Default to AU spellings everywhere: organise, optimise, recognise, colour, behaviour, defence, programme (when used as a noun), centre, favour, analyse, licence (noun) and license (verb).

The exception is product UI strings that have to match common crypto-industry usage (e.g. "Color" tokens in a Tailwind config). Marketing copy is AU.

Punctuation

No em dashes. Replace with commas, parentheses, or full stops. This is a hard rule. Em dashes have become a tell for AI-written copy and the privacy community will spot them.

  • Bad: "Husher routes through ESPs — never holding funds — for guaranteed rates."
  • Good: "Husher routes through ESPs without ever holding funds, for guaranteed rates."

En dashes are fine for numeric ranges (60–180 days, 0.4–5%).

Tone

Sober, anti-shill, technically credible. Every post should pass the Monero community sniff test. Users on r/Monero, kycnot.me, and monero.observer read everything skeptically and detect hype instantly.

  • Concrete over abstract: "0.4% default, configurable to 5% via API key" beats "the most generous affiliate program in crypto"
  • Technical over emotional: "ZEC shielded hop available as a route option" beats "experience true financial freedom"
  • Specific over sweeping: "Cake Wallet now routes through Husher" beats "we're partnered with leading wallets"

Words and phrases to use

  • Guaranteed rate (never "fixed rate")
  • Non-custodial (never "fully decentralised", we route through CEXs via ESPs)
  • ESP partner (when naming the underlying execution venue)
  • No accounts. No KYC. No surprises. (the three-line refrain)
  • Private. Fast. Non-custodial. (in that order, privacy first)

Words and phrases to avoid

  • Revolutionary, game-changing, disruptive, next-gen, web3-native
  • "True privacy" (privacy is binary, qualifiers weaken the claim)
  • "Industry-leading" (only true if we lead the industry; we don't yet)
  • "Best-in-class" (cliché and unverifiable)
  • "Seamless" (banned)
  • "Empower / empowerment" (banned)

Cadence and length

  • X posts: aim for one strong sentence, max 280 chars. Threads only when there's a real reason (route walk-through, MiCA explainer, partnership announcement).
  • Thread length: 5–9 tweets is the sweet spot. Cap at 12. If it needs more, write a blog post and link the thread to it.
  • Telegram bot updates: terse, one paragraph max, include a link.
  • Blog: 800–1500 words. Rare. Used for the "Husher Privacy Roundup" monthly digest and for substantial product launches.

Formatting in X posts

  • Two-line break between paragraphs in a single tweet (looks better on mobile)
  • Use the en dash for stats ranges, not em dash for emphasis
  • Numbers as numerals (3 reasons, not three reasons)
  • Cap one hashtag per post if any, and never #crypto

What we never do

  • No "GM" posts
  • No engagement-bait questions ("What's your favourite chain?")
  • No reply guys in our own replies
  • No emoji-heavy threads. One accent emoji at most, and rarely.
  • No screenshots of competitor outages used to dunk
  • No price talk, ever (this is not a token shill operation)