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, and bundle buys/sells/dumps on a graduated token refuse cleanly (token graduated — v4 route not ported) instead of guessing. Pre-graduation everything is exact.

The tab is the process

The engine runs in the page. The funding window and the auto-buy loop execute only while the tab is open — close it and they stop. The funding plan is persisted (jb:fundplan) and resumes on the next open, re-spreading overdue sends; auto-buy restarts skip wallets that already bought. For a long unattended funding window, the standalone Python engine in bundler/ is the better tool.

Public RPC rate limits

All reads and broadcasts go through public RPC endpoints (Robinhood, plus the funding source chain). Bursts get rate-limited — the app retries with backoff and the funding executor re-quotes before each send, but a congested RPC means slower polling, not a broken state.

Frontend gating

The vault-password gate is client-side on a static site — it is key management, not access control. What it protects is real (AES-GCM-256 on your keys); what it does not do is restrict who can read the page.

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.