2. Commands

This section explains the command surface by workflow, with practical examples so you can set up alerts fast and avoid common mistakes.

Current limits

  • Addresses: 10
  • Funding alerts: 10
  • Price alerts: 20
  • Jump alerts: 20
  • External liquidation alerts: 10
  • TWAP alerts: 10
  • Net TWAP alerts: 10
  • Hyperlend alerts: 20
  • HLP alert: 1
  • Rysk subscriptions: 10
  • Rysk HYPE expiry alert: 1 threshold per chat

Basic bot commands

Use these first to initialize, learn the surface, and check your setup.

Commands:

  • /start
  • /help
  • /outcomes
  • /list

Example behavior:

  • /start gives onboarding and quick setup hints.
  • /help shows the main command overview, ordered by the most useful workflows.
  • /outcomes shows currently open HIP-4 outcomes on mainnet. Tap any outcome to open its contracts and submit Buy/Sell calls.
  • /list shows your active configuration and alert counters.

Wallet movement tracking

This is the main wallet feature. It tracks position movements, actual spot/HIP-4 buys and sells, TWAP starts/finishes, token transfers in both directions, staking/unstaking, and liquidation risk.

Example behavior:

  • /track 0x1234...abcd Juan tracks that address with label Juan.
  • /track 0x1234...abcd 0xabcd...5678 Juan tracks multiple addresses under the same label/entity.
  • /entity_create MarketMakerX creates an entity.
  • /track 0x1234...abcd MarketMakerX tracks the address under that entity if the entity exists.
  • Alerts are aggregated by address/entity in a 60-minute window instead of sending every fill.
  • If a tracked wallet gets close to liquidation, the bot alerts below 1%, again below 0.5%, and again when it gets liquidated.

Commands:

  • Track addresses: /track <address> [more addresses...] [label or entity]
  • Stop tracking an address or whole entity: /track_remove <address|entity>
  • List tracked addresses/entities: /track_list
  • Set movement threshold: /track_threshold <usd_notional>
  • Set HIP-4/outcome movement threshold: /track_threshold_outcomes <usd_notional|reset>
  • Filter alert kinds: /track_alerts <address|entity> [all|off|perp|spot|hip4|twap|transfer|liquidation|staking|unstaking]
  • Filter alert kinds for the current channel/topic: /track_channel_alerts [all|off|perp|spot|hip4|twap|transfer|liquidation|staking|unstaking]
  • Filter assets for the scope: /track_only <asset|prefix> [more...]
  • Create an entity: /entity_create <name>
  • List entities: /entity_list
  • Delete an entity with confirmation: /entity_delete <name>

Examples:

/entity_create Juan
/track 0x1234...abcd 0xabcd...5678 Juan
/track_threshold 25000
/track_threshold_outcomes 5000
/track_alerts Juan perp spot hip4 liquidation transfer
/track_channel_alerts -unstaking
/track_list
/track_remove 0x1234...abcd
/track_remove Juan
/entity_delete Juan

Notes:

  • Minimum movement threshold is $1,000.
  • Private chat tracking is personal to you.
  • Group tracking is shared for that group, and setup commands require group admin permissions.
  • In topic-enabled groups, use /setalertstopic movements or /setalertstopic all to route movement alerts.
  • /track_remove <entity> matches the entity name exactly, so removing Amber does not remove Syncracy or Amber / Syncracy.
  • /add <address> is now only a legacy alias that saves the wallet under /track with your username label.

Smart address labels and risk context

Many relevant addresses are labeled automatically inside alerts, so you can identify the entity behind the flow faster.

Example behavior:

  • If a known address triggers a liquidation, transfer, movement, or unstaking alert, the alert can show the entity name instead of only the raw wallet.
  • Some unstaking alerts also include quick context such as market maker / delta-neutral or liquid staking deployer risk profile.

Commands:

  • No setup required. This is built into alert rendering.

Funding alerts

Tracks positive/negative funding conditions for a market.

Example behavior:

  • If you set below -0.0057 on mkts:US500, the alert triggers when funding is at or below that value.

Commands:

  • Add funding alert: /funding_add <coin> <negative|positive|below|above> [percent]
  • List funding alerts: /funding_list
  • Remove all funding alerts for one market: /funding_remove <coin>

