Reference
Release notes
20 October 2026: how a launch reaches its pool
The guides now say it the same way everywhere: a Signal v4 launch and a Classic launch go straight into their pool, with no curve and no migration. Only a bonding-curve launch opens its pool later, at the curve's target. Changed: launch a token, Signal v4 launches, trade a token, the glossary and the Build with Signal index.
12 October 2026: Signal v4 and the site as it is today
New launches on Signal are Signal v4 pools, and the guides now start there.
For integrators
- Signal v4 pools: how the pools work and the eight things an integration must respect.
- Deployments for release 4.2 and the two earlier releases with pools, with ABIs, a deployment record and a provenance record.
- Discovery, fees and rules, quote and trade, events and accounting, and a read-only example.
- The public data API page is rewritten: the v4 fields of a token record, the
suspectandlegmarks on trades, the safety endpoint, rate limits and error shapes. Corrected from the previous edition: a v4poolis a pool id, not an address;/api/livecarries the trades themselves and answers with a redirect first;/api/born?every=1pages every launch. - A page on the DexScreener adapter.
For users
- Launch a token and Signal v4 launches: the three-field launch and every rule behind it.
- Trade a token rewritten around the ticket and its cost line.
- New guides: your wallet, token safety, signals and the leaderboard, Echo, other chains and Swap, the Desk and Classic, rewards, referrals and relief.
- Security and permissions states who can change what on Signal v4, and that no independent audit of the v4 contracts has been published.
What was observed
Contract state was read at HyperEVM block 48,348,140 on 12 October 2026: release 4.2 open with 19 pools, release 4.1 closed with 11, release 2 closed with 9; 32 pair assets admitted on 4.2. Every function selector of each published v4 ABI was found in the code at its listed address. One buy was reconciled log by log against its receipt. Site behaviour was read from the application as deployed that day.
New bonding-curve launches are not offered at present. The curve and Classic pages are kept for the tokens that exist.
21 September 2026 — Public documentation baseline
This edition separates Classic launches, standard bonding curves, spot rewards and perp rewards. It includes:
- Standard 75/25 Ramses and Project X Curve deployments and compiled ABIs.
- Quote units, spender identity, two-leg HYPE protection and refund accounting.
- Event indexing, phase changes and deferred graduation.
- HYBR pairing and HYBR holder rewards through the separate Hybra Classic route.
- Market-dependent long/short profiles at 1×, 3× and 5× target exposure.
- Fee-hour attribution, batch minimums, unit ownership, settlement and liquidation risks.
- Public API coverage and its freshness and completeness limits.
Live configuration was observed on 21 September 2026. A documentation review date is not a promise that all markets, routes or profiles remain available. Always read the exact deployment and token terms.
The follow-up review matched all 72 standard 75/25 deployment records to live configuration. The market roster showed all six long/short profiles for xyz:NVDA on Ramses Curve, with no Classic companion for those rows. The guides now state that boundary, the closed-fee-hour requirement for holder allocation and the conditional third-party cash-push bounty. Read live configuration, the market roster and strategy observations for current availability and recorded terms.
Older 80/20 Curve tokens retain their original contracts. The reviewed executable example and ABI bundle intentionally cover the standard generation 2 spot routes; future adapters should be added with their own identity records and checks.
The source archive and its checksums are recorded in artifact provenance. Changes to contracts, fee interpretation or route coverage require a fresh review, not just a wording update.