Limitations

The honest list — everything the product does not do, so nothing surprises you at the wrong moment.

Launch whitelist

Pons public launching is gated by canLaunch(deployer). If your wallet is not whitelisted, launch is unavailable — the app tells you this before you fund anything, not after. Solo mode has the same restriction; there is no workaround we will pretend exists.

Lock is approval staging

Step 8 stages sell approvals for instant exits. It is not an LP lock, supply lock, or timelock — Pons exposes no such primitive today. The UI and docs say staging, not locking.

V4 quoter

Robinhood has no deployed V4Quoter — post-graduation price reads are approximations, flagged in pons.degraded in /api/state.

Standalone scope

Without the engine there are no bundle wallets, no vault, no relay distribution, no auto-buy. Standalone gives real market data and real wallet trades — but the product's bundle operations are engine-only by design, because keys never touch the site.

Frontend gating

The connect-wallet + signature gate is client-side on a static site. It shapes the UX; it is not server-enforced access control. The security boundary is the local vault, which is real.

Image persistence

The launch wizard's image upload is a local preview — Pons has no public upload endpoint. Paste an image URL to put it on-chain in the logo field; a local file stays on your machine (and still shows in Live).

Relay distribution timing

Transfer confirmations depend on relay.link + source-chain congestion. The window is a target, not a guarantee — plans pad ~8% for confirmation time, and entries that error are retried, which can extend the window.