Examples:

/funding_add mkts:US500 negative
/funding_add mkts:US500 below -0.0057
/funding_add mkts:US500 above 0.0100
/funding_remove mkts:US500

Price cross alerts

One-shot level alerts that trigger when price crosses a target.

Example behavior:

  • If you set /price_add BTC 80000, the alert fires when BTC crosses 80,000 in either direction, then auto-disables.

Commands:

  • Add alert: /price_add <coin> <price>
  • List alerts: /price_list
  • Remove alerts by market: /price_remove <coin>

Examples:

/price_add BTC 80000
/price_add spot:KNTQ 0.35
/price_remove BTC

Price jump alerts

Tracks directional moves over a time window.

Example behavior:

  • /jump_add mkts:US500 down 5 60 600 triggers when mkts:US500 drops 5% in 60 minutes, with 600s cooldown.

Commands:

  • Add jump alert: /jump_add <coin> <up|down> <percent> <minutes> [cooldown_seconds]
  • List jump alerts: /jump_list
  • Remove jump alert: /jump_remove <alert_id>
  • Change jump cooldown: /jump_cooldown <alert_id> <seconds>

Examples:

/jump_add mkts:US500 up 5 60 600
/jump_add mkts:US500 down 5 60 600
/jump_cooldown 12 300

Notes:

  • percent must be between 0 and 100.
  • minutes must be between 1 and 1440.
  • jump cooldown must be between 60 and 86400 seconds.

External liquidation alerts

Tracks large liquidation fills in a selected market.

Example behavior:

  • If you set /liquidation_add BTC 1000000, you get alerts when external liquidations on BTC are at least $1M.

Commands:

  • Add alert: /liquidation_add <coin> <usd_notional>
  • List alerts: /liquidation_list
  • Remove alert: /liquidation_remove <coin>

Examples:

/liquidation_add BTC 1000000
/liquidation_remove BTC

TWAP and Net TWAP alerts

Tracks large TWAP flow and net TWAP pressure.

Example behavior:

  • /twap_add BTC 10000000 triggers on new large buy TWAPs.
  • /twap_add BTC -5000000 triggers on new large sell TWAPs.
  • /nettwap_add BTC 3000000 triggers when net active TWAP (buy-sell) is at least +$3M.

Commands:

  • Add TWAP alert: /twap_add <coin> <usd_notional>
  • List TWAP alerts: /twap_list
  • Remove TWAP alert: /twap_remove <coin>
  • Add net TWAP alert: /nettwap_add <coin> <usd_notional>
  • List net TWAP alerts: /nettwap_list
  • Remove net TWAP alert: /nettwap_remove <coin>
  • Show active TWAPs: /show_twaps <coin> <min_usd_notional>

Examples:

/twap_add BTC 10000000
/twap_add BTC -5000000
/twap_add HYPE 2000000
/twap_add HYPE-PERP 2000000
/nettwap_add BTC 3000000
/show_twaps BTC 1000000

Notes:

  • The bot rechecks triggered TWAP and Net TWAP alerts shortly after trigger.
  • If the flow disappears almost immediately with suspicious execution or error patterns, the original alert can be edited as likely spoofing.
  • For HYPE TWAPs, HYPE means spot and HYPE-PERP means perp.

Next liquidations map

Shows near liquidation levels for a market direction.

Example behavior:

  • /nextliquidations down BTC 1000000 10 returns up to 10 relevant downside liquidation levels above your minimum notional.

Commands:

  • /nextliquidations <up|down> <coin> <min_usd_notional> [count]

Example:

/nextliquidations down BTC 1000000 10

Liquidation heatmap

Generates a liquidation heatmap image for a market around current price. When Hydromancer TP/SL data is available, take-profit and stop-loss trigger orders are overlaid as separate color layers.

Example behavior:

  • /heatmap HYPE 20 120 renders the liquidation distribution from -20% to +20% with 120 bins.

Commands:

  • /heatmap <coin> [range_pct] [bins]

Examples:

/heatmap HYPE
/heatmap BTC 20
/heatmap mkts:US500 25 140

Market structure

Returns a compact market structure snapshot for a selected lookback window.

