HC HaesunCheck MarketsFutures data you can verify
KO / EN
Derivatives involve substantial risk. Data and calculators are informational and may not match your account, region or exchange settings.
METHODOLOGY

How HaesunCheck verifies futures data

Our rule is simple: a number without a traceable source, timestamp and definition is not ready to be presented as verified data.

Source hierarchy

  1. Official exchange contract rules, specifications and public APIs.
  2. Official exchange fee schedules and Help Center documentation.
  3. Government or financial-regulator materials for regional/legal status.
  4. Official announcements for dated rule changes.

Third-party blogs, social posts and community discussions may help identify questions to investigate, but they are not used as the primary evidence for core fee, funding, leverage or regional-access claims.

Market-data provenance

Each stored snapshot includes exchange, contract, source URL, the exact API field mapping, exchange/source timestamp where available, fetch timestamp and a SHA-256 payload hash. This lets us investigate later whether a displayed value came from the intended field.

Freshness rules

Age is measured from the older of the source time and fetch time. Missing or invalid timestamps are unverified. Public risk tiers expire after 24 hours; reviewed base fees and affiliate evidence expire after 7 days. Raw API responses are retained with a matching hash, and invalid bundles are rejected before database storage.

  • LIVE — verified snapshot up to 3 minutes old.
  • RECENT — more than 3 and up to 10 minutes old.
  • STALE — older than 10 minutes; never presented as live.

A stale or failed feed does not silently fall back to an old number labeled “live.” Calculators that depend on a live funding snapshot stop auto-filling when the stored value is stale.

Fee definitions

The comparison table uses regular/default base maker and taker rates. VIP tiers, temporary promotions, token-payment discounts and account-specific negotiated rates are not mixed into the base-rate comparison. A documentation review date is stored separately from an effective date; we do not invent an effective date if the source does not state one.

Liquidation-calculation policy

A public calculator cannot know every account variable. Cross margin, portfolio margin, other positions, wallet balance, collateral haircuts, accumulated funding, close fees and exchange-specific rules can affect actual liquidation. Therefore the tool is labeled an estimator. Public maintenance-margin tiers are auto-filled only when an official unauthenticated endpoint exposes them.

Corrections and conflicting sources

If two official sources conflict, the value is not silently chosen for convenience. We check recency, scope, product type and whether one source is account-specific. Ambiguous information can be withheld until resolved. Material corrections should preserve what changed, when it changed and why.

Language policy

Korean and English pages share the same structured market-data store. Translation does not create a second copy of fee or funding values. Explanatory copy is written for each language’s search intent, while core numerical data remains common.