출처 검증 리서치: Exchange FEE Schedule Change

Decision Matrix

Source Map

• OKX: Trading Fee and Fee Tiers (okx-fees)
• Kraken: Fee Schedule (kraken-fee-schedule)
• Gate.com: Crypto Fee Overview (gate-fee-overview)
• MEXC: MEXC Trading Fees (mexc-fees)
• Bitget: Bitget Trading Fees (bitget-fees)

Control Notes

1. Page location

Page location is the part of the decision where a public source has to become an operating rule. In this package, it means fee source must be a current official page. The practical action is to record URL and access date. The unresolved edge is page redesigns, so this article keeps that uncertainty visible instead of turning it into a safety claim, reward claim, licensing claim, future-availability claim or product endorsement.

For a reader or operator, page location should be recorded before funds, account access, wallet recovery, API order flow, whitelists, identity checks, custody decisions, cross-chain transfers or tokenized-asset decisions become material. The record can stay simple: official URL, access date, product surface, account or network scope, source claim, editorial interpretation and a stop condition. Good evidence is non-secret. Bad evidence contains passwords, passphrases, seed phrases, private keys, API secrets, full balances, identity documents, verification codes, support-ticket private content or screenshots that expose account state.

2. Product split

Product split is the part of the decision where a public source has to become an operating rule. In this package, it means spot, derivatives and other products can differ. The practical action is to map each product separately. The unresolved edge is hidden product exclusions, so this article keeps that uncertainty visible instead of turning it into a safety claim, reward claim, licensing claim, future-availability claim or product endorsement.

For a reader or operator, product split should be recorded before funds, account access, wallet recovery, API order flow, whitelists, identity checks, custody decisions, cross-chain transfers or tokenized-asset decisions become material. Good evidence is non-secret.

3. Tier visibility

Tier visibility is the part of the decision where a public source has to become an operating rule. In this package, it means VIP tiers may be conditional. The practical action is to separate base fees from tier fees. The unresolved edge is account-private tier state, so this article keeps that uncertainty visible instead of turning it into a safety claim, reward claim, licensing claim, future-availability claim or product endorsement.

For a reader or operator, tier visibility should be recorded before funds, account access, wallet recovery, API order flow, whitelists, identity checks, custody decisions, cross-chain transfers or tokenized-asset decisions become material. Good evidence is non-secret.

4. Movement cost

Movement cost is the part of the decision where a public source has to become an operating rule. In this package, it means trading fee is not total cost. The practical action is to check withdrawal and fiat rails separately. The unresolved edge is network fee changes, so this article keeps that uncertainty visible instead of turning it into a safety claim, reward claim, licensing claim, future-availability claim or product endorsement.

For a reader or operator, movement cost should be recorded before funds, account access, wallet recovery, API order flow, whitelists, identity checks, custody decisions, cross-chain transfers or tokenized-asset decisions become material. Good evidence is non-secret.

5. Discount condition

Discount condition is the part of the decision where a public source has to become an operating rule. In this package, it means discounts can be token or campaign dependent. The practical action is to state conditions plainly. The unresolved edge is campaign expiry, so this article keeps that uncertainty visible instead of turning it into a safety claim, reward claim, licensing claim, future-availability claim or product endorsement.

For a reader or operator, discount condition should be recorded before funds, account access, wallet recovery, API order flow, whitelists, identity checks, custody decisions, cross-chain transfers or tokenized-asset decisions become material. Good evidence is non-secret.

6. Radar refresh

Radar refresh is the part of the decision where a public source has to become an operating rule. In this package, it means fee pages can change after publication. The practical action is to refresh before quoting old claims. The unresolved edge is unannounced updates, so this article keeps that uncertainty visible instead of turning it into a safety claim, reward claim, licensing claim, future-availability claim or product endorsement.

For a reader or operator, radar refresh should be recorded before funds, account access, wallet recovery, API order flow, whitelists, identity checks, custody decisions, cross-chain transfers or tokenized-asset decisions become material. Good evidence is non-secret.

7. Stop rule

Stop rule is the part of the decision where a public source has to become an operating rule. In this package, it means stop when source, surface, tier or date is missing. The practical action is to do not publish cheapest claims. The unresolved edge is private account exceptions, so this article keeps that uncertainty visible instead of turning it into a safety claim, reward claim, licensing claim, future-availability claim or product endorsement.

Known Unknowns

• page redesigns
• hidden product exclusions
• account-private tier state
• network fee changes
• campaign expiry
• unannounced updates
• private account exceptions

Practical Takeaway

The safe version of this package stays exact. NexuAlpha Radar treats fee schedules as changing source objects. This scan uses official fee pages from OKX, Kraken, Gate, MEXC and Bitget to build a disclosure checklist: where the venue publishes fee rates, whether the page separates product surfaces, whether VIP tiers or maker-taker roles are visible, whether movement costs need a second page, and whether the comparison date is recorded. The decision outcome is not to declare one venue cheapest. It is to decide when a fee claim is stale, when a discount is conditional, and when a reader must re-open the official page before acting. The user outcome is a documented decision boundary and a stop rule, not a promise that a venue, transfer, API, custody path, tokenized asset, stablecoin metric or onboarding flow will work under every future condition.