LP24 Protocol Documentation
Complete developer reference for integrating with the LP24 bonding-curve protocol. Deploy tokens, trade on bonding curves, and interact with graduated DEX pools — all permissionlessly, directly from smart contracts.
There is no official trading frontend. Every function documented here is called directly on-chain, and this documentation is the integration path — not a supplement to a web app. The contracts have no owner, no admin key, and no upgrade mechanism.
The per-chain sites at <chain>.lp24.tech are read-only token explorers and charts. They serve an indexed database fed by the event stream, with no wallet connection and no way to transact. Nothing in the protocol depends on them being online.
Trust attaches at exactly one surface: launch-time state — the constructor arguments, the patched constants, and the seed liquidity. Everything after deployment is verifiable on-chain.
What is LP24?
LP24 is a permissionless token launch protocol deployed across 5 chains. It combines a bonding curve for initial price discovery with automatic graduation into permanent, protocol-owned DEX liquidity. The entire lifecycle — from token creation to fully-traded pair — happens without any manual intervention.
All contracts are written in Vyper 0.4.3. Every chain runs the same economic design; only the DEX integration layer differs.
| Chain | Native | DEX venue | Pool structure |
|---|---|---|---|
| Base | ETH | Uniswap V4 | Dual — primary + secondary |
| BSC | BNB | PancakeSwap Infinity | Dual — primary + secondary |
| Polygon | POL | Uniswap V4 | Dual — primary + secondary |
| Robinhood | ETH | Uniswap V4 | Dual — primary + secondary |
| Gnosis | xDAI | Uniswap V3 | Single pool |
Protocol at a Glance
Factory.deploy_pair() with a name, symbol, mined vanity salt, and packed socials. Pays the deployment fee. Creates a minimal-proxy token and bonding curve in one transaction and registers the token under your address.Code Examples
Every guide shows the same operation in two languages; the tabs on each block switch between them, and your choice is remembered across pages.
| Language | Library | Notes |
|---|---|---|
| JavaScript | ethers v6 | Runs in Node and the browser unchanged. If you use viem, the contract calls map across directly — only the provider and signer setup differ. |
| Python | web3.py v7 or v8 | Examples stick to the core contract API, which has been stable since v6, and sign transactions explicitly rather than using signing middleware. |
ethers accepts human-readable ABI fragments, so its examples declare the few functions they need inline. web3.py requires a JSON ABI, so the Python examples load one from the compiler output. That is the only structural difference between the two sets — everything else is a direct translation.