By default, Maestro Pools only accept compatible iNFTs, i.e., staking positions from a wrapped LP.

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


The most straightforward and obvious requirement is that only staked positions with at least the required amount can be deposited into the Maestro Pool.

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


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


Protocols can also set up a whitelist, to only authorize some addresses to interact with their Maestro Pools.

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

Custom requirement contract

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

In this case, any project will have the possibility to plug in its own custom requirement contract to a Maestro pool.

Last updated