Restaking points: what you are actually underwriting

Restaking sells a yield on top of a staking yield and pays part of it in points. Points are not a yield. They are an unpriced claim on a token that does not exist, issued by a team that has not published terms, against security work that can be slashed. What you are underwriting lives in the slashing conditions.

Points are a claim, not a yield

A point balance is a number in a database. It has no price, no redemption right, and no conversion ratio until a token exists and a distribution is announced.

The honest model is an option: some probability of receiving some amount at some future date, with all three variables unknown. That is a description of what a points ledger is, not an accusation.

The comparison is against the alternative use of the same ETH. Staking paid 2.63% gross in Q3 2026, within a 2.6% to 3.3% full-year range, and more than 96% of ETH staking rewards came from new issuance rather than fees per Bitwise’s Q4 2026 figures. A restaking layer adding points has added a claim on top of a yield that is already mostly new issuance (staking yield is not income).

The slashing condition is the real term sheet

Restaking lets staked ETH secure additional protocols, called actively validated services. Each brings rules, and each rule is a route by which principal can be reduced.

The question is not how much a service pays. It is which action, by whom, causes a slashing event, and how much stake is exposed when it does. Some conditions are objective and enforced in code, such as signing two conflicting attestations. Others are committee judgements about liveness or operator behaviour, and those need reading, because a judgement call is a different risk from a cryptographic violation.

Correlation is the part that gets missed. If one operator runs validators across several services and one service faults, slashing can reach stake that is backing everything else. Diversifying across services does not help when the operator is the shared component. The operator list matters more than the service list, and the question of who secures a rollup has a name attached.

Your exposure is the operator’s exposure only if delegation is bounded

Delegation structure decides whether your risk is the risk you chose.

A bounded delegation caps how much stake an operator can attract, restricts which services the operator may join, and requires the delegator to approve changes. An unbounded delegation lets the operator add a service after you delegate, so the terms you agreed to are not the terms you hold.

Read for three things. Whether new services require your consent. Whether there is a cap per operator. And whether the penalty is proportional to the stake delegated to that operator or to the whole pool. The third is where the asymmetry hides: a small allocation to a high-risk service can expose the whole position if the penalty applies at pool level, turning a diversifying bet into a correlated one.

The exit queue meets the points ledger

Points usually vest, and the vesting clock starts on a date nobody outside the team controls. Meanwhile the underlying ETH has a queue of its own.

Ethereum’s exit queue held 850,000 ETH in October 2026 at a wait of about 14.8 days, and total stake was 43.8 million ETH on 23 October 2026. A solo validator needs 32 ETH, so most restakers reach the queue through a protocol or a pooled wrapper, and the wrapper’s own liquidity is a separate constraint.

The position therefore carries three locks: the service’s slashing exposure, the vesting schedule, and the validator exit queue. A user who models only the last has modelled the most visible lock and the shortest one.

What the pitch leaves out

The pitch is a number with a plus sign. The term sheet is a list of conditions under which the number turns negative.

None of this is a reason to avoid restaking. It is a reason to size it as a venture position, and to keep the staked amount separate from anything you might need in a drawdown.

There is a defensible version of the trade. Bounded delegation, a service list narrow enough to read, an operator with a limit you can name, and an amount you would not need to sell for a month. That is a position with a defined downside.

Verdict

Restaking points are not yield. They are an option on a future token, sold alongside a real and partly quantifiable increase in slashing exposure.

Underwrite the slashing condition first, then the delegation bounds, then the exit. If the terms of a service can change after you delegate, you are not holding a yield. You are holding whatever the operator decides next.