# User Flow

**Step 1)** Users deposit funds into the Fusion smart contract. The Fusion contracts maintain a user mapping for each strategy (for example Stader-Kelp, Lido-Kelp). 

{% hint style="success" %}
Funds in the Fusion contract can be withdrawn anytime until they are (re)staked.
{% endhint %}

**Step 2)** At regular intervals, a relayer triggers a relay transaction on the Fusion contract for each strategy.

**Step 3)** Within this transaction, all the ETH stored in the contract for that strategy (except for the ETH deducted to cover the transaction fee) will be (re)staked. For example, if a user has deposited funds into the Stader-Kelp strategy, then the users ETH will be liquid staked into Stader for ETHx, which will further be staked into Kelp for rsETH.

**Step 4)** The fee is deducted based on the number of users involved in the transaction and is sent to the executor for this transaction.

**Step 5)** The contract distributes rsETH to each user based on their proportionate share of deposited ETH.

{% hint style="info" %}
Only the contract admin can set the gas limit used for calculation of fees. The admin will have no other privileges.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.stakeease.com/aggregator/technical/stakeease-fusion/user-flow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.