> For the complete documentation index, see [llms.txt](https://etherfi.gitbook.io/etherfi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://etherfi.gitbook.io/etherfi/~/changes/8Jd9g7SmBTNMrbOKtUZq/getting-started/decentralized-application.md). # Decentralized Application Web Interface to ether.fi's Staking Smart Contracts ## Stakers In order to maintain control of one's staked ETH, a staker must generate and store his / her own keys. A complex but \*necessary\* step which Etherfi's decentralized application manages and simplifies. Here are the basic steps: * **Navigate to the application**: ether.fi >> App (top right corner) * **Connect your wallet** (metamask, trezor, ...) ether.fi >> Connect (top right corner). Once done you should see your wallet's public address abbreviated where the Connect button is, and you should be navigated to the LP tab. * **LP - Liquidity Pool (tab)** * On the liquidity pool tab, you can easily exchange ETH for eETH and back. To toggle between currencies, click on the arrow key between the text fields. * eETH accrues a relative claim on the ETH in the pool * Here's the LP interface: ![](https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2F1QkLl3apBH6XnXWn41cl%2FScreen%20Shot%202023-02-27%20at%2011.31.36%20AM.png?alt=media\&token=a6b09d6d-76d1-4bd2-8f5e-2bd5d494c02e) Here's a video of a staker swapping ETH for eETH in the Liquidity Pool: {% embed url="" %} * **Stake - Staking on Ethereum (tab)** * Deposit ETH: the early version will limit staking to 32 ETH per validator. * Download StakeInfo file: this file contains the winning Node Operator's public key -- the staker will use to encrypt their generated validator key -- and the withdrawal safe address -- used for setting withdraw credentials when creating validator keys. * Download and Use Desktop Application: the staker, because with the ether.fi protocol they controls all their keys, will need to generate both withdrawal and validator keys. With our desktop application, they can do this securely and offline. * Upload StakeRequest file: the file contains the encrypted validator keys that are being securely transmitted to the node operator. Here's a video of the entire Staker flow via our Decentralized Application: {% embed url="" %} ## Node operators With ether.fi, Node Operators may participate in an **Auction** for the right to run additional validators on ethereum. This auction mechanism serves two purposes: uses market forces to differentiate between operators (performance) and compensates all stakeholders for participating in the protocol (Stakers, eETH holders, Node Operators, and the Protocol). Here's a set of videos demonstrating the Node Operator's actions in ether.fi's validator auctions: **Make a bid**: {% embed url="" %} **Cancel a bid**: {% embed url="" %} Node operators are currently **whitelisted.** To request to be added to the whitelist please email . When applying to be a node operator, ether.fi will take into consideration a set of important qualifications: * good node performance history * demonstration that validator node infrastructure is both robust and resilient * alignment with general ether.fi's goals and beliefs ## Fees --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://etherfi.gitbook.io/etherfi/~/changes/8Jd9g7SmBTNMrbOKtUZq/getting-started/decentralized-application.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.