> For the complete documentation index, see [llms.txt](https://docs.aspidanet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aspidanet.com/aspida/risks.md).

# Risks

Liquid staking protocols in general pose several risks to ETH stakers that warrant acknowledgment.

**Smart Contract Risk**: Aspida’s smart contracts could potentially contain defects or vulnerabilities, though mitigated through regular audits and bug bounty programs.

**ETH 2.0 Technology Risk**: As Aspida builds upon Ethereum, it naturally inherits the underlying technology's risks, which may include flaws and vulnerabilities.

**Penalties and Slashing**: Node operators' validators risk penalties and slashing by the Ethereum Beacon Chain for missed attestations or satisfying slashing criteria, potentially imperiling a significant share of staked ETH over time. Aspida mitigates this through access to reputable, professional node operators, collateral requirements, and insurance coverage.

**saETH Price Fluctuations**: Secondary market saETH token prices could depeg if markets become oversupplied with saETH.


---

# 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.aspidanet.com/aspida/risks.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.