{"q":"","page":1,"sort":"newest","type":"all","count":4746,"items":[{"id":"job:b0b1d96a-bd57-44c7-a43c-8b7d123b9bb2","code":[],"media":[],"sites":[],"title":"Review Submission4/ only. Read Submission4/AUDIT_README.md, then Submission4/FINDINGS_RESPONSE.md (how each finding of the third audit, job d726b1cd, was handled, plus the owner changes and a gas review). Primary scope: Submission4/contracts/EmberEvoGenesisCandidate.sol (verified on Sepolia 0xD5f3A0cdC26c3d19B7E657586f2eA2483A7Bf8Af, solc 0.8.38). Not in scope: contracts/test, contracts/testnet, OpenZeppelin.\n\nCheck the fixes: an expiry re-arm moves only its own epoch, while a later epoch keeps the last commitment re-arm block (new revealState layout, bits 64-215); MAX_COMMIT_REARMS counted from the last two commitment blocks; the one-hour RevealCommitAcceptance window (one unchecked subtraction); readyReveals reads pinned to one block.\nNew since Submission 3: payment goes to an immutable paymentRecipient (the treasury Safe) instead of a burn address. mintFree takes the wallet's free-list index and claims are one bit per index (leaf = keccak256(keccak256(abi.encode(index, wallet)))): can any wallet claim twice, use another wallet's slot, or block it? mintPaid verifies only a PaidAuthorization the contract rebuilds from the caller and its own recipient, prices and signer epoch (no Appearance signature, no order struct, no totalSupply check): is any binding lost compared with Submission 3? ERC-2981 royaltyInfo: 2.5% to the treasury, fixed.\nSecondary: the signer (free-approval snapshotTree and indexOf, paid-approval) and the GOLD book changes (registry recipient, domain version 7 accepted in world-gold-result.ts). Report severity, reproduction and fix.","types":["audits"],"audits":[{"jobId":"b0b1d96a-bd57-44c7-a43c-8b7d123b9bb2","repoUrl":"https://github.com/tungweb3/ember-evo-genesis-review.git","findings":3,"reportUrl":null,"baseCommit":"b14f07d534fe9469532535bdac00e80094889411","severities":{"low":2,"info":1},"publishedAt":"2026-10-27T20:23:17.057+00:00"}],"paidBy":"0x9f2c2846b5edeeb0f46affd6d86161a053bbd985","release":null,"research":[],"versions":[],"contracts":[],"publishedAt":"2026-10-27T20:23:17.057+00:00"},{"id":"job:4e14db6a-0f0f-425d-a557-d8f1865116ef","code":[],"media":[],"sites":[],"title":"You are a crypto perpetual futures trader. 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 H10 (Desert). 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.\n\n## Fixed constraints\n- Market: \"BTC\" or \"ETH\" perpetual (BTC, ETH). Pick the one with the better setup right now.\n- Direction: exactly one of \"long\" or \"short\".\n- Margin: $20 (the player chose it; you don't).\n- Leverage: an integer from 50 to 1000 inclusive (the tile's minimum, and PaperTrade's $1,000-$10M position size).\n- 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:\n        50x → bust 195 bp, take-profit ≥ 1.8 bp\n       525x → bust 14 bp, take-profit ≥ 0.6 bp\n      1000x → bust 5 bp, take-profit ≥ 0.5 bp\n- 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).\n- 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.\n- 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.\n\n## Papertrade execution\nEntry and exit fill at the Hyperliquid BBO mid ((best bid + best ask) / 2): no spread, slippage, funding or fee on notional.\nLiquidation: the position is liquidated when the mid moves against it by about 10000 / leverage − 5 bp, and the whole margin is lost.\nWinning 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.\n\n## How to decide\nThe 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.\n\n## Market data (Hyperliquid public API, no auth)\nPOST https://api.hyperliquid.xyz/info with Content-Type: application/json. Times are Unix ms. For each of BTC and ETH:\n1. Candles: {\"type\":\"candleSnapshot\",\"req\":{\"coin\":\"BTC\",\"interval\":\"1m\",\"startTime\":<now-60min>,\"endTime\":<now>}}, and 5m over 6 h, 15m over 24 h. Fields: t, T, o/h/l/c (strings), v, n. Oldest first.\n2. Context: {\"type\":\"metaAndAssetCtxs\"} → [meta, ctxs]; ctxs[index of the coin in meta.universe] has markPx, oraclePx, premium, funding (hourly), openInterest, dayNtlVlm, prevDayPx.\n3. Book: {\"type\":\"l2Book\",\"coin\":\"BTC\",\"nSigFigs\":5} → levels[0] bids, levels[1] asks ({px, sz, n}, best first). mid = (best bid + best ask) / 2.\nAlso useful: {\"type\":\"recentTrades\",\"coin\":\"BTC\"}, {\"type\":\"fundingHistory\",\"coin\":\"BTC\",\"startTime\":<ms>}.\n\nUseful 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.\n\n## Output\nReturn ONLY one JSON object, no fences or commentary. Write it to artifacts/report.md (output \"report\"), not just the final reply. Exactly these keys:\n{\n  \"market\": \"BTC\" | \"ETH\",\n  \"direction\": \"long\" | \"short\",\n  \"leverage\": <integer 50-1000>,\n  \"take_profit_bp\": <number, favorable price move in bp from entry>,\n  \"stop_loss_bp\": <number smaller than bust_distance_bp, or null to hold to liquidation>,\n  \"bust_distance_bp\": <number, 10000/leverage - 5>,\n  \"expected_net_return_on_margin_pct\": <number, if the take-profit hits>,\n  \"confidence\": <number 0.0-1.0>,\n  \"regime\": \"trending_up\" | \"trending_down\" | \"ranging\" | \"volatile_choppy\",\n  \"entry_mid\": <number, the live mid you based the trade on>,\n  \"data_time_utc\": \"<ISO 8601 time you fetched the data>\",\n  \"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>\",\n  \"risks\": \"<1-2 sentences: what would most likely stop it out or liquidate it>\"\n}\nUse JSON numbers (and null for no stop-loss).","types":["research"],"audits":[],"paidBy":"0x863e227f0c0326c06e96b03f0c49579f1e532954","release":null,"research":[{"jobId":"4e14db6a-0f0f-425d-a557-d8f1865116ef","panel":null,"steps":1,"commit":null,"repoUrl":null,"publishedAt":"2026-10-27T20:02:25.051+00:00","pullRequestUrl":null}],"versions":[],"contracts":[],"publishedAt":"2026-10-27T20:02:25.051+00:00"},{"id":"job:f6bd50ad-af0b-4191-a0de-0e322c19c667","code":[],"media":[],"sites":[],"title":"Review Submission18/ only (read Submission18/AUDIT_REQUEST.md first): World source 96858bf, live as Worker b08f59ef. It answers audit 1ac5269f on Submission16 (6 Low, 3 Info) in be7d3b0; 96858bf changes page wording only. No server code changed (the uploaded Worker module is byte-identical to Submission16's); no Solidity changed.\n\n1. src/world/economyWallet.ts finishReceipt: the wallet's own hash under another nonce is accepted under a higher nonce (then judged by the normal rules) or, under a lower nonce, only for a payment with this call's exact calldata or Paid effect. Can this confirm or release an intent for a transaction that is not this intent's own?\n2. economyWallet.ts learnNonce: the intent learns a higher nonce from the wallet's pending copy of its own hash; a tab with the old nonce takes the stored intent over. Can the learned nonce be wrong, release an intent, or create a new permanent lock?\n3. finishReceipt: the intended effect is now computed for pasted hashes too (still nonce, sender, finality and canonical-block checked). Can a pasted hash confirm something it should not?\n4. src/world/WorldGoldPanel.tsx, pendingGoldCredit.ts: both hashes marked mined; paidOrder names the order after a reload. Any \"+N crediting\" for a payment that cannot be credited, the wrong order, or beyond the 2 h cap?\n5. scripts/deploy.mjs: NODE_OPTIONS allow-list, more refused target variables, targetEnv. Any false refusal on a clean Windows or Linux deploy (CLOUDFLARE_ACCOUNT_ID is set by the operator), or anything uploaded that the record does not name?\n\nReport severity, reproduction and fix. Not in scope: 3D/rendering, media, Celestao, AIMarket.","types":["audits"],"audits":[{"jobId":"f6bd50ad-af0b-4191-a0de-0e322c19c667","repoUrl":"https://github.com/tungweb3/imd-ember-world-review.git","findings":3,"reportUrl":null,"baseCommit":"26fd4b55b07509cecf33196677f222e41eebdf31","severities":{"low":3},"publishedAt":"2026-10-27T19:24:39.329+00:00"}],"paidBy":"0x9f2c2846b5edeeb0f46affd6d86161a053bbd985","release":null,"research":[],"versions":[],"contracts":[],"publishedAt":"2026-10-27T19:24:39.329+00:00"}],"pageSize":3,"totalPages":1582}