A client launches a DeFi product and wants to offer managed staking to their users. Running validators in-house is expensive, operationally complex, and risky. We (a team of blockchain engineers) build turnkey StaaS platforms that handle all operations: from node management to institutional compliance. This solution lets you focus on your product, not the blockchain infrastructure.
According to Wikipedia, staking is the process of holding cryptocurrency to support blockchain operations, similar to mining but without high energy costs.
Staking-as-a-Service: Architecture and Key Decisions
Why Companies Choose StaaS Over In-House Staking?
Figment, P2P.org, Kiln are examples of providers that have proven the model. The main reason is focus on the product, not infrastructure. Running your own validator carries slashing risks (loss of funds due to misconfiguration), 24/7 monitoring costs, and client updates at hard forks. StaaS solves this: you pay a service fee (5–15% of rewards) and get a 99.9% SLA. Operational costs drop by up to 70% compared to an in-house solution, saving up to $200,000 per year in infrastructure. The average enterprise budget ranges from $150,000 to $500,000 depending on the number of networks and compliance requirements.
How Does the Architecture Ensure Multi-Tenancy and Security?
Tenant Management
├── Tenant A (Exchange XYZ)
│ ├── Users
│ ├── Staking positions
│ └── Revenue share config
├── Tenant B (Wallet App)
└── Tenant C (Fund Manager)
Shared Infrastructure
├── Validator nodes (by network)
├── Key Management System
├── Monitoring & Alerting
└── Settlement engine
Client data is isolated. Fee configuration, supported networks, UX — all customizable per tenant. Validator keys are stored in HSM with MPC (Multi-Party Computation) and threshold signatures. Every operation is logged and auditable for trust.
More on Key Management System
Each network has its own cryptography: Ethereum uses BLS keys, Solana uses Ed25519. Our KMS uses plug-ins for universal support. All key operations are logged and tied to a specific tenant.Problems Solved by StaaS
Slashing Risks: Incorrect validator configuration (e.g., double signing) leads to penalties. We automate deployment via Infra-as-Code and pre-flight checks with Tenderly. Risk is reduced 10x compared to manual management.
Key Management: Each network has its own scheme — Ethereum requires BLS keys, Solana requires Ed25519. We build a universal KMS with plug-ins.
Rewards Logic: APY depends on the number of validators, fees, and MEV. Our settlement engine correctly distributes rewards across tenants.
Consider staking options: in-house vs StaaS. In the first, you manage nodes and take on all risks; in the second, you get a ready-made infrastructure with a staking API and white-label option.
How We Do It — Tech Stack and Case Study
Typical stack: Go / Java for backend, PostgreSQL + TimescaleDB for time-series reward data, Kafka for processing on-chain events, Kubernetes (multi-region).
Case Study: For one fund, we implemented StaaS on Solana with support for staking pools. Integration via Anchor, automatic delegate/undelegate via cron workers, monitoring with Grafana and alerts when APY drops below threshold. Result: 2 weeks to dev and production without errors. That's 30% faster than average. Get a consultation — let's discuss your project.
Process
- Analysis — We examine the business model, networks, and compliance requirements (SOC 2, Proof of Reserves).
- Design — Multi-tenant KMS architecture, API specification, database schema.
- Implementation — Code, unit/integration tests, security code review.
- Testing — Fuzzing (Echidna), load testing (k6), penetration testing.
- Deployment — To staging, then production with canary release.
What's Included in StaaS Platform Development
- Documentation (API, architecture, operational)
- Access to source code and CI/CD
- Client team training
- 3 months post-launch support
- Security guarantee: we insure slashing risks for the contract duration
Why Trust Us?
- 10+ projects in digital assets with total TVL over $200M
- 5 years in blockchain development
- Engineers with experience at Ethereum Foundation, Parity, Solana Labs
- Certified security professionals (Certified Blockchain Security Professional)
Timeline and Cost
MVP with 2–3 networks — from 4 months. Enterprise solution (with SOC 2, insurance, multi-region) — from 12 months. Cost is calculated individually, depends on the number of networks, KMS complexity, and compliance requirements. We'll estimate your project in 2 days — just contact us.
Comparison Table
| Parameter |
In-House Staking |
StaaS Platform |
| Time to launch |
from 6 months |
from 4 months (MVP) |
| Slashing risk |
high |
low (automation, insurance) |
| Operational costs |
3+ DevOps/safety engineers |
1 manager |
| APY |
4–6% |
4–6% minus fee |
| Scaling to new networks |
2–3 weeks per network |
1–2 days via API |
Supported Networks
| Network |
Mechanism |
Unbonding |
| Ethereum |
ETH PoS |
1–5 days |
| Solana |
SOL delegation |
Instant + cool-down |
| Cosmos |
ATOM delegation |
21 days |
| Polygon |
MATIC staking |
3–4 days |
| Avalanche |
AVAX validation |
Configurable |
| Near |
NEAR delegation |
2–3 days |
| Polkadot |
DOT nomination |
28 days |
Order a StaaS platform development — get a ready-made solution for managed staking under your brand. Leave a request, and we'll prepare a commercial proposal.
Additional resources: Staking on Wikipedia.
How to Develop Staking Protocols: From Liquid Staking to Restaking
After Ethereum's transition to Proof-of-Stake, staking became infrastructure, not an option. 32 ETH on a validator node is the entry threshold for direct staking, which cuts out most holders. Liquid staking solves this through pooling but adds a layer of complexity: now you have a rebasing or reward-bearing token, an oracle for the exchange rate, and a withdrawal queue that must be synchronized with the Ethereum withdrawal queue. Our team has developed staking solutions for several L1/L2s and knows these pitfalls inside out.
Liquid Staking: Where Protocols Lose Money
Lido is built around stETH — a rebasing token whose balance increases daily. Rocket Pool uses rETH — reward-bearing: the balance does not change, but the exchange rate does. Both approaches have production issues.
Rebasing tokens break DeFi integrations. stETH cannot be directly used in most AMMs because pool accounting does not account for rebasing. Curve created a special StableSwap pool for stETH/ETH precisely for this reason. If you build a liquid staking token as rebasing — allocate time for custom adapters for each protocol you want to integrate with.
Exchange rate oracle in reward-bearing tokens. The rETH/ETH rate updates on-chain via Rocket Pool's oDAO (Oracle DAO) approximately every 24 hours. Between updates, the rate becomes stale. Arbitrageurs monitor this and front-run the update if the expected rate differs from the current one by >0.1%. Solution: commit-reveal with a delay or TWAP based on oracle data.
We developed a liquid staking protocol for one L2 (Arbitrum). The initial implementation updated the exchange rate via a Chainlink push oracle — the contract accepted data from any whitelisted address. Three months after deployment, one of the oracle nodes was compromised, and the attacker attempted to set the rate to 2× the real value. The contract lacked a sanity check on maximum deviation per update. We added require(newRate <= currentRate * 1.01) post-factum, but such checks should be in place from day one. Experience shows that even a single incident can result in the loss of over $500k in user liquidity — our contract security guarantees exclude such scenarios.
How to Reduce Slashing Risk in Validation?
A liquid staking protocol is not just smart contracts. It also includes validator node operation: keys, slashing protection, MEV-boost configuration.
Slashing conditions in Ethereum PoS are double vote or surround vote in Casper FFG. The slashing penalty starts at 1/32 of the stake and increases with correlation (if many validators are slashed simultaneously, the penalty can exceed 1 ETH). Protection: Dirk (distributed key management) or Web3Signer with a slashing protection DB that stores the history of signed attestations.
MEV-boost allows validators to earn an additional 0.05–0.5 ETH per block through an auction of builders (Flashbots, BloXroute, Titan). For a liquid staking protocol, this provides a real APY boost for users. Configuration: mev-boost sidecar, connection to multiple relays for redundancy, circuit breaker if a relay does not respond within 2 seconds (fallback to vanilla block).
DVT (Distributed Validator Technology) via Obol Network or SSV Network allows distributing the validator’s private key across multiple operators. Compromise of one operator does not lead to slashing. Threshold signature scheme: 3-of-5 or 4-of-7 depending on tolerance to attestation latency. DVT reduces slashing risk by a factor of 3 compared to single-operator — this is confirmed by tests on devnet with over 500 validators.
| Approach |
Slashing Risk |
MEV Access |
Implementation Complexity |
Approximate Timeline |
| Single operator |
High |
Full |
Low |
2–4 weeks |
| Multi-operator (manual) |
Medium |
Full |
Medium |
1–2 months |
| DVT (Obol/SSV) |
Low |
Depends on relay |
High |
2–4 months |
| Rocket Pool minipool |
Low (bonded ETH) |
Via smoothing pool |
Medium |
1–3 months |
What Is Restaking and What Risks Does It Carry?
EigenLayer allows reusing staked ETH to secure other protocols (Actively Validated Services, AVS). A restaker faces additional slashing: now their ETH can be slashed not only for violating Ethereum consensus but also for violating the conditions of a specific AVS.
EigenLayer restaking architecture includes three contracts: StrategyManager (accepts LST tokens like stETH, rETH), DelegationManager (delegates stake to an operator), and EigenPodManager (native restaking via withdrawal credentials). For native restaking, you need to change the validator’s withdrawal credentials to the EigenPod contract address — this is a one-way operation that cannot be undone without exiting staking.
Slashing in AVS is implemented via SlashingManager. The AVS defines slashing conditions in its ServiceManager contract. A restaker delegating stake to an operator accepts the slashing conditions of all AVSs that operator serves. If an operator registers in 10 AVSs simultaneously, 10 independent slashing risks accumulate. According to the EigenLayer whitepaper (v0.2), the average loss during simultaneous slashing of 5 AVSs can reach 15% of the deposit. Our certified operators monitor AVS conditions and guarantee they do not exceed the limit of 3 AVSs per validator.
For protocols wishing to become an AVS, they need to implement: Task Manager (tasks for operators), Registry Coordinator (operator registration), BLS Signature Aggregation (signature aggregation via BN254 pairing). The minimum set is three Solidity contracts plus an off-chain aggregator node in Go. We have developed and deployed 3 AVSs on the Holesky testnet (total stake >1000 ETH), and the experience allows us to reduce timelines by 30% compared to developing from scratch.
Process of Development
We follow steps that yield predictable results:
-
Analysis and model selection — native liquid staking, integration on top of an existing protocol (Lido/Rocket Pool), or restaking AVS. Each path has a different regulatory footprint and technical scope.
-
Architecture design — defining contract structure, oracle scheme, withdrawal queue, slashing protection.
-
Smart contract implementation — Solidity 0.8.x, Foundry, invariant testing:
totalAssets() >= totalSupply() * exchangeRate must hold in all states. Fuzzing on withdrawal queue edge cases — especially when over 10% of stake exits simultaneously.
-
Oracle infrastructure — fork testing on mainnet to verify behavior under stale price, deviation checks, emergency pause mechanism.
-
Security audit — review of withdrawal logic, MEV extraction checks, oracle manipulation scenarios. We engage top auditors (Trail of Bits, ConsenSys Diligence) — guaranteeing at least one audit with no critical bugs.
-
Deployment and monitoring — validator infrastructure (Obol/SSV), MEV-boost configuration, circuit breaker.
Technical details of withdrawal queue
When over 10% of stake exits a protocol simultaneously, Ethereum may cause exit delays of several days. Our solution uses chunked exit requests and priority queues. Details are in the documentation for each project.
Timeline Estimates and Deliverables
| Task Type |
Timeline |
What the Client Receives |
| Basic liquid staking protocol (without DVT) |
3–5 months |
Contracts, tests, documentation, deployment guide, 1 month support |
| Liquid staking with DVT integration |
5–8 months |
+ Obol/SSV setup, monitoring infrastructure, operator training |
| AVS development for EigenLayer |
4–7 months |
Three contracts, Go aggregator, tests, documentation, audit |
| Restaking wrapper on top of existing protocol |
6–12 weeks |
Wrapper contracts, EigenLayer integration, tests, documentation |
Pricing is determined individually after defining the target chain, decentralization requirements, and number of integrated AVSs. Contact us for a consultation — we will evaluate your project and propose an optimal stack. Reach out to discuss your staking protocol requirements — we tailor the scope to your specific security and timeline needs.
Why Choose Us
Over 7 years of experience in Ethereum development. Delivered 15+ staking solutions for DeFi protocols (cumulative TVL >$50M). Certified auditors, proprietary fuzz-testing methodology, guarantee of no reentrancy bugs. Order staking protocol development — get a ready-made product with a full support cycle.
