Lux Docs

Contract Audit

Security audits and smart contract verification

Contract Audit

Security is paramount for any governance protocol. This page provides information about our security audits, verified contracts, and ongoing security measures.

Audit Status

All core smart contracts have been audited by independent security firms before mainnet deployment.

Audit Summary

AuditFirmDateStatusReport
Core Contracts v1.0Security FirmQ1 2026CompletedView Report
Governance ModuleSecurity FirmQ1 2026CompletedView Report
Staking ContractsSecurity FirmQ1 2026CompletedView Report
Treasury ModuleSecurity FirmQ2 2026In ProgressPending

Audit Scope

The following contracts were included in the security audit:

Audited Contracts
├── Governance
│   ├── Governor.sol
│   ├── Timelock.sol
│   ├── ProposalRegistry.sol
│   └── VotingModule.sol
├── Token
│   ├── GovernanceToken.sol
│   ├── VoteEscrow.sol
│   └── StakingRewards.sol
├── Treasury
│   ├── Treasury.sol
│   ├── PaymentRouter.sol
│   └── StreamingPayments.sol
└── Access
    ├── AccessControl.sol
    ├── RoleManager.sol
    └── Multisig.sol

Findings Summary

Critical Findings

FindingSeverityStatus
None identifiedCriticalN/A

High Findings

FindingSeverityStatus
None identifiedHighN/A

Medium Findings

FindingDescriptionStatus
M-01Potential reentrancy in payment flowResolved
M-02Integer overflow in vote calculationResolved

Low Findings

FindingDescriptionStatus
L-01Missing event emissionsResolved
L-02Inconsistent error messagesResolved
L-03Gas optimization suggestionsImplemented

Informational

FindingDescriptionStatus
I-01Documentation improvementsAddressed
I-02Test coverage recommendationsImplemented

Verified Contracts

All deployed contracts are verified on block explorers. You can review the source code directly:

Mainnet Contracts

ContractAddressVerified
Governor0x...View
Timelock0x...View
Token0x...View
VoteEscrow0x...View
Treasury0x...View
Staking0x...View

Testnet Contracts

ContractAddressVerified
Governor0x...View
Timelock0x...View
Token0x...View
VoteEscrow0x...View
Treasury0x...View
Staking0x...View

Security Measures

Smart Contract Security

  1. Access Controls

    • Role-based permission system
    • Multi-signature requirements for critical operations
    • Timelock delays on governance actions
  2. Reentrancy Protection

    • ReentrancyGuard on all external calls
    • Check-effects-interactions pattern
    • Pull-over-push payment patterns
  3. Integer Safety

    • SafeMath operations (Solidity 0.8+)
    • Overflow/underflow checks
    • Decimal precision handling
  4. Upgrade Safety

    • Transparent proxy pattern
    • Storage layout compatibility checks
    • Upgrade timelocks

Operational Security

┌─────────────────────────────────────────────────────────────────┐
│                    Security Architecture                         │
├─────────────────────────────────────────────────────────────────┤
│                                                                   │
│  User Action                                                      │
│       │                                                          │
│       ▼                                                          │
│  ┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐  │
│  │ Frontend │───▶│   RPC    │───▶│ Contract │───▶│ Timelock │  │
│  │   Auth   │    │  Guard   │    │  Access  │    │  Delay   │  │
│  └──────────┘    └──────────┘    └──────────┘    └──────────┘  │
│                                                                   │
│  Multi-layer Protection:                                         │
│  1. Frontend validation and rate limiting                        │
│  2. RPC endpoint security and monitoring                         │
│  3. Smart contract access controls                               │
│  4. Timelock delays for execution                                │
│                                                                   │
└─────────────────────────────────────────────────────────────────┘

Monitoring

  • Real-time Alerts: Automated monitoring for unusual activity
  • Transaction Monitoring: All governance transactions tracked
  • Health Checks: Regular contract state verification
  • Incident Response: Documented procedures for security incidents

Bug Bounty Program

We maintain an active bug bounty program to encourage responsible disclosure of security vulnerabilities.

Scope

CategoryIn Scope
Smart ContractsAll deployed contracts
InfrastructureRPC endpoints, APIs
FrontendWeb application

Rewards

SeverityReward Range
Critical$10,000 - $50,000
High$5,000 - $10,000
Medium$1,000 - $5,000
Low$100 - $1,000

Submission Process

  1. Discovery: Find a potential vulnerability
  2. Document: Create detailed report with reproduction steps
  3. Submit: Send to security team via secure channel
  4. Review: Team reviews and validates finding
  5. Reward: Bounty paid upon confirmation

Responsible Disclosure: Please do not publicly disclose vulnerabilities before they are patched. Contact the security team directly.

Contact

For security issues, contact:

Audit Reports

Full Audit Report

Download the complete audit report:

Report Contents

The audit reports include:

  1. Executive Summary: High-level findings and recommendations
  2. Methodology: Audit approach and tools used
  3. Findings: Detailed vulnerability descriptions
  4. Recommendations: Suggested fixes and improvements
  5. Resolution: Team responses and fixes applied

Third-Party Integrations

Security considerations for integrated services:

IntegrationPurposeSecurity Review
RPC ProvidersBlockchain accessProvider SLA reviewed
OraclesPrice feedsContract audited
BridgesCross-chainBridge audit reviewed
Frontend HostingWeb applicationSecurity hardened

Ongoing Security

Security is an ongoing process, not a one-time audit:

  • Continuous Monitoring: 24/7 transaction monitoring
  • Regular Reviews: Quarterly security assessments
  • Upgrade Process: All upgrades go through security review
  • Community Reporting: Incentivized vulnerability disclosure

FAQ

Are the contracts upgradeable?

Yes, contracts use the transparent proxy pattern. Upgrades require governance approval and timelock delay.

How are admin keys secured?

Admin functions are controlled by multi-signature wallets requiring multiple approvals. No single party can make changes.

What happens if a vulnerability is found?

  1. Pause affected functionality (if possible)
  2. Deploy fix through governance
  3. Post-mortem analysis
  4. Bug bounty payment (if applicable)

How often are audits conducted?

Major updates undergo full audit. Minor changes are reviewed internally with periodic external assessments.

Next Steps

On this page