> 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/archive/solo-stakers/operation-solo-staker/obol-dvt-explained/receiving-your-keys.md).

# Receiving your keys

Etherfi doesn't require a Bond for operating as a Solostaker so we keep control of the validator keys and split them on our end. You receive your keyshare prepared for use in an Obol DVT cluster.

There is no DKG ceremony.

After exchanging GPG keys with Etherfi you will receive an encrypted folder with your keyshares:

<pre class="language-markup"><code class="lang-markup">├──node0
<strong>        ├──charon-enr-private-key
</strong>        ├──cluster-lock.json
        ├──deposit-data.json
        ├──validator-keys
                ├──keystore-0.json
                ├──...
</code></pre>

You just upload this folder to your node with the CDVN repo and join the cluster by running it.


---

# 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 dynamically by asking a question.

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

```
GET https://etherfi.gitbook.io/etherfi/archive/solo-stakers/operation-solo-staker/obol-dvt-explained/receiving-your-keys.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.