Adapter Classification

Every StakeEase adapter can be categorized into one of these four types:

Core Adapters

Contracts responsible for StakeEase's efficient working. The Multicall contract is the entry point for any instant (re)staking request. It invokes other adapters in a sequential order to achieve the desired output. The FeeManager contract is used to deduct protocol fees from the user (as an introductory promotion, the fee is currently set to 0 BPS).

Fusion Adapters

Contracts that oversee the execution of StakeEase's Fusion mode. These contracts batch user deposits at the protocol level, i.e., a separate batch is created for users who want to stake into Renzo, and a separate batch is created for users who want to stake into Ether.fi and so on. The fee for the execution of a batch is split across all the participants of that batch.

Swap Adapters

Contracts to swap user funds from the deposited asset to the relevant asset (ETH or a LST).

For example, if the user provides USDT, OpenOceanAdapter will be used to swap user funds to ETH (or some LST) before proceeding with the rest of the restaking process.

Stake Adapters

Contracts to handle liquid staking on different applications.

For example, LidoAdapter will be used to stake the user's ETH on Lido.

Restake Adapters

Contracts to handle restaking on different applications.

For example, KelpAdapter will be used to stake the user's Liquid Staking Token on Kelp.