Honey Combs (Pools)

Honey Combs show the power of Hiveswap’s staked positions.

They are fixed-duration pools made to receive staked positions (spNFTs) from users, hence offering them a new layer of yield rewards in addition to what those positions are already generating.

This is a direct and permissionless way for protocols to incentivize.

There will be two different kinds of Honey Combs

• Official Honey Combs: created by the Hiveswap team, or verified partners

• Community Honey Combs: openly deployed by anyone

Staking:

Honey Combs are made to only receive staked positions (spNFTs) as deposits.

Every Honey Comb will have the following settings:

• A specific wrapped LP (or single asset). Only positions made from this deployer-defined asset can be deposited into the pool

• A reward token (additional rewards can be added any time)

• A deposit start time before which no one can stake

• A rewards' distribution phase duration (start and end times)

• An optional harvest start time before which no one can collect their earned rewards yet

Multi-Staking:

Every user can deposit as much of their spNFTs as they wish to. The reward calculations are made based on the sum of all the user's current deposits.

It's possible to add new positions anytime, as well as to withdraw staked positions completely or a desired percentage.

Interact with staked positions:

If some of the interactions are logically unavailable when staked, users can still add more to their position and harvest their xHIVE and HIVE rewards for all of their staked spNFTs into a Honey Comb.

Requirements:

By default, Honey Combs only accept compatible spNFTs, (staking positions from a wrapped LP.)

On top of that, protocols deploying a Honey Comb can optionally set their own requirements to accurately target specific positions or staking users' profiles.

Amount:

The most straightforward and obvious requirement, only staked positions with at least the required amount can be deposited into the Honey Comb.

The unit taken into account for the amount will be one of the position's LP.

Locks:

It's also possible to require specific lock settings on staked positions to validate its deposit:

• A duration: the staked position should have a total lock duration of at least x days

• An end time: the staked position should be locked until at least xx/xx/xxxx

Whitelist

Protocols can setup a whitelist, to only authorize some addresses to interact with their Honey Comb.

The uses of this mechanism are numerous: examples include, reward their most loyal users, the winners of a competition, distribute a targeted compensation, replace an airdrop and more.

Custom requirement contract:

There are also situations where some protocols will need to have very specific requirements that aren't available in the native Honey Comb contracts.

In this case, any project will have the possibility to plug in their own custom requirement contract to aHoney Comb.