> For the complete documentation index, see [llms.txt](https://paragon-protocol.gitbook.io/paragon-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://paragon-protocol.gitbook.io/paragon-protocol/brand-guidelines-and-logo-assets.md).

# Brand Guidelines & Logo Assets

Paragon’s code is open where it helps the ecosystem — our **brand is not**. These guidelines protect users from impersonation and keep the Paragon identity consistent across surfaces.

### What’s covered

* Official names & ticker
* Correct/incorrect logo use
* Colors, typography, and icons
* Co-branding and partner rules
* Legal & permissioning
* Downloadable asset kit (file structure)

***

### 1) Names & Ticker

* **Protocol:** Paragon Protocol (short: **Paragon**)
* **DEX:** ParagonSwap
* **Token:** **Paragon (XPGN)** — ticker **$XPGN**
* **Governance lock:** **veXPGN**

> Use **$XPGN** everywhere. Do **not** use old “PRGN” naming.

***

### 2) Permitted Uses ✅

You may use Paragon brand assets if:

* You’re referring to **official Paragon products** (app, docs, protocol features).
* You are **linking to our official app or website**, e.g., “Trade **$XPGN** on ParagonSwap.”
* You are **announcing a partnership** that has been **approved by the Paragon Core Team**.

***

### 3) Forbidden Uses ❌

To avoid confusion, impersonation, or implied endorsements:

* Do **not** use our name/logo in your **product, token, NFT, DAO, or company name**.
  * Not allowed: “Paragon Engine,” “XPGN Tools,” “ParagonSwap v2 (fork).”
* Do **not** sell **digital or physical** goods with Paragon/XPGN marks.
* Do **not** create names or socials that imply official status.
  * Allowed: “Paragon Fans.”
  * Not allowed: “Paragon Protocol US.”
* Do **not** alter the marks: **no recolors**, cropping, stretching, 3D, glows, outlines, or combined lockups.

***

### 4) Logo System

We provide three marks:

1. **Primary Lockup** — Paragon logomark + wordmark
2. **Glyph** — square icon (for avatars, favicons, app tiles)
3. **Wordmark** — “Paragon” text-only

Variants: **Light** (for dark backgrounds) and **Dark** (for light backgrounds).

#### Clear space & minimum size

* **Clear space:** keep at least **0.5× the logo height** free on all sides.
* **Minimum digital size:**
  * Lockup: **120 px** width
  * Glyph: **24 px** width/height
* **Minimum print size:**
  * Lockup width **30 mm**
  * Glyph **10 mm**

#### Backgrounds

* Use **Light logo** on dark/colored backgrounds (our default UI is dark).
* Use **Dark logo** on white/very light backgrounds.
* Avoid busy images; add a subtle overlay if needed.

***

### 5) Incorrect Usage (examples)

* ⛔ Recoloring the logo (stick to provided assets)
* ⛔ Adding drop shadows, outlines, bevels, gradients not in kit
* ⛔ Stretching or squashing (keep aspect ratio)
* ⛔ Rotating, tilting, or animating without approval
* ⛔ Combining Paragon mark with another logo into a single graphic
* ⛔ Placing on low-contrast backgrounds (logo must be legible)

***

### 6) Color Palette

Paragon’s UI uses a dark base with vibrant accents.

* **Paragon Black:** `#0B0F1A` (primary backgrounds)
* **Ink 2 (panels):** `#121826`
* **Slate 400 (text, secondary):** `#94A3B8`
* **White:** `#FFFFFF`

Accents:

* **Fuchsia (brand glow):** `#E879F9`
* **Cyan (actions/links):** `#22D3EE`
* **Emerald (success):** `#10B981`
* **Rose (danger):** `#F43F5E`

Use accents sparingly; **fuchsia** and **cyan** are the primary brand cues.

***

### 7) Typography

* **Primary UI:** Inter / SF Pro / system sans
* **Weights:** 400 (body), 500 (labels), 600–700 (headings)
* **Letter-spacing:** Default; avoid heavy tracking
* **All caps:** Only for small labels or tabs

***

### 8) Token Icon — **$XPGN**

We ship a **coin-style circular glyph** for token lists, CEX/DEX listings, and explorers.

* **Default:** Light variant on dark UIs
* **Stroke:** Provided; do not modify
* **Do not** recreate with gradients or community-made redraws

***

### 9) Co-Branding & Partner Lockups

* Place partner logos **left** and Paragon **right**, or stacked **top/bottom**; never merge.
* Maintain **equal visual weight** (match x-height/area, not pixel width).
* Keep **≥ 0.5× logo height** spacing between marks.
* Use **monochrome** versions if brand clashes occur (ask for approval).

***

### 10) Legal & Permissions

* The Paragon name, logos, and the **$XPGN** token icon are **protected brand assets**.
* Commercial usage, paid campaigns, major events, or app-store listings **require written approval**.
* You may not imply endorsement, investment advice, or official affiliation.

For approvals, submit a short brief (who/what/where/when) and creative previews.

***

### 11) Asset Downloads

Once you agree to these terms, download the official kit (SVG/PNG/AI/ICO):

```
/paragon-brand-kit/
  /logo/
    paragon-lockup-light.svg
    paragon-lockup-dark.svg
    paragon-wordmark-light.svg
    paragon-wordmark-dark.svg
    paragon-glyph-light.svg
    paragon-glyph-dark.svg
  /token/
    xpgn-token-glyph.svg
    xpgn-token-128.png
    xpgn-token-256.png
    xpgn-token-512.png
  /social/
    avatar-paragon-dark.png
    avatar-paragon-light.png
    cover-twitter-rectangle.png
  /favicons/
    favicon.ico
    favicon-32.png
    favicon-192.png
    site.webmanifest
  /print/
    paragon-lockup-ai.ai
    paragon-lockup-pdf.pdf
  BRAND-GUIDE.pdf
  LICENSE.txt
  READ-ME.md
```

> **Note:** Host the kit in your official repo (e.g., `paragon-protocol/brand`) and link it from your docs site’s **Brand** page.

***

### 12) Attribution Line (optional)

When credit is appropriate (press, partners):\
\&#xNAN;**“Paragon Protocol and $XPGN are trademarks of Paragon Labs.”**

***

### 13) Contact

* **Press & brand approvals:** partnerships\@paragon…
* **Community questions:** official Discord → `#brand-requests`
* **Abuse reports / takedowns:** legal\@paragon…

***

### 14) TL;DR

* Call the token **$XPGN** (not PRGN).
* Use official **SVGs**; do not modify.
* Keep **clear space** and **contrast**.
* Ask for **approval** for commercial or co-branded usage.

By downloading or using our brand assets you agree to these terms.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://paragon-protocol.gitbook.io/paragon-protocol/brand-guidelines-and-logo-assets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.