> 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/introduction/ethereum-and-pos-problem.md).

# Ethereum and PoS Problem

Back on Dec 1, 2020, Ethereum tested the proof of stake (PoS) approach on its Beacon Chain. Through this approach, users could become validators by staking 32 ETH. Their ETH tokens, however, were subject to a locking period. This meant that the staked assets would be illiquid for a while.

The possibility of all these began enticing new staking users. But there was a serious problem. Not every investor had 32 ETH to spare for staking. And because staking was a viable option for earning passive income, users tried to find alternative ways to stake ETH without jeopardizing liquidity.


---

# 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/introduction/ethereum-and-pos-problem.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.