StakeEase
Launch App
  • Overview
  • Background
    • EigenLayer
      • What is EigenLayer?
      • EigenLayer Components
      • Why EigenLayer?
      • Challenges with EigenLayer
    • Restaking Protocols
      • Intro to Restaking Protocols
      • Benefits of Restaking Protocols
      • Challenges with Restaking Protocols
  • StakeEase
    • sxETH: A Unified LRT Index
    • StakeEase Points (SEP)
    • StakeEase Referral System
    • Security
      • Audit Reports
    • Guides
      • Using the sxETH Testnet
      • Using the StakeEase Testnet
    • Contract Addresses
  • Aggregator
    • Overview
    • Technical
      • Components
      • Adapter Classification
      • User Flow
      • Workflow
      • Native Restaking
        • User Guide
        • Workflow
      • StakeEase Fusion
        • User Flow
        • Calculations
      • Contract Addresses
    • Fee Structure
    • Aggregator APIs
      • Features
      • Swagger API Reference
  • Misc
    • Roadmap
    • FAQs
    • Socials
      • Twitter
      • Discord
      • Telegram
      • Medium
    • Brand Kit
    • Terms of Service
Powered by GitBook
On this page
  1. Aggregator
  2. Technical

Workflow

PreviousUser FlowNextNative Restaking

Last updated 7 months ago

In the previous section, we took a look at StakeEase's user-facing flow. In this section, we'll take a look at what goes on behind the scenes to restake users' funds on their desired platform. Let us consider a user who wants to (re)stake their ETH on Ethereum by liquid-staking them on Lido and then restaking the received stETH on Kelp. This is the flow of all the contract interactions to achieve this:

In the case of cross-chain (re)staking, users will provide their funds to Nitro's contract on the source chain, which will bridge them to Ethereum. Once the funds arrive on Ethereum, Nitro's Ethereum contract will invoke the StakeEase Multicall contract, following which the flow remains the same, as shown in the diagram above.