Smart Contract Security & Audits
Are Noon's smart contracts secure? Code-level verification, continuous auditing, and hardcoded programmatic guardrails.
Prevent
At Noon, smart contract security is not a one-time pre-launch checkbox—it is a continuous, multi-layered discipline.
Smart contracts execute autonomously on public ledgers to handle minting, redemption, staking, yield routing, and rebalancing for $USN and $sUSN. To guarantee complete system integrity, Noon enforces security across two distinct code-level vectors: Rigorous Third-Party Code Auditing and Hardcoded On-Chain Protection Rules.
1. Smart Contract Auditing Standards
No smart contract code reaches mainnet or secondary blockchain deployments without undergoing comprehensive, remediated third-party security audits.
Our Code Audit Policy
Pre-Deployment Execution: Every core contract deployment must complete a full third-party audit before accepting user deposits.
Continuous Upgrade Trigger: Every protocol upgrade, logic modification, adapter addition, or cross-chain expansion automatically triggers a fresh, independent security review prior to mainnet execution.
Multi-Firm Diversity: We engage multiple leading auditing firms—including Quantstamp, Halborn, Hashlock, MoveBit, and Sherlock—to eliminate single-auditor blind spots and achieve multi-lens code verification.
Comprehensive Audit History
The cards below catalogs every smart contract audit executed across Noon’s protocol architecture:
2. On-Chain Code Protection & Programmatic Guardrails
Auditing code is only effective when paired with defensive, hardcoded execution rules. Noon enforces strict programmatic guardrails directly within its smart contract architecture:
Separated Role Permissions: Administrative functions—such as Admin, Staking, Rebase, and Blacklist—are isolated into distinct, role-gated smart contracts. No single admin key or role can cross boundaries to access or sweep user funds.
48-Hour Public Timelocks: All non-emergency contract updates are subjected to a mandatory 48-hour on-chain timelock. This public delay allows stakers, integrators, and security researchers to inspect queued contract changes on-chain—and exit positions if they disagree—before code executes.
Granular Emergency Circuit Breakers: Pause controls allow authorized security roles to halt minting, redemptions, staking vaults, or $USN transfers in an emergency. Crucially, pause mechanisms cannot transfer, divert, or reallocate user capital; they serve purely as a fast, low-risk containment measure.
Contract-Level Safety Rules: Direct minting and redemptions enforce per-block and per-day volume caps, utilize nonce checks to prevent replay attacks, and anchor valuations to redundant price oracles that automatically reject stale or out-of-band market feeds.
Verification & Bug Reporting
Canonical Address Verification
To protect against phishing attacks and spoofed contracts, always verify smart contract addresses against our official directory before interacting:
Whitehat Security & Vulnerability Reporting
If you discover a potential vulnerability or security flaw in Noon’s smart contracts, please report it immediately through our structured triage framework:
Last updated
Was this helpful?