---
title: "Liquidity bootstrapping pools (LBPs)"
url: "https://caper.network/wiki/economics/liquidity-bootstrapping-pools"
updated: 2026-09-09
license: CC-BY-4.0
license_url: "https://creativecommons.org/licenses/by/4.0/"
---

# Liquidity bootstrapping pools (LBPs)

|  |  |
| --- | --- |
| **Type** | Fair-launch price-discovery mechanism (dynamic-weight AMM pool) |
| **Introduced by** | Balancer (2020) |
| **Popularized by** | Copper Launch, rebranded [Fjord Foundry](https://www.fjordfoundry.com/) (2022); Fjord now runs its own sale platform |
| **Core mechanism** | Pool weights shift linearly over time, applying controlled downward price pressure — a continuous Dutch-auction-style discovery |
| **Reference implementation** | Balancer v2 LBP factory, **disabled on-chain 11 May 2026**; Balancer v3 `LBPoolFactory` (v4, May 2026) is the successor |
| **Pools created, v3 factories** | 37 created / 22 non-mock / 10 ever funded, across Ethereum mainnet, Base and Arbitrum since March 2025 (read 19 Aug, re-read 9 Sep 2026) |
| **Primary use** | Permissionless token distribution and fair launch with little starting capital |
| **Related** | [Bonding curve](/wiki/markets/bonding-curve) · [Curation markets](/wiki/economics/curation-markets) · [DAO tokenomics](/wiki/dao-governance/concepts/treasury/dao-tokenomics) |

A **liquidity bootstrapping pool** (LBP) is a token-sale mechanism, first built on [Balancer](https://docs.balancer.fi/concepts/explore-available-balancer-pools/liquidity-bootstrapping-pool/liquidity-bootstrapping-pool.html), that lets a project distribute a brand-new token and discover its price fairly while committing very little starting capital. Unlike a fixed-price sale — where whales and bots race to buy the entire allocation at launch — an LBP starts the token priced high and lets that price drift _down_ over the sale unless buyers step in, so participants who wait are rewarded and no single actor can corner the supply cheaply. Because it produces an open, permissionless primary market rather than a negotiated round, it sits alongside [bonding curves](/wiki/markets/bonding-curve) and [curation markets](/wiki/economics/curation-markets) in the family of [on-chain capital-formation](/wiki/economics/capital-markets) mechanisms that DAOs use to launch a governance token.

## How an LBP works

An LBP is a variant of a Balancer [weighted pool](https://docs.balancer.fi/concepts/explore-available-balancer-pools/weighted-pool/weighted-pool.html) holding two assets: the **project token** being sold and a **reserve asset** (typically a stablecoin or ETH). What makes it special is that the pool owner sets a _weight schedule_: per the [Balancer documentation](https://docs.balancer.fi/concepts/explore-available-balancer-pools/liquidity-bootstrapping-pool/liquidity-bootstrapping-pool.html), the owner specifies "the starting and ending weights for both tokens" and "these weights change linearly over time." A typical sale starts around 90/10 (project token / reserve) and ends near 20/80.

Because a weighted-pool's spot price is a function of the balances _and_ the weights, steadily lowering the project token's weight creates what Balancer calls "controlled downward price pressure." If nobody buys, the price keeps falling; if demand appears, buys push it back up. The net effect is a "continuous Dutch-auction-style mechanism" that stretches price discovery across hours or days instead of resolving it in a single opening block.

## Why the design resists whales and bots

Fixed-price and first-come sales reward whoever transacts first with the most gas — the classic gas-war and sniping dynamic. An LBP inverts that incentive. Since the schedule pushes price down over time, [buying early is buying at the top](https://medium.com/balancer-protocol/distribute-your-erc20-token-with-liquidity-bootstrapping-pools-b84159464c32): a bot that sweeps the pool at launch simply overpays and then watches the weight schedule mark its position down. Rational buyers instead wait for a price they consider fair, which spreads the distribution across many participants and dampens the launch-day volatility that plagues fixed-price listings. The mechanism does not _prevent_ large buys, but it makes buying everything at once economically self-defeating.

## Configuration and owner controls

The pool owner holds significant, and asymmetric, power over an LBP. Per Balancer's [specification](https://docs.balancer.fi/concepts/explore-available-balancer-pools/liquidity-bootstrapping-pool/liquidity-bootstrapping-pool.html), the owner is "the only address that can add liquidity to the pool, which must be done prior to the start of the sale," and "the proceeds can only be removed after the end time." The owner configures the start and end times, the weight schedule, and swap fees, and can pause swaps outright. A dedicated `blockProjectTokenSwapsIn` setting can prevent the project token from being sold _into_ the pool during the launch, blocking a common manipulation. This concentration of control is the mechanism's central trust assumption: buyers must trust that the owner will not pause the sale, alter the schedule, or pull reserves adversarially.

## LBPs in practice

LBPs moved from a Balancer primitive to a mainstream launch tool largely through **Copper Launch**, a front-end that made configuring one a point-and-click exercise. Copper [rebranded to Fjord Foundry](https://tokeninsight.com/en/news/copper-rebrands-to-fjord-foundry-launches-nft-lbp-product-fjord-drops) in 2022 and later signed an [exclusive LBP partnership with Balancer](https://forum.balancer.fi/t/bip-98-fjord-formerly-copper-and-balancer-exclusive-partnership/3884) (BIP-98), extending the format to NFTs. That arrangement is history rather than description: Fjord now runs its own platform and token, and the Balancer factory underneath it has been switched off (see below). Projects including GuildFi, Merit Circle, and Avocado DAO have distributed tokens this way, and Balancer has facilitated [nine-figure LBP raises](https://medium.com/balancer-protocol/balancer-facilitates-record-high-liquidity-bootstrapping-pool-for-hydradx-f08b6b0a3aee) such as HydraDX. For a DAO, an LBP is often the moment a governance token first reaches a broad holder base — the event that turns a core team's project into a token-holder community.

## Where the mechanism actually runs, read on-chain (19 August, re-read 9 September 2026)

Everything above is sourced from Balancer's v2 documentation, and that stack is no longer the one a project would reach for. Both v2 LBP deployments now sit under [`v2/deprecated/` in Balancer's own deployment registry](https://github.com/balancer/balancer-deployments/tree/master/v2/deprecated/20211202-no-protocol-fee-lbp), and the factory Copper and Fjord actually built on – `NoProtocolFeeLiquidityBootstrappingPoolFactory` – has had its on-chain kill switch pulled. `isDisabled()` returns true on Ethereum mainnet, Base and Arbitrum alike. On mainnet the `FactoryDisabled` event fires in block 25,070,461 at 2026-05-11T07:46:35Z, inside a Safe [`execTransaction`](https://eth.blockscout.com/tx/0x5f5918cf5aa81417e5d1810c15d502aa610a66594083cf81c9a9061be400be9e). The [factory is still there and still readable](https://eth.blockscout.com/address/0x0F3e0c4218b7b0108a3643cFe9D3ec0d4F57c54e); it just cannot mint another pool.

The successor is Balancer v3's `LBPoolFactory`, now in its fourth generation ([`20260501-v3-liquidity-bootstrapping-pool-v4`](https://github.com/balancer/balancer-deployments/tree/master/v3/tasks/20260501-v3-liquidity-bootstrapping-pool-v4)), sitting beside a [`FixedPriceLBPoolFactory`](https://github.com/balancer/balancer-deployments/tree/master/v3/tasks/20251205-v3-fixed-price-lbp) shipped in December 2025 – a sale format that keeps the LBP plumbing and removes the falling price the mechanism is named after.

How much either has been used is a single call. `getPoolCount()` on every v3 LBP factory ever deployed to those three chains, returned 36 pools between them on 19 August 2026, and 37 when the same call was re-run on 9 September. Each deployment creates one `MockLBPool` or `MockFixedPriceLBPool` for its own verification, and the registry names those addresses, so they can be subtracted exactly. Twenty-two pools remain, one more than three weeks earlier. The table below is the September reading; only the mainnet row moved.

| Chain | v3 LBP factories deployed | Pools created | Non-mock | Distinct symbols |
| --- | --- | --- | --- | --- |
| Ethereum mainnet | 5 | 7 | 2 | 2 |
| Base | 5 | 23 | 18 | 5 |
| Arbitrum | 5 | 7 | 2 | 2 |

Base carries what activity there is, and even there the eighteen pools resolve to five ticker symbols: `SINC-USDC-LBP` seven times, `LBPT-USDC-LBP` four, `LBP-Long` three, `AMPS-USDC-LBP` three, `LBPT-WETH-LBP` once – and the two `LBPT` tickers, five pools between them, read as one team's test series. Arbitrum's two include one literally named `TLBP-undefined-LBP`. Ethereum mainnet, the chain where the format was invented and where the nine-figure raises happened, carried exactly one non-mock v3 pool for seventeen months: [`LBPREEE`](https://eth.blockscout.com/address/0x05b09d23e97323460418a6396f73b04843c7046f), created 12 March 2025, five days after the first v3 factory shipped.

Re-running the same call on 9 September 2026 found the counter had moved by exactly one in three weeks, and what moved it is the more interesting half of the reading. Mainnet’s second non-mock pool is [`$JPT-USDC-LBP`](https://eth.blockscout.com/address/0xadf80bfc0a364096eb0cbd130d6ef2ba5acb7d6f), which reports itself as _Jackpotter Fixed Price Liquidity Bootstrapping Pool_, [created in block 25,882,547 on 1 September 2026](https://eth.blockscout.com/tx/0x765ddad54cc04ce2a927e159879ee464635f2c700db7e3e2120ebb6a71bcfacf). It came off the `FixedPriceLBPoolFactory` rather than an `LBPoolFactory` – the December 2025 sibling that keeps the LBP plumbing and drops the falling price. The first new mainnet pool in eighteen months is therefore not an LBP in the sense the mechanism is named for. Base and Arbitrum returned identical counts across the two readings.

Counting pools is still too generous, and the same registry makes the stricter count one more call. A Balancer v3 pool exists from the moment its factory deploys it, but it holds nothing until someone seeds it, and the [v3 Vault](https://eth.blockscout.com/address/0xbA1333333333a1BA1108E8412f11850A5C319bA9) records that separately: `isPoolInitialized(pool)` is false until the first liquidity arrives and true from then on, whatever is withdrawn afterwards. Run over all twenty-two non-mock pools on 9 September 2026 it returns true for ten, and the pool-token supplies agree with it exactly – every uninitialised pool reads zero.

Twelve pools were deployed and never funded. One of them is `LBPREEE`, which was Ethereum mainnet's entire v3 LBP history for seventeen months and turns out to have held nothing for all of it. Of the ten that were funded, seven hold exactly 1,000,000 wei of pool token – the smallest amount a v3 initialisation can post, which is a smoke test and not a sale – and an eighth holds about a tenth of one. Two carry real size: `$JPT-USDC-LBP` at 450,000 pool tokens, and Arbitrum's `TLBP-undefined-LBP` at roughly 555,940, and that second one names itself a test in its own ticker. The count that matters is therefore not 37, nor 22, but two.

Two caveats keep this honest. This is a census of Balancer's contracts on three chains, not of the format everywhere: Balancer deploys to more networks than these, and the mechanism has been reimplemented off Balancer entirely. And [Fjord Foundry](https://www.fjordfoundry.com/) is still trading – its [token-sales app](https://app.fjordfoundry.com/token-sales) answered 200 on 19 August 2026, and it now advertises Fjord's own $FJO token, staking, and a self-serve sale builder rather than a Balancer front-end. What the numbers do settle is narrower and harder to argue with: the reference implementation this page describes has been switched off where it started, and its replacement has been used a couple of dozen times in seventeen months.

For a DAO the practical reading is not "LBPs are dead". It is that a launch mechanism is a piece of someone else's infrastructure with a governance-controlled off switch, and that the gap between a well-documented mechanism and a used one can be three orders of magnitude. Before planning a raise around a format, count its pools – then ask the vault how many of them anyone ever put money into.

## Limitations and criticisms

- **Owner trust.** As above, the owner can pause the sale and controls the reserves and schedule. Participants are trusting an EOA or multisig, not just a formula.
- **Buyer education.** The downward-drifting price is counter-intuitive; inexperienced buyers who treat a falling price as a dump can panic-sell or over-pay early. A successful LBP depends on a market that understands the mechanism.
- **Not manipulation-proof.** Sophisticated actors can still accumulate patiently near the floor, and the project can seed wash volume to fake demand. The mechanism improves distribution; it does not guarantee a "fair" outcome.
- **One-shot.** An LBP is a bounded event with a start and an end — it discovers a launch price but does not provide the token a standing, always-open market afterward.

## How Caper approaches this

An LBP and a [bonding curve](/wiki/markets/bonding-curve) both aim at fair, permissionless price discovery, but they are different shapes. An LBP is a _time-boxed event_: an owner schedules falling weights, the sale runs, and it ends — after which liquidity has to be arranged separately. Caper takes the always-on route. Every caper's token trades against its own bonding curve where price is a function of how much supply has sold, so [raising funds](/wiki/markets/raising-funds) is not a one-off auction but a standing market that opens the moment a caper is created and never needs a counterparty or a close. There is no owner-set schedule to trust and no window that expires: the curve is the same rule for the first buyer and the ten-thousandth. The trade-off is the mirror image of the LBP's — a bonding curve gives up the LBP's deliberate anti-whale price decay in exchange for a market that is continuous, formulaic, and permanent.

## References

1. Balancer. [Liquidity Bootstrapping Pool](https://docs.balancer.fi/concepts/explore-available-balancer-pools/liquidity-bootstrapping-pool/liquidity-bootstrapping-pool.html) — protocol documentation (mechanism, weight schedule, owner controls).
2. Balancer. [Weighted Pools](https://docs.balancer.fi/concepts/explore-available-balancer-pools/weighted-pool/weighted-pool.html) — the spot-price/weight relationship LBPs build on.
3. Orb / Balancer Protocol. [Distribute Your ERC20 Token with Liquidity Bootstrapping Pools](https://medium.com/balancer-protocol/distribute-your-erc20-token-with-liquidity-bootstrapping-pools-b84159464c32).
4. [Fjord Foundry](https://www.fjordfoundry.com/) — LBP launch platform (formerly Copper Launch); [rebrand announcement](https://tokeninsight.com/en/news/copper-rebrands-to-fjord-foundry-launches-nft-lbp-product-fjord-drops).
5. Balancer governance. [BIP-98: Fjord (formerly Copper) and Balancer exclusive partnership](https://forum.balancer.fi/t/bip-98-fjord-formerly-copper-and-balancer-exclusive-partnership/3884).
6. Balancer Protocol. [Balancer Facilitates Record-High Liquidity Bootstrapping Pool for HydraDX](https://medium.com/balancer-protocol/balancer-facilitates-record-high-liquidity-bootstrapping-pool-for-hydradx-f08b6b0a3aee).
7. [Balancer deployment registry](https://github.com/balancer/balancer-deployments/blob/master/addresses/mainnet.json) – canonical addresses and per-deployment `status` for every LBP factory.
8. [`FactoryDisabled`, Ethereum block 25,070,461](https://eth.blockscout.com/tx/0x5f5918cf5aa81417e5d1810c15d502aa610a66594083cf81c9a9061be400be9e) – the transaction that switched off the v2 LBP factory, 11 May 2026.
9. [Balancer v3 `FixedPriceLBPoolFactory`](https://github.com/balancer/balancer-deployments/tree/master/v3/tasks/20251205-v3-fixed-price-lbp) – the December 2025 fixed-price sibling of the LBP.