FAQ

Is this financial advice?

No. Everything on the terminal is a statistic derived from historical and live market data. Pairs can and do break; stops and timeouts exist because mean reversion is a tendency, not a law.

Where do the pair signals come from?

Pairs are screened and fitted daily by a statistical pipeline that tests for a stable long-run relationship between coin pairs, then publishes the eligible ones with their fitted parameters and band levels. The terminal consumes that daily plan and computes live z-scores against it in the browser.

Why do the numbers change once a day?

By design. The statistics (β, μ, σ, bands) are refit and locked daily so that every live reading has a fixed, stated reference. See Z-Scores & Bands.

Why is a pair suspended?

Its most recent daily fit is missing a required statistic. Rather than display a number computed from mismatched inputs, the terminal suspends the pair until the next clean fit.

Can a z-score be extreme, like ±8σ?

Yes — a genuinely blown-out spread reads exactly that way. The daily screen filters on statistical eligibility, not on the current z level, so pairs can appear already deep past their bands.

What if a pair I hold disappears from the daily plan?

Pairs can and do leave the daily plan — a pair drops out when it fails the pipeline's statistical gates or loses its threshold solution at a refit. Nothing happens to your money: an open position was locked at entry, so it keeps being monitored and priced on that locked recipe, armed exits still fire, and the pair's page keeps working in a reduced state that says exactly what it's pricing. A watch on a dropped pair has nothing locked to price — watches float with the daily plan — so the page shows the watch honestly without a chart until you remove it or the pair returns.

Can I watch many pairs at once?

Yes. On the Pairs page, expand the book rail into the screener, check the pairs you want, and add them as one action — one request, one refresh. New watches take the suggested settings; a pair you already watch is skipped and keeps its custom settings, because a bulk add never overwrites an existing watch. Batches cap at 50 per request, and a batch that would pass your watchlist ceiling is refused with the numbers stated rather than partially applied. Bulk adds are watches only — arming is always per pair, on its own ticket.

How do I stop watching pairs?

The same way you started, wherever the watch lives: per-variant remove on the pair page's Track tab, a worded remove on every watching row of the Book page (dormant rows included), or check any number of rows — on the Book page or in the screener, with a select-all on the group head — and stop watching clears them as one request. Skips are named per item, never silent: an armed watch is excluded by design (a commitment stands down from its own pair page, not a bulk sweep), and a watch whose entry is filling settles first.

Why can't I arm a pair that shares a coin with one I already hold?

By design: one coin, one pair. Hyperliquid nets each coin into a single account position, so two hedge-weighted pairs sharing a coin would merge into one number that cannot be honestly attributed back to either pair. The terminal refuses to create that state rather than display a guess — conflicting pairs are greyed with the owning pair named, and they unlock the moment it closes. The coin itself stays yours: you can hold it outright, trade it yourself, and resize your pair freely — only a second pair through the same coin is refused. When browsing for new pairs, the free legs chip on the screener hides pairs that share a coin with your open positions or armed entries, so everything left is clear of this rule. See Pairs Trading 101.

What happens if I trade a coin one of my pairs holds?

Nothing is blocked — the coin is yours. But the venue nets each coin into one position, so after a personal trade the venue total is the pair's leg plus your personal residual, and "you trimmed the pair" vs "you traded personally" is genuinely unknowable. The desk tracks the pair by its own fill ledger and never guesses: your row shows a neutral residual chip (venue holds less / holds more / points against the pair), exits size only up to the venue holding that points the pair's way, and a row is closed for you only when the venue provably holds nothing in a leg — marked liquidated when the venue's fill flag confirms a liquidation, manual_venue otherwise.

Can I set my own profit target or stop?

