# Liquid Staking & Vault Development Liquid staking and vault development: LST/LRT receipt tokens, validator routing, restaking, and slashing-aware risk controls. nsASTR (~$20M TVL) team. Canonical: https://www.metaborong.com/services/web3/liquid-staking-vaults Service: web3/liquid-staking-vaults ## Overview Most liquid staking forks copy the receipt token and skip the part that breaks: slashing-aware accounting under real validator load. Liquid staking and vault development is the smart-contract practice that issues a transferable receipt token for staked assets, then routes validators, tracks the exchange rate, and defends the vault against slashing before mainnet. ## What is it? Liquid staking and vault development is a smart-contract practice for protocol founders that issues a transferable receipt token in exchange for staked assets while keeping them liquid. Metaborong engineered nsASTR, a liquid staking product at roughly twenty million dollars in TVL on Astar, and built Memestakes, an in-house meme-coin staking vault. Our staking contracts have cleared four Hacken audit rounds. ## What we deliver - Vault contracts with validator routing and slashing-aware exchange-rate accounting. - Liquid receipt token: rebasing or wrapped, composable by downstream DeFi. - Restaking and validator-rotation logic with an exit-queue model. - Oracle and exchange-rate feed plus risk controls for slashing and depeg. - Mainnet deployment scripts, multisig handover, and a parameter runbook. ## Key concepts **Liquid staking token**: A liquid staking token (LST) is a transferable receipt minted when an asset is staked. It represents the staked principal plus accrued rewards, so holders earn yield while keeping a tradable token they can lend, supply as collateral, or use across DeFi instead of locking the underlying. **Restaking**: Restaking is the reuse of an already-staked asset, or its liquid staking token, to secure additional protocols in exchange for extra rewards. A liquid restaking token (LRT) represents this layered position. It raises yield but compounds slashing exposure, since one position now backs more than one network. **Validator routing**: Validator routing is the vault logic that distributes staked assets across a validator set and rebalances over time. Routing targets uptime, decentralization, and slashing risk rather than raw yield. An exit queue governs unstaking so withdrawals settle in order without forcing the vault to unwind every validator at once. **Exchange rate**: The exchange rate is the ratio between a liquid staking token and the underlying staked asset. It rises as rewards accrue and falls when slashing burns value. A non-rebasing vault holds the receipt supply fixed and lets this rate climb; an oracle publishes it so downstream protocols price the token correctly. ## How we work 1. **Validator & vault spec** We pin down the receipt-token mechanic and the validator-set strategy first. Rebasing or wrapped, in-protocol or external validator selection, exit-queue model, restaking posture, and how the exchange rate accrues are decided here. The spec covers routing logic, fee splits, and the slashing boundary between the vault and the staking layer. It is the document the auditor reads first. 2. **Contracts & keepers** We build the vault contracts and the off-chain keepers in parallel. Property-based tests cover the accounting invariants: total receipt supply, validator-side balance, and exchange-rate monotonicity. Fork tests run the vault against real validator data and simulated slashing. Keepers handle rotation, restaking, and exit-queue processing, and the two pieces are tested as one system before audit. 3. **Audit & integration** The contract suite goes to external audit while we ship the operator dashboard and the integration SDK. Downstream DeFi composing your receipt token needs the exchange-rate adapter and a clear guide, so that lands with the audit rather than after. Findings feed a second-round review; our staking contracts have cleared four Hacken audit rounds on prior work. 4. **Mainnet & operate** Mainnet deployment runs from a reviewed script. Validators are routed to, the receipt token is live, the oracle feed publishes, and keepers run under monitoring. We respond to slashing events, validator-set changes, and exit-queue load through the operate phase. nsASTR currently runs at roughly twenty million dollars in TVL on Astar, the operating envelope we engineer for. ## Tech stack Solidity (Contracts), Foundry (Testing), Astar / EVM (Chains), Gelato (Keepers), Chainlink (Oracles), The Graph (Indexing), Tenderly (Monitoring), TypeScript (SDK) ## When this fits ### Fits when - You're shipping a liquid staking or restaking product and need contracts, keepers, and oracle wiring in one engagement. - Receipt-token composability matters: DeFi protocols integrate your token and need an exchange-rate adapter and SDK. - Budget covers external audit and the operate-phase keeper, oracle, and monitoring work, not just contract delivery. ### Does not fit when - You want to fork an existing liquid staking codebase and deploy it on a new chain unchanged. - Validator selection is fixed to one operator with no rotation, no restaking, and no exit queue. - The vault is a throwaway mechanic for a token launch with no long-term operate-phase requirement. ## FAQ ### What is the difference between liquid staking and a vault? Liquid staking is the mechanic: you stake an asset and receive a transferable receipt token that keeps earning rewards. The vault is the smart-contract system that makes it work, holding the staked assets, routing validators, tracking the exchange rate, and processing the exit queue. A liquid restaking vault adds a layer, reusing the staked position to secure extra protocols for additional yield. ### How do you handle slashing risk in the receipt token? Slashing-aware accounting is part of the vault contracts from day one. When a validator is slashed, the loss propagates into the exchange rate through an accounting hook rather than being deferred or socialized opaquely. The vault logs every slashing event on-chain so depositors and downstream DeFi see exactly what happened. Validator routing spreads exposure across the set, and insurance integration is optional, not assumed. ### Do you run the validators? No. Validator operations sit with your team, an in-house operator, or a delegate set you choose. We engineer the vault, the keepers, the receipt token, the oracle feed, and the integrations. We document the interface contracts between the vault and the validator layer so an operator can plug in without contract changes, and the routing logic targets uptime and decentralization rather than a single operator. ### How does the receipt token integrate with downstream DeFi? Two paths. Rebasing, where the balance changes as rewards accrue, shipped with adapter contracts for integrations that do not handle rebasing natively. Or wrapped non-rebasing, where a wrapper holds the rebasing token and exposes a fixed-supply share whose exchange rate climbs. An oracle publishes that rate so lending markets and DEXes price it correctly. We ship the SDK and integration docs so DeFi teams adopt the token without back-and-forth. ### Can you migrate or upgrade an existing liquid staking vault? Yes, when an upgrade path or migration contract is feasible. We audit the existing vault, draft a migration plan that preserves user balances and downstream integrations, and run the migration against a forked node before mainnet. We have shipped both proxy-based upgrades and migration-contract approaches across our staking work, including nsASTR on Astar and our in-house Memestakes vault.