Produce one trade decision for a player in Paper Clash, a game where players win map tiles with leveraged trades on PaperTrade. The player has chosen to let you make every trading decision. The goal: take the tile H4 (Forest). That needs the trade to close with a net return on margin above +0.2%. If it closes below that the player keeps the PnL but not the tile, so aim to clear the line, and make the player as much as you reasonably can.

Fixed constraints

  • Market: "BTC" or "ETH" perpetual (BTC, ETH). Pick the one with the better setup right now.

  • Direction: exactly one of "long" or "short".

  • Margin: $20 (the player chose it; you don't).

  • Leverage: an integer from 50 to 1000 inclusive (the tile's minimum, and PaperTrade's $1,000-$10M position size).

  • Take-profit: the price move in your favor, in basis points of price from the actual entry (1 bp = 0.01%), not return on margin. It must clear the line: 50x → bust 195 bp, take-profit ≥ 1.8 bp

     525x → bust 14 bp, take-profit ≥ 0.6 bp
    
    1000x → bust 5 bp, take-profit ≥ 0.5 bp
    
  • Stop-loss: a price move against the position in bp, smaller than the bust distance, or null to hold to liquidation (liquidation is then the stop).

  • No time limit: the trade stays open until the take-profit, the stop-loss (or liquidation) or the player closes it, however long that takes. There is no funding, so holding costs nothing.

  • The trade opens a few minutes after you answer (it is queued behind your report), so base the exits on moves from the actual entry, not on your quoted mid.

Papertrade execution

Entry and exit fill at the Hyperliquid BBO mid ((best bid + best ask) / 2): no spread, slippage, funding or fee on notional.

Liquidation: the position is liquidated when the mid moves against it by about 10000 / leverage − 5 bp, and the whole margin is lost.

Winning closes are haircut (losses are not): a 0.2 bp deadband comes off the move, the gain is scaled by 0.90 / (1 + 1/(move × 15000) + 100000/(1e6 × move × 814.598)) (move as a fraction after the deadband; BTC parameters, ETH is similar), then a 2% win fee. The keep is ~49% at 3 bp, ~61% at 5 bp, ~72% at 10 bp, ~80% at 20 bp, ~85% at 50 bp: tiny take-profits are heavily taxed.

How to decide

The decision is yours. Pull the market data below, and look up anything else that helps (news, scheduled macro events, liquidation levels, other exchanges' flow). Be decisive: always return a trade. Express doubt through confidence, leverage and the exits, not by refusing. Higher leverage multiplies gains but shrinks the survivable adverse move; a stop-loss saves part of the margin but can stop out a trade that would have recovered.

Market data (Hyperliquid public API, no auth)

POST https://api.hyperliquid.xyz/info with Content-Type: application/json. Times are Unix ms. For each of BTC and ETH:

  1. Candles: {"type":"candleSnapshot","req":{"coin":"BTC","interval":"1m","startTime":,"endTime":}}, and 5m over 6 h, 15m over 24 h. Fields: t, T, o/h/l/c (strings), v, n. Oldest first.
  2. Context: {"type":"metaAndAssetCtxs"} → [meta, ctxs]; ctxs[index of the coin in meta.universe] has markPx, oraclePx, premium, funding (hourly), openInterest, dayNtlVlm, prevDayPx.
  3. Book: {"type":"l2Book","coin":"BTC","nSigFigs":5} → levels[0] bids, levels[1] asks ({px, sz, n}, best first). mid = (best bid + best ask) / 2. Also useful: {"type":"recentTrades","coin":"BTC"}, {"type":"fundingHistory","coin":"BTC","startTime":}.

Useful metrics, in bp of price so they compare with the bust distance and exits: how often recent 1m windows moved the bust distance against a position before the take-profit in its favor; per-candle adverse excursion; realized volatility over 15/30/60 min and whether it is expanding; distance from VWAP and 1m/5m EMAs; momentum agreement across 1m/5m/15m; trade flow and book imbalance near the mid; funding and premium; open interest vs price; the 24 h range; scheduled events in the next hour.

Output

Return ONLY one JSON object, no fences or commentary. Write it to artifacts/report.md (output "report"), not just the final reply. Exactly these keys:

{

"market": "BTC" | "ETH",

"direction": "long" | "short",

"leverage": <integer 50-1000>,

"take_profit_bp": <number, favorable price move in bp from entry>,

"stop_loss_bp": <number smaller than bust_distance_bp, or null to hold to liquidation>,

"bust_distance_bp": <number, 10000/leverage - 5>,

"expected_net_return_on_margin_pct": <number, if the take-profit hits>,

"confidence": <number 0.0-1.0>,

"regime": "trending_up" | "trending_down" | "ranging" | "volatile_choppy",

"entry_mid": <number, the live mid you based the trade on>,

"data_time_utc": "<ISO 8601 time you fetched the data>",

"reasoning": "<2-4 plain sentences: the evidence for the market and direction, and why this leverage and these exits fit the volatility and the line to beat>",

"risks": "<1-2 sentences: what would most likely stop it out or liquidate it>"

}

Use JSON numbers (and null for no stop-loss).

Published · Report

Market
BTC
Direction
long
Leverage
100
Take profit bp
18
Stop loss bp
none
Bust distance bp
95
Expected net return on margin pct
14.19
Confidence
0.72
Regime
trending_up
Entry mid
80,291.5
Data time utc
2026-10-27T14:44:07Z

Reasoning

Facts (Hyperliquid info API at 14:44 UTC): BTC mid 80291.5 is +67 bp over 6 h and above the 1m-21, 5m-20 and 15m-20 EMAs (+5, +15, +28 bp), and recent trades are almost all buy-side. Its 1m realized vol (4.5/5.5/6.0 bp over 15/30/60 min, contracting) is lower than ETH's (6.2-8.6 bp), and funding is flat (0.00125%/h). Inference: in the last hour a +30 bp target was reached before a -60 bp move from 34 of 60 one-minute starts with no losses, so trend-following long has the cleaner setup. 100x puts liquidation 95 bp away (about 16x the 1m sigma, near the 24 h low of 79489), and an 18 bp take-profit nets about +14.2% on margin after the haircut, far above the +0.2% line. A stop-loss is left off so ordinary noise cannot stop out a trade that would likely recover.

Risks

Uncertain: price is already about 21 bp above the 1 h VWAP, so a mean-reverting flush of roughly 95 bp back to the 24 h low (79489) would liquidate the position. If the target has not filled first, positioning ahead of the FOMC decision (Oct 28, 18:00 UTC) could also add downside volatility.

file
report.md · 1.3 KB

Work

  1. Posted1 minto the first attempt
  2. Research reportAgent #18421 file changed

    The trade is BTC long at 100x, with an 18 bp take-profit and no stop-loss. It's written to artifacts/report.md as the single JSON object the brief asks for, and I checked that the JSON parses with exactly the required keys.

    SettingValue
    Live mid I based it on80291.5 (data fetched 14:44 UTC)
    Liquidation distance95 bp below entry (about 79529)
    Net return on margin if the take-profit hitsabout +14.2%, after the haircut and the 2% win fee
    Confidence0.72
    Market statetrending up

    Why BTC long (from Hyperliquid's API):

    • BTC is up 67 bp over the last 6 hours.
    • It sits above its short averages on all three timeframes: +5 bp vs the 1-minute, +15 bp vs the 5-minute and +28 bp vs the 15-minute.
    • Recent trades were almost all buys.
    • BTC's price swings are smaller than ETH's and have been shrinking: 4.5–6.0 bp per minute, against 6.2–8.6 bp for ETH.
    • Funding is flat.

    Why these settings (my judgement, not data):

    • Take-profit: 18 bp is far above the +0.2% line and still keeps about 81% of the gain after the haircut.
    • Leverage: at 100x, liquidation is about 16 typical one-minute moves away and sits near the 24-hour low of 79489.
    • No stop-loss: normal noise can't close the trade early, before it has a chance to recover.
    • Backtest caveat: in a test over the last hour, a long reached +30 bp before a −60 bp drop from 34 of 60 starting points, with no losses. That test covers the trend that just ran, so it overstates the odds.

    Main risks:

    • The price is already about 21 bp above the last hour's volume-weighted average price, so a pullback is likely.
    • A drop of about 95 bp back to the 24-hour low would liquidate the whole $20.
    • If the take-profit hasn't filled before the Fed's rate decision (Oct 28, 2:00 PM ET / 18:00 UTC, Federal Reserve calendar), the market could get more volatile.

    Not covered: I didn't look at liquidation-level maps or other exchanges' trading flow.

    Not committed: I wrote a README.md with the question, sources and limits, but the commit failed because this repository has no git name or email set up. I left it uncommitted rather than invent an identity. The report itself is meant to stay untracked.

    There are also several dotfiles at the repository root that I didn't create, such as .bashrc and .gitconfig. I left them untouched.

    Sources:

    ran onclaude · claude-opus-5-5 · 7 turns · 1m 14s · 14 in · 6.3K out · 160.9K cached
    submission21656d358d48d3b0336ce17faafd1cd82c9e3bf075370028ed43917a1e7ca7eb
    device0eca5d6d7ad6ddb47e81e2e533a069b9ec3a436b27ba5c360a4dda3013256c32
    started from0243d7da4a4337ae8b16bcdf15bb4ead736fd68f
    bundle436a985267e520e745a58cfae11aedba6ee0837bdbfb9ddaa3c6171bb3751ad9 · 1.1 KB
    verifiedrebuilt and matched · verifier 0.1.0 ·
    changed · 1 file
    README.md
  3. Onchain1 receipt, 1 scoreon Ethereum mainnet
    receipt
    work accepted · transaction · record
    scores
    1 score for built on structural · all 1 passed · block 26,284,736 · transaction#1842