superFLOW
A CLI tool for one-click deployment of tokens and liquidity pools across multiple chains
superFLOW
Created At
Winner of
Blockscout - Blockscout Explorer Big Pool Prize
Prize Pool
Celo - Best Open-Source Tool Built on Celo L2 1st place
Hyperlane - Best Hyperlane Automation
Project Description
superFLOW is built to solve and ease out the process of Token Generation events and later bridging and deploying liquidity pools of those tokens across multiple chains.
Usually a normal process for TGE and Post TGE looks something like this:
- Deploying ERC20 on one chain, for most projects, its Ethereum Mainnet for security and trust. 2. Bridge tokens to multiple chains of interest, for example, Arbitrum, Base, Celo, Unichain, etc., or whichever chain they want their token to be present in the LP pool of that chain, Uniswap on Arbitrum or Aerdrome on Base. 3. Actually creating a liquidity pool of the bridged token and the respective destination chains and providing liquidity in that pool.
superFLOW is built to automate the above-mentioned disjoint and time-consuming steps with one click.
With superFLOW, you provide the necessary information, like the origin chain, total supply, and other metadata of the token, which all chains they want to bridge their tokens to, and how much of the total supply they want to bridge and put in the LP pool for that chain. With all this info collected beforehand, Superflow will do all the actions mentioned above for you, and you'll have the deployment result, like the LP Pool address of each destination chain, etc., as the end result. All of the steps from token generation to bridging to creating an LP pair and providing liquidity abstracted for you under the hood. That's superFLOW!
How it's Made
Superflow is a containerised cli solution that automates all the logic for you. The end result is a docker image that you run by executing a single docker command. Under the hood the different individual steps are automated with JS and Go scripts.
- Token generation happen through a JS script.
- Bridging the token after creation is done using hyperlane warp routes. We generate warp routes for the newly deployed token connecting the parent and destination chains of interests. Bridging of token is handled via hyperlane cli. The whole logic of working with the cli is abstracted with go scripts and shipped in the container image.
- Finally the deployment of the LPs happen via JS scripts again and this step is also part of the docker image and shipped in it.
