Docs

01 Launch simulator

A plan goes in. What it costs and how it behaves comes out, with a source on every line.

You set supply, allocations, the first pool, its fee and range. You get a cost table, the impact a buy has, and notes on the configuration. The plan is held in the page’s link, so sharing the link shares the plan. You can also save it in your browser.

Each line of the cost table has one of these sources:

• Live estimate. eth_estimateGas against the real contract, from an empty address, for pool creation and token creation. Nothing is sent.
• Recent transactions. Adding liquidity needs tokens and approvals that an empty address lacks, so these lines use the median gas of the last few real transactions of that kind.
• Our tests. The optional line for publishing a plan comes from this project’s contract tests.
• Contract read. The launch factory’s fee, read from the factory.

Notes never add up to a score. A configuration with no notes is not thereby a good plan.

02 Price impact

Two numbers, because they differ: how far the price moves, and what the trader pays.

Constant product for v2-style pairs, and tick-by-tick concentrated liquidity for v3 and v4, with the contracts’ own rounding. For a real pool, it reads reserves, or price, liquidity and nearby ticks, then computes in your browser. Outputs were compared to the wei with the chain’s own quoters on a fork, and those captured vectors are in the repository’s tests.

It reports two numbers because they differ. The price move is how far the pool’s price went. The cost to the trader is how much less they received than the price before the trade would give, fee included.

Limits: a trade that walks past the ticks read is flagged as a guide. Hooks and transfer taxes are not simulated. Pools from other factories are treated as v2 or v3 style and say so.

03 Pool monitor

It decides what an address is from how the contract answers, and never guesses.

Paste a pool, a v4 pool id or a token. It decides what it is from how the contract answers, and never guesses. A token lists its pools: Uniswap v2 and v3 pairs against WETH and USDG and the Pons factory from chain, and others, including v4, from GeckoTerminal as a second source that it labels.

Recent swaps are recent only: the page reads backward from the newest block and says how far it reached. Largest holders use the explorer’s list when it answers. Otherwise they come from wallets seen in recent Transfer events, and the page says that is not a full list and how far back it read.

A ticker is not an identity on this chain. Official stock tokens are recognised from Robinhood’s token beacon in their code, and many others borrow the same names.

04 Launch record

Five stages, in the open. It holds no funds and deploys no token.

FluqoLaunchBook is a contract with five stages: draft, reviewed, announced, launched and withdrawn. It holds no funds, deploys no token, and has no owner, fee, pause or upgrade. The contract is not deployed yet; until it is, the record runs as practice in your browser.

• History. A plan’s versions, attestations, stages and bindings are read in full from the contract’s own views, so the age of a plan does not limit them. Plan vs actual reads current chain state, not past events.
• Versions. Each change is a new numbered version with its hash and link. Old ones stay readable.
• Attestation. Any wallet other than the creator and editors can attest one exact version, or only a named panel if the creator set one. A new version starts the count over.
• Binding. After launch, the creator binds the token and pool. It is proved when the creator’s wallet is what the token’s owner() answers, or when the deployer of a token made with CREATE signs for it. Otherwise it is labelled unproved, and can be proved later. A proved binding is final.
• Launchpads. Tokens made by a launch factory have no owner() for the creator and no deployer wallet of theirs, so they read as unproved.

05 Plan vs actual

The plan on one side, the chain on the other, one line at a time.

Compares the plan with chain state, per line: name, symbol, decimals, supply, owner, a scan for a mint function, balances of the wallets the plan names, pool type and fee, and what the pool holds now. A line says match, differs or unknown. Pool amounts are read now, so a difference after the first trade is expected. A share in a lock contract sits at that contract, so name the lock in the plan.

06 What is planned

Planned means not built.

• Launching a token through Fluqo itself, on a test network first. Not built.
• Advanced monitoring, such as alerts. Not built.
• Connecting other networks. Not built.
• $FLUQO for these services, if they exist and the need proves real. A paid service does not automatically need its own token.

07 Why one network

One network first. Connecting others comes last.

Promising five networks from the start means taking on bridges, contract security across chains and operations far larger than a planning tool. So Fluqo does one network first. Connecting others is the last step of the order: simulator, launching on a test network, pool monitoring, then other networks, with fee detail and clear transaction status. It may change, and nothing here depends on it.

08 Risks and questions

What a number here can and cannot tell you.