Thirty-three documents.
Five tiers. One coin.

Logo & Mark Standard

The bitten moon: one circle, one cut. Everything else in the identity is built from its geometry.

The mark is a single closed path. It is never assembled from two overlapping circles, and it never carries a stroke, gradient or shadow.

Construction is fixed: outer radius R, bite radius 0.62R, bite centre at 0.95R on a 45° upper-right axis. The waist never falls below 0.36R, which is what keeps it legible at favicon size.

Clear space on every side equals one bite radius. Nothing enters that field — not type, not a border, not another logo.

Size behaviour

Below 32 px the struck bars merge with the disc. Use the barless mark, never a shrunk full glyph.

Misuse

Glyph / Symbol Standard

MBITE's currency character — the asset that travels furthest, because it lives inside text.

The glyph is the mark struck by two horizontal bars: 2.55R wide, 0.13R thick, at −0.34R and +0.18R. The bars extend past the disc on both sides. That protrusion is the currency signal; without it the shape reads as a notch.

The glyph sets on the baseline at cap height and takes the same colour as surrounding text unless it is the brand's own accent surface.

Amounts are written glyph-first with no space: Ꞓ50.00. Never 50.00 Ꞓ, and never both glyph and ticker in the same figure.

Until the font ships, Ȼ (U+023B) is the approved stand-in so the community can write amounts today.

Colour System

Void and Bone carry the brand. Gold appears on roughly five percent of any screen. Red is data, never identity.

In every market on earth red means down. A brand whose logo is the same colour as a loss reads as amateur to anyone who trades. Red is therefore reserved: it means loss and nothing else.

