> For the complete documentation index, see [llms.txt](https://chroniumsync.gitbook.io/chroniumsync/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chroniumsync.gitbook.io/chroniumsync/precision-scan-interface/security-and-verification-layer.md).

# 🛡️ Security & Verification Layer

The **Security** tab provides a clear breakdown of token contract safety based on **authority controls**, **metadata behavior**, and verification from trusted sources.

ChroniumSync cross-references on-chain data with third-party audits (Jupiter, RugCheck) to identify red flags before they escalate.

<figure><img src="/files/oH8kRF6BrG22ihdSD7RA" alt=""><figcaption></figcaption></figure>

***

#### 🔐 Contract Authority Audit

Chronium checks the two most critical Solana contract controls:

* **Mint Authority:**\
  Indicates whether the token's minting rights are still active.\
  → *Renounced = No new tokens can be minted*\
  → Risk Level: Low if renounced
* **Freeze Authority:**\
  Determines whether token transfers can be frozen by the creator.\
  → *Renounced = Token cannot be paused or locked*\
  → Risk Level: Low if renounced

***

#### ✅ Verification Status Matrix

| Checkpoint            | Status |
| --------------------- | ------ |
| **Jupiter Verified**  | ✅ Yes  |
| **Jupiter Strict**    | ❌ No   |
| **RugCheck Verified** | ✅ Yes  |
| **Has Metadata**      | ✅ Yes  |
| **Metadata Mutable**  | ❌ No   |
| **Is Rugged**         | ❌ No   |

These signals help quickly determine if the token is:

* Properly indexed and trusted by major platforms
* Safe from unexpected minting or freezing
* Lacking any tamperable metadata behavior

***

ChroniumSync uses these checks as part of its **AI Threat Scoring** — where failed security flags lower the token’s baseline trust rating.