> For the complete documentation index, see [llms.txt](https://sdk.chorus.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk.chorus.one/our-products/chorus-one-ethereum-native-staking.md).

# Chorus One Ethereum Native Staking

Ethereum Proof-of-Stake processing of consensus and building a blockchain is enabled by validators who secure the network by proposing new blocks containing user transactions and attesting to blocks of other validators. For this work, validators are rewarded with ETH.

To create a validator, one needs to call deposit contract with transfer of a minimum amount of 32 ETH, bundling the transfer with a deposit dataset that includes the following:

* The validator's public key
* Withdrawal credentials
* The amount of ETH being deposited
* Network detail where validator will be running (Mainnet, Gnosis, etc)
* A signature proving ownership of the validator's private key

Chorus One Native Staking API for Ethereum provides functionality to generate this data on-demand. The Ethereum client instances corresponding to validators created with this API will be running in Chorus One infrastructure.

To start using API, read our [Integration Guide](/our-products/chorus-one-ethereum-native-staking/api-integration-guide.md) or jump straight to [API docs](https://native-staking.chorus.one/docs)


---

# 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://sdk.chorus.one/our-products/chorus-one-ethereum-native-staking.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.