> For the complete documentation index, see [llms.txt](https://docs.solv.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solv.finance/staking-abstraction-layer-sal/architecture/the-ecological-view.md).
# The Ecological View
There are fundamental differences between BTC staking and Ethereum staking: since the BTC network itself lacks an official staking mechanism, the staking process relies on numerous independent staking protocols. This leads to a decentralized structure where various stages—such as LST issuance, staking transaction building and execution, and yield distribution—are carried out by different roles across different network environments. Especially, the four key roles in the BTC staking process are: LST issuers, staking protocols, staking guardians, and yield distributors.
Therefore, a unified, standardized system is essential to coordinate these roles and ensure transparency and security throughout the entire process — from the deposit of your BTC assets to the final accrual of rewards into the value of LST tokens or distribution of incentives to the users. Such coordination is crucial to protect user assets and ensure smooth yield acquisition without risks.
---
# 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://docs.solv.finance/staking-abstraction-layer-sal/architecture/the-ecological-view.md?ask=&goal=
```
`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.