> For the complete documentation index, see [llms.txt](https://docs.kiln.fi/v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiln.fi/v1/kiln-products/dashboard/import-stakes.md). # Import stakes Import and manage external stakes, as if they were staked from the dashboard All stakes from protocols supported in the reporting section of the dashboard can be imported. You can import stakes either from the account level by clicking the "Import positions" and then "staking":

## Import stakes step-by-step Here is how to import ETH stakes from a given account, the process is similar for other protocols.

Step 1: click the "Import positions" button

Step 4: enter the wallet address from which you want to import stakes, you can also click the "By validators" button and enter a validator address or "By proxy" and enter a smart contract address used to batch deposit the funds or "By EigenPod" and enter a EigenPod address

Step 5: select the stakes you want to import from the chosen wallet and click the "Import stakes" button

--- # 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://docs.kiln.fi/v1/kiln-products/dashboard/import-stakes.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.