Preparing
Still loading ·
How it works
People already explain in public why they are buying a coin. Fable is a launchpad where that explanation is the buy order. The coin pays for it out of fees it already earned, and everything it buys is destroyed.
Every coin pays a 1% base: 0.3% to the platform and 0.7% to the coin’s own engine. Its creator picks 0% to 5% on top and gets half of the pick (0.5% of every trade at 1%, up to 2.5% at 5%); the rest of the pick joins the engine. So traders pay 1% to 6% in all. At 0% there is no creator fee and no creator wallet, and traders pay 1%, like $FABLE. Rates stay fixed after launch. The recipient is optional: while blank, its share funds the engine. Only fees earned after activation can become creator fees. The temporary opening fee is separate. $FABLE’s own fee is 1%: 0.3% platform and 0.7% into its engine, with no personal creator payout.
A coin's engine fee splits 70/30: 70% buy and burn through its vault, 30% to its holders' DAO pot. The pot's part slides with the coin's price in its main pool: at the launch price all of it goes to buy and burn (the pot's adds are paused then anyway), about 87/13 at 1.25 times the launch price, 79/21 at 1.5 times, and the full 70/30 from twice the launch price up. Coin-denominated fees are never sold: the vault burns them as they are.
A fable posted under a coin fires that coin's vault: it spends what has unlocked in one of its pots since that pot's last fire (0.5% of the pot a minute, up to a quarter) buying the coin and burning it.
Every 24 hours, holders vote the pot into deeper pools or new ones against any asset on the launch menu. One token, one vote, up to 5 pools per wallet. Each day's pot is shared by the pools with at least 5% of the day's votes, in proportion to their votes; a pool under 5% gets nothing, and if no pool reaches 5% the pot keeps the day's share for the next count.
Why it lasts
The usual launchpad starts a coin inside a sealed launch contract that only its own site can trade, and moves it to a real exchange later, if the coin ever gets that far. Until then no outside trader or bot can reach it, and when the hype fades the trading simply stops. Fable is built the other way round.
One launch transaction opens the coin's pools on Uniswap v4, behind Fable's own hook: code that runs inside every trade to set the coin's fee and to let nobody but the locker add liquidity. Any wallet, app or bot that trades Uniswap v4 pools can reach them, so the coin isn't shut inside a launchpad contract. Its liquidity is locked for good, it trades on real markets from its first block, and it never has to move anywhere.
Every coin launches with at least three pools, and up to six, each against a different asset: ETH, tokenized stocks, USDG or another asset on the launch menu. When those assets move against each other, the coin's price drifts apart between its pools, and once the move is bigger than a round trip costs (twice the coin's fee: 2% at the lowest, as for $FABLE, up to 12% for a 6% coin, plus the swap into that asset), arbitrage bots can trade the pools back into line. Say ETH jumps 10% overnight: the coin is now about 9% cheaper in its USDG pool than in its ETH pool, a gap a bot can profit from by buying in one pool and selling in the other. When they do, both trades pay the coin's fee, even on a day when nobody is buying the coin itself.
30% of the coin's engine fee fills a pot its holders vote, every 24 hours, into deeper pools or new ones against anything on the launch menu (less of it near the launch price in its main pool, and none at it). If nobody votes, the pot deepens the pools the coin already has. A new pool starts small and grows over about half a day. More pools and deeper pools mean more routes for arbitrage, and every route pays the fee again.
Quiet coins can still burn. After six hours without a successful burn for a coin, anyone may press its burn button, the bot included: one press spends up to 25% of every pot and pays the presser 0.1% of what it spends. Every successful burn restarts that six-hour clock. Fees that cannot be spent safely remain in the vault.
Fees
One dial the creator sets once: the pick, 0% to 5% on top of the 1% base every coin pays. 0% means no creator fee.
70% buy and burn, 30% holders' DAO pot from twice the launch price up. Below that the pot's part shrinks with the price in the coin's main pool: about 79/21 at 1.5 times the launch price, 87/13 at 1.25 times, and all of the engine fee to buy and burn at the launch price (the pot's adds are paused then anyway). A coin launched without ETH whose launch pools have all been retired sends all of it to buy and burn too, until the Safe restores one of its launch assets. $FABLE’s own fee is 1%, the platform’s part included; its 0.7% engine share is 0.49% buy and burn, 0.21% pot. A coin launched with a 0% pick works the same way: no creator fee, 1% in all, 0.7% into its own engine.
The pools
The factory puts all 1,000,000,000 of a new coin's coins into its pools (half in the main pool, the rest shared by its 2 to 5 side pools; $FABLE is the exception, with 35% of its supply handed to its genesis wallets at launch), one-sided, starting at about a 1.69 ETH valuation, and hands every position to a locker that has no way to take it back out. Nothing ever migrates: the same locked positions price every trade from launch, so there is nothing to rescue.
The buy and burn
Fables drive the buy and burn. When a post lands, the bot fires that coin's vault, and the only thing it chooses is which of the vault's assets to spend: apart from a capped refund of its gas, it cannot send the money anywhere but into a buy whose coins go to the burn address. A coin nobody talks about doesn't keep a loaded vault forever: after six hours without any successful buy and burn, the bot can fire a fallback (below). Each successful burn restarts that six-hour wait.
Each fire spends what has unlocked since that pot's last fire: each of the vault's pots unlocks 0.5% of itself a minute, up to a quarter, so a burst of posts can't drain it at once. No post is turned away for being small. Each buy and burn can move the price at most one pool fee, half of a round trip's fees, so a single buy and burn can't be traded profitably. If that limit cuts a buy and burn short, the rest carries into the next one.
And if nobody posts? After six hours without any successful burn for that coin, anyone can press its burn button, the bot included. One press spends up to 25% of every pot and pays the presser 0.1% of what it spends. A successful fable burn or press starts a fresh six-hour wait; a failed attempt does not. A fable under one coin only triggers that coin’s burn.
The mesh
From launch, holders vote once a day on where the pot goes: deepen an existing pool, or open a new one against any asset on the launch menu: stocks, USDG and the other listed assets. A pair asset the Safe retires takes no new votes until the Safe restores it.
The pot fills from the first trade. Your weight is what you have in the voting box when the round closes at midnight UTC, and your vote can split it across up to 5 pools. Each day's pot is shared by the pools with at least 5% of the day's votes, in proportion to their votes; a pool under 5% gets nothing, and if no pool reaches 5% the pot keeps the day's share for the next count. If nobody votes, the pot is spread equally across the existing pools. Taking everything out of the voting box erases your vote, so vote again after you deposit. A new pool starts small and grows over about half a day. Near the launch price, the pot's adds to a launch pool are mostly coin, and the ETH that doesn't fit buys the coin instead; pools the pot opens itself take a true 50/50 at any price. More pools means every trade is echoed by arbitrage, and every echo pays the fee again.
Safety by construction
Every contract is immutable: no upgradeable proxies, no upgrades, and no owner keys on your coin. A bug in our code could lose fees. It cannot touch your balance or the locked liquidity.
| Contract | What it does | What it can never do |
|---|---|---|
| FableToken | A stock OpenZeppelin ERC-20 with vote checkpoints. 1B fixed supply, minted once. | Mint, pause, tax or blacklist. There is no custom transfer logic at all. |
| FableFactory | One call launches the token, its pools and the coin's own contracts, and takes the launch fee. | Touch a coin after it has launched. |
| FableHook | Lets only the locker add liquidity so outsiders cannot skim fees, applies the 3-second sniper fee, sets each pool's public fee when the pool is created, and accepts only full-range adds on the pools the pot opens. | Hold funds. |
| LiquidityLocker | Owns every position forever. Anyone may call collect() to forward fees. | Decrease or transfer a position. That code path does not exist. |
| FeeSplitter | Platform share to the treasury, the creator fee to the creator, the engine fee 70% to the vault and 30% to the holders' DAO pot, from twice the launch price up, the pot's part shrinking to nothing at the launch price in its main pool (and nothing to the pot while a coin launched without ETH has no live launch pool). | Send a coin's fees anywhere but its vault, its pot, the treasury and its creator-fee recipient. |
| BurnVault | Holds the vault's share (70% of the engine fee from twice the launch price up, more below it, all of it at the launch price). Buys the coin and burns it on a post, or when anyone fires it by hand. | Send value anywhere except into a swap whose output goes to the burn address, apart from a gas refund on the bot's fires (at most 10% of what the fire spent) and the 0.1% public buy and burn bounty. |
| Builder | Holds the holders' DAO pot (30% of the engine fee from twice the launch price up, less below it, none at the launch price), counts the daily vote, and lets the bot buy pair assets and add locked liquidity. | Pay out to any address. |
The bot's gas comes first (at most a quarter of a payout); then the platform's share splits 70% to buying and burning $FABLE, 20% to Fable Drops for traders and 10% to the platform.
Every coin shows what its vault is holding and what each post burned.
02 · Start here
Robinhood Chain · 4663Contracts on Robinhood Chain · addresses under Contracts
Fable is a launchpad on Robinhood Chain where every coin trades on Uniswap v4 from its launch transaction, keeps its liquidity locked forever, and spends part of its own trading fees buying itself back and burning it each time a holder posts a fable about it.
A trade in any of the coin's pools pays the coin fee, 1% to 6%: the 1% base (0.3% platform, 0.7% engine) plus its creator's 0–5% pick. A 0% pick's trade pays the 1% base alone.
The fee waits inside the locked positions until anyone collects it into the coin's own FeeSplitter.
The splitter credits the creator's share (a 0% pick has none), pays the platform's share, and passes the rest on as the engine fee.
The engine fee fills the coin's burn vault, which fables fire, and its holders' pot, which the daily vote spends.
| Component | Kind | Role |
|---|---|---|
| FableFactory | Shared | Launches a coin in one transaction: deploys the token and its engine, opens the main and side pools with the whole supply locked, takes the launch fee and runs the creator's first buy. |
| FableHook | Shared | The one Uniswap v4 hook on every pool. It fixes each pool's fee, applies the 3-second anti-bot fee, lets only the locker add liquidity, and stops a launch pool trading below its launch price. |
| LiquidityLocker | Shared | Owns every pool position forever. It can add liquidity and collect fees, and nothing else. |
| LaunchMenu | Shared, governor-owned | The pair assets, price sources and settings that future launches may use. It never changes a launched coin's pools or fees. |
| KeeperRegistry | Shared, governor-owned | The list of bot keys allowed to fire burns, run the pots and post the Fable Drop's winners list. It cannot move funds. |
| FableGovernor | Shared, holds no money | Owns every contract with settings and is the factory's guardian. The Safe proposes each change, which waits 48 hours in public unless it only stops something, and a separate veto wallet can cancel it. |
| FableBuyRouter | Shared | The site's ETH entry point for launches, and for buys and sells across all of a coin's pools. No owner; keeps nothing. |
| FableLens | Shared, read-only | One-call views and exact quotes for pages and bots. No owner. |
| FableToken | One per coin | The coin itself: a stock ERC-20 with a fixed supply and no owner, mint, pause or tax. |
| FeeSplitter | One per coin | Divides the coin's collected fees between the platform, the creator's credit and the engine. |
| BurnVault | One per coin | Holds the buy and burn share and spends it only on buying the coin and sending it to the dead wallet. |
| PotBuilder | One per coin | The holders' pot: counts the daily vote and turns its funds into locked, two-sided liquidity. |
| FableVotingEscrow | One per coin | The voting box holders deposit the coin into to vote. |
| The bot | Off chain | Reads accepted fables and fires one burn per fable, oldest first. It also presses the burn button on quiet coins, and runs the pot's conversions, builds and nightly count. |
| The fable service | Off chain | Accepts fables from signed-in holders, serves the public API, and shows each fable as fired or with its place in line. |
Non-custodial
You sign every launch, trade, vote and claim from your own wallet, straight against the contracts. Nobody, including the platform and the Safe, can withdraw a coin's locked liquidity, its burn vault, its pot, or the coins in its voting box.
Contract addresses
Fable's contracts are deployed on Robinhood Chain. Every address is listed under Contracts; check one on the explorer before you rely on it.
03 · Start here
One transaction, paid in ETH, creates the token and opens its pools with the whole supply locked in. It also deploys the coin's own fee splitter, burn vault, pot and voting box, and makes your first buy.
Name: at least 2 characters (the field takes up to 32). Ticker: up to 12 characters: letters, digits, spaces, symbols or emoji, in any case. Description: optional, up to 280 characters.
Logo: required. PNG, JPEG or WebP, under 2 MB and at least 400 × 400 px. A non-square image is cropped to its centre, and the logo is stored at 512 × 512. Socials are optional: the form has fields for a website, X, Telegram and Discord.
The logo, description and links are uploaded before the transaction and recorded as the coin's metadata address. The token stores that address once and has no function to change it, and the name and ticker are fixed at creation too.
Every coin pays the 1% base: 0.3% to the platform and 0.7% to the coin's own engine. On top of it you pick 1%, 2%, 3%, 4% or 5%, so traders pay 2% to 6%. Half of the pick goes to your creator-fee recipient: you earn 0.5% of every trade at 1%, 1% at 2%, 1.5% at 3%, 2% at 4% and 2.5% at 5%. The rest of the pick joins the engine fee that feeds the coin's burn vault and pot. The fee is written into each pool when the pool is created and can never change. See the fee table.
Or pick 0%: you earn nothing from trades and there is no creator wallet, and traders pay the 1% base on every trade, like $FABLE: 0.3% to the platform and 0.7% to the coin's own buy and burn and pot. The 0% pick.
For a 1% to 5% pick the creator-fee recipient is optional. Leave it blank to route the creator share to the engine until the controller activates a recipient; only fees earned afterwards can become creator fees. A 0% pick has no creator fees and the form leaves the recipient blank. A supplied recipient should be a wallet or Safe you control. Fable’s opening buyer, locker and hook cannot receive creator fees; the site also refuses burn addresses and other protocol addresses.
The site records your connected launching wallet as the coin's creator. That wallet is the controller: it can point creator fees at a new recipient later, claim for it, and hand control on. How creator fees work.
Pick one main pool and 2 to 5 side pools, each against a different asset from the launch menu. At launch the menu is ETH plus 41 tokens: USDG, 20 Robinhood stock tokens and 20 Robinhood Chain community coins. Each asset can be used only once per coin. ETH is the usual main pool, not a rule; the form starts from ETH as the main pool with USDG and NVDA as side pools.
Every asset you pick needs a route from ETH, because part of your first buy is swapped into it.
The first buy is required and paid in ETH. The site asks for at least 0.0001 ETH, so each pool gets a slice that buys something. You send the launch fee plus the buy in one transaction, and pay gas.
Before you sign, the site simulates the launch to learn exactly how many coins the buy will get, and sets the minimum you accept to 99% of that figure. If the buy would get fewer, the whole launch reverts.
The main pool gets half the supply and the side pools share the other half equally.
| Pools in total | Main pool | Side pools |
|---|---|---|
| 3 (1 main + 2 side) | 50% | 25% + 25% |
| 4 (1 main + 3 side) | 50% | 16.68% + 16.66% + 16.66% |
| 5 (1 main + 4 side) | 50% | 12.5% each |
| 6 (1 main + 5 side) | 50% | 10% each |
These rows are fixed in the contract: every launch has 3 to 6 pools, split exactly like this, and nobody can change it, the Safe included (MIN_POOLS() = 3, MAX_POOLS() = 6). Rounding remainders of the supply go to the dead address.
launchVersion() = 3 and feeModelVersion() = 4, and refuses to launch otherwise. Before you sign it also checks your pick against the factory's own coinFeeBreakdown.launchWithPrices publishes it in the same transaction, paid by you. It accepts only the menu sources of the assets you picked, and at most 6 updates. This helps only while the menu's opening guard is off: with the guard on, a launch reads only guarded sources, and the signed-report source reports no live band or depth, so a launch against an asset priced that way reverts.LAUNCH_FEE()) and pays it to the platform. A launch that sends less reverts.There is no bonding-curve phase and no migration. Every coin counts as graduated from its launch transaction, so its fee split and its daily pot vote start from the first trade.
Every pool of a coin opens at the same ETH-equivalent price. ETH pools start at tick 202,000, which values the whole supply at about 1.689 ETH at the first price (the site rounds this to about 1.69 ETH).
Non-ETH pools convert that price into their asset using the asset's time-averaged price. Their finer tick spacing (10, against 200 for ETH pools) lands them within about 0.1% of the ETH price, and rounding always makes the coin slightly dearer, never cheaper.
The Safe can move the launch price for future launches only, in steps of 200 ticks, within 30,000 ticks either side of 202,000. That puts a launch market cap somewhere between about 0.08 and 34 ETH. A launched coin keeps its own launch price forever.
The 7.5% price guard
When the menu's opening guard is on, each non-ETH asset's price reference must be within 723 ticks (about 7.5%) of its average. Otherwise pricing that asset fails and the whole launch reverts with OpeningPriceOutOfRange. The price source also has its own movement limit, PriceDeviation, which the Safe can set no higher than 723 ticks. Both clear on their own once the price steadies.
Once the guard is switched on, the menu has no function to switch it off. The site blocks launching with a market it reports as unavailable.
WrongPayment, or with FirstBuyRequired when sent straight to the factory. On chain a zero slice for any pool reverts with EmptyLeg; in practice the buy should be at least about 1 gwei per pool, and the site asks for 0.0001 ETH.TooLittleReceived and nothing happens.| Error | What it means |
|---|---|
| WrongPayment | Sent through the buy router (the site's path) with no more than the launch fee. Every launch must buy its own coin. |
| FeeNotPaid FirstBuyRequired | The same checks in the factory, for a launch sent straight to it: less than the launch fee, or nothing above it. |
| LaunchesPaused | The Safe has paused new launches. |
| EmptyLeg | One pool's slice of the first buy came to zero. Raise the first buy. |
| TooLittleReceived | The first buy would get fewer coins than the minimum the site set (99% of its simulation). Try again with a fresh quote. |
| DuplicateAsset | The same asset was picked for two pools. |
| OpeningPriceOutOfRange | A non-ETH asset's price was more than 723 ticks (about 7.5%) from its average. Wait for the price to steady. |
| PriceDeviation | An asset's price source tripped its own movement limit. It clears on its own. |
| InvalidCreatorFee ProtocolFeeOutOfRange | The creator and engine fees were not one of the six allowed pairs: the 0.7% base plus a pick of 0% to 5%, half of the pick to the creator and the rest to the engine (0% = none and 0.7%; 5% = 2.5% and 3.2%). |
From the first trade your coin earns fees, fills its burn vault and pot, and takes part in the daily vote. Its fee, pools, launch price and engine split never change.
Social links are part of the metadata recorded at launch. Changing them after launch is not connected on the live site yet.
Next: claiming creator fees, how fables fire your vault and how holders vote the pot.
04 · Start here
A fable is a short post about a coin, written here by someone who holds it. Each accepted fable fires that coin's burn vault once: the vault buys the coin in its own pool and sends what it bought to the dead wallet.
Sign in (X, Google, email or a wallet). Sign-in runs on Privy. If you are new, you get an embedded wallet; if you use ZKX or MetaMask, you can link your own. You don't need an X account: without one you get a Fable name and a pixel face, and you post under them.
Posting needs at least one Ethereum wallet linked to your account; the embedded one counts. One sign-in is one Fable account, and that account can link several wallets.
At the moment you post, you must hold at least $1 of the coin across your linked wallets, coins you deposited to vote included. It is valued at the coin's price in its main pool times ETH/USD. Below that you see "Hold at least $1 of $XYZ to post; you hold $0.42." The fable is credited to the linked wallet holding the most of that coin.
1 to 500 characters once trimmed, with no control characters. It is stored and shown as plain text, and it fires only the coin it is posted under.
| Rule | Detail |
|---|---|
| One a minute | Each account can post at most one fable per minute per coin, whichever wallet it uses. Posting too soon returns "One fable a minute per coin. Try again in N s." Right after you post, the "Post a Fable" button counts the minute down ("Post again in 0:42"), also after a reload. |
| A Fable coin | The service checks the factory's record: the coin must have a creator and a vault. Addresses mentioned in the text change nothing. |
| Likes and replies | Never fire anything. Replies can be up to 280 characters, one every 10 seconds per account. |
| Once only | Each fable can fire its coin's vault once. The vault records every fable id it has used, on chain. |
| Safe to retry | Every post carries a request key (the site makes one). Sending the same key again returns the same fable instead of a second one; the same key with different text or a different coin is refused. |
Every accepted fable gets a random id (a UUID), the next number in its coin's sequence, and a post time: the later of the server's clock and the coin's launch time. You supply none of these. The id the vault records on chain is keccak256("native:" + id), and the post time goes on chain in milliseconds.
The bot fires one fable per fire, taking each coin's oldest waiting fable first. It keeps its queue in a durable journal with no expiry, so an accepted fable never expires: it waits in line until its coin's vault has enough unlocked to burn, however long that takes, and it can fire only once.
A waiting fable shows its place in line: 1 plus the number of its coin's earlier fables still waiting ("Next in line", "#3 in line"). It counts down as earlier ones burn. Under the oldest waiting fable the site says in plain words why the bot is waiting, for example "Vault refilling", "Waiting for more trading" or "Waiting for a fresh price".
The bot reads the fable feed about once a second for busy coins. A coin is busy when its vault holds unspent funds, fees are waiting, fables are queued, it had a fable in the last 10 minutes, or it has just launched. Other coins are read every 30 seconds. The bot only answers fables whose time is no more than 30 seconds ahead of the chain's clock.
A fire goes out only when it would burn at least the larger of 0.00002 ETH and 3 times the gas cost of a 200,000-gas fire at the current gas price. The bot then spends the pot (ETH or a pair asset) whose fire would burn the most value, counting the coin's own fees that burn alongside. A fable right after another one usually burns less: the pot the last fire spent, and the coin's own slice, have had less time to unlock, though another pot may still be full.
| Reason | What it means |
|---|---|
| refilling | The vault's unlocked slice is not yet worth a burn (the minimum, or 3 times the gas). |
| needs_fees | Every pot that holds something is at its 25% cap and still too small. Only new trading fees help. |
| price | No fresh, reliable price for the asset the bot would spend. It tries again. |
| sniper_fee | The pool's anti-bot fee right after launch is still on (a few seconds). |
| clock | The fable's time is ahead of the chain's clock (rare, seconds). |
| gas | Waiting for gas: the bot's balance, the gas tank's top-up, or gas prices within its cost limits. |
| sending | Another of the bot's transactions is confirming first. |
| recovering | The bot is matching a burn it already sent to its fable before firing again. |
| retrying | The last attempt reverted or failed to send. It runs again on the next tick. |
| feed_backoff | The fable service did not answer for this coin. The bot asks again after 5 seconds, doubling up to 60. |
| feed_rejected | The bot rejected this coin's feed page. The coin waits until the service serves a valid page. |
| waiting | Anything else. |
The vault spends what has unlocked in one of its pots since that pot's last fire: 0.5% of the pot a minute, up to 25%. It buys the coin in the coin's own pool, and the coins go straight from the pool to the dead wallet 0x000000000000000000000000000000000000dEaD. The same fire also burns the unlocked share of the fees the vault holds in the coin itself.
Total supply stays 1,000,000,000. Explorers show the dead wallet's balance as burned, and every coin's burned() view returns it. The vault in full.
Once a minute, an indexer reads the vaults' Fired events 20 blocks behind the chain tip. It marks a fable fired only when the event comes from that coin's own vault, is a fable fire, carries the fable's id and exact post time, and burned something. The first match is final. A fable still queued 10 minutes after posting is also checked directly on its vault.
05 · Protocol
Every trade in a coin's pools pays its coin fee, 1% to 6%: the 1% base every coin pays (0.3% platform, 0.7% engine) plus the 0% to 5% its creator picked at launch. It is written into each pool when the pool is created and never changes.
| Pick | Coin fee | Creator | Engine | Platform |
|---|---|---|---|---|
| 0% · no creator fee | 1% | none | 0.7% | 0.3% |
| 1% | 2% | 0.5% | 1.2% | 0.3% |
| 2% | 3% | 1% | 1.7% | 0.3% |
| 3% | 4% | 1.5% | 2.2% | 0.3% |
| 4% | 5% | 2% | 2.7% | 0.3% |
| 5% | 6% | 2.5% | 3.2% | 0.3% |
| $FABLE (coin #0) | 1% | none | 0.7% | 0.3% |
The creator's part is half of the pick, from 0.5% of the trade at 1% up to 2.5% at 5%; the rest of the pick and the 0.7% base are the engine fee. At 0% there is no creator part: the engine gets the 0.7% and a trade pays 1% in all, the same as $FABLE. The factory rejects any other pair (InvalidCreatorFee or ProtocolFeeOutOfRange), and coinFeeBreakdown(coinFeeBps) returns the allowed pair for creator + engine: coinFeeBreakdown(70) is (0, 70), the 0% pick, and coinFeeBreakdown(570) is (250, 320), the 5% pick. The table assumes an active recipient. Without one, its share joins the engine until activation, with no retroactive creator credit. These rates apply once a pool's first 3 seconds are over.
Every pool starts with a temporary anti-bot fee, which the contracts and the launch form call the sniper fee. It is 99% of the trade in the second the pool is created and falls in a straight line to the normal fee at 3 seconds.
| Seconds since the pool was created | 1% coin fee | 6% coin fee |
|---|---|---|
| 0 | about 99% | about 99% |
| 1 | about 66.3% | about 68% |
| 2 | about 33.7% | about 37% |
| 3 and after | the normal fee | the normal fee |
SniperFeeActive.Swap fees build up inside the locked positions until someone collects them. Anyone may call the locker's collect (all of a coin's pools) or collectFor (one pair asset). The fees go to the coin's own FeeSplitter, which divides them straight away, and anyone may also call the splitter's split directly.
The bot collects a pool once at least 0.001 ETH worth of fees is waiting, and runs that collection, then the splits, in the last minutes before the midnight UTC vote count. Every buy and burn can also collect its own pool first.
Fees arrive in both currencies of a pool: the pair asset from buys and the coin from sells. Each currency is split on its own, and nothing is converted to ETH.
Each new batch is divided in proportion to the coin's three fee parts: platform 0.3%, the creator's share (none on a 0% pick) and the engine's share. The creator's part stays in the splitter as claimable credit, the platform's part goes to the platform, and rounding dust joins the engine.
The engine fee is divided between the coin's burn vault and its holders' pot, on the sliding split below.
The launch menu's default is 70% to the burn vault and 30% to the holders' pot. The Safe may set anything from 50% to 100% vault for future launches, and each coin keeps the split it launched with forever.
The pot's share also slides with the coin's price, measured from its launch price. At the launch price the pot gets none of its cut and all of the engine fee goes to buy and burn. The pot's share rises to about 4% of its cut at 1.02 times the launch price, and it gets all of its cut from twice the launch price up. Whatever the pot does not get goes to buy and burn.
| Price against the launch price | Pot gets of its cut | Vault / pot (default) |
|---|---|---|
| 1× (the launch price) | 0% | 100 / 0 |
| 1.25× | about 42% | about 87 / 13 |
| 1.5× | about 68% | about 79 / 21 |
| 2× and above | 100% | 70 / 30 |
The price comes from the coin's reference pool: its ETH launch pool if it has one, otherwise its first launch pool whose asset the Safe has not retired. No outside price feed is used. If a coin launched without ETH has all its launch assets retired, its whole engine share goes to buy and burn until the Safe restores one. Any other failed reading falls back to the normal split.
A $1,000 buy, after the pool's first 3 seconds, in a coin launched with the default 70/30 engine split. Shown in dollars for readability; the fee is actually taken in the pair asset the buyer puts in.
| On a $1,000 buy | 1% pick (2% coin fee) | 5% pick (6% coin fee) |
|---|---|---|
| Coin fee | $20.00 (2%) | $60.00 (6%) |
| Creator | $5.00 | $25.00 |
| Engine | $12.00 | $32.00 |
| → burn vault, at 2× the launch price or above | $8.40 | $22.40 |
| → holders' pot, at 2× or above | $3.60 | $9.60 |
| → burn vault, at the launch price | $12.00 | $32.00 |
| → holders' pot, at the launch price | $0.00 | $0.00 |
| Platform, 0.3% of the base | $3.00 | $3.00 |
The platform's $3.00, with no gas-tank top-up due: $2.10 (70%) goes into $FABLE's buy and burn vault, $0.60 (20%) to Fable Drops and $0.30 (10%) to the platform. With a 0% pick the same buy pays $10.00 in all: $7.00 to the coin's engine ($4.90 burn vault and $2.10 pot at 2× or above, all $7.00 to the burn vault at the launch price) and the platform's $3.00, with nothing to a creator.
The bot's gas comes first: the treasury tops up the gas tank before anything else, with at most a quarter of each payout. Then the platform's share splits three ways: 70% goes into $FABLE's buy and burn vault, 20% to Fable Drops for traders (below), and 10% to the platform. Only the 70% is fixed in the contract, for good: the 20% and the 10% are the treasury's list of destinations, which the Safe can change with 48 hours' public notice (how) and never to more than 30% in all. $FABLE the platform earns is split without being sold: 70% burned as it is, 20% sent to the draw's pot as $FABLE, and only the 10% sold for ETH. The top-up happens only while the tank is below its level (0.05 ETH by default, which the Safe can set from 0.005 to 2 ETH), and never fills it past its ceiling. Platform income that arrives as $FABLE is burned directly (70% of it) without being bought. Every treasury sale is held to a price limit: by default it fills at most about 2% worse than the token's average price, and the Safe can widen one token's limit, to at most about 10%, with the usual 48 hours' notice.
Every night, 20% of the platform's revenue goes back to traders in Fable Drops. It is bought as $FABLE, and the whole pot is paid out: up to 100 accounts win each night. After the bot's gas, the platform's split stays 70% to buy and burn $FABLE, 20% to Fable Drops and 10% to the platform.
$FABLE is coin #0 and charges a fixed 1%, the base every coin pays: 0.3% platform plus 0.7% that goes permanently into its own engine. There is no personal creator payout. Its engine split is fixed at 70/30, which is 0.49% buy and burn and 0.21% pot at full share. More on $FABLE.
A creator can pick 0% instead of 1% to 5%. The coin then has no creator fee: its creator earns nothing from trades, and there is no creator wallet to set. Its traders pay the 1% base on every trade, exactly like $FABLE: 0.3% to the platform and 0.7% into the coin's own engine, which feeds its buy and burn vault and its holders' pot like any coin's (0.49% and 0.21% at full share). It is an ordinary coin with an ordinary vault; nothing is redirected. The choice is fixed at launch and can never be changed.
coinFeeBreakdown(70) returns. The recipient can be empty (the zero address). With a 0% pick, no creator fee is ever credited, even if a recipient is set later.| Role | Who | What it can do |
|---|---|---|
| Recipient | The address in the optional "creator-fee recipient" field, or the address the controller activates later. | Receives every claim. Can press Claim. |
| Controller | The coin's recorded creator (the launching wallet, which received the first buy) until it hands control on. | Can press Claim, change the recipient, and hand control to another wallet. |
setRecipient with a nonzero recipient. Only fees earned after that activation can become creator fees. The creator portion of earlier fees, including fees still waiting in pools, stays with the engine. Activation cannot be undone; later changes must name another nonzero recipient.claimCreator pays everything owed in one currency to the current recipient. Only the recipient or the controller can press it, and the money always goes to the recipient. Fees come in whatever currency they were earned (ETH, a pair asset, or the coin itself) and are not converted, so there is one claim per currency.transferControl) and the new wallet accepts (acceptControl). Offering to the zero address withdraws the offer.CreatorFeesRedirected): its 0.7% goes into its engine.06 · Protocol
Every coin has its own burn vault. It holds the buy and burn share of the coin's fees and can do exactly one thing with it: buy the coin in the coin's own pool and send what it bought to the dead wallet. It has no owner and no withdraw function.
The vault receives its part of the coin's trading fees in whatever currency those fees were paid in: native ETH, each pair asset the coin has a pool against (tokenized stocks, USDG and other menu assets), and the coin itself. Buys pay their fee in the pair asset and sells pay it in the coin, so the vault holds several separate pots, one per asset, plus a pot of the coin.
Its share is the vault's part of the engine fee: 70% by default, more below twice the launch price, and all of it at the launch price. See the sliding split.
A fire names one asset to spend: a pair asset the coin has a pool against (address 0 means ETH, so ETH works only for a coin with an ETH pool), or the coin itself. A coin-only fire buys nothing and just burns the coin slice. Any other address is refused with UnknownAsset. A press of the burn button names none: it spends every pot (below).
A fire can first pull that pool's waiting fees out of the locker, so fees earned since the last collection count in this fire. A coin-only fire collects every pool of the coin.
The vault swaps the unlocked slice for the coin in the coin's own Uniswap v4 pool against that asset. The coins go from the pool straight to the dead wallet and never pass through the vault.
It burns the unlocked share of the coin pot directly, pays the capped gas refund (a fable fire) or the presser's 0.1% (a press of the burn button), and emits Fired. Event reference.
SniperFeeActive.NothingToBurn), and a fire on a pot already spent in the same second reverts (NothingUnlocked). A reverted fire changes nothing: no clock restarts and no fable is used up.| Kind | Function | Who | When | Paid |
|---|---|---|---|---|
| 0 · Fable | fire(asset, thesisId, thesisTime, collectFirst) | A bot key registered in KeeperRegistry | Any time; each fable id once | Gas refund |
| 2 · Burn button | burnAll(collectFirst) | Anyone, the bot included | After 6 hours without a successful burn of any kind (counted from launch for a new coin); one press spends every pot | 0.1% of what it spends, to the presser |
Fable fires. The vault cannot see the fable itself: it trusts the registered bot key for the fable id and time, and guarantees only that each id burns once, in any order. It refuses a zero id or time, an id already used (PostAlreadyConsumed), and a fable time more than 60 seconds ahead of chain time (FutureCursor). A fable fire has no six-hour wait and no one-a-minute limit, but it only spends what has unlocked since that pot's last fire.
burnAll(collectFirst), the bot included. The deadline is readable as fallbackBurnsOpenAt(), and an early press reverts with BurnedRecently. Every successful burn, a fable fire or a press, restarts the wait.collectFirst it first collects the waiting fees of every pool of the coin.PotSkipped event, and the other pots still burn. A press that burns nothing at all reverts (NothingToBurn) and restarts nothing.PressOutOfGas). A press made from inside another trade, while Uniswap v4's pool manager is busy, is refused (PoolManagerBusy): send it as its own transaction.The bot presses the button for a coin only when no fables are waiting for it, the button is open, and it has read that coin's full fable feed within the last 30 seconds. It then applies the same worth-the-gas test as fable fires; if nothing is worth burning, it backs off from 30 seconds, doubling up to 10 minutes. Reaching six hours makes a press possible but does not guarantee one.
A press pays whoever sent it 0.1% of what each pot actually spent, not of the vault, in that pot's own currency: ETH from the ETH pot, a pair token from that token's pot, and the coin from the coin's own slice. To keep it inside the unlocked slice, each pot buys with 99.9% of its slice, and 99.9% of the coin slice is burned.
A presser who can't receive a payment (a contract that refuses ETH, or an address a token blocks) simply isn't paid, and the pot still burns. Fable fires pay no bounty.
The only way value leaves a vault
Apart from burns, the only value that ever leaves a vault is the capped gas refund on fable fires and the burn button's 0.1% to whoever presses it.
burnAll): one press spends up to 25% of every pot and pays the presser 0.1% of what it spends.When a coin sits at its launch price in its ETH launch pool while a pool the pot built prices it cheaper, the bot does not spend the ETH pot in that launch pool. That way it never buys above a cheaper live market.
07 · Protocol
The rest of the engine fee fills the coin's pot. Once a day its holders vote on where the pot goes, and the bot builds it into locked, two-sided liquidity: deeper pools, or new pools against other assets on the launch menu.
Every coin has its own pot, a PotBuilder: a small fixed copy of shared code. It gets the pot's share of that coin's engine fee (30% by default, less below twice the launch price, none at it) and can do exactly one thing with it: turn it into two-sided liquidity for that coin, locked forever.
consolidate), sell a pair coin for ETH on that pair's own outside market (cashPair), or buy a pair coin with ETH (buyPair), which is how ETH gets back into a coin that has no ETH pool. Only a bot key or the governor can call these.The nightly count divides only the pot's free coins and free ETH. Pair coins the pot holds are never reserved: a build into that pair's pool uses them first, before it spends any ETH. A count can't run while the pot holds no free coins (NothingToDo), because a share made only of ETH could never be built; that ETH waits in the pot.
Deposit the coin into that coin's own voting box (FableVotingEscrow). One deposited coin counts as one vote. A deposit must be either nothing or at least 10,000 coins. Deposits can't be transferred, and the box has no owner, fee, reward, lock period or admin withdrawal.
Name up to 5 pools, each with a whole percentage above 0, adding up to exactly 100, with no pool listed twice. Each can be an existing pool of the coin or a new pool against any asset the launch menu offers. You can't vote for the coin itself, or for an asset the Safe has retired from pot funding. More pools need more wallets.
Your split is a standing vote: it repeats every round until you change it. Depositing more coins adds their weight to the split you already have.
You can always withdraw everything, even while the bot is offline. A partial withdrawal can't leave between 0 and 10,000 behind. Withdrawing everything erases your vote; depositing again doesn't bring it back, so vote again.
Example
Pool A gets 60% of the eligible votes, pool B 36% and pool C 4%. Pool C is under 5% and gets nothing that night. A and B split the whole pot 60 : 36, so A builds with 62.5% of each half and B with 37.5%.
The bot builds each share into its pool in slices (buildSlice); only a bot key or the governor can do it. Each slice uses pair coins the pot already holds first, then swaps ETH into the pool's pair coin on that pair's own outside market. Both sides go into the pool together, at the pool's price.
| Size limit (in the contract) | Rule |
|---|---|
| Value per build | At most 0.25 ETH, both sides together. |
| Share of the pool | At most 10% of the pool's existing locked liquidity. |
| Market depth | At most the pair route's depth, and the reference market's depth, divided by the menu's depth multiple (4 by default; the Safe may set 2 to 1,000). |
| A new pool's opening | At most 1% of the coin side of the reference pool. |
The LiquidityLocker owns every position forever. It can add liquidity and collect fees, and no code path exists to decrease, remove or transfer a position. Only the factory or the coin's own pot can add liquidity, and each pool keeps exactly one position forever: the launch range for a launch pool, the full range for a mesh pool. Anyone may call collect, which sends the fees to the coin's fee splitter.
Launch pools can never trade below their launch price. Mesh pools have no floor and can only ever hold full-range liquidity. More pools and deeper pools mean more routes for arbitrage, and every route pays the coin's fee again.
08 · Protocol
Every Fable coin trades in ordinary Uniswap v4 pools from its launch transaction. Any wallet, app or bot that trades v4 pools can reach them; this site trades them through Fable's buy router.
Every pool of a coin sits behind the same hook and charges the same fee, so the coin's engine is paid whichever pool a trade goes through.
A launch pool starts holding only the coin, offered from the launch price upwards. The hook reverts any swap that would leave a launch pool's price below its launch price (BelowBirthPrice), so in a launch pool the coin can never trade below where it launched.
The router's spread sell stops each pool at that floor and returns what a pool could not take. Mesh pools have no floor.
Selling near the floor
A launch pool has no liquidity below its launch price. When a coin is at or near its launch price, its launch pools can take little or nothing of a sell; only mesh pools, if the coin has any, have liquidity below it.
ok = false. Its per-pool view also reports the fee right now (feeNowPips) and fees not yet collected.When a coin's pair assets move against each other, its price drifts apart between its pools. Once the gap is bigger than a round trip costs (twice the coin's fee, plus the swap into that asset), arbitrage bots can trade the pools back into line. Both of their trades pay the coin's fee.
The token list beside the chart has two main tabs. Trending ranks every coin by one score. New launches lists coins in their first 24 hours, in the same order.
The score looks at six things:
Each one is measured against the platform's 10 biggest coins by market cap that traded in the last day. Matching them scores what they score. More than them scores higher, and less scores lower.
So the bar rises as the platform grows. While every coin is small, a new coin with a busy launch can top Trending. Once many coins are worth millions, a coin 100 times smaller needs about 3 times their activity to pass them. That takes a huge start, like whales and heavy buying from the first minutes.
A price drop in the last 5 minutes sinks a coin: down 50% halves its score, and down 90% leaves a tenth. Coins that are nearly tied keep their places, so the list doesn't flicker.
A new coin can be on both lists. After 24 hours it leaves New launches and stays on Trending only on its numbers.
The price guards limit launches and the protocol's own trades. They never block your trades; only a launch pool's floor can stop a sell.
| Protocol action | Limit |
|---|---|
| A launch | Each non-ETH asset's price reference must be within 723 ticks (about 7.5%) of its average, or the launch reverts. |
| A buy and burn | May move its pool's price by at most one pool fee, so buying just before it and selling right after always loses. |
| A pot buy of the coin | May move the price by at most 5% of a round trip in fees, and must get at least 92.5% of a fee-free quote. |
| A pot trade of a pair coin | Refused if worse than the menu's price minus 723 ticks; about 2% plus route fees through the built-in swapper. |
| A buy and burn or a pot buy of the coin, in a pool's first 3 seconds | Not allowed: protocol-owned swaps in the coin's own pools wait for the anti-bot fee to end (SniperFeeActive). A launch's opening buy is exempt, and a pot's pair-coin trades happen on outside markets. |
09 · Protocol
$FABLE is coin #0: the first coin on Fable, launched by the wallet the Safe reserved for it, with its own fixed 1% fee and extra fuel from the platform's share of every coin's trades, its own included.
After the bot's gas (at most a quarter of each payout), 70% of the platform's share of every coin's trades, and of every launch fee, goes into $FABLE's buy and burn vault; platform income that arrives as $FABLE is burned directly (70% of it) without being bought. 20% funds Fable Drops, paid out in $FABLE to up to 100 traders every night (how Fable Drops work), and 10% goes to the platform.
Claiming creator fees, changing the recipient and handing over control all revert for $FABLE (CreatorFeesRedirected).
$FABLE's vault has no trigger key of its own. Like every coin's vault, it fires once for each fable posted about $FABLE, and six hours after its last successful burn anyone can press its burn button, the bot included. A press shows as kind 2 in the Fired event.
$FABLE trades only in a Uniswap v4 pool, so it needs its own guarded price feed before new coins can pair with it. The rehearsed plan has four steps. They come after $FABLE's launch, when setup is over, so each Safe step waits 48 hours in public first, except retiring $FABLE, which is an emergency stop and applies at once.
The Safe points the guarded v4 price feed (GuardedV4SampledSource) at $FABLE's ETH pool with a 30-minute window, and sets $FABLE's risk policy.
The Safe retires $FABLE from pot funding, to keep it off holder votes until a pot swapper that can trade Uniswap v4 is live.
The Safe queues $FABLE on the launch menu.
Once the feed is warm, a bot key (normally the bot) activates the listing, and new coins can then launch with a $FABLE pool.
Bot keys record the pool's price and liquidity once per 5-minute slot. A read uses the median of the window (30 to 75 minutes). It needs at least 4 samples covering at least half the window, with the newest no more than 10 minutes old. It also needs the live price within the risk limit (at most 723 ticks) and enough depth, taken from the lower of current liquidity and the smallest liquidity sampled. The depth floor is a Safe setting: the plan for production is 5 ETH (the rehearsal used 0.1 ETH).
The pots' built-in swapper only follows Uniswap v3 routes, so it can't trade $FABLE. Pools of $FABLE funded by holders need a new swapper, which the Safe must propose and can switch on only 48 hours later, and then the Safe un-retiring $FABLE, which also waits 48 hours. No date is set for either.
10 · Protocol
What can change, who can change it, and what nobody can change. Nothing in Fable can be upgraded, and a launched coin's pools, fees and locked liquidity are fixed. The Safe's settings shape future launches and the routes a pot trades through, and every change to them waits 48 hours in public first, unless it only stops something.
renounceOwnership always reverts. Ownership can only move to a new owner in two steps (transfer, then accept), and so does the factory's guardian role. Handing either over is a governor change, so it waits 48 hours.| Nobody can | Why |
|---|---|
| Pull a coin's liquidity | The locker has no code that decreases, removes or transfers a position. This holds for the creator, the platform and the Safe alike. |
| Take a vault's, pot's or voting box's funds | None of them has an owner or an admin withdrawal. Depositors can always withdraw their own coins from the voting box. |
| Change a launched coin's fees or split | They are recorded once when the pools are created, and nothing can set them again. The pot's part still slides with the coin's price, and a coin launched without ETH sends its whole engine fee to buy and burn while the Safe has retired every one of its launch assets. |
| Mint, pause, tax or blacklist a coin | The token is a stock OpenZeppelin ERC-20 with no owner and no custom transfer logic. |
| Pause trading | Only new launches can be paused. |
| Upgrade a contract | Nothing is upgradeable. Each coin's pot is an EIP-1167 minimal proxy, a tiny fixed copy in front of shared pot code, and neither the copy nor the shared code can ever be changed. |
| Skip the 48-hour wait | Once setup has ended, every change the Safe makes waits 48 hours in public, in FableGovernor or in its own contract, and the veto wallet can cancel it or freeze the Safe. Only the emergency stops apply at once, and they can only stop something. The veto wallet itself can only say no: it can't propose a change or move money. |
Each change waits 48 hours in public first, unless it says "at once" here.
The same rule: 48 hours in public first, unless it says "at once".
A registered bot key can fire fable burns, run the pot's conversions and builds, count rounds early, record the 5-minute price samples the guarded v4 feed (planned for $FABLE) reads, run the treasury's sales and the rewards pool's buys, and post the Fable Drop's winners list. Nothing in KeeperRegistry can move funds: the worst a bad key can do is fire a burn at a poor moment, not fire at all, or post a wrong Fable Drop winners list, which pays nothing for its first hour, so the Safe or the veto wallet can cancel it. A leaked key can pull at most its gas-tank target per hour until the Safe removes it (an emergency stop, at once), and every protocol-owned trade it starts is held to the contracts' price limits.
Every coin is a stock OpenZeppelin ERC-20 with Permit and Votes. Its supply is fixed and minted once. It has no owner, no mint function, no pause, no tax, no blacklist and no custom transfer logic. Vote checkpoints use timestamps, because on this chain block.number is the L1 block number. Burning means sending coins to the dead wallet, so total supply stays 1,000,000,000.
FableToken, BurnVault, PotBuilder, FableVotingEscrow, LiquidityLocker, FableHook, MeshBuildMath, MeshSwapGuard, PairSwapper, FableLens, FableBuyRouter and FableOpeningBuyer. The FeeSplitter's only controller is the coin's creator-fee controller, and only for creator fees.
The pots plan only with guarded sources: ones that report an average, a live price band and a depth. Launches do too once the menu's opening guard is on, and that menu has no way to switch it off again. Any other source fails closed, so no pot plans with that asset and, with the guard on, nothing launches against it.
SystemDeployer lets a hardware wallet deploy the contracts using ordinary transactions. It creates each contract at an address fixed in advance and reverts if one lands anywhere else. It holds nothing and has no power over what it deployed.
11 · Build on Fable
Every Fable contract is listed below with its address on Robinhood Chain. Each launch also creates its own token, fee splitter, burn vault, pot and voting box.
| Network | Robinhood Chain |
|---|---|
| Chain ID | 4663 |
| Native currency | ETH (18 decimals) |
| Public RPC | https://rpc.mainnet.chain.robinhood.com |
| Explorer | https://rh-scan.com ↗ |
| Pools | Uniswap v4, every one behind FableHook |
| Burn address | 0x000000000000000000000000000000000000dEaD |
| Version markers | launchVersion 3 · feeModelVersion 4 · postIdentityVersion 1 · fallbackPolicyVersion 3 |
Launches a coin in one call: deploys the token and its engine, opens the main and side pools with the whole supply locked, takes the launch fee and runs the creator's first buy. Its guardian is FableGovernor, through which the Safe acts.
The one Uniswap v4 hook on every pool: sets the fixed fee and the 3-second anti-bot fee, lets only the locker add liquidity, keeps launch pools at or above their launch price, and allows only full-range liquidity in pools the pot opens.
Owns every pool position forever. It can only add liquidity and collect fees (anyone may call collect), and it forwards the fees to the coin's FeeSplitter.
Spreads the creator's ETH first buy over every launch pool in proportion to its starting supply, in one step and exempt from the anti-bot fee, and refunds what a pool could not take.
Called only by the factory to deploy each coin's FeeSplitter, BurnVault, PotBuilder copy and voting box, and to fix the coin's engine split within 50–100% vault.
Creates each coin's voting box with the fixed 10,000-coin minimum deposit.
Created in each coin's launch transaction. FableLens.coinView(coin) returns a coin's splitter, vault and pot, and FableFactory.vaultOf(coin) returns its vault.
A stock OpenZeppelin ERC-20 (Permit + Votes) with a fixed 1,000,000,000 supply, 18 decimals, metadata set once, and no owner, mint, pause or tax.
Divides the coin's collected fees between platform, creator credit and engine (burn vault or pot, on the sliding split), and handles creator claims, recipient changes and two-step control transfer.
Holds the coin's buy and burn fees per asset and, when fired, buys the coin in its own pool and sends it to the dead wallet under the tap, the cap and the price limit.
Keeps the coin and ETH halves, counts the daily vote, and lets the bot convert fees and build locked two-sided liquidity. A fixed EIP-1167 copy of shared code; no owner, no withdraw.
Holders deposit coins (0 or at least 10,000) and keep a standing split of up to 5 pools. No owner, no reward; withdraw any time.
Lists the pair assets, the launch price and the default engine split that future launches may use (the 3–6 pool counts and their supply split are fixed in the contract); retires assets from pot funding; holds the pots' pair-swapper switch with its 48-hour notice. A replacement menu must be announced here 48 hours ahead.
The list of bot keys allowed to fire vaults, run the pots and post the Fable Drop's winners list, plus the gas tank's limits. Removing a key applies at once; adding one waits 48 hours. It cannot move funds.
Owns every contract with settings and is the factory's guardian. The 3-of-3 Safe proposes; each change waits 48 hours in public, emergency stops apply at once, and a separate veto wallet can cancel a waiting change, freeze the Safe or start a recovery.
Created by KeeperRegistry. Collects the vaults' ETH gas refunds and lets each bot key top itself up at most once an hour, so nobody funds the bot by hand.
Plans every pot build and enforces the hard limits: fair price, the 7.5% gap, 0.25 ETH, 10% of the pool, depth caps and the launch-price pause. Also computes the pot's sliding share.
Fixed price limits for the pot's own coin buys: at most 5% of a round trip, and at least 92.5% of a fee-free quote.
The pots' built-in Uniswap v3 swapper for turning ETH into a pair coin and back, only along the guarded price route and within about 2% plus fees. The burn vault does not use it.
The site's ETH-only entry point: forwards launches (optionally publishing fresh price reports first) with a caller-bound salt, and does one-signature buys and sells across all of a coin's pools. Keeps nothing.
One-call reads of the launch menu, a coin's fees and pools, the current fee including the anti-bot fee, uncollected fees, a vault's state, and exact swap quotes.
Uniswap v3 time-averaged prices, configured by the Safe through the governor, with a live-price band, a depth floor, issuer checks and up to two agreeing backup routes. The source launches and pots use for listed assets.
Experimental: accepts Uniswap v4 price reports signed by 2 of 3 separate keys, valid for at most 5 minutes and checked against the live pool.
The guarded price for a v4-only asset, $FABLE first: the median of bot-recorded 5-minute samples, plus a live-price band and a depth floor.
AnchoredV3PriceSource, ChainlinkPriceSource, V3TwapSource, V3TwoHopSource, V3OpenSource and V4SampledSource exist in the source code but are not in the production deployment plan.
Lets a hardware wallet deploy the system with ordinary transactions at addresses fixed in advance. It holds nothing and has no power over anything it deployed.
Uniswap's own v4 singleton on Robinhood Chain, already live and not deployed by Fable. It holds every Fable pool; FableHook, the locker and the lens all work through it.
Every coin launched on Fable has its own token address, a fixed supply of 1,000,000,000, no owner, no minting and no transfer tax.
12 · Build on Fable
For builders, bots and indexers: the fable service's public API, the Fired event every burn emits, and the contract reads that describe a coin.
Base URL
The fable service answers at https://fablecurve.fun. The API paths below are relative to it; contract addresses are under Contracts.
No sign-in needed.
| Request | Returns |
|---|---|
| GET /api/theses?coin=0x…&limit=50&before=<sequence> | One coin's fables, newest first. limit defaults to 50, up to 100; before pages back by sequence number. |
| GET /api/theses/latest?limit=20 | The newest fables across all coins. limit defaults to 20, up to 50. |
| GET /api/theses/<id> | One fable. |
| GET /api/theses/<id>/replies | Its replies, oldest first, up to 200. |
| GET /api/status | The bot's latest report and the indexer's progress. |
| GET /api/health | Whether the service is up. |
| Request | Does |
|---|---|
| POST /api/theses | Body { coin, text, requestId, image? }. Posts a fable; needs a Privy session (X, Google, email or a wallet) and linked wallets holding at least $1 of the coin. Returns 201. |
| POST /api/theses/<id>/like | Toggles your like. |
| POST /api/theses/<id>/replies | Body { text, image? }. Replies, with one optional image as on a fable; needs a Privy session. |
Writes are accepted only from the Fable site's own origins (otherwise 403 origin), with the Privy access token as a Bearer header. Other websites can read the API, but browsers stop them from posting to it.
requestId is 1 to 100 characters of letters, digits, _ or -. It makes posting safe to retry: the same key returns the same fable (200), and the same key with different text or a different coin returns 409.
| Field | Meaning |
|---|---|
| id | The server's random UUID for the fable. |
| coin | The coin's address. |
| sequence | Its number in the coin's contiguous sequence. |
| createdAtMs | Post time in milliseconds: the later of the server's clock and the coin's launch time. |
| text | Plain text, 1 to 500 characters. |
| author | { wallet, xId, xHandle, name, avatar, pixelSeed }: the linked wallet holding the most of the coin at posting, then the author's account. xId and xHandle are null for an account without X. name is the Fable name, avatar the picture (or null), and pixelSeed the seed of the pixel face shown when there is no picture. |
| thesisId | keccak256("native:" + id): the id the vault records on chain. |
| likes, replies | Counts. |
| burn | Either { status: "fired", tx, tokensBurned, spent, asset, firedAt } or { status: "queued", line, why, waiting }, where line is the place in line and why and waiting say why the coin's oldest fable waits (a code and plain words; null when the bot gives none). |
spent is in the spent asset's own units: wei when asset is "ETH", otherwise that token's units (asset is then the token's address). Never assume it is ETH. tokensBurned is in the coin's units and equals bought + burnedDirect from the Fired event.
GET /api/status returns { receivedAt, bot, indexer: { block, ranAt } } and is cached for 10 seconds. The site treats burn data as fresh while the indexer ran within the last 3 minutes, the bot as live while its heartbeat (sent every 30 seconds) arrived within 90 seconds, and the fable reader as down when bot.feed.ok is false. The bot's report names a reason for each waiting coin; the reasons are listed here.
| Status | Code | Meaning |
|---|---|---|
| 401 | sign-in | Not signed in. |
| 403 | link-wallet | No Ethereum wallet linked. |
| 403 | no-holding | None of your linked wallets holds the coin. |
| 403 | hold-min | Your linked wallets hold less than $1 of the coin; the message says how much you hold. |
| 403 | origin | The request didn't come from the Fable site. |
| 404 | not-a-coin | The address is not a Fable coin. |
| 400 | text-empty · text-long · text-char | The text is empty, over 500 characters, or has control characters. |
| 400 | coin · request-id | The coin address or the request key is not valid. |
| 409 | request-reused | The request key was already used with different text or a different coin. |
| 429 | rate | One fable a minute per coin; the response has a Retry-After header. |
| 503 | privy-unavailable · rpc-unavailable · busy | A service the API depends on is down, or the API is busy. Try again. |
Every fable fire of a burn vault emits one, and a press of the burn button emits one for each pot it burned:
event Fired(
address indexed asset, // what was spent; address(0) = ETH
uint256 spent, // in the spent asset's units (wei for ETH)
uint256 bought, // coins bought and sent to the dead wallet
uint256 burnedDirect, // coin-denominated fees burned directly
uint256 gasRefund, // the bot's gas refund (kind 0) or the presser's 0.1% (kind 2)
uint64 thesisTime, // the fable's post time in ms; 0 for a press
bytes32 thesisId, // keccak256("native:" + id); 0 for a press
uint8 kind, // 0 or 2, below
address caller
);
// topic0
0x135cd330164d9d4bbcfe631da50b8acc90b6f074db81852fd6453bb8e70102d8| kind | Fire | gasRefund holds |
|---|---|---|
| 0 | Fable fire by the bot (fire) | The bot's gas refund |
| 2 | A press of the burn button (burnAll), one event per pot it burned | The presser's 0.1% |
bought + burnedDirect, both in the coin's units.asset: wei for the ETH pot, the pair token's units for its pot, and the coin's units for the coin's own slice. gasRefund is 0 on coin-only fires by the bot, and on a press whose presser could not be paid.thesisTime and thesisId are 0 for every press of the burn button.FableFactory.coinCount() and FableFactory.allCoins(i) list every coin in launch order; the bot finds new coins this way. Each launch also emits these factory events, and PoolOpened fires again whenever a coin's pot opens a new pool.
event Launched(
address indexed token,
address indexed creator,
bytes32 indexed poolId, // PoolId of the main pool
uint16 creatorFeeBps,
uint16 protocolFeeBps, // the engine fee
uint24 feePips, // the pool's normal fee: 3,000 + (creatorFeeBps + protocolFeeBps) × 100
string name,
string symbol
);
event PoolOpened(address indexed token, address indexed asset, bytes32 indexed poolId, uint160 sqrtPriceX96, uint256 coinsSeeded); // coinsSeeded = 0 for a pool the pot opens
event CreatorBought(address indexed token, address indexed creator, uint256 ethIn, uint256 tokensOut);| Call | What it tells you |
|---|---|
| FableLens.menuView() | Everything the launch form needs in one call: the listed assets and whether each is ready, the fewest and most pools on offer, and today's engine split. |
| FableLens.coinView(coin) | A coin's fees, split, pools and burned total, with its splitter, vault and pot addresses. |
| FableLens.poolView(coin, asset) | One pool, including the fee right now (feeNowPips) and its uncollected fees. |
| FableLens.vaultView(coin) | The vault's last fire times, when its burn button opens (publicBurnOpensAt), the coin pot, every pot per asset and each pot's unlocked share. |
| FableLens.quote(coin, asset, buy, amountIn) | An exact quote through the hook. Call it with eth_call; ok = false for a sell below the launch floor. |
| BurnVault.fallbackBurnsOpenAt() | When the burn button opens: six hours after the coin's last successful burn, or its launch. |
| BurnVault.consumedPostIds(thesisId) | Whether a fable has fired (selector 0x944158f1). |
| FableToken.burned() | Coins at the dead wallet. |
| FableFactory.vaultOf(coin) FableFactory.poolKeyFor(coin, asset) | A coin's vault, and the pool key in which asset buys the coin. |
| FableFactory.launchVersion() FableFactory.feeModelVersion() FableFactory.coinFeeBreakdown(coinFeeBps) | 3, 4 (fee model 4: the 1% base on every coin and the creator's 0–5% pick on top), and the allowed creator and engine fees for creator + engine: coinFeeBreakdown(70) is (0, 70), coinFeeBreakdown(570) is (250, 320). |
import { createPublicClient, defineChain, http, keccak256, parseAbi, parseAbiItem, toHex } from 'viem';
const robinhood = defineChain({
id: 4663,
name: 'Robinhood Chain',
nativeCurrency: { name: 'Ether', symbol: 'ETH', decimals: 18 },
rpcUrls: { default: { http: ['https://rpc.mainnet.chain.robinhood.com'] } },
});
const client = createPublicClient({ chain: robinhood, transport: http() });
const FACTORY = '0x837cb9F4Ac0d480C95214e2184d3E81427243d15';
const COIN = '0x…';
const abi = parseAbi([
'function vaultOf(address coin) view returns (address)',
'function burned() view returns (uint256)',
'function consumedPostIds(bytes32 postId) view returns (bool)',
'function fallbackBurnsOpenAt() view returns (uint256)',
]);
const fired = parseAbiItem(
'event Fired(address indexed asset, uint256 spent, uint256 bought, uint256 burnedDirect, uint256 gasRefund, uint64 thesisTime, bytes32 thesisId, uint8 kind, address caller)'
);
const vault = await client.readContract({ address: FACTORY, abi, functionName: 'vaultOf', args: [COIN] });
const burned = await client.readContract({ address: COIN, abi, functionName: 'burned' });
// every burn of this coin: tokens burned = bought + burnedDirect
client.watchEvent({
address: vault,
event: fired,
onLogs: (logs) => logs.forEach(({ args }) => console.log(args.kind, args.bought + args.burnedDirect)),
});
// has a fable fired? thesisId = keccak256("native:" + the fable's id); the API's fable record also carries it as thesisId
const THESIS = '…'; // a fable's id (a UUID) from GET /api/theses
const thesisId = keccak256(toHex('native:' + THESIS));
const done = await client.readContract({ address: vault, abi, functionName: 'consumedPostIds', args: [thesisId] });The example uses Robinhood Chain's public RPC, the one this site adds to your wallet; any RPC endpoint you trust for chain 4663 works.
| Name | Value |
|---|---|
| LAUNCH_FEE | Starts at 0.0005 ETH per launch, set by the Safe between 0 and 0.01 ETH (read it from the factory) |
| PLATFORM_FEE_PIPS | 3,000 pips = 0.3% of every trade |
| MIN / MAX_COIN_FEE_BPS | 70 / 570 bps (creator + engine: the 0.7% base plus a whole 0–5% pick) |
| BASE_ENGINE_BPS | 70 bps: every ordinary coin's engine gets at least the 0.7% base |
| MAX_CREATOR_FEE_BPS | 250 bps: the creator share is the pick ÷ 2, so 2.5% at 5% |
| NO_CREATOR_COIN_FEE_BPS | 70 bps: the 0% pick, no creator share and all 0.7% to the engine |
| SUPPLY | 1,000,000,000 tokens, 18 decimals |
| SNIPER_START_PIPS · SNIPER_SECONDS | 990,000 pips (99%) · 3 seconds |
| MAX_FEE_PIPS | 200,000 pips: a pool's normal fee is at most 20% |
| DEFAULT_START_TICK | 202,000; the Safe may move it ±30,000 in steps of 200 for future launches |
| Tick spacing | 200 for ETH pools, 10 for every other pair asset |
| MAX_OPENING_DEVIATION_TICKS | 723 ticks (about 7.5%) |
| MIN_POOLS / MAX_POOLS | 3 / 6, fixed: no one can offer other pool counts |
| MAX_GENESIS_BPS | 3,500 bps: 35% of supply, coin #0 only |
| GRADUATION_TICKS | 16,200 ticks, about 5.05× the launch price (a milestone only) |
| Vault tap · cap | 0.5% of a pot per minute · 25% per fire |
| PUBLIC_AFTER | 6 hours |
| BOUNTY_BPS | 10 bps = 0.1% of what a press of the burn button spent, to the presser |
| REFUND_BPS · GAS_SHARE_BPS · GAS_OVERHEAD | 12,500 (1.25× gas) · 1,000 (at most 10% of the spend) · 60,000 gas |
| ROUND · COUNT_OPEN_AFTER | 1 day, closing 00:00 UTC · anyone may count from 2 hours after |
| MIN_SHARE_PERCENT | 5% of the round's eligible votes |
| MIN_DEPOSIT · MAX_POOLS_PER_VOTE | 10,000 coins · 5 pools |
| MAX_BUILD_WEI · MAX_ADD_BPS · OPEN_MAX_BPS_OF_REF | 0.25 ETH · 10% of the pool · 1% of the reference pool's coin side |
| MIN_BUILD_GAP | 60 seconds between builds into the same pool |
| PAIR_SWAPPER_DELAY | 48 hours |
| DELAY · RECOVERY_DELAY | 48 hours · 48 hours: FableGovernor's wait before a change can be carried out, and before a recovery |
| SUCCESSOR_DELAY · CHANGE_DELAY · MIGRATION_DELAY | 48 hours each: a replacement launch menu, a new treasury list, moving the rewards pool |
| VETO_WINDOW | 1 hour: a Fable Drop winners list pays nothing yet and can be cancelled |
13 · Reference
The words this site uses, in plain English.
burnAll(collectFirst) on a coin's burn vault: once the coin has gone six hours without a successful burn (or since its launch), anyone can press it, the bot included. One press spends up to 25% of every pot and pays the presser 0.1% of what it spends.0x000000000000000000000000000000000000dEaD. Coins sent there are burned; total supply stays 1,000,000,000.14 · Reference
Short answers, with a link to the full rule where there is one.
Pop-ups and toasts on the site say a few words: what happened and the fix. Here is what the common ones mean. Every message that says "nothing was sent" means no transaction reached the chain and no funds moved.
| Message | What it means |
|---|---|
| Cancelled · nothing was sent | You cancelled the request in your wallet. |
| Wrong network | Your wallet is on another network. Switch it to Robinhood Chain and try again. |
| Open your wallet | Your wallet already has a request open: approve or cancel it there. |
| Not enough ETH · include gas | Your wallet needs enough ETH for the action and for its gas. |
| Tx waiting in wallet | An earlier transaction is still waiting in your wallet. Let it finish (or cancel it there), then try again. |
| Pending · don't repeat | A transaction was sent and is waiting for confirmation. Sending it again could spend twice. |
| Maybe sent · check your wallet | Your wallet's answer was interrupted, so it is not known whether it sent. Check its activity; clear the notice only if nothing is pending. Clearing it cancels nothing. |
| Stopped after step N | Some earlier steps of a multi-step action confirmed. Check your wallet before continuing: an approval may still be active. |
| … · reverted · only gas spent | The transaction was mined but the chain refused it, so only its gas was charged. |
| Burn button opens after 6h without a burn | Buy and burns from fables are fired by the bot. Anyone can press a coin's burn button once it has gone six hours without a successful burn (the burn button). |
| Nothing has unlocked yet | Each of a vault's pots unlocks 0.5% a minute after its own last buy and burn (the tap). |
| The coin is only seconds old | For its first seconds a coin charges the sniper fee, and the vault waits until that has passed (anti-bot fee). |
| The pools can't take that sell · sell less | Selling that much would push a launch pool below its launch price, which launch pools never trade under. |
| The price moved · under your slippage limit | The trade would return less than your slippage setting allows; nothing was spent. Try again, or allow more slippage. |
| Pot paused · fees go to buy and burn | The Safe retired every launch asset of this coin, so its pot has no live price to build against until one is restored. Meanwhile all of its engine fee goes to buy and burn. |
| The bot adds it soon | Only the bot, or the Safe through FableGovernor after a 48-hour wait, puts a pot's credit into a pool, so nobody can time it around their own trades. |
| Switch to the controlling wallet | Creator-fee changes need the wallet that controls the coin's creator fees: the one that launched it, unless control was handed over (creator fees). |
| Clears in ~N min · or swap a pool | A pool asset's price is outside the 7.5% launch price guard. It clears on its own once the average catches up; swapping that pool lets you launch now (the price guard). The full reason, with its numbers, is the message's tooltip. |
| Launch unavailable · refresh the page | The site and the contracts disagree (for example a different fee model). Nothing was sent; the full reason is in the browser console. Launch errors by name are listed under launch errors. |
The launch fee (it starts at 0.0005 ETH, set by the Safe between 0 and 0.01 ETH; the launch page shows the current one) plus your first buy, in ETH, in one transaction, plus gas. The first buy is required (the chain rejects zero), and the site asks for at least 0.0001 ETH because the buy is split across all your pools.
The factory requires a paid first buy; it is the only way the creator gets coins. Your ETH is split across every launch pool in proportion to the coins each opened with, and the slices for non-ETH pools are swapped into that pool's asset on the way in. All pools rise together from one price, leaving no gap between pools for bots to arbitrage. It is also the one trade exempt from the anti-bot fee.
No. The name and ticker are fixed at creation, and the token stores its metadata address once, with no function to change it.
No. ETH is the usual choice but not a rule for ordinary coins: the main pool can be any listed asset, and each asset can be used only once per coin. Only $FABLE must include an ETH pool.
Every non-ETH launch pool opens at its asset's guarded average price. If any chosen asset's live price is more than about 7.5% (723 ticks) from that average, the whole launch reverts. This clears on its own once the price steadies. The price guard.
It comes back to your address in the same transaction: the ETH pool's leftover as ETH, any other pool's leftover in the token that slice had been swapped into.
Every coin pays the 1% base (0.3% platform, 0.7% to the coin's engine), and you pick 0%, 1%, 2%, 3%, 4% or 5% on top, so traders pay 1% to 6% after the first 3 seconds. At 0% traders pay 1% in all, like $FABLE, and you earn nothing from trades. The fee is written into each pool when it is created and cannot be changed, and pools the holders add later charge the same fee.
Half of your pick: 0.5% of every trade at 1%, 1% at 2%, 1.5% at 3%, 2% at 4% and 2.5% at 5%. The rest of the pick joins the 0.7% base as the engine fee. At 0% you earn nothing, and there is no creator wallet.
Fees are credited to your coin's FeeSplitter each time the pools' fees are collected. Anyone can collect, and the bot does once about 0.001 ETH is waiting. The recipient or the controlling wallet then presses Claim, once per currency, and the money always goes to the recipient. Fees come in whatever currency they were earned (ETH, the pair asset, or the coin itself) and are not converted.
Yes. The controller (the launching wallet, until it hands control on) can point the fees at a new recipient with one transaction, and unclaimed fees move too. Control itself moves in two steps: the controller offers it, then the new wallet accepts.
In the second a pool is created, trades pay 99%. The fee falls in a straight line to the normal fee at 3 seconds: roughly 66–68% in second 1 and 34–37% in second 2, depending on the coin's fee. Your own opening buy inside the launch transaction is exempt. What snipers pay is split like any fee, so your coin's engine gets its share. The schedule.
By default, 70% goes to the coin's buy and burn vault and 30% to its holders' pot. The pot's part slides with price: nothing at the launch price, about 13% of the engine fee at 1.25×, about 21% at 1.5×, and the full 30% from twice the launch price up. The rest goes to buy and burn. A coin keeps the split it launched with.
The bot's gas comes first, at most a quarter of each payout. Then 70% of the platform's share goes into $FABLE's buy and burn vault ($FABLE the platform earns is burned directly, 70% of it), 20% funds Fable Drops for traders and 10% goes to the platform. Only the 70% is fixed in the contract, for good. The 20% and the 10% are the treasury's list of destinations: the Safe can change that list, never to more than 30% in all, but only with 48 hours' public notice, and the veto wallet can cancel the change meanwhile. Whatever of the 30% nobody takes also goes to buy and burn $FABLE.
Every night, 20% of the platform's revenue for the UTC day that just ended (its 0.3% of every trade, plus the launch fees, after any gas-tank top-up) is bought as $FABLE and paid out, all of it, to up to 100 accounts. You need 300 tickets to enter, and more tickets means a better chance of being drawn; if 100 or fewer accounts qualify, all of them win. The winners share the pot in proportion to their tickets, and nobody takes more than 25% of a night's pot. If nobody qualifies, the pot is burned. The draw uses the hash of a block mined about a minute after midnight UTC, so anyone can run it again and check the winners. The payout is automatic: the list of winners is published, the Safe or the veto wallet can cancel it within its first hour, and each share is then sent to the winner's payout wallet, the one you choose in Wallets on the account menu, or your Privy wallet until you choose. Nobody has to claim; only if a payment was not sent does the Claim button in Rewards on the account menu pay it. After the bot's gas, the platform's split stays 70% buy and burn $FABLE, 20% Fable Drops, 10% platform. The draw's pot buys its $FABLE bit by bit (0.5% of its ETH a minute), under the same price limit as the burns. It runs from launch.
Trade. Your tickets come from the trading fees your account paid over the last 7 UTC days, across every Fable coin and every pool: 1 ticket for every 0.000001 ETH of fees. Everything you pay on a swap at the pool's normal fee counts (the coin's fee and the platform's 0.3%, valued in ETH at the price of each trade; in a pool's first 3 seconds, not the anti-bot fee), and all the wallets linked to your account count together, however you signed in. No wallet is left out: each day, a wallet's fees count for the account it was linked to at that UTC day's last block, and a wallet linked to no account then counts for nobody. You need 300 tickets (0.0003 ETH of fees, about $1) to enter. Each night the oldest day drops off, so keep trading to keep your tickets. Rewards on the account menu shows your tickets and the countdown to tonight's drop, and the leaderboard's Fable Drops board shows where you stand.
$FABLE is coin #0, launched only by the wallet the Safe reserved for it. It charges a fixed 1%: 0.3% platform plus 0.7% into its own engine, with no personal creator payout. At full share that is 0.49% buy and burn and 0.21% pot.
No. The token has no transfer tax. Fees are charged only on swaps in the coin's pools.
Sign in (X, Google, email or a wallet) and hold at least $1 of the coin across the wallets linked to your account at the moment you post. One fable a minute per coin. You don't need an X account. Coins you deposited to vote still count toward that holding. Your fable is credited to whichever linked wallet holds the most of that coin. Text is 1 to 500 characters, plain text only.
No. The limit is per account, not per wallet: one fable per minute per coin. One sign-in is one Fable account, however many wallets it links.
It spends what has unlocked in one of the coin's vault pots since that pot's last fire: 0.5% of the pot per minute, up to 25%. It also burns the unlocked share of fees the vault holds in the coin itself. The bot picks the pot that burns the most value. A fable right after another one usually burns less: the pot the last fire spent, and the coin's own slice, have had less time to unlock, though another pot may still be full.
Each coin's fables fire one at a time, oldest first. Yours fires once the ones ahead of it have fired and the vault's unlocked slice is worth at least 0.00002 ETH and 3 times the gas. Fables never expire, so a queued fable waits for new fees however long that takes. The site marks it fired when its once-a-minute indexer sees the burn.
No. Each fable id can fire its coin's vault only once, and the vault records it on chain. Likes and replies never fire anything, and a fable only fires the coin it is posted under.
To the dead wallet 0x…dEaD, straight from the pool. Total supply stays 1,000,000,000, explorers show the dead wallet's balance as burned, and each coin's burned() view returns it.
Not one burn. A single burn can move its pool's price by at most one pool fee, while buying just before it and selling right after costs two fees, so that trade always loses. If the limit cuts a burn short, the rest carries into the next one, and the bot spreads big burns across a coin's pools. Several big burns in a row can still reward someone who already holds through them; that is simply what a buy and burn does for holders.
Fables stay queued and fire when it comes back; it checks the chain first so nothing burns twice. Meanwhile any coin can still burn through its burn button: six hours after the coin's last successful burn (or its launch), anyone can press it, on the coin's page here or by calling burnAll(collectFirst) on the coin's burn vault through a block explorer. One press spends up to 25% of every pot, under the usual price limits, and the presser gets 0.1% of what it spends.
It is 0.1% of what each pot of your press actually spent, paid in that pot's own currency: ETH from the ETH pot, a pair token from that token's pot, and the coin from the coin's own slice. If your wallet can't receive one of them (a contract that refuses ETH, say), that part simply isn't paid, and the pot still burns.
It can. Six hours after its last burn of any kind, anyone may press its burn button, and the bot presses it too when the press is worth its gas. A press still spends only what has unlocked in each pot.
No. The vault has no owner and no withdraw. The only value that leaves it other than into a burn is a gas refund on fable fires (1.25 times the gas, at most 10% of what the fire spent, sent to the shared gas tank or, for non-ETH assets, to the platform) and the burn button's 0.1% to whoever presses it.
Yes. Hiding removes it from the public site only; it stays in the bot's queue and still counts in the place in line. Only the site's owner can hide a fable: authors can't delete or hide their own.
Every coin's round closes at 00:00 UTC. The count uses whatever is in your voting box at 23:59:59 UTC. The bot counts right after midnight, and from 02:00 UTC anyone can.
Deposit at least 10,000 coins into the coin's voting box. You can withdraw everything at any time, even if the bot is offline. A partial withdrawal can't leave you with less than 10,000 in the box.
No. Your split stands and repeats every round until you change it, and coins you add later count towards it automatically. If you withdraw everything your vote is erased, so vote again after you deposit.
Yes: across up to 5 pools, in whole percentages that add up to exactly 100. Each pool can be an existing pool or a new pool against any asset on the launch menu.
It gets nothing that night. The pools with at least 5% of the eligible votes split the whole pot in proportion to their votes. If no pool reaches 5%, the pot keeps the money for a later count.
The pot is split equally across the coin's existing pools that the Safe hasn't retired.
No. The pot has no payout path. Its coins can only go into locked liquidity. Its ETH and pair coins can only buy the coin, buy or sell a pair coin, or go into locked liquidity.
Builds pause in some cases, and limits make them gradual. The contract refuses pair-asset adds and new pools while the coin sits exactly at its launch price, and the bot waits until it is two fees above it. An add that puts the pair asset into a pool is refused while that pool is too far from fair: about 7.5% at a 1% coin fee, wider for higher fees (about 19.2% at 6%). Each build is capped at 0.25 ETH and 10% of the pool, and a new pool opens at no more than 1% of the reference pool's coin side. Whatever isn't built by the next count goes back into the pot.
After $FABLE launches, the Safe points the guarded v4 feed at $FABLE's ETH pool and queues the listing, each with 48 hours' notice. Once the bot's samples warm the feed and the depth floor holds, a bot key activates it, and new coins can launch with a $FABLE pool. The planned production floor is 5 ETH. Holder votes for $FABLE pools stay off until a v4-capable pot swapper is switched in (at least 48 hours after the Safe proposes it) and the Safe un-retires $FABLE (also a 48-hour change). The plan.
No. Every position is owned by the LiquidityLocker, which has no code that removes, decreases or transfers liquidity, and the hook lets only the locker add liquidity. This holds for the creator, the platform and the Safe alike.
No. It is a stock OpenZeppelin ERC-20 with a fixed 1,000,000,000 supply (18 decimals) minted once. It has no owner, mint, pause, blacklist or transfer tax, and no custom transfer logic. The only fee is the swap fee in the coin's own pools.
A launch pool opens holding only the coin, priced from the launch price upwards, so there is no liquidity below it. The hook reverts any swap that would push the price under that floor. The buy router's spread sell stops each pool at its floor and hands back what that pool could not take.
Every change goes through FableGovernor and waits 48 hours in public, where a separate veto wallet can cancel it: restoring a pair asset for pot funding, changing price feeds and risk limits, moving the pots to a new swapper, swapping in a whole new launch menu, adding bot keys, or acting as a keeper in a pot. At once, it can only stop things: retire a pair asset, drop a price feed, pause the signed price source, remove a bot key, pause new launches, cancel a Fable Drop winners list within its first hour, or switch the pots back to their built-in swapper. It can't change your coin's fees, move locked liquidity, withdraw from vaults, pots or voting deposits, or pause trading. Safety and admin.
15 · Reference
Read this before you launch, trade, vote or post. Nothing on this site is financial advice, and you are responsible for what you sign.
Market risk
Coins launched here are volatile and can lose all their value. Buy and burn and pot liquidity do not guarantee any price: each burn spends only the slice of fees that has unlocked, and the pot builds gradually.
Selling at the launch floor
A launch pool has no liquidity below its launch price, and the hook refuses any swap that would take it there. When a coin trades near its launch price, its launch pools can take little or nothing of a sell; only mesh pools, if it has any, have liquidity below it.
Smart-contract risk
Fable's contracts are fixed code that nobody can upgrade, so a bug cannot be patched in place. Funds the contracts hold, such as fees waiting in pools, vaults and pots, depend on that code working as written.
Off-chain services
Fables depend on Privy sign-in, the fable service and the bot. If they stop, fables wait in the queue; six hours after a coin's last successful burn, anyone can press its burn button. Burn status on this site comes from an indexer that runs once a minute, 20 blocks behind the chain, so it can lag.
Admin powers
The Safe, a 3-of-3 multisig, controls every setting through FableGovernor. Each change waits 48 hours in public before it can take effect: settings for future launches, listing or restoring pair assets, tuning price sources, adding bot keys, a new pot swapper or a whole new launch menu, where the platform's other 30% goes, and moving the rewards pool. Only emergency stops apply at once, and they only stop things: pausing new launches, retiring or removing a pair asset, removing a bot key, dropping a price feed or pausing the signed one, cancelling a Fable Drop winners list within its first hour, and switching the pots back to their built-in swapper. A separate veto wallet can cancel any waiting change or freeze the Safe (the Safe can still pull its stops), and together with two of the Safe's owners it can move control to a new Safe after 48 hours; the Safe can replace a lone veto with a 7-day swap. The veto can never propose a change or move money. Neither can move locked liquidity, withdraw from vaults, pots or voting deposits, change a launched coin's fees, or pause trading. Registered bot keys are trusted for each fable's id and time; a bad key can burn at a poor moment, not at all, or post a wrong Fable Drop winners list, which pays nothing for its first hour, so the Safe or the veto wallet can cancel it.
Pair assets and price feeds
A pool against ETH, USDG, a tokenized stock or another asset also carries that asset's risk: if the pair asset falls or stops trading, so does that side of the pool. Guarded price feeds fail closed, so a launch can revert or a pot build can pause while a price is unsettled.
Settings that can differ
Figures this page calls defaults (the launch price, pool counts, the supply split and the engine split) can be changed by the Safe for future launches, each with 48 hours' notice. A coin always keeps the settings it launched with. Moderation of hidden fables is not final.
Your responsibility
Check every address and amount your wallet shows before you sign; your wallet signs every transaction directly against the contracts. Make sure using Fable is legal where you live. Nothing here is advice.
One transaction: the launch fee plus your first buy. Your coin opens with locked liquidity, its own buy and burn vault and a holders' pot.