Audit Status
Scheduled Audits
Primary audits covering core contracts and bridge integrations are scheduled for Q1 2025. Auditor details will be announced when finalized.Continuous Security
- Automated scanning runs continuously through internal tools
- Dependency monitoring via Dependabot
- Static analysis using Slither
Audit Scope
Core Contracts
Token Contracts
Security Practices
Development Process
- All code changes reviewed by multiple developers
- Unit, integration, and fuzz testing required for every change
- Automated vulnerability scanning on all commits
- Extended testnet deployment before mainnet releases
Test Coverage Targets
All testing is in progress.
Security Patterns
All patterns follow OpenZeppelin’s well-established implementations.
Bug Bounty Program
TED Protocol operates a bug bounty program to incentivize responsible disclosure.Rewards
Scope
In scope:- Smart contracts on all supported chains
- Bridge integrations
- TEDP token contracts
- Cross-chain messaging logic
- Frontend/UI issues
- Third-party services
- Previously reported issues
- Social engineering attacks
Reporting
Submit security vulnerabilities to security@tedprotocol.io. Include:- Detailed description of the vulnerability
- Steps to reproduce
- Potential impact assessment
- Suggested fix (if applicable)
Third-Party Dependencies
TED Protocol relies on well-audited dependencies.Dependency Management
- Locked versions in package files
- Automated vulnerability alerts
- Regular dependency updates
- No unaudited external calls
Emergency Procedures
Incident Response Timeline
Emergency Controls
Transparency
Open Source
All TED Protocol smart contracts are open source and verified on block explorers.- GitHub: github.com/tedprotocol
- Verification: Etherscan, Arbiscan, Basescan, etc.
Upgrade History
All contract upgrades are documented with:- Upgrade rationale
- Code changes
- Audit status
- Timelock period