> For the complete documentation index, see [llms.txt](https://docs.oceanpoint.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oceanpoint.fi/oceanpoint-pools/about-pool-mechanics/asset-pools/asset-pool-community.md).

# Asset pool - Community

This feature is LIVE since v0.4

{% hint style="info" %}
**Current reward schedule**

125,000 BST / month \* Pool sBSPT supply
{% endhint %}

The fourth product introduces a new incentive mechanism for the web3 community to buy tokenized real estate properties and earn crypto through staking.

Staking your BSPT is not mandatory to earn revenues, however, staking enables users to redirect regular rental revenues paid out in DAI stablecoin towards the DAO's treasury and in return receive a compensation in BST.

{% hint style="success" %}

#### Do you want to own real estate?

To be able to purchase BSPT tokens of various properties, please visit [marketplace.oceanpoint.fi](https://marketplace.oceanpoint.fi)
{% endhint %}

{% hint style="info" %}
The more real estate tokens one stakes, the larger the share in the Community asset pool, the larger the amount of BST one might earn from the rewards treasury. Note that both the property's valuation as well as projected APY will influence a user's stake size.  
{% endhint %}

{% hint style="warning" %}
By staking BSPT, the community member commits to a 1 months lock-up period through which tokens and earned rewards can't be withdrawn.

*No vesting on earned rewards is applied after withdrawal.*
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.oceanpoint.fi/oceanpoint-pools/about-pool-mechanics/asset-pools/asset-pool-community.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.