Start with the model
Programmable launches fixed-supply ERC-20 tokens into Uniswap v4 pools on Ethereum. The selected model fixes the pool structure, fee path, reward rules and available controls before the wallet submits the launch.
Classic and Stock-Paired are available for public launches on Ethereum Mainnet.
From setup to a confirmed transaction
- Choose a modelCheck its release status, fee path and model-specific risks.
- Set the token and launch termsAdd the name, ticker, image, description, project links and the settings available for that model.
- Review the prepared transactionProgrammable checks the configured release and validates the prepared call before opening the wallet.
- Confirm in the walletThe connected wallet submits the transaction and pays Ethereum gas. A confirmed receipt becomes the launch record.
The launch wallet pays network gas and the Initial Buy required by the selected model.
The recorded pool is the source of truth
Explore and token pages read the pool recorded by the verified launch event. Market cap is an estimate based on confirmed pool price and fixed token supply. It is not a promise that the full supply can be sold at that price.
Rewards follow the launch terms
Classic rewards accrue in ETH. A launch can assign them to the launch wallet, another wallet or a recorded split of up to five wallets. Each current payout wallet claims only its own allocation and can move future rewards for that allocation to a new address.
Moving an allocation to a new payout address does not change its percentage. The disclosed CTO authority can replace future recipients and split percentages after checkpointing rewards already accrued under the current configuration.
Stock-Paired rewards accrue in its selected quote token. Profile shows the claims available to the connected wallet.
A claim pays only the caller's recorded entitlement. It cannot alter fee rates, reward percentages or liquidity custody.
Ethereum Mainnet
Public launches use Ethereum Mainnet and the official Uniswap v4 PoolManager, PositionManager, StateView, Quoter and Universal Router deployments. The wallet must be connected to Ethereum before it can submit a launch or trade.
Active Classic deployment
These are the primary contracts behind the public Classic launcher. The release manifest records the complete deployment, runtime hashes and lifecycle evidence.
| Contract | Address | Purpose |
|---|---|---|
| Classic launcher | 0xC3bd04aAc2fb2ba58efD7Eb673E544E0B80De770 | Creates the token, pool and launch records. |
| Classic fee hook | 0x35Fe236EA82F7cF525c9719d7df8F49F94D720CC | Applies the immutable buy and sell fee settings. |
| Reward vault factory | 0xF28967f9DFaC3Ca21384b59D6D75C8106b3eab2a | Creates the reward vault for each Classic pool. |
| Position recipient factory | 0x291a9ff1059d225d02B1659430804486404dB507 | Permanently holds the launch position. |
Project details are public
Token metadata can include a description, image, website, X link and Telegram link. Programmable uses those values on Explore and token pages. External terminals control their own indexing, moderation and refresh timing, so display there is not guaranteed.
Source and deployment must match
A model reaches the public launcher only when its deployment record, runtime code and required lifecycle evidence match the application release. Local tests and design documents do not make a model live.
What Programmable cannot guarantee
- A transaction can fail, be irreversible or cost more when network conditions change.
- Fixed supply and locked launch liquidity do not guarantee demand, price stability or deep liquidity.
- Tokens can be volatile, illiquid or lose all value.
- Third-party wallets, scanners and trading terminals make their own routing and display decisions.
- Source verification and lifecycle tests are not an independent audit or a guarantee that no vulnerability exists.