Example behavior:

  • /market_structure HYPE 30 returns price change, OI change, near-liquidation buckets, depth, and key walls over 30 minutes.

Commands:

  • /market_structure <coin> <minutes>

Examples:

/market_structure HYPE 30
/market_structure BTC 60
/market_structure mkts:USOIL 120

Top positions by OI

Returns the 10 largest open positions for one perp market, ranked by USD notional (position OI).

Example behavior:

  • /top10positions xyz:ORCL returns the largest open positions for that market, with side, notional, OI share, size, entry, liquidation price, and trader link.

Commands:

  • /top10positions <coin>

Examples:

/top10positions HYPE
/top10positions BTC
/top10positions xyz:ORCL

Basket TVL snapshot

Returns the current basket TVL snapshot and, when available, a chart of recent history.

Example behavior:

  • /tvl returns the cached or latest basket TVL snapshot.
  • /tvl refresh bypasses the short cache and recalculates the snapshot.

Commands:

  • /tvl
  • /tvl refresh

HLP alert

Tracks high-signal HLP vault events with fixed thresholds.

Example behavior:

  • /hlp_alert shows whether your HLP alert is on or off.
  • /hlp_alert on enables the alert.
  • /hlp_alert off disables the alert.

Commands:

  • /hlp_alert
  • /hlp_alert on
  • /hlp_alert off

Notes:

  • The alert uses fixed thresholds: PnL delta of $100,000 over 60 minutes, large opens of $1,000,000, and a 1,800s cooldown.

Inline market charts

Generates a price chart directly from a normal text message, without using a slash command.

Example behavior:

  • Sending hl HYPE returns a HYPE 1h chart with local tops and bottoms marked.
  • Sending hl HYPE 15m returns a HYPE 15m chart.
  • Sending hl KNTQ 1h returns the spot chart if that market exists in spot.

Commands:

  • Inline syntax: hl <asset> [timeframe]

Examples:

hl HYPE 5m
hl KNTQ
hl BTC 1h
hl KNTQ 4h
hl mkts:USOIL 1d

Notes:

  • Supported timeframes: 1m, 5m, 15m, 1h, 4h, 1d, 1w, 1M.
  • If no timeframe is provided, 1h is used.
  • Works in private chats and groups.
  • If an asset has a perp market, charts default to the perp. Use spot:HYPE for spot HYPE or HYPE-PERP for perp explicitly.
  • If no perp exists, the bot can fall back to the spot market, for example hl KNTQ 1h.
  • In call-game-enabled groups, chart messages can include Long/Short buttons and call markers.

Big position alerts

Tracks large position open/add and close/reduce events above your threshold. Spot markets use actual matched trades in a rolling 60-minute buy/sell window. Balance changes, transfers, and HyperCore/HyperEVM bridges are not classified as trades.

Example behavior:

  • /big_position_add mkts:US500 1000000 alerts when a >=$1M position event is detected for that market.
  • /big_position_add spot:KNTQ 10000 alerts when one address's matched KNTQ buys or sells total >=$10K in the rolling window.

Commands:

  • Add big position alert: /big_position_add <coin> <usd_notional>
  • List big position alerts: /big_position_list
  • Remove big position alert: /big_position_remove <coin>

Examples:

/big_position_add mkts:US500 1000000
/big_position_list
/big_position_remove mkts:US500

Transfer alerts

Tracks large spot token transfers, Hyperliquid deposits, and Hyperliquid withdrawals above your USD threshold.

Example behavior:

  • /transfers_add KNTQ 10000 alerts when a >=$10K KNTQ token transfer is sent or received.
  • /transfers_add deposit 100000 alerts when a >=$100K Hyperliquid USDC deposit is observed.
  • /transfers_add withdrawal 100000 alerts when a >=$100K Hyperliquid USDC withdrawal is observed.

Commands:

  • Add transfer alert: /transfers_add <token|deposit|withdrawal> <usd_notional>
  • List transfer alerts: /transfers_list
  • Remove transfer alert: /transfers_remove <token|deposit|withdrawal>

Examples:

/transfers_add KNTQ 10000
/transfers_add deposit 100000
/transfers_add withdrawal 100000
/transfers_list
/transfers_remove KNTQ
/transfers_remove deposit

