備選平台

Upbit 備選平台 — 證據比較

備選平台用於證據比較，不是推薦。納入是因為公開證據屬性與 Upbit 不同 — 不是因為 Upbit「不好」，也不是因為商業關係。

為何納入這些平台

每個候選至少在一項已發布證據屬性上與 Upbit 不同（監管、法律實體對應、準備金證明、託管、地域紀錄、產品或完整度）。選擇由公開快照決定。

證據屬性

平台	監管	法律實體	準備金證明	託管	地域範圍	產品	覆蓋度
Upbit	1	1	0	2	0	2	5 / 7i
Crypto.com	2	3	1	3	38	2	7 / 7i
HTX	0	0	1	1	43	4	5 / 7i
Binance	4	4	1	3	3	4	7 / 7i
Bitget	1	1	1	1	28	4	7 / 7i
Bybit	1	1	1	1	15	6	7 / 7i

Crypto.com

場所架構監管證據託管模式準備金證明可得性費用透明度地域紀錄產品收錄公開紀錄完整度法域

— Published venue boundary differs (national_venue vs exchange). Interface/protocol presentation is kept distinct from custodial exchange records.
— Regulatory records on file: Upbit 1 (exact IDs 1) vs Crypto.com 2 (exact IDs 2).
— Custody claim records: Upbit 2 vs Crypto.com 3.
— PoR snapshots on file: Upbit 0 vs Crypto.com 1 (PoR ≠ audit).

開啟檔案造訪 Crypto.com

HTX

場所架構監管證據託管模式準備金證明可得性費用透明度地域紀錄產品收錄公開紀錄完整度法域

— Published venue boundary differs (national_venue vs platform). Interface/protocol presentation is kept distinct from custodial exchange records.
— Regulatory records on file: Upbit 1 (exact IDs 1) vs HTX 0 (exact IDs 0).
— Custody claim records: Upbit 2 vs HTX 1.
— PoR snapshots on file: Upbit 0 vs HTX 1 (PoR ≠ audit).

開啟檔案造訪 HTX

Binance

監管證據託管模式準備金證明可得性費用透明度地域紀錄產品收錄公開紀錄完整度法域

— Regulatory records on file: Upbit 1 (exact IDs 1) vs Binance 4 (exact IDs 4).
— Custody claim records: Upbit 2 vs Binance 3.
— PoR snapshots on file: Upbit 0 vs Binance 1 (PoR ≠ audit).
— Fee snapshots on file: Upbit 4 vs Binance 2.

開啟檔案造訪 Binance

Bitget

監管證據託管模式準備金證明可得性費用透明度地域紀錄產品收錄公開紀錄完整度法域

— Regulatory records on file: Upbit 1 (exact IDs 1) vs Bitget 1 (exact IDs 0).
— Custody claim records: Upbit 2 vs Bitget 1.
— PoR snapshots on file: Upbit 0 vs Bitget 1 (PoR ≠ audit).
— Fee snapshots on file: Upbit 4 vs Bitget 2.

開啟檔案造訪 Bitget

Bybit

監管證據託管模式準備金證明可得性費用透明度地域紀錄產品收錄公開紀錄完整度法域

— Regulatory records on file: Upbit 1 (exact IDs 1) vs Bybit 1 (exact IDs 0).
— Custody claim records: Upbit 2 vs Bybit 1.
— PoR snapshots on file: Upbit 0 vs Bybit 1 (PoR ≠ audit).
— Fee snapshots on file: Upbit 4 vs Bybit 2.

開啟檔案造訪 Bybit

仍未解決的問題

未決問題與缺失領域保持未知。空儲存格不是安全結論。

Upbit: 未找到可用於 SAFE 插入的附日期官方 PoR／鑑證快照。
Upbit: 未收錄經確認的一次事件紀錄。
Crypto.com: HISTORICAL only: Mazars AUP as of 2022-12-07 still hosted. Re-check 2026-09-13 found no newer dated official Exchange PoR / attestation / wallet disclosure snapshot. STALE as current reserve evidence — do not present as current.
Crypto.com: 已確認狀態頁。未結構化附日期的重大事件（狀態≠事件）。
HTX: Current HTX Platform User Agreement defines contracting parties as collective 'HTX Operators' (legal persons/DAO/unincorporated organisations/teams) without naming a single global 營運主體 company. Do not inherit Huobi Global Limited / Huobi Global S.A. as current HTX 營運主體 without a current primary source tying that name to today's platform.
HTX: No regulator-register row attachable: named current global HTX 營運主體 entity still unresolved. Legacy Huobi licence claims from secondary news not applied.
Binance: ADGM Nest trio roles mapped from official ADGM Terms; Binance FZE mapped from FZE Terms + VARA VL/24/04/001. Do not treat any single entity licence as brand-wide global authorisation. Nest Trading Limited role kept as unknown enum (broker-dealer/off-exchange per terms) pending richer role taxonomy.
Bitget: FSA Seychelles lists BTG Technology Holdings Limited on the VASP Assessment list (2026-03-09). Not a granted licence. 營運主體 marketing licences (AUSTRAC etc.) were not confirmed on primary registers in this pass; VARA public register has no Bitget VASP licence row (2026-09-13).

局限

這不是「最佳備選」排名。檔案再核驗後差異可能變化。區域紀錄並不意味著全球獲批。