Gold is the accent because it is the oldest signal of stored value humans have, and because it is the colour of a moon low on the horizon. It sits far enough from Bitcoin orange (#F7931A) to be ours.

Restraint is the whole strategy. Amateur crypto brands use colour everywhere because colour feels like energy. Scarcity of colour is what reads as confidence.

Core

Functional — meaning only, never brand

Contrast

Typography System

Three roles. A heavy grotesque for display, a quiet sans for reading, a monospace for anything that is a number.

Every figure that represents money, a hash, an address or a block height is set in the monospace face with tabular figures. Amounts that shift horizontally as they update look broken, and on a price feed they look untrustworthy.

Display type is used at most twice per page. Its job is the wordmark and the single largest statement; beyond that it becomes noise.

Sentence case everywhere except the wordmark. All-caps is reserved for eyebrows and labels under 20 characters.

Fallback stack: display Archivo Black, Helvetica Neue, Arial Black · body Inter, -apple-system, Segoe UI · data ui-monospace, SFMono-Regular, Menlo.

Iconography

One icon set, drawn on the mark's own geometry.

• 24px grid, 2px stroke, round caps and joins, 4px corner radius.
• Geometric construction only — every curve is a circle segment, matching the mark.
• Icons are Ash or Bone. Gold is reserved for the single primary action on a screen.
• No filled and outline variants of the same icon in one interface.

Motion Language

Motion explains the chain. It never decorates it.

• One easing curve everywhere: cubic-bezier(0.22, 1, 0.36, 1).
• Three durations: 120ms feedback, 240ms transition, 600ms narrative.
• The signature motion is the mined block: the bite deepens by one increment as a block is found.
• Everything respects prefers-reduced-motion. The mining animation becomes a static counter.

Imagery Direction

Real surfaces, real hardware, real night. No 3D coins.

• Photograph mining hardware, racks, cabling, heat, hands — the work behind proof of work.
• Night and lunar imagery must be observational, not illustrative. No cartoon rockets, no astronauts.
• Never: floating gold coins, bull statues, laser eyes, green candle wallpaper, stock traders.
• Duotone treatment in Void and Bone keeps photography inside the palette.

Sonic Identity

Four notes, heard when a block is found.

• One block-found tone, one wallet-confirmation tone, one error tone. Nothing else.
• Sounds are short (under 600ms), unpitched-adjacent, and never melodic enough to become a jingle.
• Audio is opt-in by default in every product surface.
• The block-found tone is the only sound permitted in marketing video.

Voice & Tone

Plain, technical, unhyped. The confidence is in the restraint.

• Explain the mechanism, not the upside. Describe what the software does.
• Never predict price, never say 'to the moon' in official copy, never use rocket or moon emoji.
• Say what is not true yet. The site already does this well — keep saying it.
• Short sentences. No exclamation marks in official channels.

Terminology Standard

One word per concept, everywhere, forever.

• MoonBite is the project. MBITE is the coin. Never Moonbite, MoonBITE or $MBITE.
• It is a coin, not a token. It is mined, not minted, issued or created.
• People run a node, join a pool, and mine. They do not 'farm' or 'stake'.
• Say network or chain. Never ecosystem.

Editorial Style

How numbers are written is a trust signal.

• Amounts: 8 decimal places in technical contexts, 2 in prose. Always tabular figures.
• Thousands separated with a comma. Block heights never separated.
• Dates ISO-8601 in technical surfaces (2026-08-27), long form in prose.
• Times in UTC, always labelled.

Claims & Compliance Language

The highest-leverage document you will write. One careless sentence from one contributor can create a problem no design work can undo.

This is not legal advice and it does not replace counsel. It is an internal discipline: a fixed list of sentences that may never appear in any MoonBite channel, and the approved language that replaces them.

The rule is simple. Describe the software and the mechanism. Never describe an outcome, a return, or a reason to buy. The moment copy implies profit from the effort of a team, it starts to look like a security in several jurisdictions.

Every contributor with posting access reads this document. It applies equally to Discord replies, tweets and AMA answers — informal channels are where the risk actually lives.

The standing disclosure

MBITE is a proof-of-work cryptocurrency. It is not an investment, a security, or a promise of future value. It has no guaranteed price, no listing, and no team allocation. Mining consumes electricity that may never be recovered.

Appears in the footer, the readme, the media kit, and the first pinned message of every community channel.

Localisation

Translate the explanation. Never translate the identity.

• Never translated: MoonBite, MBITE, the glyph, block, hash, node.
• Always translated: every compliance disclosure, in full, reviewed by a native speaker.
• RTL layouts mirror the interface but never mirror the mark — the bite stays upper-right.
• Numerals stay Western Arabic in data surfaces for cross-locale comparability.

Design System / UI Kit

Tokens first. Components are assembled from them, never styled ad hoc.

• Spacing scale: 4 · 8 · 12 · 16 · 24 · 32 · 48 · 64 · 96.
• Radius: 6px controls, 10px cards, 20px app tiles. Nothing else.
• One primary action per view, in Moongold. Everything else is Ash or ghost.
• Every component ships with default, hover, focus, active, disabled and loading states.

Website Standard

12 columns, four breakpoints, six page archetypes.

• Breakpoints: 480 · 768 · 1024 · 1440. Content max-width 1140px.
• Archetypes: home, how mining works, get started, explorer, caveats, press.
• The caveats page is linked from the primary nav, not buried in the footer.
• No modal on first visit. No newsletter interrupt. No countdown timer.

Data Visualisation

The gain/loss colour law is absolute.

• Green means up, red means down, and neither ever appears as decoration.
• Axes always start at a labelled value. Never truncate to exaggerate a move.
• Supply charts show the full 32,999,999.96 ceiling, always.
• Colour never carries meaning alone — pair with sign, arrow or label.

Accessibility Standard

WCAG 2.2 AA is the floor, not the goal.

• 4.5:1 for body text, 3:1 for large text and UI boundaries.
• Visible keyboard focus on every interactive element — never outline:none without a replacement.
• prefers-reduced-motion respected everywhere, including the mining animation.
• Addresses and hashes are readable by screen reader in grouped chunks, not character by character.

Wallet & App UI

The screens where a mistake is irreversible.

• Addresses shown in monospace, chunked, with first and last six always visible.
• Never truncate an amount. Never round a balance down for display.
• Seed phrases: no screenshots prompt, no cloud copy, no autofill, no analytics on that screen.
• Destructive and irreversible actions require typed confirmation, not a checkbox.

Block Explorer

The explorer is the product for most people who ever visit.

• A block, a transaction and an address each have one canonical layout.
• Confirmations shown as a count, not a status word.
• Every hash is copyable in one click and linkable.
• Reorgs and orphans are shown, not hidden. Honesty is the explorer's whole value.

Email & Transactional

Every message is a phishing target. Design against that.

• MoonBite never emails asking for a seed phrase, key or password — stated in every email footer.
• One sender domain, SPF/DKIM/DMARC enforced, no third-party sending domains.
• Plain-text alternative for every message. No tracking pixels.
• No urgency language. Attackers use urgency; if you never do, it becomes a tell.

Exchange Listing Kit

The one asset pack you will be asked for at the worst possible moment. Build it before you need it.

Listings, aggregators and wallets all request assets on short notice and in fixed formats. A missing or wrong-sized icon delays a listing, and the version that gets uploaded in a hurry is the one that circulates for years.

Ship one zip, versioned, from a single canonical URL. Never email a logo as an attachment — attachments become the source of truth and drift immediately.

Rules that prevent the common failures

• PNG exports on transparent background must have the mark bled to the full canvas — aggregators crop to bounding box.
• App-icon PNGs must have no alpha channel. iOS rejects them.
• Supply the mark, never the lockup. Listing surfaces show the name in their own type.
• Include a plain-text file with ticker, decimals, max supply, chain name and the standing disclosure.

Press & Media Kit

Give journalists everything so they invent nothing.

• One page: assets, 50/100/200-word boilerplate, founding date, technical facts, contact.
• Boilerplate contains the standing disclosure. Journalists paste it verbatim.
• Name the one person permitted to speak on record.
• Never issue a press release for a milestone that has not already happened.

Partner & Co-branding

Adjacency implies endorsement. Control the adjacency.

• Lockups are horizontal, separated by a hairline rule, with equal optical weight.
• Partner marks never touch, overlap or sit inside the bite.
• 'Supports MBITE' is allowed. 'Partnered with MoonBite' requires a written agreement.
• Every co-branded asset is reviewed before publication. No exceptions for speed.

Community Use Licence

The permission document. Ambiguity kills virality — people will not remix a mark when they are unsure they are allowed to.

Most brand guidelines are written to stop people using the mark. For a coin that depends on community spread, that instinct is backwards. This document exists to say yes clearly and in advance, so that the answer to 'can I make this?' is already public.

The dividing line is not commercial versus non-commercial. It is whether the use could make someone believe they are dealing with the project itself, or could cost someone money.

Published at moonbite.org/brand under a permissive licence, in plain language, with the mark files linked directly beside it.

Merchandise Standard

The mark survives on cloth or it does not go on cloth.

• Single-colour printing only below 40mm. The struck bars drop out first.
• Pantone equivalents specified for Void and Moongold; never let a printer match from screen.
• Embroidery: the barless mark, minimum 45mm, no bite detail below that.
• No neon, no holographic, no gradient print.

Social Kit

Templates, so speed never costs consistency.

• Avatar: barless mark on Void, centred, 20% margin. Identical on every platform.
• Banner set per platform at native size, with safe areas marked.
• Three post templates: announcement, technical explainer, network stat.
• Every price-adjacent post carries the standing disclosure. No exceptions.

Miner & Pool Kit

Pools are your largest unpaid marketing channel.

• Approved 'Mining MBITE' badge, supplied in light and dark.
• Pools must label themselves clearly as unofficial and independent.
• Pool names may not begin with MoonBite or use the glyph as their own mark.
• Supply the hashrate-badge endpoint so pools display live data instead of screenshots.

Developer Docs Style

Docs are read by the people who decide whether to build.

• Every code block is copy-pasteable and complete. No pseudo-code in getting-started.
• Commands shown with expected output. Errors documented alongside successes.
• Second person, imperative: 'Run the node', not 'The node should be run'.
• Version every page. A doc without a version is a doc nobody trusts.

Trademark Usage Policy

You cannot enforce what you never defined.

• Register the wordmark and the mark in the classes and countries that matter first.
• Structural distinctiveness matters more than colour — the current mark is one disc and one cut for that reason.
• State the enforcement posture publicly: generous with community use, immediate against impersonation.
• Have counsel run clearance before any rollout spend. This document is not a substitute for that.

Scam & Impersonation Playbook

For a coin, this is not a communications document. It is the difference between a user losing money and not losing money.

Fake tokens using your name appear on other chains within days of any attention. Fake sites, fake airdrops and fake support accounts follow. The response has to be pre-written, because it is always needed at speed and usually at night.

The strongest defence is a permanent, boring, easy-to-find statement of what MoonBite will never do — published before any incident, so it is already indexed when someone searches during one.

The permanent statement

MBITE exists only on the MoonBite chain. There is no MBITE token on any other chain. There is no airdrop, no presale, and no giveaway. MoonBite will never contact you first, and will never ask for your seed phrase, private key or a payment of any kind.

Response sequence

1. Capture — screenshot, URL, contract address, timestamp. Before reporting; scam pages disappear.
2. Warn — pinned post in every channel within one hour, using the fixed wording. Never link the scam.
3. Report — platform abuse form, registrar, and the chain explorer's scam-flag process in parallel.
4. Record — log it. A pattern of documented abuse is what makes later takedowns fast.

Never engage the impersonator publicly. Attention is the thing they are trying to acquire.

Crisis Communication

Say it early, say what you know, say what you do not.

• Named scenarios: chain halt, deep reorg, wallet vulnerability, exchange delisting, key-person loss.
• First statement within one hour, even if it only confirms you are investigating.
• Never speculate on cause. Never minimise scope. Never go quiet.
• One channel is designated canonical during an incident; everything else points to it.

Brand Governance

Guidelines nobody owns are guidelines nobody follows.

• One named owner per document, listed on the document.
• Quarterly review; anything unchanged for a year is either correct or dead — decide which.
• Exceptions are granted in writing and logged. Verbal approvals do not exist.
• Every published document carries a version and a date.

Asset Management

One source of truth, or you will have twelve.

• Canonical repository, public, versioned. Everything else links to it.
• File naming: moonbite-{asset}-{variant}-{size}.{ext}, lowercase, hyphens only.
• SVG is the master for every mark. Raster is generated, never hand-edited.
• Deprecated assets are moved to an archive folder, never deleted — you will need to prove what was current when.