Reports and external feeds

Subscribes the current private chat or group to high-signal reports.

Commands:

  • Daily HYPE ETF report: /hype_etf_subscribe
  • Disable daily HYPE ETF report: /hype_etf_unsubscribe
  • HypeStrat dashboard updates: /hypestrat_subscribe
  • Disable HypeStrat updates: /hypestrat_unsubscribe
  • Situational Awareness / Leopold SEC filings: /leopold_subscribe
  • Disable Leopold filings: /leopold_unsubscribe
  • Hyperliquid docs changes: /docs_subscribe
  • Disable docs changes: /docs_unsubscribe

Examples:

/hype_etf_subscribe
/hypestrat_subscribe
/leopold_subscribe

Call game

Groups can use a lightweight call-scoring game.

Example behavior:

  • A user types HYPE long or presses a Long/Short chart button.
  • An open call does not award points. The bot creates exactly one score when the position closes.
  • The score is symmetric: performance % / 10. A +10% result is +1 point and a -10% result is -1 point.
  • A call closes when the user sends close HYPE or HYPE long closed, taps its close button, opens a replacement call, or an SL/TP is hit.
  • Optional SL/TP can be attached in any order, e.g. HYPE long sl 60 tp 80 or long HYPE tp 80.
  • If the market moves 30% or more against the call, the position is liquidated automatically and its final score is -5 points.
  • HIP-4 outcome calls can be opened from outcome cards or /outcomes with Buy/Sell buttons.
  • An outcome call is scored once when it closes, including when official settledOutcomesById state confirms that the outcome settled. The final side payout comes from official settleFraction, even if the contract has disappeared from allMids; a price near 0 or 1 alone does not close it as settled.
  • /open_calls shows the live, provisional score of every open call. It remains provisional and does not count until the position closes.
  • Leaderboard windows filter by when positions closed; they are reporting windows, not extra scoring horizons.

Commands:

  • User score: /score [username]
  • All your open calls and their provisional scores, with close buttons for the 20 most recent: /open_calls (alias: /calls)
  • Group leaderboard over closed-call results: /leaderboard
  • Global group leaderboard over closed-call results: /global_leaderboard
  • Best closed calls: /best_calls
  • Worst closed calls: /worst_calls

Examples:

HYPE long
HYPE long sl 60 tp 80
long HYPE tp 80
close HYPE
HYPE long closed
/outcomes
/open_calls
/leaderboard
/global_leaderboard
/best_calls

Hyperlend alerts

Tracks supply and borrow APY conditions.

Example behavior:

  • /hyperlend_supply USDH up 10 triggers when USDH supply APY goes above 10%.

Commands:

  • /hyperlend_supply <coin> <up|down> <percent>
  • /hyperlend_borrow <coin> <up|down> <percent>
  • /hyperlend_list
  • /hyperlend_remove <supply|borrow> <coin>

Examples:

/hyperlend_supply USDH up 10
/hyperlend_borrow USDH up 15

Rysk commands

Lets you monitor options availability, wallet expiries, and large market-wide HYPE expiries.

Commands:

  • /rysk_calls <underlying>
  • /rysk_puts <underlying>
  • /rysk_subscribe <address>
  • /rysk_unsubscribe <address>
  • /rysk_list
  • /rysk_expiry <usd_notional|off>

/rysk_expiry is HYPE-only. It reads canonical live open interest from each Rysk oToken's on-chain totalSupply, groups it by exact expiry, and checks puts and calls separately. The USD metric is HYPE-equivalent OI multiplied by the latest fresh Rysk HYPE index. If that index is unavailable or stale, it falls back to the official Hyperliquid HYPE spot mid and then the HYPE perp mid, marked as an estimate. If either side reaches your threshold, the bot sends one reminder at each remaining checkpoint: 24 hours, 1 hour, and 10 minutes. A late start or threshold crossing sends one clearly labelled catch-up for the current window instead of replaying every missed checkpoint.

The alert also includes gross exposure, strike/face notional, currently ITM HYPE, the largest strikes, and call OI by collateral type (WHYPE, kHYPE, LHYPE, or another approved wrapper).

