If you operate an external protocol, there are a number of benefits that can come from integrating with Flaunch.
Create your own launchpad that gives you full control of the business model
Integrate your protocol's functionality into Flaunch's whitelisted treasury actions to build TVL
Build popular money games with the tokenized revenue streams and profit
Builders can take up to 100% of all fees generated, and the remaining will go to your token creator and .
The Flaunch protocol is built in a way that directly rewards the token creator though, which won't benefit an external protocol. To alleviate this, we can use an escrow contract that will capture fees as a middleware and give more granular control over fee distribution in any way wanted.
To achieve this, we created the RevenueManager implementation contract that is simple to integrate. Before making your call to flaunch a token you will first need to deploy an implementation of the Treasury Manager and then initialize the RevenueManager like below.
Initialization
/**
* Parameters passed during manager initialization.
*
* @member protocolRecipient The recipient of protocol fees
* @member protocolFee The fee that the external protocol will take (2dp)
*/
struct InitializeParams {
address payable protocolRecipient;
uint protocolFee;
}
Deposit
No additional data required
Public Calls
balances(address _recipient) returns (uint)
Allows the caller to check the balance of their position. This will check all of the creator's tokens, and if the protocol fee recipient calls this then it will also show the amount available for them to claim.
claim() returns (uint)
Allows a caller to make a claim against their whole balance, without any additional {FlaunchToken} logic being passed in the parameters.
The total amount of ETH that has been claimed for a specific token
Protected Calls
Only the owner of the manager can make these calls
Allows a protocol owner to make a claim, without any additional {FlaunchToken} logic being passed in the parameters. This returns the amount of ETH claimed during the call.
Allows the end-owner creator of the ERC721 to be updated by the intermediary platform. This will change the recipient of fees that are earned from the token externally and can be used for external validation of permissioned calls.
Allows the protocol recipient to be updated. This can allow a zero value that will bypass the protocol recipient taking a protocol fee during the claim.
Transfers ownership of the contract to a new account (newOwner).
Who is using the RevenueManager?
We are currently working with a small number of launchpads to implement our RevenueManager. When they are released as public code repositories, we will share and document the implementations. Check back soon!
