Run a Validator. Earn SLDS.
Join the identity-native consensus network. Validate credentials, produce blocks, and earn proportional rewards — with as little as 10,000 SLDS staked.
$ curl -fsSL https://releases.solidus.network/install.sh | sh # v0.1.0 testnet · Linux x86_64 + aarch64 · Ed25519-signed # requires curl, jq, openssl 3+
Choose Your Validator Tier
Each tier has different stake requirements, hardware needs, and responsibilities.
Light Node
- 2–4 CPU cores, 2–4 GB RAM
- 500 GB–1 TB SSD storage
- 100 Mbps+ network
- Full validator — relay + data availability
Subnet Validator
- 4–8 CPU cores, 8–16 GB RAM
- 1–2 TB NVMe SSD
- 250 Mbps+ network
- Full validator — higher stake weight
Core Validator
- 8–16 CPU cores, 16–32 GB RAM
- 2–4 TB NVMe SSD
- 250 Mbps–1 Gbps network
- Full validator — highest stake weight + cross-subnet
Estimate Your Rewards
Based on current network APY and fee volume. Actual rewards vary with network activity.
Built for Real Operators
Low Entry Barrier
A Light Node needs just 2–4 CPU cores and 2–4 GB RAM. Run on a ~$5–15/month cloud instance or spare home hardware.
Identity-Native Consensus
Every validator is a verified human. Proof of Identity consensus eliminates Sybil attacks at the infrastructure level.
Deterministic Rewards
Earn 70% of all network fees proportional to your stake weight and reputation score. No hidden cuts. No surprises.
Governance Weight
Validator stake weight directly maps to governance voting power. The people running the infrastructure shape the protocol.
Security You Can Verify
Every release is cryptographically signed, SHA256-verified, and open source. Inspect it before you run it.
GPG Signed Releases
Every release binary is signed with the Solidus Foundation GPG key (4096-bit RSA). Verify the signature before executing.
gpg --verify solidus-node.sig solidus-nodeSHA256 Checksum
Each binary ships with a SHA256 checksum published to our releases page. Compare before running.
sha256sum -c solidus-node.sha256MIT Licensed & Audited
Full source on GitHub. Binary reproducibility documentation. Independent security audit completed January 2026.
Get Running in 5 Minutes
One command verifies the release's Ed25519 signature + SHA256, then installs the node binary.
curl -fsSL https://releases.solidus.network/install.sh | shSystem Requirements
| RESOURCE | LIGHT NODE | SUBNET VALIDATOR | CORE VALIDATOR |
|---|---|---|---|
| CPU | 2–4 cores | 4–8 cores | 8–16 cores |
| RAM | 2–4 GB | 8–16 GB | 16–32 GB |
| Storage | 500 GB–1 TB SSD | 1–2 TB NVMe | 2–4 TB NVMe |
| Network | 100 Mbps+ | 250 Mbps+ | 250 Mbps–1 Gbps |
| Monthly Infra Cost | ~$5–30 | ~$30–90 | ~$120–400 |
| Uptime Requirement | 95% | 95% | 99.5% |
Frequently Asked Questions
Slashing reduces your staked SLDS by a percentage depending on the violation. The most common cause is extended downtime (12+ consecutive hours = 0.5% slash). Double-signing results in 5% plus suspension. The Solidus dashboard alerts you immediately. Most validators on good hardware never experience a slash event.
Yes. A Light Node needs 2–4 CPU cores, 2–4 GB RAM, and a stable 100 Mbps connection. A modern desktop, mini-PC, or ~$5–15/month cloud instance qualifies. A static IP is recommended but not required for Light Nodes.
Light Nodes sync in 10–30 minutes. Subnet Validators sync in 1–4 hours. Core Validators syncing full history may take several hours depending on disk IOPS and network speed.
Rewards accumulate every block and are finalized at the end of each epoch (7 days). They are deposited to your reward address automatically. You can track accruing rewards in the dashboard in real time.
When you unstake, your SLDS remains locked for 21 days before returning to your wallet. During this period it earns no rewards. This delay prevents last-second stake manipulation around governance votes.
Yes. All validators must complete KYC Level 2 (government ID + liveness detection) through verify.solidus.network. This is non-negotiable — Proof of Identity consensus requires every validator to be a verified unique human.
You can operate multiple validator nodes, but each needs a distinct node identity DID. All nodes controlled by the same person count toward your aggregate stake weight in governance but must be registered individually.
APY is a function of total network fees collected divided by total staked SLDS, annualized. As network usage grows, APY increases. As more SLDS is staked, APY is diluted. The dashboard shows your live effective APY based on current network conditions.
