Overview

Every protocol says it is safe. The difference is whether you can check the claim.

This section is Noon's security and trust framework laid out in eight pillars, each answering exactly one question, each with its own page, and each written so the claims are verifiable.

The eight pillars

No	Pillar	Type	The specific question it answers	Primary Focus & Verification Target
1	Trusted Custody	Prevent	Where are Noon's underlying reserves actually held?	Qualified off-chain custodians (Alpaca) and institutional MPC vaults (Fordefi, Safe).
2	Smart Contract Security & Audits	Prevent	Are Noon's smart contracts secure and bug-free?	Multi-firm pre-deployment audits (Quantstamp, Halborn, Hashlock, Sherlock, etc.).
3	World-Class Operational Security	Prevent	Are the human workflows and access keys secure?	SEAL Framework compliance, multi-sig administration, and key management policies.
4	Disciplined Risk Management	Prevent	How is capital exposure allocated and bounded?	Strategy deployment caps, delta-neutral rebalancing rules, and credit vetting.
5	Independent Collateral Verification	Prove	Can anyone verify protocol claims in real time?	On-chain Proof-of-Reserves, real-time collateral tracking, and transparent balances.
6	Layered Insurance	Protect	If a strategy or venue fails, what absorbs the loss?	The Noon Insurance Fund (daily volatility), Nexus Mutual (DeFi), and broker policies.
7	Robust Governance	Protect	Who controls protocol changes, and how are they made?	48-hour public timelocks, separated administrative roles, and $sNOON governance votes.
8	Thorough Incident Response Framework	Protect	What exact protocol happens when an anomaly occurs?	Bug bounty programs, emergency circuit breakers, and response execution flows.

How the Pillars Work Together

The framework operates as a continuous, defense-in-depth safety engine:

1. Prevent (Pillars 1–4)

The first line of defense stops exploits and capital degradation before they happen.

• Custody architectures isolate collateral from platform insolvency.

• Smart contract auditing and formal verification prevent code exploits.

• Operational security rules neutralize human error, phishing, and key compromise.

• Strict allocation bounds prevent over-concentration in any single yield vector.

2. Prove (Pillar 5)

Eliminating trust through continuous, public verification.

• Real-time on-chain reporting and independent collateral attestations allow stakers, integrators, and security researchers to inspect total reserves, vault locations, and $USN supply 24/7/365.

3. Protect (Pillars 6–8)

Fail-safe systems that contain anomalies and compensate for black-swan events.

• Layered insurance buffers absorb mark-to-market fluctuations and third-party protocol risks.

• Public timelocks and role separation prevent sudden, malicious protocol changes.

• A structured incident response protocol guarantees rapid containment if a security event is detected.

For Security Researchers & Whitehats

Found a potential vulnerability or security flaw? Noon maintains an active bug bounty program and rapid-response triage system:

• 🛡️ Submit a Report: Thorough Incident Response Framework

• 📄 Verify Active Deployments: Contract Addresses & Oracles