> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/staking/stake-cosmos/overview.md).

# Overview

## Introduction

The Cosmos blockchain relies on a (delegated) Proof-of-Stake protocol. Staking your Cosmos (ATOM) allows you to passively earn rewards for helping to secure the network. ATOM holders earn the staking rewards (up to 20%) generated minus the validator’s fees.

## Set up

The ability to stake Cosmos on Ledger Enterprise leverages our Vault Signer feature, which allows users to go through an external wallet to craft operations. These requests are then verified and signed by Ledger Enterprise. This model ensures that all transactions comply with the governance regulations enforced by the hardware security module (HSM). Learn more on how to set up a Cosmos staking account here.

## Start staking

To begin staking operations on Cosmos (ATOM), please contact your Technical Account Manager

{% hint style="info" %}
This feature is currently available on demand. Please contact your Technical Account Manager for more information
{% endhint %}


---

# 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://help.enterprise.ledger.com/staking/stake-cosmos/overview.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.