Practical overview
When it fits
Use it when you want a token-launch flow that creates a Uniswap v4 pool and locks the full token supply as liquidity, and your chosen network and quote asset are supported.
Who it is for
- Creators preparing a fixed-supply ERC-20 launch on a supported network.
- Wallet-based agents seeking to use the documented token-launch flow.
Documented uses
- Deploy a fixed-supply ERC-20 and open its initial Uniswap v4 pool in one transaction.
- Choose a pool starting market capitalization and a supported quote asset.
- Set trading fees to 0%, 1% or 3%, directing fees to named beneficiaries or burning them.
Requirements & limits
The README describes the launchpad as free of platform fees and says a wallet is sufficient for the agent launch flow. A launch transaction still requires gas.
- Launches are documented for Base, Robinhood Chain and Arc; quote-asset options vary by network.
- The creator selects a 0%, 1% or 3% trading fee, with collected fees sent to named beneficiaries or burned.
- The project describes the locked liquidity position as having no owner, pause, upgrade path or transfer function.
- The repository is public and MIT-licensed, with Foundry contracts and a Next.js, React, wagmi and viem web app.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Prepare the Openlaunch app environment
Install the app dependencies and create a local environment file for RPC and contract configuration.
Before you start
- A checkout of the Openlaunch repository.
- Node.js/npm available to run the documented npm command.
Steps
Change to the
appdirectory.Run the command below.
npm installCopy
.env.exampleto.env.local.Configure RPCs and factory/locker values in
.env.local.
Expected outcome
The app dependencies are installed and `.env.local` is prepared for RPC and contract configuration.
Guide limitations
- The README does not provide the required environment variable names or values.
- This covers setup only; it does not document starting or deploying the app.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- Twigpine/openlaunch · Official homepage title · retained in its source language

