> For the complete documentation index, see [llms.txt](https://docs.bedrock.technology/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bedrock.technology/security/battle-tested-protocol.md). # Battle Tested Protocol Bedrock, a battle-tested system, established atop various smart contracts and operational for over a year, denotes a resilient and proven platform in the liquid staking space. This signifies that the system has withstood the challenges of time, demonstrating stability, security, and reliability in its execution. The extended period of operation, with more than 10k ETH staked and unstaking smoothly, surpassing one year, serves as a testament to the durability of the system. It implies that the smart contracts governing the platform have successfully processed transactions, executed functionalities, and maintained their integrity over an extended timeframe. Such a system likely boasts a track record of handling diverse scenarios, including market fluctuations, high transaction volumes, and potential security threats. The fact that it has been operational for an extended duration suggests that it has adapted to evolving conditions, addressed vulnerabilities, and garnered user trust. Furthermore, please find Bedrock on Ethereum Foundation official website - [pooled staking](https://ethereum.org/staking/pools) --- # 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.bedrock.technology/security/battle-tested-protocol.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.