Yes. When you arm or update an exit plan, the ticket pre-fills the model's entry-frozen terms, but the profit target, stop, and give-up time are yours to change — typed as a distance from your entry in % (or σ), with the dollar amount at your actual size shown beside it. The plan then carries an amber custom exit chip and keeps the model's numbers next to yours; blanking a field or typing the suggested value back restores the model's terms. The guard rails are named, never silent: a stop cannot sit on the profitable side of your entry or closer than a small floor, a custom target still waits out the strategy's minimum hold, and a stop looser than the model's is flagged as more room — and more risk — than the model planned. Changes reach the engine within about five minutes, and the ticket says so before you confirm.

Can I add to or reduce an open position?

Yes — from the pair page's +ADD and −REDUCE buttons. An add scales the position up on the recipe locked at entry (one position, one recipe — an add never picks up today's refit) and climbs the same permission ladder and caps as an entry. A reduce sheds a fraction (25/50/75% chips, or a leg-A dollar amount) with reduce-only clips — it can shrink the position but never flip it; reducing to flat closes it. Every scale fill is journaled, so the entry becomes the journal-weighted average and the Book row's expanded view shows the full fill history. Two things never change on a scale: the exit terms and the clocks — target, stop and timeout still run from the original open. One working order per position at a time: while a scale is settling the row shows SCALING and exits hold.

Does the terminal trade for me?

The engine works orders you arm — it never decides to trade. Eleven algos have live engines today: TWAP (native), Adaptive Market, Now (IOC), TWAP+, Iceberg, Chase, Scale / Ladder, Stop / Take (native), Bracket (TP + SL), PairGlide, and Autospreader (the pair algos arm from the pair ticket). Arming requires a connected wallet that has signed in and enabled trading — an order-only agent your wallet approves on Hyperliquid itself, plus a builder-fee cap — and every armed order's fee is disclosed on the ticket before you sign anything. Armed watches and armed exits fire server-side: the engine monitors the bands and places the trade through your agent even while your browser is closed. The rest of the Launcher catalogue is a preview: configure it, see the schedule on the chart, price it against the live book, with the gate stated on the Arm button itself.

Do you hold my funds?

Never. pairpetuals.com is a data and analysis terminal: it constructs orders, your wallet authorizes them, and Hyperliquid executes them. Matching, execution, settlement, and custody all occur on the Hyperliquid protocol — we never hold funds and never see wallet keys. The agent your wallet approves can only place orders; it cannot withdraw or transfer, expires on its own, and is revocable at any time — see the next answer. See Legal & Risk.

How do I revoke the trading key?

In the account rail on any trading page, the Trading · agent key card has a Revoke key button — the first click asks you to confirm, the second revokes. It takes effect on this site at once: the engine stops signing with the key within seconds, armed watches and armed exit plans stop firing, and the key is never reused — enabling trading again mints a fresh one. Be deliberate if you hold open positions: an armed exit plan is worked through this key, so after revoking, your target, stop, and timeout no longer fire — manage or close those positions yourself. The approval recorded on Hyperliquid itself is removed from Hyperliquid's own API settings page, and it expires on its own within 180 days regardless. The builder-fee cap is a separate approval, also revocable through Hyperliquid.

Why can't I connect my wallet?

Wallet connection isn't offered in some regions — the connect window names the detected country when that applies. Everything else stays open: live markets, pairs, wallet lookups, and these docs all work without connecting. The list of restricted jurisdictions is in the Terms of Use, §3. If your region is detected wrongly (a VPN or corporate network can do that), the check re-runs each time you open the connect window from an ordinary connection.

What are the "tape reads"?

Heuristics over public prints — suspected TWAPs, sweeps, block prints, aggressor flips, funding flips, OI jumps. They are always worded as "suspected" because that is what they are: inferences from public data, not facts. See The Trade Cockpit.

Why do some cost numbers say "> visible book"?

The exchange feed shows a bounded number of book levels. When a clip you're pricing exceeds what's visible, the terminal flags it instead of extrapolating a cost it cannot know. Stale or missing data is always labeled — never dressed up as live.

Is my data shared with the exchange?

Browsing requires no account. The terminal reads public Hyperliquid market data over its published API and WebSocket feeds.