# Permissionless Configurable Staking Pools

We learned how The Staking Library provides a firm foundation for Staking operations, and allows anyone to have a Staking Derivative:

{% content-ref url="/pages/wjuUXSbPQC2Vbhf8CSqv" %}
[The Staking Library](/the-staking-library.md)
{% endcontent-ref %}

Then, we learned how the Operator Marketplace makes staking operations much easier, and increases the user experience for both Pool Owners and Node Operators:

{% content-ref url="/pages/8al101kYMumrrAiepfDu" %}
[Operator Marketplace](/operator-marketplace.md)
{% endcontent-ref %}

Now, lets take a look at the Staking pools, and the superpowers of their Modular Architecture.

## One Transaction To Rule Them All!

During the same transaction for creation of a staking pool, the following functionalities can be configured:

### Private Pools - optional

* If a pool is Public, everyone can use it. 
* Private pools are only available to their owners and other whitelisted addresses.
* Pool owners can make pools public or private as they wish.
* Any contract with a `isWhitelisted()` function can be used by the Private Pools.

{% content-ref url="/pages/ee1qPNg9mYqC5t04mRUo" %}
[Private Pools and Whitelisting](/ethereum-guides/staking-pool-handbook/private-pools-and-whitelisting.md)
{% endcontent-ref %}

### Interfaces - optional

* **If you don't need an ERC20 for example, a pool can operate without an interface.**
* While gETH allows multiple interfaces, Portal only allows 1 interface per derivative for security reasons.
* Interfaces should be created on the initiation process. Currently, an interface **can** not be added after the pool initiation for security reasons.
* New interfaces require the approval of the Senate.
* Any interface can be chosen from the list below:

{% content-ref url="/pages/NMzvFXpWn6oyM78TmdkQ" %}
[Current Interfaces](/key-concepts/permissionless-configurable-staking-pools/current-interfaces.md)
{% endcontent-ref %}

### Maintainers - optional

* **If you don't have a very active pool, you can choose your operators without a maintainer.**
* Pool tasks such as management of the Operators can be automated through maintainers.
* Adding a maintainer is not a security risk, any contract or address can be chosen as a maintainer. However, it is always best to DYOR.
* Maintainers can not steal Pool fees or Pool funds.

{% content-ref url="/pages/pr7YAwNKRplvqovwxwxF" %}
[Maintainers](/key-concepts/permissionless-configurable-staking-pools/maintainers.md)
{% endcontent-ref %}

### Bound Liquidity Pools - optional

* **If you don't need liquidity, your pool doesn't need a bound liquidity pool.**
* **You can always change your mind later.**

{% content-ref url="/pages/D6utzcdejMctLxSHh3Qr" %}
[Bound Liquidity Pools](/key-concepts/bound-liquidity-pools.md)
{% endcontent-ref %}


---

# 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.geode.fi/key-concepts/permissionless-configurable-staking-pools.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.