Docs · Oceanpoint pools

Detailed functionalities

CP initial deposit

The initial deposit by a Certified Partner (CP) is collateral that secures the marketplace team's commitment and performance. This deposit:

  • Acts as a guarantee against underperformance, protecting community members.
  • Must be between 500 and 99,000 sBST, so that CPs have a stake in the success of their marketplace.
  • Counts toward the pool's 100,000 sBST target; community members pledge the rest.
  • Is made together with the choice of the pool's lock period, between 90 and 365 days.

Campaign configuration

Only Blocksquare can configure a marketplace pool campaign: its start date, its length (between 5 and 30 days) and the initial maximum pledge per wallet. This control ensures:

  • Compliance with KYB and collaboration agreements, so that only verified and committed partners can open marketplace pools.
  • The community can support new operators through informed decisions.

Maximum pledge

During a campaign, each wallet can pledge only up to a maximum amount of sBST. This maximum starts at the initial limit, rises in a straight line each day, and is lifted completely once the campaign is halfway through. This mechanism encourages wider participation by:

  • Letting smaller holders take part early in the campaign, spreading pool ownership more widely.
  • Gradually allowing larger pledges, so pools can still be filled while access stays fair.

For example, take a 30-day campaign where the CP has deposited 10,000 sBST, leaving 90,000 sBST to be pledged, with an initial maximum pledge of 9,000 sBST. The limit grows by 5,400 sBST each day, so by day 15 you could pledge up to 90,000 sBST.

This design encourages early participation while gradually allowing larger contributions, keeping community participation broad and fair.

Post-campaign deposits

Community pledges are accepted only during the campaign. After the campaign ends, the CP has a short window to top up the pool, provided at least one community member pledged during the campaign. Once a pool has reached 100,000 sBST, further deposits are possible up to that cap, for example to replace sBST that others have withdrawn.

Withdrawal conditions

Withdrawal conditions balance the CP's ability to reclaim its collateral with the protection of pool participants:

  • Failed campaigns: if the pool does not reach 100,000 sBST, both community members and the CP can withdraw their sBST shortly after the campaign ends.
  • Community withdrawals: when the pool reaches 100,000 sBST, community pledges are locked for the pool's lock period. After that, community members can withdraw their sBST together with their rewards.
  • CP withdrawals: the CP's collateral is locked for twice the community lock period, starting when the pool reaches 100,000 sBST. After that, the CP can withdraw only once the governance multisig releases the collateral.

Collateral liquidation

When launching a marketplace pool, Certified Partners define a set of KPIs they intend to achieve. These KPIs can be anything from registered users and assets under tokenization to completed offerings, secondary-market properties or revenues distributed. To ensure commitment, the CP deposits at least 500 sBST as collateral when activating the pool. At the end of the CP lock period, the CP's results are checked against the KPIs set at the start.

The pool's owner, the governance multisig (see Governance board), then decides on the collateral. It can:

  • Release the collateral so the CP can withdraw it.
  • Extend the CP's lock period.
  • Liquidate the collateral, which transfers the CP's sBST out of the pool to the multisig.

Pools reward distribution

BST rewards are added only to pools that have reached 100,000 sBST. Within a pool, rewards are shared among community members in proportion to their pledged sBST; the CP's collateral does not earn marketplace-pool rewards. How much each pool receives is set through governance and changes over time; see /stats for current yields.

Non-Transferability of Staked Tokens

The pool tracks each pledge with a staked-sBST token that cannot be transferred. This is critical for:

  • Keeping reward calculations and distributions accurate and preventing manipulation.
  • Keeping the staking process intact and reinforcing participants' commitment to the marketplace pools they chose.