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

# SOL Liquid Staking Docs

## **1. Introduction**

The **Liquid Collective Stake Pool** is a Solana-based liquid staking protocol designed to maximize **staking efficiency and security**. It allows users to stake SOL while maintaining liquidity, enabling them to participate in DeFi while earning staking rewards.

This document provides a **high-level overview** for business stakeholders and a **technical deep dive** for developers.

***

## **2. Key Features**

* **Capital Efficiency & Security**: Users can stake SOL while maintaining liquidity, with an allowlist ensuring only trusted validators participate.
* **Governance & Flexibility**: Admins control staking rules, updates, and can pause operations to mitigate risks.
* **Optimized Architecture**: Built on Solana using the Anchor Framework, with a modular design separating instructions, processors, and account management.
* **Robust Smart Contracts**: Implements access control, validation layers, and pausing mechanisms to enhance security.
* **Seamless Withdrawals**: Supports both instant SOL withdrawals and unstaking options for flexibility.

***

## **3. Protocol Architecture**

The **Liquid Collective Stake Pool** consists of **multiple smart contracts and instructions** that govern staking, unstaking, and liquidity management.

### **Smart Contract Modules**

| **Module**                | **Description**                         |
| ------------------------- | --------------------------------------- |
| `deposit_sol.rs`          | Allows users to deposit SOL             |
| `deposit_stake.rs`        | Deposits an existing stake account      |
| `withdraw_sol.rs`         | Withdraws SOL directly                  |
| `withdraw_stake.rs`       | Withdraws stake from the pool           |
| `pause.rs` / `unpause.rs` | Admin-controlled pause/resume functions |
| `set_admin.rs`            | Defines the stake pool administrator    |
| `allowlist.rs`            | Manages trusted validators              |

### **Program Flow**

1. **User Deposits SOL** → Receives **liquid staking tokens** representing their share.
2. **SOL is Staked** → Pooled and delegated to validators on Solana.
3. **Rewards Accumulate** → Users earn staking rewards proportional to their pool share.

***

## **4. Security and Governance**

### **Security Features**

* **Validator Allowlist** → Ensures only pre-approved validators can receive stake.
* **Pausing Mechanism** → Admins can pause deposits/withdrawals during emergencies.
* **Access Control** → Only designated admins can modify settings.
* **Staker Allowlist** → Only allowlisted wallets can stake and redeem.

### **Audits**

Here is a [link](https://certificate.quantstamp.com/full/liquid-collective-solana/cbb18ece-3a03-4897-a040-f197fc641e4d/index.html) to the audit report.

### **Governance & Admin Controls**

* **Set by the `set_admin.rs` instruction**.
* Governance decisions include **pool updates, validator management, and security measures**.

***


---

# 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.liquidcollective.io/sol/readme.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.