🏭 TOKEN FACTORY

Tokens launched through the LUNC Dev Studio Token Factory get their market here. Create a token in the factory, open its first pool, and it appears in this market — created on the factory → trading on the DEX. This is the home market every factory token is shown in from day one. Live: trading is open right here — connect your wallet, pick a pair, and trade. The factory never promises liquidity or returns; a pool is only worth what its market puts in it.

Markets — live on-chain

Every pool on the DEX factory contracts, read live from the chain. The badge is Dev Shield's pool verdict: VERIFIED CODE means the contract code and admin match the verified record right now. Tap a market to load it into the trade panel. means the contract code and admin match the verified record right now. Tap a market to load it into the trade panel.

⭐ Main pools

The pools that matter first: every pool with at least $500 of live liquidity, biggest first — the deepest factory pools this DEX trades, plus the main Terraswap and Terraport pools as live market data. The pool featured at the top of this page is the deepest LUNC pool in this market.

My positions

Your balances of the pool tokens and your LP positions, read live from the chain when wallet access is available.

🎛️ The Control Room — Emergency Stop & Recall DEMO

This is the control room that ships with the new 2.0 contracts — the room the admin works from. The three controls the owner holds are the centerpiece, shown as they will appear:

Freezes swaps on the pool instantly. Funds stay in the contracts — trading just stops while things get checked.

Sweeps the funds held inside the contracts to the pre-set safe wallet and shuts the pool down until it has been analyzed.

Kills a scheduled dangerous action — a contract migration or an admin change — while it sits in its recall window.

How to read this panel: these show the new contract design — they cannot act on any live pool. Every real control is owner-only and takes the owner's own signature. Settled trades in user wallets stay final — recall protects funds held inside the contracts.

🔧 How a repair works

When something goes wrong, this is the playbook — in order:

• ① Detect — Dev Shield and the operator monitor watch every pool around the clock. If a pool's contract code or admin changes, or an attack pattern appears, the alarm fires straight away.
• ② Pause — one tap of ⏸ Pause Trading freezes swaps on the pool. The funds stay where they are; trading just stops while things get checked.
• ③ Recall — if the threat is real, 🛑 Emergency Recall sweeps the funds held inside the contracts to the pre-set safe wallet, out of harm's way, and the pool shuts down.
• ④ Fix — with the funds safe, the problem gets repaired: contract code or admin restored, keys rotated. And if anyone has scheduled a dangerous change, it is still sitting in its recall window, where ↩️ Cancel Pending Action kills it before it can ever run.
• ⑤ Resume — trading restarts only when the pool verifies against the chain record again. If it does not verify, it stays closed.

On the current contracts there is no playbook — no pause, no recall, nothing to press. That is the gap the new contract design closes.

🔑 Who can press them

• The owner alone. Only the contract owner's wallet can pause, recall, or cancel. Nobody else — not this website, not a server, not a bot.
• Multi-sig where feasible — the owner can be a multi-sig wallet, so no single person and no single key can act alone.
• One tap of the owner's, from their own wallet — every action is signed by the owner in their own wallet app. No server ever holds keys, and nothing anywhere can press these controls for them.
• Alerts fire both times it matters — when a dangerous action is scheduled, and again before its recall window closes, the owners are pinged. A stolen key cannot finish a dangerous change in silence.

📡 Live monitoring

The operator monitor is part of the design: every pool's trades, code, and admin, checked continuously against the verified record — the detection half of the playbook above.

🛡️ Dev Shield — checked before every trade

Shield is an automated security engine — a fixed set of on-chain checks that run in your browser before a trade can be signed. It is not a person and it does not guess: every line in its verdict comes from a check that just ran against the live chain.

• Pool code & admin — the pair contract's code and admin must match the verified record. Any change = the pool is blocked automatically. (The October drains began with contract code changes.)
• Token admin — whether the token's admin can still change its contract. An admin renounced to the burn address means nobody can change it — the safer state — and Shield shows the state plainly, either way.
• Token minter — whether new tokens can still be minted, and who holds that power.
• Sell test — before you buy, the pool is asked to price a sale of the token you would receive. If the sell side fails, the trade is blocked — a token you cannot sell back never gets your signature.
• Price impact — how much your own trade moves the price. Over 5% is flagged; over 15% is flagged red.
• Your permissions — when your wallet is connected, Shield lists the permissions (authz grants) your wallet has given away. A grant with no expiry is flagged red — the kind of open door the October attack walked through. The full wallet check lives in the Wallet security watch, right under the header.

What Shield does not check — stated plainly: it cannot undo or reverse a trade that has already settled on-chain (no tool can, on any non-custodial pool), and it does not judge a token's team, promises, or off-chain claims — it reads contracts, not reputations. If a pool ever trips the wire, the response is to alert the operator, banner the pool here, and trace any moved funds to the exchanges.

🛑 Emergency Stop & Recall

The brake the old contracts never had, built into the new 2.0 contracts and held by the owner alone:

• Pause — one tap freezes trading on a pool while things get checked.
• Recall — funds held inside the contracts sweep to a pre-set safe wallet, out of harm's way, and the pool shuts down until it has been analyzed.
• Recall windows — dangerous changes (migrations, admin changes) wait 24 hours standard or 7 days critical before they can run, with alerts when one is scheduled and again before the window closes.

The full control room — the three controls, the recall windows, and the repair playbook — lives in the Admin tab. Shown there as a demonstration: the controls ship with the new 2.0 contracts.

📡 Watched around the clock

• The operator watchtower — every pool's trades, contract code, and admin, checked continuously against the verified record. A pool whose code or admin changes glows red within minutes, not after a drain.
• Page tamper watch — this page's own bytes are re-checked against a sealed record every 10 minutes. If the page is ever swapped for a fake copy — the way a fake wallet popup would try to reach you — the change gets flagged.
• Dev Shield alerts — the moment the watch finds something, an alert goes out straight away, and every high-severity alert carries what happened and how to fix or block it. Watching is only worth anything if somebody hears about it straight away.

🔑 No keys, no custody

• This page holds no keys and no funds. There is no operator key sitting on a server for anyone to steal — the October breach began with a stolen key; here there is nothing to steal.
• Signing happens only inside your own wallet. This page prepares a trade and shows you exactly what it is; your wallet app is the only place a signature can ever happen.
• Your seed phrase must never be shared — not with a developer, not in a chat, not typed into any website. This page never asks for it. Anyone who does is a scammer.