Security Model
How network stays protected
Selendra security based on Nominated Proof-of-Stake with economic penalties for dishonest behavior.
Validator Security
- Minimum bond: 10,000 SEL
- Current validators: 4 (expanding to 20 by 2026, 50+ by 2027)
- HSM storage recommended for keys
Consensus Security
- Requires 2/3 honest validator stake
- Aura: deterministic block production
- AlephBFT: 2-3 second finality, finalized blocks never revert
Smart Contract Security
EVM: Standard Ethereum risks (reentrancy, overflow, access control). Use audited libraries.
WASM: Sandboxed execution, memory/gas limits enforced.
Both VMs prevent DoS through resource limits.
Cryptography
- Account keys: secp256k1 (Bitcoin/Ethereum compatible)
- Session keys: ed25519
- Hashing: Blake2
Account Security
- Users responsible for private keys (no recovery)
- Multi-sig available via pallets
- Hardware wallets recommended
Audit Status
- Substrate framework: audited by multiple firms
- Selendra-specific: audits planned for 2026
- Smart contracts: developer responsibility
Report vulnerabilities: security@selendra.org
Incident Response
- Security council can fast-track patches
- Emergency proposals bypass normal voting
- Validators notified via private channels first
Best Practices
Users: Hardware wallets, verify transactions, test with small amounts
Developers: Audit before mainnet, implement emergency pause, use established patterns
Future Enhancements
2026: Security audit, expand to 20 validators, bug bounty program
2027: Expand to 50+ validators, advanced anomaly detection
Contribute
Found an issue or want to contribute?
Help us improve this documentation by editing this page on GitHub.