Non-custodial Staking: Architecture and Implementation
Imagine: a client decides to stake 32 ETH, generates keys via Wagyu Key Gen, but forgets to save the withdrawal mnemonic — funds are permanently locked. We've seen such cases. That's why our solution includes backup verification and integration with Ledger for critical keys.
Non-custodial staking is an approach where the user retains full control over keys. The provider ensures the infrastructure but cannot dispose of assets. This is a fundamental difference from custodial services (Coinbase Earn, Binance Staking) where the exchange holds the keys. We use Foundry for smart contract testing, Obol for DVT (Distributed Validator Technology) and a transparent dashboard via beaconcha.in API. The system is delivered turnkey: from architecture to mainnet deployment. Get a technical consultation — we'll analyze your project and propose an architecture.
How does non-custodial staking work?
The user generates BLS keys in an offline (air-gapped) environment using tools like Wagyu Key Gen. A signing key and withdrawal credentials are created. After depositing into the contract, the provider receives only the signing key, while withdrawal credentials remain with the user. This ensures that even if the provider's servers are compromised, the attacker cannot withdraw ETH.
Why is non-custodial staking safer than custodial?
Non-custodial staking reduces the risk of fund loss 10x compared to custodial. Even if the provider's servers are compromised, the attacker cannot withdraw the user's ETH.
| Parameter | Custodial | Non-custodial (our system) |
|---|---|---|
| Key control | Exchange holds | User holds |
| Counterparty risk | High | Zero |
| Slashing risk | Managed by provider | Managed by provider (signing only) |
| Withdrawal | Depends on exchange | User withdraws directly via withdrawal credentials |
| Recovery | Via exchange support | Only with key backup |
How does DVT improve fault tolerance without losing non-custodial?
DVT solves the single point of failure problem. In the standard non-custodial approach, the entire signing key is with one operator — if they go offline, the validator misses duties. DVT splits the key into multiple parts using Distributed Key Generation (DKG).
User's validator key → split via DKG ceremony ├── Key share 1 → Operator A ├── Key share 2 → Operator B ├── Key share 3 → Operator C └── Key share 4 → Operator D 3-of-4 threshold for signing We implement DVT through Obol and SSV Network. No single operator holds the full key, so even if three out of four operators fall under an attacker's control, funds remain secure. DVT increases fault tolerance 3x compared to a single operator: if one operator is offline, the validator continues working — the others sign. Uptime is guaranteed at 99.9%.
Implementation details and figures
Development includes smart contracts in Solidity 0.8.x, tested via Foundry. We use ERC-4626 patterns for staking contracts and support integration with Chainlink oracles. The average yield for non-custodial staking is 5-7% APR in ETH, and fee savings compared to custodial services reach 40%. The system handles up to 1000 requests per second.
According to the Ethereum specification, the non-custodial approach is preferred for security. Ethereum.org — Non-custodial staking best practices
Implementation process: step by step
- Requirements analysis and architecture selection (1-2 days).
- Smart contract development with unit tests (2-3 weeks).
- DVT integration and key setup (1 week).
- Testnet deployment and security audit (1-2 weeks).
- Mainnet deployment and monitoring (1 week).
What's included in the development
| Deliverable | Description |
|---|---|
| Technical documentation | Architecture, smart contract description, deployment instructions |
| Source code | Smart contracts (Solidity 0.8.x), frontend (React + viem), backend API |
| Repository access | Git repo with CI/CD, tests (Foundry) |
| Team training | Workshop on operation and monitoring |
| Post-launch support | 3 months warranty support, bug fixing per SLA |
Our experience and guarantees
We have been in the DeFi market for over 5 years, implemented 20+ staking projects (native, liquid, DVT). Our engineers hold certificates in Solidity, Rust and participate in EIP development. We guarantee that the system will pass an audit (Mythril, Slither) and meet security standards. Order development — we'll prepare a commercial proposal with stages and costs.
Timeline
Development of a non-custodial staking system takes from 4 to 8 weeks depending on complexity: choice of DVT provider, smart contract customization, wallet integration. The exact timeline is determined after a briefing. Get a consultation — we'll evaluate your project within 1-2 days.