FOLLOW THE MECHANISM
- 1Base position
Assets already support staking or are represented by a receipt.
- 2Allocate
An operator commits eligible stake to additional service conditions.
- 3Perform
Services pay rewards and can enforce specified penalties.
- 4Exit
Deallocation and withdrawal rules release remaining claims.
A conceptual sequence. Real implementations can add steps, intermediaries, and conditions.
Reuse capital, add duties
Restaking aims to let assets supporting one system also back another service. An operator might validate additional messages, attest to data or perform other agreed work. The capital is not multiplied: more obligations are attached to it. Rewards for those extra duties may come from service fees or incentives, while the original staking process continues under its own rules. Calling the combined result enhanced staking can conceal how different the added services and loss conditions are.
The allocation boundary matters
EigenLayer’s official contract documentation describes operator sets and allocations of stake that can be subject to slashing. The precise rules are determined by the contracts, registered services, operator allocations and deployment version. An operator choice is therefore more than a reward-rate choice: it can determine which additional conditions the delegated position is exposed to. This explanation uses the current documentation to identify the mechanism, without asserting that every service, asset or deployment has identical enabled penalties.
Follow the reward and loss paths separately
An illustrative position can earn base staking rewards and an additional service reward, with operator fees deducted under each arrangement. A base-layer penalty and a service-level penalty are different events, and either can affect the value eventually available. Liquid restaking wrappers add another receipt, accounting system and exit path. A reward token may also have a different price from the staked asset, so adding their percentages without conversion can be meaningless. The balance sheet should keep each reward unit and obligation distinct.
Shared operators can transmit problems
If many services rely on overlapping operators or collateral, their apparent security may be correlated. A bug, ambiguous rule or widespread operator outage can produce several simultaneous problems. Withdrawal delays can exist so claims can still be enforced after an operator requests an exit. Restaking is not a promise that the base chain will reimburse losses in an added service. Its usefulness and risk depend on which duties are verifiable, how penalties are authorized, and whether the committed collateral realistically covers the obligations.
MAKE IT CONCRETE
Illustrative overlapping exposure
One 100-unit position backs two services. Reporting 100 units for each service does not create 200 independent units of loss-absorbing capital. Allocation rules determine how much each can actually reach.
FAILURE PATHS & COMMON MISREADINGS
Where the model can break
- Extra rewards correspond to extra obligations and dependencies.
- A historical whitepaper is not proof of today’s deployment settings.
KEEP EXPLORING