Latency01
The spread changes before the user acts
Telegram, networks, exchange matching, and manual page checks all consume time. Spreads can narrow or disappear within seconds.
Risk
Risk disclosure
Spot-arbitrage observation involves execution risk. Alerts are information, not trading instructions, and do not represent final outcomes.
No auto-trading, no custody, and no profitability promise.
ArbPingRisk
01Market and execution risk
02Funds and route risk
03Responsibility boundary
Risk disclosure for ArbPing: latency, slippage, fees, depth, transfer limits, exchange maintenance, stale snapshots, and user responsibility.
Latency
Situations that can make alerts differ from actual results
Risk content should explain concrete user-facing scenarios, not only show abstract disclaimers.
Depth02
Available size is smaller or slippage increases
depth5 is only a limited-depth preview. Actual order size, taker sequence, and book movement can change the average fill price.
Route03
Transfer routes are unavailable
Network maintenance, paused deposits or withdrawals, wrong tags, or route_blocked state can prevent cross-exchange transfer as expected.
Fees04
Personal fee tiers and withdrawal costs differ
Alert estimates are not every user's final cost. VIP tier, withdrawal fee, and tax responsibility must be checked by the user.
Market and execution risk
A spread can disappear before a user reads the alert. Orders are affected by book movement, slippage, minimum order size, exchange rate limits, and matching latency.
Funds and route risk
Cross-exchange transfers can be affected by network congestion, deposit or withdrawal maintenance, address errors, arrival time, and exchange risk controls. The platform does not custody user assets.
Responsibility boundary
Users decide whether to trade and accept the outcome. ArbPing does not provide investment advice, execute trades, or promise profitability.