Katana | Brand Kit — Naming, Logos & Product Terminology
Katana brand reference for consistent naming, product terminology, network identity, KAT token labels and documentation presentation across applications.
Why brand consistency matters
Consistent naming reduces user confusion and helps search engines associate pages with the correct network and product. Applications should distinguish Katana Network, KAT, vKAT, avKAT, Vault Bridge, Katana Perps and third-party core apps clearly.
Naming rules
Use “Katana” or “Katana Network” for the chain. Use “KAT” for the token. Use “vKAT” and “avKAT” exactly for staking forms. Avoid inventing alternative spellings that could look like separate products.
Product boundaries
Sushi, Morpho and other integrated protocols remain independent applications. Documentation should describe them as core or integrated apps on Katana, not as products owned by Katana unless that relationship is explicitly established.
Visual identity
Use official logo assets with sufficient contrast and spacing. Do not recolor marks in ways that reduce recognizability, and avoid mixing unrelated project logos into Katana navigation or SEO metadata.
SEO consistency
Titles, H1, canonical URLs, Open Graph and structured data should use the same product naming. Conflicting names across metadata and visible headings can increase title rewriting and reduce topical clarity.
Documentation consistency
Technical pages should use the same token symbols, chain IDs and contract names as the current network reference. Brand consistency includes technical vocabulary, not only logos.
Frequently Asked Questions
How should the network name be written?
Use Katana or Katana Network consistently.
Should KAT be written in lowercase?
Use the official uppercase token symbol KAT.
Are Sushi and Morpho owned by Katana?
They are independent protocols integrated as core apps on Katana.
Why does naming matter for SEO?
Consistent naming across metadata and visible headings helps search engines understand page identity.