When ETHERSCAN_API_KEY is configured, the same alert adds a holder/funding view. It retains and reads holder state only for positive-OI oTokens in the target HYPE expiry. For speed, the shared MMarket increase-event stream is fetched in two batched scans and partitioned by target series; this does not build a holder index for unrelated options. Direct oToken transfer history is queried only for a target series whose supply is actually outside MMarket. Current internal MMarket balances and direct wallet balances are then verified through HyperEVM RPC batches. The alert always reports attributed OI / total OI; incomplete discovery, reconciliation mismatch, or any failed balance read is shown as unknown rather than $0.

The funding check follows the current long/holder, not every historical trade counterparty. The option writer's settlement collateral is already locked in MarginPool; the holder is the party that must supply HYPE for a put exercise or the exact USD asset for a call exercise. Historical events are used only to discover candidate holders, and zero current balances are discarded.

For ITM puts, the bot checks whether each current long has the exact HYPE/WHYPE required to exercise. For ITM calls, it checks the exact USD settlement token required by that series (active series currently include both USDC and USDT0), not an arbitrary stablecoin. ready now means the exact EVM balance and MarginPool allowance are both present. The alert also shows the full exact-token EVM balance, so funds that only need approval are not mistaken for missing funds. Native HyperEVM HYPE and internal Rysk balances are same-domain near-ready liquidity; they can still require wrapping, withdrawal, or approval. All HyperEVM balance/allowance/native/internal reads for a funding snapshot are pinned to one block, preventing a wrap or withdrawal in flight from being counted at both origin and destination. The alert therefore shows both the immediate EOA-ready gap and a separate gap after approval/mobilisation of visible HyperEVM funds. HyperCore HYPE and USDC are shown separately but never subtracted from that gap: this prevents a Core→EVM bridge in flight from double-counting the same capital, and a unified/portfolio account may also be using those balances as collateral. Rysk's off-chain willRedeem flag is treated as a non-binding intent hint: yes, unknown, and no are reported separately, and even no remains inside the conservative all-ITM maximum.

This is an exposure/liquidity signal, not a guaranteed directional trade. A visible put-side HYPE gap can create buy demand if holders exercise; exercised calls can release HYPE or 1:1 HYPE-linked collateral that holders may sell or unwrap. Makers may already be hedged, and funds can arrive from other wallets, subaccounts, exchanges, OTC desks, loans, or bridges before settlement. Rysk's post-expiry physical exercise window is configurable.

Examples:

/rysk_calls HYPE
/rysk_puts BTC
/rysk_subscribe 0x1234...abcd
/rysk_expiry 5000000
/rysk_expiry status
/rysk_expiry off

Unstaking alerts

Tracks new unstaking requests above your minimum size.

Commands:

  • /unstaking_add <min_hype_amount>
  • /unstaking_list
  • /unstaking_timeleft <minutes>
  • /unstaking_remove

Examples:

/unstaking_add 100000
/unstaking_timeleft 30

Retired profiles migration

Profiles have been retired. They were too complex and did not see enough usage.

Temporary migration command:

  • /profiles_subscriptions

How it works:

  • The command shows the alerts you inherited from subscribed profiles.
  • It formats those alerts as copy-paste commands.
  • Paste the commands in private chat or in the group where you want the alerts to live directly.
  • Wick Catcher alerts are not exported because Wick Catcher has also been retired.

Referrals

Use referrals to grow your distribution.

Commands:

  • /referrals

How it works:

  • The command returns your personal referral link and your referral count.
  • Existing referrals from old profile imports are kept.

Why this matters:

  • Referrals are expected to unlock higher limits and more premium features in future updates.

Group topic routing

Use this in topic-enabled groups to control where each alert type is posted.

Command:

  • /setalertstopic <filters>

Examples:

/setalertstopic all
/setalertstopic prices
/setalertstopic transfers
/setalertstopic gamification
/setalertstopic funding,prices,jumps
/setalertstopic off

Available filters include all, liquidations, external_liquidations, big_positions, transfers, movements, gamification, funding, prices, jumps, twaps, and nettwaps.

Important:

  • Run the command inside the exact topic where you want those alerts to appear.
  • Running it in the group default/general topic routes those alerts to the default/general topic.
  • For split routing, go into each topic and run setalertstopic with different filters.