# Managing a Pool

{% embed url="<https://www.youtube.com/watch?t=418s&v=dCNlTnqCm-M>" %}
Funding your pool
{% endembed %}

Once a Pool is deployed, there are no ways for a project to adjust the configuration. The core actions the Pool owner can take is to fund the Pool with more rewards, set metadata, withdraw any $GYSR spent on that Pool, and to clean up expired funding schedules.

### Funding

Funding a Pool requires a balance of the ERC-20 token the owner would like to distribute. The parameters are:

* `Amount` - how much of the reward token to be distributed
* `Period` - what duration these rewards should be released over
* `Start Date` - what date the rewards will begin to be released
* `Token` - the reward token address (only for the Waterfall)

There can be up to 16 funding schedules on a single Pool (per token). If there are 16 funding schedules, once one of them ends, it will be deleted and another schedule can be added on.

If a Pool is funded with a future start date, there will be a *"boiling period"* before rewards start distributing. During this time, users can still stake and (in the case of a Fountain) begin their vesting period or (in the case of a Geyser) get a jump start on earning a time multiplier and share seconds.

### Metadata

Pool owners can now define project metadata to be listed on their Pool's staking page. Currently the possible values include:

* `Name` - a custom name for this specific Pool
* `Website` - the URL of the project or organization behind this Pool
* `Description` - a description of the Pool and project behind it

### Withdrawing

As users spend $GYSR on a Pool, earned funds will become available for the Pool owner to withdraw. There is a “Withdraw” capability under a Pool’s management page. Confirm the transaction and all of the $GYSR in the pool will be sent to the owner.

### Cleaning

Once funding schedules have expired, the Pool owner can optionally run the "Clean" action from the management page. The clean method removes all "stale" fundings (with no remaining rewards) in order to save on storage space, reduce gas costs, and make room for more funding schedules.

###


---

# 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.gysr.io/guide/managing-a-pool.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.
