Frequently Asked Questions

Solidus is a decentralized identity blockchain. It lets apps verify users once — KYC, email, phone — and issue a portable Verifiable Credential. Users present that credential anywhere without repeating the verification process. No central server owns the data.

Auth0 and Okta are identity providers — they authenticate users on behalf of an app. Solidus issues cryptographic credentials that users carry. The difference: with Solidus, the user owns their credential, not the service. Cost is $0.01 per re-presentation vs Auth0's $0.023/MAU/month.

Yes. Solidus runs its own BFT consensus chain purpose-built for identity operations. It is not Ethereum or a fork of any existing chain — it's designed from first principles around DID and VC state management.

PoI is Solidus's consensus mechanism. 21 validators rotate committee membership. They use a PBFT-variant with stake-weighted voting. Finality is 1–2 seconds. The network can tolerate up to 7 dishonest validators before safety is at risk.

Yes. All protocol code is MIT licensed. Repository: github.com/solidusnetwork

DIDs (Decentralized Identifiers) are W3C-standardized identifiers that users control, not companies. A DID looks like `did:solidus:z6Mk...`. The user holds the private key. DIDs are portable — they work across any app that understands the W3C standard.

Free tier: 1,000 verifications/month at $0. After that: re-presentation of existing credential = $0.01. New KYC Level 2 = $5. Level 3 = $20. All paid per-event, no monthly fee.

No. Pay per verification. If you run zero verifications in a month, you pay zero. Subscription plans (Startup, Growth, Enterprise) are available for teams that want predictable billing.

One cryptographic check. A user who already has a Solidus credential costs $0.01 to verify — you're just checking the signature. A user doing KYC for the first time costs $5 (L2) or $20 (L3).

No. The fee split is transparent and on-chain: 70% to validators, 20% to the Foundation treasury, 10% burned. No platform fees, no annual minimums, no overage charges.

1,000 verifications/month. 1 app. Sandbox mode. Full API access. Full docs. No credit card required.

Minimum 10,000 SLDS stake. Register at node.solidus.network. Median onboarding time is ~2 minutes after stake is confirmed.

Light Node: 2 vCPU, 4GB RAM, 100GB SSD, 100 Mbps. Subnet Validator: 4 vCPU, 16GB RAM, 500GB SSD, 1 Gbps. Core Validator: 8 vCPU, 64GB RAM, 10TB storage, 10 Gbps.

70% of protocol fees are distributed proportionally to stake weight. Light Node = 1× multiplier, Subnet = 10×, Core = 100×. Expected APY ranges from 8.5% to 14.2% depending on tier and network volume.

Yes. Slashing conditions: double-signing = 100% slash, excessive downtime = 0.5% per epoch, invalid block proposal = 10%. Evidence must be submitted within 7 epochs.

28-day cooling period after initiating unstake. Earnings continue during cooling period.

Sign up at docs.solidus.network for an API key. `npm install @solidus-network/sdk`. Median time from API key to first production verification: 4 hours.

JavaScript/TypeScript (first-class), Python, Go, Rust, Java. React Native support included in the JS SDK.

Yes. Sandbox is free, unlimited. You get simulated verification results, configurable outcomes (pass, fail, timeout, document_rejected), webhook replay, and time-travel for testing credential expiry.

Median 4 hours from API key to production. Auth0 migration median: 2 days. This includes replacing your existing auth calls and testing the credential flow.

docs.solidus.network — quickstart, SDK reference, API reference, webhooks guide, and sample projects for major frameworks.

No PII is stored on-chain. We store a BLAKE3 hash of the document plus an Ed25519 signature from the issuer; the credential payload itself never touches the chain. Off-chain, document images are deleted after 30 days and session recordings after 365. BBS+ selective-disclosure proofs (reveal a subset of credential fields, hide the rest) are live on testnet, with the full issuer flow shipping next and an external audit pending. ZK predicate proofs (e.g., age ≥ 18 without DOB) remain on the roadmap.

BFT consensus requires 67%+ honest validators to make progress. One hacked validator cannot manipulate the network. An attacker would need to compromise 8+ validators simultaneously — economically prohibitive given stake requirements.

Not assessed. There is no DPIA, no DPO and no records of processing, and the DPA is an unreviewed draft. What exists is posture rather than compliance: no-custody by default, configurable retention, and automated deletion on 30-day (documents) and 365-day (session recording) timers. There is no user-initiated erasure and no account-deletion path; an erasure request goes to [email protected] and is handled by hand. The current status of every framework we are asked about is published at verify.solidus.network/.well-known/solidus-compliance.json.

Protocol code is MIT open source and publicly reviewable on GitHub. SOC 2 Type II and ISO 27001 are future targets. The codebase is fully transparent for community and third-party security review.