> For the complete documentation index, see [llms.txt](https://docs.starke.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.starke.finance/products/staking-service/overview.md).

# Overview

Staking is the process of delegating your Solana tokens to a validator, locking them into the network’s consensus mechanism in exchange for rewards. This mechanism helps secure the blockchain while allowing token holders to earn additional SOL.

At Starke Finance, staking is the foundation of our platform. We run **enterprise-grade validator operations** with a focus on performance, compliance, and resilience:

* **Certifications:** [ISO 27001 & SOC 2](https://starke.finance/trust-center)
* **Custody Integration:** Seamless support with regulated custodians for institutional staking
* **Infrastructure:** Redundant, multi-region setup with bare-metal servers to ensure maximum uptime
* **Reliability:** 99.999% availability over the last 12 months
* **Fees:** 0% validator commission. Delegators keep 100% of their staking rewards
* **Funding our vision:** By staking with Starke Validator, delegators not only earn rewards but also directly support the development of Starke Finance and its mission to bridge TradFi and DeFi.

As we expand, our staking service is evolving into a multichain focus, extending our institutional-grade reliability beyond Solana.


---

# 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.starke.finance/products/staking-service/overview.md?ask=<question>&goal=<user_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.