# OVERVIEW

Welcome to the comprehensive documentation for the Ignition Stake Pool program — a FOGO blockchain program for creating and managing pools of staked tokens.

{% hint style="info" %}
Program ID: `SP1s4uFeTAX9jsXXmwyDs1gxYYf7cdDZ8qHUHVxE1yr`
{% endhint %}

## Overview

The Ignition Stake Pool program allows users to pool their stake accounts and receive liquid tokens in return, enabling better capital efficiency and democratizing access to staking rewards on FOGO.

## Key Features

* Liquid Staking: Convert staked tokens into transferable pool tokens
* Validator Management: Efficient management of large validator sets using optimized data structures
* Fee Protection: Built-in safeguards against malicious fee increases
* Multi-Client Support: Rust CLI, TypeScript SDK, and Python bindings
* Transient Operations: Secure handling of deposits and withdrawals through temporary accounts

## Key Concepts

### Stake Pool Mechanics

* Pool Tokens: Liquid representation of staked tokens with proportional rewards
* Validator Lists: Efficiently managed using big\_vec data structure for large validator sets
* Reserve Account: Maintains liquidity for immediate withdrawals
* Transient Accounts: Temporary accounts for secure deposit/withdrawal operations

### Security Features

* Fee Protection: Maximum 3/2 ratio increase per epoch prevents malicious fee changes
* Minimum Stakes: 1,000,000 lamports minimum active stake per validator
* Batch Limits: Maximum 4 validators per update instruction to respect compute limits
* PDA Security: All authority accounts use program-derived addresses

## External Resources

* FOGO Documentation: <https://docs.fogo.io/>


---

# Agent Instructions: 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:

```
GET https://docs.ignitionfi.xyz/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.