Purpose and scope
IGNIS combines token creation, bonding-curve discovery, direct decentralized-exchange trading, market analytics, public discussions, trader profiles, private messaging, and an optional browser-local Fast Wallet in one Flare interface. It is designed to reduce the number of disconnected tools needed to launch a community and follow its market.
IGNIS is non-custodial at the website layer. The interface prepares transactions, but the connected wallet decides whether to sign them. Smart contracts and external DEX contracts—not the website database—control token supply, curve reserves, graduation, locked liquidity, and claimable fee balances.
System architecture and trust boundaries
The factory controls launch configuration and lifecycle. Creator-rights state controls the current controller and fee recipient. FeeEscrow controls cumulative claims. Moderation can change interface visibility, but cannot move user funds, edit economics, unlock liquidity, or disable direct contract access.
The production website indexes both V1 and Gen2 so historical launches remain usable. Only new creation writes route to the active Gen2 factory at 0x85837bC0…3FC7141D. The legacy V1 factory remains part of the read path and is not migrated or rewritten.
Launch and graduation lifecycle
The creator pins public metadata, pays the configured launch fee, and optionally performs a capped paid creator buy.
A fixed-supply token trades against its dedicated WFLR bonding curve with explicit quote, slippage, deadline, and average-price protections.
Reaching the snapshotted threshold attempts permissionless SparkDEX V4 graduation. A failed external pool call leaves a retryable Ready state.
The canonical pool becomes the trading venue and the resulting position NFT remains permanently held by the token's immutable Gen2 reward vault.
The current production snapshot uses a fixed supply of one billion tokens, a 100 FLR launch fee, and a $6,100 graduation target. The normal curve fee is 1%. A separate anti-snipe surcharge starts at 98% and decays over the first five seconds, making the total opening fee 99% before returning to the normal 1%.
Economics, fees, and custody
Protocol trading fees are divided 70% to the current creator-rights fee recipient and 30% to the protocol treasury. The split applies through cumulative FeeEscrow credits, so a rights handover changes future entitlement without rewriting past claims.
- Curve fees are credited in WFLR.
- Graduated pool synchronization may credit WFLR and the launch token.
- Each Gen2 vault can request only distributor WFLR reported as claimable to that vault; it cannot make arbitrary calls or withdraw its LP NFT.
- Anyone may trigger collection, but the caller receives no bounty and cannot redirect the proceeds.
- Creator and treasury claims remain separate cumulative liabilities in FeeEscrow.
Markets, charts, and trade execution
The Markets terminal catalogs supported Flare pools and displays confirmed pool-specific prices, rolling candles, activity, attributed traders, wallet overlays, average buy and sell lines, current token holdings, market condition evidence, and verified route details.
Execution is intentionally pool-specific. IGNIS trades the exact verified pool selected by the user through its supported router adapter. It does not claim to be a universal best-route aggregator, split an order across venues, or silently substitute another pool. This keeps the displayed liquidity, chart, approval target, quote, and submitted route aligned.
Routes remain unavailable until contract identity, pool tokens, router, quote path, and supported adapter checks pass. A visible market is not automatically an executable market.
Data, indexing, and rolling history
Flare events and contract reads are authoritative. Neon stores a materialized index so every visitor shares the same launch catalog, activity stream, market search, rankings, and chart rollups. Production API reads do not create schemas or perform historical backfills.
Launches, IGNIS trades, transfers, rights, profiles, private messages, watchlists, sessions, fees, and claims are outside the rebuildable Markets-history retention process. Heavy history work has its own lease, time budget, page limits, growth guard, and ten-minute schedule; core IGNIS activity continues independently every minute.
Wallet, Fast Wallet, and social security
Connected-wallet requests remain visible in the user's wallet. Private interface actions use scoped signatures, same-origin checks, bounded payloads, authenticated sessions, and server-side authorization. Direct messages are private to the participants at the application layer, but are not end-to-end encrypted.
The optional Fast Wallet is a browser-local hot wallet. Its key is encrypted locally and never uploaded to IGNIS. Backup and restore are user-controlled. Ordinary sessions auto-lock after genuine inactivity, while an explicitly armed Copy Session has a visible expiry, per-trade cap, total budget, slippage ceiling, failure cutoff, and immediate stop. It is for bounded trading funds, not long-term custody.
Operations, monitoring, and recovery
Core activity, current Markets indexing, and historical Markets work run as separately leased jobs so expensive chart history cannot hold up launches, current trades, profiles, forums, or claims. Server RPC calls fail over across independent providers. Indexer health exposes the confirmed head, indexed block, lag, latest success, and latest failure.
Application rate limits reduce accidental abuse per runtime instance. Vercel WAF rules are the cross-instance enforcement layer and must exclude authenticated cron requests. Operational alerts report delayed core indexing, market worker failures, and storage-guard transitions when a webhook is configured.
Database recovery uses Neon snapshots or branches. A restore drill must target a separate temporary branch/database first. Production recovery must never truncate protected user or protocol tables merely to recover rebuildable chart capacity.
Current validation status
Automated release validation covers lint, TypeScript, production compilation, contract-address invariants, launch-call construction, indexing, chart retention, wallet security, permissions, and API protection. The read-only mainnet gate targets the active Gen2 factory and simulates zero-buy and paid creator-buy launches without broadcasting a transaction.
Owner-operated acceptance has already covered two Gen2 launches, curve buys and sells, direct Markets buys and sells across tested DEX adapters, Fast Wallet execution and recovery, profiles, forums, direct messages, and watchlists. A separate $3 Gen2 canary exercised the graduation path; these completed tests are not treated as unfinished launch blockers.
Known limitations and external dependencies
- IGNIS does not guarantee profit, token quality, continuous liquidity, or uninterrupted third-party infrastructure.
- Market history is intentionally rolling, not permanent full-chain storage.
- Direct verified routes are supported; universal multihop, route splitting, and exhaustive token-tax simulation are not part of this release.
- External metadata providers may omit an image. IGNIS can inherit a verified image already known for the same token address, but never treats a matching ticker as identity.
- SparkDEX controls distributor eligibility and allocation. The remaining live acceptance unknown is whether the tiny graduated canary LP position receives any FTSO-related WFLR allocation; IGNIS can collect it only after SparkDEX reports WFLR claimable to the vault.
It is a technical system overview, not a promise of returns, an audit certificate, or legal advice. Contract state and verified source remain authoritative where this document and live state differ.