FIP-95: Tribe Turbo Launch Group

Motivation Tribe Turbo needs time for testing and improvement, which we will achieve using a guarded launch. OlympusDAO as well as Balancer have agreed to participate in this guarded launch with gOHM and BAL respectively. Both partner communities have signaled support for utilizing Turbo, and if approved, will participate in the guarded launch, which will allow Tribe DAO to learn and adapt the product and process as necessary.

Specification Whitelist gOHM, BAL, and xTRIBE for Tribe Turbo. Start the Tribe Turbo Guarded Launch, with gOHM, BAL, and xTRIBE. Set the following Turbo whitelist criteria, which is to be enforced by Optimistic Approval. Optimistic Approval will also be responsible for onboarding new DAOs to Turbo.

Tribe Turbo Whitelist Criteria: Overall Project/Market Conditions Token must be listed and have a live USD price feed with Chainlink (Oracle)

Legitimacy of the project/protocol

Supply cap * 2 for the token is less than the average daily volume of 30d.

Average daily on-chain liquidity over 30 days > $10,000,000

Volatility - daily 30 days price variance over the last 60 days < 8%

Token Security Token contract must be verified on Etherscan.

Token contract has received an audit from a known security auditor

The project should have a publicly visible test environment

Administrative privileges over the protocol should not be owned by an EOA, any multisig must have known members.

If token supply is not fixed, conditions under which supply can increase needs to be made aware of and low risk

No restrictions on transferring or trading such as holding the tokens for a number of blocks before you can transfer them, fees/taxes on transfers etc

Token transfers shouldn’t be pausable or subject to a whitelist

Token ownership should be widely distributed with no address (whale) owning