Security Model
How network stays protected
Selendra security is based on Nominated Proof-of-Stake.
Stake is bonded for 14 eras, and validators who underperform lose rewards.
The deployed runtime carries no pallet_offences, so there is no automated slashing path today.
Validator Security
- Minimum bond: 25,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: deterministic finality, finalized blocks never revert
- Finality lands about 1s after the block (measured); until then a block is only probabilistic
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
2027: Security audit, expand to 20 validators, bug bounty program
2028: Expand to 50+ validators, advanced anomaly detection