> 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/why-aspida.md). # Why Aspida? * **Security and expertise**. The Aspida team possesses extensive domain expertise in Proof of Stake (PoS) networks and validation, with over 7 years of experience in PoS network validation. Security remains a paramount concern at Aspida, with top-tier security auditors engaged for all smart contract audits, complemented by an ongoing bounty program to further enhance security measures. * **Protocol-Own-Liquidity**. The protocol is designed to maximize capital efficiency while internalizing liquidity via protocol-own-liquidity module, to provide secondary market liquidity via different liquidity venues. * **Staking Threshold**. There is no minimum staking threshold, any amount of ETH amounts qualify for accruing staking rewards in Aspida. * **Optimized risk-adjusted yields**. Aspida seamlessly integrates with restaking protocols such as Eigenlayer to capture additional yield and continually explores further integrations to optimize risk-adjusted yields. * **Decentralization**. Adhering to Ethereum's decentralized principles, Aspida natively integrated with permissionless operator networks leveraging DVT networks, such as SSV. * **Protocol Backstop**. To mitigate slashing risks, both operators and the Aspida DAO treasury stand ready to cover any losses, providing protocol-native insurance against slashing events. * **Multichain Interoperability**. Aspida is committed to building customized cross-chain features to enable seamless cross-chain interoperability, facilitating greater flexibility and accessibility across multiple blockchain networks. --- # 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/why-aspida.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.