Endur
Endur is a liquid staking protocol on Starknet. Users stake STRK and receive xSTRK, which stays liquid while the stake earns. At the August 14, 2026 survey it held $6.0M across 6 pools, well below the size floor. A client position sized for an advised sleeve would be a large share of such a small venue, creating its own exit risk. We do not open an individual review until the protocol clears the size floor. One practice advising 100 households moves $1M to $8M into a venue based on the same research, and at this size that book would constrain exits. The file reopens if the protocol grows past the floor and holds there.
- TVL sustained above the retired TVL threshold for 30 days
Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-15.
The research file
Applicability to the surveyed record
Endur documents xSTRK as a Starknet liquid-staking receipt issued by an ERC-4626 vault. Deposits first meet withdrawal demand. Endur distributes excess STRK through delegator contracts to validators, and compounded staking rewards increase xSTRK’s exchange value. These steps make up the current liquid-staking mechanism.
Current observation and perimeter
The DefiLlama protocol API read on 2026-08-15 classified Endur as Liquid Staking, reported only Starknet, and showed approximately $5.56M TVL. Endur’s current docs also list BTC-denominated LST products, but this survey and its description remain focused on xSTRK. The protocol’s total size is below the shared v1 size floor.
Control and exit applicability
A validator registry approves validators, assets, and delegators, while an automated relayer manages allocations and processes withdrawals under contract rules. Redeeming xSTRK creates a queue NFT and draws funds from new deposits or validator unstaking. Normal completion ranges from hours to eight days and can reach fourteen in extreme demand. An instant DEX exit depends on secondary liquidity and price.
Why the class rule decides
The shared v1 size rule decides this case because Endur remains below the size floor despite its live, documented xSTRK system. We do not open an individual review until DefiLlama TVL clears the size floor for 30 consecutive days. We would then review registry and relayer authority, validator selection and concentration, contract upgrade control, Starknet staking dependencies, audits and incidents, xSTRK exchange-rate accounting, withdrawal-queue history, executable DEX liquidity, stressed exit, and named liquid-staking alternatives.
Research status
This is a capacity-unproven record for Endur, not a quality rejection or approval. Reported TVL says how big the venue is, not what the client owns, who can change the rules, or how a position exits at a proposed size. The individual review opens when the protocol clears the size floor.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Endur — liquid-staking architecture · primary · accessed 2026-08-15
Supports: ERC-4626 LST, withdraw queue, delegator contracts, validator registry, deposit and withdrawal flow - Endur — xSTRK mechanism · primary · accessed 2026-08-15
Supports: xSTRK receipt, exchange rate, staking rewards, auto-compounding - Endur — withdrawal log · primary · accessed 2026-08-15
Supports: NFT queue, funding sources, normal redemption, 14-day stress case, permissionless claim - Endur — mainnet contracts · primary · accessed 2026-08-15
Supports: Starknet deployment, xSTRK contract, withdraw queue contract, validator registry contract - DefiLlama — Endur survey record · secondary · accessed 2026-08-15
Supports: current TVL, Starknet perimeter, Liquid Staking category, survey observation
Inherited controls
The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.
| Chain | Verdict | Control | Control constraint |
|---|---|---|---|
| Starknet | Approved with limits | Mixed control | validity proofs and a regular exit window constrain control, but permissioned proposers and an instant emergency Security Council remain live dependencies. |