Security
Security best practices
Security guidelines for Selendra development.
Security Features
- Rust memory safety for WASM contracts
- EVM battle-tested patterns for Solidity
- Unified accounts reducing address confusion
- Low transaction costs enabling frequent operations
Key Topics
Smart Contracts - Vulnerabilities, audit checklist, testing
[Node Security] - Validator setup, network hardening, access control
[Application Security] - Frontend security, key management, APIs
Report Issues
Critical: security@selendra.org or @security_manager on Telegram
General:
- GitHub: github.com/selendra/selendra/issues
- Telegram: t.me/selendranetwork
Bug Bounty
| Severity | Reward |
|---|---|
| Critical | $5,000 - $20,000 (SEL) |
| High | $1,000 - $5,000 |
| Medium | $500 - $1,000 |
| Low | $100 - $500 |
Requirements: Exploit description, proof of concept, impact assessment
Pre-Deployment Checklist
- Professional audit complete
- All inputs validated
- Access controls implemented
- Emergency mechanisms in place
- Events properly emitted
- Gas optimized
- Test coverage >90%
Resources
- Smart Contract Best Practices
- Common Vulnerabilities
- Audit Checklist
- Security updates: t.me/selendra
Contribute
Found an issue or want to contribute?
Help us improve this documentation by editing this page on GitHub.