Blast Points for Thruster LP Integrations

We are distributing Blast Points to eligible USDB, WETH, and BLAST TVL in Thruster (e.g. ETH/USDB, X/ETH, etc.) on a regular cadence. Whichever address holds the LP token (either CFMM ERC-20 or CLMM NFT) will be eligible for Blast Points.

However, based on how Blast’s point system works, it should not be allocated to a contract address that does not support the Blast Points API as those Points then become unclaimable or transferable, which we or Blast cannot do anything about.

Rules

For us to reallocate Blast Points to your address properly for holding or having seeded / having control of the liquidity via a proxy, you need to be following these rules:

  • If the owner of the LP is an EOA, then Blast Points will be streamed directly to the address.

  • If the owner of the LP is a contract, then:

    1. If the contract is a pass-through contract where the LP is only able to deposited and withdrawn by the same address, the team must notify the Thruster team so that the contract will bypass it and distribute directly to the end user.

    2. If the contract is not a pass-through contract, the contract must be configured to receive Blast Points otherwise these points will be lost.

      1. It is required that contracts that are not a pass-through only manage liquidity positions for a single pool.

      2. If the contract manages LP positions across multiple pools, the owner of the contract is responsible for dividing the points between the pools. Thruster will not send a breakdown by pool for the Blast Points sent.

    3. By default, Blast Points will be sent to the address that is the owner of the LP. If the LP is burned and the owner is the zero or dead address, Blast Points will not be disbursed.

  • You are the pool creator or an individual LP with control of over 50% of the total LP value, that happens to be holding LP tokens via a contract (multisig, intermediary locker contract, etc.) or burned the LP tokens for a non-malicious reason (safety or LP integrations primarily)

    • If you don’t fill these requirements, you are a integrator of Thruster LPs (automated range provider, LP as collateral in a lending market, etc.) with over $500,000 in each pool you request reassignment for

  • Your LP position or pool on Thruster has had over $200,000 in ETH or USDB total liquidity for over 24 hours of time at one point, and still has over $100,000 in liquidity at the time of the reassignment request

  • You can reasonably verify that you are officially connected with the LP (either own/control, or are on the team of the team that controls the LP). Actions (one or many or all) that prove reliable verification include:

    • Send Twitter DM or like specific tweet from official project Twitter

    • Send specified message to specified address on chain from deployer or LP holder

    • Undergo specific on-chain actions that only the deployer or LP could complete

  • You are a legitimate LP (not a scam / fake token LP, or an LP putting liquidity purposefully out of range to farm full rewards without risk)

Logistics

There is some logistical complexity here as we want to make sure this is done correctly as point reassignment is irreversible. A few things related to this:

  • Once we transfer the points, we cannot take them back. So make sure that your contract is properly configured to accept and redistribute points if you provide an intermediary contract, not an EOA

  • In all scenarios: once we reassign Blast Points, we are not responsible for how those Points are used by the end protocol, but will bring up issues if usage seems explicitly malicious. This also means that we cannot pass arbitrary points reassignment to our API, if there is a contract in between — that must be handled by the team that interfaces with the liquidity in their contracts.

How to Get in Contact

Assuming your pool fits this requirement, please get in touch through the proper channels.

Our Twitter or our Discord partner channel works best in this scenario.

Last updated