Solon does not slap a 'compliance' label on — risk control is written directly into the contracts: whitelists, freezes, forced transfers, proof-of-reserve gating and multi-sig governance, all enforced by code, logged on-chain, and re-checkable by anyone. This page discloses our security architecture, bug bounty program and disclosure policy.
Defense in depth across three layers: contracts enforce rules, governance splits power among multiple parties, and infrastructure provides cross-region redundancy. No single point can act maliciously on its own.
| Layer | Mechanism | Notes |
|---|---|---|
| Contract layer Code is law — cannot be bypassed |
Identity whitelist — IdentityRegistry | Both sides of a securities-grade transfer must be KYC-registered; unregistered addresses revert immediately |
| Compliance freeze / forced transfer | Any transfer to or from a frozen address reverts; judicial scenarios such as court orders allow forced transfers, fully logged | |
| Emergency pause | One click halts all contract transfers in extreme scenarios; resumption is likewise logged | |
| Proof-of-reserve gating — SolonProof | Insufficient reserves, expired or revoked proofs, failed audits — 9 gating scenarios auto-block; see the gate reason-code table | |
| Governance layer Multi-party control, fully logged |
Multi-sig governance 2-of-3 | Critical actions — bridge parameters, treasury spending, emergency pause — require committee multi-sig; proposals and confirmations are all on-chain |
| Mandatory pre-issuance filing | The issuance wizard mandates 13 required fields across regulatory filing / legal opinion / dispute resolution — no filing, no issuance | |
| Infrastructure layer Dual-region active-active, chain never halts |
Dual validators, Clique PoA | Singapore + Seoul nodes alternate block production; the chain keeps running if either goes down. Quarterly disaster drills |
| Real-time monitoring & tiered alerts | The status page publicly assesses P1/P2/P3 severity, backed by the emergency playbook |
Open to security researchers worldwide. Rewards are tiered by impact, benchmarked against major L1 standards and scaled to Solon, paid in USDT.
| Severity | Bounty (USD) | Examples |
|---|---|---|
| Critical | $50,000 | Direct loss of funds; consensus compromise (double-signing / illegitimate blocks); bypassing whitelist or freeze to transfer; forging reserve proofs to pass the gate |
| High | $20,000 | Unauthorized mint / burn; bypassing emergency pause; gate wrongly admitting non-compliant assets; single-party manipulation of the multi-sig flow |
| Medium | $5,000 | Core function of a single asset broken (cannot transfer / claim dividends); critical events not logged; faucet limits bypassed |
| Low | $1,000 | Misleading display errors on explorer / status pages; RPC behavior deviating from Ethereum standards; front-end injection issues |
Our coordinated disclosure process with researchers is transparent, timely and predictable.
| Item | Commitment |
|---|---|
| Report channel | Email hi@solon.digital — subject line prefixed with [SECURITY]; please include reproduction steps, impact scope and a PoC |
| Acknowledgement | Acknowledged within 1 business day |
| Initial assessment | Severity and remediation plan within 7 days |
| Coordinated disclosure window | Up to 90 days: both parties stay confidential until the fix ships, then we publish credits (anonymous if preferred) and a vulnerability summary |
| Safe harbor | Research conducted under these rules will not face legal action from us |
In scope: Solon's official protocol contracts (IdentityRegistry / SolonProof / DividendPool / LimitBook / SolonBridge / SolonOffering — addresses in the contract address book), public node RPC and the official front-end. Out of scope: contracts deployed and operated by third parties, and deprecated legacy contracts (as labeled in the explorer).
Incidents are handled by impact tier, sharing the same P1/P2/P3 language as operations monitoring, each tier with a written playbook.
| Tier | Response time | Typical scenarios & first action |
|---|---|---|
| P1 · Critical | within 15 minutes | Funds at risk / stalled block production / abnormal bridge flows → multi-sig immediately pauses the affected contracts; stop the bleeding on-chain first |
| P2 · Severe | within 1 hour | Node height divergence / performance degradation / liquidity shortage → locate root cause, degrade service if needed |
| P3 · Notice | same day | Elevated RPC latency / display anomalies → fix and review alert thresholds |
Full emergency playbook →Live status page →
What institutional due diligence asks — who audited, what was audited, where the reports are — is disclosed and updated here.
| Item | Status | Notes |
|---|---|---|
| On-chain contract function tests | Done | Whitelist / freeze / forced transfer / emergency pause all passed on deployment day (results in the developer docs） |
| PoR gating live runs | Ongoing | The full PoR feed → gate → auto-pause pipeline runs continuously on testnet; the ledger is public |
| Third-party security audit | Before mainnet | All protocol contracts will be audited by an independent security firm; reports will be published here |
| Bug Bounty | Open | See the bounty tiers above; escalating to a long-term program at mainnet |
Security is not a promise — it is a running system. These pages read on-chain data directly; anyone can verify independently.
PoR auto-pause ledger → Dual-proof view → Network status → Block explorer → Multi-sig governance log →
Solon