Deployment Overview
π SEAL360 Contract Deployment Status
This page provides a comprehensive overview of all SEAL360 smart contract deployments across different networks and versions.
π Current Deployments
Fuji Testnet (Active)
| Version | Status | Date | Contracts |
|---|---|---|---|
| v2.4.0 + Fee System | β Active | Jan 24, 2026 | 10 contracts |
| v3.3.4-clean + staking v2.2.0 | π΄ Deprecated | Jan 18, 2026 | 7 contracts |
| v3.3.3-ultimate | π΄ Deprecated | Jan 11, 2026 | 8 contracts |
| v3.3.3-ultimate | π΄ Deprecated | Jan 11, 2026 | 8 contracts |
Mainnet
| Network | Status | Expected | Notes |
|---|---|---|---|
| Avalanche C-Chain | π‘ Pending | Q1 2026 | After final audit |
| Ethereum | π‘ Planned | Q2 2026 | Cross-chain bridge |
π Version History
v2.4.0 (Current)
- Fee Distribution System with 3 new contracts
- Automated fee splitting: 33.33% Treasury, 33.33% Stakers, 33.34% Growth
- Enhanced Multisig Timelock (3-of-4 signatures)
- 100% dynamic deployment scripts (zero hardcoding)
- Complete contract verification on Snowtrace
- Full Details β
v3.3.3-ultimate
- Diamond tier implementation
- Advanced governance features
- Deprecated due to clean state requirement
v3.3.1
- Critical security patches (MEDIO-001, MEDIO-002, MEDIO-003)
- Gas optimizations
- Enhanced governance protections
π Deployment Checklist
Before deploying to any network, ensure:
Pre-Deployment
- All contracts compiled successfully
- Unit tests passing (100% coverage)
- Integration tests completed
- Security audit performed
- Gas optimization review
- Documentation updated
Deployment
- Deploy in correct order (Token β Core β Governance β Periphery)
- Verify all contract addresses
- Initialize contracts with correct parameters
- Transfer ownership to Timelock/Multisig
- Verify contracts on block explorer
Post-Deployment
- Test all contract interactions
- Verify ABI exports
- Update dApp configuration
- Update documentation
- Announce to community
π οΈ Deployment Tools
Supported Networks
// Hardhat configuration
export const networks = {
fuji: {
chainId: 43113,
rpc: 'https://api.avax-test.network/ext/bc/C/rpc',
explorer: 'https://testnet.snowtrace.io'
},
avalanche: {
chainId: 43114,
rpc: 'https://api.avax.network/ext/bc/C/rpc',
explorer: 'https://snowtrace.io'
}
};Deployment Scripts
Located in seal360-contracts/scripts/deploy/:
core/- Token, Staking, Vestinggovernance/- Governor, Timelockperiphery/- Bonding Curve, Badges
π Deployment Statistics
Gas Usage (Fuji v2.4.0)
| Contract | Deployment Gas | Optimization |
|---|---|---|
| SEAL360Token | ~2.1M | -15% |
| S360StakingRewards | ~3.8M | -12% |
| S360Governor | ~4.2M | -8% |
| S360TimelockController | ~1.9M | -10% |
| S360BondingCurve | ~2.5M | -18% |
Total Deployment Cost
- Fuji: ~0.5 AVAX ($20 at current prices)
- Mainnet Estimate: ~1.2 AVAX ($48 at current prices)
π Security Considerations
Multi-Signature Setup
Current Timelock Multisig (Fuji):
- Required Signatures: 4 of 7
- Signers: Core team members + advisors
- Emergency Actions: Whitelisted only
Access Control
Admin Roles:
βββ DEFAULT_ADMIN_ROLE (Timelock)
βββ PROPOSER_ROLE (Governor)
βββ EXECUTOR_ROLE (Governor + Multisig)
βββ EMERGENCY_ROLE (Multisig 4/7)π Quick Links
- v2.4.0 Current Deployment β
- Testnet Deployment Guide β
- Mainnet Deployment (Coming Soon) β
- Contract Verification β
- Troubleshooting β
π Need Help?
Developer Support
- π Read the full deployment guide
- π¬ Join our Discord developer channel (opens in a new tab)
- π§ Email: dev@seal360.net
Report Issues
- π GitHub Issues: seal360-contracts/issues (opens in a new tab)
- π Security: security@seal360.net