PromptBase
Upgrade
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
(claude-5-opus)
Token size
767
Example input
[EXECUTION_RULES]: Strategy is cross-exchange ETH arbitrage. We monitor the Uniswap V3 WETH/USDC pool and the Binance ETH/USDT spot book. The Python daemon triggers a limit buy on the DEX when the price diverges by more than 1.5% below the Binance ask. Our dev team implemented a mandatory 3-block confirmation wait time (approx. 36 to 45 seconds) on the DEX fill before firing the counter-sell on Binance to prevent orphaned block risks. Once confirmed, we exit the position instantly to lock the spread. We close out completely if the spread narrows below 0.3%. The PM assumes this setup is foolproof for capturing fragmented liquidity. [RISK_PARAMETERS]: We operate with a $250,000 maximum position size per leg to avoid draining the decentralized liquidity pool. We set a hard maximum slippage tolerance of 0.1% on the Uniswap router. On the Binance side, we execute the sell using purely Market Orders to guarantee we get the fill and do not end up net-long ETH. There is a rigid stop-loss programmed at 0.5% drawdown on the total portfolio leg to protect the principal. The risk desk mandates that no position can be held for more than 120 seconds under any circumstances. If the Binance API times out, the script executes a retry loop every 2 seconds indefinitely until filled. [MARKET_CONSTRAINTS]: The target environment is the Ethereum mainnet, which currently averages 12 seconds per block. Gas fees fluctuate wildly, sometimes peaking at 150 gwei during high-volume periods. The Binance API has a strict rate limit of 1200 weight per minute, and IP bans occur if we spam retries during maintenance windows. Average intraday volatility for ETH is 4-5%. While the DEX pool has $50M in liquidity, available depth at the top of the book can evaporate in milliseconds when macroeconomic news breaks. MEV searchers are highly active in this exact spread. The strategy operates 24/7 without pauses for weekend illiquidity or scheduled exchange maintenance.
Example output
Example 1: High-Frequency Crypto Arbitrage (Institutional Prop Desk) [INPUTS] Execution Rules (Entry/Exit Text): Strategy is cross-exchange ETH arbitrage. We monitor the Uniswap V3 WETH/USDC pool and the Binance ETH/USDT spot book. The Python daemon triggers a limit buy on the DEX when the price diverges by more than 1.5% below the Binance ask. Our dev team implemented a mandatory 3-block confirmation wait time (approx. 36 to 45 seconds) on the DEX fill before firing the counter-sell on Binance to prevent orphaned block risks. Once confirmed, we exit the position instantly to lock the spread. We close out completely if the spread narrows below 0.3%. The PM assumes this setup is foolproof for capturing fragmented liquidity. Risk Parameters & Order Types: We operate with a $250,000 maximum position size per leg to avoid draining the decentralized liquidity pool. We set a hard maximum slippage tolerance of 0.1% on the Uniswap router. On the Binance side, we execute the sell using purely Market Orders to guarantee we get the fill and do not end up net-long ETH. There is a rigid stop-loss programmed at 0.5% drawdown on the total portfolio leg to protect the principal. The risk desk mandates that no position can be held for more than 120 seconds under any circumstances. If the Binance API times out, the script executes a retry loop every 2 seconds indefinitely until filled. Market Environment Constraints: The target environment is the Ethereum mainnet, which currently averages 12 seconds per block. Gas fees fluctuate wildly, sometimes peaking at 150 gwei during high-volume periods. The Binance API has a strict rate limit of 1200 weight per minute, and IP bans occur if we spam retries during maintenance windows. Average intraday volatility for ETH is 4-5%. While the DEX pool has $50M in liquidity, available depth at the top of the book can evaporate in milliseconds when macroeconomic news breaks. MEV searchers are highly active in this exact spread. The strategy operates 24/7 without pauses for weekend illiquidity or scheduled exchange maintenance. [SIMULATED OUTPUT] Logic Parameter Extraction Entry Trigger: 1.5% negative price divergence between Uniswap V3 and Binance spot. Execution Delay: Mandatory 3-block confirmation (36-45 seconds) delay between leg 1 (buy) and leg 2 (sell). Exit Trigger: Spread compression below 0.3% or hard time-stop at 120 seconds. Risk Thresholds: 0.1% max slippage on DEX, 0.5% hard stop-loss on total position. Order Types: Limit Order (DEX Buy), Market Order (CEX Sell). Environment: 4-5% daily volatility, active MEV environment, API rate limits present. Structural Contradiction Analysis Latency-Induced Arbitrage Collapse: The strategy requires a 36-45 second delay before hedging the position on Binance. In a market with 4-5% daily volatility, holding unhedged ETH for 45 seconds during a divergence event exposes the capital to directional risk that mathematically exceeds the 0.5% stop-loss threshold. Order Type Asymmetry: Utilizing a Market Order on Binance during a high-volatility event guarantees slippage. If the order book depth evaporates, the Market Order will fill at prices that instantly breach the 0.5% stop-loss, converting a theoretical arbitrage into a realized directional loss. Slippage Paradox: The 0.1% maximum slippage tolerance on Uniswap conflicts with the requirement to beat MEV searchers in a 1.5% divergence scenario. MEV bots will front-run the transaction, causing the 0.1% tolerance to consistently fail, resulting in zero executions or reverted transaction gas penalties. Infinite Retry Loop Liability: The mandate to retry Binance API calls every 2 seconds indefinitely violates the exchange's 1200 weight/minute rate limit. In the event of an API timeout, this logic will trigger an IP ban within minutes, stranding the $250,000 DEX position indefinitely. Vulnerability Recalibration Matrix Hedging Latency Elimination: The 3-block wait time must be removed or mitigated via a delta-neutral perpetual futures hedge. Holding unhedged directional exposure for 45 seconds invalidates the definition of statistical arbitrage. Order Type Replacement: Replace the Binance Market Order with a Limit Order pegged to the required spread margin. If the spread collapses, the system must cancel the order rather than forcing a fill at a catastrophic loss. Slippage Parameter Expansion: The Uniswap slippage tolerance must be widened to a minimum of 0.5% to ensure execution during volatility spikes, or the strategy must incorporate a private RPC endpoint (e.g., Flashbots) to bypass the public mempool entirely. API Rate Limit Protection: The indefinite 2-second retry loop must be replaced with an exponential backoff algorithm capped at 5 retries. A fallback liquidation protocol using decentralized perpetuals must be established if the Binance API remains unreachable. Parameter Deployment Directive TO: Quantitative Engineering Desk SUBJECT: Logic Audit & Parameter Recalibration Directive The current cross-exchange arbitrage logic contains critical execution vulnerabilities. The 45-second unhedged delay combined with CEX Market Orders exposes the principal to directional volatility that mathematically guarantees breaching the 0.5% stop-loss. Furthermore, the API retry loop will trigger institutional IP bans. Suspend live capital deployment immediately. Implement the attached recalibration matrix, explicitly focusing on delta-neutral hedging during block confirmations and replacing market orders with spread-pegged limit parameters.
Claude

Algorithmic Logic Stress Evaluator

Add to Cart
PromptBase Select
Get this prompt + 9 more with SelectFrom $14/mo · Cancel anytimeFrom $14/mo · Cancel anytime
View Select
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
CLAUDE-5-OPUS
Tested icon
Guide icon
4 examples icon
Free credits icon
Stop burning capital on flawed execution logic. This prompt aggressively synthesizes your pasted algorithmic parameters, entry/exit text, and risk rules to identify logical contradictions. It processes your provided strategy documentation to output a structured vulnerability summary and a text-based logic recalibration framework.
...more
Added 2 weeks ago
Report
Browse Marketplace