Units and fee conventions
Percent input fields use ordinary percentage units: enter 0.1 for 0.1%, not 0.001. The result labels identify currency, percentage, BTC, satoshis or time. Keep all quote-currency inputs consistent within a calculation. The dollar notation does not imply that USDT is always identical in value to USD.
The standalone arbitrage calculator compares the same base quantity on both legs and includes the modeled buy fee in the initial cash budget. In the terminal matrix, the buy-notional budget is specified before fees; the supplied costs are deducted from estimated net profit. Network fees, withdrawal fees, funding and venue trading fees are different costs. They must be counted consistently and only once.
Static examples and live data
The default example values are illustrative. They are rendered directly in the HTML so the formula and an example remain available without JavaScript. Results update locally when a visitor submits new inputs.
External data is requested automatically on market pages, or after an explicit address lookup. Failed providers are labelled unavailable. The site does not silently substitute a fabricated live price. Data-source notes distinguish exchange timestamps, local receipt times and historical observations.
Annualization and exposure
Simple annualization scales an observed rate by periods per year. Compounded annualization answers a different mathematical question. Neither forecasts future performance. Funding returns must also be compared with all capital committed to the position.
The hedge and leveraged-cost calculators are linear scenario models. They do not simulate liquidation paths, maintenance-margin tiers, collateral haircuts or automatic position closure. A positive ending scenario can still involve an insolvent leg along the path.
Validation and limitations
The source package includes numerical tests for fees, funding signs, independent intervals, order-book depth, exact post-fee rebalancing and invalid inputs. Static-page checks cover links, metadata and sitemap consistency. These checks do not establish investment performance or remove software risk.
Visual browser and live-provider compatibility must be checked on the actual deployment. Provider schemas and access rules can change. Report suspected errors using the contact information on the About page, including the tool, inputs and expected result.