{"version":1,"generatedAt":"2026-10-13T06:55:48.868Z","batchId":"20261013T1435","articles":[{"slug":"how-to-deposit-on-okx-2026-crypto-p2p-card-step-by-step","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-13T06:55:26.000Z","updatedAt":"2026-10-13T06:55:26.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"5 min","es":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"How to Deposit on OKX in 2026: Crypto Transfer, P2P and Card, Step by Step","zh-Hans":"2026 年 OKX 怎么充值？链上转币、P2P 和银行卡三种方式一步步讲清","es":"Comisiones de OKX P2P en 2026: cuánto cuesta de verdad comprar USDT con pesos"},"summary":{"en":"Deposit on OKX step by step: pick the same network, mind tags and minimums, no USDT on BSC. P2P has zero OKX fee; live MXN, ARS, COP, BRL spreads on 13 Oct 2026.","zh-Hans":"在 OKX 充值，先完成身份认证，再进入「资产 > 充值」，选好币种和网络，复制 OKX 给出的地址，然后在另一个钱包或交易所用完全相同的网络转出即可。手里只有法币的话，走「交易 > 买币/卖币」：P2P 市场 OKX 不收服务费，最低 1 USDT 起；第三方银行卡通道的限额和价格由服务商自己定。最容易亏钱的三个错误是：选错网络、漏填标签（Tag/Memo）、转入金额低于最低充值额。","es":"OKX no cobra comisión en su mercado P2P y permite operar desde 1 USDT; el costo real es la brecha entre el precio de compra y de venta más lo que cobre tu banco."},"availableLocales":["en","zh-Hans","es"],"claims":[{"id":"c1","text":"OKX requires identity verification before a deposit, and the deposit network must match the withdrawal network on the sending platform.","sourceIds":["okx-network"],"risk":"low"},{"id":"c2","text":"OKX does not support USDT deposits on BNB Smart Chain; its USDT list shows 16 other networks.","sourceIds":["okx-network","okx-withdraw-fees"],"risk":"low"},{"id":"c3","text":"Deposits below the minimum are neither credited nor refunded.","sourceIds":["okx-min-deposit","okx-not-credited"],"risk":"low"},{"id":"c4","text":"USDT on Tron needs 19 confirmations and on Ethereum 32.","sourceIds":["okx-deposit-time"],"risk":"low"},{"id":"c5","text":"OKX P2P charges no service fee and starts from 1 USDT; payment providers may charge their own fees.","sourceIds":["okx-p2p-faq"],"risk":"low"},{"id":"c6","text":"On 13 Oct 2026 06:49 UTC the OKX P2P buy/sell gap was 0.71% for MXN, 0.26% for ARS, 0.60% for COP and 5.1% for BRL.","sourceIds":["okx-p2p-books"],"risk":"medium"},{"id":"c7","text":"New P2P users face escalating bans after more than 5 pre-payment cancellations a day; P2P purchases can carry a T+N withdrawal hold.","sourceIds":["okx-p2p-cancel","okx-locked"],"risk":"low"},{"id":"c8","text":"Travel Rule locked deposits are unlocked from the Asset page by submitting the sender's details.","sourceIds":["okx-travel-rule","okx-locked"],"risk":"low"},{"id":"c9","text":"OKX code nexu888 returns 40% of trading fees, turning a 0.100% taker fee into 0.060% net.","sourceIds":["nexualpha-partners","okx-fee-spot"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"is-binance-pool-shutting-down-november-10-cloud-mining-pool-savings","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-13T06:55:26.000Z","updatedAt":"2026-10-13T06:55:26.000Z","readTime":"5 min","readTimeByLocale":{"en":"5 min","zh-Hans":"4 min"},"author":"NexuAlpha Research Desk","title":{"en":"Is Binance Pool Shutting Down? Yes, on 10 November 2026: What Miners and Pool Savings Users Must Do","zh-Hans":"币安矿池要关了吗？是的，2026 年 11 月 10 日停止：矿工和矿池理财用户该做什么"},"summary":{"en":"Binance Pool, Pool Savings, Cloud Mining and the Transaction Accelerator close at 15:00 SGT on 10 Nov 2026. Deadlines, what miners and savers must do, and the pool's share.","zh-Hans":"是的。币安在 2026 年 10 月 13 日发布公告，将在新加坡时间 2026 年 11 月 10 日 15:00（UTC 07:00）停止币安矿池及所有相关服务，包括矿池理财（Pool Savings）、云算力（Cloud Mining）和交易加速器。矿工必须在这个时间点之前把矿机切换到其他矿池，矿池理财持有人应尽快赎回，还有待结算收益的用户要确认自己的币安账户能够正常接收。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"Binance will discontinue Binance Pool, Pool Savings, Cloud Mining and the Transaction Accelerator at 07:00 UTC on 10 November 2026.","sourceIds":["binance-notice","cointelegraph"],"risk":"low"},{"id":"c2","text":"Shares submitted after the cutoff are not credited; eligible shares before it are included in the final reward calculation.","sourceIds":["binance-notice"],"risk":"low"},{"id":"c3","text":"Binance asks users to complete required steps such as identity verification by 23:59 UTC on 10 November and keeps pool pages viewable until 07:00 UTC on 24 November.","sourceIds":["binance-notice"],"risk":"low"},{"id":"c4","text":"Binance Pool mined 48 of 4,416 Bitcoin blocks (1.09%) in the past month and 9 of 1,058 (0.85%) in the past week.","sourceIds":["mempool-pools-1m","mempool-pools-1w"],"risk":"low"},{"id":"c5","text":"Binance Pool launched in April 2020.","sourceIds":["cointelegraph"],"risk":"low"},{"id":"c6","text":"OKX code nexu888 returns 40% of trading fees, turning a 0.100% taker fee into 0.060% net.","sourceIds":["nexualpha-partners","okx-fee-spot"],"risk":"low"}],"relatedVenues":["binance","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"wormhole-w-down-33-percent-pump-unwound-negative-funding","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-13T04:56:57.000Z","updatedAt":"2026-10-13T04:56:57.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"Why Is Wormhole (W) Down 33% Today? The Futures Pump Has Unwound and Funding Turned Negative (13 October 2026)","zh-Hans":"Wormhole（W）今天为什么跌了 33%？合约推起来的涨幅几乎全部回吐，资金费率转负（2026 年 10 月 13 日）"},"summary":{"en":"Wormhole's W fell about 33% on 13 Oct 2026 to $0.0192, giving back most of a 78% futures-driven pump; open interest is down 75% from its peak and funding is negative.","zh-Hans":"截至 2026 年 10 月 13 日新加坡时间 12:51（UTC 04:51），Wormhole 的 W 代币 24 小时下跌约 33%，报 0.0192 美元左右。 原因是 10 月 11 日到 12 日那一波由合约推动的拉升基本退潮：W 从约 0.0178 美元涨到 0.03175 美元的高点，涨幅约 78%，现在只比起涨点高约 8%。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"W fell about 33% in the 24 hours to 04:51 UTC on 13 October 2026 to about $0.0192, after rising about 78% from $0.0178 to $0.03175 between 11 and 12 October.","sourceIds":["binance-spot-w","binance-futures-w","okx-w-swap"],"risk":"low"},{"id":"c2","text":"Binance W perpetual open interest rose from 509 million W to 961 million W and has since fallen to 624 million W, removing about three quarters of the build-up.","sourceIds":["binance-futures-w"],"risk":"low"},{"id":"c3","text":"Funding on W perpetuals is negative on Binance, OKX and Hyperliquid; on 12 October Hyperliquid funding had been positive.","sourceIds":["binance-futures-w","okx-w-swap","hyperliquid-w"],"risk":"low"},{"id":"c4","text":"Binance perpetual volume was $592 million in 24 hours against $42.9 million on Binance spot.","sourceIds":["binance-futures-w","binance-spot-w"],"risk":"low"},{"id":"c5","text":"Upbit's KRW-W market traded 63.8 billion won in the 12 hours of the peak and showed no price premium over Binance.","sourceIds":["upbit-w","binance-spot-w"],"risk":"low"},{"id":"c6","text":"No new Wormhole announcement explains the rise or the fall.","sourceIds":["wormhole-blog"],"risk":"medium"}],"relatedVenues":["binance","okx","hyperliquid"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"okx-vs-binance-fees-2026-trading-withdrawal-compared","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-13T04:55:04.000Z","updatedAt":"2026-10-13T04:55:04.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"6 min","ru":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"OKX Fees vs Binance in 2026: Spot, Futures and Withdrawal Fees Side by Side","zh-Hans":"2026 年 OKX 和币安手续费哪个低？现货、合约、提币费用逐项对比","ru":"Комиссия Binance за сделку в 2026 году: сколько берёт биржа и как это выглядит рядом с OKX"},"summary":{"en":"OKX vs Binance fees on 13 Oct 2026: spot 0.08%/0.10% vs 0.10%/0.10% (0.075% with BNB), futures 0.02%/0.05% on both, plus USDT, BTC and ETH withdrawal fees.","zh-Hans":"普通用户在 OKX 做现货，挂单（Maker）费率 0.080%、吃单（Taker）0.100%；币安现货挂单和吃单都是 0.100%。所以挂限价单时 OKX 更便宜，直接市价买入时两家一样。U 本位永续合约两家完全相同，都是挂单 0.020%、吃单 0.050%。如果在币安用 BNB 抵扣手续费，现货再打 75 折（0.075%），币安就反超；而提 USDT 走二层网络或 TON 时，OKX 通常更省。","ru":"Обычный пользователь Binance платит 0,10% за сделку на споте и мейкером, и тейкером; при оплате комиссии в BNB ставка снижается на 25%, до 0,075%."},"availableLocales":["en","zh-Hans","ru"],"claims":[{"id":"c1","text":"A regular OKX user pays 0.080% maker and 0.100% taker on spot; a regular Binance user pays 0.100% on both sides.","sourceIds":["okx-fee-spot","okx-fees-page","binance-fees-facts"],"risk":"low"},{"id":"c2","text":"Paying fees in BNB cuts Binance spot fees by 25% (to 0.075%) and USDⓈ-M futures fees by 10%.","sourceIds":["binance-fees-facts"],"risk":"low"},{"id":"c3","text":"Both exchanges charge regular users 0.020% maker and 0.050% taker on USDT-margined perpetual futures.","sourceIds":["okx-fee-futures","binance-fees-facts"],"risk":"low"},{"id":"c4","text":"On 13 October 2026 USDT withdrawals cost 1.5 USDT on TRC20 at both exchanges, 0.83 vs 0.5 USDT on ERC20 (OKX vs Binance), and 0.02 vs 0.3 USDT on TON.","sourceIds":["okx-withdraw-fees","binance-networks"],"risk":"low"},{"id":"c5","text":"OKX lists no BNB Smart Chain network for USDT withdrawals; Binance charges 0.01 USDT on BEP20.","sourceIds":["okx-withdraw-fees","binance-networks"],"risk":"low"},{"id":"c6","text":"OKX spot VIP 1 starts at $1 million 30-day volume or $100,000 in assets and charges 0.0675%/0.080%.","sourceIds":["okx-fee-spot"],"risk":"low"},{"id":"c7","text":"OKX code nexu888 returns 40% of trading fees; Binance code 11350287 returns 25%.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["okx","binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"south-korea-blocks-mexc-kucoin-27-crypto-exchange-websites","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-13T03:03:46.000Z","updatedAt":"2026-10-13T03:03:46.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"Is MEXC Blocked in South Korea? Korea Orders 27 Exchange Websites Blocked, Including KuCoin, BingX and BitMart: What Users Should Do Now (13 October 2026)","zh-Hans":"MEXC 在韩国被封了吗？韩国下令屏蔽 27 家交易所网站，KuCoin、BingX、BitMart 都在名单上：用户现在该怎么做（2026 年 10 月 13 日）"},"summary":{"en":"Korea's FIU ordered 27 unregistered exchange websites blocked on 13 October 2026, including MEXC, KuCoin, BingX and BitMart. The full list, why, and how users withdraw.","zh-Hans":"是的。 韩国金融情报分析院（FIU）2026 年 10 月 13 日发布消息：韩国广播媒体通信审议委员会已在 10 月 6 日和 7 日两次审议后，决定在韩国境内屏蔽 27 家未申报加密平台的网站，MEXC、KuCoin、BingX、BitMart、Phemex、Bitrue、WEEX、Pionex 都在其中。 这些平台的手机 App 此前已经在谷歌和苹果应用商店被禁止新装和更新。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"Korea's content regulator decided on 6-7 October 2026 to block domestic access to 27 unregistered crypto platform websites including MEXC and KuCoin, announced by the FIU on 13 October.","sourceIds":["fsc-release","fsc-attachment","ct-report"],"risk":"low"},{"id":"c2","text":"Unregistered crypto business in Korea is punishable by up to five years in prison or a 50 million won fine.","sourceIds":["fsc-release"],"risk":"low"},{"id":"c3","text":"Only 28 businesses are registered with the FIU.","sourceIds":["fsc-release"],"risk":"low"},{"id":"c4","text":"A June 2026 DAXA inspection found average fees of 1.5%-10% on unregistered platforms versus 0.16% at the five KRW exchanges.","sourceIds":["fsc-release"],"risk":"low"},{"id":"c5","text":"The FIU warns that referring users to unregistered platforms may expose recommenders to criminal liability.","sourceIds":["fsc-release"],"risk":"low"},{"id":"c6","text":"The FIU will publish withdrawal methods and procedures through DAXA.","sourceIds":["fsc-release"],"risk":"low"}],"relatedVenues":["mexc","kucoin"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"bitget-withdrawal-to-bank-account-2026-sepa-pix-swift-p2p","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-13T03:02:19.000Z","updatedAt":"2026-10-13T03:02:19.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"6 min","id":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"Bitget Withdrawal to Bank Account (2026): Which Currencies Go Straight to Your Bank, the Fees, and the P2P Route for Everyone Else","zh-Hans":"Bitget 怎么提现到银行卡？2026 年哪些法币能直接到账、手续费多少，其他地区怎么走 P2P","id":"Cara Withdraw Bitget ke Rekening Bank di Indonesia (2026): Jual USDT lewat P2P IDR, Biaya dan Batasnya"},"summary":{"en":"Bitget pays out to banks only in EUR, BRL, USD, MXN, VND, ZAR and ZEN.com currencies. Fees per currency, steps, limits, and the fee-free P2P route for everyone else.","zh-Hans":"Bitget 只对少数几种法币提供\"直接提到银行账户\"的通道：欧元走 SEPA（每笔 1 欧元），巴西雷亚尔走 Pix（2.6 雷亚尔），美元走 SWIFT（30 美元），墨西哥比索走 SPEI（5 比索），越南盾银行转账（0.8%），南非兰特（20 兰特），另有九种货币经 ZEN. com 出金（0.5%）。","id":"Bitget tidak menyediakan penarikan rupiah langsung ke bank; IDR tidak ada di daftar mata uang transfer bank Bitget."},"availableLocales":["en","zh-Hans","id"],"claims":[{"id":"c1","text":"Bitget offers direct bank withdrawals only in EUR (SEPA, 1 EUR), BRL (Pix, 2.6 BRL), USD (SWIFT, 30 USD), MXN (SPEI, 5 MXN), VND (0.8%), ZAR (20 ZAR) and nine ZEN.com currencies (0.5%).","sourceIds":["bg-fiat-fees","bg-fiat-regions"],"risk":"low"},{"id":"c2","text":"Users whose currency is not supported use P2P; Bitget P2P supports IDR and charges no trading or service fee.","sourceIds":["bg-fiat-regions","bg-p2p-currencies","bg-p2p-intro"],"risk":"low"},{"id":"c3","text":"Bank and P2P payment accounts must match the verified Bitget name; joint and third-party accounts are rejected.","sourceIds":["bg-fiat-fees","bg-eur-withdraw","bg-p2p-sell"],"risk":"low"},{"id":"c4","text":"SEPA withdrawals take 1-2 business days with a 10 EUR minimum; SWIFT 1-3 working days; Pix usually instant; VND 1-2 business days.","sourceIds":["bg-eur-withdraw","bg-usd-swift","bg-brl-withdraw","bg-vnd-withdraw"],"risk":"low"},{"id":"c5","text":"Bitget USDT withdrawal fees on 13 October 2026 ranged from 0.01 USDT on BEP20 to 2 USDT on ERC20, with a 10 USDT minimum.","sourceIds":["bg-coins-api"],"risk":"low"},{"id":"c6","text":"P2P daily buy limit is 3,000,000 USDT and weekly/monthly 30,000,000 USDT, with the daily window in UTC+8.","sourceIds":["bg-p2p-limits"],"risk":"low"},{"id":"c7","text":"Verified 24-hour withdrawal limit is 3 million USDT at VIP 0 and 20 million at VIP 7.","sourceIds":["bg-kyc-limits"],"risk":"low"},{"id":"c8","text":"NexuAlpha's Bitget invite code is nexu888.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"is-blur-shutting-down-nfts-blend-loans-blur-token-november-12","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-13T00:57:19.000Z","updatedAt":"2026-10-13T00:57:19.000Z","readTime":"5 min","readTimeByLocale":{"en":"5 min","zh-Hans":"4 min"},"author":"NexuAlpha Research Desk","title":{"en":"Is Blur Shutting Down? What Happens to Your NFTs, Blend Loans and BLUR Tokens After 12 November 2026","zh-Hans":"Blur 要关闭了吗？11 月 12 日之后你的 NFT、Blend 借贷和 BLUR 代币会怎样"},"summary":{"en":"Blur's website closes 12 November 2026 but the protocol stays on-chain. What happens to your NFTs, listings, bids, Blend loans and BLUR, and what to do before the deadline.","zh-Hans":"Blur 关闭的是网站，不是智能合约：官方 10 月 12 日在 X 上宣布，blur.io 前端将于 2026 年 11 月 12 日下线，链上的 Blur 市场协议继续运行，BLUR 代币仍掌控协议的费用开关。同一天起，Blur 的 NFT 借贷产品 Blend 停止撮合新贷款，借款人必须在此之前还款，否则贷款违约。消息公布后 24 小时内，BLUR 在币安下跌约 31%，报 0.0132 美元。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"The blur.io frontend will be deprecated on 12 November 2026; the marketplace protocol stays on-chain and BLUR keeps control of the fee switch.","sourceIds":["blur-x-thread","theblock-blur"],"risk":"low"},{"id":"c2","text":"Blend stops matching new loans on 12 November 2026; borrowers must repay or let loans default; Blur will provide a withdrawal tool afterwards.","sourceIds":["blur-x-thread","theblock-blur"],"risk":"low"},{"id":"c3","text":"Blur monthly volume fell from about $1.43 billion in March 2023 to under $7 million by March 2026.","sourceIds":["theblock-blur"],"risk":"low"},{"id":"c4","text":"BLUR fell 30.8% on Binance in 24 hours to $0.01317 by 00:53 UTC on 13 October; Binance perp funding -0.60%, open interest about 282 million BLUR.","sourceIds":["binance-blur-spot","binance-blur-perp","okx-blur-spot"],"risk":"low"},{"id":"c5","text":"Legacy marketplace approvals on Magic Eden left $5.7 million of NFTs exposed before a rescue.","sourceIds":["theblock-magic-eden"],"risk":"low"}],"relatedVenues":["binance","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"hyperliquid-referral-code-2026-where-to-enter-4-percent-discount","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-13T00:56:00.000Z","updatedAt":"2026-10-13T00:56:00.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"4 min","vi":"6 min"},"author":"NexuAlpha Research Desk","title":{"en":"Hyperliquid Referral Code 2026: Where to Enter It, the 4% Fee Discount and the Limits Nobody Mentions","zh-Hans":"Hyperliquid 邀请码 2026：填在哪里、能省多少手续费，以及没人告诉你的几个限制","vi":"Mã giới thiệu Hyperliquid là gì? Nhập ở đâu và được giảm bao nhiêu phí (2026)"},"summary":{"en":"Hyperliquid referral code NEXU888: enter it on the Referrals page or via a /join/ link for 4% off fees on your first $25M. Steps, fee table, builder-code catch, FAQ.","zh-Hans":"Hyperliquid 的邀请码在 app. hyperliquid. xyz/referrals 页面填写，或者直接打开 app. hyperliquid. xyz/join/邀请码 这样的链接自动绑定；NexuAlpha 的邀请码是 NEXU888。 按 Hyperliquid 官方文档，使用邀请码后，你前 2500 万美元交易量的手续费打 96 折（即减免 4%）。","vi":"Mã giới thiệu Hyperliquid gắn vào địa chỉ ví và giảm 4% phí giao dịch cho 25 triệu USD khối lượng đầu tiên, theo tài liệu chính thức; nhập tại app. hyperliquid. xyz/referrals hoặc qua link app. hyperliquid. xyz/join/NEXU888."},"availableLocales":["en","zh-Hans","vi"],"claims":[{"id":"c1","text":"A Hyperliquid referral code gives a 4% fee discount for the user's first $25 million of volume and does not apply to vaults or sub-accounts.","sourceIds":["hl-referrals","hl-fees"],"risk":"low"},{"id":"c2","text":"Codes are entered on app.hyperliquid.xyz/referrals or applied through an app.hyperliquid.xyz/join/CODE link.","sourceIds":["hl-referrals"],"risk":"low"},{"id":"c3","text":"Builder codes override referral codes for the order they are attached to.","sourceIds":["hl-staking-referral"],"risk":"low"},{"id":"c4","text":"Base perpetual fees are 0.045% taker and 0.015% maker; base spot fees 0.070% and 0.040%; HYPE staking discounts range from 5% to 40%.","sourceIds":["hl-fees"],"risk":"low"},{"id":"c5","text":"Onboarding needs an EVM wallet or email login; enabling trading is a gas-free signature; trading is gas-free.","sourceIds":["hl-onboarding"],"risk":"low"},{"id":"c6","text":"NexuAlpha's Hyperliquid code is NEXU888.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["hyperliquid"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"crypto-fear-and-greed-index-today-cmc-55-vs-alternative-69","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-12T22:56:30.000Z","updatedAt":"2026-10-12T22:56:30.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"5 min","tr":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"Crypto Fear and Greed Index Today: Why CoinMarketCap Says 55 and Alternative.me Says 69","zh-Hans":"今天加密货币恐慌贪婪指数是多少？为什么 CoinMarketCap 显示 55、Alternative.me 显示 69","tr":"Kripto Korku ve Açgözlülük Endeksi Bugün: CoinMarketCap Neden 55, Alternative.me Neden 69 Diyor?"},"summary":{"en":"CoinMarketCap's crypto Fear and Greed Index reads 55 (neutral), Alternative.me 69 (greed). Why they differ, what each measures, and what liquidations and funding say.","zh-Hans":"截至 2026 年 10 月 12 日 UTC 22:38（北京时间 13 日早上 6:38），CoinMarketCap 的加密货币恐慌贪婪指数为 55，属于“中性”，前一天是 58，一周前是 67；而更老牌的 Alternative. me 指数 12 日读数是 69，属于“贪婪”，比前一天的 61 反而上升。 两者都是 0 到 100 的情绪指标，但采用的数据完全不同，所以在比特币缓慢下跌、成交和社交热度却不低的日子里，会出现一个跌、一个涨的情况。","tr":"CoinMarketCap'in kripto Korku ve Açgözlülük Endeksi 13 Ekim 2026 TSİ 01:38 itibarıyla 55 (nötr), Alternative. me ise 12 Ekim için 69 (açgözlülük) gösteriyor; iki endeks farklı verilerle hesaplandığı için ayrışıyor."},"availableLocales":["en","zh-Hans","tr"],"claims":[{"id":"c1","text":"CMC index was 55 (neutral) at 22:38 UTC 12 Oct 2026, from 58 a day earlier and 67 a week earlier.","sourceIds":["cmc-fng-api"],"risk":"low"},{"id":"c2","text":"Alternative.me printed 69 (greed) for 12 Oct, up from 61.","sourceIds":["alternative-fng-api"],"risk":"low"},{"id":"c3","text":"The two indexes use different inputs (options, implied volatility, top-10 momentum, SSR vs Bitcoin volatility, volume, social, dominance, trends).","sourceIds":["cmc-fng-page","alternative-fng-page"],"risk":"low"},{"id":"c4","text":"About $49.7M liquidated in 24 h to 22:52 UTC, ~78% longs.","sourceIds":["nexualpha-market-events"],"risk":"low"},{"id":"c5","text":"BTC traded ~$82,616, -1.27% in 24 h.","sourceIds":["binance-btc-ticker"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"bybit-kyc-level-1-vs-level-2-2026-documents-limits","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-12T22:54:13.000Z","updatedAt":"2026-10-12T22:54:13.000Z","readTime":"8 min","readTimeByLocale":{"en":"8 min","zh-Hans":"6 min"},"author":"NexuAlpha Research Desk","title":{"en":"Bybit KYC Level 1 vs Level 2 in 2026: Documents, Withdrawal Limits and What Each Level Unlocks","zh-Hans":"Bybit 实名认证一级和二级有什么区别？2026 年所需材料、提现额度与解锁功能"},"summary":{"en":"Bybit KYC Level 2 = Advanced: add a proof of address. Limits: 20K USDT/day without KYC, 1M Standard, 2M Advanced. Needed for Bybit Stocks and the card.","zh-Hans":"在 Bybit 上，大家说的“KYC 一级”就是官方的“个人认证（标准）”，需要上传身份证件并完成人脸识别；“KYC 二级”是“个人认证（高级）”，在一级基础上再提交一份近三个月内的地址证明。 未认证账户每天最多提现 2 万 USDT、每月 10 万 USDT；完成一级后，非 VIP 账户日提现上限升到 100 万 USDT 且不设月度上限；完成二级后翻倍到 200 万 USDT。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"Bybit splits individual KYC into Standard (identity assessment and POI), Advanced (POA) and Pro (EDD); Bybit Stocks calls the needed level KYC Level 2.","sourceIds":["bybit-kyc-howto","bybit-kyc-faq","bybit-learn-stocks"],"risk":"low"},{"id":"c2","text":"Unverified accounts can withdraw up to 20,000 USDT a day and 100,000 USDT a month; Standard 1M a day, Advanced/Pro 2M a day, no monthly limit.","sourceIds":["bybit-kyc-benefits","bybit-kyc-faq"],"risk":"low"},{"id":"c3","text":"Without KYC, Bybit's table shows no deposits or trading; Standard is mandatory for all products.","sourceIds":["bybit-kyc-benefits","bybit-kyc-faq"],"risk":"low"},{"id":"c4","text":"Proof of address must be dated within the last three months and can only be submitted after Standard.","sourceIds":["bybit-kyc-howto","bybit-kyc-faq"],"risk":"low"},{"id":"c5","text":"VIP daily withdrawal limits run from 8M USDT (VIP 1-3) to 60M USDT (PRO 6); VIP defaults stay at 1M/2M until raised manually.","sourceIds":["bybit-kyc-faq"],"risk":"low"},{"id":"c6","text":"Verification generally takes about 15 minutes and up to 48 hours.","sourceIds":["bybit-kyc-faq"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"bitget-kyc-level-1-vs-level-2-2026-documents-limits","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-12T20:53:38.000Z","updatedAt":"2026-10-12T20:53:38.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"7 min"},"author":"NexuAlpha Research Desk","title":{"en":"Bitget KYC Level 1 vs Level 2 in 2026: Documents, Withdrawal Limits and What You Can Do Without KYC","zh-Hans":"Bitget 实名认证一级和二级怎么分？2026 年所需材料、提现额度和不认证能做什么"},"summary":{"en":"Bitget has one individual KYC, not Level 1 and 2. Verified limits run 3M-20M USDT a day by VIP level; no deposits or trading without KYC. Documents, POA, EDD.","zh-Hans":"Bitget 现在的帮助中心里，个人账户没有\"一级认证\"\"二级认证\"这种编号：只有一次\"个人认证\"，填国家、证件类型和姓名，拍证件，再做人脸识别；通过之后，24 小时提现额度按 VIP 等级走，VIP 0 是 300 万 USDT，最高 VIP 7 是 2000 万 USDT。 不做认证基本没法用：Bitget 从 2024 年 1 月 1 日起把身份认证设为充币和交易等核心服务的前提。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"Bitget describes one individual verification rather than numbered Level 1 and Level 2; proof of address and EDD are separate requests sent to some users.","sourceIds":["bitget-kyc-faq","bitget-poa","bitget-edd-faq"],"risk":"medium"},{"id":"c2","text":"Since 1 January 2024 identity verification is required for crypto deposits and trading on Bitget.","sourceIds":["bitget-kyc-faq","bitget-academy-kyc"],"risk":"low"},{"id":"c3","text":"Verified 24-hour withdrawal limits run from 3 million USDT at VIP 0 to 20 million USDT at VIP 7.","sourceIds":["bitget-kyc-faq","bitget-vip-fee-api"],"risk":"low"},{"id":"c4","text":"Bitget's January 2025 academy guide says verification raises a VIP 0 account's daily withdrawal limit from 20,000 USDT to 3 million USDT.","sourceIds":["bitget-academy-kyc"],"risk":"medium"},{"id":"c5","text":"Bitget quotes KYC review times of up to 60 minutes (FAQ), within one hour and no more than four hours (academy), and typically one business day (step-by-step guides).","sourceIds":["bitget-kyc-faq","bitget-academy-kyc","bitget-kyc-web","bitget-kyc-app"],"risk":"low"},{"id":"c6","text":"Proof of address must show full name, address and issue date, be issued within the last three months, and match the KYC name.","sourceIds":["bitget-poa"],"risk":"low"},{"id":"c7","text":"EDD asks for source of funds or wealth evidence in JPG, PNG or PDF, files over 20 MB split; trading may be restricted if EDD is late.","sourceIds":["bitget-edd-faq"],"risk":"low"},{"id":"c8","text":"One verified account per user, sub-accounts inherit access, five attempts per 24 hours, 18+, restricted regions include the US, Canada, France, Germany, Hong Kong, Singapore and Japan.","sourceIds":["bitget-kyc-faq","bitget-kyc-rejected"],"risk":"low"},{"id":"c9","text":"A verification reset makes the account unverified, usually takes 1-3 business days, and a different UID needs approval and a 30-day wait.","sourceIds":["bitget-kyc-reset"],"risk":"low"},{"id":"c10","text":"Bitget invite code nexu888 returns up to 60% of trading fees, settled daily.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"evernorth-xrpn-stock-nasdaq-debut-vs-buying-xrp","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-12T20:52:17.000Z","updatedAt":"2026-10-12T20:52:17.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"6 min"},"author":"NexuAlpha Research Desk","title":{"en":"Evernorth (XRPN) Stock Starts Trading on Nasdaq: Is Buying XRPN the Same as Buying XRP? (October 2026)","zh-Hans":"Evernorth（XRPN）在纳斯达克上市：买 XRPN 股票等于买 XRP 吗？（2026 年 10 月）"},"summary":{"en":"Evernorth's XRPN closed its Nasdaq debut at $16.91, about twice the XRP behind each share. What you own, the float, lock-ups, warrants, and XRPN vs XRP.","zh-Hans":"不等于。XRPN 是 Evernorth 这家公司的股票，公司手里大约有 4.73 亿枚 XRP 和一部分现金，你买到的是公司股权，而不是 XRP 本身；上市首日收盘价 16.91 美元，大约是每股背后 XRP 价值的两倍。如果你只想跟随 XRP 的价格涨跌，直接在交易所买 XRP 更直接，XRPN 在此之上还叠加了溢价、极小的流通盘和未来解禁带来的抛压。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"Evernorth's merger with Armada Acquisition Corp. II closed on 9 October 2026 and XRPN began trading on Nasdaq on 12 October.","sourceIds":["sec-evernorth-8k","nasdaq-xrpn-quote","decrypt-evernorth"],"risk":"low"},{"id":"c2","text":"XRPN closed its first session at $16.91, down 1.05%, after trading between $16.39 and $19.38.","sourceIds":["nasdaq-xrpn-quote"],"risk":"low"},{"id":"c3","text":"Evernorth holds about 473 million XRP.","sourceIds":["decrypt-evernorth","cointelegraph-evernorth"],"risk":"medium"},{"id":"c4","text":"22,268,905 Class A shares, 32,211,992 Class C shares and 24,669,868 company units were outstanding at closing, about 5.98 XRP per economic interest by our arithmetic.","sourceIds":["sec-evernorth-8k","decrypt-evernorth"],"risk":"medium"},{"id":"c5","text":"80.3% of SPAC shares with redemption rights were redeemed at about $10.58 each, $195.39 million in total.","sourceIds":["sec-evernorth-8k"],"risk":"low"},{"id":"c6","text":"SBI Holdings holds 39.9% of voting Class A shares; Ripple, the Larsen-linked trust and the sponsor are locked up for six months after closing.","sourceIds":["sec-evernorth-8k"],"risk":"low"},{"id":"c7","text":"11,739,645 warrants exercisable at $11.50 are outstanding.","sourceIds":["sec-evernorth-8k"],"risk":"low"},{"id":"c8","text":"OKX invite code nexu888 returns up to 40% of trading fees.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["okx","binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"how-to-buy-us-stocks-with-usdc-on-bybit","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-12T20:51:27.000Z","updatedAt":"2026-10-12T20:51:27.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"5 min","es":"8 min","pt-BR":"7 min","id":"6 min","vi":"10 min"},"author":"NexuAlpha Research Desk","title":{"en":"How to Buy US Stocks With USDC on Bybit: Step-by-Step Guide (2026)","zh-Hans":"怎么在 Bybit 用 USDC 买美股：完整步骤（2026）","es":"Cómo comprar acciones de EE. UU. con USDC en Bybit: guía paso a paso (2026)","pt-BR":"Como comprar ações americanas com USDC na Bybit: passo a passo (2026)","id":"Cara Beli Saham AS Pakai USDC di Bybit: Langkah Lengkap untuk Pengguna Indonesia (2026)","vi":"Cách mua cổ phiếu Mỹ bằng USDC trên Bybit: hướng dẫn từng bước (2026)"},"summary":{"en":"Six steps to buy US stocks with USDC on Bybit: KYC Level 2, UTA, W-8BEN, convert USDC to USD fee-free, then trade 1,000+ stocks from $5 with no commission.","zh-Hans":"在 Bybit 用 USDC 买美股，顺序是：完成 KYC 二级认证、把账户升级为统一交易账户（UTA）、在“股票”页面签署经纪协议并提交 W-8BEN 税表、用 Bybit 闪兑把 USDC 换成美元（官方说明 USDC 换美元免手续费），然后进入 TradFi > 股票，选代码下单即可。","es":"Para comprar acciones de EE. UU.","pt-BR":"Para comprar ações dos EUA com USDC na Bybit, faça o KYC nível 2, use a Conta de Trading Unificada, envie o W-8BEN, converta USDC em USD pelo Bybit Convert sem taxa e opere em TradFi > Ações.","id":"Untuk membeli saham AS dengan USDC di Bybit, selesaikan KYC Level 2, pakai Unified Trading Account, isi W-8BEN, tukar USDC ke USD lewat Bybit Convert tanpa biaya, lalu pasang order di TradFi > Saham.","vi":"Để mua cổ phiếu Mỹ bằng USDC trên Bybit, bạn cần KYC cấp 2, dùng Tài khoản Giao dịch Hợp nhất, nộp mẫu W-8BEN, đổi USDC sang USD miễn phí bằng Bybit Chuyển đổi rồi đặt lệnh trong TradFi > Cổ phiếu."},"availableLocales":["en","zh-Hans","es","pt-BR","id","vi"],"claims":[{"id":"c1","text":"Bybit Stocks requires KYC Level 2, a supported country of residence and a Unified Trading Account.","sourceIds":["bybit-learn-how-to"],"risk":"low"},{"id":"c2","text":"Non-US persons must submit a W-8BEN and accept brokerage terms before the first trade.","sourceIds":["bybit-learn-how-to"],"risk":"low"},{"id":"c3","text":"Bybit Stocks settles in USD; USDC converts to USD via Bybit Convert with zero fees; fractional orders from $5; no minimum balance.","sourceIds":["bybit-learn-how-to"],"risk":"low"},{"id":"c4","text":"Sessions: pre-market about 4:00-9:30, regular 9:30-16:00, post-market 16:00-20:00, overnight 20:00-4:00 ET; only limit orders outside regular hours; T+1 settlement; GTC cancelled after 90 days.","sourceIds":["bybit-learn-how-to"],"risk":"low"},{"id":"c5","text":"Launched 12 October 2026 with 1,000+ US stocks and ETFs, zero commission, shares executed and held in custody by Alpaca; Infra Capital Limited is the introducing broker (FSC Mauritius GB23202169).","sourceIds":["bybit-prnewswire"],"risk":"low"},{"id":"c6","text":"Bybit posted a 'Full Stocks Ahead: Share 150,000 USDC' campaign and listed five TradFi perpetuals on 12 October 2026.","sourceIds":["bybit-announcement-feed"],"risk":"low"},{"id":"c7","text":"Bybit sign-up code 48553.","sourceIds":["nexualpha-partners"],"risk":"low"},{"id":"c8","text":"Bybit posted a Vietnamese announcement of the US stocks and ETFs launch with a region-availability disclaimer; the vi-VN feed carries no Full Stocks Ahead post.","sourceIds":["bybit-announcement-feed-vi"],"risk":"low"},{"id":"c9","text":"Bybit P2P listed USDC ads priced in VND at about 26,100-26,600 VND per USDC on 13 October 2026.","sourceIds":["bybit-p2p-vnd"],"risk":"medium"},{"id":"c10","text":"The Vietnamese Bybit Learn guide repeats the KYC Level 2, UTA, W-8BEN, USD funding and session requirements.","sourceIds":["bybit-learn-how-to-vi"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"okx-kyc-level-1-vs-level-2-2026-documents-limits","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-12T18:54:14.000Z","updatedAt":"2026-10-12T18:54:14.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"6 min"},"author":"NexuAlpha Research Desk","title":{"en":"OKX KYC Level 1 vs Level 2 in 2026: What Replaced the Levels, Which Documents You Need and Your Real Withdrawal Limit","zh-Hans":"OKX 实名认证一级和二级还有吗？2026 年的认证流程、所需材料和真实提现额度"},"summary":{"en":"OKX no longer splits individual KYC into Level 1 and Level 2: one verification unlocks trading and withdrawals. Documents, fee-tier withdrawal limits, POA, SoF checks.","zh-Hans":"在 OKX 全球站，个人账户已经不再区分\"一级认证\"和\"二级认证\"：你只需要完成一次身份认证（基本信息、政府签发的证件、实时自拍，部分地区还要地址证明），通过后就能交易、充值和提现。 认证之后每 24 小时能提多少币，取决于你的手续费等级，而不是认证等级；okx. com/fees 费率表数据里，普通用户的 24 小时提现额度是 1000 万美元。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"OKX individual accounts complete one identity verification, after which they can trade, deposit and withdraw.","sourceIds":["okx-verify-individual"],"risk":"low"},{"id":"c2","text":"OKX's 24-hour crypto withdrawal limit is determined by the fee tier; the fee schedule data lists $10M for Regular users up to $80M for VIP 8 and VIP 9.","sourceIds":["okx-beginner-guide","okx-fees"],"risk":"medium"},{"id":"c3","text":"Proof of address must generally be issued within 3 months (6 months for EEA); mobile phone bills are not accepted.","sourceIds":["okx-verify-individual","okx-poa"],"risk":"low"},{"id":"c4","text":"The Source of Funds / Source of Wealth task is different from identity verification and does not by itself mean wrongdoing.","sourceIds":["okx-sof-sow"],"risk":"low"},{"id":"c5","text":"OKX reviews applications within 24 hours; users must be 18+; Türkiye and the UAE have specific document requirements.","sourceIds":["okx-verify-individual","okx-eligibility-review","okx-beginner-guide"],"risk":"low"},{"id":"c6","text":"One primary personal account per identity under the same OKX entity; accounts cannot be merged as self-service.","sourceIds":["okx-identity-linked"],"risk":"low"},{"id":"c7","text":"OKX invite code nexu888 returns up to 40% of trading fees, settled hourly.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"what-is-binance-ai-how-to-turn-it-on-october-2026","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-12T18:54:14.000Z","updatedAt":"2026-10-12T18:54:14.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"What Is Binance AI? How to Turn It On, What It Shows You and What It Won't Do (October 2026)","zh-Hans":"币安 AI 是什么？怎么开启、能看到什么、不能替你做什么（2026 年 10 月）"},"summary":{"en":"Binance AI launched globally on 12 Oct 2026: adaptive layout, 4-hour market briefs, voice alerts, PNL recap. How to get it, the 20 USDC feedback contest and Auto Order Routing.","zh-Hans":"币安 AI（Binance AI）是币安 App 和网页版里的一组个性化功能，2026 年 10 月 12 日在全球正式上线，此前从 9 月起做过一轮内测：界面会围绕你持有和关注的资产自动重新排列，每四小时生成一份 AI 市场简报，支持语音价格提醒、昨日盈亏回顾和引导式提示。现在不需要再申请资格，把币安 App 更新到最新版，功能推送到你的账户后就会根据使用习惯自动调整。它不会替你下单，只负责解释、汇总和提醒，交易仍然由你自己操作。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"Binance introduced Binance AI globally on 12 October 2026 with a progressive rollout to eligible users who update the app.","sourceIds":["binance-ai-launch"],"risk":"low"},{"id":"c2","text":"Features include adaptive UI, Yesterday's PNL, Top movers, voice Smart alerts, Smart tooltips, Master trade and a Market brief refreshed every four hours.","sourceIds":["binance-ai-launch"],"risk":"low"},{"id":"c3","text":"The September 2026 beta was limited to verified users with rolling, non-guaranteed places.","sourceIds":["binance-ai-beta"],"risk":"low"},{"id":"c4","text":"Auto Order Routing charges one standard spot fee, no commission on the intermediary conversion, toggled in Trading Mode; price improvement not guaranteed.","sourceIds":["binance-auto-order-routing"],"risk":"low"},{"id":"c5","text":"The feedback campaign runs 12-18 October UTC, picks 25 users for 20 USDC each, and excludes US, UK, EEA, Hong Kong and Singapore.","sourceIds":["binance-ai-feedback"],"risk":"low"},{"id":"c6","text":"Binance says prompts may be used for training and AI outputs are not guaranteed.","sourceIds":["binance-ai-launch"],"risk":"low"},{"id":"c7","text":"Binance referral code 11350287 returns up to 25% of trading fees, settled hourly.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"bybit-referral-code-2026-how-to-use-at-sign-up","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-12T16:55:36.000Z","updatedAt":"2026-10-12T16:55:36.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"6 min"},"author":"NexuAlpha Research Desk","title":{"en":"Bybit Referral Code 2026: How to Use It at Sign-Up, and the 14-Day Fix If You Forgot","zh-Hans":"Bybit 邀请码 2026：注册时填在哪里，忘填了还有 14 天补救期"},"summary":{"en":"Bybit referral code 48553: enter it before you press Sign Up. Forgot it? Main accounts can add an affiliate code within 14 days. Steps, KYC levels, limits, FAQ.","zh-Hans":"Bybit 邀请码就是注册页\"推荐码 / 邀请码\"一栏里要填的那串字符，必须在点击\"注册\"之前填好；NexuAlpha 的 Bybit 邀请码是 48553，用链接 https://www. bybit. com/register? affiliate_id=48553 打开注册页会自动带上。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"The referral or affiliate code must be entered before pressing Sign Up Now; afterwards it cannot be added, modified or deleted through registration.","sourceIds":["bybit-register-guide","bybit-account-settings-faq"],"risk":"low"},{"id":"c2","text":"A main account with no code can add a Bybit Affiliate code within 14 days of registration via Join an Affiliate's Community; it cannot be changed afterwards and Referral Program codes are not supported.","sourceIds":["bybit-add-affiliate-code"],"risk":"low"},{"id":"c3","text":"The Referral Program pays the sharer a one-time bonus; the Affiliate Program pays ongoing commission on trading fees.","sourceIds":["bybit-affiliate-faq"],"risk":"low"},{"id":"c4","text":"Standard KYC is mandatory for all Bybit products; non-VIP daily withdrawal limits are 20K USDT unverified, 1M Standard and 2M Advanced/Pro; KYC takes about 15 minutes, up to 48 hours.","sourceIds":["bybit-kyc-faq","bybit-kyc-benefits"],"risk":"low"},{"id":"c5","text":"NexuAlpha's Bybit code is 48553; Bybit base fees 0.10%/0.10% spot and 0.02%/0.055% perpetuals.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"why-is-crypto-down-today-bitcoin-oil-cpi-solana-longs","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-12T16:55:36.000Z","updatedAt":"2026-10-12T16:55:36.000Z","readTime":"5 min","readTimeByLocale":{"en":"5 min","zh-Hans":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"Why Is Crypto Down Today? Bitcoin Slips Below $83,000 as Oil Jumps Before CPI, and Solana Longs Take the Hit (12 October 2026)","zh-Hans":"币圈今天为什么跌？油价在 CPI 前跳涨，比特币跌回 8.3 万美元下方，SOL 多头爆仓最多（2026 年 10 月 12 日）"},"summary":{"en":"12 Oct 2026: BTC slipped from $84,352 to $82,640 as oil jumped before Wednesday's CPI; SOL -3.4%, $6.8M liquidated in 4 hours, 93% longs, SOL nearly half.","zh-Hans":"2026 年 10 月 12 日加密市场下跌，直接原因是宏观：乌克兰能源设施和霍尔木兹海峡油轮再遭袭击，油价跳涨，而美国通胀数据两天后就要公布，比特币把本周初的反弹吐了回去。 币安现货上 BTC 先摸到 84,352 美元，到北京时间 13 日 00:48（UTC 16:48）回落到约 82,640 美元，24 小时跌 1.5%。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"BTC touched $84,352 on Binance and was about $82,640 at 16:48 UTC on 12 October 2026, down 1.5% in 24 hours; SOL fell 3.4% and XRP 3.5%.","sourceIds":["binance-spot-ticker","nexualpha-market-events"],"risk":"low"},{"id":"c2","text":"Oil rose after new strikes in Ukraine and a tanker attack in the Strait of Hormuz; Brent reached $107.25, highest since 16 September; CPI is due Wednesday.","sourceIds":["cointelegraph-btc-oil"],"risk":"low"},{"id":"c3","text":"Decrypt's Fear and Greed Index fell to 56 from 82 in August; alternative.me reads 69.","sourceIds":["decrypt-fear-greed","alternative-fng"],"risk":"low"},{"id":"c4","text":"NexuAlpha counted $6.79M of liquidations in four hours, 93% longs, with OKX SOL at $3.30M.","sourceIds":["nexualpha-market-events"],"risk":"low"},{"id":"c5","text":"70% of Binance SOL perpetual accounts were long; open interest flat in coins at about 8.51M SOL.","sourceIds":["binance-sol-futures"],"risk":"low"}],"relatedVenues":["binance","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"usdt-withdrawal-fees-binance-vs-bitget-by-network-2026","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-12T14:56:27.000Z","updatedAt":"2026-10-12T14:56:27.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"5 min","ru":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"USDT Withdrawal Fees on Binance vs Bitget in 2026: Every Network Compared","zh-Hans":"2026 年币安和 Bitget 提 USDT 手续费多少？各条链逐一对比","ru":"Комиссия за вывод USDT на Binance и Bitget в 2026 году: таблица по всем сетям"},"summary":{"en":"USDT withdrawal fees on Binance and Bitget for every network on 12 Oct 2026: BEP20 0.01, TRC20 1.5, ERC20 0.5 vs 2 USDT, plus minimums, BTC, ETH and USDC.","zh-Hans":"2026 年 10 月 12 日，从币安或 Bitget 提 USDT，最便宜的都是 BNB Smart Chain（BEP20），两家都只收 0.01 USDT；其次是 Plasma 的 0.012 USDT 和 Polygon 的 0.07 USDT。 大家最习惯用的波场 TRC20 两家都收 1.5 USDT，差距最大的是以太坊主网 ERC20：币安 0.5 USDT，Bitget 2 USDT。","ru":"Дешевле всего выводить USDT с Binance и Bitget через BEP20 — 0,01 USDT на обеих биржах; TRC20 стоит 1,5 USDT, а в Ethereum Binance берёт 0,5 USDT против 2 USDT у Bitget."},"availableLocales":["en","zh-Hans","ru"],"claims":[{"id":"c1","text":"On 12 October 2026 USDT withdrawals over BEP20 cost 0.01 USDT on both Binance and Bitget; TRC20 costs 1.5 USDT on both.","sourceIds":["binance-networks","bitget-coins"],"risk":"low"},{"id":"c2","text":"ERC20 USDT withdrawals cost 0.5 USDT on Binance and 2 USDT on Bitget.","sourceIds":["binance-networks","bitget-coins"],"risk":"low"},{"id":"c3","text":"Bitget's USDT withdrawal minimum is 10 USDT on every network; Binance's is 1 USDT on BEP20 and 3-5 USDT elsewhere.","sourceIds":["binance-networks","bitget-coins"],"risk":"low"},{"id":"c4","text":"Bitget is cheaper on Arbitrum, Optimism, TON and Aptos; Binance is cheaper on Ethereum mainnet and Solana for USDT.","sourceIds":["binance-networks","bitget-coins"],"risk":"low"},{"id":"c5","text":"BTC Lightning withdrawals were open on Binance and closed on Bitget at check time.","sourceIds":["binance-networks","bitget-coins"],"risk":"low"},{"id":"c6","text":"Bitget code nexu888 returns up to 60% of trading fees; Binance code 11350287 returns 25%.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["binance","bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"why-is-strk-down-today-starknet-gives-back-l1-rally","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-12T14:56:27.000Z","updatedAt":"2026-10-12T14:56:27.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"Why Is STRK Down Today? Starknet Gives Back a Quarter of Its Layer-1 Rally While Dip Buyers Turn Long (12 October 2026)","zh-Hans":"STRK 今天为什么跌？Starknet 回吐四分之一\"转 L1\"涨幅，抄底的人开始做多（2026 年 10 月 12 日）"},"summary":{"en":"STRK fell 17% on 12 Oct 2026, from a $0.1265 peak to $0.093, with no new Starknet news; open interest down 22%, funding positive, and more accounts now long.","zh-Hans":"Starknet（STRK）在 2026 年 10 月 12 日 24 小时内下跌约 17%，从 UTC 零点算起跌了约 24%。 原因是项目方宣布\"正在认真考虑成为 L1\"之后的四天连涨，已经找不到新的买盘：币价在 10 月 11 日深夜见顶 0.1265 美元，到北京时间 22:50（UTC 14:50）回落到 0.093 美元，期间项目方没有发布任何新消息。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"STRK fell from a $0.1265 peak on 11 October to about $0.093 at 14:50 UTC on 12 October 2026, about 17% over 24 hours.","sourceIds":["binance-strk-spot","okx-strk"],"risk":"low"},{"id":"c2","text":"STRK rose 151% from the 7 October close to the 11 October close.","sourceIds":["binance-strk-spot"],"risk":"low"},{"id":"c3","text":"Binance STRK open interest fell from 495.8M tokens ($59.2M) to 440.3M ($46.0M).","sourceIds":["binance-strk-futures"],"risk":"low"},{"id":"c4","text":"Binance STRK funding turned from negative to +0.005% per 4-hour period from 20:00 UTC on 11 October; OKX settled at +0.005%.","sourceIds":["binance-strk-futures","okx-strk"],"risk":"low"},{"id":"c5","text":"The share of Binance accounts long STRK rose from 37.5% to 42.2% on 12 October.","sourceIds":["binance-strk-futures"],"risk":"low"},{"id":"c6","text":"Starknet said it is actively considering becoming an L1, with a 2027 target for full quantum resistance.","sourceIds":["decrypt-starknet-l1"],"risk":"low"},{"id":"c7","text":"NexuAlpha counted $15.1M of liquidations in four hours, 98% longs.","sourceIds":["nexualpha-market-events"],"risk":"low"}],"relatedVenues":["binance","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"why-is-gtc-up-gitcoin-upbit-listing-funding-floor","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-12T12:56:50.000Z","updatedAt":"2026-10-12T12:56:50.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"Why Is GTC Up 50% Today? Upbit Listed Gitcoin, and Binance Futures Funding Hit the -2% Floor (12 October 2026)","zh-Hans":"GTC 今天为什么涨 50%？Upbit 上线 Gitcoin，币安合约资金费率打到 -2% 下限（2026 年 10 月 12 日）"},"summary":{"en":"Gitcoin (GTC) rose 50-60% on 12 October 2026 after Upbit listed it against the Korean won; Binance futures trade 6% below spot and funding is pinned at the -2% floor.","zh-Hans":"Gitcoin（GTC）10 月 12 日一天涨了约五到六成，直接原因是韩国最大交易所 Upbit 在北京时间 18:00（UTC 10:00）宣布把 GTC 加入韩元和 USDT 市场，18:30 开盘交易。 币安现货在公告后的 15 分钟内从 0.166 美元冲到 0.393 美元，随后回吐约四分之一涨幅，北京时间 20:51 报 0.293 美元。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"Upbit announced GTC KRW and USDT markets at 19:00 KST (10:00 UTC) on 12 October 2026 with trading from 19:30 KST.","sourceIds":["upbit-notice-6653"],"risk":"low"},{"id":"c2","text":"Binance GTC spot rose from $0.16579 to $0.393 inside the 10:00 UTC 15-minute candle and traded near $0.293 at 12:51 UTC; 24h spot +61%, perp +52%.","sourceIds":["binance-gtc","nexualpha-market-events"],"risk":"low"},{"id":"c3","text":"Binance GTC perpetual predicted funding for 16:00 UTC was -2%, the floor; the perpetual traded about 5.8% below the index (our arithmetic).","sourceIds":["binance-gtc"],"risk":"low"},{"id":"c4","text":"Binance GTC open interest rose 63% in coins and 2.7x in dollars between 10:00 and 12:00 UTC; long accounts fell to 38-39%.","sourceIds":["binance-gtc"],"risk":"low"},{"id":"c5","text":"Upbit KRW-GTC peaked at 494 won (about $0.367 at 1,348 won per USDT, our arithmetic) and turned over 49.5 billion won.","sourceIds":["upbit-ticker"],"risk":"low"},{"id":"c6","text":"No GTC perpetual was found on OKX, Bybit or Hyperliquid at 12:51 UTC.","sourceIds":["other-venues-check"],"risk":"low"},{"id":"c7","text":"Binance code 11350287 returns 25% of trading fees, settled hourly.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"altcoins-outrun-bitcoin-near-fil-zro-thin-liquidity-before-cpi","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-12T10:55:47.000Z","updatedAt":"2026-10-12T10:55:47.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"6 min","vi":"8 min"},"author":"NexuAlpha Research Desk","title":{"en":"Why Are Altcoins Up While Bitcoin Stalls Near $83,500? NEAR, FIL and ZRO Rally on Thin Liquidity Before Wednesday's CPI (12 October 2026)","zh-Hans":"比特币卡在 8.35 万美元，山寨币为什么在涨？NEAR、FIL、ZRO 在薄流动性中拉升，周三 CPI 前要注意什么（2026 年 10 月 12 日）","vi":"Vì sao altcoin tăng khi Bitcoin đứng yên quanh 83.500 USD? NEAR, FIL, ZRO bứt phá trên thanh khoản mỏng trước CPI Mỹ (12/10/2026)"},"summary":{"en":"Altcoins outran bitcoin on 12 October 2026: ZRO +18%, FIL +14%, NEAR +10% at an 11-month high, on thin liquidity as bitcoin ETFs lost $681M last week. Our liquidation and funding data, and what to watch before CPI.","zh-Hans":"10 月 12 日周一，小币跑赢了比特币：CoinDesk 覆盖 80 个中小资产的指数 24 小时涨约 3%，五大资产指数只涨 1.2%，比特币在 8.35 万美元附近横盘。 Binance 合约数据（北京时间 18:49）显示 ZRO 涨 18.4%、FIL 涨 14.5%、NEAR 涨 10.3%，NEAR 创下至少 11 个月来的最高价。","vi":"Ngày 12/10/2026, chỉ số 80 coin nhỏ của CoinDesk tăng khoảng 3% so với 1,2% của nhóm 5 đồng lớn trong khi Bitcoin đi ngang quanh 83.500 USD."},"availableLocales":["en","zh-Hans","vi"],"claims":[{"id":"c1","text":"CoinDesk 80 rose about 3% in 24 hours vs 1.2% for the CoinDesk 5 as bitcoin traded near $83,500 on 12 October 2026.","sourceIds":["coindesk-altcoins-thin","binance-futures"],"risk":"low"},{"id":"c2","text":"ZRO +18.4%, FIL +14.5%, NEAR +10.3% on Binance perpetuals at 10:49 UTC; NEAR's high was the highest in 330 daily candles.","sourceIds":["binance-futures","coindesk-altcoins-thin"],"risk":"low"},{"id":"c3","text":"Spot bitcoin ETFs had $681 million of net outflows last week, the most since June.","sourceIds":["coindesk-altcoins-thin"],"risk":"medium"},{"id":"c4","text":"NexuAlpha's lower-bound tracker recorded $33.8 million of liquidations in 24 hours, about 70% shorts; $4.47 million in four hours, about 72% longs.","sourceIds":["nexualpha-market-events"],"risk":"low"},{"id":"c5","text":"Hyperliquid lists NEAR, FIL, ZRO and ZEC perpetuals.","sourceIds":["hyperliquid-meta"],"risk":"low"}],"relatedVenues":["binance","okx","hyperliquid"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"standard-chartered-rlusd-custody-lmax-collateral-what-it-means","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-12T10:52:27.000Z","updatedAt":"2026-10-12T10:52:27.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"6 min"},"author":"NexuAlpha Research Desk","title":{"en":"Standard Chartered Now Holds Ripple's RLUSD for Institutions, and LMAX Plans to Accept It as Collateral: What It Means (12 October 2026)","zh-Hans":"渣打银行开始托管 Ripple 稳定币 RLUSD，LMAX 计划接受它作保证金：这意味着什么（2026 年 10 月 12 日）"},"summary":{"en":"Standard Chartered launched institutional custody for Ripple's RLUSD on the XRP Ledger on 12 October 2026 and plans, with LMAX, to let it back trades as collateral. What is live, what is not, and why it matters.","zh-Hans":"渣打银行 10 月 12 日宣布，面向机构客户的 RLUSD（Ripple 发行的美元稳定币，XRP Ledger 版本）托管服务已经上线，由其迪拜国际金融中心（DIFC）分行提供，受迪拜金融服务管理局（DFSA）监管。 同一份公告里，LMAX Group、Ripple 和渣打还表示，打算让 RLUSD 成为 LMAX 指定产品的合格保证金：代币留在银行托管，LMAX 只“看到”它的价值。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"Standard Chartered's custody for RLUSD on the XRP Ledger is live for eligible institutional clients through its DFSA-regulated DIFC branch.","sourceIds":["lmax-joint-release","cointelegraph-sc-rlusd"],"risk":"low"},{"id":"c2","text":"LMAX, Ripple and Standard Chartered intend to make RLUSD eligible collateral on agreed LMAX products via collateral mirroring, subject to documentation, testing, regulation and approvals.","sourceIds":["lmax-joint-release","cointelegraph-sc-rlusd"],"risk":"low"},{"id":"c3","text":"RLUSD circulating supply was about $2.45 billion on 12 October 2026, $1.30 billion on Ethereum and $1.14 billion on XRPL.","sourceIds":["defillama-stablecoins"],"risk":"low"},{"id":"c4","text":"Ripple and LMAX announced a partnership in January 2026.","sourceIds":["cointelegraph-sc-rlusd"],"risk":"low"},{"id":"c5","text":"OKX sign-up code nexu888.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"bybit-us-stocks-etfs-usdc-alpaca-what-you-own","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-12T08:55:53.000Z","updatedAt":"2026-10-12T08:55:53.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"Bybit Now Sells Real U.S. Stocks and ETFs for USDC: What You Own, Who Holds It and What It Costs (12 October 2026)","zh-Hans":"Bybit 开放用 USDC 买美股和 ETF：你买到的是什么、股票由谁托管、成本在哪里（2026 年 10 月 12 日）"},"summary":{"en":"Bybit launched trading in 1,000+ U.S. stocks and ETFs for USDC on 12 October 2026, custodied by Alpaca Securities; here is what you own, the zero-commission terms and what to check.","zh-Hans":"2026 年 10 月 12 日，Bybit 上线股票交易，符合条件的用户可以用账户里的 USDC 买卖 1,000 多只美国上市股票和 ETF，包括苹果、英伟达、特斯拉、美光和景顺 QQQ ETF。 和 Bybit 已有的代币化股票、传统金融永续合约不同，这个产品给的是底层股票的经济权益：订单经一家受毛里求斯监管的介绍经纪商发出，由美国券商 Alpaca Securities 执行、清算并托管，Alpaca 是 FINRA 和 SIPC 会员。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"Bybit launched trading in 1,000+ U.S. stocks and ETFs for eligible KYC users, paid in USDC, on 12 October 2026.","sourceIds":["bybit-prnewswire","bybit-announcement-feed"],"risk":"low"},{"id":"c2","text":"Orders are executed, cleared and custodied by Alpaca Securities LLC, a FINRA/SIPC member; the introducing broker is Infra Capital Limited, regulated by the FSC Mauritius (GB23202169).","sourceIds":["bybit-prnewswire"],"risk":"low"},{"id":"c3","text":"Zero commission, 24/5 trading including pre-market and after-hours, fractional shares, dividends in USDC, voting rights later.","sourceIds":["bybit-prnewswire"],"risk":"low"},{"id":"c4","text":"Bybit listed TradFi perpetuals as recently as 9 October 2026.","sourceIds":["nexualpha-official-announcements"],"risk":"low"},{"id":"c5","text":"Bybit sign-up code 48553.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"reserve-rights-rsr-upbit-listing-46-percent-negative-funding","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-12T08:54:03.000Z","updatedAt":"2026-10-12T08:54:03.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"6 min","tr":"6 min"},"author":"NexuAlpha Research Desk","title":{"en":"Why Is RSR Up 46% Today? Upbit Listed Reserve Rights, and Shorts Now Pay Almost 2% Every Eight Hours (12 October 2026)","zh-Hans":"RSR 今天为什么涨 46%？Upbit 上线 Reserve Rights，空头每 8 小时要付近 2% 资金费（2026 年 10 月 12 日）","tr":"RSR Neden Yükseldi? Upbit Listelemesiyle %46 Artış ve %2'ye Yaklaşan Negatif Fonlama (12 Ekim 2026)"},"summary":{"en":"Reserve Rights (RSR) rose about 46% on 12 October 2026 after Upbit listed it against the Korean won; Binance funding hit -1.96% and open interest grew 4.4x in eight hours.","zh-Hans":"2026 年 10 月 12 日 Reserve Rights（RSR）24 小时上涨约 46%，直接原因是韩国最大交易所 Upbit 在北京时间 12:54（UTC 04:54）公告把 RSR 加入韩元和 USDT 市场，并于北京时间 13:05 开放交易。 币安现货在两小时内从约 0.00166 美元冲到 0.002999 美元，北京时间 16:48 回落到 0.00236 美元附近。","tr":"Reserve Rights (RSR), Upbit'in 12 Ekim 2026'da TSİ 07:54'te RSR'yi won ve USDT piyasalarına ekleyeceğini duyurmasıyla 24 saatte yaklaşık %46 yükseldi."},"availableLocales":["en","zh-Hans","tr"],"claims":[{"id":"c1","text":"Upbit announced RSR KRW and USDT markets at 13:54 KST (04:54 UTC) on 12 October 2026 with trading from 14:05 KST.","sourceIds":["upbit-notice-6651"],"risk":"low"},{"id":"c2","text":"RSR rose about 46-47% in 24 hours on Binance; spot high $0.002999, $0.00236 at 08:48 UTC.","sourceIds":["binance-rsr","nexualpha-market-events"],"risk":"low"},{"id":"c3","text":"Binance RSR perpetual funding settled at -1.96% at 08:00 UTC against a -2% floor; OKX settled at its -1% floor.","sourceIds":["binance-rsr","okx-rsr"],"risk":"low"},{"id":"c4","text":"Binance RSR open interest rose about 4.4x in coins between 00:00 and 08:48 UTC (our arithmetic).","sourceIds":["binance-rsr"],"risk":"low"},{"id":"c5","text":"Upbit KRW-RSR peaked at 4.98 won, about $0.0037 at 1,347 won per USDT (our arithmetic), and traded about 1.6% above Binance at 08:48 UTC.","sourceIds":["upbit-ticker","binance-rsr"],"risk":"low"},{"id":"c6","text":"Hyperliquid lists RSR with 3x max leverage and -0.1254% hourly funding.","sourceIds":["hyperliquid-rsr"],"risk":"low"},{"id":"c7","text":"OKX code nexu888 returns 40% of fees hourly; Hyperliquid code NEXU888; Bybit code 48553.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["binance","okx","hyperliquid","bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"france-crypto-self-custody-wallet-declaration-100000-euros-cf821","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-12T07:06:48.000Z","updatedAt":"2026-10-12T07:06:48.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"France Wants Self-Custody Crypto Wallets Over €100,000 Declared: What Amendment CF821 Says, the €10,000 Fine and What Happens Next (2026)","zh-Hans":"法国拟要求申报 10 万欧元以上的自托管加密钱包：CF821 修正案写了什么、最高罚 1 万欧元、接下来怎么走（2026）"},"summary":{"en":"France's Finance Committee backed amendment CF821: declare self-custody crypto wallets worth €100,000+ on 31 December or face up to €10,000 in fines. Plus the stablecoin swap tax, crypto exit tax and why none of it is law yet.","zh-Hans":"2026 年 10 月 9 日，法国国民议会财政委员会通过了 I-CF821 号修正案：法国纳税人自己保管、不在任何加密服务商处托管的钱包，如果 12 月 31 日的价值达到或超过 10 万欧元，就要向税务部门申报，不申报最高可罚 1 万欧元。这还不是法律。同一天晚上，财政委员会否决了 2027 年预算案的整个收入部分，国民议会全体会议将于 10 月 13 日（周二）从政府原始文本重新开始审议，所有加密相关修正案都必须重新提交、重新表决。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"Amendment I-CF821 requires declaring self-custody crypto wallets worth €100,000 or more on 31 December, amending CGI articles 1649 bis C and 1729 C ter.","sourceIds":["an-cf821"],"risk":"low"},{"id":"c2","text":"Sponsors cite €3.5 billion of crypto gains in 2021 versus €400 million of holdings declared; fine up to €10,000.","sourceIds":["an-cf821"],"risk":"low"},{"id":"c3","text":"The Finance Committee adopted CF821 on 9 October and rejected the revenue part of the 2027 budget by 31 votes to 3.","sourceIds":["clubic-budget-2027-crypto","ct-wallet-reporting"],"risk":"low"},{"id":"c4","text":"CF1826 would make crypto-to-stablecoin swaps taxable from 1 January 2027; CF1822 extends exit tax to crypto above €800,000.","sourceIds":["ct-stablecoin-swap-tax","clubic-budget-2027-crypto"],"risk":"low"},{"id":"c5","text":"The plenary starts on 13 October from the government's draft; amendments must be re-tabled; revenue debate until 19 October; 70 days to 10 December.","sourceIds":["clubic-budget-2027-crypto","ct-wallet-reporting"],"risk":"low"},{"id":"c6","text":"DAC8 reporting applies from 1 January 2026, with first exchanges due by September 2027.","sourceIds":["ct-stablecoin-swap-tax"],"risk":"low"},{"id":"c7","text":"OKX code nexu888 returns 40% of fees hourly.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"fsb-g20-stablecoin-cross-border-risks-what-it-means-for-usdt-usdc","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-12T07:06:48.000Z","updatedAt":"2026-10-12T07:06:48.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"6 min","id":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"FSB Warns the G20 About Stablecoin Cross-Border Risks: What the 12 October Note Says and What It Means for Your USDT and USDC (2026)","zh-Hans":"金融稳定委员会向 G20 警示稳定币跨境风险：10 月 12 日报告说了什么，你的 USDT、USDC 受不受影响（2026）","id":"FSB Peringatkan G20 soal Risiko Stablecoin Lintas Negara: Apa Artinya bagi Pemegang USDT di Indonesia Menjelang Aturan OJK 2027"},"summary":{"en":"The FSB told the G20 on 12 October 2026 that the $300 billion, 99% dollar-pegged stablecoin market lacks cross-border oversight and insolvency rules. What the note says, why it is not binding, and what holders should watch.","zh-Hans":"2026 年 10 月 12 日，金融稳定委员会（FSB）在 G20 财长和央行行长 10 月 15 日开会前，发布了主席、英格兰银行行长贝利（Andrew Bailey）致 G20 的信，并附上一份全球稳定币专题报告。 报告给出的数据是：稳定币总市值约 3,000 亿美元，其中 99% 锚定美元；大型稳定币的跨境监管、危机处置和破产安排“尚不成熟甚至还不存在”。 对普通持币人来说，今天什么都不会变：FSB 的文件没有法律约束力。","id":"FSB menerbitkan catatan stablecoin untuk G20 pada 12 Oktober 2026: pasar sekitar 300 miliar dolar AS, 99% dipatok ke dolar, dan negara berkembang menghadapi risiko substitusi mata uang serta arus modal."},"availableLocales":["en","zh-Hans","id"],"claims":[{"id":"c1","text":"The FSB published a Chair's letter and a stablecoin note on 12 October 2026 ahead of the G20 finance ministers' meeting on 15 October.","sourceIds":["fsb-press-12-2026","fsb-chair-letter"],"risk":"low"},{"id":"c2","text":"Stablecoin market about $300 billion in mid-2026, essentially unchanged from a year earlier, 99% pegged to the US dollar.","sourceIds":["fsb-stablecoin-note"],"risk":"low"},{"id":"c3","text":"Cross-border oversight, crisis management, accountability and cooperation in stress or insolvency remain immature or not yet developed.","sourceIds":["fsb-chair-letter","fsb-stablecoin-note"],"risk":"low"},{"id":"c4","text":"EMDEs face currency substitution, bank disintermediation and capital-flow challenges, so stablecoins could become systemic at a lower threshold.","sourceIds":["fsb-stablecoin-note"],"risk":"low"},{"id":"c5","text":"FSB activities are not binding and do not give rise to legal rights or obligations.","sourceIds":["fsb-stablecoin-note"],"risk":"low"},{"id":"c6","text":"OJK expects a stablecoin rule direction around January 2027 covering reserves, governance, consumer protection and redemption.","sourceIds":["antara-ojk-stablecoin"],"risk":"medium"},{"id":"c7","text":"OKX code nexu888 returns 40% of fees hourly; Bitget code nexu888 up to 60%.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["okx","bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"kucoin-stock-index-perps-skuu-2x-sk-hynix-20x-funding","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-12T04:57:35.000Z","updatedAt":"2026-10-12T04:57:35.000Z","readTime":"8 min","readTimeByLocale":{"en":"8 min","zh-Hans":"7 min"},"author":"NexuAlpha Research Desk","title":{"en":"KuCoin Lists 20x Perps on a 2x SK Hynix ETF, AppLovin, Moderna and SoFi: What You Are Trading, and Why SK Hynix Funding Just Jumped (12 October 2026)","zh-Hans":"KuCoin 上线 2 倍 SK 海力士 ETF 等股票永续，最高 20 倍：你交易的到底是什么，SK 海力士资金费率为何突然跳升（2026 年 10 月 12 日）"},"summary":{"en":"KuCoin lists 20x USDT perps on AppLovin, Moderna, SoFi, a Treasury index and the 2x SK Hynix ETF SKUU on 12 October 2026; what you trade, liquidation math and why SK Hynix funding jumped at Korea's open.","zh-Hans":"KuCoin 合约于 2026 年 10 月 12 日宣布，当天 UTC 09:00（北京时间 17:00）上线 5 个以 USDT 结算的“股票指数”永续合约：AppLovin（APPUSDT）、Moderna（MRNAUSDT）、SoFi（SOFIUSDT）、一个官方称跟踪 ICE 美国 20 年期以上国债指数的合约（TMFUSDT），以及跟踪 GraniteShares 2 倍做多 SK 海力士每日 ETF 的 SKUUUSDT。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"KuCoin lists APPUSDT, TMFUSDT, SKUUUSDT, MRNAUSDT and SOFIUSDT at 09:00 UTC on 12 Oct 2026 with up to 20x leverage.","sourceIds":["kucoin-announcement"],"risk":"low"},{"id":"c2","text":"The contracts are synthetic, USDT-settled, do not represent ownership and deliver no shares.","sourceIds":["kucoin-announcement"],"risk":"low"},{"id":"c3","text":"SKUUUSDTM has 5% initial and 2.5% maintenance margin, 0.02%/0.06% fees.","sourceIds":["kucoin-contract-skuu"],"risk":"low"},{"id":"c4","text":"SKUU seeks 2x SK Hynix daily performance via swaps totalling 200% notional; launched 14 Jul 2026.","sourceIds":["graniteshares-skuu"],"risk":"low"},{"id":"c5","text":"20x on SKUU is about 40x SK Hynix's daily move; ~2.5% cushion equals ~1.25% in SK Hynix (our arithmetic).","sourceIds":["kucoin-contract-skuu","graniteshares-skuu"],"risk":"medium"},{"id":"c6","text":"Binance SKHYNIXUSDT funding was 0% for eight weekend settlements, then +0.047398% at 04:00 UTC on 12 Oct.","sourceIds":["binance-skhynix"],"risk":"low"},{"id":"c7","text":"OKX warns leverage on its TQQQUSD leveraged-ETF X-Perp may amplify liquidation risk.","sourceIds":["okx-xperps-notice"],"risk":"low"},{"id":"c8","text":"OKX nexu888 returns 40% hourly; Bitget nexu888 up to 60% daily.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["kucoin","binance","okx","bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"wormhole-w-token-up-66-percent-why-funding-split-leverage","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-12T04:55:30.000Z","updatedAt":"2026-10-12T04:55:30.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"6 min","vi":"9 min"},"author":"NexuAlpha Research Desk","title":{"en":"Why Is Wormhole (W) Up 66% Today? Futures Did the Lifting, and Funding Now Points in Opposite Directions (12 October 2026)","zh-Hans":"Wormhole（W）一天涨 66% 是为什么？行情由合约推动，各平台资金费率方向相反（2026 年 10 月 12 日）","vi":"Vì sao Wormhole (W) tăng 66% hôm nay? Lực đẩy đến từ hợp đồng tương lai, funding rate trái chiều giữa các sàn (12/10/2026)"},"summary":{"en":"Wormhole's W token rose about 66% on 12 October 2026 without an official announcement; futures volume was 7.7x spot, open interest 2.7x, and funding split between Binance, OKX and Hyperliquid.","zh-Hans":"截至 2026 年 10 月 12 日北京时间 12:48（UTC 04:48），Wormhole 的代币 W 在 24 小时内上涨约 63% 到 66%，从约 0.0174 美元涨到 0.0283 美元，是 NexuAlpha 行情数据里涨幅最大的币种。 我们没有找到 Wormhole 官方发布的、能解释这波行情的新公告。","vi":"Token W của Wormhole tăng khoảng 63–66% trong 24 giờ đến 11:48 ngày 12/10/2026 giờ Việt Nam mà không có thông báo chính thức."},"availableLocales":["en","zh-Hans","vi"],"claims":[{"id":"c1","text":"W rose about 63% on Binance's 24h ticker and 65.97% in NexuAlpha's feed to about $0.0283 on 12 Oct 2026.","sourceIds":["binance-futures-w","nexualpha-market-events"],"risk":"low"},{"id":"c2","text":"Binance W perpetual volume was $263.9M vs $34.1M spot, about 7.7x (our arithmetic).","sourceIds":["binance-futures-w","binance-spot-w"],"risk":"low"},{"id":"c3","text":"Binance W open interest grew from about $8.9M to about $24.0M (our arithmetic from 844.05M W at $0.02838).","sourceIds":["binance-futures-w"],"risk":"low"},{"id":"c4","text":"Funding was -0.0055% on Binance, -0.0228% on OKX and +0.0398% per hour on Hyperliquid.","sourceIds":["binance-futures-w","okx-w-swap","hyperliquid-w"],"risk":"low"},{"id":"c5","text":"Binance's long/short account ratio fell from 1.70 to 0.88.","sourceIds":["binance-futures-w"],"risk":"low"},{"id":"c6","text":"No new official Wormhole announcement was found; latest announcement updated 7 Aug 2026.","sourceIds":["wormhole-blog"],"risk":"medium"},{"id":"c7","text":"OKX code nexu888 returns 40% of fees hourly; Hyperliquid code NEXU888.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["binance","okx","hyperliquid"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"sui-rally-samsung-wallet-usdc-hashi-data-network-price-stalls","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-12T02:58:46.000Z","updatedAt":"2026-10-12T02:58:46.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"5 min","tr":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"Why SUI Rose 57% in Four Weeks, and Why Samsung Wallet, Hashi and the $30 Million DATA Deal Have Not Pushed It Higher (October 2026)","zh-Hans":"SUI 四周涨 57%，为什么三星钱包、Hashi 和 3,000 万美元 DATA 投资都没再推高币价（2026 年 10 月）","tr":"SUI Neden Yükseldi, Neden Durdu? Samsung Wallet, Hashi ve 30 Milyon Dolarlık DATA Yatırımı Fiyatı Neden Taşımadı (Ekim 2026)"},"summary":{"en":"SUI rose about 57% in four weeks to 11 October 2026, but nearly all of it came before Sui's Samsung Wallet, Hashi and $30M DATA Network news; here are the numbers, why the token stalled and what to watch.","zh-Hans":"币安数据显示，SUI 在 2026 年 10 月 11 日收于 1.1305 美元，比四周前的 0.7209 美元上涨约 57%，但几乎全部涨幅都发生在 9 月 17 日至 27 日之间。","tr":"SUI dört haftada yaklaşık %57 yükseldi ama kazancın neredeyse tamamı 17–27 Eylül arasında geldi; 27 Eylül zirvesinden bu yana token yaklaşık %11 geriledi."},"availableLocales":["en","zh-Hans","tr"],"claims":[{"id":"c1","text":"SUI closed at $1.1305 on 11 October 2026, up 56.8% from $0.7209 on 14 September and 10.6% below its $1.2640 close on 27 September.","sourceIds":["binance-sui-data"],"risk":"low"},{"id":"c2","text":"Samsung Wallet supports USDC on Sui in the US at launch; the SUI token is not supported and users need no SUI to send USDC.","sourceIds":["sui-samsung"],"risk":"low"},{"id":"c3","text":"Hashi mainnet rolls out in phases this month with more than $500 million in committed capital; Anchorage Digital is a day-one partner.","sourceIds":["sui-hashi"],"risk":"low"},{"id":"c4","text":"Sui Foundation is investing $30 million in the DATA Network, whose chain will be retired as the protocol moves natively to Sui with $DATA carried over one-to-one.","sourceIds":["sui-data-network","theblock-data"],"risk":"low"},{"id":"c5","text":"Binance SUIUSDT open interest fell from about $171 million on 28 September to about $135 million on 12 October.","sourceIds":["binance-sui-data"],"risk":"low"},{"id":"c6","text":"OKX code nexu888 returns 40% of trading fees hourly; Bybit code 48553.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["okx","bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"okx-unitree-cxmt-a-share-x-perps-what-you-trade-risks","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-12T02:55:44.000Z","updatedAt":"2026-10-12T02:55:44.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"6 min"},"author":"NexuAlpha Research Desk","title":{"en":"OKX Lists Unitree and CXMT Stock Perps: What You Are Actually Trading on Two Chinese A-Share Names, and the Risks (2026)","zh-Hans":"OKX 上线宇树、长鑫 A 股 X-Perp 合约：你交易的到底是什么，风险在哪里（2026）"},"summary":{"en":"OKX launched USD-settled X-Perps on Unitree and CXMT on 12 October 2026. They trade 24/7 with leverage and funding while the A-shares trade four hours a day with a 20% limit; here is what you own and the risks.","zh-Hans":"OKX 于 2026 年 10 月 12 日宣布上线四个股票类 X-Perp 合约：CXMTUSD、BSPUSD、TQQQUSD 和 UNITREEUSD，当天北京时间 16:30 至 17:15 陆续开放交易。 它们是以美元结算、带资金费、到期日约在五年后的杠杆衍生品，不是股票：你拿到的只是宇树科技（688836）和长鑫科技（688825）这两只科创板股票的价格敞口，没有所有权、没有投票权，也没有股东权利。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"OKX lists CXMTUSD, BSPUSD, TQQQUSD and UNITREEUSD X-Perps opening 08:30-09:15 UTC on 12 October 2026.","sourceIds":["okx-listing"],"risk":"low"},{"id":"c2","text":"X-Perps settle in USDC, USDG or USD, charge funding at 00:00, 08:00 and 16:00 UTC and expire about five years out.","sourceIds":["okx-xperps-guide"],"risk":"low"},{"id":"c3","text":"STAR Market stocks trade 9:30-11:30 and 13:00-15:00 Beijing time with a 20% daily price limit after the first five trading days.","sourceIds":["sse-schedule","sse-mechanism"],"risk":"low"},{"id":"c4","text":"Unitree listed on 19 August 2026 at CNY150.80 and closed its first day at CNY845; it traded at CNY424.70 on 12 October.","sourceIds":["yicai-unitree","yahoo-prices"],"risk":"low"},{"id":"c5","text":"CXMT began trading on 27 July 2026; its highest close was CNY61.80 on 17 August and it traded at CNY49.66 on 12 October.","sourceIds":["yahoo-prices"],"risk":"low"},{"id":"c6","text":"OKX code nexu888 returns 40% of trading fees hourly; standard perp fees 0.02% maker, 0.05% taker.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"crypto-liquidations-overnight-longs-wiped-then-shorts-squeezed-asia-open","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-12T00:56:01.000Z","updatedAt":"2026-10-12T00:56:01.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"6 min"},"author":"NexuAlpha Research Desk","title":{"en":"Crypto Whipsaw Overnight: $4.1 Million of Longs Liquidated on a Half-Percent Bitcoin Dip, Then Shorts Squeezed Again at Monday's Asia Open (12 October 2026)","zh-Hans":"一夜多空双杀：比特币只跌 0.5%，多头 1 小时爆仓 411 万美元，周一亚洲开盘空头又被轧（2026 年 10 月 12 日）"},"summary":{"en":"Overnight on 11-12 October 2026 a 0.5% bitcoin dip liquidated $4.1 million of longs in one hour, then Monday's Asia open squeezed $1.6 million of shorts; here are the numbers, funding and what to watch.","zh-Hans":"短短八小时内，加密合约市场的多空两边都挨了打。 北京时间 10 月 12 日周一凌晨 05:03 到 06:03（世界协调时 11 日 21:03 至 22:03），NexuAlpha 爆仓数据记录到 411 万美元强平，其中 99.9% 是多单，而这一小时里比特币盘中只跌了约 0.5%，ETH 约 0.9%。 最大一笔是 OKX 上一张 83.3 万美元的 BTC 多单。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"NexuAlpha recorded $4.11M of liquidations between 21:03 and 22:03 UTC on 11 Oct 2026, 99.9% longs; lower bound.","sourceIds":["nexualpha-market-events"],"risk":"low"},{"id":"c2","text":"The largest order in that flush was an $833,260 BTC long on OKX at 21:15 UTC.","sourceIds":["nexualpha-market-events"],"risk":"low"},{"id":"c3","text":"BTCUSDT fell 0.49% from open to low in the 21:00 UTC hour; ETH fell 0.94% and SOL 1.33%.","sourceIds":["binance-futures-data"],"risk":"low"},{"id":"c4","text":"In the hour to 00:48 UTC on 12 Oct, $1.63M was liquidated, almost all shorts, led by a $677,703 ETH short.","sourceIds":["nexualpha-market-events"],"risk":"low"},{"id":"c5","text":"Binance BTC open interest fell about $44M and ETH about $72M between 21:00 and 22:00 UTC (our arithmetic).","sourceIds":["binance-futures-data"],"risk":"low"},{"id":"c6","text":"OKX code nexu888 returns 40% of fees hourly; Bybit code 48553.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["okx","binance","bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"papertrade-1000x-hyperliquid-eth-price-manipulation-1-28-million","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-12T00:54:17.000Z","updatedAt":"2026-10-12T00:54:17.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"6 min"},"author":"NexuAlpha Research Desk","title":{"en":"Papertrade Price Manipulation Explained: How One Trader Took $1.28 Million From a 1,000x Exchange by Moving Hyperliquid's ETH Price (2026)","zh-Hans":"Papertrade 被拉盘套利 128 万美元：1000 倍杠杆交易所为何会被 Hyperliquid 上的 ETH 报价“撬动”（2026）"},"summary":{"en":"A trader made about $1.28 million on the new 1,000x exchange Papertrade by moving Hyperliquid's ETH midpoint, the price Papertrade uses for every trade; here is how it worked and what traders should check.","zh-Hans":"Papertrade 是 2026 年 10 月 10 日在 Hyperliquid 的 HyperEVM 上线的永续合约交易所，最高 1000 倍杠杆，所有成交价都直接取 Hyperliquid 盘口最优买价与卖价的中间价。 上线后约 8 小时内，一个钱包赚了约 128 万美元；The Block 引用的链上分析显示，它一边在 Papertrade 持有巨额仓位，一边在 Hyperliquid 现货上来回买卖数千枚 ETH 去推动这个中间价。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"Papertrade launched on HyperEVM on 10 October 2026 with up to 1,000x leverage on synthetic BTC and ETH, pricing trades at Hyperliquid's BBO midpoint.","sourceIds":["cryptobriefing-papertrade","papertrade-docs"],"risk":"low"},{"id":"c2","text":"One wallet made about $1.28 million in the first eight hours while buying about 6,060 ETH and selling about 5,210 ETH on Hyperliquid, trading about $231 million of ETH there that day.","sourceIds":["bloomingbit-theblock","cryptobriefing-papertrade","theblock-papertrade"],"risk":"medium"},{"id":"c3","text":"The wallet later lost about $450,000 when ETH shorts were liquidated.","sourceIds":["bloomingbit-theblock","cryptobriefing-papertrade","blocktempo-papertrade"],"risk":"low"},{"id":"c4","text":"Papertrade said it tightened open-interest limits and blamed loose launch limits, not its design; it claimed profits were returned, which The Block could not verify.","sourceIds":["bloomingbit-theblock"],"risk":"medium"},{"id":"c5","text":"Papertrade's documentation lists BBO manipulation as a residual risk and says its oracle has no deviation, TWAP or lookback breaker.","sourceIds":["papertrade-docs"],"risk":"low"},{"id":"c6","text":"Hyperliquid's mark price used for liquidations is a median including external exchange prices.","sourceIds":["hyperliquid-price-indices"],"risk":"low"},{"id":"c7","text":"Launch-day trader losses were about $18.2-18.6 million (Crypto Briefing) or $30.24 million (BlockTempo).","sourceIds":["cryptobriefing-papertrade","blocktempo-papertrade"],"risk":"medium"},{"id":"c8","text":"Hyperliquid code NEXU888; OKX code nexu888 returns 40% of fees hourly.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["hyperliquid","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"xrp-ledger-overflow-bug-could-mint-xrp-fixed-what-it-means","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-11T18:56:15.000Z","updatedAt":"2026-10-11T18:56:15.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"5 min","id":"6 min"},"author":"NexuAlpha Research Desk","title":{"en":"XRP Ledger Bug Could Have Minted XRP From Nothing: What Was Fixed, Was Anyone Hurt, and What XRP Holders Should Do (October 2026)","zh-Hans":"XRP 账本潜伏十年的漏洞可凭空增发 XRP：修了什么、有没有人受损、持币者要不要动（2026 年 10 月）","id":"Bug XRP Ledger Bisa Mencetak XRP dari Nol: Apa yang Diperbaiki dan Apakah XRP Anda Aman? (Oktober 2026)"},"summary":{"en":"A 2015 overflow bug in the XRP Ledger could have minted XRP beyond the 100 billion cap; it was fixed in xrpld 3.4.1 without a validator vote and never exploited, so holders need not act.","zh-Hans":"XRP 账本（XRPL）支付引擎里一个从 2015 年就存在的整数溢出漏洞，理论上能让攻击者用一笔交易造出超过 1,000 亿上限、而且可以花出去的 XRP。漏洞在 2026 年 9 月 22 日被报告，9 月 25 日随 xrpld 3.4.1 修复，10 月 9 日公开披露；开发方表示没有发现任何被利用的迹象，持币者不需要做任何操作。真正引发争议的是修复方式：这是十多年来第一次绕过验证者投票直接生效，而且源代码延后约两周才公开。","id":"Bug overflow di mesin pembayaran XRP Ledger yang ada sejak 2015 secara teori bisa menciptakan XRP melebihi batas 100 miliar dalam satu transaksi. Bug dilaporkan 22 September 2026, diperbaiki di xrpld 3.4."},"availableLocales":["en","zh-Hans","id"],"claims":[{"id":"c1","text":"An unchecked 64-bit overflow in the XRPL payment engine, present since 2015, could have minted spendable XRP beyond the 100 billion supply in one transaction.","sourceIds":["xrpl-disclosure","theblock-xrpl"],"risk":"low"},{"id":"c2","text":"Reported 22 September 2026, fixed in xrpld 3.4.1 on 25 September, disclosed 9 October; no evidence of exploitation.","sourceIds":["xrpl-disclosure","xrpld-341-release"],"risk":"low"},{"id":"c3","text":"The fix took effect on upgrade without an amendment vote, the first such change in more than ten years; over 80% of default UNL validators ran it on release day.","sourceIds":["xrpl-disclosure","theblock-xrpl"],"risk":"low"},{"id":"c4","text":"Veria Labs' Cayden Liao says an AI agent found the bug, a single exploit could have created about 18 trillion XRP, and Ripple paid a $250,000 bounty.","sourceIds":["theblock-xrpl"],"risk":"medium"},{"id":"c5","text":"No more than the original 100 billion XRP can be created.","sourceIds":["xrpl-about-xrp"],"risk":"low"},{"id":"c6","text":"OJK recorded 23.21 million crypto consumer accounts and Rp23.16 trillion of transactions in August 2026.","sourceIds":["antara-ojk"],"risk":"low"},{"id":"c7","text":"OKX code nexu888 returns 40% of fees, settled hourly.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"liquid-network-l-btc-peg-outs-suspended-602-btc-shortfall","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-11T18:53:55.000Z","updatedAt":"2026-10-11T18:53:55.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"6 min"},"author":"NexuAlpha Research Desk","title":{"en":"Liquid Network Peg-Outs Still Suspended: Why L-BTC Cannot Be Redeemed for Bitcoin Yet, and the 602 BTC Gap (October 2026)","zh-Hans":"Liquid 侧链 L-BTC 仍无法赎回比特币：9 月漏洞后还差 602 BTC，持有人该怎么办（2026 年 10 月）"},"summary":{"en":"Liquid Network peg-outs remain suspended in October 2026 after the September exploit left the L-BTC reserve about 602 BTC short; here is what happened, where recovery stands and what L-BTC holders can do.","zh-Hans":"截至 2026 年 10 月 11 日，Liquid 网络的 peg-out（把 L-BTC 换回比特币主链上的 BTC）仍处于暂停状态。 9 月 6 日的一次漏洞攻击从联盟储备中转走约 4,000 BTC，攻击者次日归还了 3,400 BTC，但仍有约 602 BTC 没有追回，储备只覆盖流通 L-BTC 的约 86%。 Liquid 表示，要等 1:1 储备完全补齐、安全工作完成后才会恢复赎回，目前没有给出时间表。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"An exploit on 6 September 2026 created about 4,000 unbacked LBTC and drained the Liquid reserve from about 4,205 BTC to 197 BTC via a SideSwap peg-out.","sourceIds":["blockstream-assessment"],"risk":"low"},{"id":"c2","text":"3,400 BTC was returned on 7 September; about 602 BTC remains outstanding.","sourceIds":["blockstream-assessment","cryptobriefing-liquid"],"risk":"low"},{"id":"c3","text":"Liquid transactions resumed on 10 September but peg-outs remain disabled, still as of 11 October.","sourceIds":["liquid-x-update","cryptobriefing-liquid"],"risk":"low"},{"id":"c4","text":"The reserve covers about 86% of outstanding L-BTC (our arithmetic: 3,597 / 4,199 = 85.7%).","sourceIds":["blockstream-assessment","cryptobriefing-liquid"],"risk":"low"},{"id":"c5","text":"USDt and other Liquid-issued assets were unaffected by the exploit.","sourceIds":["blockstream-assessment","cryptobriefing-liquid"],"risk":"low"},{"id":"c6","text":"OKX code nexu888 returns 40% of fees, settled hourly.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"clarity-act-failed-senate-what-happens-now-sec-cftc-crypto-rules","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-11T16:55:43.000Z","updatedAt":"2026-10-11T16:55:43.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"6 min"},"author":"NexuAlpha Research Desk","title":{"en":"The CLARITY Act Failed in the Senate: What Happens to US Crypto Rules Now, and What It Means for Your Accounts (2026)","zh-Hans":"美国《CLARITY 法案》参议院闯关失败：加密监管接下来怎么走，对你的账户有什么影响（2026）"},"summary":{"en":"The CLARITY Act failed a 49-50 Senate vote on 15 September 2026. Here is what the SEC and CFTC have done since, what gap remains for spot crypto, and what it means for your accounts.","zh-Hans":"《数字资产市场清晰法案》（CLARITY Act）原本要为美国加密市场建立一套完整规则，但 2026 年 9 月 15 日在参议院程序性投票中以 49 票赞成、50 票反对未获通过，离所需的 60 票差距明显。 距离 11 月中期选举不远，今年通过的希望已经很小。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"The CLARITY Act failed a Senate procedural vote 49-50 on 15 September 2026; 60 votes were needed.","sourceIds":["coindesk-clarity-stalled","coindesk-advisors"],"risk":"low"},{"id":"c2","text":"The SEC issued a five-year Innovation Exemption for trading tokenized NMS stock on Tokenized Securities Venues on 17 September 2026.","sourceIds":["sec-innovation-exemption","coindesk-advisors"],"risk":"low"},{"id":"c3","text":"The SEC proposed crypto custody rules for advisers and funds on 1 October 2026, including state trust companies as custodians.","sourceIds":["sec-custody-proposal","coindesk-clarity-failure"],"risk":"low"},{"id":"c4","text":"The CFTC published an ANPRM on Regulation CTX and Regulation CAM on 5 October 2026 with a 60-day comment period.","sourceIds":["cftc-anprm","coindesk-cftc"],"risk":"low"},{"id":"c5","text":"Unleveraged spot crypto trading still lacks comprehensive federal oversight beyond CFTC anti-fraud and anti-manipulation authority.","sourceIds":["coindesk-cftc","coindesk-clarity-failure"],"risk":"low"},{"id":"c6","text":"Backpack code luckybitcoin; Kraken code 7f97gkqw.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["coinbase","kraken","backpack"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"bitcoin-short-squeeze-trump-energy-ceasefire-shorts-liquidated","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-11T16:53:51.000Z","updatedAt":"2026-10-11T16:53:51.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"6 min","vi":"9 min"},"author":"NexuAlpha Research Desk","title":{"en":"Bitcoin Short Squeeze After Trump's \"Energy Ceasefire\" Post: $12.5 Million Liquidated in Four Hours, 99.7% of It Shorts (October 2026)","zh-Hans":"特朗普宣布俄乌“能源停火”当晚，币圈空头被轧：4 小时爆仓 1254 万美元，99.7% 是空单（2026）","vi":"Short squeeze Bitcoin đêm 11/10 sau tuyên bố “ngừng bắn năng lượng” của Trump: 12,5 triệu USD bị thanh lý trong 4 giờ, 99,7% là lệnh short (2026)"},"summary":{"en":"A short squeeze on 11 October 2026 liquidated $12.5 million in four hours, 99.7% of it shorts, led by ETH on OKX, on the day Trump announced a Russia-Ukraine energy ceasefire.","zh-Hans":"北京时间 10 月 11 日深夜，加密永续合约市场出现了一轮典型的“轧空”。 NexuAlpha 爆仓数据显示，截至 10 月 12 日 00:48（UTC 11 日 16:48）的 4 小时内，被强平的仓位合计 1254 万美元，其中 1250 万美元是空单，占比 99.7%。 单笔最大的一张是 23:40 在 OKX 被强平的 ETH 空单，价值 253 万美元。","vi":"Tối 11/10/2026 giờ Việt Nam, dữ liệu NexuAlpha ghi nhận 12,54 triệu USD vị thế bị thanh lý trong 4 giờ, 99,7% là short, lệnh lớn nhất là short ETH 2,53 triệu USD trên OKX."},"availableLocales":["en","zh-Hans","vi"],"claims":[{"id":"c1","text":"NexuAlpha recorded $12.54M of liquidations in the four hours to 16:48 UTC on 11 Oct 2026, 99.7% shorts; lower bound.","sourceIds":["nexualpha-market-events"],"risk":"low"},{"id":"c2","text":"Largest single liquidation was a $2,528,150 ETH short on OKX at 15:40:26 UTC.","sourceIds":["nexualpha-market-events"],"risk":"low"},{"id":"c3","text":"Trump announced an energy ceasefire between Russia and Ukraine on Truth Social; Zelenskyy said it was news to him and Ukraine would agree if Russia did.","sourceIds":["coindesk-ceasefire","guardian-ceasefire"],"risk":"low"},{"id":"c4","text":"CoinDesk reported markets were not reacting at the time, with BTC just under $83,000.","sourceIds":["coindesk-ceasefire"],"risk":"low"},{"id":"c5","text":"Binance ETHUSDT funding settled at -0.0118% and -0.0117% before flipping to +0.0012% at 16:00 UTC; BTC from -0.0027%/-0.0010% to +0.0013%.","sourceIds":["binance-klines-funding"],"risk":"low"},{"id":"c6","text":"OKX code nexu888 returns 40% of fees hourly; Hyperliquid code NEXU888; Binance code 11350287 25%.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["okx","binance","hyperliquid"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"october-10-crypto-crash-one-year-later-liquidity-leverage-liquidations","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-11T14:54:26.000Z","updatedAt":"2026-10-11T14:54:26.000Z","readTime":"7 min","author":"NexuAlpha Research Desk","title":{"en":"One Year After the $19 Billion October 10 Crash: Bitcoin Liquidity Has Rebuilt, Altcoins Have Not — and What Leverage Looks Like Now (2026)","zh-Hans":"“10·10”190 亿美元爆仓一周年：比特币流动性已经恢复，山寨币没有，现在的杠杆处在什么水平（2026）","tr":"10 Ekim Kripto Çöküşünün Birinci Yılı: 19 Milyar Dolarlık Likidasyondan Sonra Bitcoin Toparlandı, Altcoinler Toparlanamadı (2026)"},"summary":{"en":"A year after $19 billion was liquidated on 10 October 2025, bitcoin and ether order books are deeper but altcoin liquidity is thinner. Our liquidation and funding data show where leverage stands now.","zh-Hans":"2025 年 10 月 10 日，比特币在几个小时内从约 12.2 万美元跌破 10.5 万美元，单日超过 190 亿美元的杠杆仓位被强平，是加密市场史上最大的一次爆仓。 一年过去，CoinDesk Research 的数据显示，比特币和以太坊的盘口深度已经超过崩盘当天，而山寨币深度和现货成交量仍在萎缩。 NexuAlpha 自己的数据显示这个周末很平静：24 小时内追踪到约 320 万美元爆仓，多空几乎各占一半，主流永续合约的资金费率接近零。","tr":"10 Ekim 2025'te 19 milyar dolardan fazla kaldıraçlı pozisyon tasfiye edildi. Bir yıl sonra CoinDesk Research verisine göre bitcoin ve ether emir defterleri çöküş gününden derin, altcoin derinliği ve spot hacim ise zayıf."},"availableLocales":["en","zh-Hans","tr"],"claims":[{"id":"c1","text":"More than $19B of leveraged positions were liquidated on 10 October 2025 as BTC fell from ~$122.6K to below $105K after 100% tariff announcement.","sourceIds":["coindesk-depth","coindesk-lessons"],"risk":"low"},{"id":"c2","text":"Bitcoin 1% depth ~$11.7M on 7 Oct 2026, ~75% above crash day; altcoin 5% depth down about a third since early 2025.","sourceIds":["coindesk-depth"],"risk":"medium"},{"id":"c3","text":"NexuAlpha tracked $3.23M of liquidations in 24h to 14:48 UTC 11 Oct 2026, 47% longs / 53% shorts, 478 orders; lower bound.","sourceIds":["nexualpha-market-events"],"risk":"low"},{"id":"c4","text":"Binance ETHUSDT funding settled at -0.0118% and -0.0117% on 11 Oct at 00:00 and 08:00 UTC.","sourceIds":["binance-funding"],"risk":"low"},{"id":"c5","text":"OKX code nexu888 returns 40% of fees hourly; Hyperliquid code NEXU888; Bybit code 48553.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["okx","binance","hyperliquid","bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"imf-tokenized-us-stocks-after-hours-volatility-liquidity-what-it-means","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-11T14:52:01.000Z","updatedAt":"2026-10-11T14:52:01.000Z","readTime":"7 min","author":"NexuAlpha Research Desk","title":{"en":"IMF on Tokenized US Stocks: Half of Trades Happen After Hours, Prices Swing 1.5x More — What It Means for You (2026)","zh-Hans":"IMF 研究代币化美股：一半交易发生在美股休市时段，波动是正股的 1.5 倍，对你意味着什么（2026）"},"summary":{"en":"The IMF's October 2026 stability report found more than half of tokenized US stock trading happens after hours and prices swing 1.5 times more than the shares. What it means for investors.","zh-Hans":"国际货币基金组织（IMF）在 2026 年 10 月的《全球金融稳定报告》中，研究了交易最活跃的五只代币化美股产品，发现超过一半的成交发生在美股常规交易时段之外，约 80% 的单笔成交不足一股。同时，这些产品的波动约为对应正股的 1.5 倍，流动性也明显更差，去中心化交易所上尤其如此。对普通投资者来说，代币化美股确实提供了周末交易和碎股买入，但代价是更大的价格摆动和更薄的盘口；你到底持有什么权利，还要看产品的法律结构。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"In the IMF sample more than half of tokenized US equity trading took place outside regular US hours and about 80% of trades were below one share.","sourceIds":["coindesk-imf","cryptonews-imf"],"risk":"low"},{"id":"c2","text":"Tokenized stocks were about 1.5 times as volatile as the underlying shares; DEXs were most volatile and least liquid.","sourceIds":["coindesk-imf","cryptonews-imf"],"risk":"low"},{"id":"c3","text":"Public tokenized RWAs were about $65B at end-July 2026, of which tokenized equities about $2.3B.","sourceIds":["coindesk-imf","cryptonews-imf"],"risk":"low"},{"id":"c4","text":"OKX and ICE filed for a venue offering round-the-clock trading in tokenized US shares.","sourceIds":["coindesk-imf"],"risk":"medium"},{"id":"c5","text":"Backpack registration code is luckybitcoin.","sourceIds":["nexualpha-partners"],"risk":"low"}],"relatedVenues":["backpack","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"coldcard-x-account-phishing-post-what-to-do","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-11T12:59:53.000Z","updatedAt":"2026-10-11T12:59:53.000Z","readTime":"7 min","author":"NexuAlpha Research Desk","title":{"en":"Coldcard's Official X Account Posted a Phishing Link: What Happened and What Bitcoin Holders Should Do Now (2026)","zh-Hans":"COLDCARD 官方 X 账号发出钓鱼链接：发生了什么，比特币持有者现在该怎么做（2026）"},"summary":{"en":"A phishing link was posted from COLDCARD's official X account on 11 October 2026. What the company said, why it suspects platform-level access at X, and what to do if you clicked or still need to migrate a seed.","zh-Hans":"2026 年 10 月 11 日，比特币硬件钱包厂商 COLDCARD 的官方 X 账号 @COLDCARDwallet 发出了一条带钓鱼链接的帖子。 公司随后删除了该帖，提醒用户不要打开或与链接互动，并强调唯一官方网站是 coldcard. com。 在另一条直接@X 客服的帖子里，COLDCARD 表示找不到与这条帖子对应的任何登录、会话或访问记录，自己的凭据和离线双重认证依然安全，因此担心存在 X 平台层面或管理员层面的未授权访问。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"On 11 October 2026 a phishing link was posted from COLDCARD's official X account; COLDCARD deleted it and said coldcard.com is its only official website.","sourceIds":["coldcard-x-post-1","cointelegraph-coldcard"],"risk":"low"},{"id":"c2","text":"COLDCARD told X Support it found no matching login, session or access records, that its credentials and offline 2FA remain secure, and that it is concerned about platform-level or administrative access.","sourceIds":["coldcard-x-post-2"],"risk":"low"},{"id":"c3","text":"The July 2026 COLDCARD exploit stole at least $100M of bitcoin from about 7,300 wallets per Galaxy Digital; DefiLlama estimates $115M.","sourceIds":["cointelegraph-coldcard"],"risk":"medium"},{"id":"c4","text":"COLDCARD's current recommended releases are Mk4/Mk5 5.6.3 and Q 1.5.3Q, and updating firmware does not repair a seed created on affected firmware.","sourceIds":["coldcard-security-status"],"risk":"low"},{"id":"c5","text":"OKX invite code nexu888 returns 40% of trading fees, settled hourly.","sourceIds":["nexualpha-partners"],"risk":"medium"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"trump-memecoin-gala-dinner-leaderboard-what-holders-should-know","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-11T12:59:49.000Z","updatedAt":"2026-10-11T12:59:49.000Z","readTime":"7 min","author":"NexuAlpha Research Desk","title":{"en":"Trump Memecoin Dinner on 22 November 2026: How the $TRUMP Leaderboard Works, Who Gets a Seat and Why the Price Has Not Moved","zh-Hans":"特朗普 Meme 币晚宴定在 2026 年 11 月 22 日：$TRUMP 排行榜怎么算、谁能入座、为什么币价这次没涨"},"summary":{"en":"The $TRUMP Coin Club's second dinner is on 22 November 2026 for the top 185 holders.","zh-Hans":"$TRUMP 官方“Coin Club”将在 2026 年 11 月 22 日于华盛顿特区的 Trump National 举办第二场“Gala Dinner”（盛大晚宴），排行榜前 185 名持有者获得席位，前 29 名还能参加有特朗普本人出席的 VIP 招待会。 排名依据的是截至 11 月 12 日美东时间下午 1 点最终快照的“时间加权”持仓，而且币必须放在已在俱乐部登记的自托管钱包里。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"The $TRUMP Coin Club Gala Dinner is on 22 November 2026 at Trump National, Washington D.C., for the top 185 holders, with a VIP reception for the top 29; final snapshot 12 November 2026 at 1 p.m. Eastern.","sourceIds":["trump-gala-page","trump-winter-terms"],"risk":"low"},{"id":"c2","text":"The gala page lists a scoring window from 30 September while the terms define the measurement period from 5 October 2026.","sourceIds":["trump-gala-page","trump-winter-terms"],"risk":"low"},{"id":"c3","text":"TRUMP fell from $2.053 on 30 September to $1.873 on 11 October 2026 on Binance, about 8.8%.","sourceIds":["binance-trump-klines"],"risk":"low"},{"id":"c4","text":"The project said about 67% of supply had unlocked and less than 9.6% of total supply is expected to be deployed or sold over the coming months.","sourceIds":["trump-market-update"],"risk":"low"},{"id":"c5","text":"The first dinner announcement in 2025 lifted TRUMP from about $9 to above $14 within hours; exchange-held coins do not count for the leaderboard.","sourceIds":["cryptoticker-dinner"],"risk":"medium"},{"id":"c6","text":"Binance code 11350287 returns 25% of trading fees, settled hourly.","sourceIds":["nexualpha-partners"],"risk":"medium"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"ether-etf-outflows-nine-days-solana-etf-streak-ends-bitcoin-etf-week","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-11T12:56:31.000Z","updatedAt":"2026-10-11T12:56:31.000Z","readTime":"6 min","author":"NexuAlpha Research Desk","title":{"en":"Ether ETFs Lose Money Nine Days in a Row: $542 Million Left Last Week, Solana Funds' Streak Ends and Bitcoin ETFs Shed $680 Million (October 2026)","zh-Hans":"以太坊现货 ETF 连续 9 天净流出：上周流出 5.42 亿美元，Solana ETF 连续流入纪录终结，比特币 ETF 一周流出约 6.8 亿美元（2026 年 10 月）","pt-BR":"ETFs de Ethereum têm 9 dias seguidos de saídas: US$ 542 milhões saíram na semana, ETFs de Solana encerram sequência e os de Bitcoin perdem US$ 680 milhões (outubro de 2026)"},"summary":{"en":"US spot Ether ETFs had nine straight days of outflows worth about $697M, losing $542M in the week to 9 October 2026 as ETHA led redemptions, Solana ETFs ended a 14-week streak and Bitcoin ETFs shed about $680M.","zh-Hans":"从 2026 年 9 月 29 日到 10 月 9 日，美国以太坊现货 ETF 每个交易日都是净流出，九个交易日合计约 6.97 亿美元；其中 10 月 5 日至 9 日这一周流出约 5.42 亿美元，是今年 1 月以来最差的一周，贝莱德 ETHA 一只基金就占了约 88%。 Solana 现货 ETF 结束了连续 14 周的净流入纪录，单周流出 2,480 万美元；比特币现货 ETF 在连续三周流入后，一周流出约 6.8 亿美元。","pt-BR":"Os ETFs de Ethereum à vista negociados nos Estados Unidos registraram resgates líquidos em todos os pregões de 29 de setembro a 9 de outubro de 2026: nove dias seguidos, somando cerca de US$ 697 milhões."},"availableLocales":["en","zh-Hans","pt-BR"],"claims":[{"id":"c1","text":"US spot Ether ETFs had net outflows on nine straight trading days from 29 September to 9 October 2026, worth about $697 million.","sourceIds":["theblock-etf-week","farside-eth"],"risk":"low"},{"id":"c2","text":"Spot Ether ETFs lost $542.1 million in the week of 5-9 October, ETHA $477.0 million of it; $201.9 million left ETHA on 6 October, the day its 1-for-3 reverse split took effect.","sourceIds":["theblock-etf-week","farside-eth"],"risk":"low"},{"id":"c3","text":"Spot Solana ETFs lost $24.8 million, ending a 14-week inflow streak; spot Bitcoin ETFs lost about $680 million.","sourceIds":["theblock-etf-week","farside-btc","farside-sol"],"risk":"low"},{"id":"c4","text":"Binance ETHUSDT funding settled at -0.0118% and -0.0117% on 11 October 2026 at 00:00 and 08:00 UTC; ETH open interest fell from $6.17B to $5.78B between 8 and 9 October.","sourceIds":["binance-eth-funding","binance-eth-oi","nexualpha-market-events"],"risk":"low"},{"id":"c5","text":"ETH fell from $2,726.93 on 5 October to $2,487.70 on 9 October on Binance spot, about 8.8%.","sourceIds":["binance-eth-klines"],"risk":"low"},{"id":"c6","text":"OKX USDT perpetual fees are 0.02% maker and 0.05% taker; code nexu888 returns 40% of fees, settled hourly.","sourceIds":["nexualpha-partners"],"risk":"medium"}],"relatedVenues":["binance","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"crypto-liquidations-shorts-85-percent-negative-funding-bitcoin-83k","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-11T09:30:10.000Z","updatedAt":"2026-10-11T09:30:10.000Z","readTime":"5 min","readTimeByLocale":{"en":"5 min","zh-Hans":"5 min","ru":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"Crypto Liquidations Today: Shorts Took 85% of $11.9 Million as Funding Turned Negative With Bitcoin at $83,000 (11 October 2026)","zh-Hans":"今日爆仓：1,190 万美元中空头占 85%，资金费率转负，比特币守在 8.3 万美元（2026 年 10 月 11 日）","ru":"Ликвидации на крипторынке 11 октября 2026 года: 85% из 11,9 млн долларов пришлись на шорты, ставка финансирования ушла в минус"},"summary":{"en":"NexuAlpha tracked $11.87 million of crypto liquidations in 24 hours to 11 October 2026, 85% shorts, with a $1.45 million SOL short the largest, as ETH funding turned negative and Bitcoin held $83,000.","zh-Hans":"截至 2026 年 10 月 11 日 UTC 09:13（北京时间 17:13）的 24 小时内，NexuAlpha 爆仓追踪器在其覆盖的交易所和合约上记录到 1,187 万美元强平，其中 1,011 万美元、约 85% 来自空头。 最大一笔是 OKX 上一张 145 万美元的 SOL 空单。 同一时间，币安 ETH 永续合约连续两期资金费率结算在约 −0.012%，也就是空头在付钱给多头。","ru":"За сутки до 09:13 UTC 11 октября 2026 года трекер NexuAlpha учёл ликвидации на 11,87 млн долларов, 85% из них — шорты; крупнейшая — шорт по SOL на OKX на 1,45 млн."},"availableLocales":["en","zh-Hans","ru"],"claims":[{"id":"c1","text":"NexuAlpha tracked $11.87M of liquidations in the 24 hours to 09:13 UTC on 11 October 2026, $10.11M shorts, 1,053 orders; a lower bound.","sourceIds":["nexualpha-market-events"],"risk":"low"},{"id":"c2","text":"The largest tracked liquidation was a $1,452,978 SOL short on OKX at 14:29 UTC on 10 October, in an hour when Binance SOL futures rose from 109.87 to 110.75.","sourceIds":["nexualpha-market-events","binance-sol-klines"],"risk":"low"},{"id":"c3","text":"Binance ETHUSDT funding settled at -0.0118% and -0.0117% on 11 October at 00:00 and 08:00 UTC.","sourceIds":["binance-funding"],"risk":"low"},{"id":"c4","text":"CoinGlass data reported by Cointelegraph showed $1.09B of liquidations in the 24 hours to 10:00 UTC on 9 October, $1.05B longs.","sourceIds":["cointelegraph-liq"],"risk":"medium"},{"id":"c5","text":"Farside data reported by Cointelegraph showed October net outflows of $407.4M for Bitcoin ETFs and $578.9M for Ether ETFs through 8 October.","sourceIds":["cointelegraph-etf"],"risk":"medium"},{"id":"c6","text":"Decrypt cited a 30-year Treasury yield near 5.7%, Brent near $100 and Fed minutes pointing to another hike.","sourceIds":["decrypt-etf"],"risk":"medium"},{"id":"c7","text":"OKX USDT perpetual fees are 0.02% maker and 0.05% taker; code nexu888 returns 40% of fees, settled hourly.","sourceIds":["nexualpha-partners"],"risk":"medium"}],"relatedVenues":["okx","binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"securitize-stocks-tokenized-us-equities-solana-what-you-own","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-11T09:25:43.000Z","updatedAt":"2026-10-11T09:25:43.000Z","readTime":"7 min","author":"NexuAlpha Research Desk","title":{"en":"Securitize Stocks on Solana: What You Actually Own With Its Tokenized Apple, Nvidia and Tesla Shares (2026)","zh-Hans":"Securitize 在 Solana 上线代币化美股：买它的苹果、英伟达、特斯拉代币，你到底持有什么（2026）"},"summary":{"en":"Securitize launched 1:1-backed tokenized US stocks on Solana with dividends and voting rights. What a security entitlement means, who can buy, trading hours and why the NYSE and OKX-ICE venues are not live yet.","zh-Hans":"2026 年 10 月 8 日，纽交所上市公司 Securitize（代码 SECZ）推出 Securitize Stocks：在 Solana 上发行、对应 12 只美国大盘股（包括苹果、英伟达、特斯拉和微软）的代币，面向美国、欧盟及其他获准地区的合格投资者。 每枚代币都由一股真实股票 1:1 支持，法律上属于美国《统一商法典》第 8 条下的“证券权益”（security entitlement），持有人可以获得分红，如果该类股票有投票权，也可以投票。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"On 8 October 2026 Securitize launched Securitize Stocks with 12 US stocks on Solana for eligible investors in the US, EU and other permitted jurisdictions.","sourceIds":["securitize-pr","decrypt-securitize"],"risk":"low"},{"id":"c2","text":"Each token is backed 1:1 by an underlying share, is a security entitlement under UCC Article 8, passes through dividends and voting where applicable, and backing shares are not lent.","sourceIds":["securitize-pr"],"risk":"low"},{"id":"c3","text":"Holders are not registered shareholders unless they convert, conversion requires issuer-sponsored tokenization, and the issuers have not sponsored or endorsed the product.","sourceIds":["securitize-pr"],"risk":"low"},{"id":"c4","text":"Trading is on Securitize's broker-dealer via a Solana PropAMM with Jump Trading, settling in USDC, during extended hours; NYSE and OKXICE venues have not launched.","sourceIds":["securitize-pr","cointelegraph-securitize"],"risk":"low"},{"id":"c5","text":"Securitize shares rose about 10% on launch day and about 54% over a month; RWA.xyz showed $38.88B distributed tokenized assets ex-stablecoins versus $25.36B a year earlier.","sourceIds":["cointelegraph-securitize"],"risk":"medium"},{"id":"c6","text":"Bitget code nexu888 returns 60% of trading fees, settled daily.","sourceIds":["nexualpha-partners"],"risk":"medium"}],"relatedVenues":["bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"starknet-strk-rally-l1-plan-open-interest-negative-funding","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-11T09:25:43.000Z","updatedAt":"2026-10-11T09:25:43.000Z","readTime":"5 min","readTimeByLocale":{"en":"5 min","zh-Hans":"5 min"},"author":"NexuAlpha Research Desk","title":{"en":"Starknet (STRK) Jumps 54% in a Day After Its Layer-1 Plan: Open Interest Tripled While Most Traders Bet Against It (2026)","zh-Hans":"Starknet（STRK）宣布考虑转型 L1 后单日涨 54%：持仓量翻三倍，多数交易者却在做空（2026）"},"summary":{"en":"STRK rose about 54% in a day after Starknet said it is considering becoming a quantum-resistant layer 1. Binance data shows open interest tripling while long accounts fell to 43% and funding turned negative.","zh-Hans":"2026 年 10 月 11 日，STRK 是 NexuAlpha 行情数据中涨幅最大的币种：在币安 24 小时上涨约 54%，报 0.109 美元左右，比 10 月 7 日收盘价 0.049 美元翻了一倍多。 导火索是 Starknet 10 月 8 日发帖称正在“积极考虑成为 L1”，目标是在 2027 年成为“第一个完全抗量子的网络”。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"On 8 October 2026 Starknet said it is actively considering becoming an L1 to be the first fully quantum-resistant network, targeting 2027.","sourceIds":["starknet-post","decrypt-strk"],"risk":"low"},{"id":"c2","text":"As an L2 Starknet relies on Ethereum's security; Ethereum targets core post-quantum infrastructure around 2029; no migration path has been given.","sourceIds":["decrypt-strk","ben-sasson"],"risk":"medium"},{"id":"c3","text":"STRK rose about 54% on Binance spot in the 24 hours to 09:12 UTC on 11 October and about 122% from the 7 October close (our arithmetic).","sourceIds":["binance-spot","nexualpha-market-events"],"risk":"low"},{"id":"c4","text":"Binance STRK futures open interest rose from $15.2M to $45.4M between the 9 and 11 October snapshots while long accounts fell from 61.2% to 42.7%.","sourceIds":["binance-futures"],"risk":"low"},{"id":"c5","text":"Binance STRK funding settled negative at 00:00, 04:00 and 08:00 UTC on 11 October; OKX STRK funding was negative.","sourceIds":["binance-futures","okx-funding"],"risk":"low"},{"id":"c6","text":"OKX USDT perpetual fees are 0.02% maker and 0.05% taker; code nexu888 returns 40% of fees, settled hourly.","sourceIds":["nexualpha-partners"],"risk":"medium"}],"relatedVenues":["binance","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"esma-non-mica-stablecoins-usdt-three-month-deadline-eu-users","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-11T09:20:22.000Z","updatedAt":"2026-10-11T09:20:22.000Z","readTime":"6 min","author":"NexuAlpha Research Desk","title":{"en":"ESMA Gives EU Crypto Platforms Three Months to Drop Non-MiCA Stablecoins: What Happens to Your USDT (2026)","zh-Hans":"欧盟 ESMA 给加密平台三个月下架不合规稳定币：你在欧洲平台上的 USDT 会怎样（2026）","es":"La ESMA da tres meses a los exchanges para dejar las stablecoins no MiCA: qué pasa con tu USDT en España (2026)"},"summary":{"en":"ESMA told EU supervisors that licensed crypto platforms must stop all services for non-MiCA stablecoins and clear legacy exposure within three months, by 8 January 2027.","zh-Hans":"2026 年 10 月 8 日，欧盟证券与市场管理局（ESMA）发布一份意见书，要求各国监管机构督促持牌加密资产服务商（CASP）不再为发行方不符合 MiCA 的稳定币提供任何服务——从交易到托管都包括在内。 平台如果仍有这类敞口，监管机构应要求其“最迟在发布之日起三个月内”整改完毕，按我们的计算即 2027 年 1 月 8 日。 此后只能保留卖出、兑换、转出或提取现有持仓的功能。","es":"El 8 de octubre de 2026 la ESMA, el supervisor europeo de los mercados de valores, publicó una opinión dirigida a las autoridades nacionales, entre ellas la CNMV."},"availableLocales":["en","zh-Hans","es"],"claims":[{"id":"c1","text":"ESMA's 8 October 2026 opinion says CASPs should not provide crypto-asset services in relation to non-MiCA-compliant ARTs or EMTs, covering all CASP services.","sourceIds":["esma-opinion","esma-press"],"risk":"low"},{"id":"c2","text":"Supervisors should require remediation of legacy exposure no later than three months after publication, with only sell, conversion, transfer or withdrawal functions afterwards; three months from 8 October 2026 is 8 January 2027 (our arithmetic).","sourceIds":["esma-opinion"],"risk":"low"},{"id":"c3","text":"ESMA considers warnings, disclosures or client acknowledgements insufficient.","sourceIds":["esma-opinion"],"risk":"low"},{"id":"c4","text":"ESMA's interim EMT register lists Circle Internet Financial Europe SAS with USDC and EURC white papers and Paxos Issuance Europe; it has no Tether entry.","sourceIds":["esma-emt-register"],"risk":"medium"},{"id":"c5","text":"ESMA's CASP register lists OKX Europe Limited (Malta), Bybit EU GmbH, Coinbase Luxembourg, Kraken entities and 15 CNMV-authorised CASPs including Bit2Me.","sourceIds":["esma-casp-register"],"risk":"medium"},{"id":"c6","text":"OKX code nexu888 returns 40% of fees, settled hourly; cross-region referrals count only where supported.","sourceIds":["nexualpha-partners","okx-referral-faq"],"risk":"medium"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"cftc-event-contracts-swaps-proposal-casino-gambling-exclusion","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-11T09:18:06.000Z","updatedAt":"2026-10-11T09:18:06.000Z","readTime":"6 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC Moves to Define Event Contracts as Swaps and Exclude Casino Gambling: What It Means for Kalshi, Polymarket and Users (2026)","zh-Hans":"CFTC 拟将事件合约定义为“掉期”并排除赌场博彩：对 Kalshi、Polymarket 和用户意味着什么（2026）"},"summary":{"en":"The CFTC proposed defining sports, political and other event contracts as swaps and issued an interim rule excluding casino-style gambling. What changes for Kalshi, Polymarket and users, and what to watch next.","zh-Hans":"2026 年 10 月 9 日（周五），美国商品期货交易委员会（CFTC）一次发布了两项措施。 第一项是拟议规则：把体育、政治、文化和天气类事件合约明确纳入“掉期”（swap）定义，从而归入 CFTC 的联邦管辖。 第二项是临时最终规则：在《联邦公报》刊登后立即生效，明确体育博彩投注、赌场游戏等“赌场式博彩产品”不属于掉期。 两者合在一起，划出了 CFTC 希望法院接受的界线——预测市场是衍生品，赌场不是。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"The CFTC published a proposed rule further defining swap to include event contracts on sports, politics, cultural and weather events, with 30 days for comments after Federal Register publication.","sourceIds":["cftc-9310"],"risk":"low"},{"id":"c2","text":"The CFTC issued an interim final rule codifying that casino-style gambling products are excluded from the swap definition, effective on Federal Register publication.","sourceIds":["cftc-9309"],"risk":"low"},{"id":"c3","text":"States have sued Kalshi and Polymarket; the 6th Circuit ruled for Ohio and Tennessee while the 3rd Circuit favored Kalshi in New Jersey.","sourceIds":["cointelegraph-cftc","decrypt-cftc"],"risk":"medium"},{"id":"c4","text":"The measures formalize proposals sent to the White House last month.","sourceIds":["decrypt-cftc"],"risk":"medium"},{"id":"c5","text":"Blockchain.com applied for DCM and FCM licenses, and Selig is the CFTC's sole commissioner with four seats vacant.","sourceIds":["cointelegraph-blockchaincom"],"risk":"medium"},{"id":"c6","text":"Bitget regular USDT futures fees are 0.02% maker and 0.06% taker; code nexu888 returns 60% of fees, settled daily.","sourceIds":["nexualpha-partners"],"risk":"medium"}],"relatedVenues":["bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"ledger-confirms-hardware-implant-cryptobilis-device-what-changes","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-11T09:16:35.000Z","updatedAt":"2026-10-11T09:16:35.000Z","readTime":"6 min","author":"NexuAlpha Research Desk","title":{"en":"Ledger Confirms a Hidden Hardware Implant in a CryptoBilis Device: What the Finding Changes (2026)","zh-Hans":"Ledger 确认 CryptoBilis 设备被植入未授权硬件：这一发现改变了什么（2026）"},"summary":{"en":"Ledger confirmed an unauthorized hardware implant in one device tied to the CryptoBilis wallet drains, estimated above $86 million. What the finding changes, what is still unknown and what buyers should do now.","zh-Hans":"2026 年 10 月 10 日 UTC 17:09（北京时间 10 月 11 日凌晨 1:09），Ledger 官方支持账号发布更新：在 CryptoBilis 钱包被盗事件的一名受害者设备中，确认存在“未经授权的硬件植入物”。 这是此案第一次被确认的物理层面原因。 链上调查者估计，从这家东南亚经销商购买设备的用户损失超过 8,600 万美元。 Ledger 仍未确认受影响人数、损失金额以及植入物的工作方式，并表示自身系统没有被攻破。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"On 10 October 2026 at 17:09 UTC Ledger said one impacted user's device contained an unauthorized hardware implant and that it is reaching out to impacted users.","sourceIds":["ledger-update"],"risk":"low"},{"id":"c2","text":"CryptoBilis has ceased sales of all hardware wallet inventory until the investigation concludes, and information can be sent to bounty@ledger.fr.","sourceIds":["cointelegraph-implant"],"risk":"medium"},{"id":"c3","text":"Ledger said the incident appears isolated to one reseller and its market and its infrastructure, systems and services were not compromised; it has not confirmed losses or the number affected.","sourceIds":["cointelegraph-implant","ledger-statement"],"risk":"medium"},{"id":"c4","text":"Investigator Specter estimated losses above $86 million across Ethereum, Tron and Bitcoin.","sourceIds":["specter","cointelegraph-implant"],"risk":"medium"},{"id":"c5","text":"Ledger's reseller directory lists CryptoBilis and CryptoBilis PH.","sourceIds":["ledger-resellers"],"risk":"low"},{"id":"c6","text":"SEAL asked victims drained to the traced addresses to contact SEAL 911.","sourceIds":["seal"],"risk":"low"},{"id":"c7","text":"OKX regular spot fees are 0.08% maker and 0.10% taker; code nexu888 returns 40% of fees, settled hourly.","sourceIds":["nexualpha-partners"],"risk":"medium"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"what-is-funding-rate-crypto-perpetuals-how-it-is-calculated","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-11T06:05:56.000Z","updatedAt":"2026-10-11T06:05:56.000Z","readTime":"6 min","readTimeByLocale":{"en":"6 min","zh-Hans":"5 min","tr":"5 min","id":"6 min","vi":"8 min"},"author":"NexuAlpha Research Desk","title":{"en":"What Is the Funding Rate in Crypto Perpetual Futures? How It Is Calculated and What It Costs You (2026)","zh-Hans":"永续合约资金费率是什么？怎么计算、要付多少钱（2026）","tr":"Fonlama oranı (funding rate) nedir? Vadesiz kontratlarda nasıl hesaplanır, size ne kadara mal olur? (2026)","id":"Apa Itu Funding Rate di Kontrak Perpetual Kripto? Cara Menghitung dan Berapa Biayanya (2026)","vi":"Funding rate là gì? Cách tính phí funding hợp đồng vĩnh cửu và bạn thực sự phải trả bao nhiêu (2026)"},"summary":{"en":"The funding rate is a payment between longs and shorts on perpetual futures, usually every 8 hours. How Binance, OKX and Bybit calculate it, when it is charged and what it costs, with live examples.","zh-Hans":"资金费率是永续合约多头和空头之间定期互相支付的一笔钱：费率为正时多头付给空头，为负时空头付给多头，交易所不从中抽成。币安、OKX 和 Bybit 的算法结构相同：每 8 小时 0.01% 的利率部分，加上衡量合约价格偏离现货指数程度的溢价部分；默认每 8 小时结算一次，部分合约改为 1、2 或 4 小时。只有在结算时刻持有仓位才需要支付或收取，金额等于仓位名义价值乘以费率。","tr":"Fonlama oranı, vadesiz kontratta long ve short taraflar arasındaki düzenli ödemedir; Binance ve OKX'te varsayılan olarak Türkiye saatiyle 03:00, 11:00 ve 19:00'da uzlaşır ve tutar nominal değer çarpı orandır.","id":"Funding rate adalah pembayaran berkala antara pihak long dan short di kontrak perpetual; di Binance dan OKX bawaannya diselesaikan pukul 07.00, 15.00, dan 23.00 WIB, sebesar nilai nosional dikali tarif.","vi":"Funding rate là khoản thanh toán định kỳ giữa phe long và short trong hợp đồng vĩnh cửu; trên Binance và OKX mặc định thanh toán lúc 7:00, 15:00 và 23:00 giờ Việt Nam, bằng giá trị danh nghĩa nhân tỷ lệ."},"availableLocales":["en","zh-Hans","tr","id","vi"],"claims":[{"id":"c1","text":"Funding is paid between longs and shorts; positive rates mean longs pay shorts, negative rates mean shorts pay longs, and Binance and OKX charge no fee on it.","sourceIds":["binance-funding-faq","okx-funding"],"risk":"low"},{"id":"c2","text":"Binance, OKX and Bybit use an interest component of 0.01% per 8 hours plus an averaged premium index, clamped at ±0.05%; on Binance the rate equals 0.01% while the premium is between -0.04% and 0.06%.","sourceIds":["binance-funding-faq","okx-funding","bybit-funding"],"risk":"low"},{"id":"c3","text":"Default settlement is every 8 hours at 00:00, 08:00 and 16:00 UTC; OKX supports 1, 2, 4 and 8-hour cycles; Bybit switches to hourly settlement when a rate hits its limit.","sourceIds":["binance-funding-faq","okx-funding","bybit-funding"],"risk":"low"},{"id":"c4","text":"Binance's ERAUSDT perpetual settled five consecutive 4-hour funding rates totalling about -3.15% between 12:00 UTC on 10 October and 04:00 UTC on 11 October 2026.","sourceIds":["binance-funding-history","binance-funding-info"],"risk":"medium"},{"id":"c5","text":"At 05:57 UTC on 11 October 2026 Binance BTCUSDT funding was -0.00085% and ETHUSDT -0.011%.","sourceIds":["binance-premium-index","nexualpha-market-events"],"risk":"medium"},{"id":"c6","text":"OKX regular USDT perpetual fees are 0.02% maker and 0.05% taker; code nexu888 returns 40% of fees, settled hourly.","sourceIds":["nexualpha-partners"],"risk":"medium"}],"relatedVenues":["binance","okx","bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"binance-new-user-usdt-simple-earn-30-bonus-apr-real-value","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-11T06:04:27.000Z","updatedAt":"2026-10-11T06:04:27.000Z","readTime":"6 min","author":"NexuAlpha Research Desk","title":{"en":"Binance New-User 30% Bonus APR on USDT Simple Earn: Rules and What It Is Really Worth (October 2026)","zh-Hans":"币安新用户 USDT 活期理财额外 30% 年化：规则解读与实际能拿多少（2026 年 10 月）"},"summary":{"en":"Binance pays new users an extra 30% APR on the first 200 USDT in Flexible Simple Earn for 7 days, until 8 November 2026. Eligibility, payout timing and why it is worth about 1.24 USDT.","zh-Hans":"币安正在给新用户的 USDT 活期简单赚币（Simple Earn Flexible）额外加 30% 年化，但只针对前 200 USDT，只持续 7 天，叠加在正常的实时年化之上。 按我们的计算，额外奖励最多约 1.15 USDT，加上 10 月 11 日币安显示的约 2.42% 实时年化，总共约 1.24 USDT。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"Binance's new-user promotion runs from 2026-10-08 12:00 UTC to 2026-11-08 23:59:59 UTC for users registered after 2026-10-08 10:00 UTC who pass identity verification; master accounts only.","sourceIds":["binance-announcement"],"risk":"low"},{"id":"c2","text":"Eligible users get a 30% Bonus Tiered APR on the first 200 USDT subscribed to USDT Flexible for up to 7 days on top of real-time APR; minimum 0.1 USDT; not stackable with regional new-user APR offers.","sourceIds":["binance-announcement"],"risk":"low"},{"id":"c3","text":"A first crypto deposit, P2P purchase or fiat deposit/Buy Crypto purchase of at least 1 USD qualifies; purchases from an existing fiat balance do not.","sourceIds":["binance-announcement"],"risk":"low"},{"id":"c4","text":"Bonus accrues from the day after subscription and is paid daily to the Spot Account between 00:00 and 08:00 UTC; redemption stops the bonus on the redeemed amount from that day.","sourceIds":["binance-announcement"],"risk":"low"},{"id":"c5","text":"USDT Flexible real-time APR was 2.418% at about 06:00 UTC on 11 October 2026; the 7-day bonus on 200 USDT is about 1.15 USDT (our arithmetic).","sourceIds":["binance-simple-earn-data","binance-announcement"],"risk":"medium"},{"id":"c6","text":"The Binance Alpha STABLE competition rewards the top 2,000 buyers per round with 1,925 STABLE each across two rounds ending 16 and 23 October.","sourceIds":["binance-alpha-stable"],"risk":"low"},{"id":"c7","text":"Binance spot fees are 0.10% for regular users; code 11350287 returns 25% of fees, settled hourly.","sourceIds":["binance-spot-fee","nexualpha-partners"],"risk":"medium"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"binance-vs-bybit-fees-2026-spot-futures-after-rebate","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-11T06:03:08.000Z","updatedAt":"2026-10-11T06:03:08.000Z","readTime":"6 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs Bybit Fees in 2026: Spot, Futures, Discounts and the Cost After a Rebate","zh-Hans":"2026 年币安 vs Bybit 手续费对比：现货、合约、抵扣与返佣后的真实成本","vi":"So sánh phí giao dịch Binance và Bybit 2026: spot, futures, giảm phí và hoàn phí"},"summary":{"en":"Binance and Bybit charge the same spot fees, but Bybit's futures taker fee is 0.055% vs Binance's 0.05%. With BNB discounts and a 25% rebate Binance falls to 0.0375%. Full table and examples.","zh-Hans":"新注册账户在币安和 Bybit 的现货费率相同（挂单 0.10%、吃单 0.10%），合约挂单费也相同（0.02%），区别在合约吃单：Bybit 是 0.055%，币安是 0.05%。 币安官方公布了 BNB 抵扣（现货减免 25%、U 本位合约减免 10%），通过合作邀请码注册还能返还最多 25% 手续费，合约吃单的实际成本降到 0.0375%。","vi":"Binance và Bybit thu phí spot như nhau (0,10%/0,10%) và phí maker futures như nhau (0,02%); Bybit thu phí taker futures 0,055% so với 0,05% của Binance."},"availableLocales":["en","zh-Hans","vi"],"claims":[{"id":"c1","text":"Binance regular-user fees are 0.10%/0.10% spot and 0.02%/0.05% on USDT-M perpetuals; Bybit VIP 0 fees are 0.10%/0.10% spot and 0.02%/0.055% on perpetuals.","sourceIds":["binance-spot-fee","binance-futures-fee","bybit-fees"],"risk":"low"},{"id":"c2","text":"Binance gives 25% off spot fees and 10% off USDⓈ-M futures fees paid in BNB; Bybit's fee page names an MNT program without a percentage.","sourceIds":["binance-spot-fee","binance-futures-fee","bybit-fees"],"risk":"low"},{"id":"c3","text":"Bybit's Adventure Zone and xStocks spot fees are 0.20%/0.20% at VIP 0; Pre-Market perps 0.04%/0.10%; Innovation Zone perps 0.04%/0.11%; fiat spot pairs 0.20% taker/0.15% maker below 100,000 USD volume.","sourceIds":["bybit-fees"],"risk":"low"},{"id":"c4","text":"Binance code 11350287 returns 25% of fees, settled hourly; no Bybit share is confirmed in the partner feed.","sourceIds":["nexualpha-partners"],"risk":"medium"},{"id":"c5","text":"Both exchanges compute funding from a 0.01%-per-8-hour interest component and a premium component clamped at ±0.05%; Binance's BTCUSDT rate was -0.00085% at 05:57 UTC on 11 October 2026.","sourceIds":["binance-funding-faq","bybit-funding","binance-premium-index"],"risk":"low"},{"id":"c6","text":"Vietnam's Ministry of Finance, answering a citizen on 6 October 2026, cited Resolution 05/2025/NQ-CP Article 7(2): six months after the first licence, domestic investors trading outside licensed providers may face administrative or criminal penalties; Decree 284/2026 sets maximum fines of VND 200 million for organisations and VND 100 million for individuals.","sourceIds":["chinhphu-mof-answer","chinhphu-decree-284"],"risk":"medium"}],"relatedVenues":["binance","bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"how-to-sign-up-okx-referral-code-nexu888-fee-rebate","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-11T04:54:33.000Z","updatedAt":"2026-10-11T04:54:33.000Z","readTime":"7 min","author":"NexuAlpha Research Desk","title":{"en":"OKX Referral Code nexu888: Where to Enter It at Sign-Up, What If You Forget, and the 40% Fee Rebate (2026)","zh-Hans":"OKX 邀请码 nexu888 填在哪里：注册时怎么填、忘填怎么办、40% 手续费返佣（2026）"},"summary":{"en":"Enter OKX referral code nexu888 in the optional referral field before you finish signing up, or open the invite link that fills it in. OKX says codes usually cannot be added later.","zh-Hans":"OKX 邀请码必须在注册完成之前填写：在注册表单上展开“邀请码（选填）”一栏输入 nexu888，或者直接打开该邀请码对应的 OKX 邀请链接，系统会自动带入。OKX 官方常见问题明确说明，邀请码必须在注册完成前生效，注册后通常无法补填或更改，所以提交前一定要确认这一栏。用 nexu888 注册的账户会关联 NexuAlpha 的合作条款，交易手续费返还 40%，由 OKX 按小时结算。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"The OKX referral code is entered in the 'Referral code (optional)' field during sign-up or carried by the referral link, and must be applied before sign-up is completed.","sourceIds":["okx-referral-faq","okx-join"],"risk":"low"},{"id":"c2","text":"After registration the referral relationship usually cannot be added or changed; deleting and re-registering does not restore eligibility and multiple accounts violate the rules.","sourceIds":["okx-referral-faq"],"risk":"low"},{"id":"c3","text":"On mobile, OKX advises reopening the link, binding the email on the invite page, opening the app through the link and signing up with the same email, or entering the code manually.","sourceIds":["okx-referral-faq"],"risk":"low"},{"id":"c4","text":"OKX identity verification requires choosing the real country and nationality, being 18+, using original government-issued documents; Türkiye and the UAE have more specific requirements.","sourceIds":["okx-kyc"],"risk":"low"},{"id":"c5","text":"OKX regular-user fees are 0.08% maker / 0.10% taker on spot and 0.02% / 0.05% on USDT perpetuals; code nexu888 returns 40% of fees, settled hourly.","sourceIds":["okx-fees","nexualpha-partners"],"risk":"medium"},{"id":"c6","text":"Welcome Rewards tasks and amounts vary by region, period, channel and user group; internal transfers and certain stablecoin/fiat trades do not count; statuses update within 48 hours.","sourceIds":["okx-referral-faq"],"risk":"low"},{"id":"c7","text":"OKX TR is a separate Turkish company supporting TRY bank transfers; cross-region referrals are not rewarded unless supported.","sourceIds":["okx-tr","okx-referral-faq"],"risk":"medium"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"binance-bstocks-vs-tradfi-perps-what-you-own-hours-dividends","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-11T04:52:57.000Z","updatedAt":"2026-10-11T04:52:57.000Z","readTime":"7 min","author":"NexuAlpha Research Desk","title":{"en":"Binance bStocks vs TradFi Perps in 2026: What You Own, Trading Hours, Dividends and Fees","zh-Hans":"币安 bStocks 代币化股票和 TradFi 股票永续合约有什么区别：持有什么、交易时间、分红与费用（2026）"},"summary":{"en":"Binance bStocks like JPMB and USDEB are 1:1-backed spot tokens with reinvested dividends; TradFi perps like USDEXUSDT are 20x USDT-settled contracts with 8-hour funding. What you own, hours, dividends and fees compared.","zh-Hans":"在币安上，同一只美股现在可以用两种完全不同的方式参与。 bStocks（例如 JPMB、USDEB）是币安关联公司在阿布扎比发行的现货代币，背后有对应股票支撑，可以 1:1 换成正股，分红自动再投资进余额，但它不是股票，也没有投票权。 TradFi 永续合约（例如 USDEXUSDT）是以 USDT 结算的衍生品，最高 20 倍杠杆、每 8 小时结算资金费率，你不持有任何资产，可能被强平，盈亏取决于币安的价格指数。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"Binance listed JPMB, LLYB, SECZB and USDEB bStocks against USDT on 7 October 2026 at 12:00 UTC with zero maker fees until 31 October 2026 23:59 UTC.","sourceIds":["bn-bstocks-listing"],"risk":"low"},{"id":"c2","text":"bStocks are certificates issued by BTech Holdings Limited, an ADGM SPV and Binance affiliate; they are not shares and carry no direct voting or dividend rights, but convert 1:1 to the underlying share with zero conversion fees.","sourceIds":["bn-bstocks-faq","bn-bstocks-listing"],"risk":"low"},{"id":"c3","text":"bStock dividends are reinvested net of withholding tax through a balance multiplier.","sourceIds":["bn-bstocks-faq","bn-mrvl-orcl"],"risk":"low"},{"id":"c4","text":"USDEXUSDT, VKTXUSDT, MCDUSDT and AKAMUSDT are USDT-settled perps with up to 20x leverage, 8-hour funding capped at ±2% and 24/7 trading.","sourceIds":["bn-tradfi-listing"],"risk":"low"},{"id":"c5","text":"At weekends and holidays the index for equity TradFi perps uses Binance's order book (EWMA) and mark price may deviate up to ±3% from the index.","sourceIds":["bn-tradfi-faq"],"risk":"medium"},{"id":"c6","text":"The four bStocks became collateral in Cross Margin, Portfolio Margin and Portfolio Margin Pro without borrowing support.","sourceIds":["bn-bstocks-collateral"],"risk":"low"},{"id":"c7","text":"Binance regular-user fees are 0.10% spot maker/taker and 0.02%/0.05% on USDⓈ-M perpetuals; code 11350287 returns 25% of fees, settled hourly.","sourceIds":["bn-fees","nexualpha-partners"],"risk":"medium"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"ledger-cryptobilis-reseller-wallet-drains-what-to-do","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-11T04:50:58.000Z","updatedAt":"2026-10-11T04:50:58.000Z","readTime":"7 min","author":"NexuAlpha Research Desk","title":{"en":"Ledger CryptoBilis Wallet Drains: What Happened and What to Do If You Bought From a Reseller (2026)","zh-Hans":"Ledger 经销商 CryptoBilis 钱包被盗事件：发生了什么，从经销商买的硬件钱包该怎么办（2026）","tr":"Ledger CryptoBilis Olayı: Bayiden Alınan Cüzdanlar Boşaltıldı, Türkiye'deki Kullanıcılar Ne Yapmalı? (2026)"},"summary":{"en":"Ledger is investigating stolen funds from users who bought devices from Southeast Asian reseller CryptoBilis and paused its sales. Investigators estimate $72–86 million; Ledger has not confirmed a figure.","zh-Hans":"2026 年 10 月 9 日，硬件钱包厂商 Ledger 表示正在调查东南亚用户资金被盗的报告，这些用户都是从授权经销商 CryptoBilis 购买的设备；Ledger 已要求该经销商暂停全部销售和发货。 链上调查者估计可疑损失在 7200 万美元以上到 8600 万美元以上之间，但 Ledger 没有确认任何金额，也没有公布原因。","tr":"Ledger, Güneydoğu Asya'daki yetkili bayi CryptoBilis'ten cihaz alan kullanıcıların fon kaybı bildirimlerini inceliyor ve bayinin satışlarını durdurdu."},"availableLocales":["en","zh-Hans","tr"],"claims":[{"id":"c1","text":"Ledger is investigating reports of loss of funds from Southeast Asian users who bought from reseller CryptoBilis and asked the reseller to pause all sales and shipments.","sourceIds":["ledger-statement"],"risk":"low"},{"id":"c2","text":"Ledger advises buyers from the reseller in the last 90 days not to set up the device and, if already set up, to consider moving assets to a new Ledger signer with a new seed.","sourceIds":["ledger-statement"],"risk":"low"},{"id":"c3","text":"Ledger's reseller directory lists CryptoBilis for Indonesia and Malaysia and CryptoBilis PH for the Philippines; it does not list CryptoBilis for Türkiye.","sourceIds":["ledger-resellers"],"risk":"low"},{"id":"c4","text":"Investigators estimated suspected losses at more than $72 million (tanuki42) and more than $86 million (Specter); Ledger has not confirmed a figure.","sourceIds":["tanuki42","specter","coindesk","cointelegraph"],"risk":"medium"},{"id":"c5","text":"Ledger told Cointelegraph the incident appears isolated to the reseller and market and that its infrastructure, systems and services were not compromised.","sourceIds":["cointelegraph"],"risk":"medium"},{"id":"c6","text":"Onchain Lens reported about $270,000 deposited to Binance, 430.2 ETH sent to Tornado Cash and about $70.6 million still held in tracked wallets.","sourceIds":["onchainlens"],"risk":"medium"},{"id":"c7","text":"A supply-chain attack with a pre-known recovery phrase is a possible but unconfirmed explanation.","sourceIds":["coindesk","cz"],"risk":"medium"},{"id":"c8","text":"OKX regular USDT perpetual fees are 0.02% maker and 0.05% taker; code nexu888 returns 40% of fees, settled hourly.","sourceIds":["okx-fees","nexualpha-partners"],"risk":"medium"},{"id":"c9","text":"OKX TR is a separate Turkish entity with TRY bank-transfer deposits; OKX states Türkiye has specific identity-document requirements and cross-region referrals may not count.","sourceIds":["okx-tr","okx-kyc","okx-referral-faq"],"risk":"medium"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"okx-unified-tokenized-stocks-what-you-own-dividends-hours","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-10T13:04:03.000Z","updatedAt":"2026-10-10T13:04:03.000Z","readTime":"7 min","author":"NexuAlpha Research Desk","title":{"en":"OKX Unified Tokenized Stocks Explained: What You Own, 24/7 Hours, Dividends and Who Can Trade (2026)","zh-Hans":"OKX 统一代币化股票详解：你到底持有什么、7×24 小时交易、分红怎么发、谁能买（2026）"},"summary":{"en":"OKX Unified Tokenized Stocks (xStocks-based, 24/7, USDT pairs) give share-for-share price exposure, not ownership. Rights, dividends, U.S. restriction, the Oct 9 and Oct 12 listings and costs explained.","zh-Hans":"OKX 统一代币化股票（Unified Tokenized Stocks）是一类现货资产，命名方式是在美股代码前加一个“X”，按“股”为单位提供美股或 ETF 的价格敞口，以 USDT 计价，全天候交易。 它基于 Payward 的 xStocks 框架，可以作为 xStocks 提取到 Solana 或 X Layer 网络，分红会以份额余额小幅增加的方式发到你的账户。 但它不让你成为股东，没有投票权，也不能向美国人士发售。"},"claims":[{"id":"c1","text":"Unified Tokenized Stocks give price exposure in share units with an X-prefixed ticker, traded 24/7 against USDT, powered by Payward's xStocks with deposits and withdrawals on Solana and X Layer.","sourceIds":["okx-uts"],"risk":"low"},{"id":"c2","text":"They do not represent ownership or confer voting rights, are not OKX-issued tokens, and may not be offered or sold to U.S. persons.","sourceIds":["okx-uts"],"risk":"low"},{"id":"c3","text":"Dividends are reinvested at the issuer level and passed on as a share-balance increase net of withholding tax; trading is not paused.","sourceIds":["okx-uts"],"risk":"low"},{"id":"c4","text":"First batch (xBRKB, xWEN, xAEHR, xCRDO, xFLNC, xOUST, xGPRO, xPOET) opened 9 Oct 2026; second batch (xQNT, xAMC, xBB, xIONQ, xCGNX, xFLY, xFWDI, xINFQ) on 12 Oct 2026.","sourceIds":["okx-uts"],"risk":"low"},{"id":"c5","text":"Outside U.S. market hours prices use the last close plus a market estimate; index-based price limits with parameters J, X, Y, Z apply.","sourceIds":["okx-uts"],"risk":"low"},{"id":"c6","text":"OKX regular spot fees are 0.08% maker and 0.10% taker; code nexu888 returns 40% of fees hourly.","sourceIds":["okx-fees","nexualpha-partners"],"risk":"medium"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bitget-acn-stock-perp-dividend-settlement-longs-shorts","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-10T13:02:39.000Z","updatedAt":"2026-10-10T13:02:39.000Z","readTime":"6 min","author":"NexuAlpha Research Desk","title":{"en":"Bitget ACN Stock Perp Dividend: Longs Get $1.71 a Share, Shorts Pay It on 13 October 2026","zh-Hans":"Bitget ACN 股票永续合约分红结算：10 月 13 日多头每股收 1.71 美元，空头要付"},"summary":{"en":"Bitget settles a $1.71-per-share ACN dividend on its ACNSTOCKUSDT stock perp from 13 Oct 2026, 00:00 UTC: longs are credited, shorts are charged as a funding fee. Timing, examples and margin risk.","zh-Hans":"Bitget 将于 2026 年 10 月 13 日 08:00（UTC+8，即 UTC 0 点）起，对 ACNSTOCKUSDT 股票永续合约进行每股 1.71 美元的现金分红结算。结算时持有多仓的用户按仓位大小以资金费的形式收到这笔钱，持有空仓的用户则以资金费的形式被扣除同样金额，以结算时刻的持仓快照为准。如果你持有空单，尤其是高杠杆空单，务必在快照前补足保证金或提前平仓，否则这笔扣款可能把仓位推向强平。"},"claims":[{"id":"c1","text":"Bitget settles a 1.71 USD per share cash dividend on ACNSTOCKUSDT starting 2026-10-13 08:00 UTC+8; ex-dividend date 2026-10-13 ET.","sourceIds":["bitget-acn"],"risk":"low"},{"id":"c2","text":"Longs are credited and shorts are charged the dividend as a funding fee based on a position snapshot; long and short positions on one UID are netted.","sourceIds":["bitget-acn"],"risk":"low"},{"id":"c3","text":"Bitget warns the deduction may cause insufficient margin and liquidation for shorts and recommends topping up or closing before settlement.","sourceIds":["bitget-acn"],"risk":"low"},{"id":"c4","text":"Recent Bitget stock perps are USDT-settled, up to 20x, trade 24/7 and settle funding every eight hours, and confer no dividend rights.","sourceIds":["bitget-stockperps"],"risk":"medium"},{"id":"c5","text":"OKX Unified Tokenized Stocks reinvest dividends at the issuer level as a share-balance increase net of withholding tax.","sourceIds":["okx-uts"],"risk":"low"},{"id":"c6","text":"Bitget VIP 0 futures fees are 0.02% maker / 0.06% taker; code nexu888 returns 60% of fees, settled daily.","sourceIds":["bitget-fee","nexualpha-partners"],"risk":"medium"}],"relatedVenues":["bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"october-10-crypto-crash-one-year-later-liquidity-leverage","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-10T13:01:11.000Z","updatedAt":"2026-10-10T13:01:11.000Z","readTime":"8 min","author":"NexuAlpha Research Desk","title":{"en":"One Year After the 10/10 Crypto Crash: Bitcoin Liquidity Is Back, Altcoins and Leverage Risk Are Not","zh-Hans":"10·10 加密暴跌一周年：比特币深度已恢复，山寨币和杠杆风险还在"},"summary":{"en":"A year after $19 billion was liquidated on 10 October 2025, bitcoin and ether order books are deeper but altcoin depth and spot volume are not. Data, this week's $1.19 billion flush and what to watch.","zh-Hans":"2025 年 10 月 10 日，加密市场单日爆仓超过 190 亿美元，是有记录以来规模最大的一次强平。一年后再看，比特币和以太坊订单簿按美元计算的深度已经超过暴跌当天；但山寨币的深度还在持续下滑，中心化交易所每周现货成交额仍比暴跌那一周低了将近三分之二。杠杆风险也没有消失：2026 年 10 月 8 日到 9 日，24 小时内又有 11.9 亿美元仓位被强平，以太坊按市值折算的爆仓强度约为比特币的六倍。"},"claims":[{"id":"c1","text":"More than $19 billion of leveraged positions were liquidated on 10 October 2025 as bitcoin fell from about $122,600 to below $105,000.","sourceIds":["cd-liquidity"],"risk":"low"},{"id":"c2","text":"Bitcoin depth within 1% was about $11.7M on 7 October 2026, roughly 75% above crash day; ether 0.5% depth more than doubled to about $4.2M.","sourceIds":["cd-liquidity"],"risk":"medium"},{"id":"c3","text":"Altcoin depth 5% from price fell about a third since January 2025 to around $2M; weekly spot volume averaged about $279B versus $801B in the crash week.","sourceIds":["cd-liquidity"],"risk":"medium"},{"id":"c4","text":"On 8-9 October 2026, $1.19B was liquidated in 24 hours, ether $356M versus bitcoin $298M, about six times bitcoin's rate relative to market value.","sourceIds":["cd-flush"],"risk":"medium"},{"id":"c5","text":"About 78% of roughly $25M liquidated in the following four hours were shorts after Trump ruled out an Iran strike before the midterms.","sourceIds":["cd-flush"],"risk":"low"},{"id":"c6","text":"OKX regular USDT perpetual fees are 0.02% maker and 0.05% taker; code nexu888 returns 40% of fees hourly.","sourceIds":["okx-fees","nexualpha-partners"],"risk":"medium"}],"relatedVenues":["hyperliquid","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-sign-up-bitget-referral-code-fee-rebate","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-10T11:40:30.000Z","updatedAt":"2026-10-10T11:40:30.000Z","readTime":"6 min","author":"NexuAlpha Research Desk","title":{"en":"How to Sign Up on Bitget in 2026: Referral Code nexu888, Setup Steps and Up to 60% Fee Rebate","zh-Hans":"2026 年 Bitget 注册教程：邀请码 nexu888、开户步骤与最高 60% 手续费返佣"},"summary":{"en":"Step-by-step Bitget sign-up: where to enter referral code nexu888, password rules, 2FA and anti-phishing setup, VIP 0 fees and how up to 60% of fees comes back daily.","zh-Hans":"在 Bitget 注册页选择邮箱或手机号，在选填的“邀请码”一栏填入 nexu888，设置 8 到 32 位的密码，再输入 Bitget 发来的 6 位验证码，就完成了开户。注册免费，不需要任何证件。注册时填写邀请码，账户才会绑定 NexuAlpha 的合作条件：手续费最高返还 60%，由 Bitget 官方每天自动结算。"},"claims":[{"id":"c1","text":"Bitget registration offers email or mobile sign-up with an optional referral code field, then a password and a 6-digit verification code.","sourceIds":["bitget-register"],"risk":"low"},{"id":"c2","text":"Bitget passwords must be 8 to 32 characters with at least one number, one uppercase letter and one special character.","sourceIds":["bitget-register"],"risk":"low"},{"id":"c3","text":"Bitget states that registration is free and requires no documents.","sourceIds":["bitget-register"],"risk":"low"},{"id":"c4","text":"Bitget's Official Verification Tool checks whether a webpage, email or social account is official and allows reporting.","sourceIds":["bitget-official-channels"],"risk":"low"},{"id":"c5","text":"The anti-phishing code is set under Security > Advanced Security > Anti-Phishing Code.","sourceIds":["bitget-anti-phishing"],"risk":"low"},{"id":"c6","text":"Bitget VIP 0 fees are 0.10%/0.10% on spot and 0.02%/0.06% on USDT-M futures.","sourceIds":["bitget-fee"],"risk":"low"},{"id":"c7","text":"NexuAlpha's Bitget referral code nexu888 returns up to 60% of trading fees, settled daily by Bitget.","sourceIds":["nexualpha-partners"],"risk":"medium"}],"relatedVenues":["bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-spot-trading-tournament-season-4-rules-rewards-cost","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-10T11:40:30.000Z","updatedAt":"2026-10-10T11:40:30.000Z","readTime":"6 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Spot Trading Tournament Season 4: Rules, Rewards and What Entry Really Costs","zh-Hans":"币安现货交易赛第 4 季：规则、奖金分配和参赛真实成本"},"summary":{"en":"Binance's Spot Trading Tournament Season 4 (Oct 9-16, 2026) shares 400 BNB among users who trade 500 USD of ZEC/USDC or USUAL/USDT. Here are the reward tiers, the fee cost of entry and who it is worth it for.","zh-Hans":"币安现货交易赛第 4 季从 2026 年 10 月 9 日 10:00（UTC）持续到 10 月 16 日 10:00（UTC），总奖池为 400 BNB 代币券，已完成身份认证的用户只要在 ZEC/USDC 或 USUAL/USDT 上累计交易满 500 美元即可参与排名。"},"claims":[{"id":"c1","text":"The promotion runs from 2026-10-09 10:00 UTC to 2026-10-16 10:00 UTC with a 400 BNB token voucher pool.","sourceIds":["binance-sts4"],"risk":"low"},{"id":"c2","text":"Eligible pairs are ZEC/USDC and USUAL/USDT and the qualification threshold is 500 USD of total trading volume.","sourceIds":["binance-sts4"],"risk":"low"},{"id":"c3","text":"Verified new, regular and VIP 1-6 users may join; Spot Liquidity Provider Program members, Binance Brokers and EEA users are excluded.","sourceIds":["binance-sts4"],"risk":"medium"},{"id":"c4","text":"Main reward tiers: 12/10/8/6/4 BNB for places 1-5, 40 BNB split for 6-20, 40 BNB for 21-50, 64 BNB for 51-200, 56 BNB for 201-1,000, and a proportional 80 BNB pool capped at 0.05 BNB per user.","sourceIds":["binance-sts4"],"risk":"medium"},{"id":"c5","text":"Sprint rounds run 2026-10-09 10:00 to 10-11 10:00 UTC and 10-11 10:01 to 10-13 10:00 UTC with 12/10/8/6/4 BNB for the top five.","sourceIds":["binance-sts4"],"risk":"low"},{"id":"c6","text":"Vouchers are distributed by 2026-10-30 and expire within 21 days after distribution.","sourceIds":["binance-sts4"],"risk":"low"},{"id":"c7","text":"Binance's regular-user spot fee is 0.10% maker and 0.10% taker.","sourceIds":["binance-fee"],"risk":"low"},{"id":"c8","text":"NexuAlpha's Binance referral code 11350287 returns up to 25% of trading fees, settled hourly by Binance.","sourceIds":["nexualpha-partners"],"risk":"medium"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-vs-bitget-vs-binance-fees-after-rebate","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-10T11:40:30.000Z","updatedAt":"2026-10-10T11:40:30.000Z","readTime":"6 min","author":"NexuAlpha Research Desk","title":{"en":"OKX vs Bitget vs Binance Fees in 2026: Which Is Cheapest After Rebates?","zh-Hans":"2026 年 OKX、Bitget、币安手续费对比：算上返佣谁最便宜？"},"summary":{"en":"OKX, Bitget and Binance fees compared for spot and futures, before and after referral rebates. Bitget's 0.06% futures taker fee becomes the cheapest at 0.024% once 60% comes back.","zh-Hans":"只看普通用户标价，OKX 现货最便宜，合约和币安持平，Bitget 的合约吃单费最贵；但把合作邀请码的手续费返佣算进去，排名就反过来了：Bitget 在所有产品上都最便宜（现货 0.04%、合约吃单 0.024%），OKX 第二，返佣比例最低的币安反而最贵。对经常做合约的用户来说，这个差距最明显。"},"claims":[{"id":"c1","text":"OKX regular-user fees are 0.08%/0.10% on spot and 0.02%/0.05% on USDT-margined futures.","sourceIds":["okx-fees"],"risk":"low"},{"id":"c2","text":"Bitget VIP 0 fees are 0.10%/0.10% on spot and 0.02%/0.06% on USDT-M futures.","sourceIds":["bitget-fee"],"risk":"low"},{"id":"c3","text":"Binance regular-user fees are 0.10%/0.10% on spot and 0.02%/0.05% on USDT-M perpetuals.","sourceIds":["binance-spot-fee","binance-futures-fee"],"risk":"low"},{"id":"c4","text":"NexuAlpha partner shares return up to 40% (OKX, hourly), 60% (Bitget, daily) and 25% (Binance, hourly) of trading fees.","sourceIds":["nexualpha-partners"],"risk":"medium"},{"id":"c5","text":"After rebates the effective futures taker rate is 0.030% on OKX, 0.024% on Bitget and 0.0375% on Binance.","sourceIds":["okx-fees","bitget-fee","binance-futures-fee","nexualpha-partners"],"risk":"medium"}],"relatedVenues":["okx","bitget","binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-advanced-trade-websocket-account-channel-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-10T08:58:00.000Z","updatedAt":"2026-10-10T08:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Advanced Trade WebSocket Account Channel Checklist","zh-Hans":"Coinbase Advanced Trade WebSocket 账户通道清单"},"summary":{"en":"Coinbase Advanced Trade WebSocket work should be treated as account-channel change control, not as a simple market-data socket.","zh-Hans":"Coinbase Advanced Trade WebSocket 账户通道清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Advanced Trade WebSocket documentation describes setup, authentication and subscription workflows for Advanced Trade WebSockets.","sourceIds":["coinbase-ws-auth"],"risk":"medium"},{"id":"c2","text":"Coinbase List Accounts API reference documents an authenticated endpoint for retrieving account information.","sourceIds":["coinbase-list-accounts"],"risk":"medium"},{"id":"c3","text":"Coinbase Advanced Trade Portfolios documentation says portfolios can segregate strategies and that API keys can be scoped to portfolio resources.","sourceIds":["coinbase-portfolios"],"risk":"medium"},{"id":"c4","text":"Coinbase Create Portfolio API reference documents a portfolio endpoint requiring authorization.","sourceIds":["coinbase-create-portfolio"],"risk":"medium"},{"id":"c5","text":"Together, these sources support a checklist for account-channel scope, authorization and reconciliation rather than a blanket claim that every key can access every account.","sourceIds":["coinbase-ws-auth","coinbase-list-accounts","coinbase-portfolios"],"risk":"low"},{"id":"c6","text":"These sources do not prove a private account can create portfolios, trade every product, avoid compliance review, bypass region rules or recover from an integration failure.","sourceIds":["coinbase-portfolios","coinbase-list-accounts"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-vs-bybit-private-api-auth-session-replay-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-10T08:58:00.000Z","updatedAt":"2026-10-10T08:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase vs Bybit Private API Auth, Session and Replay Controls","zh-Hans":"Coinbase 与 Bybit 私有 API 认证、会话与重放控制对比"},"summary":{"en":"Coinbase Advanced Trade and Bybit V5 both expose authenticated private API surfaces, but the control model should not be shared as one generic crypto-exchange connector.","zh-Hans":"Coinbase 与 Bybit 私有 API 认证、会话与重放控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Advanced Trade WebSocket documentation describes WebSocket setup, authentication and subscription surfaces for Advanced Trade data.","sourceIds":["coinbase-ws-auth"],"risk":"medium"},{"id":"c2","text":"Coinbase List Accounts API reference describes an authenticated account endpoint using bearer-token authorization.","sourceIds":["coinbase-list-accounts"],"risk":"medium"},{"id":"c3","text":"Bybit V5 Integration Guidance documents authentication expectations for V5 API requests.","sourceIds":["bybit-v5-guide"],"risk":"medium"},{"id":"c4","text":"Bybit V5 Error Codes documentation includes permission-denied and API-key-expiry failure labels that can be logged without exposing secrets.","sourceIds":["bybit-v5-error"],"risk":"medium"},{"id":"c5","text":"Bybit Rate Limit Rules documentation provides source material for per-endpoint and account-level request budgeting.","sourceIds":["bybit-v5-rate-limit"],"risk":"low"},{"id":"c6","text":"These sources do not prove private account eligibility, regional access, live order execution, support recovery, latency, fill quality or future API compatibility.","sourceIds":["coinbase-ws-auth","coinbase-list-accounts","bybit-v5-guide","bybit-v5-error"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-private-api-error-code-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-10T08:58:00.000Z","updatedAt":"2026-10-10T08:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Private API Error-Code Disclosure Radar","zh-Hans":"加密平台私有 API 错误码披露雷达"},"summary":{"en":"NexuAlpha Radar treats private API error codes as disclosure evidence only when the code can be mapped to a public source without exposing credentials.","zh-Hans":"加密平台私有 API 错误码披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit V5 Error Codes documentation includes permission and API-key-expiry labels suitable for non-secret incident classification.","sourceIds":["bybit-v5-error"],"risk":"medium"},{"id":"c2","text":"Bybit V5 Rate Limit Rules documentation provides a source for rate-limit classification and retry budgeting.","sourceIds":["bybit-v5-rate-limit"],"risk":"medium"},{"id":"c3","text":"Coinbase List Accounts API reference documents an authenticated account endpoint using authorization.","sourceIds":["coinbase-list-accounts"],"risk":"medium"},{"id":"c4","text":"Coinbase Advanced Trade WebSocket documentation describes authenticated WebSocket setup and subscription surfaces.","sourceIds":["coinbase-ws-auth"],"risk":"medium"},{"id":"c5","text":"OKX API documentation describes private WebSocket login and subscription controls that should be treated as venue-specific session evidence.","sourceIds":["okx-api-docs"],"risk":"low"},{"id":"c6","text":"These sources do not prove private account eligibility, support recovery, live order safety, compliance status, regional access, uptime or future endpoint availability.","sourceIds":["bybit-v5-error","coinbase-list-accounts","okx-api-docs"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-collateral-appchain-transfer-agent-recordkeeping-controls","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-10T08:58:00.000Z","updatedAt":"2026-10-10T08:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Collateral AppChain and Transfer-Agent Recordkeeping Controls","zh-Hans":"DTCC Collateral AppChain 与 Transfer-Agent 记录控制"},"summary":{"en":"DTCC Collateral AppChain and transfer-agent modernization answer different RWA control questions. DTCC describes Collateral AppChain as a framework for collateral visibility, rules and movement, while Chainlink SmartData.","zh-Hans":"DTCC Collateral AppChain 与 Transfer-Agent 记录控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"DTCC Collateral AppChain documentation describes collateral visibility, rules and movement across a digital-asset collateral framework.","sourceIds":["dtcc-collateral-appchain"],"risk":"medium"},{"id":"c2","text":"DTCC's Chainlink collaboration announcement describes efforts to advance 24/7 collateral management and connect data with collateral workflows.","sourceIds":["dtcc-chainlink-collateral"],"risk":"medium"},{"id":"c3","text":"Chainlink SmartData documentation describes onchain data offerings for real-world asset reporting patterns including reserves, NAV, AUM and multi-variable reports.","sourceIds":["chainlink-smartdata"],"risk":"medium"},{"id":"c4","text":"SEC transfer-agent modernization material describes transfer agents as important recordkeeping participants in clearance and settlement.","sourceIds":["sec-transfer-agent-modernization"],"risk":"medium"},{"id":"c5","text":"Together, the sources support a readiness map across data, collateral movement and records, not a claim that every tokenized collateral workflow is legally final.","sourceIds":["dtcc-collateral-appchain","dtcc-chainlink-collateral","chainlink-smartdata","sec-transfer-agent-modernization"],"risk":"low"},{"id":"c6","text":"These sources do not prove ownership rights, redemption, custody, tax treatment, investor eligibility, reserve sufficiency, insolvency outcome or secondary-market liquidity.","sourceIds":["dtcc-collateral-appchain","sec-transfer-agent-modernization"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-regulation-crypto-assets-safe-harbor-state-preemption-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-10T08:58:00.000Z","updatedAt":"2026-10-10T08:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Regulation Crypto Assets Safe-Harbor and State-Preemption Risk Map","zh-Hans":"SEC Regulation Crypto Assets 安全港与州法优先风险地图"},"summary":{"en":"The SEC Regulation Crypto Assets proposal is decision-relevant because it separates offering pathways, safe-harbor conditions and state-preemption effects from broad crypto-market headlines.","zh-Hans":"SEC Regulation Crypto Assets 安全港与州法优先风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"SEC's August 2026 press release says Regulation Crypto Assets would create a tailored securities offering regime for certain investment contracts involving crypto assets.","sourceIds":["sec-regulation-crypto-assets"],"risk":"medium"},{"id":"c2","text":"SEC's August 2026 release says the proposal includes a conditional safe harbor from the term investment contract when specified conditions are satisfied.","sourceIds":["sec-regulation-crypto-assets"],"risk":"medium"},{"id":"c3","text":"SEC's August 2026 release says the proposal would preempt state securities law registration and qualification requirements for covered offers, sales and certain secondary market transactions.","sourceIds":["sec-regulation-crypto-assets"],"risk":"medium"},{"id":"c4","text":"SEC's March 2026 interpretation provides taxonomy framing for crypto assets and transactions under federal securities laws.","sourceIds":["sec-crypto-interpretation"],"risk":"medium"},{"id":"c5","text":"The SEC Crypto Newsroom lists the proposal and related crypto-policy materials as official SEC crypto-task-force materials.","sourceIds":["sec-crypto-newsroom"],"risk":"low"},{"id":"c6","text":"These sources do not prove that any issuer, token, exchange, wallet, broker, state, secondary venue or investor route qualifies under the proposal or future final rules.","sourceIds":["sec-regulation-crypto-assets","sec-crypto-interpretation"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-okx-websocket-rate-limit-session-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-10T05:58:00.000Z","updatedAt":"2026-10-10T05:58:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs OKX WebSocket Rate-Limit and Session Controls","zh-Hans":"Binance 与 OKX WebSocket 限流和会话控制对比"},"summary":{"en":"Binance and OKX both support WebSocket-based account and market workflows, but their operating controls should be implemented as venue-specific session policies.","zh-Hans":"Binance 与 OKX WebSocket 限流和会话控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance Spot WebSocket API account pages describe signed USER_DATA methods and request-weight accounting for account-related calls.","sourceIds":["binance-ws-account"],"risk":"medium"},{"id":"c2","text":"Binance User Data Stream documentation describes WebSocket subscription surfaces and request weight for session subscription methods.","sourceIds":["binance-ws-user-data-stream"],"risk":"medium"},{"id":"c3","text":"OKX WebSocket documentation describes connection limits, login operations, private channel login requirements and subscription request limits.","sourceIds":["okx-websocket-guide"],"risk":"medium"},{"id":"c4","text":"OKX upcoming changes documentation says port 8443 WebSocket connections will stop being accepted after the stated transition date and that port 443 should be used.","sourceIds":["okx-upcoming-changes"],"risk":"medium"},{"id":"c5","text":"Together, the sources support a venue-specific session-control checklist rather than a universal WebSocket client assumption.","sourceIds":["binance-ws-user-data-stream","binance-ws-account","okx-websocket-guide","okx-upcoming-changes"],"risk":"low"},{"id":"c6","text":"These sources do not prove private account eligibility, live order execution, regional access, uptime, latency, fill quality or support recovery.","sourceIds":["binance-ws-user-data-stream","binance-ws-account","okx-websocket-guide"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-v5-api-key-ip-permission-change-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-10T05:58:00.000Z","updatedAt":"2026-10-10T05:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit V5 API Key IP and Permission Change Checklist","zh-Hans":"Bybit V5 API Key IP 与权限变更清单"},"summary":{"en":"Bybit V5 API-key operations should be treated as a permission and IP-binding change-control task, not a generic login step.","zh-Hans":"Bybit V5 API Key IP 与权限变更清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit V5 changelog includes API-key-related changes and records limitations around IP address modification through API workflows.","sourceIds":["bybit-v5-changelog"],"risk":"medium"},{"id":"c2","text":"Bybit Get API Key Information documentation describes an endpoint for retrieving API-key information and permission fields.","sourceIds":["bybit-api-key-info"],"risk":"medium"},{"id":"c3","text":"Bybit Integration Guidance documents authentication expectations for system-generated API keys and V5 request handling.","sourceIds":["bybit-integration-guide"],"risk":"medium"},{"id":"c4","text":"Bybit Error Codes documentation includes permission-denied and API-key-expired failure labels that should be captured without secrets.","sourceIds":["bybit-error-codes"],"risk":"medium"},{"id":"c5","text":"Bybit Rate Limit Rules documentation provides a source for classifying rate-limit exposure before production integration.","sourceIds":["bybit-rate-limit"],"risk":"low"},{"id":"c6","text":"These sources do not prove a user's account may create every key type, avoid compliance review, bypass regional rules, recover a deleted key or trade successfully.","sourceIds":["bybit-api-key-info","bybit-error-codes"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"chainlink-smartdata-vs-dtcc-collateral-appchain-rwa-readiness-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-10T05:58:00.000Z","updatedAt":"2026-10-10T05:58:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Chainlink SmartData vs DTCC Collateral AppChain: RWA Readiness Map","zh-Hans":"Chainlink SmartData 与 DTCC Collateral AppChain：RWA 准备度地图"},"summary":{"en":"Chainlink SmartData and DTCC Collateral AppChain address different parts of the tokenized-asset operating stack.","zh-Hans":"Chainlink SmartData 与 DTCC Collateral AppChain：RWA 准备度地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Chainlink SmartData documentation describes onchain data offerings for tokenized real-world assets, including reserves, NAV, AUM and multi-variable report patterns.","sourceIds":["chainlink-smartdata-docs"],"risk":"medium"},{"id":"c2","text":"Chainlink Data Feeds documentation describes data-feed families and warns integrators to review feed quality and assume responsibility for use of feeds in smart contracts.","sourceIds":["chainlink-data-feeds"],"risk":"medium"},{"id":"c3","text":"DTCC Collateral AppChain documentation describes a shared framework for collateral visibility, rules and movement across existing infrastructure.","sourceIds":["dtcc-collateral-appchain"],"risk":"medium"},{"id":"c4","text":"SEC transfer-agent modernization material frames transfer agents as part of the clearance and settlement system and discusses modernization in light of electronic and blockchain-related processes.","sourceIds":["sec-transfer-agent-modernization"],"risk":"medium"},{"id":"c5","text":"These sources support a readiness map across data, collateral movement and recordkeeping, not a claim that any one RWA product is approved or risk-free.","sourceIds":["chainlink-smartdata-docs","dtcc-collateral-appchain","sec-transfer-agent-modernization"],"risk":"low"},{"id":"c6","text":"These sources do not prove redemption, ownership rights, custody, tax treatment, reserve sufficiency, secondary-market liquidity or investor eligibility.","sourceIds":["chainlink-smartdata-docs","dtcc-collateral-appchain"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-bybit-api-key-read-only-ip-restriction-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-10T05:58:00.000Z","updatedAt":"2026-10-10T05:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up a Bybit API Key with Read-Only and IP Restrictions Safely","zh-Hans":"如何安全设置 Bybit API Key 的只读权限与 IP 限制"},"summary":{"en":"A safe Bybit API-key setup starts with read-only scope, fixed IP planning and non-secret evidence, not with broad trading permissions.","zh-Hans":"如何安全设置 Bybit API Key 的只读权限与 IP 限制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit Integration Guidance documents V5 API authentication expectations and system-generated API-key behavior.","sourceIds":["bybit-integration-guide"],"risk":"medium"},{"id":"c2","text":"Bybit Get API Key Information documentation describes an endpoint for retrieving API-key metadata and permission-related information.","sourceIds":["bybit-api-key-info"],"risk":"medium"},{"id":"c3","text":"Bybit Error Codes documentation includes permission-denied and key-expiry labels that can be recorded without exposing secrets.","sourceIds":["bybit-error-codes"],"risk":"medium"},{"id":"c4","text":"Bybit Rate Limit Rules documentation provides the source for request and traffic-limit planning before a production bot is enabled.","sourceIds":["bybit-rate-limit"],"risk":"medium"},{"id":"c5","text":"A read-only and IP-restricted onboarding flow is a safety procedure derived from the documented surfaces, not a guarantee that an account is eligible for every feature.","sourceIds":["bybit-integration-guide","bybit-api-key-info","bybit-rate-limit"],"risk":"low"},{"id":"c6","text":"This tutorial does not ask the reader to reveal API keys, passwords, identity documents, one-time codes, seed phrases, tax identifiers or account balances.","sourceIds":["bybit-integration-guide","bybit-error-codes"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-innovation-exemption-tokenized-nms-stock-amm-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-10T05:58:00.000Z","updatedAt":"2026-10-10T05:58:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Innovation Exemption Tokenized NMS Stock AMM Risk Map","zh-Hans":"SEC Innovation Exemption 代币化 NMS 股票 AMM 风险地图"},"summary":{"en":"The SEC Innovation Exemption is decision-relevant because it narrows tokenized-stock market structure into a conditional experiment, not a blanket approval.","zh-Hans":"SEC Innovation Exemption 代币化 NMS 股票 AMM 风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"SEC press-release material describes temporary, conditional exemptive relief for Tokenized Securities Venues trading tokenized NMS stock through permissioned AMM liquidity pools.","sourceIds":["sec-innovation-exemption-release"],"risk":"medium"},{"id":"c2","text":"SEC material describes conditions including symbol and volume limits, same-rights checks for tokenized NMS stock, public smart contracts, trading-stoppage coordination and public notice.","sourceIds":["sec-innovation-exemption-release"],"risk":"medium"},{"id":"c3","text":"Commissioner Uyeda's statement frames the exemption as scoped relief intended to support observation, transparency and future policymaking.","sourceIds":["sec-uyeda-innovation-statement"],"risk":"medium"},{"id":"c4","text":"Commissioner Peirce's statement describes the order as time-limited exemptions for onchain trading of stocks listed on major U.S. exchanges.","sourceIds":["sec-peirce-innovation-statement"],"risk":"medium"},{"id":"c5","text":"BIS 2026 material says tokenisation and stablecoin-related innovation should preserve trust in money and address macro-financial safeguards.","sourceIds":["bis-trust-money-2026"],"risk":"low"},{"id":"c6","text":"These sources do not prove any specific TSV, tokenized stock, AMM pool, broker, wallet, user, liquidity provider or jurisdiction is eligible or safe.","sourceIds":["sec-innovation-exemption-release","sec-uyeda-innovation-statement","sec-peirce-innovation-statement"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-advanced-trade-portfolio-api-key-scope-update-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-10T02:58:00.000Z","updatedAt":"2026-10-10T02:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Advanced Trade Portfolio API Key Scope Update Checklist","zh-Hans":"Coinbase Advanced Trade Portfolio API Key Scope 更新清单"},"summary":{"en":"Coinbase Advanced Trade API onboarding should be treated as portfolio-scoped key management, not a generic exchange-login step.","zh-Hans":"Coinbase Advanced Trade Portfolio API Key Scope 更新清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Advanced Trade documentation describes REST API and WebSocket protocol support for programmatic trading and market data.","sourceIds":["coinbase-advanced-trade-overview"],"risk":"medium"},{"id":"c2","text":"Coinbase API key authentication documentation describes API key based authentication and JWT bearer-token use for API calls.","sourceIds":["coinbase-api-key-authentication"],"risk":"medium"},{"id":"c3","text":"Coinbase Advanced Trade portfolio guidance says portfolios can segregate trading strategies and that each portfolio should have a dedicated CDP API key to limit access.","sourceIds":["coinbase-advanced-trade-portfolios"],"risk":"medium"},{"id":"c4","text":"The Create Portfolio reference describes authorization through a JWT signed using a CDP API Key Secret and passed as a bearer token.","sourceIds":["coinbase-create-portfolio"],"risk":"medium"},{"id":"c5","text":"Portfolio and API key documentation do not prove that a user's account is eligible for every portfolio, product, jurisdiction or permission.","sourceIds":["coinbase-advanced-trade-portfolios","coinbase-create-portfolio"],"risk":"low"},{"id":"c6","text":"These sources do not authorize credential sharing, hidden key collection, broad production permissions or untested order placement.","sourceIds":["coinbase-api-key-authentication","coinbase-advanced-trade-overview"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-order-book-sequence-checksum-gap-recovery-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-10T02:58:00.000Z","updatedAt":"2026-10-10T02:58:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Order Book Sequence, Checksum and Gap Recovery Disclosure Radar","zh-Hans":"加密订单簿 Sequence、Checksum 与 Gap Recovery 披露雷达"},"summary":{"en":"The NexuAlpha radar signal is that order-book streaming disclosures are only useful when they explain sequence integrity, checksum validation and recovery after gaps.","zh-Hans":"加密订单簿 Sequence、Checksum 与 Gap Recovery 披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Kraken provides a WebSocket v2 book checksum guide for validating local order-book state.","sourceIds":["kraken-book-checksum-v2"],"risk":"medium"},{"id":"c2","text":"Bybit documents V5 WebSocket public orderbook behavior as part of its API documentation.","sourceIds":["bybit-orderbook"],"risk":"medium"},{"id":"c3","text":"Coinbase Advanced Trade documentation describes WebSocket protocol support for real-time market data.","sourceIds":["coinbase-advanced-trade-overview"],"risk":"medium"},{"id":"c4","text":"OKX API documentation publishes product-specific API guide material across REST, WebSocket and authentication surfaces.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c5","text":"A venue's order-book stream documentation does not prove a local client reconstructs the book correctly under packet loss, reconnects or throttling.","sourceIds":["kraken-book-checksum-v2","bybit-orderbook","coinbase-advanced-trade-overview","okx-api-guide"],"risk":"low"},{"id":"c6","text":"These sources do not prove liquidity depth, execution quality, profitable market making, price direction or liquidation safety.","sourceIds":["kraken-book-checksum-v2","bybit-orderbook","coinbase-advanced-trade-overview","okx-api-guide"],"risk":"low"}],"relatedVenues":["kraken","bybit","coinbase","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fsb-global-crypto-framework-bis-stablecoin-trust-oversight-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-10T02:58:00.000Z","updatedAt":"2026-10-10T02:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"FSB Global Crypto Framework and BIS Stablecoin Trust Oversight Map","zh-Hans":"FSB 全球加密框架与 BIS 稳定币信任监管地图"},"summary":{"en":"The decision-relevant industry signal is that global crypto oversight remains a framework-and-implementation problem, not a solved approval layer.","zh-Hans":"FSB 全球加密框架与 BIS 稳定币信任监管地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"The FSB global regulatory framework page provides the policy baseline for crypto-asset activities and global stablecoin arrangements.","sourceIds":["fsb-2023-global-framework"],"risk":"medium"},{"id":"c2","text":"The BIS Annual Economic Report 2026 chapter frames trust in money as a core policy issue for the next-generation monetary and financial system.","sourceIds":["bis-annual-2026-trust-money"],"risk":"medium"},{"id":"c3","text":"BIS 2026 media-release material says stablecoins show some tokenisation potential but current forms fall short on key properties of money and could affect macroeconomic and financial stability if widely adopted.","sourceIds":["bis-2026-trust-money-release"],"risk":"medium"},{"id":"c4","text":"BIS 2026 working paper material describes measurement challenges across cryptoassets, stablecoins and DeFi data.","sourceIds":["bis-hidden-complexity-2026"],"risk":"medium"},{"id":"c5","text":"Together, these sources support a diligence map, not a claim that any specific stablecoin, venue or jurisdiction is approved or safe.","sourceIds":["fsb-2023-global-framework","bis-annual-2026-trust-money","bis-2026-trust-money-release"],"risk":"low"},{"id":"c6","text":"These sources do not establish private eligibility, redemption success, legal treatment, tax treatment, reserve sufficiency, sanctions screening or future supervision.","sourceIds":["fsb-2023-global-framework","bis-2026-trust-money-release","bis-hidden-complexity-2026"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-coinbase-advanced-trade-api-key-portfolio-permissions-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-10T02:58:00.000Z","updatedAt":"2026-10-10T02:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up a Coinbase Advanced Trade API Key and Portfolio Permissions Safely","zh-Hans":"如何安全设置 Coinbase Advanced Trade API Key 与 Portfolio 权限"},"summary":{"en":"A safe Coinbase Advanced Trade API setup is a venue-onboarding task, not a credential-collection task.","zh-Hans":"如何安全设置 Coinbase Advanced Trade API Key 与 Portfolio 权限：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Advanced Trade documentation describes REST API and WebSocket protocol support for programmatic trading and market data.","sourceIds":["coinbase-advanced-trade-overview"],"risk":"medium"},{"id":"c2","text":"Coinbase API key authentication documentation describes API key based authentication and JWT bearer-token use.","sourceIds":["coinbase-api-key-authentication"],"risk":"medium"},{"id":"c3","text":"Coinbase portfolio guidance says each Advanced Trade portfolio should have a dedicated CDP API key to limit access.","sourceIds":["coinbase-advanced-trade-portfolios"],"risk":"medium"},{"id":"c4","text":"The Create Portfolio API reference uses bearer JWT authorization for portfolio creation requests.","sourceIds":["coinbase-create-portfolio"],"risk":"medium"},{"id":"c5","text":"A portfolio-specific key setup does not prove regional eligibility, product access, suitability, tax treatment, trading success or support recovery.","sourceIds":["coinbase-advanced-trade-portfolios","coinbase-create-portfolio"],"risk":"low"},{"id":"c6","text":"This tutorial does not ask the reader to reveal API keys, seed phrases, identity documents, passwords, one-time codes or account balances.","sourceIds":["coinbase-api-key-authentication"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-vs-kraken-rest-authentication-timestamp-nonce-replay-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-10T02:58:00.000Z","updatedAt":"2026-10-10T02:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"OKX vs Kraken REST Authentication: Timestamp, Nonce and Replay Controls","zh-Hans":"OKX 与 Kraken REST 认证对比：时间戳、Nonce 与重放控制"},"summary":{"en":"OKX and Kraken both require signed private REST requests, but their replay-control models should be implemented separately.","zh-Hans":"OKX 与 Kraken REST 认证对比：时间戳、Nonce 与重放控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"OKX API documentation describes REST authentication as a signed request process using API key credentials, timestamp, method, request path and body material.","sourceIds":["okx-rest-authentication"],"risk":"medium"},{"id":"c2","text":"OKX documentation treats API access as product documentation with separate REST, WebSocket, authentication and rate-limit surfaces rather than a universal venue credential.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c3","text":"Kraken's Spot REST authentication guide describes private endpoint authentication using API-Key and API-Sign headers and a nonce value in the request data.","sourceIds":["kraken-rest-authentication"],"risk":"medium"},{"id":"c4","text":"Kraken documentation's nonce model creates a monotonicity requirement that differs from a pure timestamp-expiry control.","sourceIds":["kraken-rest-authentication"],"risk":"medium"},{"id":"c5","text":"Coinbase API key authentication provides a third reference point showing that API key authentication models differ by venue and should not be collapsed into one signing assumption.","sourceIds":["coinbase-api-key-authentication"],"risk":"low"},{"id":"c6","text":"These sources do not prove private account eligibility, regional access, correct key permissions, support recovery, order execution quality or future API behavior.","sourceIds":["okx-rest-authentication","kraken-rest-authentication","coinbase-api-key-authentication"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-coinbase-websocket-auth-ed25519-jwt-session-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-09T23:58:00.000Z","updatedAt":"2026-10-09T23:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs Coinbase WebSocket Authentication: Ed25519 Sessions and JWT Controls","zh-Hans":"Binance 与 Coinbase WebSocket 认证对比：Ed25519 Session 与 JWT 控制"},"summary":{"en":"Binance and Coinbase both support programmatic trading workflows, but their WebSocket authentication controls should not be treated as interchangeable.","zh-Hans":"Binance 与 Coinbase WebSocket 认证对比：Ed25519 Session 与 JWT 控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance's developer introduction says private endpoints may require HMAC signing, RSA or Ed25519 asymmetric keys and selected session-based authentication workflows.","sourceIds":["binance-introduction"],"risk":"medium"},{"id":"c2","text":"Binance's Spot WebSocket user data stream page says the subscribe method requires an authenticated WebSocket connection using Ed25519 keys.","sourceIds":["binance-user-data-stream"],"risk":"medium"},{"id":"c3","text":"Coinbase Advanced Trade documentation says Advanced Trade supports REST API and WebSocket protocol workflows for programmatic trading and market data.","sourceIds":["coinbase-ws-overview"],"risk":"medium"},{"id":"c4","text":"Coinbase's Create Portfolio reference describes authorization through a JWT signed using a CDP API Key Secret and passed as a bearer token.","sourceIds":["coinbase-portfolio-auth"],"risk":"medium"},{"id":"c5","text":"Coinbase Advanced Trade documentation and API references describe permissioned endpoint access through Coinbase App API credentials and bearer authorization rather than Binance-style Ed25519 WebSocket session logon.","sourceIds":["coinbase-ws-overview","coinbase-portfolio-auth"],"risk":"low"},{"id":"c6","text":"These sources do not prove that a private bot has correct permissions, regional access, stable reconnect behavior or a safe production order lifecycle.","sourceIds":["binance-introduction","binance-user-data-stream","coinbase-ws-overview","coinbase-portfolio-auth"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-api-authentication-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-09T23:58:00.000Z","updatedAt":"2026-10-09T23:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange API Authentication Disclosure Radar: Key Type, Permission and Session Controls","zh-Hans":"加密交易所 API 认证披露雷达：Key Type、Permission 与 Session Controls"},"summary":{"en":"The radar finding is that API authentication disclosure is fragmented across key type, signing method, permission scope, WebSocket session state and venue-specific support pages.","zh-Hans":"加密交易所 API 认证披露雷达：Key Type、Permission 与 Session Controls：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance's developer documentation says private endpoints can use HMAC signing, RSA or Ed25519 asymmetric keys and selected session-based authentication workflows.","sourceIds":["binance-introduction"],"risk":"medium"},{"id":"c2","text":"Coinbase's Advanced Trade API reference describes JWT bearer-token authorization for a permissioned portfolio endpoint.","sourceIds":["coinbase-portfolio-auth"],"risk":"medium"},{"id":"c3","text":"Kraken's WebSocket FAQ says public market data feeds do not require authentication, while private feeds require a valid authentication token.","sourceIds":["kraken-ws-faq"],"risk":"medium"},{"id":"c4","text":"Bybit's V5 integration guidance documents request construction, authentication context and operational integration guidance for API users.","sourceIds":["bybit-v5-guide"],"risk":"medium"},{"id":"c5","text":"The radar does not prove which exchange is safer; it only maps which authentication controls are publicly documented and testable.","sourceIds":["binance-introduction","coinbase-portfolio-auth","kraken-ws-faq","bybit-v5-guide"],"risk":"low"},{"id":"c6","text":"A private API integration still needs account-level verification, permission minimization, secret storage, clock handling, IP policy and incident response.","sourceIds":["binance-introduction","coinbase-portfolio-auth","kraken-ws-faq","bybit-v5-guide"],"risk":"low"}],"relatedVenues":["binance","coinbase","kraken","bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-create-bitmex-account-verify-identity-withdrawal-address-controls","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-09T23:58:00.000Z","updatedAt":"2026-10-09T23:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"How to Create a BitMEX Account, Verify Identity and Review Withdrawal Address Controls","zh-Hans":"如何创建 BitMEX 账户、完成身份验证并核验提现地址控制"},"summary":{"en":"A safe BitMEX onboarding flow should treat account creation, identity verification, jurisdiction screening, credential security, withdrawal-address controls and support contact paths as one sequence.","zh-Hans":"如何创建 BitMEX 账户、完成身份验证并核验提现地址控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"BitMEX compliance materials describe identity and account verification expectations for customers, including additional documentation for corporate customers.","sourceIds":["bitmex-compliance"],"risk":"medium"},{"id":"c2","text":"BitMEX restricted-jurisdiction materials describe access restrictions and the need to complete KYC where applicable for account access or withdrawal requests.","sourceIds":["bitmex-restricted-jurisdiction"],"risk":"medium"},{"id":"c3","text":"BitMEX terms of service address account credentials, registered withdrawal addresses and scenarios involving security compromise of credentials or addresses.","sourceIds":["bitmex-terms"],"risk":"medium"},{"id":"c4","text":"BitMEX contact materials direct users to logged-in support channels and describe withdrawal access in connection with refreshing or completing identity verification.","sourceIds":["bitmex-contact"],"risk":"medium"},{"id":"c5","text":"The accessible BitMEX sources support eligibility, verification and withdrawal-address control checks, but not a guaranteed support outcome or trading suitability.","sourceIds":["bitmex-compliance","bitmex-restricted-jurisdiction","bitmex-terms","bitmex-contact"],"risk":"low"},{"id":"c6","text":"These sources do not prove account eligibility, derivative risk tolerance, tax treatment, future fee level or support resolution for a private user.","sourceIds":["bitmex-compliance","bitmex-restricted-jurisdiction","bitmex-terms","bitmex-contact"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"jpmorgan-kinexys-tokenized-deposit-money-market-settlement-risk-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-09T23:58:00.000Z","updatedAt":"2026-10-09T23:58:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"J.P. Morgan Kinexys Tokenized Deposits and Money Market Fund Settlement Risk Map","zh-Hans":"J.P. Morgan Kinexys 代币化存款与货币基金结算风险地图"},"summary":{"en":"J.P. Morgan's Kinexys materials describe bank-led blockchain infrastructure for programmable money movement, deposit-ledger payments, tokenized collateral and tokenized money market funds.","zh-Hans":"J.P. Morgan Kinexys 代币化存款与货币基金结算风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"J.P. Morgan's Kinexys page describes blockchain solutions for programmable money movement, near-real-time settlement and asset tokenization.","sourceIds":["jpm-kinexys-home"],"risk":"medium"},{"id":"c2","text":"The J.P. Morgan Payments developer article describes Kinexys Digital Payments as a private, permissioned blockchain-based deposit ledger and payment rail using Blockchain Deposit Accounts.","sourceIds":["jpm-kinexys-payments-blog"],"risk":"medium"},{"id":"c3","text":"J.P. Morgan Asset Management announced MONY as its first tokenized money market fund, powered by Kinexys Digital Assets and available on public Ethereum for qualified investors.","sourceIds":["jpm-mony-launch"],"risk":"medium"},{"id":"c4","text":"JPMorganChase's digital-assets framework article describes JPM Coin as a deposit token for institutional clients and discusses tokenized forms of money in payments.","sourceIds":["jpm-digital-assets-framework"],"risk":"medium"},{"id":"c5","text":"These sources do not prove every user can access Kinexys, that a public-chain token grants retail rights, or that settlement remains near-real-time during every incident.","sourceIds":["jpm-kinexys-home","jpm-kinexys-payments-blog","jpm-mony-launch"],"risk":"low"},{"id":"c6","text":"A tokenized money market fund claim must still separate fund eligibility, issuer terms, blockchain record, investor record and redemption process.","sourceIds":["jpm-mony-launch","jpm-kinexys-home"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-cftc-spot-crypto-registered-exchange-venue-choice-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-09T23:58:00.000Z","updatedAt":"2026-10-09T23:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"SEC and CFTC Spot Crypto Registered Exchange Venue Choice Risk Map","zh-Hans":"SEC 与 CFTC 现货加密资产注册交易所场所选择风险地图"},"summary":{"en":"The SEC and CFTC staff statement on spot crypto trading should be read as a venue-choice and regulatory-engagement signal, not as a blanket approval for every token, exchange or account.","zh-Hans":"SEC 与 CFTC 现货加密资产注册交易所场所选择风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"The SEC and CFTC staff statement says staff are coordinating efforts to facilitate trading of certain spot crypto asset products on registered exchanges.","sourceIds":["sec-cftc-spot-statement"],"risk":"medium"},{"id":"c2","text":"The SEC and CFTC staff statement says SEC- and CFTC-registered exchanges are not prohibited from facilitating trading of certain spot commodity products.","sourceIds":["sec-cftc-spot-statement"],"risk":"medium"},{"id":"c3","text":"The SEC/CFTC chair statement discusses harmonization, innovation exemptions and possible safe harbors for spot, leveraged, margined and DeFi activity.","sourceIds":["sec-cftc-chair-statement"],"risk":"medium"},{"id":"c4","text":"The 2026 SEC/CFTC MOU says the agencies entered a memorandum to guide coordination and collaboration while supporting innovation, market integrity and customer protection.","sourceIds":["sec-cftc-mou"],"risk":"medium"},{"id":"c5","text":"The SEC 2026 crypto-assets interpretation is a separate source on federal securities-law application and does not approve a private venue or token by itself.","sourceIds":["sec-crypto-laws-interpretation"],"risk":"low"},{"id":"c6","text":"These sources do not prove a platform is approved, a specific token is non-security, or a user account can trade without jurisdictional, custody, tax or eligibility restrictions.","sourceIds":["sec-cftc-spot-statement","sec-cftc-chair-statement","sec-cftc-mou","sec-crypto-laws-interpretation"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-api-binary-protocol-json-fallback-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-09T20:58:00.000Z","updatedAt":"2026-10-09T20:58:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto API Binary Protocol and JSON Fallback Disclosure Radar","zh-Hans":"加密交易 API 二进制协议与 JSON 回退披露雷达"},"summary":{"en":"The NexuAlpha radar signal is that exchanges are separating high-performance binary or FIX channels from JSON and REST fallback paths, and disclosure quality now matters as much as raw latency.","zh-Hans":"加密交易 API 二进制协议与 JSON 回退披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"OKX's API changelog describes SBE services alongside existing REST and JSON WebSocket APIs.","sourceIds":["okx-api-changelog"],"risk":"medium"},{"id":"c2","text":"Binance's spot API documentation changelog includes FIX order-entry and FIX drop-copy changes.","sourceIds":["binance-spot-api-changelog"],"risk":"medium"},{"id":"c3","text":"Coinbase's Advanced Trade WebSocket documentation describes WebSocket market-data behavior and channel usage.","sourceIds":["coinbase-ws-overview"],"risk":"medium"},{"id":"c4","text":"Bybit's V5 integration guidance documents request timing, authentication and integration constraints for API users.","sourceIds":["bybit-v5-guide"],"risk":"medium"},{"id":"c5","text":"Across these sources, protocol choice affects parsing, authentication, sequencing, reconnect and fallback evidence.","sourceIds":["okx-api-changelog","binance-spot-api-changelog","coinbase-ws-overview","bybit-v5-guide"],"risk":"low"},{"id":"c6","text":"These sources do not prove that a private trading system reconciles all fills, handles every disconnect, or is protected against future schema and policy changes.","sourceIds":["okx-api-changelog","binance-spot-api-changelog","coinbase-ws-overview","bybit-v5-guide"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-use-1inch-fusion-plus-cross-chain-swap-api-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-09T20:58:00.000Z","updatedAt":"2026-10-09T20:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"How to Use 1inch Fusion Plus Cross Chain Swap API Safely","zh-Hans":"如何安全使用 1inch Fusion+ 跨链 Swap API"},"summary":{"en":"A safe 1inch Fusion+ onboarding flow starts with official documentation and test-size intent evidence, not with a wallet signature or production API key.","zh-Hans":"如何安全使用 1inch Fusion+ 跨链 Swap API：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"1inch documentation describes Swap API execution modes, including Fusion mode and intent-based flows.","sourceIds":["oneinch-swap-api-intro"],"risk":"medium"},{"id":"c2","text":"1inch Fusion+ documentation describes cross-chain swap functionality and its architecture for gasless cross-chain swaps.","sourceIds":["oneinch-fusion-plus-intro"],"risk":"medium"},{"id":"c3","text":"1inch SDK documentation lists official SDKs for swap and cross-chain integration workflows.","sourceIds":["oneinch-sdk-overview"],"risk":"medium"},{"id":"c4","text":"1inch's rebranding FAQ directs users to official 1inch URLs and verified access paths.","sourceIds":["oneinch-rebranding-faq"],"risk":"medium"},{"id":"c5","text":"A safe onboarding record needs official domain, application or API-key source, route, token, chain, quote, signing boundary and stop condition.","sourceIds":["oneinch-swap-api-intro","oneinch-fusion-plus-intro","oneinch-sdk-overview","oneinch-rebranding-faq"],"risk":"low"},{"id":"c6","text":"These sources do not prove a particular route is profitable, that every token is safe, that every resolver will fill an order, or that users can recover funds after signing an unsafe transaction.","sourceIds":["oneinch-swap-api-intro","oneinch-fusion-plus-intro","oneinch-sdk-overview","oneinch-rebranding-faq"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-sbe-order-entry-private-data-api-migration-readiness","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-09T20:58:00.000Z","updatedAt":"2026-10-09T20:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"OKX SBE Order Entry and Private Data API Migration Readiness Checklist","zh-Hans":"OKX SBE 下单与私有数据 API 迁移准备清单"},"summary":{"en":"OKX's SBE order entry and private-data rollout should be treated as an integration migration, not a simple endpoint swap.","zh-Hans":"OKX SBE 下单与私有数据 API 迁移准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"OKX's API changelog describes new SBE order-entry and private-data WebSocket services with demo and production timing targets.","sourceIds":["okx-api-changelog"],"risk":"medium"},{"id":"c2","text":"OKX's changelog says existing REST and JSON WebSocket APIs remain unaffected by the new SBE services.","sourceIds":["okx-api-changelog"],"risk":"medium"},{"id":"c3","text":"OKX's API guide describes REST and WebSocket API usage, authentication and trading endpoint context.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c4","text":"OKX's checksum deprecation notice directs JSON WebSocket order-book users to seqId and prevSeqId validation after checksum deprecation.","sourceIds":["okx-checksum-deprecation"],"risk":"medium"},{"id":"c5","text":"OKX's API announcements page lists API-related notices as the official announcement surface for developers.","sourceIds":["okx-api-announcements"],"risk":"low"},{"id":"c6","text":"These sources do not prove a private integration has migrated safely, that production timing will not change, or that every account and region can use the same SBE service path.","sourceIds":["okx-api-changelog","okx-api-guide","okx-checksum-deprecation","okx-api-announcements"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-october-2026-crypto-custody-proposal-adviser-fund-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-09T20:58:00.000Z","updatedAt":"2026-10-09T20:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"SEC October 2026 Crypto Custody Proposal Adviser and Fund Risk Map","zh-Hans":"SEC 2026 年 10 月加密资产托管提案顾问与基金风险地图"},"summary":{"en":"The SEC's October 2026 crypto custody proposal is a regulatory process signal, not an immediate operating permission for every adviser, fund or custodian.","zh-Hans":"SEC 2026 年 10 月加密资产托管提案顾问与基金风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"The SEC press release says the Commission proposed rules and amendments for how registered investment advisers and regulated funds can custody crypto assets.","sourceIds":["sec-press-2026-100"],"risk":"medium"},{"id":"c2","text":"The SEC rule page identifies File No. S7-2026-35 and lists Dec. 7, 2026 as the public comment due date.","sourceIds":["sec-rule-s7-2026-35"],"risk":"medium"},{"id":"c3","text":"The SEC Chair's statement frames the proposal as part of a broader crypto asset regulatory approach.","sourceIds":["sec-atkins-statement"],"risk":"medium"},{"id":"c4","text":"The SEC proposed release describes proposed custody, recordkeeping, Form ADV and Form N-CEN amendments.","sourceIds":["sec-proposed-release"],"risk":"medium"},{"id":"c5","text":"The SEC materials distinguish a proposal and comment process from an already-effective final rule.","sourceIds":["sec-press-2026-100","sec-rule-s7-2026-35","sec-proposed-release"],"risk":"low"},{"id":"c6","text":"These sources do not prove that any private adviser, fund, custodian or wallet arrangement currently satisfies final legal obligations.","sourceIds":["sec-press-2026-100","sec-rule-s7-2026-35","sec-atkins-statement","sec-proposed-release"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"swift-ubs-chainlink-tokenized-fund-redemption-settlement-risk-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-09T20:58:00.000Z","updatedAt":"2026-10-09T20:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Swift UBS Chainlink Tokenized Fund Redemption Settlement Risk Map","zh-Hans":"Swift、UBS 与 Chainlink 代币化基金申赎结算风险地图"},"summary":{"en":"The Swift, UBS and Chainlink tokenized-fund work should be read as workflow evidence, not a blanket claim that every fund token can redeem through public-chain rails.","zh-Hans":"Swift、UBS 与 Chainlink 代币化基金申赎结算风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Swift reported a pilot with UBS Asset Management and Chainlink for settling tokenized fund subscriptions and redemptions using existing Swift infrastructure.","sourceIds":["swift-ubs-chainlink-pilot"],"risk":"medium"},{"id":"c2","text":"Chainlink describes Digital Transfer Agent workflows that connect Swift messages to tokenized fund subscription and redemption processes.","sourceIds":["chainlink-swift-partnership"],"risk":"medium"},{"id":"c3","text":"UBS describes UBS Tokenize as its tokenization capability and lists tokenized fund workflow milestones.","sourceIds":["ubs-tokenize"],"risk":"medium"},{"id":"c4","text":"Chainlink's asset-management materials describe tokenized fund workflows and subscription or redemption processes using Swift and Chainlink infrastructure.","sourceIds":["chainlink-asset-management"],"risk":"medium"},{"id":"c5","text":"The sources distinguish workflow, messaging and settlement process evidence from a universal promise that every fund token is redeemable by every holder.","sourceIds":["swift-ubs-chainlink-pilot","chainlink-swift-partnership","ubs-tokenize","chainlink-asset-management"],"risk":"low"},{"id":"c6","text":"These sources do not prove private fund eligibility, secondary-market liquidity, tax treatment, investor suitability, operational exception handling or future production scope.","sourceIds":["swift-ubs-chainlink-pilot","chainlink-swift-partnership","ubs-tokenize","chainlink-asset-management"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-v5-api-timestamp-recv-window-rate-limit-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-09T17:58:00.000Z","updatedAt":"2026-10-09T17:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit V5 API Timestamp Recv-Window and Rate-Limit Checklist","zh-Hans":"Bybit V5 API timestamp、recv-window 与 rate-limit 控制清单"},"summary":{"en":"Bybit V5 API integration should be treated as a timestamp, replay-window and throttling control problem before any trading feature is enabled.","zh-Hans":"Bybit V5 API timestamp、recv-window 与 rate-limit 控制清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit V5 documentation lists API authentication headers including X-BAPI-API-KEY, X-BAPI-TIMESTAMP, X-BAPI-SIGN and X-BAPI-RECV-WINDOW.","sourceIds":["bybit-v5-guide"],"risk":"medium"},{"id":"c2","text":"Bybit V5 documentation defines a timestamp rule around server time and recv-window.","sourceIds":["bybit-v5-guide"],"risk":"medium"},{"id":"c3","text":"Bybit V5 documentation says the request string differs for GET and POST requests before signing.","sourceIds":["bybit-v5-guide"],"risk":"medium"},{"id":"c4","text":"Bybit V5 rate-limit documentation describes IP limits, WebSocket connection limits and per-UID API limits.","sourceIds":["bybit-v5-rate-limit"],"risk":"medium"},{"id":"c5","text":"Bybit V5 error-code documentation includes request-window, signature, permission, rate-limit and unmatched-IP errors.","sourceIds":["bybit-v5-error"],"risk":"low"},{"id":"c6","text":"Public API documentation cannot prove that a private key is safely stored, that an account is regionally eligible, or that future endpoint behavior will remain unchanged.","sourceIds":["bybit-v5-guide","bybit-v5-rate-limit","bybit-v5-error","bybit-v5-announcement"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"circle-cctp-v2-fast-transfer-finality-usdc-risk-map","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-09T17:58:00.000Z","updatedAt":"2026-10-09T17:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Circle CCTP V2 Fast Transfer Finality and USDC Risk Map","zh-Hans":"Circle CCTP V2 Fast Transfer finality 与 USDC 风险地图"},"summary":{"en":"Circle CCTP V2 should be read as a native USDC transfer mechanism with finality and issuer-term boundaries, not as a generic bridge promise.","zh-Hans":"Circle CCTP V2 Fast Transfer finality 与 USDC 风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Circle describes CCTP as a protocol for moving USDC across supported blockchains using native burn and mint flows.","sourceIds":["circle-cctp-page","circle-cctp-v2-blog"],"risk":"medium"},{"id":"c2","text":"Circle's CCTP V2 materials describe Fast Transfer as reducing transfer time from minutes to seconds for supported routes.","sourceIds":["circle-cctp-v2-blog","circle-cctp-v2-press"],"risk":"medium"},{"id":"c3","text":"Circle's CCTP V2 materials describe Standard Transfer as settling according to a blockchain's standard finality time.","sourceIds":["circle-cctp-v2-blog","circle-cctp-v2-press"],"risk":"medium"},{"id":"c4","text":"Circle's CCTP V2 materials describe Hooks as enabling automated post-transfer actions on the destination blockchain.","sourceIds":["circle-cctp-v2-blog","circle-cctp-v2-press"],"risk":"medium"},{"id":"c5","text":"Circle's USDC Terms distinguish supported blockchains, redemption eligibility, copies, wrappers, forks and third-party-platform risks.","sourceIds":["circle-usdc-terms"],"risk":"low"},{"id":"c6","text":"These sources do not prove that every app route is official, that every wallet display represents issuer-native USDC, or that future chain support and redemption terms will remain unchanged.","sourceIds":["circle-cctp-page","circle-cctp-v2-blog","circle-cctp-v2-press","circle-usdc-terms"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-advanced-trade-websocket-vs-bybit-v5-api-replay-freshness-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-09T17:58:00.000Z","updatedAt":"2026-10-09T17:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Advanced Trade WebSocket vs Bybit V5 API Replay and Freshness Controls","zh-Hans":"Coinbase Advanced Trade WebSocket 与 Bybit V5 API 重放和新鲜度控制对比"},"summary":{"en":"Coinbase Advanced Trade WebSocket and Bybit V5 API solve different freshness problems, so they should not be compared as generic exchange API labels.","zh-Hans":"Coinbase Advanced Trade WebSocket 与 Bybit V5 API 重放和新鲜度控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase documents separate Advanced Trade WebSocket endpoints for market data and user order data.","sourceIds":["coinbase-ws-overview"],"risk":"medium"},{"id":"c2","text":"Coinbase documentation says WebSocket subscribe messages that use CDP keys include a JWT and that JWTs expire after a short period.","sourceIds":["coinbase-ws-overview","coinbase-api-key-auth"],"risk":"medium"},{"id":"c3","text":"Coinbase documentation describes sequence numbers and warns that sequence gaps can indicate dropped messages or out-of-order delivery.","sourceIds":["coinbase-ws-overview"],"risk":"medium"},{"id":"c4","text":"Bybit V5 documentation describes authenticated request headers including API key, timestamp, signature and recv-window.","sourceIds":["bybit-v5-guide"],"risk":"medium"},{"id":"c5","text":"Bybit V5 documentation says recv-window is used to specify how long an HTTP request is valid and helps prevent replay attacks.","sourceIds":["bybit-v5-guide"],"risk":"low"},{"id":"c6","text":"Bybit rate-limit documentation describes IP, WebSocket and UID-based API rate-limit controls and response headers for limit status.","sourceIds":["bybit-v5-rate-limit"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-withdrawal-delay-trusted-contact-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-09T17:58:00.000Z","updatedAt":"2026-10-09T17:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Withdrawal Delay and Trusted Contact Disclosure Radar","zh-Hans":"加密账户提现延迟与 trusted contact 披露雷达"},"summary":{"en":"The NexuAlpha radar signal is that withdrawal-protection pages should disclose the delay, approver, threshold and cancellation path as first-class controls.","zh-Hans":"加密账户提现延迟与 trusted contact 披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Help says transfer protection can add a time delay, verification requirement, or both to outbound transactions.","sourceIds":["coinbase-transfer-protection"],"risk":"medium"},{"id":"c2","text":"Coinbase Help says transfer protection can use trusted contacts, passkey, security key, authenticator app or push notification verification methods.","sourceIds":["coinbase-transfer-protection"],"risk":"medium"},{"id":"c3","text":"Coinbase Help says transfer protection status can show pending approvals or delayed state and that transactions can be cancelled before completion.","sourceIds":["coinbase-transfer-protection"],"risk":"medium"},{"id":"c4","text":"Coinbase Help says vault withdrawals require approvals from linked email addresses followed by a 48-hour waiting period.","sourceIds":["coinbase-vault-pending"],"risk":"medium"},{"id":"c5","text":"Coinbase Help says vault setup uses co-signers and that the master account holder requests withdrawal while approvals are still required.","sourceIds":["coinbase-vault-setup"],"risk":"low"},{"id":"c6","text":"These sources do not prove that every account has the feature, that every recovery path will succeed, or that a private user should expose email, identity or balance evidence.","sourceIds":["coinbase-transfer-protection","coinbase-vault-pending","coinbase-account-security","coinbase-vault-setup"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-coinbase-vault-withdrawal-delay-and-cosigner-controls","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-09T17:58:00.000Z","updatedAt":"2026-10-09T17:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up Coinbase Vault Withdrawal Delay and Co-Signer Controls","zh-Hans":"如何设置 Coinbase Vault 提现延迟与共同批准控制"},"summary":{"en":"A Coinbase Vault setup should be treated as a controlled withdrawal-governance workflow, not as a storage slogan.","zh-Hans":"如何设置 Coinbase Vault 提现延迟与共同批准控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Help describes a vault as a separate account that stores crypto more securely.","sourceIds":["coinbase-vault-setup"],"risk":"medium"},{"id":"c2","text":"Coinbase Help says vault setup includes choosing a crypto asset, creating a vault, choosing co-signers and inviting co-signer email addresses.","sourceIds":["coinbase-vault-setup"],"risk":"medium"},{"id":"c3","text":"Coinbase Help says only the master account holder can request a withdrawal but approvals are required.","sourceIds":["coinbase-vault-setup"],"risk":"medium"},{"id":"c4","text":"Coinbase Help says vault withdrawals require approval from linked email addresses followed by a 48-hour waiting period.","sourceIds":["coinbase-vault-pending"],"risk":"medium"},{"id":"c5","text":"Coinbase Help says transfer protection and account-security controls can add further outbound-transfer protections.","sourceIds":["coinbase-transfer-protection","coinbase-account-security"],"risk":"low"},{"id":"c6","text":"These sources do not prove that a private account is eligible, that co-signers will receive email, that support can restore lost access, or that deposits should be made before a test withdrawal plan exists.","sourceIds":["coinbase-vault-setup","coinbase-vault-pending","coinbase-transfer-protection","coinbase-account-security"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-annual-economic-report-stablecoin-tokenisation-fragmentation-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-09T11:58:00.000Z","updatedAt":"2026-10-09T11:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Annual Economic Report Stablecoin Tokenisation Fragmentation Map","zh-Hans":"BIS 年度经济报告稳定币与代币化碎片化地图"},"summary":{"en":"The BIS 2026 policy signal is that stablecoins and tokenisation should be judged against trust, singleness, elasticity, integrity and interoperability, not against speed alone.","zh-Hans":"BIS 年度经济报告稳定币与代币化碎片化地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"The BIS Annual Economic Report 2026 discusses stablecoins, tokenisation, network fragmentation and tokenised commercial bank deposits within the monetary architecture.","sourceIds":["bis-annual-2026"],"risk":"medium"},{"id":"c2","text":"BIS remarks on anchoring trust in money describe stablecoins as having weaknesses including deviations from par, fragmentation and financial-integrity risks.","sourceIds":["bis-anchoring-trust"],"risk":"medium"},{"id":"c3","text":"BIS Project Agorá says its prototype uses tokenised commercial bank deposits and tokenised central bank reserves for wholesale cross-border payment testing.","sourceIds":["bis-project-agora"],"risk":"medium"},{"id":"c4","text":"BIS remarks on stablecoins and tokenised deposits compare digital money arrangements against desirable properties of money.","sourceIds":["bis-stablecoin-tokenised-deposits"],"risk":"medium"},{"id":"c5","text":"BIS materials distinguish policy and prototype evidence from retail product guarantees or account-specific permissions.","sourceIds":["bis-annual-2026","bis-project-agora","bis-stablecoin-tokenised-deposits"],"risk":"low"},{"id":"c6","text":"These sources do not prove that a private stablecoin product is safe, that a tokenised-deposit system is generally available, or that any jurisdiction has adopted a single binding rule for all users.","sourceIds":["bis-annual-2026","bis-anchoring-trust","bis-project-agora","bis-stablecoin-tokenised-deposits"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"chainlink-data-streams-vs-pyth-price-feeds-update-freshness-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-09T11:58:00.000Z","updatedAt":"2026-10-09T11:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Chainlink Data Streams vs Pyth Price Feeds Update Freshness Controls","zh-Hans":"Chainlink Data Streams 与 Pyth Price Feeds 更新新鲜度控制对比"},"summary":{"en":"Chainlink Data Streams and Pyth Price Feeds should be compared as data-delivery and freshness-control systems, not as generic oracle labels.","zh-Hans":"Chainlink Data Streams 与 Pyth Price Feeds 更新新鲜度控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Chainlink documentation describes Data Streams as a low-latency data product using offchain reporting and onchain verification patterns.","sourceIds":["chainlink-data-streams"],"risk":"medium"},{"id":"c2","text":"Chainlink documentation describes Data Feeds as onchain reference data for smart contracts and applications.","sourceIds":["chainlink-data-feeds"],"risk":"medium"},{"id":"c3","text":"Pyth documentation describes Price Feeds as publishing price data with price, confidence and publish-time information.","sourceIds":["pyth-price-feeds"],"risk":"medium"},{"id":"c4","text":"Pyth best-practice documentation recommends checking confidence and staleness before using a price value.","sourceIds":["pyth-best-practices"],"risk":"medium"},{"id":"c5","text":"Both documentation sets make the consuming application responsible for handling feed meaning, update assumptions and failure behavior.","sourceIds":["chainlink-data-streams","chainlink-data-feeds","pyth-price-feeds","pyth-best-practices"],"risk":"low"},{"id":"c6","text":"These sources do not prove that a private integration handles stale data safely, that future feed methodology will be unchanged, or that a liquidation or execution path is suitable for every market.","sourceIds":["chainlink-data-streams","chainlink-data-feeds","pyth-price-feeds","pyth-best-practices"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-tokenized-collateral-interoperability-programmability-risk-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-09T11:58:00.000Z","updatedAt":"2026-10-09T11:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Tokenized Collateral Interoperability and Programmability Risk Map","zh-Hans":"DTCC 代币化抵押品互操作性与可编程性风险地图"},"summary":{"en":"DTCC's 2026 tokenization materials point to a shift from isolated token displays toward interoperable collateral infrastructure.","zh-Hans":"DTCC 代币化抵押品互操作性与可编程性风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"DTCC says tokenization is moving from experimentation to implementation and identifies interoperability as a critical enabler for institutional adoption.","sourceIds":["dtcc-interoperability-2026"],"risk":"medium"},{"id":"c2","text":"DTCC says tokenization can connect assets, cash and data across traditional and emerging financial infrastructure.","sourceIds":["dtcc-interoperability-2026"],"risk":"medium"},{"id":"c3","text":"DTCC describes live production transactions using tokenized DTC-custodied assets across several use cases.","sourceIds":["dtcc-live-production-trades"],"risk":"medium"},{"id":"c4","text":"DTCC describes its Tokenization Service as bridging traditional and blockchain-based environments for asset mobility and institutional participation.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c5","text":"DTCC's 2026 collateral materials discuss Collateral AppChain and tokenized collateral mobility as a capital-markets infrastructure direction.","sourceIds":["dtcc-tokenized-collateral-release"],"risk":"low"},{"id":"c6","text":"These sources do not prove that every asset is eligible, that every network is approved, that collateral can always move instantly, or that private legal, tax and operational requirements are satisfied.","sourceIds":["dtcc-interoperability-2026","dtcc-live-production-trades","dtcc-tokenization-service","dtcc-tokenized-collateral-release"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-rest-authentication-nonce-signature-replay-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-09T11:58:00.000Z","updatedAt":"2026-10-09T11:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken REST Authentication Nonce and Signature Replay Checklist","zh-Hans":"Kraken REST 认证 nonce 与签名重放控制清单"},"summary":{"en":"Kraken REST authentication is an implementation checklist, not just an API-key possession check. Kraken's exchange API documentation describes REST authentication with API-Key, API-Sign and a nonce, while Kraken Support.","zh-Hans":"Kraken REST 认证 nonce 与签名重放控制清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Kraken exchange API documentation describes private REST authentication using API-Key, API-Sign and a nonce.","sourceIds":["kraken-rest-auth"],"risk":"medium"},{"id":"c2","text":"Kraken exchange API documentation describes API-Sign construction with the request path, SHA256 nonce and POST data, and HMAC-SHA512 using the decoded API secret.","sourceIds":["kraken-rest-auth"],"risk":"medium"},{"id":"c3","text":"Kraken Support publishes API-key creation guidance that includes permission selection.","sourceIds":["kraken-create-api-key"],"risk":"medium"},{"id":"c4","text":"Kraken Support publishes general API context for account integrations and automation.","sourceIds":["kraken-api-overview"],"risk":"medium"},{"id":"c5","text":"Kraken Support publishes account-security guidance covering device, email and account protections.","sourceIds":["kraken-account-security"],"risk":"low"},{"id":"c6","text":"Public documentation cannot prove that a private bot protects secrets, handles nonce reuse correctly, is eligible for all endpoints, or will continue working after future policy changes.","sourceIds":["kraken-rest-auth","kraken-create-api-key","kraken-api-overview","kraken-account-security"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"stablecoin-multichain-native-issuance-disclosure-radar","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-09T11:58:00.000Z","updatedAt":"2026-10-09T11:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Stablecoin Multichain Native Issuance Disclosure Radar","zh-Hans":"稳定币多链原生发行披露雷达"},"summary":{"en":"The NexuAlpha radar signal is that multichain stablecoin pages need to disclose more than a ticker and a contract address.","zh-Hans":"稳定币多链原生发行披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Circle Developers describes CCTP as a protocol for transferring USDC across supported blockchains using native burn and mint flows.","sourceIds":["circle-cctp"],"risk":"medium"},{"id":"c2","text":"Circle's USDC Terms define legal and operational boundaries for USDC, including issuer and redemption-related terms.","sourceIds":["circle-usdc-terms"],"risk":"medium"},{"id":"c3","text":"BIS stablecoin remarks describe that the same stablecoin token on different chains is not inherently interoperable across networks.","sourceIds":["bis-stablecoins-framing"],"risk":"medium"},{"id":"c4","text":"The BIS Annual Economic Report 2026 discusses fragmentation across public permissionless networks and tokenised money architectures.","sourceIds":["bis-annual-2026"],"risk":"medium"},{"id":"c5","text":"A multichain stablecoin disclosure needs to distinguish native issuance, bridged assets, supported chains, contract identity and redemption route.","sourceIds":["circle-cctp","circle-usdc-terms","bis-stablecoins-framing","bis-annual-2026"],"risk":"low"},{"id":"c6","text":"These sources do not prove that every wallet display is official, that every bridge asset is equivalent to issuer-native stablecoin, or that future chain support and redemption terms will remain unchanged.","sourceIds":["circle-cctp","circle-usdc-terms","bis-stablecoins-framing","bis-annual-2026"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"franklin-benji-transfer-agent-vs-chainlink-smartdata-proof-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-09T08:58:00.000Z","updatedAt":"2026-10-09T08:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Franklin BENJI Transfer Agent vs Chainlink SmartData Proof Map","zh-Hans":"Franklin BENJI Transfer Agent 与 Chainlink SmartData 证明地图"},"summary":{"en":"Franklin BENJI and Chainlink SmartData answer different tokenized-asset evidence questions. Franklin's BENJI materials and prospectus say the fund's transfer agent maintains the official record of share ownership through a.","zh-Hans":"Franklin BENJI Transfer Agent 与 Chainlink SmartData 证明地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Franklin's BENJI page says the fund's transfer agent maintains the official record of share ownership through a proprietary blockchain-integrated system.","sourceIds":["franklin-benji-overview"],"risk":"medium"},{"id":"c2","text":"Franklin's DevHub publishes BENJI-related contract addresses across multiple public blockchain networks.","sourceIds":["franklin-benji-contracts"],"risk":"medium"},{"id":"c3","text":"The Franklin prospectus says all fund and shareholder records in the blockchain-integrated recordkeeping system are under the full and complete control of the fund's transfer agent.","sourceIds":["franklin-fobxx-prospectus"],"risk":"medium"},{"id":"c4","text":"Chainlink SmartData documentation describes Proof of Reserve feeds, NAVLink feeds and SmartAUM feeds as SmartData product categories.","sourceIds":["chainlink-smartdata"],"risk":"medium"},{"id":"c5","text":"Chainlink SmartData documentation says users are responsible for reviewing feed quality before integrating feeds into smart contracts.","sourceIds":["chainlink-smartdata"],"risk":"low"},{"id":"c6","text":"These sources do not prove that a token address alone establishes legal ownership, that a feed fits every collateral use case, or that future records, reserves or NAV values will remain unchanged.","sourceIds":["franklin-benji-overview","franklin-benji-contracts","franklin-fobxx-prospectus","chainlink-smartdata"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-use-morpho-blue-wallet-collateral-and-borrow-controls-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-09T08:58:00.000Z","updatedAt":"2026-10-09T08:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"How to Use Morpho Blue: Wallet, Collateral and Borrow Controls","zh-Hans":"如何安全使用 Morpho Blue：钱包、抵押品与借款控制"},"summary":{"en":"Morpho Blue onboarding is a wallet, collateral and market-risk control flow, not a username-and-password registration flow.","zh-Hans":"如何安全使用 Morpho Blue：钱包、抵押品与借款控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Morpho documentation describes Morpho Blue as variable-rate markets with transparent lending and borrowing rules.","sourceIds":["morpho-blue-concepts"],"risk":"medium"},{"id":"c2","text":"Morpho Borrow developer documentation says users supply collateral and borrow assets directly from isolated lending markets.","sourceIds":["morpho-borrow-get-started"],"risk":"medium"},{"id":"c3","text":"Morpho LTV documentation says collateral supports borrowing up to the market's liquidation loan-to-value limit.","sourceIds":["morpho-ltv-health"],"risk":"medium"},{"id":"c4","text":"Morpho Bundles documentation says a bundle can combine approval, supplying collateral and borrowing into one transaction that reverts as a whole if a step fails.","sourceIds":["morpho-bundles"],"risk":"medium"},{"id":"c5","text":"Morpho documentation treats collateral, loan asset, market and health or LTV metrics as distinct objects for integration.","sourceIds":["morpho-borrow-get-started","morpho-ltv-health"],"risk":"low"},{"id":"c6","text":"Public Morpho documentation cannot prove private wallet safety, future liquidity, oracle behavior, gas cost, liquidation timing, tax treatment or support recovery.","sourceIds":["morpho-blue-concepts","morpho-borrow-get-started","morpho-ltv-health","morpho-bundles"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-add-withdrawal-addresses-api-permission-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-09T08:58:00.000Z","updatedAt":"2026-10-09T08:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken Add Withdrawal Addresses API Permission Checklist","zh-Hans":"Kraken Add Withdrawal Addresses API 权限控制清单"},"summary":{"en":"Kraken's Add Withdrawal Addresses API permission should be treated as a high-risk account-control surface, not as a harmless address-book convenience.","zh-Hans":"Kraken Add Withdrawal Addresses API 权限控制清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Kraken Support says the Add Withdrawal Addresses API permission allows an API key to add and remove cryptocurrency and fiat withdrawal addresses.","sourceIds":["kraken-address-api-permission"],"risk":"medium"},{"id":"c2","text":"Kraken Support warns that combining Add Withdrawal Addresses with Withdraw Funds can allow an attacker with the key to add an address and initiate a withdrawal.","sourceIds":["kraken-address-api-permission"],"risk":"medium"},{"id":"c3","text":"Kraken Support recommends separate keys, least privilege, IP whitelisting, key expiry, API-key 2FA and account-activity review as risk-reduction controls.","sourceIds":["kraken-address-api-permission","kraken-create-api-key"],"risk":"medium"},{"id":"c4","text":"Kraken Support publishes account-security guidance covering device, email and account protections.","sourceIds":["kraken-account-security"],"risk":"medium"},{"id":"c5","text":"Kraken Support publishes a general API explainer for account API access and integration context.","sourceIds":["kraken-api-overview"],"risk":"low"},{"id":"c6","text":"The public help pages do not prove a private key's current permissions, account eligibility, support outcome, incident status or future policy.","sourceIds":["kraken-address-api-permission","kraken-create-api-key","kraken-account-security","kraken-api-overview"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-api-key-creation-vs-withdrawal-address-permission-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-09T08:58:00.000Z","updatedAt":"2026-10-09T08:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken API Key Creation vs Withdrawal Address Permission Controls","zh-Hans":"Kraken API Key 创建与提现地址权限控制对比"},"summary":{"en":"Kraken API key creation and withdrawal-address permission controls solve adjacent but different API-risk problems.","zh-Hans":"Kraken API Key 创建与提现地址权限控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Kraken Support publishes a help surface for creating API keys and choosing API permissions.","sourceIds":["kraken-create-api-key"],"risk":"medium"},{"id":"c2","text":"Kraken Support says the Add Withdrawal Addresses API permission can add or remove withdrawal addresses.","sourceIds":["kraken-address-api-permission"],"risk":"medium"},{"id":"c3","text":"Kraken Support warns that combining address-management permission with withdrawal capability can allow a compromised key to add an address and initiate withdrawal activity.","sourceIds":["kraken-address-api-permission"],"risk":"medium"},{"id":"c4","text":"Kraken Support recommends separate keys, least privilege, IP whitelisting, key expiry, API-key 2FA and account-activity review as risk-reduction controls.","sourceIds":["kraken-address-api-permission","kraken-create-api-key"],"risk":"medium"},{"id":"c5","text":"Kraken Support publishes general API context for account API access and integrations.","sourceIds":["kraken-api-overview"],"risk":"low"},{"id":"c6","text":"Public API documentation cannot prove that a private bot stores keys safely, that a private account is eligible, or that future permissions remain unchanged.","sourceIds":["kraken-create-api-key","kraken-address-api-permission","kraken-account-security","kraken-api-overview"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"tokenized-asset-data-feed-quality-disclosure-radar","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-09T08:58:00.000Z","updatedAt":"2026-10-09T08:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Tokenized Asset Data Feed Quality Disclosure Radar","zh-Hans":"代币化资产数据源质量披露雷达"},"summary":{"en":"The NexuAlpha radar signal is that tokenized-asset pages increasingly depend on data-feed quality disclosures, not only on token ticker names.","zh-Hans":"代币化资产数据源质量披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Chainlink Data Feeds documentation says feeds include asset prices, proof of reserves, NAV and interest-rate data published onchain.","sourceIds":["chainlink-data-feeds"],"risk":"medium"},{"id":"c2","text":"Chainlink Selecting Data Feeds documentation says users should evaluate feed properties and risks, especially custom feeds.","sourceIds":["chainlink-selecting-feeds"],"risk":"medium"},{"id":"c3","text":"Chainlink SmartData documentation describes Proof of Reserve, NAVLink and SmartAUM feed categories.","sourceIds":["chainlink-smartdata"],"risk":"medium"},{"id":"c4","text":"DTCC says tokenization is moving into live production transactions using tokenized DTC-custodied assets.","sourceIds":["dtcc-live-tokenization"],"risk":"medium"},{"id":"c5","text":"DTCC describes its Tokenization Service as bridging traditional and blockchain-based environments for asset mobility and institutional participation.","sourceIds":["dtcc-tokenization-service"],"risk":"low"},{"id":"c6","text":"These sources do not prove that every tokenized asset has complete data disclosure, that a feed is suitable for a private protocol, or that future collateral mobility will be uninterrupted.","sourceIds":["chainlink-data-feeds","chainlink-selecting-feeds","chainlink-smartdata","dtcc-live-tokenization","dtcc-tokenization-service"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-stablecoin-remuneration-exchange-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-09T05:58:00.000Z","updatedAt":"2026-10-09T05:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Stablecoin Remuneration on Exchanges: User Risk Map","zh-Hans":"BIS 关于交易所稳定币收益化：用户风险地图"},"summary":{"en":"BIS research turns stablecoin rewards on centralized exchanges into a user-risk and macro-financial question.","zh-Hans":"BIS 研究把中心化交易所上的稳定币收益化变成了用户风险与宏观金融问题。BIS 指出，remuneration models 可能使稳定币类似银行存款或货币市场基金替代品，也可能成为交易所风险活动的融资工具；另有 BIS 研究将外币稳定币使用与新兴和发展中经济体的 dollarisation channel 联系起来。"},"claims":[{"id":"c1","text":"BIS says stablecoin remuneration models on centralized exchanges may shape the macro-financial implications of wider stablecoin adoption.","sourceIds":["bis-stablecoin-remuneration"],"risk":"medium"},{"id":"c2","text":"BIS says stablecoin remuneration may turn stablecoins into substitutes for bank deposits or money market funds, or funding instruments for exchanges' risky activities.","sourceIds":["bis-stablecoin-remuneration"],"risk":"medium"},{"id":"c3","text":"BIS dollarisation research compares foreign-currency stablecoin dynamics with conventional deposit dollarisation across more than 130 economies.","sourceIds":["bis-dollarisation"],"risk":"medium"},{"id":"c4","text":"BIS monetary-policy remarks say large-scale substitution into foreign-currency stablecoins could weaken monetary sovereignty and policy effectiveness.","sourceIds":["bis-new-money"],"risk":"medium"},{"id":"c5","text":"BIS tokenised-deposit remarks distinguish stablecoins from tokenised deposits and central-bank-money settlement trust anchors.","sourceIds":["bis-monetary-frontier"],"risk":"low"},{"id":"c6","text":"BIS sources do not prove a private exchange reward product's legal treatment, reserve claim, redemption outcome, tax treatment or future yield.","sourceIds":["bis-stablecoin-remuneration","bis-dollarisation","bis-new-money"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-onboard-gmx-wallet-account-direct-trading-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-09T05:58:00.000Z","updatedAt":"2026-10-09T05:58:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"How to Onboard GMX: Wallet, GMX Account and Direct Trading Safety Checklist","zh-Hans":"如何安全上手 GMX：钱包、GMX Account 与直接交易核验清单"},"summary":{"en":"GMX onboarding is wallet-based rather than username-and-password registration. GMX docs say users connect a wallet on the Trade page, can trade directly from supported networks where GMX markets are deployed, and can use a GMX.","zh-Hans":"如何安全上手 GMX：钱包、GMX Account 与直接交易核验清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"GMX describes itself as a decentralized exchange where users trade without a username or password.","sourceIds":["gmx-trading-overview"],"risk":"medium"},{"id":"c2","text":"GMX says users connect a wallet from the Trade page and can use WalletConnect where supported.","sourceIds":["gmx-trading-overview"],"risk":"medium"},{"id":"c3","text":"GMX says active markets are available for direct wallet trading on Arbitrum, Avalanche and MegaETH.","sourceIds":["gmx-direct-wallet"],"risk":"medium"},{"id":"c4","text":"GMX says the GMX Account lets users trade on GMX from chains that do not have GMX markets deployed, with Arbitrum as the supported settlement chain.","sourceIds":["gmx-account"],"risk":"medium"},{"id":"c5","text":"GMX distinguishes wallet funds from GMX Account funds and says deposits into GMX Account may bridge funds using cross-chain infrastructure.","sourceIds":["gmx-account"],"risk":"low"},{"id":"c6","text":"The official docs do not prove a private wallet's eligibility, bridge result, gas cost, liquidation outcome, funding rate, tax treatment or support recovery.","sourceIds":["gmx-trading-overview","gmx-account"],"risk":"low"}],"relatedVenues":["gmx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-api-address-permission-vs-okx-wallet-verification-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-09T05:58:00.000Z","updatedAt":"2026-10-09T05:58:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken API Address Permission vs OKX Wallet Verification: Withdrawal Control Map","zh-Hans":"Kraken API 地址权限与 OKX 钱包地址验证：提现控制地图"},"summary":{"en":"Kraken's Add Withdrawal Addresses API permission and OKX wallet address verification solve different withdrawal-control problems.","zh-Hans":"Kraken 的 Add Withdrawal Addresses API 权限与 OKX 的钱包地址验证解决的是不同提现控制问题。Kraken 警示，拥有地址管理权限的 API key 可以新增或删除提现地址，若再与 Withdraw Funds 权限组合，风险会显著上升。"},"claims":[{"id":"c1","text":"Kraken says the Add Withdrawal Addresses permission allows an API key to add and remove cryptocurrency and fiat withdrawal addresses.","sourceIds":["kraken-api-address-permission"],"risk":"medium"},{"id":"c2","text":"Kraken warns that combining Add Withdrawal Addresses with Withdraw Funds can allow an attacker with the key to add an address and initiate a withdrawal.","sourceIds":["kraken-api-address-permission"],"risk":"medium"},{"id":"c3","text":"Kraken recommends IP whitelisting, API key expiry, least privilege, separate keys, account-activity review and API-key 2FA to reduce risk.","sourceIds":["kraken-api-address-permission","kraken-security"],"risk":"medium"},{"id":"c4","text":"OKX says a user withdrawing crypto to a new address may be asked to complete one-time verification to confirm ownership of that address.","sourceIds":["okx-wallet-address-verify"],"risk":"medium"},{"id":"c5","text":"OKX says the verification flow distinguishes exchanges or platforms from private wallets and asks users to select the correct entity where applicable.","sourceIds":["okx-wallet-address-verify"],"risk":"low"},{"id":"c6","text":"Neither source set proves that a private withdrawal route, support case, travel-rule review or API integration will succeed in the future.","sourceIds":["kraken-api-address-permission","okx-wallet-address-verify","okx-crypto-withdrawals"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-shield-account-takeover-reimbursement-boundary-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-09T05:58:00.000Z","updatedAt":"2026-10-09T05:58:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"OKX Shield: Account Takeover Reimbursement Boundary Checklist","zh-Hans":"OKX Shield：账户接管补偿边界核验清单"},"summary":{"en":"OKX Shield should be read as an account-security incident review programme, not as insurance or a guaranteed loss-recovery product.","zh-Hans":"OKX Shield 应被理解为账户安全事件审核计划，而不是保险或保证赔付产品。OKX 称该计划属于自愿且酌情的 goodwill programme，可考虑符合条件的第三方账户接管损失，仅面向符合条件的 KYC 用户，并使用按用户层级划分的最高限额；实际可用性还取决于账户状态、服务实体和个案审核。"},"claims":[{"id":"c1","text":"OKX describes OKX Shield as a voluntary, discretionary goodwill programme that may reimburse eligible users for third-party account takeover losses.","sourceIds":["okx-shield-announcement"],"risk":"medium"},{"id":"c2","text":"OKX states that OKX Shield is not insurance, an investor compensation scheme, a deposit guarantee scheme or an unconditional promise to reimburse a loss.","sourceIds":["okx-shield-announcement","okx-shield-guide","okx-shield-faq-au"],"risk":"medium"},{"id":"c3","text":"OKX says eligible KYC users may see maximum reimbursement limits based on user tier, including regular, VIP 1-3 and VIP 4-6 bands.","sourceIds":["okx-shield-guide"],"risk":"medium"},{"id":"c4","text":"OKX says the displayed limit is not a guarantee that every loss will be reimbursed up to that amount.","sourceIds":["okx-shield-guide"],"risk":"medium"},{"id":"c5","text":"OKX FAQ says availability depends on account status, device health, supported environment, enabled security controls, user tier and the serving OKX entity.","sourceIds":["okx-shield-faq-au"],"risk":"low"},{"id":"c6","text":"The official sources do not prove that a private incident will qualify, that evidence will be complete, or that any specific reimbursement amount will be approved.","sourceIds":["okx-shield-announcement","okx-shield-guide","okx-shield-faq-au"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-dtcc-tokenized-securities-record-rights-boundary-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-09T05:58:00.000Z","updatedAt":"2026-10-09T05:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"SEC and DTCC Tokenized Securities: Record, Rights and Settlement Boundary Map","zh-Hans":"SEC 与 DTCC 代币化证券：记录、权利与结算边界地图"},"summary":{"en":"SEC tokenized-securities statements and DTCC's DTC Tokenization Service materials point to a rights-and-recordkeeping question, not a generic crypto-wrapper question.","zh-Hans":"SEC 与 DTCC 代币化证券：记录、权利与结算边界地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"SEC staff describe a tokenized security as a security represented as a crypto asset where the ownership record is maintained in whole or in part through crypto networks.","sourceIds":["sec-tokenized-securities"],"risk":"medium"},{"id":"c2","text":"SEC staff state that tokenized-securities models vary in structure and in the rights afforded to holders.","sourceIds":["sec-tokenized-securities"],"risk":"medium"},{"id":"c3","text":"SEC's Innovation Exemption statement describes temporary, conditional relief for certain Tokenized Securities Venues and tokenized NMS stock trading.","sourceIds":["sec-innovation-exemption"],"risk":"medium"},{"id":"c4","text":"The SEC statement says tokenized NMS stock under the described exemption must provide holders with the same rights and privileges as traditional securities, including dividends and voting rights.","sourceIds":["sec-innovation-exemption"],"risk":"medium"},{"id":"c5","text":"DTCC announced development timelines for DTC's tokenization service and described collaboration with more than 50 financial industry firms.","sourceIds":["dtcc-tokenization-service"],"risk":"low"},{"id":"c6","text":"These sources do not prove that every tokenized asset, broker interface, wallet record or venue gives the same rights, settlement finality or recourse.","sourceIds":["sec-tokenized-securities","sec-innovation-exemption","dtcc-tokenization-service"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-api-restrictions-permission-readback-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-09T03:08:00.000Z","updatedAt":"2026-10-09T03:08:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Binance API Restrictions Permission Readback Checklist","zh-Hans":"Binance API 权限回读与限制控制清单"},"summary":{"en":"A Binance API key should be reviewed through permission readback, timing security and IP scope, not by trusting a bot setup screen.","zh-Hans":"Binance API 权限回读与限制控制清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance REST documentation states that endpoints have security types and that signed endpoints require a signature.","sourceIds":["binance-spot-rest-general"],"risk":"medium"},{"id":"c2","text":"Binance timing security documentation describes timestamp and recvWindow validation for signed requests.","sourceIds":["binance-spot-rest-general"],"risk":"medium"},{"id":"c3","text":"Binance wallet API documentation includes a Get API Key Permission endpoint that reports permission and restriction fields.","sourceIds":["binance-api-restrictions"],"risk":"medium"},{"id":"c4","text":"Binance developer documentation includes sub-account API key IP restriction endpoints for institutional or broker contexts.","sourceIds":["binance-subaccount-ip-restriction"],"risk":"medium"},{"id":"c5","text":"A key existing in the interface does not prove that its runtime permissions match the user's intended least-privilege design.","sourceIds":["binance-api-restrictions","binance-api-key-faq"],"risk":"low"},{"id":"c6","text":"Public Binance documentation cannot prove private account eligibility, regional availability, support review, future API changes or a bot vendor's key handling.","sourceIds":["binance-spot-rest-general","binance-api-restrictions","binance-api-key-faq","binance-subaccount-ip-restriction"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-api-key-permission-scope-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-09T03:08:00.000Z","updatedAt":"2026-10-09T03:08:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange API Key Permission Scope Disclosure Radar","zh-Hans":"交易所 API Key 权限范围披露雷达"},"summary":{"en":"The NexuAlpha radar signal is that exchange API-key safety depends on visible permission scope, portfolio or account boundary, IP controls and secret-handling rules.","zh-Hans":"交易所 API Key 权限范围披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance documentation includes fields that expose API key permissions and IP restriction state.","sourceIds":["binance-api-restrictions"],"risk":"medium"},{"id":"c2","text":"Coinbase developer documentation says Advanced Trade portfolios can use dedicated CDP API keys scoped to a specific portfolio.","sourceIds":["coinbase-advanced-portfolios"],"risk":"medium"},{"id":"c3","text":"Coinbase Help describes portfolio, permission, passphrase and IP address whitelist fields in API key creation.","sourceIds":["coinbase-api-key-help"],"risk":"medium"},{"id":"c4","text":"Kraken Support publishes an API key creation help surface for account API access.","sourceIds":["kraken-create-api-key"],"risk":"medium"},{"id":"c5","text":"An API key inventory is not complete if it records only key name and exchange without permission, portfolio and network restriction fields.","sourceIds":["binance-api-restrictions","coinbase-advanced-portfolios","coinbase-api-key-help","kraken-create-api-key"],"risk":"low"},{"id":"c6","text":"Public exchange documentation cannot prove private key storage, bot-vendor custody, breach response, region-specific restrictions or future permission changes.","sourceIds":["binance-api-restrictions","coinbase-advanced-portfolios","coinbase-api-key-help","kraken-create-api-key"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fatf-travel-rule-gaps-exchange-transfer-information-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-09T03:08:00.000Z","updatedAt":"2026-10-09T03:08:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"FATF Travel Rule Gaps and Exchange Transfer Information Map","zh-Hans":"FATF Travel Rule 缺口与交易所转账信息控制图"},"summary":{"en":"FATF Travel Rule coverage should be read as a jurisdiction and VASP implementation problem, not as proof that every exchange transfer will be frictionless.","zh-Hans":"FATF Travel Rule 缺口与交易所转账信息控制图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"FATF's 2026 targeted update states that jurisdictions have continued progress on Recommendation 15, including Travel Rule implementation.","sourceIds":["fatf-2026-targeted-update"],"risk":"medium"},{"id":"c2","text":"FATF's 2026 news release reports that significant regulatory and implementation gaps remain in virtual-asset oversight.","sourceIds":["fatf-2026-news"],"risk":"medium"},{"id":"c3","text":"Crypto.com Help publishes a Travel Rule FAQ for crypto deposits and withdrawals.","sourceIds":["crypto-com-travel-rule"],"risk":"medium"},{"id":"c4","text":"FATF's virtual assets topic page describes the Travel Rule as requiring collection and transmission of originator and beneficiary information.","sourceIds":["fatf-virtual-assets-topic"],"risk":"medium"},{"id":"c5","text":"A country or exchange mentioning the Travel Rule does not prove that a specific transfer route, wallet counterparty or offshore VASP will be accepted.","sourceIds":["fatf-2026-targeted-update","crypto-com-travel-rule","fatf-virtual-assets-topic"],"risk":"low"},{"id":"c6","text":"Public policy and exchange help pages cannot prove private account eligibility, support review timing, beneficiary correctness, sanctions outcome or recovery after a mistaken transfer.","sourceIds":["fatf-2026-targeted-update","fatf-2026-news","crypto-com-travel-rule","fatf-virtual-assets-topic"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-onboard-aave-wallet-supply-borrow-health-factor-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-09T03:08:00.000Z","updatedAt":"2026-10-09T03:08:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"How to Onboard Aave: Wallet, Supply, Borrow and Health Factor Controls","zh-Hans":"如何安全使用 Aave：钱包、供应、借款与健康因子控制"},"summary":{"en":"Aave onboarding is a wallet and protocol-action checklist, not an account-registration flow. Aave help and developer documentation describe connecting a wallet, supplying tokens, toggling collateral status, borrowing with.","zh-Hans":"如何安全使用 Aave：钱包、供应、借款与健康因子控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Aave Help publishes supplying guidance for users interacting with Aave markets.","sourceIds":["aave-supplying"],"risk":"medium"},{"id":"c2","text":"Aave Help says supplied tokens can be used as collateral and describes health factor as a key indicator for liquidation risk.","sourceIds":["aave-toggle-collateral"],"risk":"medium"},{"id":"c3","text":"Aave developer documentation describes market operations and health-factor preview behavior.","sourceIds":["aave-market-operations"],"risk":"medium"},{"id":"c4","text":"Aave Pool documentation describes supply and borrow functions and collateral requirements.","sourceIds":["aave-pool"],"risk":"medium"},{"id":"c5","text":"A protocol action being documented does not prove that a user's wallet, asset, chain, allowance or health factor is safe for a specific transaction.","sourceIds":["aave-supplying","aave-toggle-collateral","aave-market-operations","aave-pool"],"risk":"low"},{"id":"c6","text":"Public Aave documentation cannot prove private wallet security, future liquidity, oracle behavior, gas cost, liquidation timing, tax treatment or support recovery.","sourceIds":["aave-supplying","aave-toggle-collateral","aave-market-operations","aave-pool"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"uniswap-v4-vs-pancakeswap-infinity-hook-control-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-09T03:08:00.000Z","updatedAt":"2026-10-09T03:08:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Uniswap v4 vs PancakeSwap Infinity Hook Control Map","zh-Hans":"Uniswap v4 与 PancakeSwap Infinity Hook 控制图对比"},"summary":{"en":"Uniswap v4 and PancakeSwap Infinity should be compared as programmable pool-control systems, not as generic DEX labels.","zh-Hans":"Uniswap v4 与 PancakeSwap Infinity Hook 控制图对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Uniswap developer documentation describes v4 hooks as contracts that can be attached to liquidity pools.","sourceIds":["uniswap-v4-hooks"],"risk":"medium"},{"id":"c2","text":"Uniswap developer guidance provides hook-building material for developers working with v4 hooks.","sourceIds":["uniswap-build-first-hook"],"risk":"medium"},{"id":"c3","text":"PancakeSwap documentation describes Infinity hooks as add-ons that can extend or customize liquidity pool behavior.","sourceIds":["pancakeswap-infinity-hooks"],"risk":"medium"},{"id":"c4","text":"PancakeSwap developer documentation publishes a custom-layer hook surface for Infinity contracts.","sourceIds":["pancakeswap-custom-layer-hook"],"risk":"medium"},{"id":"c5","text":"A hook-enabled pool being visible in a frontend does not prove that every callback, fee behavior or access rule is safe for a user.","sourceIds":["uniswap-v4-hooks","pancakeswap-infinity-hooks","pancakeswap-custom-layer-hook"],"risk":"low"},{"id":"c6","text":"Public protocol documentation cannot prove private wallet safety, third-party hook quality, future frontend routing, gas cost, MEV exposure or price outcome.","sourceIds":["uniswap-v4-hooks","uniswap-build-first-hook","pancakeswap-infinity-hooks","pancakeswap-custom-layer-hook"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"chainlink-smartdata-circle-reserve-tokenized-asset-disclosure-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-09T00:08:00.000Z","updatedAt":"2026-10-09T00:08:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Chainlink SmartData and Circle Reserve Disclosure for Tokenized-Asset Controls","zh-Hans":"Chainlink SmartData 与 Circle 储备披露的代币化资产控制图"},"summary":{"en":"Tokenized-asset disclosure should separate oracle data categories from issuer reserve disclosures. Chainlink documents SmartData, Proof of Reserve, NAVLink, SmartAUM and MVR feeds for RWA-style data, while Circle publishes.","zh-Hans":"Chainlink SmartData 与 Circle 储备披露的代币化资产控制图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Chainlink SmartData documentation describes Proof of Reserve, NAVLink and SmartAUM feed categories for tokenized real-world-asset data.","sourceIds":["chainlink-smartdata"],"risk":"medium"},{"id":"c2","text":"Chainlink SmartData address documentation lists SmartData feed categories and warns users to review feed configuration and data quality.","sourceIds":["chainlink-smartdata-addresses"],"risk":"medium"},{"id":"c3","text":"Chainlink Selecting Quality Data Feeds documentation discusses custom feeds, proof-of-reserve feeds and data-source risk categories.","sourceIds":["chainlink-quality-feeds"],"risk":"medium"},{"id":"c4","text":"Circle's transparency page describes USDC reserve and stability disclosures.","sourceIds":["circle-transparency"],"risk":"medium"},{"id":"c5","text":"A reserve feed, NAV feed, AUM feed or issuer reserve page does not by itself prove every redemption, collateral or ownership condition for a tokenized asset.","sourceIds":["chainlink-smartdata","chainlink-smartdata-addresses","chainlink-quality-feeds","circle-transparency"],"risk":"low"},{"id":"c6","text":"Public oracle and reserve documentation cannot prove private account eligibility, future redemption availability, issuer insolvency outcome, tax treatment or local legal status.","sourceIds":["chainlink-smartdata","chainlink-smartdata-addresses","chainlink-quality-feeds","circle-transparency"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"chainlink-vs-pyth-price-feed-freshness-confidence-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-09T00:08:00.000Z","updatedAt":"2026-10-09T00:08:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Chainlink vs Pyth Price Feed Freshness and Confidence Controls","zh-Hans":"Chainlink 与 Pyth 价格数据新鲜度和置信区间控制对比"},"summary":{"en":"Chainlink and Pyth should be compared as price-evidence systems with different freshness and uncertainty fields, not as interchangeable oracle labels.","zh-Hans":"Chainlink 与 Pyth 价格数据新鲜度和置信区间控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Chainlink documents Data Feeds as a way to connect smart contracts to real-world data including prices, reserves and L2 sequencer status.","sourceIds":["chainlink-data-feeds-overview"],"risk":"medium"},{"id":"c2","text":"Chainlink Data Feeds API reference documents latestRoundData returning roundId, answer, startedAt, updatedAt and answeredInRound.","sourceIds":["chainlink-api-reference"],"risk":"medium"},{"id":"c3","text":"Pyth payload documentation describes price, exponent, confidence and feedUpdateTimestamp fields for price-feed messages.","sourceIds":["pyth-payload-reference"],"risk":"medium"},{"id":"c4","text":"Pyth best-practices documentation discusses staleness, availability gaps and confidence intervals as integration risks.","sourceIds":["pyth-best-practices"],"risk":"medium"},{"id":"c5","text":"A price feed being available does not prove that a consuming protocol has selected an acceptable freshness, confidence or fallback policy.","sourceIds":["chainlink-api-reference","pyth-payload-reference","pyth-best-practices"],"risk":"low"},{"id":"c6","text":"Public oracle documentation cannot prove private protocol risk settings, future feed availability, market-session behavior, bridge state or liquidation safety.","sourceIds":["chainlink-data-feeds-overview","chainlink-api-reference","pyth-payload-reference","pyth-best-practices"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"circle-mica-usdc-redemption-jurisdiction-boundary","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-09T00:08:00.000Z","updatedAt":"2026-10-09T00:08:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Circle MiCA and USDC Redemption Jurisdiction Boundary","zh-Hans":"Circle MiCA 与 USDC 赎回司法辖区边界"},"summary":{"en":"Circle's USDC redemption evidence should be separated by jurisdiction and account relationship. Circle's non-EEA USDC Terms distinguish Circle Mint users from other holders, while its MiCA Redemption Policy and MiCA USDC White.","zh-Hans":"Circle MiCA 与 USDC 赎回司法辖区边界：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Circle's USDC Terms describe non-EEA applicability and distinguish Circle Mint users from holders without a Circle Mint account.","sourceIds":["circle-usdc-terms"],"risk":"medium"},{"id":"c2","text":"Circle's MiCA Redemption Policy describes redemption conditions and process context for USDC and EURC within the European Union and EEA.","sourceIds":["circle-mica-redemption"],"risk":"medium"},{"id":"c3","text":"Circle's MiCA USDC White Paper points EEA holders to the MiCA redemption-policy framework and non-EEA holders to other Circle terms.","sourceIds":["circle-mica-whitepaper"],"risk":"medium"},{"id":"c4","text":"Circle's transparency page describes reserve and stability disclosures for USDC.","sourceIds":["circle-transparency"],"risk":"medium"},{"id":"c5","text":"Holding USDC does not prove direct redemption eligibility without identifying holder location, issuer entity and account status.","sourceIds":["circle-usdc-terms","circle-mica-redemption","circle-mica-whitepaper"],"risk":"low"},{"id":"c6","text":"Public legal and transparency pages cannot prove private account approval, future transaction processing, regulator restrictions, bank availability or third-party platform price stability.","sourceIds":["circle-usdc-terms","circle-mica-redemption","circle-mica-whitepaper","circle-transparency"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-create-coinbase-advanced-trade-api-key-with-portfolio-scope-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-09T00:08:00.000Z","updatedAt":"2026-10-09T00:08:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"How to Create a Coinbase Advanced Trade API Key With Portfolio Scope Safely","zh-Hans":"如何安全创建带 Portfolio 范围的 Coinbase Advanced Trade API Key"},"summary":{"en":"A Coinbase Advanced Trade API key should be onboarded as a permission-scoped credential, not as a generic bot password.","zh-Hans":"如何安全创建带 Portfolio 范围的 Coinbase Advanced Trade API Key：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Developer initial setup documentation describes signing up for CDP and generating a Secret API key from the API Keys portal.","sourceIds":["coinbase-initial-setup"],"risk":"medium"},{"id":"c2","text":"Coinbase Advanced Trade portfolio documentation says each portfolio should have a dedicated API key to limit access to that portfolio.","sourceIds":["coinbase-portfolios"],"risk":"medium"},{"id":"c3","text":"Coinbase Advanced Trade REST endpoint documentation describes public and private endpoints and an API key permissions endpoint.","sourceIds":["coinbase-rest-endpoints"],"risk":"medium"},{"id":"c4","text":"Coinbase WebSocket authentication documentation describes an authentication surface for Advanced Trade WebSocket usage.","sourceIds":["coinbase-websocket-auth"],"risk":"medium"},{"id":"c5","text":"An API key being created does not prove that trade, transfer or manage permission is required for a user's first integration.","sourceIds":["coinbase-initial-setup","coinbase-portfolios","coinbase-rest-endpoints"],"risk":"low"},{"id":"c6","text":"Public Coinbase documentation cannot prove private account eligibility, future endpoint access, key download recovery, account region support or bot safety.","sourceIds":["coinbase-initial-setup","coinbase-portfolios","coinbase-rest-endpoints","coinbase-websocket-auth"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-withdrawal-address-verification-allowlist-controls","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-09T00:08:00.000Z","updatedAt":"2026-10-09T00:08:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"OKX Withdrawal Address Verification and Allowlist Controls","zh-Hans":"OKX 提币地址验证与白名单控制清单"},"summary":{"en":"OKX withdrawal safety should be read as an address-book and verification workflow, not as a generic whitelist label.","zh-Hans":"OKX 提币地址验证与白名单控制清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"OKX help documentation describes withdrawal address book recipient types for OKX users and on-chain addresses.","sourceIds":["okx-address-book"],"risk":"medium"},{"id":"c2","text":"OKX address type upgrade documentation describes network scope and token scope options for saved withdrawal addresses.","sourceIds":["okx-address-type-upgrade"],"risk":"medium"},{"id":"c3","text":"OKX wallet-address verification documentation explains a wallet-signature verification flow when verification is required for a withdrawal address.","sourceIds":["okx-wallet-address-verification"],"risk":"medium"},{"id":"c4","text":"OKX allowlist documentation describes allowlist behavior and a new-address withdrawal lock option.","sourceIds":["okx-allowlist-app"],"risk":"medium"},{"id":"c5","text":"Saving or verifying a recipient does not prove that the destination details, memo, network or future account restrictions are correct for a specific withdrawal.","sourceIds":["okx-address-book","okx-address-type-upgrade","okx-wallet-address-verification","okx-allowlist-app"],"risk":"low"},{"id":"c6","text":"Public help documentation cannot prove private account eligibility, region-specific availability, support review timing, future lock periods or recovery after a mistaken withdrawal.","sourceIds":["okx-address-book","okx-address-type-upgrade","okx-wallet-address-verification","okx-allowlist-app"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-okx-account-configuration-api-key-permission-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-08T21:08:00.000Z","updatedAt":"2026-10-08T21:08:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs OKX Account Configuration and API-Key Permission Controls","zh-Hans":"Binance 与 OKX 账户配置和 API Key 权限控制对比"},"summary":{"en":"Binance and OKX account-control documentation should be compared as permission and reconciliation systems, not as generic API access.","zh-Hans":"Binance 与 OKX 账户配置和 API Key 权限控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance publishes official Spot REST account endpoint documentation for account-state queries.","sourceIds":["binance-account-endpoints"],"risk":"medium"},{"id":"c2","text":"Binance publishes official Spot user data stream documentation for account event streams.","sourceIds":["binance-user-data-stream"],"risk":"medium"},{"id":"c3","text":"OKX publishes official API-key creation guidance in its API documentation.","sourceIds":["okx-api-key-creation"],"risk":"medium"},{"id":"c4","text":"OKX publishes an official account-configuration endpoint in its REST API documentation.","sourceIds":["okx-account-config"],"risk":"medium"},{"id":"c5","text":"An API key existing does not prove that the key should have trading, withdrawal, transfer or account-wide authority.","sourceIds":["binance-account-endpoints","binance-user-data-stream","okx-api-key-creation","okx-account-config"],"risk":"low"},{"id":"c6","text":"Public documentation cannot prove private account permission, regional eligibility, future rate limits, user-data stream freshness or production recovery after a disconnect.","sourceIds":["binance-account-endpoints","binance-user-data-stream","okx-api-key-creation","okx-account-config"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"circle-usdc-mint-redemption-reserve-transparency-risk-map","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-08T21:08:00.000Z","updatedAt":"2026-10-08T21:08:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Circle USDC Mint, Redemption and Reserve Transparency: Risk Map","zh-Hans":"Circle USDC 铸造、赎回与储备透明度：风险地图"},"summary":{"en":"Circle USDC should be evaluated through issuer, redemption and reserve-disclosure boundaries rather than treated as a generic dollar token.","zh-Hans":"Circle USDC 铸造、赎回与储备透明度：风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Circle publishes official USDC product information.","sourceIds":["circle-usdc"],"risk":"medium"},{"id":"c2","text":"Circle publishes USDC terms as official legal terms for the token.","sourceIds":["circle-usdc-terms"],"risk":"medium"},{"id":"c3","text":"Circle publishes reserve-transparency material for USDC and related stablecoin disclosures.","sourceIds":["circle-transparency"],"risk":"medium"},{"id":"c4","text":"Circle publishes Circle Mint material for business minting and redemption workflows.","sourceIds":["circle-mint"],"risk":"medium"},{"id":"c5","text":"A stablecoin product page does not prove that a private user can mint, redeem or access a specific network route.","sourceIds":["circle-usdc","circle-usdc-terms","circle-transparency","circle-mint"],"risk":"low"},{"id":"c6","text":"Public issuer material cannot prove future redemption timing, account eligibility, jurisdictional availability, network finality or secondary-market liquidity.","sourceIds":["circle-usdc","circle-usdc-terms","circle-transparency","circle-mint"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-status-page-maintenance-incident-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-08T21:08:00.000Z","updatedAt":"2026-10-08T21:08:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange Status-Page Maintenance and Incident Disclosure Radar","zh-Hans":"交易所状态页维护与事故披露 Radar"},"summary":{"en":"Exchange status evidence should be separated from product marketing and from account-specific support outcomes.","zh-Hans":"交易所状态页维护与事故披露 Radar：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase maintains a public status page.","sourceIds":["coinbase-status"],"risk":"medium"},{"id":"c2","text":"Kraken maintains a public status page.","sourceIds":["kraken-status"],"risk":"medium"},{"id":"c3","text":"OKX maintains a public status page.","sourceIds":["okx-status"],"risk":"medium"},{"id":"c4","text":"Binance maintains public support announcement channels for service and product updates.","sourceIds":["binance-announcements"],"risk":"medium"},{"id":"c5","text":"A status page recovery marker does not prove that a private user's pending transaction, order or support case is resolved.","sourceIds":["coinbase-status","kraken-status","okx-status","binance-announcements"],"risk":"low"},{"id":"c6","text":"Public incident disclosures cannot prove private account eligibility, hidden holds, compliance review, final settlement or future recurrence.","sourceIds":["coinbase-status","kraken-status","okx-status","binance-announcements"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-create-uniswap-v4-pool-set-hooks-and-liquidity-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-08T21:08:00.000Z","updatedAt":"2026-10-08T21:08:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"How to Create a Uniswap v4 Pool, Set Hooks and Add Liquidity Safely","zh-Hans":"如何安全创建 Uniswap v4 池、设置 Hooks 并添加流动性"},"summary":{"en":"A Uniswap v4 onboarding workflow should treat pool creation, hooks, liquidity and swaps as separate checkpoints. Uniswap publishes v4 developer guides for creating a pool, managing liquidity and swapping.","zh-Hans":"如何安全创建 Uniswap v4 池、设置 Hooks 并添加流动性：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Uniswap publishes a v4 developer guide for creating a pool.","sourceIds":["uniswap-create-pool"],"risk":"medium"},{"id":"c2","text":"Uniswap publishes v4 developer material for setting up liquidity management.","sourceIds":["uniswap-liquidity-setup"],"risk":"medium"},{"id":"c3","text":"Uniswap publishes a v4 developer guide for swaps.","sourceIds":["uniswap-swap"],"risk":"medium"},{"id":"c4","text":"Uniswap publishes v4 concept documentation for hooks.","sourceIds":["uniswap-hooks"],"risk":"medium"},{"id":"c5","text":"A working tutorial path does not prove that a specific pool, hook, token pair or wallet is safe for real funds.","sourceIds":["uniswap-create-pool","uniswap-liquidity-setup","uniswap-swap","uniswap-hooks"],"risk":"low"},{"id":"c6","text":"Public developer documentation cannot prove private wallet security, approval safety, hook behavior under every path, future gas cost or price outcome.","sourceIds":["uniswap-create-pool","uniswap-liquidity-setup","uniswap-swap","uniswap-hooks"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-websocket-v2-add-cancel-order-lifecycle-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-08T21:08:00.000Z","updatedAt":"2026-10-08T21:08:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken WebSocket v2 Add and Cancel Order Lifecycle Readiness Checklist","zh-Hans":"Kraken WebSocket v2 下单与撤单生命周期准备清单"},"summary":{"en":"Kraken WebSocket v2 order controls should be treated as a lifecycle with command, acknowledgement, execution and reconciliation states.","zh-Hans":"Kraken WebSocket v2 下单与撤单生命周期准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Kraken publishes official Spot WebSocket v2 documentation.","sourceIds":["kraken-ws-v2"],"risk":"medium"},{"id":"c2","text":"Kraken documents add_order as a WebSocket v2 order-entry method.","sourceIds":["kraken-add-order"],"risk":"medium"},{"id":"c3","text":"Kraken documents cancel_order as a WebSocket v2 cancellation method.","sourceIds":["kraken-cancel-order"],"risk":"medium"},{"id":"c4","text":"Kraken documents a REST route for getting a WebSockets token used in WebSocket authentication workflows.","sourceIds":["kraken-ws-token"],"risk":"medium"},{"id":"c5","text":"A successful WebSocket command does not by itself prove final order state without acknowledgement and reconciliation evidence.","sourceIds":["kraken-ws-v2","kraken-add-order","kraken-cancel-order","kraken-ws-token"],"risk":"low"},{"id":"c6","text":"Public documentation cannot prove private account permission, final fill state, token freshness, future rate limits or support recovery for a specific trading session.","sourceIds":["kraken-ws-v2","kraken-add-order","kraken-cancel-order","kraken-ws-token"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-uta-account-mode-margin-mode-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-08T18:06:00.000Z","updatedAt":"2026-10-08T18:06:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit UTA Account Mode and Margin Mode Readiness Checklist","zh-Hans":"Bybit UTA 账户模式与保证金模式准备清单"},"summary":{"en":"Bybit's Unified Trading Account documentation makes account mode and margin mode separate readiness controls.","zh-Hans":"Bybit UTA 账户模式与保证金模式准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit Get Account Info documentation describes account information such as margin mode and account mode.","sourceIds":["bybit-account-info"],"risk":"medium"},{"id":"c2","text":"Bybit Different Account Modes documentation distinguishes UTA versions and explains how unifiedMarginStatus identifies account mode.","sourceIds":["bybit-account-modes"],"risk":"medium"},{"id":"c3","text":"Bybit Set Margin Mode documentation provides an account-level route for margin-mode changes.","sourceIds":["bybit-set-margin-mode"],"risk":"medium"},{"id":"c4","text":"Bybit Help Center maintains a Unified Trading Account topic area for user-facing UTA explanations.","sourceIds":["bybit-uta-help"],"risk":"medium"},{"id":"c5","text":"A documented account or margin mode does not prove a private account can switch modes at a specific time.","sourceIds":["bybit-account-info","bybit-account-modes","bybit-set-margin-mode","bybit-uta-help"],"risk":"low"},{"id":"c6","text":"Public documentation does not prove collateral eligibility, open-position safety, pending-order cleanup, liquidation result or regional availability.","sourceIds":["bybit-account-info","bybit-account-modes","bybit-set-margin-mode","bybit-uta-help"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-vs-kraken-websocket-authentication-liveness-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-08T18:06:00.000Z","updatedAt":"2026-10-08T18:06:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase vs Kraken WebSocket Authentication: Liveness-Control Checklist","zh-Hans":"Coinbase 与 Kraken WebSocket 认证：连接存活控制清单"},"summary":{"en":"Coinbase Advanced Trade WebSocket and Kraken WebSocket v2 should be compared as session-control systems, not just streaming endpoints.","zh-Hans":"Coinbase 与 Kraken WebSocket 认证：连接存活控制清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase documents Advanced Trade WebSocket as an official real-time API surface with dedicated overview material.","sourceIds":["coinbase-ws-overview"],"risk":"medium"},{"id":"c2","text":"Coinbase documents WebSocket authentication separately from the generic WebSocket overview.","sourceIds":["coinbase-ws-auth"],"risk":"medium"},{"id":"c3","text":"Kraken documents Spot WebSocket v2 as an official WebSocket API surface.","sourceIds":["kraken-ws-v2"],"risk":"medium"},{"id":"c4","text":"Kraken documents a Get Websockets Token route for WebSocket authentication workflows.","sourceIds":["kraken-ws-token"],"risk":"medium"},{"id":"c5","text":"A WebSocket connection being open does not prove account permission, token freshness, order-state reconciliation or downstream trading safety.","sourceIds":["coinbase-ws-overview","coinbase-ws-auth","kraken-ws-v2","kraken-ws-token"],"risk":"low"},{"id":"c6","text":"Public documentation cannot prove a private key scope, private account eligibility, regional access, future endpoint behavior or production liveness under network failure.","sourceIds":["coinbase-ws-overview","coinbase-ws-auth","kraken-ws-v2","kraken-ws-token"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"genius-act-stablecoin-aml-vs-bis-tokenised-deposit-risk-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-08T18:06:00.000Z","updatedAt":"2026-10-08T18:06:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"GENIUS Act Stablecoin AML vs BIS Tokenised Deposit Risk Map","zh-Hans":"GENIUS Act 稳定币 AML 与 BIS 代币化存款风险地图"},"summary":{"en":"The U.S. Treasury's GENIUS Act AML proposal and the BIS stablecoin/tokenised-deposit analysis answer different questions.","zh-Hans":"GENIUS Act 稳定币 AML 与 BIS 代币化存款风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Treasury's GENIUS Act AML proposal describes proposed AML and sanctions compliance requirements for permitted payment stablecoin issuers.","sourceIds":["treasury-genius-aml-proposal"],"risk":"medium"},{"id":"c2","text":"Treasury's GENIUS Act enactment statement frames the Act as a stablecoin regulatory milestone.","sourceIds":["treasury-genius-enactment"],"risk":"medium"},{"id":"c3","text":"BIS speech compares stablecoins and tokenised deposits through monetary trust, singleness and settlement considerations.","sourceIds":["bis-tokenised-deposits-speech"],"risk":"medium"},{"id":"c4","text":"BIS Annual Economic Report 2026 discusses unified-ledger and regulated private-money concepts in tokenisation context.","sourceIds":["bis-annual-economic-report-2026"],"risk":"medium"},{"id":"c5","text":"Issuer AML obligations, reserve disclosures, user transfer checks, settlement finality and tokenised-deposit claims are separate controls.","sourceIds":["treasury-genius-aml-proposal","treasury-genius-enactment","bis-tokenised-deposits-speech","bis-annual-economic-report-2026"],"risk":"low"},{"id":"c6","text":"Public policy materials do not prove a private stablecoin transfer is reversible, compliant, insured, redeemable in a user's jurisdiction or equivalent to a bank deposit.","sourceIds":["treasury-genius-aml-proposal","treasury-genius-enactment","bis-tokenised-deposits-speech","bis-annual-economic-report-2026"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"pyth-chainlink-oracle-freshness-confidence-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-08T18:06:00.000Z","updatedAt":"2026-10-08T18:06:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Pyth and Chainlink Oracle Freshness: Confidence and Heartbeat Disclosure Radar","zh-Hans":"Pyth 与 Chainlink 预言机新鲜度：置信区间与 Heartbeat 披露雷达"},"summary":{"en":"Oracle readiness depends on freshness and uncertainty controls, not only on whether a price endpoint returns a number.","zh-Hans":"Pyth 与 Chainlink 预言机新鲜度：置信区间与 Heartbeat 披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Pyth best-practices documentation discusses confidence intervals for price feeds.","sourceIds":["pyth-best-practices"],"risk":"medium"},{"id":"c2","text":"Pyth price-data documentation explains price-data fields and feed update information.","sourceIds":["pyth-understanding-price-data"],"risk":"medium"},{"id":"c3","text":"Chainlink Data Feeds documentation describes Data Feeds as an official price-feed surface.","sourceIds":["chainlink-data-feeds-overview"],"risk":"medium"},{"id":"c4","text":"Chainlink Data Feeds API reference documents latestRoundData fields including timestamps used for freshness checks.","sourceIds":["chainlink-data-feeds-api"],"risk":"medium"},{"id":"c5","text":"A price value without freshness and uncertainty context is not enough for collateral, liquidation, settlement or user-facing risk decisions.","sourceIds":["pyth-best-practices","pyth-understanding-price-data","chainlink-data-feeds-overview","chainlink-data-feeds-api"],"risk":"low"},{"id":"c6","text":"Public oracle documentation does not prove a particular application selected the correct feed, threshold, fallback or emergency pause rule.","sourceIds":["pyth-best-practices","pyth-understanding-price-data","chainlink-data-feeds-overview","chainlink-data-feeds-api"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-crypto-custody-vs-transfer-agent-recordkeeping-boundary-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-08T18:06:00.000Z","updatedAt":"2026-10-08T18:06:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Crypto Custody vs Transfer Agent Recordkeeping: Boundary Map","zh-Hans":"SEC 加密资产 Custody 与 Transfer Agent 记录保存：边界地图"},"summary":{"en":"SEC custody and transfer-agent materials should not be collapsed into one tokenized-asset rule. The SEC has a crypto custody proposal statement for advisers and funds, a Transfer Agent Rules proposal page, and staff.","zh-Hans":"SEC 加密资产 Custody 与 Transfer Agent 记录保存：边界地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"SEC published a statement on a proposal to address custody of crypto assets under the Investment Advisers Act and Investment Company Act.","sourceIds":["sec-crypto-custody-statement"],"risk":"medium"},{"id":"c2","text":"SEC Transfer Agent Rules page describes a proposal to update rules and forms for registered transfer agents.","sourceIds":["sec-transfer-agent-rules"],"risk":"medium"},{"id":"c3","text":"SEC staff tokenized-securities statement describes categories and rights-boundary issues for tokenized securities.","sourceIds":["sec-tokenized-securities-statement"],"risk":"medium"},{"id":"c4","text":"SEC press release on the Innovation Exemption concerns temporary conditional relief for certain tokenized NMS stock trading models.","sourceIds":["sec-innovation-exemption"],"risk":"medium"},{"id":"c5","text":"Custody, transfer-agent recordkeeping, trading venue operation and tokenized-security classification are different regulatory objects.","sourceIds":["sec-crypto-custody-statement","sec-transfer-agent-rules","sec-tokenized-securities-statement","sec-innovation-exemption"],"risk":"low"},{"id":"c6","text":"Public SEC materials do not prove that a private product is approved, that a token conveys direct ownership, or that a user has account-level custody protection.","sourceIds":["sec-crypto-custody-statement","sec-transfer-agent-rules","sec-tokenized-securities-statement","sec-innovation-exemption"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-unified-ledger-vs-stablecoin-two-tier-money-trust-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-08T12:02:00.000Z","updatedAt":"2026-10-08T12:02:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Unified Ledger vs Stablecoins: Two-Tier Money Trust Map","zh-Hans":"BIS Unified Ledger 与 Stablecoins：双层货币信任地图"},"summary":{"en":"BIS material frames tokenisation as a monetary-system design question, not a blanket endorsement of stablecoins or private crypto settlement.","zh-Hans":"BIS Unified Ledger 与 Stablecoins：双层货币信任地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"The 2026 BIS release frames the next-generation monetary and financial system around safeguarding trust in money.","sourceIds":["bis-2026-trust-money"],"risk":"medium"},{"id":"c2","text":"The 2026 BIS release says policy work should address weaknesses in current stablecoin arrangements and bring tokenisation into the two-tier system.","sourceIds":["bis-2026-trust-money"],"risk":"medium"},{"id":"c3","text":"BIS Annual Economic Report 2025 material describes a unified ledger involving tokenised central bank reserves, commercial bank money and financial assets.","sourceIds":["bis-aer-2025-next-gen"],"risk":"medium"},{"id":"c4","text":"BIS speech material discusses money in transition and the role of tokenisation in settlement and market infrastructure.","sourceIds":["bis-money-transition"],"risk":"medium"},{"id":"c5","text":"BIS digital-assets policy material treats tokenisation and DLT as potential efficiency tools that also raise monetary-policy and stability considerations.","sourceIds":["bis-digital-assets-policy"],"risk":"low"},{"id":"c6","text":"BIS materials do not prove that a private stablecoin, exchange balance, tokenized asset, wallet route or payment rail is safe, insured, redeemable or legally equivalent to bank money.","sourceIds":["bis-2026-trust-money","bis-aer-2025-next-gen","bis-money-transition","bis-digital-assets-policy"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-smp-trade-group-order-control-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-08T12:02:00.000Z","updatedAt":"2026-10-08T12:02:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit SMP Trade Group and Order-Control Readiness Checklist","zh-Hans":"Bybit SMP Trade Group 与订单控制准备清单"},"summary":{"en":"Bybit's self-match-prevention documentation turns SMP into an account and order-control question rather than a generic safety badge.","zh-Hans":"Bybit SMP Trade Group 与订单控制准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit self-match-prevention documentation describes execution policies including cancel maker, cancel taker and cancel both.","sourceIds":["bybit-smp"],"risk":"medium"},{"id":"c2","text":"Bybit SMP documentation describes SMP Trade Group behavior and UID-level relationships.","sourceIds":["bybit-smp"],"risk":"medium"},{"id":"c3","text":"Bybit changelog records updates to SMP behavior for compliant sites and derivative or spot contexts.","sourceIds":["bybit-v5-changelog"],"risk":"medium"},{"id":"c4","text":"Bybit user-setting configuration documentation exposes smpType as a trade-behaviour field.","sourceIds":["bybit-user-setting-config"],"risk":"medium"},{"id":"c5","text":"Bybit place-order documentation includes smpType and client order identity fields in the order-control surface.","sourceIds":["bybit-place-order"],"risk":"low"},{"id":"c6","text":"The public documentation does not prove a private account's institution status, group membership, live order cleanup, future site behavior or final execution outcome.","sourceIds":["bybit-smp","bybit-v5-changelog","bybit-user-setting-config","bybit-place-order"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-portfolio-vs-kraken-account-balance-evidence-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-08T12:02:00.000Z","updatedAt":"2026-10-08T12:02:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Portfolio vs Kraken Account Balance: Evidence-Control Comparison","zh-Hans":"Coinbase Portfolio 与 Kraken Account Balance：账户证据控制对比"},"summary":{"en":"Coinbase portfolios and Kraken account-balance endpoints are both account-state evidence surfaces, but they should not be treated as the same control.","zh-Hans":"Coinbase Portfolio 与 Kraken Account Balance：账户证据控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Advanced Trade portfolio documentation says portfolios support multiple trading environments and portfolio-specific segregation.","sourceIds":["coinbase-portfolios-guide"],"risk":"medium"},{"id":"c2","text":"Coinbase portfolio documentation says a dedicated CDP API key should be created for each portfolio to limit access scope.","sourceIds":["coinbase-portfolios-guide"],"risk":"medium"},{"id":"c3","text":"Coinbase API reference documents a create-portfolio endpoint under Advanced Trade portfolio APIs.","sourceIds":["coinbase-create-portfolio"],"risk":"medium"},{"id":"c4","text":"Kraken documents a get-account-balance endpoint as an account-data route.","sourceIds":["kraken-account-balance"],"risk":"medium"},{"id":"c5","text":"Kraken documents a get-trade-balance endpoint separately from the raw account-balance endpoint.","sourceIds":["kraken-trade-balance"],"risk":"low"},{"id":"c6","text":"Public account-data documentation does not prove private balances, account eligibility, reconciliation correctness, tax treatment, support recovery or future endpoint behavior.","sourceIds":["coinbase-portfolios-guide","coinbase-create-portfolio","kraken-account-balance","kraken-trade-balance"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-client-order-id-retry-reconciliation-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-08T12:02:00.000Z","updatedAt":"2026-10-08T12:02:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange Client Order ID Retry and Reconciliation Radar","zh-Hans":"加密交易所 Client Order ID 重试与对账雷达"},"summary":{"en":"Client order identity is a retry-safety field, not a complete execution receipt. Coinbase Exchange documentation lets users query or cancel orders by exchange id or client-assigned client_oid.","zh-Hans":"加密交易所 Client Order ID 重试与对账雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Exchange get-order documentation says an order can be queried by exchange-assigned id or client-assigned client_oid.","sourceIds":["coinbase-get-order"],"risk":"medium"},{"id":"c2","text":"Coinbase Exchange cancel-order documentation says cancellation can use exchange id or client-assigned client_oid and describes cancel-reject behavior.","sourceIds":["coinbase-cancel-order"],"risk":"medium"},{"id":"c3","text":"Kraken WebSocket v2 add_order documentation is an order-entry surface for creating orders over WebSocket.","sourceIds":["kraken-ws-add-order"],"risk":"medium"},{"id":"c4","text":"OKX place-order documentation is a separate official order-entry surface with its own request and response semantics.","sourceIds":["okx-place-order"],"risk":"medium"},{"id":"c5","text":"Bybit place-order documentation includes orderLinkId and other order-control fields.","sourceIds":["bybit-place-order"],"risk":"low"},{"id":"c6","text":"A client order id does not prove final fill, settlement, cancellation, position state, private risk approval or support recovery.","sourceIds":["coinbase-get-order","coinbase-cancel-order","kraken-ws-add-order","okx-place-order","bybit-place-order"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-collateral-appchain-tokenized-collateral-mobility-risk-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-08T12:02:00.000Z","updatedAt":"2026-10-08T12:02:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Collateral AppChain: Tokenized Collateral Mobility Risk Map","zh-Hans":"DTCC Collateral AppChain：代币化抵押品流动性风险地图"},"summary":{"en":"DTCC's Collateral AppChain material should be read as institutional market-infrastructure evidence, not as proof that any retail tokenized asset is liquid, redeemable or legally equivalent to direct ownership.","zh-Hans":"DTCC Collateral AppChain：代币化抵押品流动性风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"DTCC digital-assets material describes services for connecting traditional and digital markets through trusted infrastructure and approved networks.","sourceIds":["dtcc-digital-assets"],"risk":"medium"},{"id":"c2","text":"DTCC Collateral AppChain material frames the product around collateral mobility, visibility, operational efficiency and tokenized capital markets.","sourceIds":["dtcc-collateral-appchain"],"risk":"medium"},{"id":"c3","text":"DTCC's 2026 Collateral AppChain insight discusses movement from experimentation toward production infrastructure.","sourceIds":["dtcc-appchain-production"],"risk":"medium"},{"id":"c4","text":"DTCC's 2025 platform announcement describes tokenized real-time collateral management and AppChain-based infrastructure.","sourceIds":["dtcc-appchain-release"],"risk":"medium"},{"id":"c5","text":"Collateral mobility, tokenized collateral and participant access are separate questions from retail token ownership or exchange listing.","sourceIds":["dtcc-digital-assets","dtcc-collateral-appchain"],"risk":"low"},{"id":"c6","text":"The cited DTCC materials do not prove a private user's access, legal entitlement, eligible asset list, settlement finality, redemption right or future production adoption.","sourceIds":["dtcc-digital-assets","dtcc-collateral-appchain","dtcc-appchain-production","dtcc-appchain-release"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-okx-api-timestamp-signature-replay-risk-radar","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-08T09:02:00.000Z","updatedAt":"2026-10-08T09:02:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Binance and OKX API Timestamp Signatures: Replay and Drift Risk Radar","zh-Hans":"Binance 与 OKX API Timestamp Signatures：重放与时钟漂移风险雷达"},"summary":{"en":"Binance and OKX both require signed private API requests, but their replay-control evidence should be recorded as venue-specific authentication rules.","zh-Hans":"Binance 与 OKX API Timestamp Signatures：重放与时钟漂移风险雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance WebSocket API request-security documentation describes SIGNED request security and timestamp-related request validation.","sourceIds":["binance-request-security"],"risk":"medium"},{"id":"c2","text":"Binance WebSocket API documentation includes general API information that shapes request handling and error interpretation.","sourceIds":["binance-general-api"],"risk":"medium"},{"id":"c3","text":"OKX REST authentication documentation describes signed requests using timestamp, method, request path and body as signature inputs.","sourceIds":["okx-rest-auth"],"risk":"medium"},{"id":"c4","text":"OKX trade WebSocket documentation is a separate private order route surface and should not be conflated with REST signing.","sourceIds":["okx-trade-ws-place-order"],"risk":"medium"},{"id":"c5","text":"Timestamp drift, receive-window assumptions and signature canonicalization are distinct failure causes that can look similar to users.","sourceIds":["binance-request-security","okx-rest-auth"],"risk":"low"},{"id":"c6","text":"Public API documentation does not prove private account permission, order acceptance, withdrawal acceptance, support recovery or future rate limits.","sourceIds":["binance-request-security","okx-rest-auth","okx-trade-ws-place-order"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-next-generation-monetary-system-tokenisation-readiness-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-08T09:02:00.000Z","updatedAt":"2026-10-08T09:02:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Next-Generation Monetary System: Tokenisation Readiness Map","zh-Hans":"BIS 下一代货币金融系统：Tokenisation 准备度地图"},"summary":{"en":"The BIS next-generation monetary-system discussion should be read as a policy and infrastructure map, not as proof that a specific stablecoin or tokenized deposit product is approved for a user.","zh-Hans":"BIS 下一代货币金融系统：Tokenisation 准备度地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"BIS Annual Economic Report 2025 includes a chapter on the next-generation monetary and financial system.","sourceIds":["bis-aer-2025-next-generation"],"risk":"medium"},{"id":"c2","text":"BIS frames tokenisation and ledger design as monetary and financial infrastructure questions rather than exchange product listings.","sourceIds":["bis-aer-2025-next-generation"],"risk":"medium"},{"id":"c3","text":"FSB maintains a crypto-assets and global stablecoins framework page as regulatory implementation context.","sourceIds":["fsb-crypto-stablecoin-framework"],"risk":"medium"},{"id":"c4","text":"A policy or infrastructure report does not prove private account eligibility, issuer redemption, product launch, legal rights or user recourse.","sourceIds":["bis-aer-2025-next-generation","fsb-crypto-stablecoin-framework"],"risk":"medium"},{"id":"c5","text":"Stablecoins, tokenised deposits, tokenized securities and central bank money are separate settlement and claim objects.","sourceIds":["bis-aer-2025-next-generation"],"risk":"low"},{"id":"c6","text":"The public sources do not prove a future product timeline, jurisdiction-specific approval, tax treatment, support recovery or indexing outcome.","sourceIds":["bis-aer-2025-next-generation","fsb-crypto-stablecoin-framework"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"circle-usdc-vs-paxos-usdp-redemption-reserve-control-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-08T09:02:00.000Z","updatedAt":"2026-10-08T09:02:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Circle USDC vs Paxos USDP: Redemption, Reserve and Issuer-Control Map","zh-Hans":"Circle USDC 与 Paxos USDP：赎回、储备与发行方控制地图"},"summary":{"en":"USDC and USDP are both dollar stablecoins, but a user should not treat their issuer controls as interchangeable.","zh-Hans":"Circle USDC 与 Paxos USDP：赎回、储备与发行方控制地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Circle's USDC Terms define the contractual terms for USDC minting and redemption by eligible Circle Mint customers.","sourceIds":["circle-usdc-terms"],"risk":"medium"},{"id":"c2","text":"Circle's transparency page presents reserve and attestation-oriented reporting for Circle stablecoins.","sourceIds":["circle-transparency"],"risk":"medium"},{"id":"c3","text":"Paxos documentation describes USDP as a Paxos-issued stablecoin product and documents product actions such as minting, redeeming and transferring.","sourceIds":["paxos-usdp-docs"],"risk":"medium"},{"id":"c4","text":"Issuer terms and reserve reports prove public issuer-side disclosures, not a private user's account approval or redemption result.","sourceIds":["circle-usdc-terms","circle-transparency","paxos-usdp-docs"],"risk":"medium"},{"id":"c5","text":"Network support, wallet custody, issuer compliance controls and venue listing support are separate objects from the token ticker.","sourceIds":["circle-usdc-terms","paxos-usdp-docs"],"risk":"low"},{"id":"c6","text":"The cited public sources do not prove future fees, taxes, support recovery, redemption timing, chain availability or private eligibility.","sourceIds":["circle-usdc-terms","paxos-usdp-docs"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-use-1inch-wallet-swap-slippage-and-price-impact-controls-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-08T09:02:00.000Z","updatedAt":"2026-10-08T09:02:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"How to Use 1inch: Wallet Connection, Swap, Slippage and Price-Impact Controls","zh-Hans":"如何使用 1inch：钱包连接、Swap、滑点与价格影响控制"},"summary":{"en":"A safe 1inch onboarding flow is a venue workflow, not an account-registration promise. 1inch help materials explain slippage tolerance and price impact concepts that affect swap execution.","zh-Hans":"如何使用 1inch：钱包连接、Swap、滑点与价格影响控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"1inch help documentation explains slippage tolerance as a setting relevant to swap execution.","sourceIds":["oneinch-slippage"],"risk":"medium"},{"id":"c2","text":"1inch help documentation explains price impact and distinguishes it from slippage.","sourceIds":["oneinch-price-impact"],"risk":"medium"},{"id":"c3","text":"A DEX aggregator route requires wallet, chain, token and approval checks before signing.","sourceIds":["oneinch-slippage","oneinch-price-impact"],"risk":"medium"},{"id":"c4","text":"A swap quote is not proof of final execution, final received amount, tax treatment, support recovery or future liquidity.","sourceIds":["oneinch-slippage","oneinch-price-impact"],"risk":"medium"},{"id":"c5","text":"Wallet onboarding should not be described as exchange account registration or KYC.","sourceIds":["oneinch-slippage","oneinch-price-impact"],"risk":"low"},{"id":"c6","text":"Public help pages do not prove private wallet safety, token legitimacy, transaction success, fee, MEV outcome or future route availability.","sourceIds":["oneinch-slippage","oneinch-price-impact"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-use-cow-swap-wallet-intent-order-and-surplus-controls-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-08T09:02:00.000Z","updatedAt":"2026-10-08T09:02:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"How to Use CoW Swap: Wallet, Intent Order and Surplus-Control Checklist","zh-Hans":"如何使用 CoW Swap：钱包、Intent Order 与 Surplus 控制清单"},"summary":{"en":"CoW Swap onboarding should be framed around intents and solver execution, not as a conventional exchange account tutorial. CoW Protocol documentation describes CoW Swap tutorials and references intent-based order concepts.","zh-Hans":"如何使用 CoW Swap：钱包、Intent Order 与 Surplus 控制清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"CoW Protocol documentation provides a CoW Swap tutorial as an official onboarding surface.","sourceIds":["cow-swap-tutorial"],"risk":"medium"},{"id":"c2","text":"CoW Protocol documentation describes intents as a core concept for orders.","sourceIds":["cow-intents"],"risk":"medium"},{"id":"c3","text":"A wallet signature request is different from a centralized exchange login or KYC flow.","sourceIds":["cow-swap-tutorial","cow-intents"],"risk":"medium"},{"id":"c4","text":"Intent signing, solver execution and settlement evidence are separate steps in a safe decision record.","sourceIds":["cow-swap-tutorial","cow-intents"],"risk":"medium"},{"id":"c5","text":"A public tutorial cannot prove private wallet safety, token legitimacy, solver outcome, final settlement, tax treatment or support recovery.","sourceIds":["cow-swap-tutorial","cow-intents"],"risk":"low"},{"id":"c6","text":"The onboarding flow must avoid seed phrases, private keys, identity documents, tax identifiers and credential collection.","sourceIds":["cow-swap-tutorial","cow-intents"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-margin-otoco-vs-okx-chase-trigger-order-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-08T06:13:00.000Z","updatedAt":"2026-10-08T06:13:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Margin OTOCO vs OKX Chase Trigger Orders: Advanced Order-Control Boundaries","zh-Hans":"Binance Margin OTOCO 与 OKX Chase Trigger Orders：高级订单控制边界"},"summary":{"en":"Binance margin OTOCO changes and OKX chase trigger orders both affect advanced order automation, but they are different evidence objects.","zh-Hans":"Binance Margin OTOCO 与 OKX Chase Trigger Orders：高级订单控制边界：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance margin trading change log documents 2026 updates affecting OTO and OTOCO margin order endpoints.","sourceIds":["binance-margin-changelog"],"risk":"medium"},{"id":"c2","text":"Binance support documentation explains sideEffectType values for margin order endpoints, including AUTO_BORROW_REPAY as an auto borrow and auto repay behavior.","sourceIds":["binance-side-effect-faq"],"risk":"medium"},{"id":"c3","text":"OKX API changelog documents a chase limit order mode for FUTURES/SWAP trigger orders and describes advChaseParams and subAlgoIdList fields.","sourceIds":["okx-api-changelog"],"risk":"medium"},{"id":"c4","text":"OKX place algo order documentation is the official route family for algorithmic order placement.","sourceIds":["okx-place-algo-order"],"risk":"medium"},{"id":"c5","text":"Borrow-repay side effects and chase trigger execution are separate control surfaces and should not be treated as interchangeable order types.","sourceIds":["binance-margin-changelog","binance-side-effect-faq","okx-api-changelog"],"risk":"low"},{"id":"c6","text":"The public documentation does not prove private account eligibility, margin availability, trigger execution, spawned order fill, liquidation outcome or support recovery.","sourceIds":["binance-margin-changelog","okx-api-changelog","okx-place-algo-order"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-stablecoin-tokenisation-two-tier-money-trust-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-08T06:13:00.000Z","updatedAt":"2026-10-08T06:13:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Stablecoin and Tokenisation Framework: Two-Tier Money Trust Map","zh-Hans":"BIS 稳定币与代币化框架：双层货币信任地图"},"summary":{"en":"The BIS 2026 stablecoin and tokenisation material frames tokenised finance as a trust and monetary-architecture question, not simply an asset-on-chain story.","zh-Hans":"BIS 稳定币与代币化框架：双层货币信任地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"BIS says stablecoins display some potential of tokenisation but their current form can fall short on key properties of money and pose macro-financial risks.","sourceIds":["bis-next-generation-money"],"risk":"medium"},{"id":"c2","text":"BIS annual report material discusses stablecoins, tokenised deposits and tokenised money market fund shares as different money-like instruments.","sourceIds":["bis-annual-report-2026"],"risk":"medium"},{"id":"c3","text":"BIS Paper 170 analyses stablecoin effects on the international monetary and financial system and highlights possible digital dollarisation risks.","sourceIds":["bis-paper-170"],"risk":"medium"},{"id":"c4","text":"A BIS 2026 speech frames tokenisation within the traditional two-tier system as involving tokenised commercial bank deposits and central-bank reserves.","sourceIds":["bis-global-outlook-innovation"],"risk":"medium"},{"id":"c5","text":"Stablecoins, tokenised deposits and tokenised fund shares are not interchangeable rights bundles or settlement guarantees.","sourceIds":["bis-annual-report-2026","bis-next-generation-money"],"risk":"low"},{"id":"c6","text":"The BIS materials do not prove a private issuer's reserve quality, redemption path, wallet eligibility, jurisdictional treatment or account-specific rights.","sourceIds":["bis-paper-170","bis-annual-report-2026"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-api-changelog-signature-versioning-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-08T06:13:00.000Z","updatedAt":"2026-10-08T06:13:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange API Changelog Radar: Signature, Versioning and Order-Semantics Disclosures","zh-Hans":"交易所 API Changelog 雷达：签名、版本与订单语义披露"},"summary":{"en":"Exchange API changelogs are not release-note wallpaper; they are operational controls. Binance developer material says product-specific updates and official documentation should be reviewed before deployment, and its.","zh-Hans":"交易所 API Changelog 雷达：签名、版本与订单语义披露：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance developer introduction says official supported interfaces are documented in its portal and product-specific updates should be reviewed before deployment or upgrade.","sourceIds":["binance-developer-intro"],"risk":"medium"},{"id":"c2","text":"Binance spot block matching change log includes a time-sensitive signed-endpoint notice about percent-encoding payloads before computing signatures.","sourceIds":["binance-block-match-changelog"],"risk":"medium"},{"id":"c3","text":"Binance margin trading change log includes 2026 changes for margin order endpoints and sideEffectType behavior.","sourceIds":["binance-margin-changelog"],"risk":"medium"},{"id":"c4","text":"OKX API changelog includes order-semantics updates such as chase trigger order parameters and spawned order identifiers.","sourceIds":["okx-api-changelog"],"risk":"medium"},{"id":"c5","text":"A changelog entry can change signing logic, request weights, endpoint semantics, read-side reconciliation or user-facing error handling.","sourceIds":["binance-block-match-changelog","binance-margin-changelog","okx-api-changelog"],"risk":"low"},{"id":"c6","text":"A public changelog cannot prove a private integration has migrated, tested, rolled back or survived production traffic.","sourceIds":["binance-developer-intro","okx-api-changelog"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fsb-crypto-stablecoin-framework-implementation-gap-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-08T06:13:00.000Z","updatedAt":"2026-10-08T06:13:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"FSB Crypto and Stablecoin Framework: Implementation Gap Map","zh-Hans":"FSB 加密资产与稳定币框架：实施缺口地图"},"summary":{"en":"The FSB's crypto-asset and global stablecoin materials frame the next policy problem as implementation quality, not headline rule-making.","zh-Hans":"FSB 加密资产与稳定币框架：实施缺口地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"FSB's thematic peer review assesses implementation of the 2023 global regulatory framework for crypto-asset activities and global stablecoin arrangements.","sourceIds":["fsb-thematic-review-pdf"],"risk":"medium"},{"id":"c2","text":"The FSB-IOSCO joint information note describes complementary reviews and distinguishes financial stability, investor protection and market integrity scopes.","sourceIds":["fsb-iosco-joint-note"],"risk":"medium"},{"id":"c3","text":"FSB's October 2025 release says progress on regulating global stablecoin arrangements is lagging compared with crypto-asset markets and activities.","sourceIds":["fsb-crypto-stablecoin-gaps-release"],"risk":"medium"},{"id":"c4","text":"FSB's 2025 annual report says full and consistent implementation of the crypto-asset and global stablecoin framework was a key focus area.","sourceIds":["fsb-annual-report-2025"],"risk":"medium"},{"id":"c5","text":"FSB materials distinguish crypto-asset activities, global stablecoin arrangements, data reporting and cross-border cooperation as separate implementation surfaces.","sourceIds":["fsb-thematic-review-pdf","fsb-crypto-stablecoin-gaps-release"],"risk":"low"},{"id":"c6","text":"The source set does not prove a specific exchange, issuer, wallet, protocol, token or user account is licensed, safe, compliant, non-compliant or available in a jurisdiction.","sourceIds":["fsb-thematic-review-pdf","fsb-iosco-joint-note"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-chase-limit-trigger-order-api-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-08T06:13:00.000Z","updatedAt":"2026-10-08T06:13:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"OKX Chase Limit Trigger Orders: API Readiness Checklist","zh-Hans":"OKX Chase Limit Trigger Orders：API 就绪清单"},"summary":{"en":"OKX's chase limit order update should be handled as an API-readiness change, not a trading signal. The OKX changelog says FUTURES and SWAP trigger orders can use chase as a post-trigger execution type, with advChaseParams in.","zh-Hans":"OKX Chase Limit Trigger Orders：API 就绪清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"OKX changelog documents chase as a post-trigger execution type for FUTURES/SWAP trigger orders.","sourceIds":["okx-api-changelog"],"risk":"medium"},{"id":"c2","text":"OKX changelog describes advChaseParams for placement and amendment flows.","sourceIds":["okx-api-changelog"],"risk":"medium"},{"id":"c3","text":"OKX changelog describes subAlgoIdList as a read-side field for spawned chase order identifiers after trigger firing.","sourceIds":["okx-api-changelog"],"risk":"medium"},{"id":"c4","text":"OKX official API documentation contains separate place-algo-order, amend-algo-order and algo orders channel surfaces.","sourceIds":["okx-place-algo-order","okx-amend-algo-order","okx-algo-orders-channel"],"risk":"medium"},{"id":"c5","text":"A chase trigger order requires both write-route validation and read-route reconciliation; a placement response alone is not a final execution record.","sourceIds":["okx-api-changelog","okx-algo-orders-channel"],"risk":"low"},{"id":"c6","text":"The source set does not prove private account eligibility, market acceptance, fill quality, liquidation behavior, support outcome or future availability.","sourceIds":["okx-api-changelog","okx-place-algo-order"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-order-amend-keep-priority-api-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-08T03:04:00.000Z","updatedAt":"2026-10-08T03:04:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Order Amend Keep Priority: API Readiness Checklist","zh-Hans":"Binance Order Amend Keep Priority：API 就绪清单"},"summary":{"en":"Binance's order-amend surface should be treated as a reconciliation feature, not a shortcut around normal order controls. The official trading endpoint, filters and user-data stream documents are the evidence boundary.","zh-Hans":"Binance Order Amend Keep Priority：API 就绪清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance publishes official Spot REST trading endpoint documentation.","sourceIds":["binance-trading-endpoints"],"risk":"medium"},{"id":"c2","text":"Binance publishes official Spot API filter documentation.","sourceIds":["binance-filters"],"risk":"medium"},{"id":"c3","text":"Binance publishes official Spot user-data stream documentation for account events.","sourceIds":["binance-user-data-stream"],"risk":"medium"},{"id":"c4","text":"The trading endpoint source is the correct venue-owned source for order-amend implementation boundaries.","sourceIds":["binance-trading-endpoints","binance-trading-endpoints-catalog"],"risk":"medium"},{"id":"c5","text":"Filters and account event streams remain relevant when an order lifecycle changes.","sourceIds":["binance-filters","binance-user-data-stream"],"risk":"low"},{"id":"c6","text":"The public source set does not prove a private order can be amended, preserve priority, avoid rejection or reconcile under every future state.","sourceIds":["binance-trading-endpoints","binance-filters","binance-user-data-stream"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-test-order-vs-okx-place-order-pretrade-validation-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-08T03:04:00.000Z","updatedAt":"2026-10-08T03:04:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Test Order vs OKX Place Order: Pre-Trade Validation Controls","zh-Hans":"Binance Test Order 与 OKX Place Order：交易前校验控制"},"summary":{"en":"Binance and OKX expose different evidence objects before a live order is allowed to become an execution event.","zh-Hans":"Binance 与 OKX 在真实订单进入执行事件前，提供的是不同类型的证据对象。Binance 记录了交易端点、交易过滤器和 user-data 订单更新；OKX 在 order-book trading API 中记录了下单参数和独立的 close-position 路径。"},"claims":[{"id":"c1","text":"Binance publishes official Spot REST trading endpoint documentation for order-related actions.","sourceIds":["binance-trading-endpoints"],"risk":"medium"},{"id":"c2","text":"Binance publishes exchange filter documentation that defines rule families such as price, percent-price, lot-size and notional controls.","sourceIds":["binance-filters"],"risk":"medium"},{"id":"c3","text":"Binance publishes user-data stream documentation for order update events after account activity occurs.","sourceIds":["binance-trading-endpoints"],"risk":"medium"},{"id":"c4","text":"OKX publishes official place-order documentation under its order-book trading API.","sourceIds":["okx-place-order"],"risk":"medium"},{"id":"c5","text":"OKX publishes a separate close-positions route, so closing exposure should not be treated as identical to every ordinary order submission.","sourceIds":["okx-close-positions"],"risk":"low"},{"id":"c6","text":"The public documentation does not prove that a private account, symbol, region, margin mode, clock, balance or risk setting will accept a future production order.","sourceIds":["binance-trading-endpoints","binance-filters","okx-place-order","okx-close-positions"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-pre-check-order-api-risk-limit-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-08T03:04:00.000Z","updatedAt":"2026-10-08T03:04:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit Pre Check Order API: Risk-Limit Readiness Checklist","zh-Hans":"Bybit Pre Check Order API：风险限额就绪清单"},"summary":{"en":"Bybit's V5 pre-check route is useful only when it is placed in a larger evidence chain. The source-backed chain is instrument metadata, local order construction, pre-check response, live place-order response and post-action.","zh-Hans":"Bybit Pre Check Order API：风险限额就绪清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit publishes official documentation for a V5 pre-check-order route.","sourceIds":["bybit-pre-check-order"],"risk":"medium"},{"id":"c2","text":"Bybit publishes official V5 create-order documentation.","sourceIds":["bybit-create-order"],"risk":"medium"},{"id":"c3","text":"Bybit publishes official instruments-info documentation.","sourceIds":["bybit-instruments-info"],"risk":"medium"},{"id":"c4","text":"A pre-check response is different from a live order response.","sourceIds":["bybit-pre-check-order","bybit-create-order"],"risk":"medium"},{"id":"c5","text":"Instrument metadata is part of a safe order validation record because it shapes size, price and market assumptions.","sourceIds":["bybit-instruments-info"],"risk":"low"},{"id":"c6","text":"The public documentation does not prove future acceptance, fill result, account risk limit, liquidation handling or support outcome.","sourceIds":["bybit-pre-check-order","bybit-create-order","bybit-instruments-info"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-reduce-only-vs-okx-close-position-order-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-08T03:04:00.000Z","updatedAt":"2026-10-08T03:04:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit Reduce-Only vs OKX Close Position: Order-Control Boundary Map","zh-Hans":"Bybit Reduce-Only 与 OKX Close Position：订单控制边界图"},"summary":{"en":"Bybit's reduce-only order control and OKX's close-position route both sit near the same user goal: reducing or exiting exposure. They are not the same control.","zh-Hans":"Bybit Reduce-Only 与 OKX Close Position：订单控制边界图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit publishes official V5 create-order documentation for order submission parameters.","sourceIds":["bybit-create-order"],"risk":"medium"},{"id":"c2","text":"Bybit publishes a V5 pre-check-order route intended to check an order before order placement.","sourceIds":["bybit-pre-check-order"],"risk":"medium"},{"id":"c3","text":"Bybit publishes instruments-info documentation that exposes instrument and limit metadata used by integrations.","sourceIds":["bybit-instruments-info"],"risk":"medium"},{"id":"c4","text":"OKX publishes a close-positions route in its order-book trading API.","sourceIds":["okx-close-positions"],"risk":"medium"},{"id":"c5","text":"A reduce-only flag, an order pre-check and a close-position endpoint are different evidence objects.","sourceIds":["bybit-create-order","bybit-pre-check-order","okx-close-positions"],"risk":"low"},{"id":"c6","text":"The source set does not prove future fills, private margin availability, liquidation behavior, risk-limit upgrades or account-specific close outcomes.","sourceIds":["bybit-create-order","bybit-pre-check-order","bybit-instruments-info","okx-close-positions"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-create-bingx-account-complete-kyc-2fa-fund-password-withdrawal-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-08T03:04:00.000Z","updatedAt":"2026-10-08T03:04:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"How to Create a BingX Account, Complete KYC, Enable 2FA and Withdraw Safely","zh-Hans":"如何创建 BingX 账户、完成 KYC、启用 2FA 并安全提现"},"summary":{"en":"A safe BingX onboarding record should move in four separate steps: account access, identity verification, second-factor setup, fund-password control and a small withdrawal test only after the previous controls are confirmed.","zh-Hans":"安全的 BingX 入门记录应拆成四个独立步骤：账户访问、身份认证、二次验证、资金密码控制，以及只有在前面控制已确认后才做的小额提现测试。"},"claims":[{"id":"c1","text":"BingX publishes an official support article for completing identity verification.","sourceIds":["bingx-kyc"],"risk":"medium"},{"id":"c2","text":"BingX publishes an official support article for enabling Google Authenticator 2FA.","sourceIds":["bingx-google-authenticator"],"risk":"medium"},{"id":"c3","text":"BingX publishes an official support article for withdrawing crypto.","sourceIds":["bingx-withdraw"],"risk":"medium"},{"id":"c4","text":"BingX publishes an official support article for setting a fund password.","sourceIds":["bingx-fund-password"],"risk":"medium"},{"id":"c5","text":"KYC, authenticator setup, fund password and withdrawal are separate control surfaces.","sourceIds":["bingx-kyc","bingx-google-authenticator","bingx-withdraw","bingx-fund-password"],"risk":"low"},{"id":"c6","text":"The official support pages do not prove private eligibility, regional support, withdrawal approval, reward availability, tax treatment or support recovery.","sourceIds":["bingx-kyc","bingx-google-authenticator","bingx-withdraw","bingx-fund-password"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-convert-vs-kraken-instant-buy-quote-fee-spread-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-07T23:58:00.000Z","updatedAt":"2026-10-07T23:58:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Convert vs Kraken Instant Buy: Quote, Fee, Spread and Confirmation Controls","zh-Hans":"Binance Convert 与 Kraken Instant Buy：报价、费用、价差与确认控制"},"summary":{"en":"Binance Convert and Kraken Instant Buy solve a similar user job, but the control surface is not identical.","zh-Hans":"Binance Convert 与 Kraken Instant Buy 都服务于“快速换币”这个用户任务，但控制表面并不相同。"},"claims":[{"id":"c1","text":"Binance Convert documentation describes choosing assets, previewing a conversion quote and confirming the conversion.","sourceIds":["binance-convert-assets"],"risk":"medium"},{"id":"c2","text":"Binance Convert documentation says confirmed conversions are processed almost immediately and can be checked in Convert History.","sourceIds":["binance-convert-assets"],"risk":"medium"},{"id":"c3","text":"Binance's Convert blog describes the product as quote-based and distinct from a complex trading interface.","sourceIds":["binance-convert-blog"],"risk":"medium"},{"id":"c4","text":"Kraken says Instant Buy fees consist of a displayed fee and, where applicable, a spread included in the price.","sourceIds":["kraken-instant-buy-faq"],"risk":"medium"},{"id":"c5","text":"Kraken's fee page says Instant Buy/Sell service prices include a spread and that displayed confirmation fees are the fees incurred by clients.","sourceIds":["kraken-fee-schedule"],"risk":"low"},{"id":"c6","text":"Neither source set proves that a private account receives the same quote, funding method, spread, region or execution outcome in the future.","sourceIds":["binance-convert-assets","kraken-instant-buy-faq","kraken-fee-schedule"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"erc3643-vs-solana-transfer-hook-tokenized-asset-control-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-07T23:58:00.000Z","updatedAt":"2026-10-07T23:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"ERC-3643 vs Solana Transfer Hook: Tokenized-Asset Transfer Control Map","zh-Hans":"ERC-3643 与 Solana Transfer Hook：代币化资产转让控制地图"},"summary":{"en":"ERC-3643 and Solana Transfer Hook both affect token transfer control, but they are not interchangeable compliance proofs.","zh-Hans":"ERC-3643 与 Solana Transfer Hook：代币化资产转让控制地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"EIP-3643 describes a permissioned token standard whose transfer behavior differs from standard ERC-20 because of identity and compliance checks.","sourceIds":["erc3643-eip"],"risk":"medium"},{"id":"c2","text":"ERC-3643 documentation says its compliance framework can add rules for token offerings and transfers and relies on on-chain identity.","sourceIds":["erc3643-compliance"],"risk":"medium"},{"id":"c3","text":"Solana Transfer Hook documentation says the interface can execute custom instruction logic on every transfer for a specific mint account.","sourceIds":["solana-transfer-hook"],"risk":"medium"},{"id":"c4","text":"Solana transfer documentation distinguishes standard transfer instructions and Token Extension transfer variants.","sourceIds":["solana-token-transfer"],"risk":"medium"},{"id":"c5","text":"A transfer hook can enforce technical execution conditions without by itself proving legal ownership, investor status, redemption or secondary-market rights.","sourceIds":["solana-transfer-hook","erc3643-eip"],"risk":"low"},{"id":"c6","text":"A regulated-token compliance standard can define transfer eligibility without proving that every wallet, custodian or marketplace client will support the route.","sourceIds":["erc3643-compliance","solana-token-transfer"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-create-phemex-account-complete-kyc-2fa-withdrawal-whitelist-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-07T23:58:00.000Z","updatedAt":"2026-10-07T23:58:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"How to Create a Phemex Account, Complete KYC, Enable 2FA and Set Withdrawal Whitelist Safely","zh-Hans":"如何安全创建 Phemex 账户、完成 KYC、启用 2FA 并设置提现白名单"},"summary":{"en":"A safe Phemex onboarding flow is not only registration. Phemex help materials say identity verification uses issuing country, ID document and selfie verification; security guidance recommends binding 2FA after registration; and.","zh-Hans":"如何安全创建 Phemex 账户、完成 KYC、启用 2FA 并设置提现白名单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Phemex KYC guidance describes identity verification using issuing country, ID document and selfie verification steps.","sourceIds":["phemex-kyc-howto"],"risk":"medium"},{"id":"c2","text":"Phemex identity statement says users may need to provide identity proof and that ongoing monitoring or additional due diligence may be required.","sourceIds":["phemex-identity-statement"],"risk":"medium"},{"id":"c3","text":"Phemex security guidance recommends binding two-factor authentication after registration.","sourceIds":["phemex-security"],"risk":"medium"},{"id":"c4","text":"Phemex security guidance describes withdrawal whitelist and a new-address withdrawal lock as account-security controls.","sourceIds":["phemex-security"],"risk":"medium"},{"id":"c5","text":"Phemex withdrawal FAQ describes withdrawal confirmation, TXID checks and temporary withdrawal restrictions after certain account changes.","sourceIds":["phemex-withdrawal-faq"],"risk":"low"},{"id":"c6","text":"The official sources do not prove a private user's eligibility, regional availability, verification approval, withdrawal success, fee, tax treatment or support outcome.","sourceIds":["phemex-kyc-howto","phemex-security","phemex-withdrawal-faq"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"oecd-carf-xml-schema-exchange-reporting-readiness-map","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-07T23:58:00.000Z","updatedAt":"2026-10-07T23:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"OECD CARF XML Schema: Exchange Reporting Readiness Map","zh-Hans":"OECD CARF XML Schema：交易所报告准备度地图"},"summary":{"en":"The OECD CARF XML schema turns crypto-asset tax transparency from a policy headline into a data-readiness problem for reporting service providers and tax administrations.","zh-Hans":"OECD CARF XML Schema：交易所报告准备度地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"OECD describes CARF as designed to collect and automatically exchange information on transactions in relevant crypto-assets.","sourceIds":["oecd-carf-intro"],"risk":"medium"},{"id":"c2","text":"OECD describes CARF as including rules and commentary, a competent authority agreement and an electronic XML format.","sourceIds":["oecd-carf-intro"],"risk":"medium"},{"id":"c3","text":"OECD announced XML schemas and user guides for CARF and amended CRS to support transmission of information between tax authorities.","sourceIds":["oecd-carf-schema-announcement"],"risk":"medium"},{"id":"c4","text":"OECD schema materials say the XML schema can also be used for domestic reporting by Reporting Crypto-Asset Service Providers where domestic law permits.","sourceIds":["oecd-carf-schema-pdf"],"risk":"medium"},{"id":"c5","text":"CARF documentation does not by itself prove a specific exchange's user-facing tax report, jurisdictional filing status or private account classification.","sourceIds":["oecd-carf-schema-pdf","oecd-carf-monitoring"],"risk":"low"},{"id":"c6","text":"A public readiness article must avoid collecting or displaying private identity documents, tax identifiers, full transaction histories or balances.","sourceIds":["oecd-carf-schema-pdf"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"uniswap-v4-hooks-vs-solana-transfer-hook-integration-radar","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-07T23:58:00.000Z","updatedAt":"2026-10-07T23:58:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Uniswap v4 Hooks vs Solana Transfer Hook: Integration Failure Radar","zh-Hans":"Uniswap v4 Hooks 与 Solana Transfer Hook：集成失败雷达"},"summary":{"en":"Uniswap v4 hooks and Solana Transfer Hook both add programmable logic around swaps or transfers, but their integration risks surface in different places.","zh-Hans":"Uniswap v4 Hooks 与 Solana Transfer Hook：集成失败雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Uniswap v4 documentation says every pool can have one hook and hooks can intercept or modify execution flow at specific pool lifecycle points.","sourceIds":["uniswap-hooks-concepts"],"risk":"medium"},{"id":"c2","text":"Uniswap v4 documentation says hook permissions are encoded in the hook contract address and used by PoolManager.","sourceIds":["uniswap-hooks-concepts"],"risk":"medium"},{"id":"c3","text":"Solana Transfer Hook documentation says Transfer Hook can execute custom logic on every transfer for a specific mint.","sourceIds":["solana-transfer-hook"],"risk":"medium"},{"id":"c4","text":"Solana transfer documentation says Token Extension Program transfers prefer checked transfer variants and can add extension-specific behavior.","sourceIds":["solana-transfer-basics"],"risk":"medium"},{"id":"c5","text":"A hook-aware integration can fail because of address permissions, missing extra accounts, unsupported clients, simulation gaps or user-interface wording.","sourceIds":["uniswap-hooks-concepts","solana-transfer-hook"],"risk":"low"},{"id":"c6","text":"Public protocol documentation does not prove a specific wallet, router, exchange, custodian or app has implemented every hooked route safely.","sourceIds":["uniswap-hooks-start","solana-transfer-basics"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"chainlink-navlink-tokenized-fund-data-disclosure-radar","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-07T21:08:00.000Z","updatedAt":"2026-10-07T21:08:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Chainlink NAVLink and Tokenized Fund Data Disclosure Radar","zh-Hans":"Chainlink NAVLink 与代币化基金数据披露雷达"},"summary":{"en":"Chainlink's tokenized-fund materials make NAV data, reserve data and cross-system orchestration visible as infrastructure inputs, not as proof that any tokenized fund is suitable for every investor.","zh-Hans":"Chainlink NAVLink 与代币化基金数据披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Chainlink Data Feeds documentation describes price feeds, proof-of-reserve style data, NAV, AUM and multi-variable feed categories.","sourceIds":["chainlink-data-feeds"],"risk":"medium"},{"id":"c2","text":"Chainlink SmartData changelog describes onchain data offerings for tokenized assets, including NAV, AUM and collateral data.","sourceIds":["chainlink-smartdata-changelog"],"risk":"medium"},{"id":"c3","text":"Chainlink fund-tokenization material explains why tokenized fund workflows require NAV data and offchain-to-onchain data delivery.","sourceIds":["chainlink-fund-tokenization"],"risk":"medium"},{"id":"c4","text":"Chainlink tokenization interoperability material describes NAVLink as a pricing input for fund subscriptions and redemptions.","sourceIds":["chainlink-tokenization-interoperability"],"risk":"medium"},{"id":"c5","text":"The sources support an infrastructure-readiness checklist, not a claim that a specific fund is universally eligible or low risk.","sourceIds":["chainlink-data-feeds","chainlink-fund-tokenization","chainlink-tokenization-interoperability"],"risk":"low"},{"id":"c6","text":"A disclosure radar should separate data source, validator, oracle delivery, contract action, investor eligibility and fallback controls.","sourceIds":["chainlink-data-feeds","chainlink-smartdata-changelog","chainlink-fund-tokenization","chainlink-tokenization-interoperability"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-create-bitmart-account-complete-identity-verification-and-secure-withdrawals","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-07T21:08:00.000Z","updatedAt":"2026-10-07T21:08:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"How to Create a BitMart Account, Complete Identity Verification and Secure Withdrawals","zh-Hans":"如何创建 BitMart 账户、完成身份验证并安全设置提现"},"summary":{"en":"A BitMart onboarding checklist should stop at account setup, identity verification, two-factor authentication, official-channel checks and withdrawal readiness.","zh-Hans":"如何创建 BitMart 账户、完成身份验证并安全设置提现：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"BitMart support says identity verification can be completed from the website or BitMart app.","sourceIds":["bitmart-kyc"],"risk":"medium"},{"id":"c2","text":"BitMart support says users are required to complete identity verification before their first withdrawal.","sourceIds":["bitmart-kyc"],"risk":"medium"},{"id":"c3","text":"BitMart support documents adding two-factor authentication.","sourceIds":["bitmart-2fa"],"risk":"medium"},{"id":"c4","text":"BitMart security guidance warns users about phishing websites and credential requests.","sourceIds":["bitmart-security-warning"],"risk":"medium"},{"id":"c5","text":"BitMart states that staff will never ask for account password, Google Authenticator code, SMS verification code or email verification code.","sourceIds":["bitmart-security-warning"],"risk":"low"},{"id":"c6","text":"BitMart account-security material presents Google Authenticator and anti-phishing code as account-security controls.","sourceIds":["bitmart-account-security"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-websocket-token-deadman-switch-order-control-radar","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-07T21:08:00.000Z","updatedAt":"2026-10-07T21:08:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken WebSocket Token and Dead Man's Switch Order-Control Radar","zh-Hans":"Kraken WebSocket token 与 dead man's switch 订单控制雷达"},"summary":{"en":"Kraken order automation should separate WebSocket session control from dead man's switch protection. Kraken support documentation says authenticated WebSocket trading uses a token retrieved through GetWebSocketsToken and that the.","zh-Hans":"Kraken WebSocket token 与 dead man's switch 订单控制雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Kraken support documentation describes authenticated WebSocket trading through a token obtained from a REST token endpoint.","sourceIds":["kraken-ws-trading"],"risk":"medium"},{"id":"c2","text":"Kraken support documentation describes addOrder and cancelOrder messages over an authenticated WebSocket connection.","sourceIds":["kraken-ws-trading"],"risk":"medium"},{"id":"c3","text":"Kraken API key information documentation lists permissions including create-ws-token and order or trade permissions.","sourceIds":["kraken-api-key-info"],"risk":"medium"},{"id":"c4","text":"Kraken Futures documentation describes a dead man's switch endpoint that cancels orders after a timeout unless refreshed.","sourceIds":["kraken-deadman-switch"],"risk":"medium"},{"id":"c5","text":"Kraken Futures trade history provides a separate surface for checking recent trade history.","sourceIds":["kraken-futures-history"],"risk":"low"},{"id":"c6","text":"A radar should separate token acquisition, WebSocket command acknowledgement, dead-man timeout, state query and evidence hygiene.","sourceIds":["kraken-ws-trading","kraken-api-key-info","kraken-deadman-switch","kraken-futures-history"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-bybit-subaccount-api-permission-ip-binding-controls","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-07T21:08:00.000Z","updatedAt":"2026-10-07T21:08:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"OKX and Bybit Subaccount API Permission and IP Binding Controls","zh-Hans":"OKX 与 Bybit 子账户 API 权限和 IP 绑定控制"},"summary":{"en":"OKX and Bybit both document API permissions, subaccount boundaries and IP binding, but their control surfaces are not interchangeable.","zh-Hans":"OKX 与 Bybit 子账户 API 权限和 IP 绑定控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"OKX API documentation lists Read, Trade and Withdraw as API key permissions.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c2","text":"OKX API documentation says API keys can be linked to IP addresses and describes inactivity expiry behavior for unlinked trade or withdraw keys.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c3","text":"OKX help documentation explains creating API keys for main accounts and subaccounts.","sourceIds":["okx-subaccounts-faq"],"risk":"medium"},{"id":"c4","text":"Bybit API documentation describes creating a Sub UID API key with readOnly, ips and permissions parameters.","sourceIds":["bybit-create-sub-api"],"risk":"medium"},{"id":"c5","text":"Bybit documentation states that leaving ips unbound or using wildcard behavior has different validity consequences than binding IPs.","sourceIds":["bybit-create-sub-api"],"risk":"low"},{"id":"c6","text":"Bybit subaccount guidance describes API key creation from the subaccount management surface.","sourceIds":["bybit-subaccount-guide"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-innovation-exemption-tokenized-nms-stock-tsv-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-07T21:08:00.000Z","updatedAt":"2026-10-07T21:08:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Innovation Exemption, Tokenized NMS Stocks and TSV Risk Map","zh-Hans":"SEC Innovation Exemption、代币化 NMS 股票与 TSV 风险地图"},"summary":{"en":"The SEC's Innovation Exemption materials should be read as a conditional market-structure development, not as a blanket approval of every tokenized stock product.","zh-Hans":"SEC Innovation Exemption、代币化 NMS 股票与 TSV 风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"SEC Innovation Exemption statements describe temporary, conditional relief for limited trading of tokenized NMS stocks on Tokenized Securities Venues.","sourceIds":["sec-innovation-uyeda","sec-innovation-atkins"],"risk":"medium"},{"id":"c2","text":"SEC statements discuss permissioned trading, automated market makers or liquidity pools in the tokenized NMS stock context.","sourceIds":["sec-innovation-uyeda","sec-innovation-atkins"],"risk":"medium"},{"id":"c3","text":"SEC tokenized-securities staff statement explains that tokenized securities can have different structures and holder-rights models.","sourceIds":["sec-tokenized-securities"],"risk":"medium"},{"id":"c4","text":"SEC Crypto@SEC collects related tokenized securities and innovation-exemption materials.","sourceIds":["sec-crypto-topic"],"risk":"medium"},{"id":"c5","text":"The cited materials do not prove that an unrelated platform, token, venue or user's account is approved.","sourceIds":["sec-innovation-uyeda","sec-tokenized-securities"],"risk":"low"},{"id":"c6","text":"A risk map should separate regulatory source, venue scope, instrument eligibility, rights model, liquidity mechanism and exit condition.","sourceIds":["sec-innovation-uyeda","sec-innovation-atkins","sec-tokenized-securities","sec-crypto-topic"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-coinbase-stp-vs-self-trade-prevention-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-07T18:08:00.000Z","updatedAt":"2026-10-07T18:08:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs Coinbase Self-Trade Prevention and Order-State Controls","zh-Hans":"Binance 与 Coinbase 自成交防护和订单状态控制对比"},"summary":{"en":"Binance and Coinbase both document self-trade controls, but they expose different evidence surfaces. Binance Spot documentation defines STP modes, prevented matches, tradeGroupId behavior and prevented quantity fields.","zh-Hans":"Binance 与 Coinbase 自成交防护和订单状态控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance documentation defines STP as preventing a user's orders or tradeGroupId from matching against their own.","sourceIds":["binance-stp-faq"],"risk":"medium"},{"id":"c2","text":"Binance documentation describes STP modes, prevented matches and prevented quantity as order evidence surfaces.","sourceIds":["binance-stp-faq"],"risk":"medium"},{"id":"c3","text":"Binance trading endpoints are a separate source for order placement and order-state API behavior.","sourceIds":["binance-trade-rest"],"risk":"medium"},{"id":"c4","text":"Coinbase Drop Copy provides execution reports for orders placed through other FIX sessions or REST API.","sourceIds":["coinbase-drop-copy"],"risk":"medium"},{"id":"c5","text":"Coinbase Drop Copy documentation includes restated execution reports and SelfTradeType values connected to self-trade prevention.","sourceIds":["coinbase-drop-copy"],"risk":"low"},{"id":"c6","text":"Coinbase REST order lookup is a separate account-specific order-state confirmation surface.","sourceIds":["coinbase-get-order"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-websocket-level2-batch-channel-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-07T18:08:00.000Z","updatedAt":"2026-10-07T18:08:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase WebSocket Level2 Batch Channel Readiness Checklist","zh-Hans":"Coinbase WebSocket level2 batch 频道准备清单"},"summary":{"en":"Coinbase WebSocket readiness should be handled as a channel-specific evidence plan. Coinbase documentation separates the Exchange WebSocket overview from channel documentation, and the channel page is the source for level2 and.","zh-Hans":"Coinbase WebSocket level2 batch 频道准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Exchange WebSocket documentation describes the feed overview and connection surface.","sourceIds":["coinbase-ws-overview"],"risk":"medium"},{"id":"c2","text":"Coinbase channel documentation is the source for channel-specific subscriptions and payload expectations.","sourceIds":["coinbase-ws-channels"],"risk":"medium"},{"id":"c3","text":"Coinbase REST authentication documentation defines signed authenticated request material for private REST checks.","sourceIds":["coinbase-rest-auth"],"risk":"medium"},{"id":"c4","text":"Coinbase order lookup is a separate authenticated surface for account-specific order-state confirmation.","sourceIds":["coinbase-get-order"],"risk":"medium"},{"id":"c5","text":"A channel message alone is not a complete account audit after message gaps or disconnects.","sourceIds":["coinbase-ws-overview","coinbase-ws-channels","coinbase-get-order"],"risk":"low"},{"id":"c6","text":"A readiness checklist should separate channel purpose, ordering signal, connection behavior, REST confirmation and non-secret logging.","sourceIds":["coinbase-ws-overview","coinbase-ws-channels","coinbase-rest-auth","coinbase-get-order"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-digital-assets-vs-bis-stablecoin-trust-settlement-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-07T18:08:00.000Z","updatedAt":"2026-10-07T18:08:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Digital Assets vs BIS Stablecoin Trust: Settlement Readiness Map","zh-Hans":"DTCC 数字资产与 BIS 稳定币信任框架：结算准备度地图"},"summary":{"en":"DTCC and BIS materials point to different readiness questions for tokenized finance. DTCC describes digital-asset infrastructure that connects traditional market infrastructure with approved networks, lifecycle support,.","zh-Hans":"DTCC 数字资产与 BIS 稳定币信任框架：结算准备度地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"DTCC describes connecting established market infrastructure with emerging digital asset ecosystems.","sourceIds":["dtcc-digital-assets","dtcc-products-digital-assets"],"risk":"medium"},{"id":"c2","text":"DTCC says securities held at DTC can be represented as digital assets and used across approved networks while anchored to existing protections and resiliency.","sourceIds":["dtcc-digital-assets","dtcc-products-digital-assets"],"risk":"medium"},{"id":"c3","text":"DTCC lists governance, controls and auditable activity records as digital asset infrastructure themes.","sourceIds":["dtcc-digital-assets"],"risk":"medium"},{"id":"c4","text":"BIS Annual Economic Report 2026 discusses trust in money and innovation beyond stablecoins.","sourceIds":["bis-annual-economic-report-2026"],"risk":"medium"},{"id":"c5","text":"BIS frames stablecoins and tokenisation as monetary-system questions, not just technology questions.","sourceIds":["bis-annual-economic-report-2026"],"risk":"low"},{"id":"c6","text":"A readiness map should separate token representation, settlement asset, governance record, interoperability and policy boundary.","sourceIds":["dtcc-digital-assets","bis-annual-economic-report-2026"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fatf-2026-vasp-travel-rule-defi-stablecoin-action-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-07T18:08:00.000Z","updatedAt":"2026-10-07T18:08:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"FATF 2026 VASP, Travel Rule, DeFi and Stablecoin Action Map","zh-Hans":"FATF 2026 VASP、Travel Rule、DeFi 与稳定币行动地图"},"summary":{"en":"FATF's 2026 virtual-asset materials are useful as an action map, not as proof that any one exchange, stablecoin or DeFi route is approved.","zh-Hans":"FATF 2026 VASP、Travel Rule、DeFi 与稳定币行动地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"FATF's 2026 targeted update assesses implementation of standards for virtual assets and VASPs.","sourceIds":["fatf-2026-targeted-update"],"risk":"medium"},{"id":"c2","text":"FATF states that regulatory and implementation gaps remain despite progress in legislation and Travel Rule adoption.","sourceIds":["fatf-2026-targeted-update"],"risk":"medium"},{"id":"c3","text":"FATF's virtual-assets topic page points readers to 2026 virtual-asset implementation materials.","sourceIds":["fatf-virtual-assets-topic"],"risk":"medium"},{"id":"c4","text":"FATF's stablecoin and unhosted-wallet report frames illicit-finance risks around stablecoins and P2P activity via unhosted wallets.","sourceIds":["fatf-stablecoins-unhosted-wallets"],"risk":"medium"},{"id":"c5","text":"FATF's 2026 DeFi report frames regulatory challenges around DeFi arrangements and risk controls.","sourceIds":["fatf-defi-2026"],"risk":"low"},{"id":"c6","text":"A reader should treat FATF materials as a control checklist rather than as approval of a private product, exchange or route.","sourceIds":["fatf-2026-targeted-update","fatf-stablecoins-unhosted-wallets","fatf-defi-2026"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"uniswap-v4-hooks-permissioned-vs-pool-risk-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-07T18:08:00.000Z","updatedAt":"2026-10-07T18:08:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Uniswap v4 Hooks, Permissioned Logic and Pool-Risk Disclosure Radar","zh-Hans":"Uniswap v4 hooks、权限逻辑与池子风险披露雷达"},"summary":{"en":"Uniswap v4 makes pool logic more extensible through hooks, so a useful radar cannot stop at token pair, fee tier or TVL.","zh-Hans":"Uniswap v4 hooks、权限逻辑与池子风险披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Uniswap v4 documentation describes v4 as a protocol architecture with hooks and singleton-related design.","sourceIds":["uniswap-v4-overview"],"risk":"medium"},{"id":"c2","text":"Uniswap hooks documentation explains hook-based custom logic in the pool lifecycle.","sourceIds":["uniswap-v4-hooks"],"risk":"medium"},{"id":"c3","text":"Uniswap PoolManager documentation is a source for the core manager surface.","sourceIds":["uniswap-v4-poolmanager"],"risk":"medium"},{"id":"c4","text":"Uniswap create-pool documentation is a source for pool creation flow and developer context.","sourceIds":["uniswap-v4-quickstart"],"risk":"medium"},{"id":"c5","text":"A hook-enabled pool can require a different disclosure checklist than a simple token-pair comparison.","sourceIds":["uniswap-v4-overview","uniswap-v4-hooks"],"risk":"low"},{"id":"c6","text":"A radar should separate hook address, permission behavior, approval surface, route, warning, code evidence and stop rule.","sourceIds":["uniswap-v4-overview","uniswap-v4-hooks","uniswap-v4-poolmanager","uniswap-v4-quickstart"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"api-error-idempotency-retry-window-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-07T11:58:00.000Z","updatedAt":"2026-10-07T11:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange API Error, Idempotency and Retry-Window Disclosure Radar","zh-Hans":"加密交易所 API 错误、幂等性与重试窗口披露雷达"},"summary":{"en":"The radar finding is that exchange API documentation often describes pieces of retry safety in different places rather than as one complete control.","zh-Hans":"加密交易所 API 错误、幂等性与重试窗口披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Exchange order documentation exposes client order identity surfaces useful for cancel and reconciliation workflows.","sourceIds":["coinbase-cancel-order"],"risk":"medium"},{"id":"c2","text":"OKX API documentation describes request-deadline and rate-limit behavior in its technical guide.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c3","text":"Kraken WebSocket v2 order documentation is a source for order-entry request behavior on Kraken's WebSocket API.","sourceIds":["kraken-ws-add-order"],"risk":"medium"},{"id":"c4","text":"Binance Spot REST documentation describes signed request timing and request-security concepts.","sourceIds":["binance-spot-rest"],"risk":"medium"},{"id":"c5","text":"Binance account endpoints provide account and order-state evidence surfaces separate from the initial mutating request.","sourceIds":["binance-account-endpoints"],"risk":"low"},{"id":"c6","text":"A retry radar should separate idempotency, freshness, rate limits, acknowledgement and final state instead of treating a timeout as permission to repeat.","sourceIds":["coinbase-cancel-order","okx-api-guide","kraken-ws-add-order","binance-spot-rest","binance-account-endpoints"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"chainlink-smartdata-tokenized-asset-feed-risk-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-07T11:58:00.000Z","updatedAt":"2026-10-07T11:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Chainlink SmartData and Tokenized-Asset Feed Risk Map","zh-Hans":"Chainlink SmartData 与代币化资产数据源风险地图"},"summary":{"en":"Chainlink's tokenized-asset data pages are useful evidence for what oracle infrastructure can expose, but they do not prove that a specific tokenized asset is suitable, fully liquid or legally equivalent to an underlying security.","zh-Hans":"Chainlink SmartData 与代币化资产数据源风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Chainlink Data Feeds documentation describes feeds for asset prices, proof of reserves, NAV and interest rates.","sourceIds":["chainlink-data-feeds-docs"],"risk":"medium"},{"id":"c2","text":"Chainlink Data Streams documentation describes signed reports and tokenized-asset or SmartData stream categories.","sourceIds":["chainlink-data-streams-docs"],"risk":"medium"},{"id":"c3","text":"Chainlink Proof of Reserve materials describe reserve monitoring as an oracle-backed transparency and control surface.","sourceIds":["chainlink-proof-of-reserve"],"risk":"medium"},{"id":"c4","text":"Chainlink tokenization education material frames proof-of-reserve data as relevant to tokenized asset verification.","sourceIds":["chainlink-tokenization"],"risk":"medium"},{"id":"c5","text":"Chainlink tokenized-asset data material describes external data as necessary for useful blockchain-based assets.","sourceIds":["chainlink-data-tokenized-assets"],"risk":"low"},{"id":"c6","text":"Oracle documentation does not prove issuer rights, private-account eligibility, redemption access, legal equivalence or market liquidity for a specific tokenized product.","sourceIds":["chainlink-data-feeds-docs","chainlink-data-streams-docs","chainlink-proof-of-reserve"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-websocket-sequence-channel-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-07T11:58:00.000Z","updatedAt":"2026-10-07T11:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Exchange WebSocket Sequence and Channel Readiness Checklist","zh-Hans":"Coinbase Exchange WebSocket 序列与频道准备清单"},"summary":{"en":"Coinbase Exchange WebSocket readiness should be treated as a channel-by-channel evidence plan rather than a single connection test.","zh-Hans":"Coinbase Exchange WebSocket 序列与频道准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Exchange WebSocket documentation describes feed access and connection behavior for exchange data.","sourceIds":["coinbase-ws-overview"],"risk":"medium"},{"id":"c2","text":"Coinbase channel documentation provides channel-specific subscription and payload expectations.","sourceIds":["coinbase-ws-channels"],"risk":"medium"},{"id":"c3","text":"Coinbase REST authentication documentation defines signed authenticated request material for private REST checks.","sourceIds":["coinbase-exchange-auth"],"risk":"medium"},{"id":"c4","text":"Coinbase order REST documentation is a separate evidence surface for order-state review.","sourceIds":["coinbase-get-orders"],"risk":"medium"},{"id":"c5","text":"A WebSocket channel event is not a full account audit unless the integration reconciles final state after gaps or disconnects.","sourceIds":["coinbase-ws-overview","coinbase-ws-channels","coinbase-get-orders"],"risk":"low"},{"id":"c6","text":"A readiness checklist should separate requested channel, ordering signal, disconnect behavior, authenticated REST confirmation and non-secret logs.","sourceIds":["coinbase-ws-overview","coinbase-ws-channels","coinbase-exchange-auth","coinbase-get-orders"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-vs-coinbase-websocket-heartbeat-reconnect-order-state-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-07T11:58:00.000Z","updatedAt":"2026-10-07T11:58:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken vs Coinbase WebSocket Heartbeat, Reconnect and Order-State Controls","zh-Hans":"Kraken 与 Coinbase WebSocket 心跳、重连与订单状态控制对比"},"summary":{"en":"Kraken and Coinbase both expose WebSocket feeds that can support trading automation, but neither feed should be treated as a complete order-risk record on its own.","zh-Hans":"Kraken 与 Coinbase WebSocket 心跳、重连与订单状态控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Kraken documents WebSocket v2 as a separate API surface for public and private channels.","sourceIds":["kraken-ws-v2"],"risk":"medium"},{"id":"c2","text":"Kraken WebSocket v2 trading endpoints include add_order, so trading actions and market-data subscriptions should be reconciled separately.","sourceIds":["kraken-ws-add-order"],"risk":"medium"},{"id":"c3","text":"Kraken REST documentation provides a WebSockets token endpoint for authenticated WebSocket access.","sourceIds":["kraken-auth-token"],"risk":"medium"},{"id":"c4","text":"Coinbase Exchange WebSocket documentation describes feed connection behavior and channel subscriptions for exchange data.","sourceIds":["coinbase-ws-overview"],"risk":"medium"},{"id":"c5","text":"Coinbase channel documentation is a source for channel-specific payload expectations and sequence handling.","sourceIds":["coinbase-ws-channels"],"risk":"low"},{"id":"c6","text":"A safe comparison separates connection liveness, message order, reconnect behavior, authenticated scope and final order-state reconciliation.","sourceIds":["kraken-ws-v2","kraken-ws-add-order","coinbase-ws-overview","coinbase-ws-channels"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"project-pine-tokenised-collateral-liquidity-policy-map","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-07T11:58:00.000Z","updatedAt":"2026-10-07T11:58:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Project Pine Tokenised Collateral and Liquidity Policy Map","zh-Hans":"Project Pine 代币化抵押品与流动性政策地图"},"summary":{"en":"Project Pine is useful for tokenised-asset readers because it frames tokenisation as a central-bank operations experiment, not a retail asset endorsement.","zh-Hans":"Project Pine 代币化抵押品与流动性政策地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"BIS describes Project Pine as a joint research study with the New York Fed's New York Innovation Center and the BIS Innovation Hub Swiss Centre.","sourceIds":["bis-project-pine"],"risk":"medium"},{"id":"c2","text":"BIS says Project Pine explored central bank monetary policy operations in a tokenised wholesale-market setting.","sourceIds":["bis-project-pine"],"risk":"medium"},{"id":"c3","text":"The BIS project page marks Project Pine as concluded and research-oriented.","sourceIds":["bis-project-pine"],"risk":"medium"},{"id":"c4","text":"The Project Pine report is the primary report for prototype assumptions, architecture, smart contracts and testing.","sourceIds":["bis-project-pine-report"],"risk":"medium"},{"id":"c5","text":"BIS annual economic material discusses tokenised collateral and central-bank liquidity in a broader tokenised financial-system context.","sourceIds":["bis-aer-tokenised-system","bis-tokenisation-central-banks"],"risk":"low"},{"id":"c6","text":"A policy map should not convert a central-bank prototype into evidence that a private tokenised asset is approved, liquid or suitable.","sourceIds":["bis-project-pine","bis-project-pine-report","bis-aer-tokenised-system"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-bybit-self-trade-prevention-prevented-match-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-07T08:55:00.000Z","updatedAt":"2026-10-07T08:55:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs Bybit Self-Trade Prevention and Prevented-Match Controls","zh-Hans":"Binance 与 Bybit 自成交防护和阻止成交控制对比"},"summary":{"en":"Binance and Bybit both document self-trade prevention controls, but the operating evidence is not identical.","zh-Hans":"Binance 与 Bybit 自成交防护和阻止成交控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance Spot documentation describes Self Trade Prevention as a feature preventing a user or tradeGroupId from matching against itself.","sourceIds":["binance-stp-faq"],"risk":"medium"},{"id":"c2","text":"Binance Spot documentation uses selfTradePreventionMode to define what happens when an order could cause a self-trade.","sourceIds":["binance-stp-faq"],"risk":"medium"},{"id":"c3","text":"Binance account endpoints expose prevented-match evidence fields and account prevented-match queries for order review.","sourceIds":["binance-account-endpoints"],"risk":"medium"},{"id":"c4","text":"Bybit V5 documentation describes Self Match Prevention and smpType modes such as cancel taker, cancel maker and cancel both.","sourceIds":["bybit-smp"],"risk":"medium"},{"id":"c5","text":"Bybit create-order documentation exposes smpType as an order parameter, while cancel-order documentation defines the cancel surface separately.","sourceIds":["bybit-create-order","bybit-cancel-order"],"risk":"low"},{"id":"c6","text":"A safe comparison separates prevention configuration, account scope, cancellation consequence, prevented-match evidence and final order-state reconciliation.","sourceIds":["binance-stp-faq","binance-account-endpoints","bybit-smp","bybit-create-order"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-stablecoin-dollarisation-tokenised-deposit-policy-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-07T08:55:00.000Z","updatedAt":"2026-10-07T08:55:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Stablecoin Dollarisation and Tokenised-Deposit Policy Risk Map","zh-Hans":"BIS 稳定币美元化与代币化存款政策风险地图"},"summary":{"en":"BIS 2026 material makes stablecoin adoption a policy and settlement-asset question, not merely a wallet or payment-app feature.","zh-Hans":"BIS 2026 材料把稳定币采用视为政策和结算资产问题，而不只是钱包或支付应用功能。BIS 年度经济报告材料把代币化与央行货币锚联系起来，并提示，当外币稳定币替代本币时，可能产生货币和金融稳定问题。"},"claims":[{"id":"c1","text":"BIS Annual Economic Report 2026 material frames tokenisation within a central-bank-money anchored monetary architecture rather than a standalone private-token story.","sourceIds":["bis-annual-trust-money"],"risk":"medium"},{"id":"c2","text":"BIS material warns that foreign-currency stablecoin adoption can raise dollarisation and monetary-sovereignty concerns in some economies.","sourceIds":["bis-annual-trust-money","bis-stablecoins-deposits-speech"],"risk":"medium"},{"id":"c3","text":"The BIS August 2026 speech says stablecoins and tokenised deposits could coexist if roles are clearly delineated and safeguards are in place.","sourceIds":["bis-stablecoins-deposits-speech"],"risk":"medium"},{"id":"c4","text":"BIS Project Agorá explores wholesale cross-border payments using tokenised commercial bank deposits and tokenised central bank reserves on a shared programmable platform.","sourceIds":["bis-project-agora","bis-agora-report"],"risk":"medium"},{"id":"c5","text":"Project Agorá materials describe prototype and real-value testing context, not a universal retail payment service.","sourceIds":["bis-project-agora","bis-agora-report"],"risk":"low"},{"id":"c6","text":"A policy-risk map should classify the money claim, issuer, settlement anchor, participant type, jurisdiction and production status before drawing user conclusions.","sourceIds":["bis-annual-trust-money","bis-stablecoins-deposits-speech","bis-project-agora"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"blackrock-hkd-digital-liquidity-fund-tokenised-mmf-register-boundary","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-07T08:55:00.000Z","updatedAt":"2026-10-07T08:55:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"BlackRock HKD Digital Liquidity Fund and the Register Boundary for Tokenised MMFs","zh-Hans":"BlackRock 港元数字流动性基金与代币化货币市场基金登记边界"},"summary":{"en":"BlackRock’s HKD Digital Liquidity Fund announcement is useful RWA evidence because it keeps tokenised fund access inside regulated money-market-fund and register boundaries.","zh-Hans":"BlackRock 港元数字流动性基金与代币化货币市场基金登记边界：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"BlackRock announced regulatory authorization for a Hong Kong-domiciled HKD Digital Liquidity Fund designed to operate across traditional and digital financial channels.","sourceIds":["blackrock-hkd-dlf"],"risk":"medium"},{"id":"c2","text":"BlackRock says the fund builds on participation in HKMA Project Ensemble tokenisation work in Hong Kong.","sourceIds":["blackrock-hkd-dlf","hkma-project-ensemble"],"risk":"medium"},{"id":"c3","text":"BlackRock tokenised-MMF material says participation is limited to KYC/AML-approved investors using approved wallets.","sourceIds":["blackrock-tokenised-mmf"],"risk":"medium"},{"id":"c4","text":"BlackRock tokenised-MMF material says the shareholder register remains the official record of ownership.","sourceIds":["blackrock-tokenised-mmf"],"risk":"medium"},{"id":"c5","text":"HKMA Project Ensemble materials describe a sandbox for tokenisation use cases including tokenised deposits and settlement-related experimentation.","sourceIds":["hkma-project-ensemble"],"risk":"low"},{"id":"c6","text":"A tokenised money-market-fund analysis should distinguish official register, investor eligibility, wallet approval, fund risk and redemption terms from generic token transferability.","sourceIds":["blackrock-hkd-dlf","blackrock-tokenised-mmf","hkma-project-ensemble"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-self-match-prevention-smp-type-order-history-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-07T08:55:00.000Z","updatedAt":"2026-10-07T08:55:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit Self Match Prevention: smpType and Order-History Readiness Checklist","zh-Hans":"Bybit Self Match Prevention：smpType 与订单历史准备清单"},"summary":{"en":"Bybit Self Match Prevention should be treated as an order-lifecycle control, not a label that proves a strategy is safe.","zh-Hans":"Bybit Self Match Prevention 应被视为订单生命周期控制，而不是证明策略安全的标签。Bybit V5 文档通过下单时选择的执行方式解释 SMP，create-order 文档也把 smpType 暴露为请求参数。"},"claims":[{"id":"c1","text":"Bybit V5 documentation describes Self Match Prevention as a function where users can choose an execution method when placing an order.","sourceIds":["bybit-smp"],"risk":"medium"},{"id":"c2","text":"Bybit create-order documentation exposes smpType as part of the order request surface.","sourceIds":["bybit-create-order"],"risk":"medium"},{"id":"c3","text":"Bybit cancel-order documentation defines cancellation separately from SMP configuration.","sourceIds":["bybit-cancel-order"],"risk":"medium"},{"id":"c4","text":"Bybit order-history documentation is the evidence surface for reviewing final order lifecycle state after a prevention or cancellation event.","sourceIds":["bybit-order-history"],"risk":"medium"},{"id":"c5","text":"Bybit V5 changelog material records API field changes over time, so integrations should verify current response fields instead of relying on old wrappers.","sourceIds":["bybit-v5-changelog"],"risk":"low"},{"id":"c6","text":"A Bybit SMP runbook should separate requested mode, accepted order, cancel result, order-history state and non-secret audit log.","sourceIds":["bybit-smp","bybit-create-order","bybit-cancel-order","bybit-order-history"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-order-final-state-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-07T08:55:00.000Z","updatedAt":"2026-10-07T08:55:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange Order Final-State Disclosure Radar","zh-Hans":"加密交易所订单最终状态披露雷达"},"summary":{"en":"NexuAlpha’s current order-finality radar treats exchange order APIs as reconciliation surfaces rather than execution promises.","zh-Hans":"加密交易所订单最终状态披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance account endpoints provide account-level order and prevented-match evidence surfaces for Spot API review.","sourceIds":["binance-account-endpoints"],"risk":"medium"},{"id":"c2","text":"OKX API v5 documentation describes private order management and WebSocket order-state confirmation patterns inside a broad API guide.","sourceIds":["okx-api-docs"],"risk":"medium"},{"id":"c3","text":"Kraken REST documentation includes an order-info endpoint for querying order details.","sourceIds":["kraken-orders-info"],"risk":"medium"},{"id":"c4","text":"Bybit V5 documentation includes order-history and cancellation endpoints as separate lifecycle evidence surfaces.","sourceIds":["bybit-order-history","bybit-cancel-order"],"risk":"medium"},{"id":"c5","text":"Order finality cannot be inferred from a local timeout, local queue state or a single cancellation attempt without a venue-side state check.","sourceIds":["binance-account-endpoints","okx-api-docs","kraken-orders-info","bybit-order-history"],"risk":"low"},{"id":"c6","text":"A radar-quality order runbook must preserve source URL, endpoint, request class, order id, final state, fill check and stop rule without logging credentials.","sourceIds":["binance-account-endpoints","okx-api-docs","kraken-orders-info","bybit-order-history"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-vs-okx-api-cancel-deadline-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-07T05:55:00.000Z","updatedAt":"2026-10-07T05:55:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase vs OKX API Cancel, Client Order ID and Deadline Controls","zh-Hans":"Coinbase 与 OKX API 撤单、客户端订单 ID 与截止时间控制对比"},"summary":{"en":"Coinbase and OKX both expose controls that matter after an automated order is submitted, but they frame the controls differently.","zh-Hans":"Coinbase 与 OKX API 撤单、客户端订单 ID 与截止时间控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Exchange API documentation says the cancel order endpoint cancels a single open order by id and may also use a client assigned client_oid with a client: namespace.","sourceIds":["coinbase-cancel-order"],"risk":"medium"},{"id":"c2","text":"Coinbase documentation says the cancel order endpoint requires the trade permission and recommends specifying product_id to prevent a race condition when canceling an order.","sourceIds":["coinbase-cancel-order"],"risk":"medium"},{"id":"c3","text":"Coinbase Exchange REST authentication documentation describes API key, passphrase, signature and timestamp headers for authenticated requests.","sourceIds":["coinbase-exchange-auth"],"risk":"medium"},{"id":"c4","text":"OKX API documentation describes expTime as a supported request effective deadline for order and amend flows.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c5","text":"OKX API documentation says rate-limit rejection returns error code 50011 and that private REST and WebSocket order-management limits are based on User ID.","sourceIds":["okx-api-guide"],"risk":"low"},{"id":"c6","text":"A safe venue comparison separates cancel identifier, API permission, deadline or freshness control, rate-limit owner, acknowledgement and final order-state reconciliation.","sourceIds":["coinbase-cancel-order","coinbase-exchange-auth","okx-api-guide","okx-api-agreement"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"deribit-heartbeat-cancel-on-disconnect-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-07T05:55:00.000Z","updatedAt":"2026-10-07T05:55:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Deribit Heartbeat and Cancel-on-Disconnect Readiness Checklist","zh-Hans":"Deribit 心跳与断线撤单准备清单"},"summary":{"en":"Deribit documentation makes connection liveness an order-risk control rather than a background networking detail.","zh-Hans":"Deribit 心跳与断线撤单准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Deribit public API documentation describes setheartbeat as a WebSocket-only endpoint that sends heartbeat and test_request messages.","sourceIds":["deribit-public-api"],"risk":"medium"},{"id":"c2","text":"Deribit public API documentation says software should respond to test_request messages and that the API server closes the connection if the software fails to do so.","sourceIds":["deribit-public-api"],"risk":"medium"},{"id":"c3","text":"Deribit public API documentation says orders opened over the connection will be cancelled if the account is configured to cancel on disconnect.","sourceIds":["deribit-public-api"],"risk":"medium"},{"id":"c4","text":"Deribit FIX API documentation describes a CancelOnDisconnect Logon tag that controls Close on Disconnect, with account defaults used when the tag is not provided.","sourceIds":["deribit-fix-api"],"risk":"medium"},{"id":"c5","text":"Deribit HTTP API documentation separately lists private cancel behavior, so explicit cancels and disconnect-triggered cancels should not be treated as the same control.","sourceIds":["deribit-http-api","deribit-fix-api"],"risk":"low"},{"id":"c6","text":"A venue update does not prove a private account's cancel-on-disconnect default, FIX entitlement, order scope or session behavior without account-specific testing.","sourceIds":["deribit-public-api","deribit-fix-api","deribit-http-api"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fsb-2026-crypto-work-programme-implementation-gap-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-07T05:55:00.000Z","updatedAt":"2026-10-07T05:55:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"FSB 2026 Crypto Work Programme and Implementation Gap Map","zh-Hans":"FSB 2026 加密工作计划与实施缺口地图"},"summary":{"en":"FSB crypto work remains a policy-implementation story rather than a single new trading rule. The FSB crypto-assets policy area lists the 2026 work programme and recent regional consultative group activity, while the FSB.","zh-Hans":"FSB 2026 加密工作计划与实施缺口地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"FSB's crypto policy area lists a 2026 work programme and crypto-related regional consultative group activity.","sourceIds":["fsb-policy-area-crypto"],"risk":"medium"},{"id":"c2","text":"FSB says the G20 charged it with coordinating delivery of an effective and comprehensive regulatory framework for crypto-assets.","sourceIds":["fsb-crypto-global-stablecoins"],"risk":"medium"},{"id":"c3","text":"FSB's crypto-assets and global stablecoins page keeps the 2023 crypto-asset and global-stablecoin recommendations as key reference documents.","sourceIds":["fsb-crypto-global-stablecoins"],"risk":"medium"},{"id":"c4","text":"FSB material says implementation progress is welcome but gaps and inconsistencies remain.","sourceIds":["fsb-policy-area-crypto","fsb-thematic-review-pdf"],"risk":"medium"},{"id":"c5","text":"AMF says FSB and IOSCO published reports assessing implementation of recommendations on crypto-asset and stablecoin activities.","sourceIds":["amf-fsb-iosco-implementation"],"risk":"low"},{"id":"c6","text":"A global policy implementation map does not prove that a specific user, account, stablecoin, venue or jurisdiction has a final binding permission.","sourceIds":["fsb-policy-area-crypto","fsb-crypto-global-stablecoins","amf-fsb-iosco-implementation"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-create-osl-account-complete-verification-and-set-2fa-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-07T05:55:00.000Z","updatedAt":"2026-10-07T05:55:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"How to Create an OSL Account, Complete Verification and Set 2FA Safely","zh-Hans":"如何安全创建 OSL 账户、完成认证并设置 2FA"},"summary":{"en":"An OSL onboarding checklist should treat registration, identity verification, bank verification and 2FA as separate evidence gates.","zh-Hans":"OSL 开户清单应把注册、身份认证、银行验证与 2FA 当作相互独立的证据门。OSL 支持材料描述了通过邮箱和密码创建账户；认证流程包括手机号、身份证件、人脸识别、个人信息、住址证明、数字资产知识测评、签名与银行验证；2FA 设置可通过认证器应用或支持的安全密钥完成。"},"claims":[{"id":"c1","text":"OSL support says registration includes visiting the official website or app, signing up, entering an email address, setting a password, entering an email verification code and completing identity verification to start trading.","sourceIds":["osl-register-login"],"risk":"medium"},{"id":"c2","text":"OSL account verification guidance describes mobile-number verification, identity document and facial recognition, personal information, proof of address, background and wealth information, digital asset knowledge assessment, signature submission and bank verification steps.","sourceIds":["osl-account-verification"],"risk":"medium"},{"id":"c3","text":"OSL support says 2FA setup uses an authenticator app flow and also describes YubiKey support as an optional path.","sourceIds":["osl-2fa"],"risk":"medium"},{"id":"c4","text":"OSL wallet-address guidance describes address verification steps and 2FA/name/signature controls for adding or verifying wallet addresses.","sourceIds":["osl-wallet-address"],"risk":"medium"},{"id":"c5","text":"The SFC publishes lists of virtual asset trading platform operators, which should be checked separately from an individual account onboarding flow.","sourceIds":["sfc-vatp-list"],"risk":"low"},{"id":"c6","text":"A registration tutorial must not collect credentials, identity documents, tax data, one-time codes, private keys, recovery phrases or wallet seed phrases.","sourceIds":["osl-register-login","osl-account-verification","osl-2fa","osl-wallet-address"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"uk-wholesale-tokenised-markets-settlement-readiness-map","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-07T05:55:00.000Z","updatedAt":"2026-10-07T05:55:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"UK Wholesale Tokenised Markets Settlement Readiness Map","zh-Hans":"英国批发代币化市场结算准备度地图"},"summary":{"en":"Wholesale tokenised-market work is moving from concept papers into policy and industry-readiness frameworks, but the evidence still does not turn a tokenised fund or settlement pilot into a retail access promise.","zh-Hans":"英国批发代币化市场结算准备度地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"GOV.UK published a Wholesale Digital Markets Champion first report that frames steps toward a tokenised wholesale financial markets system.","sourceIds":["govuk-wholesale-digital-markets"],"risk":"medium"},{"id":"c2","text":"MAS says tokenisation in financial services can support direct exchange of tokenised financial assets on programmable platforms and describes Project Guardian work on GL1, industry frameworks and settlement facilities.","sourceIds":["mas-tokenisation-pathways"],"risk":"medium"},{"id":"c3","text":"MAS says Project Guardian focuses include open interoperable networks, trust anchors, asset tokenisation and institutional-grade DeFi protocols.","sourceIds":["mas-project-guardian-live"],"risk":"medium"},{"id":"c4","text":"BIS-CPMI says token arrangements can change market structures, but safety and efficiency benefits require sound governance and risk management.","sourceIds":["bis-cpmi-tokenisation"],"risk":"medium"},{"id":"c5","text":"BIS material identifies settlement assets, third-party reliance, liquidity and governance as tokenisation risk areas that can resemble traditional finance but materialise differently.","sourceIds":["bis-fsi-tokenisation-stability","bis-cpmi-tokenisation"],"risk":"low"},{"id":"c6","text":"A tokenisation policy or pilot source does not prove retail availability, fund suitability, legal ownership, redemption rights, tax result or exchange listing support.","sourceIds":["govuk-wholesale-digital-markets","mas-tokenisation-pathways","mas-project-guardian-live","bis-cpmi-tokenisation"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"api-effective-deadline-retry-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-07T02:55:00.000Z","updatedAt":"2026-10-07T02:55:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto API Effective Deadline and Retry Replay Disclosure Radar","zh-Hans":"加密 API 有效截止时间与重试重放披露雷达"},"summary":{"en":"NexuAlpha radar treats request freshness as a disclosure field, not a hidden implementation detail. Binance documentation exposes signed-request security and response weight headers, OKX documents expTime and rate-limit code.","zh-Hans":"加密 API 有效截止时间与重试重放披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance Spot REST documentation says responses include used-weight headers for rate limiters and describes request security for secure endpoints.","sourceIds":["binance-spot-rest"],"risk":"medium"},{"id":"c2","text":"OKX documentation describes expTime for supported order requests and rate-limit rejection code 50011.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c3","text":"Kraken support says nonce is required for authenticated Spot REST API calls.","sourceIds":["kraken-nonce"],"risk":"medium"},{"id":"c4","text":"Coinbase Advanced Trade documentation presents REST and WebSocket APIs for programmatic trading and order management.","sourceIds":["coinbase-advanced-overview"],"risk":"medium"},{"id":"c5","text":"Freshness controls and client order identifiers reduce retry ambiguity only when final state is reconciled after a timeout or disconnect.","sourceIds":["binance-spot-rest","okx-api-guide","kraken-nonce","coinbase-advanced-overview"],"risk":"low"},{"id":"c6","text":"A local bot log cannot prove a venue-side order outcome unless it is tied to a non-secret official response or subsequent status query.","sourceIds":["binance-spot-rest","okx-api-guide","kraken-nonce","coinbase-advanced-overview"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-kraken-api-permission-nonce-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-07T02:55:00.000Z","updatedAt":"2026-10-07T02:55:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs Kraken API Permission, Nonce and IP Allowlist Controls","zh-Hans":"Binance 与 Kraken API 权限、Nonce 与 IP 白名单控制对比"},"summary":{"en":"Binance and Kraken both protect authenticated exchange actions, but the control model is not identical.","zh-Hans":"Binance 与 Kraken API 权限、Nonce 与 IP 白名单控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance Spot REST documentation says each endpoint has a security type that indicates required API-key permissions and that non-NONE secure endpoints are SIGNED requests.","sourceIds":["binance-spot-rest"],"risk":"medium"},{"id":"c2","text":"Binance Spot REST documentation says API keys can be configured for specific secure endpoint types and that an API key cannot trade by default.","sourceIds":["binance-spot-rest"],"risk":"medium"},{"id":"c3","text":"Binance support says adding IP access restrictions is mandatory to enable withdrawal permission.","sourceIds":["binance-api-key-faq"],"risk":"medium"},{"id":"c4","text":"Kraken support says a nonce is required for authenticated Spot REST API calls, including account, funding and trading endpoints.","sourceIds":["kraken-nonce"],"risk":"medium"},{"id":"c5","text":"Kraken API-key security material warns that keys should use minimal permissions and that key material can permit sensitive actions.","sourceIds":["kraken-api-security","kraken-create-key"],"risk":"low"},{"id":"c6","text":"A safe exchange-API comparison separates permission scope, signature input, nonce or timestamp freshness, IP allowlist, withdrawal boundary and post-action reconciliation.","sourceIds":["binance-spot-rest","binance-api-key-faq","kraken-nonce","kraken-api-security"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fatf-stablecoin-unhosted-wallet-control-action-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-07T02:55:00.000Z","updatedAt":"2026-10-07T02:55:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"FATF Stablecoin, Unhosted Wallet and Offshore VASP Control Action Map","zh-Hans":"FATF 稳定币、非托管钱包与离岸 VASP 控制行动图"},"summary":{"en":"FATF material makes stablecoin and wallet routing a counterparty-control problem rather than a generic crypto label.","zh-Hans":"FATF 稳定币、非托管钱包与离岸 VASP 控制行动图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"FATF describes P2P transactions via unhosted wallets as transactions that can occur without a regulated intermediary VASP or financial institution.","sourceIds":["fatf-stablecoins-unhosted"],"risk":"medium"},{"id":"c2","text":"FATF highlights that stablecoin issuers may face difficulties controlling cross-chain activities that can fall outside counter-illicit-finance controls.","sourceIds":["fatf-stablecoins-unhosted"],"risk":"medium"},{"id":"c3","text":"FATF reports that stablecoins exceeded 250 in circulation by mid-2025 and had market capitalisation exceeding USD 300 billion in the stablecoin and unhosted-wallet report.","sourceIds":["fatf-stablecoins-unhosted"],"risk":"medium"},{"id":"c4","text":"FATF offshore-VASP material frames oversight gaps around offshore VASPs as exploitable blind spots.","sourceIds":["fatf-offshore-vasps"],"risk":"medium"},{"id":"c5","text":"FATF DeFi material frames qualifying DeFi arrangements and implementation of Recommendation 15 as ongoing regulatory challenges.","sourceIds":["fatf-defi-2026","fatf-2025-va-vasp-update"],"risk":"low"},{"id":"c6","text":"A policy report does not prove a specific wallet route, exchange account or stablecoin transfer is compliant, recoverable or low risk.","sourceIds":["fatf-stablecoins-unhosted","fatf-offshore-vasps","fatf-defi-2026"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-use-balancer-swap-pool-join-wallet-controls-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-07T02:55:00.000Z","updatedAt":"2026-10-07T02:55:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"How to Use Balancer Swap and Pool Join Wallet Controls Safely","zh-Hans":"如何安全使用 Balancer 兑换与加入池子的 Wallet 控制"},"summary":{"en":"Balancer onboarding should be treated as wallet and pool-control verification, not account registration.","zh-Hans":"如何安全使用 Balancer 兑换与加入池子的 Wallet 控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Balancer documentation describes Balancer as a programmable AMM and lists integration guides for swaps and liquidity operations.","sourceIds":["balancer-docs-home"],"risk":"medium"},{"id":"c2","text":"Balancer pool-join documentation recommends queryJoin to estimate BPT received and accounting for possible slippage.","sourceIds":["balancer-pool-joins"],"risk":"medium"},{"id":"c3","text":"Balancer pool-join documentation says thresholds matter because token amounts can change between transaction submission and execution.","sourceIds":["balancer-pool-joins"],"risk":"medium"},{"id":"c4","text":"Balancer relayer documentation says relayers must be authorized by the Balancer DAO and each user must opt in.","sourceIds":["balancer-relayers"],"risk":"medium"},{"id":"c5","text":"Balancer relayer documentation warns that relayers have access to Vault token approvals and should be approved with extreme care.","sourceIds":["balancer-relayers"],"risk":"low"},{"id":"c6","text":"A DEX wallet tutorial cannot prove a selected pool, token, chain, router, relayer or user wallet is safe or profitable.","sourceIds":["balancer-docs-home","balancer-pool-joins","balancer-relayers"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-exp-time-rate-limit-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-07T02:55:00.000Z","updatedAt":"2026-10-07T02:55:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"OKX expTime and Rate Limit Readiness Checklist","zh-Hans":"OKX expTime 与速率限制准备清单"},"summary":{"en":"OKX API documentation turns order timeout handling into an explicit request-control decision. The current API guide describes an optional expTime request header for place-order and amend-order calls so a request can be discarded.","zh-Hans":"OKX expTime 与速率限制准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"OKX documentation describes transaction timeouts and says expTime can be used as a request effective deadline for supported order and amend requests.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c2","text":"OKX documentation says a request rejected due to rate limits returns error code 50011.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c3","text":"OKX documentation says public unauthenticated REST rate limits are based on IP address.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c4","text":"OKX documentation says private REST and WebSocket order-management rate limits are based on User ID, with sub-accounts having individual User IDs.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c5","text":"OKX API Agreement points users to the OKX API documentation for endpoints, rate limits, authentication requirements and data schemas.","sourceIds":["okx-api-agreement"],"risk":"low"},{"id":"c6","text":"A venue update does not prove a private account has access to the endpoint, rate tier, product, region or sub-account mode.","sourceIds":["okx-api-guide","okx-api-agreement","nexualpha-source-registry"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cftc-tokenized-collateral-pilot-btc-eth-usdc-guardrails-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-07T00:09:00.000Z","updatedAt":"2026-10-07T00:09:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC Tokenized Collateral Pilot: BTC, ETH, USDC and Guardrails Map","zh-Hans":"CFTC 代币化抵押品试点：BTC、ETH、USDC 与护栏地图"},"summary":{"en":"The CFTC's tokenized collateral pilot is best read as a derivatives-market guardrail map, not a general endorsement of every tokenized asset.","zh-Hans":"CFTC 代币化抵押品试点：BTC、ETH、USDC 与护栏地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"The CFTC announced a digital assets pilot program for certain digital assets, including BTC, ETH and USDC, to be used as collateral in derivatives markets.","sourceIds":["cftc-pilot"],"risk":"medium"},{"id":"c2","text":"The CFTC release says its divisions issued guidance on tokenized assets as collateral in the trading of futures and swaps.","sourceIds":["cftc-pilot"],"risk":"medium"},{"id":"c3","text":"The CFTC release says the guidance applies to tokenized real-world assets including U.S. Treasury securities and money market funds.","sourceIds":["cftc-pilot"],"risk":"medium"},{"id":"c4","text":"The CFTC release identifies legal enforceability, segregation, custody and control, haircuts, valuation and operational risks as topics.","sourceIds":["cftc-pilot"],"risk":"medium"},{"id":"c5","text":"The CFTC release says the initial three-month period under the no-action position limits acceptable digital assets to bitcoin, ether and USDC.","sourceIds":["cftc-pilot"],"risk":"low"},{"id":"c6","text":"SEC staff statements describe tokenized securities as securities-form financial instruments and keep securities-law analysis separate from derivatives-collateral pilot claims.","sourceIds":["sec-tokenized-securities","sec-crypto-topic"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-api-role-based-access-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-07T00:09:00.000Z","updatedAt":"2026-10-07T00:09:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto API Role-Based Access Disclosure Radar","zh-Hans":"加密 API 基于角色的访问披露雷达"},"summary":{"en":"The disclosure gap in crypto API documentation is often not whether an exchange offers an API, but whether a builder can prove the smallest role, permission, withdrawal boundary and cancel authority before connecting automation.","zh-Hans":"加密 API 基于角色的访问披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Gemini roles documentation says role-based access control enforces least-privilege permissions across API keys.","sourceIds":["gemini-roles"],"risk":"medium"},{"id":"c2","text":"Gemini roles documentation says roles can grant trading capabilities, restrict withdrawal permissions to treasury systems and limit monitoring tools to read-only access.","sourceIds":["gemini-roles"],"risk":"medium"},{"id":"c3","text":"Coinbase API-key guidance describes permission levels and recommends secure credential storage outside the code base.","sourceIds":["coinbase-auth"],"risk":"medium"},{"id":"c4","text":"Kraken cancel-all documentation ties cancel-all behavior to order creation or cancel-close order permissions.","sourceIds":["kraken-cancel-all"],"risk":"medium"},{"id":"c5","text":"The NexuAlpha crypto radar rules require official or institutional evidence before factual publication and reject guaranteed safety, rewards or investment outcomes.","sourceIds":["nexualpha-radar"],"risk":"low"},{"id":"c6","text":"A role-based access radar should not treat an endpoint list as proof that a private account is eligible or that automation is safe.","sourceIds":["gemini-roles","coinbase-auth","kraken-cancel-all","nexualpha-radar"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"gemini-api-require-heartbeat-session-cancel-readiness-checklist","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-07T00:09:00.000Z","updatedAt":"2026-10-07T00:09:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Gemini API Require Heartbeat and Cancel All Session Orders Checklist","zh-Hans":"Gemini API Require Heartbeat 与会话撤单检查清单"},"summary":{"en":"Gemini's order documentation makes heartbeat and session cancellation an integration-control topic, not just an endpoint list.","zh-Hans":"Gemini API Require Heartbeat 与会话撤单检查清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Gemini order documentation lists order placement and management endpoints including create new order, cancel order, cancel all active orders, cancel all session orders and heartbeat.","sourceIds":["gemini-orders"],"risk":"medium"},{"id":"c2","text":"Gemini order documentation says cancel all session orders cancels orders opened by the current session and has the same effect as heartbeat expiration when Require Heartbeat is selected.","sourceIds":["gemini-orders"],"risk":"medium"},{"id":"c3","text":"Gemini order documentation says cancel all active orders cancels outstanding orders created by all sessions owned by the account, including interactive UI orders.","sourceIds":["gemini-orders"],"risk":"medium"},{"id":"c4","text":"Gemini roles documentation says API keys use roles and that calls without a required role return HTTP 403 with reason MissingRole.","sourceIds":["gemini-roles"],"risk":"medium"},{"id":"c5","text":"Gemini API-key authentication documentation says private REST API requests require API key, payload and signature headers.","sourceIds":["gemini-auth"],"risk":"low"},{"id":"c6","text":"A NexuAlpha source-backed venue update must keep official source boundaries separate from user eligibility, trading outcome or commercial claims.","sourceIds":["nexualpha-source-registry","gemini-orders","gemini-roles"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"gemini-vs-coinbase-order-preview-cancel-session-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-07T00:09:00.000Z","updatedAt":"2026-10-07T00:09:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"Gemini vs Coinbase Order Preview and Cancel Session Controls","zh-Hans":"Gemini 与 Coinbase 订单预览和会话撤单控制对比"},"summary":{"en":"Gemini and Coinbase expose different order-safety controls, so the useful decision is which failure mode the integration must prove first.","zh-Hans":"Gemini 与 Coinbase 订单预览和会话撤单控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Gemini documentation says role-based access control is used to enforce least-privilege permissions across API keys.","sourceIds":["gemini-roles"],"risk":"medium"},{"id":"c2","text":"Gemini API-key authentication documentation says private REST requests use API key pairs and HMAC-SHA384 signatures over Base64-encoded payload headers.","sourceIds":["gemini-auth"],"risk":"medium"},{"id":"c3","text":"Gemini order documentation describes endpoints for creating an order, canceling one order, canceling all active orders and canceling all session orders.","sourceIds":["gemini-orders"],"risk":"medium"},{"id":"c4","text":"Gemini order documentation says cancel all active orders can cancel outstanding orders created by all sessions owned by the account, including UI orders.","sourceIds":["gemini-orders"],"risk":"medium"},{"id":"c5","text":"Coinbase documentation lists Advanced Trade private endpoints that include create order, cancel orders, list orders, list fills, get order and preview orders.","sourceIds":["coinbase-endpoints","coinbase-auth"],"risk":"low"},{"id":"c6","text":"A responsible integration comparison separates preview, session cancel scope, all-account cancel scope, key role, signing requirement, final state and non-secret reconciliation evidence.","sourceIds":["gemini-roles","gemini-auth","gemini-orders","coinbase-endpoints","coinbase-auth"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-gemini-api-key-roles-and-session-cancel-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-07T00:09:00.000Z","updatedAt":"2026-10-07T00:09:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up Gemini API Key Roles and Session Cancel Controls Safely","zh-Hans":"如何安全设置 Gemini API Key Roles 与会话撤单控制"},"summary":{"en":"A safe Gemini API-key setup starts with role selection, signature handling and a written cancel boundary before any trading bot is connected.","zh-Hans":"如何安全设置 Gemini API Key Roles 与会话撤单控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Gemini API-key authentication documentation says users can provision API key pairs by logging into the exchange and navigating to Settings/API.","sourceIds":["gemini-auth"],"risk":"medium"},{"id":"c2","text":"Gemini API-key authentication documentation says an API key is the public identifier and an API secret is used to generate HMAC-SHA384 signatures.","sourceIds":["gemini-auth"],"risk":"medium"},{"id":"c3","text":"Gemini private REST requests use headers including X-GEMINI-APIKEY, X-GEMINI-PAYLOAD and X-GEMINI-SIGNATURE.","sourceIds":["gemini-auth"],"risk":"medium"},{"id":"c4","text":"Gemini roles documentation says role-based access control enforces least-privilege permissions across API keys.","sourceIds":["gemini-roles"],"risk":"medium"},{"id":"c5","text":"Gemini roles documentation says API keys can isolate trading, withdrawal and read-only responsibilities.","sourceIds":["gemini-roles"],"risk":"low"},{"id":"c6","text":"Gemini orders documentation describes cancel order, cancel all active orders, cancel all session orders and heartbeat behavior that a bot operator must test before relying on session cancellation.","sourceIds":["gemini-orders"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"circle-cctp-v2-fast-vs-standard-finality-controls-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-06T21:21:00.000Z","updatedAt":"2026-10-06T21:21:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Circle CCTP V2 Fast vs Standard Transfer Finality Controls","zh-Hans":"Circle CCTP V2 Fast 与 Standard Transfer 终局性控制"},"summary":{"en":"Circle CCTP V2 changes the cross-chain USDC decision from bridge selection to finality and attestation controls.","zh-Hans":"Circle CCTP V2 Fast 与 Standard Transfer 终局性控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Circle Help Center describes CCTP as a permissionless onchain utility for securely transferring USDC between blockchains through native burning and minting.","sourceIds":["circle-cctp-help"],"risk":"medium"},{"id":"c2","text":"Circle Help Center says CCTP V2 is now the canonical CCTP and CCTP V1 is legacy with phase-out beginning July 31, 2026.","sourceIds":["circle-cctp-help","circle-cctp-product"],"risk":"medium"},{"id":"c3","text":"Circle's CCTP product page says Standard USDC Transfer is free while Fast USDC Transfer has an on-chain fee, and fees are subject to change with advance notice.","sourceIds":["circle-cctp-product"],"risk":"medium"},{"id":"c4","text":"Circle's CCTP V2 blog says Fast Transfer enables seconds-level settlement and Hooks allow post-transfer actions on the destination blockchain.","sourceIds":["circle-cctp-blog"],"risk":"medium"},{"id":"c5","text":"The CCTP V2 white paper defines maxFee, feeExecuted, expirationBlock, hookData and finality threshold fields that differentiate fast and standard paths.","sourceIds":["circle-cctp-whitepaper"],"risk":"low"},{"id":"c6","text":"The transfer-control map separates source event, attestation, finality threshold, fee ceiling, hook payload, destination mint, expiration and fallback route.","sourceIds":["circle-cctp-help","circle-cctp-product","circle-cctp-blog","circle-cctp-whitepaper"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-vs-kraken-order-preview-cancel-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-06T21:21:00.000Z","updatedAt":"2026-10-06T21:21:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Advanced Trade vs Kraken Order Preview and Cancel Controls","zh-Hans":"Coinbase Advanced Trade 与 Kraken 订单预览和撤单控制对比"},"summary":{"en":"Coinbase Advanced Trade and Kraken expose different order-control surfaces, so the useful comparison is not brand preference but failure-mode coverage.","zh-Hans":"Coinbase Advanced Trade 与 Kraken 订单预览和撤单控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase documentation says Advanced Trade v3 includes private endpoints for create order, cancel orders, list orders, list fills, get order and preview orders.","sourceIds":["coinbase-endpoints"],"risk":"medium"},{"id":"c2","text":"Coinbase documentation maps API-key permission levels such as view, trade and transfer to endpoint access.","sourceIds":["coinbase-auth","coinbase-endpoints"],"risk":"medium"},{"id":"c3","text":"Coinbase API-key guidance says credentials should be stored outside the code base and IP allowlisting is recommended for additional key security.","sourceIds":["coinbase-auth"],"risk":"medium"},{"id":"c4","text":"Kraken spot REST documentation says Cancel All Orders requires order creation or cancel-close order permissions and cancels all open orders.","sourceIds":["kraken-cancel-all"],"risk":"medium"},{"id":"c5","text":"Kraken futures documentation describes a dead man's switch endpoint where a timeout in seconds starts a countdown that cancels all user orders unless refreshed or deactivated with zero.","sourceIds":["kraken-deadman"],"risk":"low"},{"id":"c6","text":"A responsible comparison separates order preview, permission scope, cancel scope, timer refresh behavior, partial fills, final state and non-secret reconciliation evidence.","sourceIds":["coinbase-auth","coinbase-endpoints","kraken-cancel-all","kraken-deadman"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-api-secret-storage-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-06T21:21:00.000Z","updatedAt":"2026-10-06T21:21:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto API Secret Storage Disclosure Radar","zh-Hans":"加密平台 API Secret 存储披露雷达"},"summary":{"en":"Crypto API-key risk is usually created before the first order is submitted. Coinbase documentation says credentials should be stored securely, outside the code base, and IP allowlisting is recommended.","zh-Hans":"加密平台 API Secret 存储披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase API-key guidance says credentials should be stored securely and not stored in the code base, with environment variables named as a recommended pattern.","sourceIds":["coinbase-auth"],"risk":"medium"},{"id":"c2","text":"Coinbase documentation recommends whitelisting IP addresses for enhanced API-key security.","sourceIds":["coinbase-auth"],"risk":"medium"},{"id":"c3","text":"Backpack support says API-key creation is web-only and the Read Only button restricts key permissions to view-only access.","sourceIds":["backpack-api-keys"],"risk":"medium"},{"id":"c4","text":"Backpack API documentation says mutating calls require ED25519 signed requests unless otherwise documented.","sourceIds":["backpack-api"],"risk":"medium"},{"id":"c5","text":"Kraken's Get API Key Info endpoint exposes information about API key permissions, including order and trade permission labels.","sourceIds":["kraken-key-info"],"risk":"low"},{"id":"c6","text":"A useful secret-storage radar records creation surface, account scope, permission scope, storage location class, log redaction, IP/device controls, rotation trigger and revoke path.","sourceIds":["coinbase-auth","backpack-api-keys","backpack-api","kraken-key-info"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-coinbase-cdp-api-key-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-06T21:21:00.000Z","updatedAt":"2026-10-06T21:21:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up a Coinbase CDP API Key Safely","zh-Hans":"如何安全设置 Coinbase CDP API Key"},"summary":{"en":"A safe Coinbase CDP API-key setup starts by choosing the narrowest permission and treating the downloaded private key as a secret from the first click.","zh-Hans":"如何安全设置 Coinbase CDP API Key：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase says CDP API keys are used to authenticate permissioned Advanced Trade REST API and WebSocket API channels.","sourceIds":["coinbase-auth"],"risk":"medium"},{"id":"c2","text":"Coinbase says API key creation includes nickname, portfolio, permission level and allowlisted IP configuration.","sourceIds":["coinbase-auth"],"risk":"medium"},{"id":"c3","text":"Coinbase says the user completes 2FA and the API key JSON automatically downloads.","sourceIds":["coinbase-auth"],"risk":"medium"},{"id":"c4","text":"Coinbase says credentials should be stored securely outside the code base and recommends environment variables.","sourceIds":["coinbase-auth"],"risk":"medium"},{"id":"c5","text":"Coinbase says IP whitelisting is recommended for enhanced API-key security.","sourceIds":["coinbase-auth"],"risk":"low"},{"id":"c6","text":"Coinbase Advanced Trade endpoint documentation maps private endpoints to view, trade and transfer permissions, which should drive onboarding tests.","sourceIds":["coinbase-endpoints","coinbase-sdk"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-dead-man-switch-api-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-06T21:21:00.000Z","updatedAt":"2026-10-06T21:21:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken Dead Man's Switch API Readiness Checklist","zh-Hans":"Kraken Dead Man's Switch API 准备清单"},"summary":{"en":"Kraken's dead man's switch should be treated as an outage-control mechanism, not as a generic safety label.","zh-Hans":"Kraken Dead Man's Switch API 准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Kraken futures documentation says the dead man's switch endpoint triggers a countdown timer using a timeout specified in seconds.","sourceIds":["kraken-deadman"],"risk":"medium"},{"id":"c2","text":"Kraken futures documentation says expiring the timer cancels all user orders, and a timeout of zero deactivates the mechanism.","sourceIds":["kraken-deadman"],"risk":"medium"},{"id":"c3","text":"Kraken futures documentation recommends refreshing every 15 to 20 seconds with a 60-second timeout.","sourceIds":["kraken-deadman"],"risk":"medium"},{"id":"c4","text":"Kraken futures documentation lists possible errors including authenticationError, apiLimitExceeded, nonceDuplicate and nonceBelowThreshold.","sourceIds":["kraken-deadman"],"risk":"medium"},{"id":"c5","text":"Kraken spot Cancel All Orders documentation identifies the cancel-all action and required order permissions for spot REST.","sourceIds":["kraken-cancel-all"],"risk":"low"},{"id":"c6","text":"The readiness record must separate futures endpoint behavior, spot cancel-all behavior, key permission, timer refresh, server time, rate limits and post-cancel order reconciliation.","sourceIds":["kraken-deadman","kraken-cancel-all","kraken-key-info"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"backpack-api-ed25519-batch-order-readiness-checklist","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-06T18:12:00.000Z","updatedAt":"2026-10-06T18:12:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Backpack API ED25519 and Batch Order Readiness Checklist","zh-Hans":"Backpack API ED25519 与批量订单准备清单"},"summary":{"en":"Backpack Exchange API integration should be treated as a signed-order control workflow, not just a REST endpoint copy task.","zh-Hans":"Backpack API ED25519 与批量订单准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Backpack's API documentation says endpoints that mutate state require signed requests using an ED25519 keypair unless documented otherwise.","sourceIds":["backpack-api"],"risk":"medium"},{"id":"c2","text":"Backpack signed requests include X-Timestamp, X-Window, X-API-Key and X-Signature headers, with the default window documented as 5000 milliseconds and a maximum of 60000 milliseconds.","sourceIds":["backpack-api"],"risk":"medium"},{"id":"c3","text":"Backpack documents instruction-prefixed signing strings for order execution and cancel workflows, including batch order execution.","sourceIds":["backpack-api"],"risk":"medium"},{"id":"c4","text":"Backpack's order query and cancel documentation says one of orderId or clientId should be specified and warns that orderId takes precedence when both are provided.","sourceIds":["backpack-api"],"risk":"medium"},{"id":"c5","text":"Backpack's API-key support page says API key creation is web-only and the Read Only button restricts a key to view-only access.","sourceIds":["backpack-api-keys"],"risk":"low"},{"id":"c6","text":"The safe readiness record separates key custody, request signing, time window, batch item identity, cancel evidence, accepted-but-not-executed states and non-secret reconciliation logs.","sourceIds":["backpack-api","backpack-api-keys","backpack-api-faq"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-stablecoins-tokenised-deposits-trust-anchor-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-06T18:12:00.000Z","updatedAt":"2026-10-06T18:12:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Stablecoins and Tokenised Deposits Trust Anchor Map","zh-Hans":"BIS 稳定币与代币化存款信任锚地图"},"summary":{"en":"BIS material frames tokenisation as a trust-architecture question rather than a speed contest. Its 2026 Annual Economic Report chapter argues that stablecoins in their current form do not uphold the properties that support trust.","zh-Hans":"BIS 稳定币与代币化存款信任锚地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"The BIS 2026 Annual Economic Report chapter says stablecoins in their current form do not uphold the properties that support trust in money.","sourceIds":["bis-2026-trust"],"risk":"medium"},{"id":"c2","text":"The BIS chapter says tokenisation can improve monetary rails when design choices safeguard the properties of money while enabling efficiency gains.","sourceIds":["bis-2026-trust"],"risk":"medium"},{"id":"c3","text":"The BIS media release frames the next-generation monetary and financial system around innovation integrated into the existing architecture while preserving trust.","sourceIds":["bis-2026-release"],"risk":"medium"},{"id":"c4","text":"The BIS speech says stablecoins and tokenised deposits could coexist if roles are clearly delineated and safeguards are in place.","sourceIds":["bis-tokenised-deposits-speech"],"risk":"medium"},{"id":"c5","text":"The IMF note treats tokenized finance as a design and infrastructure topic rather than a proof that every tokenized instrument is equivalent to its traditional analogue.","sourceIds":["imf-tokenized-finance"],"risk":"low"},{"id":"c6","text":"A trust-anchor map should separate issuer, record, settlement asset, redemption path, legal finality, platform governance, access policy and operational resilience.","sourceIds":["bis-2026-trust","bis-2026-release","bis-tokenised-deposits-speech","imf-tokenized-finance"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"curve-stableswap-ng-vs-uniswap-v4-pool-control-checklist","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-06T18:12:00.000Z","updatedAt":"2026-10-06T18:12:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Curve Stableswap-NG vs Uniswap v4 Pool Control Checklist","zh-Hans":"Curve Stableswap-NG 与 Uniswap v4 池子控制清单"},"summary":{"en":"Curve Stableswap-NG and Uniswap v4 solve different pool-control problems. Curve documentation frames Stableswap-NG as an AMM implementation for stable or rate-linked assets, with pool variants, built-in oracles, dynamic fees,.","zh-Hans":"Curve Stableswap-NG 与 Uniswap v4 池子控制清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Curve documents Stableswap-NG as a StableSwap AMM implementation with plain pools, metapools, rate-oracle support, rebasing-token support, ERC4626 support, dynamic fees and built-in oracles.","sourceIds":["curve-ng-overview"],"risk":"medium"},{"id":"c2","text":"Curve plain-pool documentation warns production users not to set minimum output values such as _min_dy or _min_amount to zero or arbitrary numbers because MEV can frontrun or sandwich a transaction.","sourceIds":["curve-plainpool"],"risk":"medium"},{"id":"c3","text":"Uniswap v4 documentation says each liquidity pool can have its own hook contract attached to it.","sourceIds":["uniswap-v4-hooks"],"risk":"medium"},{"id":"c4","text":"Uniswap v4 documentation says the PoolManager is the singleton contract that holds pool state and coordinates swaps, liquidity and hook execution.","sourceIds":["uniswap-v4-poolmanager"],"risk":"medium"},{"id":"c5","text":"A Curve stable pool document does not prove the selected token pair is low risk, and a Uniswap hook document does not prove the attached hook is safe or simple.","sourceIds":["curve-ng-overview","uniswap-v4-hooks"],"risk":"low"},{"id":"c6","text":"The safe comparison separates asset type, invariant, hook or pool logic, oracle input, fee behavior, approval path, minimum output and post-transaction reconciliation.","sourceIds":["curve-ng-overview","curve-plainpool","uniswap-v4-hooks","uniswap-v4-poolmanager"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-backpack-api-key-order-controls-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-06T18:12:00.000Z","updatedAt":"2026-10-06T18:12:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up a Backpack API Key and Order Controls Safely","zh-Hans":"如何安全设置 Backpack API Key 与订单控制"},"summary":{"en":"A safe Backpack API-key setup starts with the web key-creation flow, a narrow permission choice and a non-production signing test.","zh-Hans":"如何安全设置 Backpack API Key 与订单控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Backpack support says API key creation is currently supported on the web only.","sourceIds":["backpack-api-keys"],"risk":"medium"},{"id":"c2","text":"Backpack support says the user enters a key name, chooses the sub-account and creates the key, with Read Only restricting permissions to view-only access.","sourceIds":["backpack-api-keys"],"risk":"medium"},{"id":"c3","text":"Backpack API documentation says mutating API requests require ED25519 signed requests unless documented otherwise.","sourceIds":["backpack-api"],"risk":"medium"},{"id":"c4","text":"Backpack API documentation defines X-Timestamp, X-Window, X-API-Key and X-Signature headers for signed requests.","sourceIds":["backpack-api"],"risk":"medium"},{"id":"c5","text":"Backpack API documentation describes order execution, order query, cancel order and cancel-all order controls that can use orderId or clientId depending on route.","sourceIds":["backpack-api"],"risk":"low"},{"id":"c6","text":"A safe tutorial must stop before live trading until key scope, signing, timestamp window, order identity, cancel state and logs are tested without exposing secrets.","sourceIds":["backpack-api-keys","backpack-api","backpack-api-faq"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"stablecoin-freeze-sanctions-disclosure-radar","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-06T18:12:00.000Z","updatedAt":"2026-10-06T18:12:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Stablecoin Freeze and Sanctions Disclosure Radar","zh-Hans":"稳定币冻结与制裁披露雷达"},"summary":{"en":"Stablecoin freeze risk should be mapped as an issuer-control and sanctions-compliance boundary, not as a rumor about wallets.","zh-Hans":"稳定币冻结与制裁披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Circle's USDC Terms reserve the right to block certain USDC addresses and, for Circle-custodied addresses, freeze associated USDC temporarily or permanently under stated conditions.","sourceIds":["circle-usdc-terms"],"risk":"medium"},{"id":"c2","text":"Circle's legal documentation includes broader Digital Currency blocked-address language for Circle Mint account terms.","sourceIds":["circle-legal"],"risk":"medium"},{"id":"c3","text":"Tether's legal terms define sanctioned persons and reserve rights to suspend services, freeze Tether Tokens or terminate token wallets under legal, sanctions, risk or terms conditions.","sourceIds":["tether-legal"],"risk":"medium"},{"id":"c4","text":"Tether has published enforcement-related freeze notices tied to OFAC and U.S. law-enforcement coordination.","sourceIds":["tether-freeze-ofac"],"risk":"medium"},{"id":"c5","text":"A block explorer can show token events or address state, but it cannot by itself prove the issuer's legal trigger, account notice, redemption outcome or recovery path.","sourceIds":["circle-usdc-terms","tether-legal"],"risk":"low"},{"id":"c6","text":"The radar record separates issuer authority, address status, custody surface, redemption path, sanctions or law-enforcement trigger, user notice and appeal evidence.","sourceIds":["circle-usdc-terms","circle-legal","tether-legal","tether-freeze-ofac"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"chainlink-ace-private-beta-tokenized-compliance-boundary-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-06T12:05:00.000Z","updatedAt":"2026-10-06T12:05:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"Chainlink ACE Private Beta: Tokenized Asset Compliance Boundary Map","zh-Hans":"Chainlink ACE Private Beta：代币化资产合规边界地图"},"summary":{"en":"Chainlink ACE should be evaluated as a compliance infrastructure layer in private beta, not as proof that a tokenized asset is approved or safe for every user.","zh-Hans":"Chainlink ACE Private Beta：代币化资产合规边界地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Chainlink ACE documentation describes ACE as a compliance layer for EVM smart contracts.","sourceIds":["chainlink-ace-overview"],"risk":"medium"},{"id":"c2","text":"Chainlink ACE documentation labels ACE as private beta and says access requires contacting Chainlink.","sourceIds":["chainlink-ace-overview"],"risk":"medium"},{"id":"c3","text":"Chainlink ACE beta-scope documentation narrows what private-beta users can assume about current feature set and limitations.","sourceIds":["chainlink-ace-overview","chainlink-ace-beta-scope"],"risk":"medium"},{"id":"c4","text":"Chainlink ACE documentation says the ACE Platform provides managers for policy, identity and reporting-oriented operations.","sourceIds":["chainlink-ace-overview"],"risk":"low"},{"id":"c5","text":"Chainlink's ACE product page links ACE with regulated, policy-protected asset movement across public and private blockchains.","sourceIds":["chainlink-ace-product","chainlink-ace-technical"],"risk":"low"},{"id":"c6","text":"A compliance engine can support a workflow without proving investor eligibility, asset approval, resale rights or legal suitability.","sourceIds":["chainlink-ace-overview","chainlink-ace-product"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-earn-deallocate-status-api-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-06T12:05:00.000Z","updatedAt":"2026-10-06T12:05:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken Earn Deallocate Status API Readiness Checklist","zh-Hans":"Kraken Earn Deallocate Status API 就绪清单"},"summary":{"en":"Kraken Earn API operations should be handled as asynchronous fund-control workflows, not as a single button result.","zh-Hans":"Kraken Earn Deallocate Status API 就绪清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Kraken's Deallocate Earn Funds documentation says the endpoint deallocates funds from a strategy and requires Earn Funds permission.","sourceIds":["kraken-deallocate-earn"],"risk":"medium"},{"id":"c2","text":"Kraken's Deallocate Earn Funds documentation says the amount and strategy ID are required fields.","sourceIds":["kraken-deallocate-earn"],"risk":"medium"},{"id":"c3","text":"Kraken's Deallocate Earn Funds documentation describes asynchronous handling and status polling when a 202 response is returned.","sourceIds":["kraken-deallocate-earn","kraken-deallocation-status"],"risk":"medium"},{"id":"c4","text":"Kraken Earn status documentation describes a pending field for dispatched allocation or deallocation operations.","sourceIds":["kraken-deallocation-status","kraken-allocation-status"],"risk":"low"},{"id":"c5","text":"Kraken's Get API Key Info documentation lists permissions, restrictions, nonce window, validity and last-used fields for the authenticated API key.","sourceIds":["kraken-api-key-info"],"risk":"low"},{"id":"c6","text":"An Earn deallocation workflow should not expose API secrets, API signatures, 2FA codes or private account data in the evidence log.","sourceIds":["kraken-deallocate-earn","kraken-api-key-info"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"permit2-vs-token-approval-revoke-control-boundary","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-06T12:05:00.000Z","updatedAt":"2026-10-06T12:05:00.000Z","readTime":"22 min","author":"NexuAlpha Research Desk","title":{"en":"Permit2 vs Token Approval Revokes: Expiry, Allowance and Wallet Safety Controls","zh-Hans":"Permit2 与 Token 授权撤销对比：到期、额度与钱包安全控制"},"summary":{"en":"Permit2 and standard ERC-20 approval revokes solve different wallet-control problems. Uniswap documentation says Permit2 combines SignatureTransfer and AllowanceTransfer, with one-time signatures, time-bound allowances and.","zh-Hans":"Permit2 与 Token 授权撤销对比：到期、额度与钱包安全控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Uniswap Permit2 documentation describes two modules: SignatureTransfer for signature-based one-time transfers and AllowanceTransfer for amount-and-duration permissions.","sourceIds":["uniswap-permit2-overview"],"risk":"medium"},{"id":"c2","text":"Uniswap AllowanceTransfer documentation says its approve function includes token, spender, amount and expiration parameters.","sourceIds":["uniswap-allowance-transfer"],"risk":"medium"},{"id":"c3","text":"Uniswap Permit2 documentation says users still need a one-time standard ERC-20 approval of the Permit2 contract before Permit2 can move a token.","sourceIds":["uniswap-permit2-overview"],"risk":"medium"},{"id":"c4","text":"Uniswap SignatureTransfer documentation describes one-time permissions that are signed and consumed without leaving a standing allowance.","sourceIds":["uniswap-signature-transfer"],"risk":"low"},{"id":"c5","text":"EIP-2612 defines a token-native permit function that modifies allowance through a signed message instead of msg.sender.","sourceIds":["eip-2612"],"risk":"low"},{"id":"c6","text":"A wallet safety checklist should not treat Permit2 expiration, token-contract revoke and EIP-2612 permit as the same control.","sourceIds":["uniswap-permit2-overview","uniswap-allowance-transfer","uniswap-signature-transfer","eip-2612"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"stablecoin-payout-support-disclosure-radar","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-06T12:05:00.000Z","updatedAt":"2026-10-06T12:05:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"Stablecoin Payout Support Disclosure Radar: Preview Access, Recipient Scope and Transfer Controls","zh-Hans":"稳定币付款支持披露雷达：预览访问、收款人范围与转账控制"},"summary":{"en":"Stablecoin payout support should be checked as a product-eligibility and transfer-control question, not as a general crypto payout promise.","zh-Hans":"稳定币付款支持披露雷达：预览访问、收款人范围与转账控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Stripe documentation labels stablecoin payouts for Connect as private preview.","sourceIds":["stripe-stablecoin-payouts"],"risk":"medium"},{"id":"c2","text":"Stripe documentation says stablecoin payouts start with USDC and that the platform balance stays in fiat while Stripe handles conversion and payout.","sourceIds":["stripe-stablecoin-payouts"],"risk":"medium"},{"id":"c3","text":"Stripe documentation says platforms must request access and complete additional requirements before using stablecoin payouts.","sourceIds":["stripe-stablecoin-payouts","stripe-account-requirements"],"risk":"medium"},{"id":"c4","text":"Stripe documentation says users link a crypto wallet through Express Dashboard and can receive payouts to that wallet instead of a bank account.","sourceIds":["stripe-stablecoin-payouts","stripe-express-dashboard"],"risk":"low"},{"id":"c5","text":"Stripe documentation says stablecoin payouts require the Transfers API.","sourceIds":["stripe-stablecoin-payouts","stripe-transfers-api"],"risk":"low"},{"id":"c6","text":"A payout support disclosure should not imply universal country, company, nonprofit, New York, Hawaii or account-level availability without current eligibility evidence.","sourceIds":["stripe-stablecoin-payouts"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"swift-blockchain-ledger-tokenized-deposit-readiness-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-06T12:05:00.000Z","updatedAt":"2026-10-06T12:05:00.000Z","readTime":"22 min","author":"NexuAlpha Research Desk","title":{"en":"Swift Blockchain Ledger and Tokenized Deposit Readiness Map","zh-Hans":"Swift 区块链账本与代币化存款就绪地图"},"summary":{"en":"Swift's blockchain-ledger work should be read as institutional infrastructure experimentation and planned implementation, not as proof that retail stablecoin or exchange settlement is already live.","zh-Hans":"Swift 区块链账本与代币化存款就绪地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Swift's March 2026 newsletter says its blockchain-based ledger is moving from design to MVP implementation with live transactions planned for 2026.","sourceIds":["swift-ledger-road-ahead"],"risk":"medium"},{"id":"c2","text":"Swift describes the ledger focus as corporate and treasury flows using tokenized deposits to validate and synchronize interbank payment commitments.","sourceIds":["swift-ledger-road-ahead"],"risk":"medium"},{"id":"c3","text":"Swift reports a digital asset interoperability trial involving tokenized bonds, fiat and digital-currency payments, and coordinated process roles such as paying agent, custodian and registrar.","sourceIds":["swift-digital-finance-scale"],"risk":"medium"},{"id":"c4","text":"Swift, UBS Asset Management and Chainlink reported a pilot for settling tokenized fund subscriptions and redemptions using the Swift network.","sourceIds":["swift-tokenized-funds-chainlink"],"risk":"low"},{"id":"c5","text":"Swift corporate-actions material describes collaboration with Chainlink and industry stakeholders to use AI and blockchain for corporate-action data workflows.","sourceIds":["swift-corporate-actions"],"risk":"low"},{"id":"c6","text":"Swift's institutional pilots do not prove consumer exchange settlement availability, token price outcome, or public retail stablecoin transfer support.","sourceIds":["swift-ledger-road-ahead","swift-digital-finance-scale","swift-tokenized-funds-chainlink"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-vs-okx-amend-cancel-acknowledgement-websocket-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-06T11:58:00.000Z","updatedAt":"2026-10-06T11:58:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit vs OKX Amend and Cancel Acknowledgement Controls","zh-Hans":"Bybit 与 OKX 改单撤单确认控制对比"},"summary":{"en":"Bybit and OKX both treat order amendment or cancellation as an asynchronous control problem: an accepted request is not the same as final order state.","zh-Hans":"Bybit 与 OKX 改单撤单确认控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit amend-order documentation says the acknowledgement indicates the amend request was accepted and that websocket should be used to confirm order status.","sourceIds":["bybit-amend-order"],"risk":"medium"},{"id":"c2","text":"Bybit websocket trade guidance defines timestamp and receive-window conditions for authenticated websocket trade requests.","sourceIds":["bybit-websocket-trade"],"risk":"medium"},{"id":"c3","text":"OKX order-operation guidance says amend and cancel acknowledgements are acceptance signals, while final results should be confirmed through websocket order updates.","sourceIds":["okx-order-operations-guide"],"risk":"medium"},{"id":"c4","text":"OKX documents expTime, cxlOnFail, request IDs and independent trading rate limits for order, amend and cancel workflows.","sourceIds":["okx-api-overview","okx-order-operations-guide"],"risk":"low"},{"id":"c5","text":"Neither venue's acknowledgement alone proves that the original order changed, canceled, retained queue priority or avoided a partial fill race.","sourceIds":["bybit-amend-order","okx-order-operations-guide"],"risk":"low"},{"id":"c6","text":"The safe comparison separates request acceptance, final order state, partial fill behavior, timeout handling, rate-limit behavior and local reconciliation.","sourceIds":["bybit-amend-order","bybit-websocket-trade","okx-order-operations-guide","okx-api-overview"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-websocket-order-entry-batch-timestamp-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-06T11:58:00.000Z","updatedAt":"2026-10-06T11:58:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit WebSocket Order Entry Batch Timestamp Readiness Checklist","zh-Hans":"Bybit WebSocket 批量下单改单撤单时间戳准备清单"},"summary":{"en":"Bybit's V5 order-entry materials should be read as an implementation-readiness checklist rather than a guarantee that every bot can safely batch trade.","zh-Hans":"Bybit WebSocket 批量下单改单撤单时间戳准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit's V5 changelog lists WebSocket order-entry updates for batch create, amend and cancel workflows.","sourceIds":["bybit-v5-changelog"],"risk":"medium"},{"id":"c2","text":"Bybit websocket trade guidance rejects requests outside the documented timestamp and receive-window condition.","sourceIds":["bybit-websocket-trade-guideline"],"risk":"medium"},{"id":"c3","text":"Bybit rate-limit documentation separates API limits by endpoint, product and upgrade status.","sourceIds":["bybit-rate-limit-rules"],"risk":"medium"},{"id":"c4","text":"Bybit amend-order documentation requires orderId or orderLinkId and treats amend acknowledgement as asynchronous.","sourceIds":["bybit-amend-order-reference"],"risk":"low"},{"id":"c5","text":"A changelog entry does not prove a user's key, account mode, product category, symbol or bot architecture is ready for batch trading.","sourceIds":["bybit-v5-changelog","bybit-rate-limit-rules"],"risk":"low"},{"id":"c6","text":"The safe readiness record separates clock validity, request envelope, batch item mapping, websocket state confirmation, endpoint limit and rollback action.","sourceIds":["bybit-v5-changelog","bybit-websocket-trade-guideline","bybit-rate-limit-rules","bybit-amend-order-reference"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-tokenization-service-live-production-trades-rights-controls-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-06T11:58:00.000Z","updatedAt":"2026-10-06T11:58:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Tokenization Service Live Production Trades Rights Controls Map","zh-Hans":"DTCC Tokenization Service 真实生产交易与权利控制地图"},"summary":{"en":"DTCC's tokenization materials make a narrow but important claim: tokenized DTC-held assets are being framed as market-infrastructure objects with rights, controls and reconciliation layers, not as generic exchange tokens.","zh-Hans":"DTCC Tokenization Service 真实生产交易与权利控制地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"DTCC describes its Tokenization Service as built on market infrastructure to support interoperability, asset mobility and market connectivity for tokenized assets.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c2","text":"DTCC Tokenization Service materials state that tokenized DTC assets can use the same CUSIP and are designed to represent the same legal rights, economic interest and investor protections as the underlying securities.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c3","text":"DTCC's live production trades page describes July 2026 transactions involving tokenized assets and references an expected October 2026 Tokenization Service launch.","sourceIds":["dtcc-live-production-trades"],"risk":"medium"},{"id":"c4","text":"DTCC's July 2026 press release says DTC-held securities were converted into tokens and used in production trades across multiple use cases.","sourceIds":["dtcc-tokenization-press-release"],"risk":"low"},{"id":"c5","text":"SEC tokenized-securities materials warn that tokenized-security models vary and the rights or obligations can differ depending on the structure.","sourceIds":["sec-tokenized-securities-statement"],"risk":"low"},{"id":"c6","text":"The safe decision record separates DTC participant eligibility, wallet delivery, official record, same-CUSIP rights, compliance controls, corporate actions and rollback.","sourceIds":["dtcc-tokenization-service","dtcc-live-production-trades","dtcc-tokenization-press-release","sec-tokenized-securities-statement"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fix-drop-copy-sequence-reset-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-06T11:58:00.000Z","updatedAt":"2026-10-06T11:58:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"FIX Drop Copy Sequence Reset Disclosure Radar","zh-Hans":"FIX Drop Copy 序列重置披露雷达"},"summary":{"en":"FIX drop copy and sequence-reset documentation is a reconciliation-control signal, not a guarantee that a trading desk has complete books.","zh-Hans":"FIX Drop Copy 序列重置披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Exchange FIX Drop Copy documentation says drop copy receives execution reports for orders placed through FIX sessions or REST API associated with an API key.","sourceIds":["coinbase-exchange-drop-copy"],"risk":"medium"},{"id":"c2","text":"Coinbase Exchange Drop Copy documentation describes a single-connection limit per API key and a weekly FIX5 reset schedule.","sourceIds":["coinbase-exchange-drop-copy"],"risk":"medium"},{"id":"c3","text":"Coinbase International Exchange FIX overview says every connection establishes a new session and new sequence numbers, and resend requests are not supported.","sourceIds":["coinbase-intx-fix-overview"],"risk":"medium"},{"id":"c4","text":"Coinbase Exchange upcoming-changes documentation shows execution-report fields can change through scheduled documentation updates.","sourceIds":["coinbase-exchange-upcoming-changes"],"risk":"low"},{"id":"c5","text":"Coinbase REST order lookup documentation allows order queries using exchange-assigned or client-assigned identifiers with required permissions.","sourceIds":["coinbase-get-single-order"],"risk":"low"},{"id":"c6","text":"The safe radar separates drop-copy coverage, reset calendar, change notices, REST lookup fallback, client-order-ID lineage and local gap recovery.","sourceIds":["coinbase-exchange-drop-copy","coinbase-intx-fix-overview","coinbase-exchange-upcoming-changes","coinbase-get-single-order"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cftc-tokenized-collateral-stablecoin-margin-readiness-checklist","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-06T08:58:00.000Z","updatedAt":"2026-10-06T08:58:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC Tokenized Collateral and Payment Stablecoin Margin Readiness Checklist","zh-Hans":"CFTC 代币化抵押品与支付稳定币保证金准备清单"},"summary":{"en":"CFTC 2026 materials make tokenized collateral a market-infrastructure readiness question, not a promise that every stablecoin can be used as margin.","zh-Hans":"CFTC 代币化抵押品与支付稳定币保证金准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"CFTC staff issued 2026 FAQs concerning registrant and registered-entity activities related to crypto assets and blockchain technologies.","sourceIds":["cftc-crypto-faq-2026"],"risk":"medium"},{"id":"c2","text":"CFTC Letter 26-05 concerns digital assets accepted as margin collateral by futures commission merchants and revises payment-stablecoin issuer treatment in a limited no-action context.","sourceIds":["cftc-letter-26-05"],"risk":"medium"},{"id":"c3","text":"CFTC Treasury-market remarks discuss tokenized collateral and payment stablecoin work for exchanges, clearinghouses and market participants.","sourceIds":["cftc-treasury-market-tokenization"],"risk":"medium"},{"id":"c4","text":"CFTC final-rule materials include crypto-asset and payment-stablecoin references within a regulated derivatives context.","sourceIds":["cftc-final-rule-2026-05635"],"risk":"low"},{"id":"c5","text":"A payment stablecoin appearing in CFTC material does not prove that a private account, clearing member or exchange will accept it as margin.","sourceIds":["cftc-letter-26-05","cftc-treasury-market-tokenization"],"risk":"low"},{"id":"c6","text":"The safe readiness checklist separates issuer eligibility, custody control, valuation, haircut, operational workflow, redemption and default handling.","sourceIds":["cftc-crypto-faq-2026","cftc-letter-26-05","cftc-treasury-market-tokenization","cftc-final-rule-2026-05635"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-use-gmx-wallet-account-trading-and-risk-controls-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-06T08:58:00.000Z","updatedAt":"2026-10-06T08:58:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"How to Use GMX Wallet Account Trading and Risk Controls Safely","zh-Hans":"如何安全使用 GMX 钱包账户交易与风险控制"},"summary":{"en":"A GMX onboarding checklist should separate wallet connection, GMX Account funding, delegated trading and order execution before any user opens a position.","zh-Hans":"如何安全使用 GMX 钱包账户交易与风险控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"GMX documentation provides SDK getting-started material for integration and trading flows.","sourceIds":["gmx-sdk-getting-started"],"risk":"medium"},{"id":"c2","text":"GMX delegated-trading documentation describes subaccount and relay surfaces for delegated trading flows.","sourceIds":["gmx-delegated-trading"],"risk":"medium"},{"id":"c3","text":"GMX frontend-integration documentation is an official integration surface for building or embedding GMX interfaces.","sourceIds":["gmx-frontend-integration"],"risk":"medium"},{"id":"c4","text":"GMX SDK order examples document transaction-building paths for order actions.","sourceIds":["gmx-order-examples"],"risk":"low"},{"id":"c5","text":"GMX's whitepaper describes GMX as a decentralized perpetual exchange with wallet-based access.","sourceIds":["gmx-whitepaper"],"risk":"low"},{"id":"c6","text":"A connected wallet does not prove that the user selected the intended chain, collateral, leverage, delegated permission or withdrawal route.","sourceIds":["gmx-sdk-getting-started","gmx-delegated-trading","gmx-frontend-integration","gmx-order-examples","gmx-whitepaper"],"risk":"low"}],"relatedVenues":["gmx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"oracle-price-feed-staleness-confidence-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-06T08:58:00.000Z","updatedAt":"2026-10-06T08:58:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Oracle Price Feed Staleness and Confidence Disclosure Radar","zh-Hans":"预言机价格源陈旧度与置信区间披露雷达"},"summary":{"en":"Oracle feed selection should start with data-quality evidence, not with brand familiarity or total value secured.","zh-Hans":"预言机价格源陈旧度与置信区间披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Chainlink tells application designers to consider the accuracy, availability and quality of data feeds they consume.","sourceIds":["chainlink-quality-feeds"],"risk":"medium"},{"id":"c2","text":"Chainlink documentation describes risk categories and single-source feed considerations for data-feed selection.","sourceIds":["chainlink-quality-feeds"],"risk":"medium"},{"id":"c3","text":"Chainlink SmartData Proof of Reserve documentation warns that feed configurations can vary and self-reported reserves carry issuer-risk considerations.","sourceIds":["chainlink-smartdata-por"],"risk":"medium"},{"id":"c4","text":"Pyth documentation explains price, confidence, publisher count and feed-update timestamp fields for price data.","sourceIds":["pyth-understanding-price-data"],"risk":"low"},{"id":"c5","text":"Pyth best-practice guidance discusses staleness constraints and the need to select acceptable age thresholds when consuming prices.","sourceIds":["pyth-best-practices"],"risk":"low"},{"id":"c6","text":"A current oracle response does not by itself prove suitability for collateral, liquidation, redemption, accounting or user-display decisions.","sourceIds":["chainlink-quality-feeds","chainlink-smartdata-por","pyth-understanding-price-data","pyth-best-practices"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-tokenized-nms-stock-innovation-exemption-venue-controls-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-06T08:58:00.000Z","updatedAt":"2026-10-06T08:58:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Tokenized NMS Stock Innovation Exemption Venue Controls Map","zh-Hans":"SEC 代币化 NMS 股票创新豁免与场所控制地图"},"summary":{"en":"The SEC innovation-exemption materials should be read as a temporary, conditional market-structure pathway for certain tokenized NMS stock venues, not as a blanket approval for every tokenized equity product.","zh-Hans":"SEC 代币化 NMS 股票创新豁免与场所控制地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"SEC innovation-exemption statements describe temporary, conditional relief for limited trading of tokenized NMS stocks on certain onchain venues.","sourceIds":["sec-uyeda-innovation-exemption"],"risk":"medium"},{"id":"c2","text":"SEC materials identify Tokenized Securities Venues as a market-structure object rather than a generic crypto exchange category.","sourceIds":["sec-uyeda-innovation-exemption","sec-atkins-innovation-bridge"],"risk":"medium"},{"id":"c3","text":"The SEC tokenized-securities statement discusses transfer of a crypto asset and control of the security, security entitlement, or ownership through legally effective mechanisms.","sourceIds":["sec-tokenized-securities-statement"],"risk":"medium"},{"id":"c4","text":"The SEC Crypto@SEC page lists crypto task force materials, including tokenized NMS stock exemptive-relief materials and related fact-sheet context.","sourceIds":["sec-crypto-task-force-index"],"risk":"low"},{"id":"c5","text":"A temporary exemption does not prove that every tokenized stock product is available to every user, transferable in every wallet, or eligible as collateral.","sourceIds":["sec-uyeda-innovation-exemption","sec-tokenized-securities-statement"],"risk":"low"},{"id":"c6","text":"The safe decision record separates venue condition, investor-protection condition, ownership-record treatment, liquidity-provider role, sunset date, and account jurisdiction.","sourceIds":["sec-uyeda-innovation-exemption","sec-atkins-innovation-bridge","sec-tokenized-securities-statement","sec-crypto-task-force-index"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"wallet-transaction-simulation-warning-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-06T08:58:00.000Z","updatedAt":"2026-10-06T08:58:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Wallet Transaction Simulation Warning Disclosure Radar","zh-Hans":"钱包交易模拟警告披露雷达"},"summary":{"en":"Wallet transaction simulation should be treated as a warning layer, not a guarantee that a signature is safe.","zh-Hans":"钱包交易模拟警告披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"MetaMask says transaction simulations enhance security alerts but do not guarantee detection of all threats.","sourceIds":["metamask-security-alerts"],"risk":"medium"},{"id":"c2","text":"MetaMask describes URL, JSON-RPC method, chain ID and transaction data as data points used for security checks when alerts are on.","sourceIds":["metamask-security-alerts"],"risk":"medium"},{"id":"c3","text":"Phantom developer documentation says a connected web application can prompt the user for permission to send transactions on the user's behalf.","sourceIds":["phantom-send-transaction-docs"],"risk":"medium"},{"id":"c4","text":"Phantom wallet skill guidance requires simulation-before-signing explanations for warnings, blocking conditions and expected asset changes.","sourceIds":["phantom-wallet-skill-guidance"],"risk":"low"},{"id":"c5","text":"Trust Wallet describes built-in risk monitoring tools, including Security Scanner, as part of its security posture.","sourceIds":["trust-wallet-security"],"risk":"low"},{"id":"c6","text":"A clean simulation or absent warning does not prove a signature cannot transfer assets, grant permissions or create a later loss path.","sourceIds":["metamask-security-alerts","phantom-send-transaction-docs","phantom-wallet-skill-guidance","trust-wallet-security"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"chainlink-ccip-20-institutional-interoperability-risk-map","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-06T05:58:00.000Z","updatedAt":"2026-10-06T05:58:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Chainlink CCIP 2.0 Institutional Interoperability Risk Map","zh-Hans":"Chainlink CCIP 2.0 机构互操作性风险地图"},"summary":{"en":"Chainlink's CCIP 2.0 announcement is decision-relevant because it frames interoperability, compliance and token movement as institutional infrastructure requirements, not as a guarantee that any tokenized product is compliant or.","zh-Hans":"Chainlink CCIP 2.0 机构互操作性风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Chainlink says CCIP 2.0 introduces features for institutional security, compliance and speed requirements.","sourceIds":["chainlink-ccip-20"],"risk":"medium"},{"id":"c2","text":"Chainlink's Payments Orchestrator page describes a system built on CRE, CCIP and ACE for tokenized-deposit and settlement coordination.","sourceIds":["chainlink-payments-orchestrator"],"risk":"medium"},{"id":"c3","text":"Chainlink's Automated Compliance Engine page describes regulated, policy-protected asset movement across public and private blockchains.","sourceIds":["chainlink-ace"],"risk":"medium"},{"id":"c4","text":"DTCC's interoperability article frames interoperability as an implementation issue for institutional digital assets, cash and collateral.","sourceIds":["dtcc-interoperability"],"risk":"low"},{"id":"c5","text":"Protocol-level interoperability does not prove asset eligibility, legal finality, counterparty acceptance or private account approval.","sourceIds":["chainlink-ccip-20","chainlink-payments-orchestrator","chainlink-ace","dtcc-interoperability"],"risk":"low"},{"id":"c6","text":"The safe decision record separates chain support, asset policy, compliance logic, settlement evidence and fallback recovery.","sourceIds":["chainlink-ccip-20","chainlink-payments-orchestrator","chainlink-ace","dtcc-interoperability"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-kraken-fix-sequence-reset-cancel-on-disconnect-controls","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-06T05:58:00.000Z","updatedAt":"2026-10-06T05:58:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase and Kraken FIX Sequence Reset and Cancel-on-Disconnect Controls","zh-Hans":"Coinbase 与 Kraken FIX 序列重置和断线撤单控制"},"summary":{"en":"Coinbase and Kraken FIX controls solve different failure modes, so a venue runbook should not treat sequence reset, drop-copy recovery and cancel-on-disconnect as the same safety action.","zh-Hans":"Coinbase 与 Kraken FIX 序列重置和断线撤单控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase International Exchange FIX documentation describes FIX order-entry connectivity and sequence-number reset behavior, including ResetSeqNumFlag.","sourceIds":["coinbase-intx-fix-overview"],"risk":"medium"},{"id":"c2","text":"Coinbase Exchange drop-copy documentation says drop copy provides execution reports for orders placed through FIX sessions or REST API associated with the API key.","sourceIds":["coinbase-exchange-drop-copy"],"risk":"medium"},{"id":"c3","text":"Kraken FIX logon documentation includes a CancelOrdersOnDisconnect field in the logon message surface.","sourceIds":["kraken-fix-logon"],"risk":"medium"},{"id":"c4","text":"Kraken WebSocket documentation describes cancelAllOrdersAfter as an authenticated cancel-on-disconnect control.","sourceIds":["kraken-cancel-all-after"],"risk":"low"},{"id":"c5","text":"A FIX sequence reset does not prove that live orders were cancelled, and a cancel-on-disconnect timer does not prove that every execution report was received.","sourceIds":["coinbase-intx-fix-overview","coinbase-exchange-drop-copy","kraken-fix-logon","kraken-cancel-all-after"],"risk":"low"},{"id":"c6","text":"The safe control record separates session recovery, order cancellation intent, final execution evidence, and manual override authority.","sourceIds":["coinbase-intx-fix-overview","coinbase-exchange-drop-copy","kraken-fix-logon","kraken-cancel-all-after"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-collateral-appchain-interoperability-readiness-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-06T05:58:00.000Z","updatedAt":"2026-10-06T05:58:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Collateral AppChain Interoperability Readiness Map","zh-Hans":"DTCC Collateral AppChain 互操作性准备地图"},"summary":{"en":"DTCC's Collateral AppChain material should be read as institutional collateral-infrastructure evidence, not as proof that every tokenized asset is eligible collateral.","zh-Hans":"DTCC Collateral AppChain 互操作性准备地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"DTCC describes its Collateral AppChain as supporting collateral mobility, 24/7 collateral operations, visibility and operational efficiency.","sourceIds":["dtcc-collateral-appchain"],"risk":"medium"},{"id":"c2","text":"DTCC's 2026 production-infrastructure article says the Collateral AppChain is a deployment layer for a multi-asset collateral ecosystem.","sourceIds":["dtcc-production-infrastructure"],"risk":"medium"},{"id":"c3","text":"DTCC's interoperability article says tokenization is moving from experimentation to implementation and that interoperability matters for institutional digital assets, cash and collateral.","sourceIds":["dtcc-interoperability"],"risk":"medium"},{"id":"c4","text":"DTCC material does not by itself prove that a user's specific asset is eligible, transferable, settled or accepted by a counterparty.","sourceIds":["dtcc-collateral-appchain","dtcc-production-infrastructure"],"risk":"low"},{"id":"c5","text":"Collateral mobility requires a record of asset type, rule set, network, custodian or recordkeeper, and exception workflow.","sourceIds":["dtcc-collateral-appchain","dtcc-interoperability"],"risk":"low"},{"id":"c6","text":"The safe decision record separates infrastructure capability from account-specific collateral availability.","sourceIds":["dtcc-collateral-appchain","dtcc-production-infrastructure","dtcc-interoperability"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dydx-indexer-websocket-subaccount-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-06T05:58:00.000Z","updatedAt":"2026-10-06T05:58:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"dYdX Indexer WebSocket and Subaccount Readiness Checklist","zh-Hans":"dYdX Indexer WebSocket 与子账户准备清单"},"summary":{"en":"dYdX v4 indexer evidence should be treated as an application data-readiness question, not as proof that a wallet is approved or a trade is safe.","zh-Hans":"dYdX Indexer WebSocket 与子账户准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"dYdX IndexerClient documentation shows initialization with IndexerConfig and public indexer HTTP/WebSocket endpoints.","sourceIds":["dydx-indexer-client"],"risk":"medium"},{"id":"c2","text":"The dYdX v4-chain indexer README documents WebSocket subscriptions including v4_markets, v4_orderbook and v4_subaccounts.","sourceIds":["dydx-v4-indexer-readme"],"risk":"medium"},{"id":"c3","text":"The public dYdX Indexer API documentation exposes account, subaccount, market, orderbook, fill, funding and compliance-screen routes.","sourceIds":["dydx-indexer-api"],"risk":"medium"},{"id":"c4","text":"Indexer availability does not prove a wallet's legal eligibility, compliance state, margin sufficiency or order execution outcome.","sourceIds":["dydx-indexer-client","dydx-indexer-api"],"risk":"low"},{"id":"c5","text":"A connected websocket should be paired with REST backfill for gap recovery and incident evidence.","sourceIds":["dydx-v4-indexer-readme","dydx-indexer-api"],"risk":"low"},{"id":"c6","text":"The safe rollout record keeps endpoint, channel, subaccount identifier, compliance-screen result and fallback route separate.","sourceIds":["dydx-indexer-client","dydx-v4-indexer-readme","dydx-indexer-api"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-use-drift-deposit-withdraw-borrow-lend-wallet-controls-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-06T05:58:00.000Z","updatedAt":"2026-10-06T05:58:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"How to Use Drift Deposits, Withdrawals and Borrow/Lend Controls Safely","zh-Hans":"如何安全使用 Drift 充值、提现与借贷控制"},"summary":{"en":"Drift onboarding is a wallet, collateral and margin workflow, not a credential-collecting exchange registration flow.","zh-Hans":"如何安全使用 Drift 充值、提现与借贷控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Drift's wallet setup guide says users connect a wallet, sign a confirmation message, pay a one-time setup fee and deposit funds before trading.","sourceIds":["drift-wallet-setup"],"risk":"medium"},{"id":"c2","text":"Drift's deposit and withdrawal guide says users need SOL for transactions and can deposit supported collateral such as USDC or SOL.","sourceIds":["drift-deposit-withdraw"],"risk":"medium"},{"id":"c3","text":"Drift's deposit and withdrawal guide says withdrawal amounts cannot exceed the account's available balance and require wallet transaction confirmation.","sourceIds":["drift-deposit-withdraw"],"risk":"medium"},{"id":"c4","text":"Drift's borrow/lend guide says deposited assets can act as collateral, with allowed borrowing varying by collateral type.","sourceIds":["drift-borrow-lend"],"risk":"low"},{"id":"c5","text":"Drift's borrow/lend guide lists smart-contract risk, bad debt and interest-rate risk as risk categories.","sourceIds":["drift-borrow-lend"],"risk":"low"},{"id":"c6","text":"A successful wallet connection does not prove margin safety, collateral suitability, yield continuity, tax treatment or recovery from a mistaken transaction.","sourceIds":["drift-wallet-setup","drift-deposit-withdraw","drift-borrow-lend"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-kraken-okx-cancel-all-after-order-safety-controls","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-06T02:58:00.000Z","updatedAt":"2026-10-06T02:58:00.000Z","readTime":"22 min","author":"NexuAlpha Research Desk","title":{"en":"Binance, Kraken and OKX Cancel-All-After Order Safety Controls","zh-Hans":"Binance、Kraken 与 OKX Cancel-All-After 订单安全控制"},"summary":{"en":"Binance, Kraken and OKX expose different order-cancellation safety controls, so an automation runbook should separate immediate cancel-all actions from timer-based cancel-on-disconnect controls.","zh-Hans":"Binance、Kraken 与 OKX Cancel-All-After 订单安全控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance Spot WebSocket API documentation includes openOrders.cancelAll for cancelling all open orders on one symbol.","sourceIds":["binance-ws-trade-cancel-all"],"risk":"medium"},{"id":"c2","text":"Kraken official WebSocket documentation describes cancelAllOrdersAfter as an authenticated cancel-on-disconnect control.","sourceIds":["kraken-cancel-on-disconnect"],"risk":"medium"},{"id":"c3","text":"OKX API documentation includes a cancel-all-after endpoint under its order-book trading API.","sourceIds":["okx-cancel-all-after"],"risk":"medium"},{"id":"c4","text":"Binance signed endpoints require timestamp and recvWindow controls, so request timing is part of cancellation safety evidence.","sourceIds":["binance-spot-rest-timing"],"risk":"low"},{"id":"c5","text":"A cancel request or timer acknowledgement does not alone prove that every private order reached a terminal cancelled state.","sourceIds":["binance-ws-trade-cancel-all","kraken-cancel-on-disconnect","okx-cancel-all-after"],"risk":"low"},{"id":"c6","text":"The safe decision record keeps venue acknowledgement, final order-state query, reconnect gap and manual pause authority separate.","sourceIds":["binance-ws-trade-cancel-all","kraken-cancel-on-disconnect","okx-cancel-all-after","binance-spot-rest-timing"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-signed-endpoint-percent-encoding-invalid-signature-migration","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-06T02:58:00.000Z","updatedAt":"2026-10-06T02:58:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Signed-Endpoint Percent-Encoding Migration Checklist","zh-Hans":"Binance 签名端点 Percent-Encoding 迁移清单"},"summary":{"en":"Binance developer documentation now makes percent-encoding part of the signed-payload control surface for affected REST examples, and the Spot Block Matching changelog warns that requests not following the order will be rejected.","zh-Hans":"Binance 签名端点 Percent-Encoding 迁移清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance Spot Block Matching changelog states that a REST API signing change will require percent-encoding payloads before computing signatures and warns of INVALID_SIGNATURE rejection for non-compliant requests.","sourceIds":["binance-spot-block-matching-changelog"],"risk":"medium"},{"id":"c2","text":"Binance General REST API Information documents SIGNED endpoints, timestamp, recvWindow and signature examples.","sourceIds":["binance-spot-rest-api"],"risk":"medium"},{"id":"c3","text":"Binance REST API documentation includes examples for HMAC, RSA and Ed25519 signing and explicitly addresses non-ASCII characters in signing payloads.","sourceIds":["binance-spot-rest-api"],"risk":"medium"},{"id":"c4","text":"Binance Rebate changelog repeats the same percent-encoding warning for signed REST API behavior.","sourceIds":["binance-rebate-changelog"],"risk":"low"},{"id":"c5","text":"A local signature unit test passing on ASCII-only fixtures does not prove that non-ASCII symbols, encoded payloads or body-plus-query concatenation are handled correctly.","sourceIds":["binance-spot-rest-api","binance-spot-block-matching-changelog"],"risk":"low"},{"id":"c6","text":"The migration should be treated as a signing-library compatibility test, not as a new trading recommendation or fee claim.","sourceIds":["binance-spot-rest-api","binance-spot-block-matching-changelog","binance-rebate-changelog"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-stablecoin-tokenisation-trust-money-2026-policy-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-06T02:58:00.000Z","updatedAt":"2026-10-06T02:58:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"BIS 2026 Stablecoin and Tokenisation Trust-in-Money Policy Map","zh-Hans":"BIS 2026 稳定币与代币化信任货币政策地图"},"summary":{"en":"BIS 2026 materials frame stablecoins and tokenisation as a trust-in-money question rather than a simple technology adoption story.","zh-Hans":"BIS 2026 材料把稳定币与代币化放在“货币信任”问题中，而不是简单的技术采用叙事。BIS 表示，稳定币展示了部分代币化潜力，但在关键货币属性上仍有不足；把代币化纳入双层货币体系，则可能保留央行货币锚。"},"claims":[{"id":"c1","text":"BIS states that preserving trust in money is central to the next-generation monetary and financial system.","sourceIds":["bis-trust-money-release"],"risk":"medium"},{"id":"c2","text":"BIS 2026 materials describe stablecoins as showing some tokenisation potential while also falling short on key properties of money.","sourceIds":["bis-trust-money-release","bis-annual-economic-report-2026"],"risk":"medium"},{"id":"c3","text":"BIS materials frame tokenisation inside the current two-tier system as a way to preserve the central-bank money anchor.","sourceIds":["bis-trust-money-release","bis-annual-economic-report-2026"],"risk":"medium"},{"id":"c4","text":"BIS Working Paper 1377 says translating blockchain data into meaningful economic measures is challenging and method dependent.","sourceIds":["bis-hidden-complexity-wp1377"],"risk":"low"},{"id":"c5","text":"FSI summary materials describe implementation gaps and jurisdictional variation in cryptoasset and stablecoin regulatory frameworks.","sourceIds":["fsi-crypto-stablecoin-framework-summary"],"risk":"low"},{"id":"c6","text":"None of these institutional sources proves that a specific exchange product, token, issuer, wallet or jurisdiction-specific route is approved for a user.","sourceIds":["bis-trust-money-release","bis-annual-economic-report-2026","bis-hidden-complexity-wp1377","fsi-crypto-stablecoin-framework-summary"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-status-api-maintenance-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-06T02:58:00.000Z","updatedAt":"2026-10-06T02:58:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange Status API and Maintenance Disclosure Radar","zh-Hans":"交易所状态 API 与维护披露雷达"},"summary":{"en":"Exchange status pages and status APIs are useful incident evidence, but they do not prove account-specific execution, withdrawal availability or compensation.","zh-Hans":"交易所状态 API 与维护披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Status API documentation exposes programmatic status endpoints such as status and components through its public status page API.","sourceIds":["coinbase-status-api"],"risk":"medium"},{"id":"c2","text":"Kraken Status API documentation exposes summary, status, components, incidents and scheduled-maintenance endpoint examples.","sourceIds":["kraken-status-api"],"risk":"medium"},{"id":"c3","text":"OKX publishes a public status page for system maintenance, issue descriptions and deposit or withdrawal status.","sourceIds":["okx-status-page"],"risk":"medium"},{"id":"c4","text":"OKX API documentation includes a system-status API route for exchange status data.","sourceIds":["okx-system-status-api"],"risk":"low"},{"id":"c5","text":"A green component status does not prove that a private account, symbol, region, wallet route or API key can act successfully.","sourceIds":["coinbase-status-api","kraken-status-api","okx-status-page"],"risk":"low"},{"id":"c6","text":"A responsible status radar separates public component status, scheduled maintenance, private account checks and incident stop rules.","sourceIds":["coinbase-status-api","kraken-status-api","okx-status-page","okx-system-status-api"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-use-aerodrome-liquidity-pools-gauges-and-wallet-controls","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-06T02:58:00.000Z","updatedAt":"2026-10-06T02:58:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"How to Use Aerodrome Liquidity Pools, Gauges and Wallet Controls Safely","zh-Hans":"如何安全使用 Aerodrome 流动性池、Gauge 与钱包控制"},"summary":{"en":"Aerodrome onboarding should be described as wallet-and-liquidity setup, not account registration.","zh-Hans":"如何安全使用 Aerodrome 流动性池、Gauge 与钱包控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Aerodrome's official documentation describes Aerodrome as a decentralized exchange and liquidity hub on Base.","sourceIds":["aerodrome-docs"],"risk":"medium"},{"id":"c2","text":"Aerodrome documentation describes gauges as smart contracts connected to liquidity pools that coordinate emissions, votes and rewards.","sourceIds":["aerodrome-docs","aerodrome-contracts-spec"],"risk":"medium"},{"id":"c3","text":"Aerodrome liquidity documentation distinguishes stable pools, volatile pools and concentrated liquidity pools.","sourceIds":["aerodrome-liquidity-docs"],"risk":"medium"},{"id":"c4","text":"Aerodrome liquidity documentation explains that APR calculations differ for basic and concentrated pools when staking is available.","sourceIds":["aerodrome-liquidity-docs"],"risk":"low"},{"id":"c5","text":"Aerodrome contract specification materials describe pools, gauges and related factory contracts at an implementation level.","sourceIds":["aerodrome-contracts-spec"],"risk":"low"},{"id":"c6","text":"A DEX wallet connection is not an exchange account registration and does not require credential, KYC file, private key or seed phrase collection.","sourceIds":["aerodrome-docs","aerodrome-liquidity-docs","aerodrome-contracts-spec"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-user-data-stream-reconnect-gap-backfill-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-05T23:58:00.000Z","updatedAt":"2026-10-05T23:58:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Binance User Data Stream Reconnect Gap and REST Backfill Checklist","zh-Hans":"Binance User Data Stream 重连缺口与 REST 回补清单"},"summary":{"en":"A Binance User Data Stream reconnect plan should prove more than transport recovery. Binance documentation describes account and order updates through User Data Stream, REST request security requirements, WebSocket API.","zh-Hans":"Binance User Data Stream 重连缺口与 REST 回补清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance User Data Stream documentation is the official venue surface for private account and order event streaming.","sourceIds":["binance-user-data-stream"],"risk":"medium"},{"id":"c2","text":"Binance REST request security documentation describes signed endpoint requirements and timestamp handling for private requests.","sourceIds":["binance-request-security"],"risk":"medium"},{"id":"c3","text":"Binance WebSocket API documentation describes WebSocket API operating information separate from REST calls.","sourceIds":["binance-websocket-api-info"],"risk":"medium"},{"id":"c4","text":"Binance API changelog documentation is the official place to review API changes over time.","sourceIds":["binance-api-changelog"],"risk":"low"},{"id":"c5","text":"A reconnect checklist should distinguish stream transport recovery from account-state reconciliation.","sourceIds":["binance-user-data-stream","binance-request-security","binance-websocket-api-info"],"risk":"low"},{"id":"c6","text":"Evidence should not expose API secrets, signatures, private balances, withdrawal permissions, 2FA codes or identity data.","sourceIds":["binance-request-security","binance-user-data-stream"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-fsb-fast-payment-stablecoin-governance-oversight-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-05T23:58:00.000Z","updatedAt":"2026-10-05T23:58:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"BIS and FSB Fast-Payment and Stablecoin Governance Oversight Map","zh-Hans":"BIS 与 FSB 快速支付、稳定币治理监管地图"},"summary":{"en":"BIS and FSB materials make cross-border payment speed a governance question, not a standalone success metric.","zh-Hans":"BIS 与 FSB 快速支付、稳定币治理监管地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"BIS CPMI has published work on linking fast payment systems across borders with governance and oversight considerations.","sourceIds":["bis-cpmi-fast-payments"],"risk":"medium"},{"id":"c2","text":"BIS analysis of the next-generation monetary and financial system discusses tokenisation and stablecoins as part of broader monetary and financial infrastructure questions.","sourceIds":["bis-next-generation-system"],"risk":"medium"},{"id":"c3","text":"The FSB maintains a policy workstream on crypto-assets and global stablecoins.","sourceIds":["fsb-crypto-stablecoins"],"risk":"medium"},{"id":"c4","text":"Cross-border payment speed does not by itself prove legal finality, consumer protection or dispute recourse.","sourceIds":["bis-cpmi-fast-payments","fsb-crypto-stablecoins"],"risk":"low"},{"id":"c5","text":"A stablecoin or payment-bridge risk review should identify operator governance, interoperability, AML and sanctions controls, resilience and recourse.","sourceIds":["bis-cpmi-fast-payments","bis-next-generation-system","fsb-crypto-stablecoins"],"risk":"low"},{"id":"c6","text":"This article does not claim that a specific stablecoin, bridge, bank token or payment system is approved, safe, cheap, instant or universally available.","sourceIds":["bis-cpmi-fast-payments","bis-next-generation-system","fsb-crypto-stablecoins"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-kraken-okx-websocket-cancel-state-reconciliation-controls","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-05T23:58:00.000Z","updatedAt":"2026-10-05T23:58:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase, Kraken and OKX WebSocket Cancel-State Reconciliation Controls","zh-Hans":"Coinbase、Kraken 与 OKX WebSocket 撤单状态对账控制"},"summary":{"en":"Coinbase, Kraken and OKX expose different WebSocket surfaces for order lifecycle monitoring, so a cancel-state runbook should not normalize every message into one generic event.","zh-Hans":"Coinbase、Kraken 与 OKX WebSocket 撤单状态对账控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Exchange documentation describes WebSocket channels for real-time exchange data and channel-specific subscriptions.","sourceIds":["coinbase-websocket-channels"],"risk":"medium"},{"id":"c2","text":"Kraken WebSocket v2 documentation includes add_order as a trading method with authenticated order placement semantics.","sourceIds":["kraken-ws-add-order"],"risk":"medium"},{"id":"c3","text":"Kraken WebSocket v2 documentation includes cancel_order as a separate method for cancelling open orders.","sourceIds":["kraken-ws-cancel-order"],"risk":"medium"},{"id":"c4","text":"OKX API documentation includes a trading WebSocket order channel for order updates under its API guide.","sourceIds":["okx-order-channel"],"risk":"low"},{"id":"c5","text":"Cancel-state reconciliation must distinguish an acknowledgement message from final venue order state.","sourceIds":["coinbase-websocket-channels","kraken-ws-cancel-order","okx-order-channel"],"risk":"low"},{"id":"c6","text":"A local bot log, UI toast or user screenshot is not enough to prove the venue has accepted, rejected, filled or cancelled the order.","sourceIds":["coinbase-websocket-channels","kraken-ws-add-order","kraken-ws-cancel-order","okx-order-channel"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-add-uniswap-v3-liquidity-wallet-approval-position-controls","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-05T23:58:00.000Z","updatedAt":"2026-10-05T23:58:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"How to Add Uniswap v3 Liquidity with Wallet Approval and Position Controls","zh-Hans":"如何添加 Uniswap v3 流动性：钱包授权与头寸控制清单"},"summary":{"en":"Uniswap v3 onboarding is a wallet-and-contract workflow, not custodial account registration.","zh-Hans":"如何添加 Uniswap v3 流动性：钱包授权与头寸控制清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Uniswap v3 documentation includes setup guidance for providing liquidity.","sourceIds":["uniswap-v3-setup"],"risk":"medium"},{"id":"c2","text":"Uniswap v3 documentation includes a guide for minting a liquidity position.","sourceIds":["uniswap-v3-mint"],"risk":"medium"},{"id":"c3","text":"Uniswap v3 documentation includes guidance for increasing liquidity in a position.","sourceIds":["uniswap-v3-increase"],"risk":"medium"},{"id":"c4","text":"Uniswap v3 documentation includes a guide for collecting fees.","sourceIds":["uniswap-v3-collect"],"risk":"low"},{"id":"c5","text":"Uniswap v3 documentation includes single-hop swap guidance, which is separate from liquidity provision.","sourceIds":["uniswap-v3-single-swap"],"risk":"low"},{"id":"c6","text":"A Uniswap v3 onboarding tutorial should describe wallet signing boundaries and should not describe this as custodial exchange account registration.","sourceIds":["uniswap-v3-setup","uniswap-v3-mint","uniswap-v3-increase","uniswap-v3-collect"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-transfer-agent-tokenized-security-recordkeeping-boundary-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-05T23:58:00.000Z","updatedAt":"2026-10-05T23:58:00.000Z","readTime":"22 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Transfer Agent Rules and Tokenized Security Recordkeeping Boundary Map","zh-Hans":"SEC Transfer Agent Rules 与代币化证券记录边界地图"},"summary":{"en":"The SEC transfer-agent modernization proposal and the SEC staff statement on tokenized securities point to the same boundary: a token record is not automatically the complete legal ownership record.","zh-Hans":"SEC Transfer Agent Rules 与代币化证券记录边界地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"The SEC rulemaking activity page lists Transfer Agent Rules as a proposed rule under the relevant 2026 rulemaking activity.","sourceIds":["sec-rulemaking-activity"],"risk":"medium"},{"id":"c2","text":"The SEC proposed Transfer Agent Rules release addresses registration, reporting and recordkeeping requirements for registered transfer agents.","sourceIds":["sec-transfer-agent-rules-pdf"],"risk":"medium"},{"id":"c3","text":"The SEC proposed release discusses tokenization model reporting in the context of transfer-agent activity.","sourceIds":["sec-transfer-agent-rules-pdf"],"risk":"medium"},{"id":"c4","text":"The SEC tokenized-securities statement describes issuer or agent systems using onchain and offchain records for tokenized securities.","sourceIds":["sec-tokenized-securities-statement"],"risk":"low"},{"id":"c5","text":"The statement discusses the master securityholder file and the relationship between token records and security ownership records.","sourceIds":["sec-tokenized-securities-statement"],"risk":"low"},{"id":"c6","text":"A tokenized-security checklist should not treat wallet possession, UI balance or third-party wrapper language as proof of issuer-recognized holder rights without the official recordkeeping layer.","sourceIds":["sec-transfer-agent-rules-pdf","sec-tokenized-securities-statement"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-pay-order-query-signature-reconciliation-control-map","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-05T21:05:00.000Z","updatedAt":"2026-10-05T21:05:00.000Z","readTime":"22 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Pay Order Query and Signature Reconciliation Control Map","zh-Hans":"Binance Pay 订单查询与签名对账控制地图"},"summary":{"en":"A Binance Pay merchant integration should treat order creation, request signing and order query as separate controls.","zh-Hans":"Binance Pay 订单查询与签名对账控制地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance Pay common rules describe HTTPS transfer, JSON request and response format, UTF-8 encoding and HMAC-SHA512 signature requirements.","sourceIds":["binance-pay-common-rules"],"risk":"medium"},{"id":"c2","text":"Binance Pay request headers include BinancePay-Timestamp, BinancePay-Nonce, BinancePay-Certificate-SN and BinancePay-Signature.","sourceIds":["binance-pay-common-rules"],"risk":"medium"},{"id":"c3","text":"Binance Pay common rules state that request timestamps are processed within a narrow time window and include INVALID_TIMESTAMP as a business error.","sourceIds":["binance-pay-common-rules"],"risk":"medium"},{"id":"c4","text":"Binance Pay Query Order can use either merchantTradeNo or prepayId when one of the two identifiers is present.","sourceIds":["binance-pay-query-order"],"risk":"low"},{"id":"c5","text":"Binance Pay Query Order response fields include merchantId, prepayId, transactionId, merchantTradeNo, tradeType and status.","sourceIds":["binance-pay-query-order"],"risk":"low"},{"id":"c6","text":"A merchant reconciliation checklist should not treat a local order row, a callback payload or a user screenshot as final payment evidence without querying the official order state.","sourceIds":["binance-pay-common-rules","binance-pay-query-order"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"circle-usdc-chain-support-vs-lido-token-wrapper-asset-route-boundary","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-05T21:05:00.000Z","updatedAt":"2026-10-05T21:05:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"Circle USDC Chain Support vs Lido Token Wrappers: Asset Route Boundary Map","zh-Hans":"Circle USDC 支持链与 Lido Token Wrapper：资产路径边界地图"},"summary":{"en":"USDC chain support and liquid-staking token wrappers solve different asset-route problems. Circle documentation lists supported chains and warns that unsupported tokens or unsupported appchain transfers may not be credited, while.","zh-Hans":"Circle USDC 支持链与 Lido Token Wrapper：资产路径边界地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Circle documentation lists specific chains and API chain codes for supported USDC and EURC flows.","sourceIds":["circle-supported-chains"],"risk":"medium"},{"id":"c2","text":"Circle supported-chain documentation warns against sending unsupported tokens or unsupported appchain transfers to Circle Mint addresses.","sourceIds":["circle-supported-chains"],"risk":"medium"},{"id":"c3","text":"Circle's multichain USDC page describes USDC availability across multiple networks.","sourceIds":["circle-multichain-usdc"],"risk":"medium"},{"id":"c4","text":"Lido documentation describes integration considerations for stETH and wrapped stETH.","sourceIds":["lido-token-integration"],"risk":"low"},{"id":"c5","text":"BIS commentary distinguishes stablecoins and tokenised deposits by monetary properties such as singleness, interoperability and integrity.","sourceIds":["bis-tokenised-deposits-stablecoins"],"risk":"low"},{"id":"c6","text":"A route checklist should not treat native USDC support, bridged USDC, stETH and wstETH as interchangeable assets.","sourceIds":["circle-supported-chains","lido-token-integration","bis-tokenised-deposits-stablecoins"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-onboard-binance-pay-merchant-api-keys-order-query-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-05T21:05:00.000Z","updatedAt":"2026-10-05T21:05:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"How to Onboard Binance Pay Merchant API Keys and Order Query Safely","zh-Hans":"如何安全完成 Binance Pay 商户 API Key 与订单查询上线"},"summary":{"en":"A safe Binance Pay merchant onboarding path starts with merchant-account access, API identity key creation, request-signing verification and read-style order query testing before production fulfillment.","zh-Hans":"如何安全完成 Binance Pay 商户 API Key 与订单查询上线：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance Pay authentication documentation says API keys are managed in the Binance Merchant Admin Portal.","sourceIds":["binance-pay-authentication"],"risk":"medium"},{"id":"c2","text":"Binance Pay authentication documentation warns that secret API keys should not be shared in publicly accessible places.","sourceIds":["binance-pay-authentication"],"risk":"medium"},{"id":"c3","text":"Binance Pay common rules require HTTPS and HMAC-SHA512 signature checks for API requests.","sourceIds":["binance-pay-common-rules"],"risk":"medium"},{"id":"c4","text":"Binance Pay common rules define timestamp, nonce, certificate serial number and signature request headers.","sourceIds":["binance-pay-common-rules"],"risk":"low"},{"id":"c5","text":"Binance Pay Create Order V2 and Query Order documentation define merchant-side order creation and status-query workflows.","sourceIds":["binance-pay-create-order-v2","binance-pay-query-order"],"risk":"low"},{"id":"c6","text":"A merchant onboarding tutorial should not collect credentials or ask readers to paste secrets into evidence logs.","sourceIds":["binance-pay-authentication","binance-pay-common-rules"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-account-verification-api-key-permission-update-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-05T21:05:00.000Z","updatedAt":"2026-10-05T21:05:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken Account Verification, Profile Updates and API Key Permission Checklist","zh-Hans":"Kraken 账户验证、资料更新与 API Key 权限清单"},"summary":{"en":"Kraken account readiness is not a single login state. Kraken support documentation separates account information updates from verification levels, while Kraken API documentation exposes API key permissions, restrictions,.","zh-Hans":"Kraken 账户验证、资料更新与 API Key 权限清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Kraken support documentation describes user-facing account information update workflows separately from trading or API activity.","sourceIds":["kraken-update-account-info"],"risk":"medium"},{"id":"c2","text":"Kraken verification documentation describes account verification levels and related account capabilities.","sourceIds":["kraken-verification-levels"],"risk":"medium"},{"id":"c3","text":"Kraken Get API Key Info documentation lists API key permissions and restrictions.","sourceIds":["kraken-api-key-info"],"risk":"medium"},{"id":"c4","text":"Kraken Get API Key Info documentation includes validity, nonce window and last-used fields for the authenticated key.","sourceIds":["kraken-api-key-info"],"risk":"low"},{"id":"c5","text":"A Kraken readiness review should distinguish verified account status from API key permission scope.","sourceIds":["kraken-verification-levels","kraken-api-key-info"],"risk":"low"},{"id":"c6","text":"Evidence should not include API secrets, signatures, 2FA codes, identity documents or private support-ticket content.","sourceIds":["kraken-update-account-info","kraken-api-key-info"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"payment-api-signature-timestamp-status-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-05T21:05:00.000Z","updatedAt":"2026-10-05T21:05:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Payment API Signature, Timestamp and Status Disclosure Radar","zh-Hans":"支付 API 签名、时间戳与状态披露雷达"},"summary":{"en":"Public payment and account API documentation exposes different control evidence: Binance Pay documents signature headers, timestamp windows and order status; Kraken documents API key permissions, restrictions and last-used.","zh-Hans":"支付 API 签名、时间戳与状态披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance Pay common rules disclose signing requirements and timestamp-related request failures.","sourceIds":["binance-pay-common-rules"],"risk":"medium"},{"id":"c2","text":"Binance Pay Query Order discloses official order status fields.","sourceIds":["binance-pay-query-order"],"risk":"medium"},{"id":"c3","text":"Kraken Get API Key Info discloses permissions, restrictions, nonce window, validity and last-used fields.","sourceIds":["kraken-api-key-info"],"risk":"medium"},{"id":"c4","text":"Circle supported-chain documentation discloses which chain and currency pairs are supported by Circle Mint and related APIs.","sourceIds":["circle-supported-chains"],"risk":"low"},{"id":"c5","text":"Payment readiness evidence can be split into signing proof, permission proof, route support proof and status proof.","sourceIds":["binance-pay-common-rules","binance-pay-query-order","kraken-api-key-info","circle-supported-chains"],"risk":"low"},{"id":"c6","text":"A disclosure radar should not convert public documentation into a private account, payment or transfer success claim.","sourceIds":["binance-pay-common-rules","kraken-api-key-info","circle-supported-chains"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"aave-vs-lido-exit-path-health-factor-withdrawal-queue-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-05T12:05:00.000Z","updatedAt":"2026-10-05T12:05:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"Aave vs Lido Exit Paths: Health Factor, Withdrawal Queue and Liquidity Controls","zh-Hans":"Aave 与 Lido 退出路径对比：健康因子、提款队列与流动性控制"},"summary":{"en":"Aave and Lido expose very different exit controls even when both involve Ethereum assets. Aave documentation frames withdrawal around supplied assets, collateral use, health-factor impact and wallet transaction approval.","zh-Hans":"Aave 与 Lido 退出路径对比：健康因子、提款队列与流动性控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Aave market-operations documentation describes health-factor preview for actions including supply, borrow, repay and withdraw.","sourceIds":["aave-market-operations"],"risk":"medium"},{"id":"c2","text":"Aave withdrawal help says collateralized supplied tokens may require repayment or additional collateral to maintain a healthy balance before withdrawal.","sourceIds":["aave-withdraw"],"risk":"medium"},{"id":"c3","text":"Lido's WithdrawalQueueERC721 documentation describes a FIFO queue for stETH withdrawal requests and an unstETH NFT representing the position in the queue.","sourceIds":["lido-withdrawal-queue"],"risk":"medium"},{"id":"c4","text":"Lido documentation says the unstETH NFT is minted on request and burned on claim after finalization.","sourceIds":["lido-withdrawal-queue"],"risk":"low"},{"id":"c5","text":"Lido's Public Risk Disclosure separates protocol-level withdrawals from secondary-market transactions and describes timing and liquidity risks.","sourceIds":["lido-risk-disclosure"],"risk":"low"},{"id":"c6","text":"A user should not treat an Aave collateral withdrawal and a Lido stETH exit as the same operation even when both involve ETH exposure.","sourceIds":["aave-market-operations","aave-withdraw","lido-withdrawal-queue","lido-risk-disclosure"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-travel-rule-deposit-withdrawal-verification-checklist","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-05T12:05:00.000Z","updatedAt":"2026-10-05T12:05:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit Travel Rule Deposit and Withdrawal Verification Checklist","zh-Hans":"Bybit Travel Rule 入金与出金验证清单"},"summary":{"en":"Bybit Travel Rule checks should be treated as transfer-information controls, not as a trading feature.","zh-Hans":"Bybit Travel Rule 入金与出金验证清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit's Travel Rule FAQ says Travel Rule verification is required for crypto deposit and withdrawal transactions under local compliance requirements.","sourceIds":["bybit-travel-rule"],"risk":"medium"},{"id":"c2","text":"Bybit's Travel Rule FAQ distinguishes transfers involving exchanges or crypto service providers from private wallet contexts.","sourceIds":["bybit-travel-rule"],"risk":"medium"},{"id":"c3","text":"Bybit's on-chain withdrawal FAQ covers withdrawal actions and points users to real-time status checks for tokens or chains.","sourceIds":["bybit-withdrawal-faq"],"risk":"medium"},{"id":"c4","text":"Bybit's deposit and withdrawal hub groups crypto deposit, withdrawal, wallet maintenance and Travel Rule materials in the same support area.","sourceIds":["bybit-deposit-withdrawal-hub"],"risk":"low"},{"id":"c5","text":"A Travel Rule workflow can require transfer information but does not justify collecting passwords, 2FA codes, private keys or recovery phrases.","sourceIds":["bybit-travel-rule","bybit-withdrawal-faq"],"risk":"low"},{"id":"c6","text":"A user should verify asset, network, address, VASP or wallet category and transfer status before relying on a deposit or withdrawal path.","sourceIds":["bybit-travel-rule","bybit-withdrawal-faq","bybit-deposit-withdrawal-hub"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cftc-managed-pool-copy-trading-fraud-due-diligence-checklist","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-05T12:05:00.000Z","updatedAt":"2026-10-05T12:05:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC Managed-Pool Fraud and Copy-Trading Due-Diligence Checklist","zh-Hans":"CFTC 资金池欺诈与跟单交易尽调清单"},"summary":{"en":"Copy-trading or managed-pool offers should be checked against regulator fraud patterns before a user treats campaign language as protection.","zh-Hans":"CFTC 资金池欺诈与跟单交易尽调清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"The CFTC published a 2026 enforcement release charging a commodity pool operator and company with fraud.","sourceIds":["cftc-pool-fraud"],"risk":"medium"},{"id":"c2","text":"The FBI IC3 annual report provides official cybercrime and investment-fraud context for online financial scams.","sourceIds":["ic3-2025-report"],"risk":"medium"},{"id":"c3","text":"Bitget's official support article describes a CFD Copy Trading Rally promotion using first-trade loss protection language.","sourceIds":["bitget-copy-trading-rally"],"risk":"medium"},{"id":"c4","text":"Bitget's promotions section groups ongoing competitions and promotions separately from ordinary product documentation.","sourceIds":["bitget-promotions"],"risk":"low"},{"id":"c5","text":"A campaign or copy-trading page does not prove a third-party managed account, private signal seller or pool operator is safe.","sourceIds":["cftc-pool-fraud","ic3-2025-report","bitget-copy-trading-rally"],"risk":"low"},{"id":"c6","text":"Users should verify custody, authority, eligibility, loss-protection conditions, regulator evidence and stop rules before copying or delegating trades.","sourceIds":["cftc-pool-fraud","ic3-2025-report","bitget-copy-trading-rally","bitget-promotions"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"circle-gateway-vs-cctp-unified-balance-transfer-boundary-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-05T12:05:00.000Z","updatedAt":"2026-10-05T12:05:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Circle Gateway vs CCTP: Unified Balance and Burn-Mint Transfer Boundary Map","zh-Hans":"Circle Gateway 与 CCTP 对比：统一余额与 burn-mint 转账边界地图"},"summary":{"en":"Circle Gateway and CCTP should not be collapsed into one generic stablecoin bridge label. Circle says Gateway enables a unified USDC balance for supported crosschain access, while CCTP moves Circle-issued assets through native.","zh-Hans":"Circle Gateway 与 CCTP 对比：统一余额与 burn-mint 转账边界地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Circle's Gateway page describes Gateway as enabling a unified USDC balance and crosschain access on supported routes.","sourceIds":["circle-gateway"],"risk":"medium"},{"id":"c2","text":"Circle's Gateway page distinguishes Gateway from CCTP and points teams to product comparison guidance in developer docs.","sourceIds":["circle-gateway"],"risk":"medium"},{"id":"c3","text":"Circle's CCTP page describes CCTP as crosschain infrastructure using native burn-and-mint for Circle-issued assets such as USDC.","sourceIds":["circle-cctp"],"risk":"medium"},{"id":"c4","text":"Circle's CCTP page says CCTP V1 is legacy while CCTP V2 is the canonical CCTP path.","sourceIds":["circle-cctp"],"risk":"low"},{"id":"c5","text":"Circle Developer Terms describe developer-account, fee and service conditions that are separate from product marketing pages.","sourceIds":["circle-developer-terms"],"risk":"low"},{"id":"c6","text":"A developer should separate balance abstraction, burn-mint transfer, fee deduction, route support and settlement evidence before promising crosschain liquidity.","sourceIds":["circle-gateway","circle-cctp","circle-developer-terms"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-instant-loss-protection-compliance-claim-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-05T12:05:00.000Z","updatedAt":"2026-10-05T12:05:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Instant, Loss-Protection and Compliance Claim Disclosure Radar","zh-Hans":"Crypto 即时、损失保护与合规措辞披露雷达"},"summary":{"en":"NexuAlpha Radar flags three phrases that users often overread: instant access, loss protection and compliance verification.","zh-Hans":"Crypto 即时、损失保护与合规措辞披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Circle Gateway marketing describes unified USDC balance and fast supported-route crosschain access rather than universal liquidity under all conditions.","sourceIds":["circle-gateway"],"risk":"medium"},{"id":"c2","text":"Bitget's official campaign page uses first-trade loss protection wording in a copy-trading promotion context.","sourceIds":["bitget-copy-trading-rally"],"risk":"medium"},{"id":"c3","text":"Bybit's Travel Rule FAQ describes verification requirements for crypto deposit and withdrawal transactions under local compliance requirements.","sourceIds":["bybit-travel-rule"],"risk":"medium"},{"id":"c4","text":"Treasury's OFAC page describes a proposed rule to implement GENIUS Act sanctions compliance requirements for permitted payment stablecoin issuers.","sourceIds":["treasury-genius-ofac"],"risk":"low"},{"id":"c5","text":"Instant, loss-protection and compliance wording each requires account-specific and route-specific conditions before a user acts.","sourceIds":["circle-gateway","bitget-copy-trading-rally","bybit-travel-rule","treasury-genius-ofac"],"risk":"low"},{"id":"c6","text":"NexuAlpha should convert promotional or compliance wording into a decision checklist rather than a guarantee claim.","sourceIds":["circle-gateway","bitget-copy-trading-rally","bybit-travel-rule","treasury-genius-ofac"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"genius-act-stablecoin-aml-sanctions-cip-implementation-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-05T12:05:00.000Z","updatedAt":"2026-10-05T12:05:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"GENIUS Act Stablecoin AML, Sanctions and CIP Implementation Map","zh-Hans":"GENIUS Act 稳定币 AML、制裁与 CIP 实施地图"},"summary":{"en":"GENIUS Act stablecoin compliance should be read as an issuer and supervisory implementation question, not as a user guarantee that any stablecoin route is safe.","zh-Hans":"GENIUS Act 稳定币 AML、制裁与 CIP 实施地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Treasury's OFAC recent action page describes a proposed rule to implement GENIUS Act sanctions compliance requirements for permitted payment stablecoin issuers.","sourceIds":["treasury-genius-ofac"],"risk":"medium"},{"id":"c2","text":"Treasury's GENIUS Act congressional report discusses technologies to counter illicit finance involving digital assets.","sourceIds":["treasury-genius-report"],"risk":"medium"},{"id":"c3","text":"The Federal Reserve published a statement on proposed customer-identification-program requirements for payment stablecoin issuers.","sourceIds":["federal-reserve-cip-statement"],"risk":"medium"},{"id":"c4","text":"Federal Reserve statement language raises concerns about illicit finance risks in secondary market stablecoin transactions.","sourceIds":["federal-reserve-cip-statement"],"risk":"low"},{"id":"c5","text":"A proposed rule or report does not prove a specific wallet, issuer, exchange route or transfer is approved for a user.","sourceIds":["treasury-genius-ofac","treasury-genius-report","federal-reserve-cip-statement"],"risk":"low"},{"id":"c6","text":"Users and operators should separate issuer compliance duties from account-specific transfer, identity and sanctions-screening evidence.","sourceIds":["treasury-genius-ofac","treasury-genius-report","federal-reserve-cip-statement"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-onboard-bybit-travel-rule-wallet-verification-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-05T12:05:00.000Z","updatedAt":"2026-10-05T12:05:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"How to Onboard Bybit Travel Rule Wallet Verification Without Exposing Secrets","zh-Hans":"如何安全完成 Bybit Travel Rule 钱包验证而不暴露秘密"},"summary":{"en":"A safe Bybit Travel Rule onboarding flow starts after the user is already inside the official Bybit account and transfer flow.","zh-Hans":"如何安全完成 Bybit Travel Rule 钱包验证而不暴露秘密：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit's Travel Rule FAQ says Travel Rule verification is required for crypto deposit and withdrawal transactions under local compliance requirements.","sourceIds":["bybit-travel-rule"],"risk":"medium"},{"id":"c2","text":"Bybit's Travel Rule FAQ describes transfer contexts involving exchanges or crypto service providers and wallet verification conditions.","sourceIds":["bybit-travel-rule"],"risk":"medium"},{"id":"c3","text":"Bybit's on-chain withdrawal FAQ provides withdrawal-related transfer context and status-checking boundaries.","sourceIds":["bybit-withdrawal-faq"],"risk":"medium"},{"id":"c4","text":"Bybit's deposit/withdrawal topic hub groups deposit, withdrawal, wallet maintenance and Travel Rule materials in one official support area.","sourceIds":["bybit-deposit-withdrawal-hub"],"risk":"low"},{"id":"c5","text":"A safe onboarding tutorial must not ask users to paste passwords, 2FA codes, private keys, recovery phrases or KYC documents into NexuAlpha.","sourceIds":["bybit-travel-rule","bybit-withdrawal-faq","bybit-deposit-withdrawal-hub"],"risk":"low"},{"id":"c6","text":"A user should treat Travel Rule completion as one transfer-control step, not as proof that the asset, network or account is universally available.","sourceIds":["bybit-travel-rule","bybit-withdrawal-faq","bybit-deposit-withdrawal-hub"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-vs-okx-order-book-sequence-gap-recovery-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-05T09:05:00.000Z","updatedAt":"2026-10-05T09:05:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit vs OKX Order Book Sequence and Gap Recovery Controls","zh-Hans":"Bybit 与 OKX 订单簿序列和断档恢复控制对比"},"summary":{"en":"Bybit and OKX order book WebSocket feeds should be compared as sequencing systems before they are compared as latency feeds.","zh-Hans":"Bybit 与 OKX 订单簿序列和断档恢复控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit's V5 orderbook WebSocket documentation describes snapshot and delta messages for local order book maintenance.","sourceIds":["bybit-orderbook"],"risk":"medium"},{"id":"c2","text":"Bybit's orderbook payload includes an update ID, cross sequence field and matching-engine timestamp fields for sequencing analysis.","sourceIds":["bybit-orderbook"],"risk":"medium"},{"id":"c3","text":"Bybit's full orderbook documentation also describes seq as a cross sequence that can compare generation order across orderbook levels.","sourceIds":["bybit-full-orderbook"],"risk":"medium"},{"id":"c4","text":"OKX API V5 documentation includes WebSocket order book channels and documents sequencing fields such as seqId and prevSeqId for order book continuity.","sourceIds":["okx-docs-v5"],"risk":"low"},{"id":"c5","text":"OKX documentation states that at least some order book variants do not return checksum and rely on seqId or prevSeqId sequencing instead.","sourceIds":["okx-docs-v5"],"risk":"low"},{"id":"c6","text":"A local order book implementation must define bootstrap, continuity checks, stale-data handling, reconnect behavior and downgrade behavior before using the book for execution.","sourceIds":["bybit-orderbook","okx-docs-v5","bybit-full-orderbook"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-onramp-quote-order-status-fee-network-risk-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-05T09:05:00.000Z","updatedAt":"2026-10-05T09:05:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Onramp Quote, Order Status, Fee and Network Risk Checklist","zh-Hans":"Coinbase Onramp 报价、订单状态、费用与网络风险清单"},"summary":{"en":"Coinbase Onramp integration should treat a quote as an estimate and an order lookup as the later evidence layer.","zh-Hans":"Coinbase Onramp 报价、订单状态、费用与网络风险清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase's Onramp Quote API documentation describes quote inputs such as purchase currency, payment amount, payment currency, payment method and country.","sourceIds":["coinbase-onramp-quotes"],"risk":"medium"},{"id":"c2","text":"The Coinbase quote documentation says the returned quote is an estimate and does not guarantee completion or final fees.","sourceIds":["coinbase-onramp-quotes"],"risk":"medium"},{"id":"c3","text":"The quote response fields include payment total, payment subtotal, purchase amount, Coinbase fee, network fee, quote ID and, when applicable, an onramp URL.","sourceIds":["coinbase-onramp-quotes"],"risk":"medium"},{"id":"c4","text":"Coinbase's order-by-ID endpoint documents order status, payment totals, purchase amount, fees, destination address, destination network and transaction hash fields.","sourceIds":["coinbase-onramp-order"],"risk":"low"},{"id":"c5","text":"Coinbase payment-method sandbox documentation says the sandbox uses pre-provisioned mock payment methods and does not connect to real bank or payment networks.","sourceIds":["coinbase-payments-sandbox"],"risk":"low"},{"id":"c6","text":"An onramp workflow should not release product value solely from an initial quote; it should reconcile order status and destination evidence.","sourceIds":["coinbase-onramp-quotes","coinbase-onramp-order","coinbase-payments-sandbox"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-tokenization-service-same-cusip-control-authority-risk-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-05T09:05:00.000Z","updatedAt":"2026-10-05T09:05:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Tokenization Service Same-CUSIP and Control Authority Risk Map","zh-Hans":"DTCC Tokenization Service 同 CUSIP 与控制权限风险地图"},"summary":{"en":"DTCC's Tokenization Service should be read as market-infrastructure tokenization, not a generic wrapper-token claim.","zh-Hans":"DTCC Tokenization Service 同 CUSIP 与控制权限风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"DTCC's Tokenization Service page says tokenized DTC assets can move between traditional and blockchain ecosystems using the same CUSIP.","sourceIds":["dtcc-tokenization"],"risk":"medium"},{"id":"c2","text":"DTCC states that DTC-issued tokens are designed to represent the same legal rights, economic interest and investor protections associated with the underlying securities.","sourceIds":["dtcc-tokenization"],"risk":"medium"},{"id":"c3","text":"DTCC describes controls including mint, burn, pause and clawback functionality for DTC-issued tokens.","sourceIds":["dtcc-tokenization"],"risk":"medium"},{"id":"c4","text":"The SEC's tokenized-securities statement says tokenized securities models vary and may be issuer-sponsored or third-party sponsored.","sourceIds":["sec-tokenized-securities"],"risk":"low"},{"id":"c5","text":"The SEC transfer-agent proposal page says proposed updates reflect electronic recordkeeping, communications and services provided to issuers, investors and intermediaries.","sourceIds":["sec-transfer-agent-rules"],"risk":"low"},{"id":"c6","text":"A tokenized-asset decision record should separate recordkeeping authority, network mobility, control functions and investor-rights language.","sourceIds":["dtcc-tokenization","sec-tokenized-securities","sec-transfer-agent-rules"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-onboard-aave-v3-supply-wallet-approval-and-risk-parameters","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-05T09:05:00.000Z","updatedAt":"2026-10-05T09:05:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"How to Onboard Aave V3 Supply With Wallet Approval and Risk Parameters","zh-Hans":"如何安全上手 Aave V3 Supply：钱包授权与风险参数清单"},"summary":{"en":"Aave V3 onboarding should be framed as wallet approval, reserve-status and risk-parameter verification, not as a yield promise.","zh-Hans":"如何安全上手 Aave V3 Supply：钱包授权与风险参数清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Aave V3 documentation describes Aave as a non-custodial liquidity protocol with supply and borrow functionality.","sourceIds":["aave-v3-overview"],"risk":"medium"},{"id":"c2","text":"Aave Market Operations documentation covers lending and borrowing actions such as supply, borrow, repay and withdraw.","sourceIds":["aave-market-operations"],"risk":"medium"},{"id":"c3","text":"Aave Market Operations documentation includes health factor preview as part of advanced operation planning.","sourceIds":["aave-market-operations"],"risk":"medium"},{"id":"c4","text":"Aave Market Data documentation exposes reserve fields such as isFrozen, isPaused, supplyInfo, borrowInfo and isolationModeConfig.","sourceIds":["aave-market-data"],"risk":"low"},{"id":"c5","text":"Aave Pool documentation describes the Pool contract as the main user-interaction contract and documents risk fields including loan-to-value, liquidation thresholds and caps.","sourceIds":["aave-pool-contract"],"risk":"low"},{"id":"c6","text":"A safe Aave onboarding flow must verify reserve state, wallet network, allowance, risk parameters and exit path before supplying assets.","sourceIds":["aave-v3-overview","aave-market-operations","aave-market-data","aave-pool-contract"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-master-key-gsl-api-key-change-disclosure-radar","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-05T09:05:00.000Z","updatedAt":"2026-10-05T09:05:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken Master Key, Global Settings Lock and API Key Change Disclosure Radar","zh-Hans":"Kraken Master Key、Global Settings Lock 与 API Key 变更披露雷达"},"summary":{"en":"Kraken account-security documentation separates three controls that users often collapse into one: a Master Key for password reset and GSL override, Global Settings Lock for blocking account changes, and API key security for.","zh-Hans":"Kraken Master Key、Global Settings Lock 与 API Key 变更披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Kraken's GSL support page says Global Settings Lock can prevent account changes and hide sensitive account information.","sourceIds":["kraken-gsl"],"risk":"medium"},{"id":"c2","text":"Kraken's GSL page says users are notified by email of attempted GSL unlocks and that unlock without Master Key can take a minimum period depending on settings.","sourceIds":["kraken-gsl"],"risk":"medium"},{"id":"c3","text":"Kraken's Master Key page says a Master Key can prevent unwanted password reset and can be used to turn off GSL immediately.","sourceIds":["kraken-master-key"],"risk":"medium"},{"id":"c4","text":"Kraken's Master Key page lists passkeys as a recommended Master Key option where supported.","sourceIds":["kraken-master-key"],"risk":"low"},{"id":"c5","text":"Kraken's API key security page warns that API keys, private keys or QR codes can grant sensitive account actions to anyone with access.","sourceIds":["kraken-api-key-security"],"risk":"low"},{"id":"c6","text":"A Kraken account-security evidence record should not include QR codes, private API material, identity documents, balances or support-only private details.","sourceIds":["kraken-gsl","kraken-master-key","kraken-api-key-security"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-onchainpay-b402-request-signing-verify-settle-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-05T06:15:00.000Z","updatedAt":"2026-10-05T06:15:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Binance OnchainPay B402 Request Signing, Verify and Settle Readiness Checklist","zh-Hans":"Binance OnchainPay B402 请求签名、验证与结算准备清单"},"summary":{"en":"Binance OnchainPay B402 integration should start with signing discipline before any payment workflow is treated as production-ready.","zh-Hans":"Binance OnchainPay B402 请求签名、验证与结算准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance OnchainPay B402 request-signing documentation describes RSA-SHA256 signatures using a submitted public key.","sourceIds":["binance-b402-signing"],"risk":"medium"},{"id":"c2","text":"The B402 signing documentation says signed requests include client identity, access token, signature and timestamp headers.","sourceIds":["binance-b402-signing"],"risk":"medium"},{"id":"c3","text":"The B402 signing documentation says the server validates timestamp freshness and signature input.","sourceIds":["binance-b402-signing"],"risk":"medium"},{"id":"c4","text":"The B402 signing documentation warns that JSON body bytes and timestamp values must match the signing payload.","sourceIds":["binance-b402-signing"],"risk":"low"},{"id":"c5","text":"Binance developer documentation states that documented interfaces are the supported reference for production integrations.","sourceIds":["binance-developer-intro"],"risk":"low"},{"id":"c6","text":"A B402 integration must treat verify and settle evidence as signed operational state, not as an unaudited front-end receipt.","sourceIds":["binance-b402-signing","binance-developer-intro","binance-pay-common"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-pay-vs-coinbase-payment-webhook-signature-reconciliation-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-05T06:15:00.000Z","updatedAt":"2026-10-05T06:15:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Pay vs Coinbase Payment Webhook Signature and Reconciliation Controls","zh-Hans":"Binance Pay 与 Coinbase 支付 Webhook 签名和对账控制对比"},"summary":{"en":"Binance Pay and Coinbase payment webhooks both move merchant state through signed event callbacks, but they should not be implemented as the same control.","zh-Hans":"Binance Pay 与 Coinbase 支付 Webhook 签名和对账控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance Pay Merchant API common rules describe HTTPS transfer, JSON payloads and signature checking for API requests and push notification signatures.","sourceIds":["binance-pay-common"],"risk":"medium"},{"id":"c2","text":"Binance Pay common rules list timestamp, nonce, certificate serial number and signature headers for request signing.","sourceIds":["binance-pay-common"],"risk":"medium"},{"id":"c3","text":"Binance Pay notification documentation says failed notification processing can trigger retry behavior and expects an HTTP 200 OK response with a success body.","sourceIds":["binance-pay-share-webhook"],"risk":"medium"},{"id":"c4","text":"Coinbase payment documentation describes Payments APIs and payment workflow surfaces for application developers.","sourceIds":["coinbase-payments-overview"],"risk":"low"},{"id":"c5","text":"Coinbase payment documentation is a separate payment stack from Binance Pay Merchant API documentation.","sourceIds":["coinbase-payments-overview"],"risk":"low"},{"id":"c6","text":"A merchant integration must reconcile event identity, signature validity where documented, retry handling and order lookup before treating a callback as final settlement evidence.","sourceIds":["binance-pay-common","binance-pay-share-webhook","coinbase-payments-overview"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fsb-iosco-crypto-stablecoin-implementation-gap-risk-checklist","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-05T06:15:00.000Z","updatedAt":"2026-10-05T06:15:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"FSB-IOSCO Crypto and Stablecoin Implementation Gap Risk Checklist","zh-Hans":"FSB-IOSCO 加密资产与稳定币实施差距风险清单"},"summary":{"en":"FSB implementation-review material turns crypto and stablecoin regulation into a jurisdiction-by-jurisdiction evidence problem.","zh-Hans":"FSB-IOSCO 加密资产与稳定币实施差距风险清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"The FSB thematic review page says the report looks at implementation of the FSB's 2023 global regulatory framework for crypto-asset activities.","sourceIds":["fsb-thematic-review"],"risk":"medium"},{"id":"c2","text":"The FSB thematic review page says the report describes progress on crypto-asset activities and service providers, stablecoins, data reporting, financial-stability monitoring and cross-border cooperation.","sourceIds":["fsb-thematic-review"],"risk":"medium"},{"id":"c3","text":"The FSB press release says significant gaps and inconsistencies remain in implementation of crypto and stablecoin recommendations.","sourceIds":["fsb-press-gaps"],"risk":"medium"},{"id":"c4","text":"The FSB crypto-assets and global stablecoins page says stablecoins and crypto-assets raise broader issues including consumer and investor protection, market integrity, AML/CFT, sanctions and tax evasion.","sourceIds":["fsb-crypto-framework"],"risk":"low"},{"id":"c5","text":"The FSB maintains a public workstream for crypto-assets and global stablecoins.","sourceIds":["fsb-crypto-framework"],"risk":"low"},{"id":"c6","text":"A user-facing decision checklist must distinguish global recommendation, local implementation and account-specific eligibility.","sourceIds":["fsb-thematic-review","fsb-press-gaps","fsb-crypto-framework"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-onboard-raydium-liquidity-wallet-fee-and-reward-controls","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-05T06:15:00.000Z","updatedAt":"2026-10-05T06:15:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"How to Onboard Raydium Liquidity: Wallet, Fee and Reward Controls","zh-Hans":"如何开始使用 Raydium 流动性：钱包、费用与奖励控制"},"summary":{"en":"Raydium onboarding is wallet-based DEX liquidity use, not centralized exchange account registration.","zh-Hans":"如何开始使用 Raydium 流动性：钱包、费用与奖励控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Raydium liquidity documentation describes adding tokens to a pool through a wallet and receiving LP tokens.","sourceIds":["raydium-liquidity"],"risk":"medium"},{"id":"c2","text":"Raydium liquidity documentation describes removing liquidity to retrieve the user's pool share.","sourceIds":["raydium-liquidity"],"risk":"medium"},{"id":"c3","text":"Raydium protocol fee documentation describes trading fees and fee splits across pool types.","sourceIds":["raydium-fees"],"risk":"medium"},{"id":"c4","text":"Raydium farm documentation says constant-product LP tokens may be staked for farm rewards.","sourceIds":["raydium-farms"],"risk":"low"},{"id":"c5","text":"Raydium farm documentation says concentrated liquidity farm rewards are distributed automatically when positions are in range.","sourceIds":["raydium-farms"],"risk":"low"},{"id":"c6","text":"A Raydium liquidity onboarding guide must not describe the process as centralized exchange account registration or collect wallet seed phrases.","sourceIds":["raydium-liquidity","raydium-fees","raydium-farms"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"iosco-tokenization-dlt-infrastructure-market-linkage-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-05T06:15:00.000Z","updatedAt":"2026-10-05T06:15:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"IOSCO Tokenization, DLT Infrastructure and Market-Linkage Risk Map","zh-Hans":"IOSCO 代币化、DLT 基础设施与市场关联风险地图"},"summary":{"en":"IOSCO's financial-asset tokenization work treats tokenization as a market-infrastructure and investor-protection issue, not a generic blockchain upgrade.","zh-Hans":"IOSCO 代币化、DLT 基础设施与市场关联风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"IOSCO's release says tokenization may enhance efficiency and transparency while introducing or amplifying risks.","sourceIds":["iosco-tokenization-release"],"risk":"medium"},{"id":"c2","text":"IOSCO's release says its report examines market practices, regulatory approaches and challenges in financial asset tokenization.","sourceIds":["iosco-tokenization-release"],"risk":"medium"},{"id":"c3","text":"DTCC describes tokenized DTC assets moving between traditional and blockchain ecosystems using the same CUSIP.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c4","text":"DTCC says DTC-issued tokens are designed to represent the same legal rights, economic interest and investor protections associated with underlying securities.","sourceIds":["dtcc-tokenization-service"],"risk":"low"},{"id":"c5","text":"DTCC describes controls including mint, burn, pause and clawback functionality.","sourceIds":["dtcc-tokenization-service"],"risk":"low"},{"id":"c6","text":"The SEC statement on tokenized securities provides a separate official reference point for U.S. tokenized-securities framing.","sourceIds":["sec-tokenized-securities"],"risk":"low"},{"id":"c7","text":"A tokenized-asset decision must separate legal rights, custody, recordkeeping and settlement infrastructure from wallet display.","sourceIds":["iosco-tokenization-release","dtcc-tokenization-service","sec-tokenized-securities"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"circle-cctp-v2-attestation-supported-chain-transfer-risk-map","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-05T03:20:00.000Z","updatedAt":"2026-10-05T03:20:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Circle CCTP v2 Attestation, Supported Chain and Transfer Risk Map","zh-Hans":"Circle CCTP v2 证明、支持链与转移风险地图"},"summary":{"en":"Circle CCTP is a cross-chain USDC transfer protocol, but a successful message flow should not be treated as a universal asset-recovery or chain-support guarantee.","zh-Hans":"Circle CCTP v2 证明、支持链与转移风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Circle publishes CCTP documentation for cross-chain USDC transfer workflows.","sourceIds":["circle-cctp"],"risk":"medium"},{"id":"c2","text":"Circle publishes a CCTP technical guide describing message and attestation workflows.","sourceIds":["circle-attestation"],"risk":"medium"},{"id":"c3","text":"Circle documents supported chains and currencies for Circle Mint and related APIs.","sourceIds":["circle-supported-chains"],"risk":"medium"},{"id":"c4","text":"Circle documentation warns that unsupported token or chain routes can create loss or stuck-fund scenarios in some contexts.","sourceIds":["circle-supported-chains"],"risk":"low"},{"id":"c5","text":"A CCTP transfer review must separate protocol message state from recipient wallet, supported-chain and recovery evidence.","sourceIds":["circle-cctp","circle-attestation","circle-supported-chains"],"risk":"low"},{"id":"c6","text":"A successful cross-chain transfer claim needs source chain, destination chain, message hash, attestation and recipient-state evidence.","sourceIds":["circle-cctp","circle-attestation"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-status-page-api-maintenance-incident-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-05T03:20:00.000Z","updatedAt":"2026-10-05T03:20:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange Status Page, API Maintenance and Incident Disclosure Radar","zh-Hans":"交易所状态页、API 维护与事故披露雷达"},"summary":{"en":"An exchange status page is useful evidence, but it is not a complete private-account diagnosis.","zh-Hans":"交易所状态页、API 维护与事故披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase publishes a public status page for product and API availability.","sourceIds":["coinbase-status"],"risk":"medium"},{"id":"c2","text":"Kraken publishes a public status page for exchange, API and product availability.","sourceIds":["kraken-status"],"risk":"medium"},{"id":"c3","text":"OKX publishes a public status page for system, maintenance and deposit or withdrawal information.","sourceIds":["okx-status"],"risk":"medium"},{"id":"c4","text":"Binance developer documentation includes system-status material for API or wallet checks.","sourceIds":["binance-system-status"],"risk":"low"},{"id":"c5","text":"Status pages can indicate component-level conditions but do not prove a user's private account state.","sourceIds":["coinbase-status","kraken-status","okx-status"],"risk":"low"},{"id":"c6","text":"A retry decision should combine public status evidence with private non-secret order, wallet or account logs.","sourceIds":["coinbase-status","kraken-status","okx-status","binance-system-status"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fsb-defi-tokenisation-data-gap-financial-stability-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-05T03:20:00.000Z","updatedAt":"2026-10-05T03:20:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"FSB DeFi, Tokenisation and Data-Gap Financial Stability Risk Map","zh-Hans":"FSB DeFi、代币化与数据缺口金融稳定风险地图"},"summary":{"en":"FSB materials treat DeFi, stablecoins and tokenisation as connected financial-stability questions, not as isolated product slogans.","zh-Hans":"FSB DeFi、代币化与数据缺口金融稳定风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"FSB describes crypto-assets, stablecoins and DeFi as closely interrelated segments that should be assessed holistically.","sourceIds":["fsb-crypto-hub"],"risk":"medium"},{"id":"c2","text":"FSB's DeFi risk release says DeFi can replicate traditional finance functions while exposing operational, liquidity, maturity, leverage and interconnectedness vulnerabilities.","sourceIds":["fsb-defi-risk"],"risk":"medium"},{"id":"c3","text":"FSB's DeFi risk release identifies tokenisation growth and DeFi data gaps as areas for additional work.","sourceIds":["fsb-defi-risk"],"risk":"medium"},{"id":"c4","text":"FSB's 2022 crypto risk assessment discusses vulnerabilities across unbacked crypto-assets, stablecoins and DeFi.","sourceIds":["fsb-crypto-risk-assessment"],"risk":"low"},{"id":"c5","text":"BIS Basel SCO60 sets out prudential treatment for banks' cryptoasset exposures and includes tokenised traditional assets within defined scope conditions.","sourceIds":["bis-sco60"],"risk":"low"},{"id":"c6","text":"Institutional readiness for DeFi or tokenisation depends on data, exposure, liquidity, governance, custody and interconnection evidence.","sourceIds":["fsb-crypto-hub","fsb-defi-risk","bis-sco60"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-coinbase-advanced-trade-api-key-portfolio-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-05T03:20:00.000Z","updatedAt":"2026-10-05T03:20:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up Coinbase Advanced Trade API Key and Portfolio Controls Safely","zh-Hans":"如何安全设置 Coinbase Advanced Trade API Key 与组合账户控制"},"summary":{"en":"Coinbase Advanced Trade API onboarding should be treated as developer-access setup, not ordinary account registration or a shortcut to trading.","zh-Hans":"如何安全设置 Coinbase Advanced Trade API Key 与组合账户控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase publishes API authentication documentation for CDP API access.","sourceIds":["coinbase-auth"],"risk":"medium"},{"id":"c2","text":"Coinbase publishes Advanced Trade portfolio guidance and says portfolios can segregate trading strategies or managed accounts.","sourceIds":["coinbase-portfolios"],"risk":"medium"},{"id":"c3","text":"Coinbase portfolio documentation says dedicated API keys can limit access to specific portfolios.","sourceIds":["coinbase-portfolios"],"risk":"medium"},{"id":"c4","text":"Coinbase publishes a Python SDK overview that includes REST and WebSocket clients.","sourceIds":["coinbase-sdk"],"risk":"low"},{"id":"c5","text":"Coinbase Advanced Trade documentation describes REST and WebSocket protocol support for programmatic trading and market data.","sourceIds":["coinbase-ws-overview"],"risk":"low"},{"id":"c6","text":"A Coinbase Advanced Trade API tutorial must protect secrets and separate portfolio scope, SDK convenience and order reconciliation.","sourceIds":["coinbase-auth","coinbase-portfolios","coinbase-sdk"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-vs-coinbase-api-key-portfolio-order-reconciliation-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-05T03:20:00.000Z","updatedAt":"2026-10-05T03:20:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken vs Coinbase API Key, Portfolio and Order Reconciliation Controls","zh-Hans":"Kraken 与 Coinbase API Key、组合账户和订单对账控制对比"},"summary":{"en":"Kraken and Coinbase both support authenticated trading APIs, but their control boundaries should not be merged into a single bot template.","zh-Hans":"Kraken 与 Coinbase API Key、组合账户和订单对账控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Kraken publishes Spot REST authentication guidance for authenticated private API calls.","sourceIds":["kraken-rest-auth"],"risk":"medium"},{"id":"c2","text":"Kraken publishes Add Order documentation for order submission.","sourceIds":["kraken-add-order"],"risk":"medium"},{"id":"c3","text":"Kraken publishes Cancel Order documentation for cancellation workflows.","sourceIds":["kraken-cancel-order"],"risk":"medium"},{"id":"c4","text":"Coinbase publishes API authentication documentation for Coinbase Developer Platform APIs.","sourceIds":["coinbase-auth"],"risk":"low"},{"id":"c5","text":"Coinbase publishes Advanced Trade portfolio guidance, including portfolio-level API key scoping.","sourceIds":["coinbase-portfolios"],"risk":"low"},{"id":"c6","text":"A cross-venue trading integration must reconcile authentication, order submission, cancellation and account or portfolio scope before treating API state as final.","sourceIds":["kraken-rest-auth","kraken-add-order","kraken-cancel-order","coinbase-auth","coinbase-portfolios"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-api-domain-ip-binding-expiry-timestamp-control-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-05T03:20:00.000Z","updatedAt":"2026-10-05T03:20:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"OKX API Domain, IP Binding, Key Expiry and Timestamp Control Checklist","zh-Hans":"OKX API 域名、IP 绑定、Key 过期与时间戳控制清单"},"summary":{"en":"OKX API integration should begin with domain and key-control mapping, not with order code. Current OKX documentation describes regional API domain requirements, API key creation, permission types, IP binding recommendations,.","zh-Hans":"OKX API 域名、IP 绑定、Key 过期与时间戳控制清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"OKX publishes an API guide covering REST and WebSocket APIs.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c2","text":"OKX documentation describes regional API domain requirements for some registered user groups.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c3","text":"OKX documentation describes API key permissions including read, trade and withdraw.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c4","text":"OKX documentation recommends binding API keys to IP addresses and describes inactivity expiry for some unbound trade or withdraw keys.","sourceIds":["okx-api-guide","okx-ip-whitelist"],"risk":"low"},{"id":"c5","text":"OKX publishes a status page for maintenance and system information.","sourceIds":["okx-status"],"risk":"low"},{"id":"c6","text":"An OKX private integration must resolve region, permission, IP binding, timestamp and rate-limit controls before private API use.","sourceIds":["okx-api-guide","okx-status"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"uniswap-v4-hooks-poolmanager-permissionless-liquidity-control-map","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-05T03:20:00.000Z","updatedAt":"2026-10-05T03:20:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Uniswap v4 Hooks, PoolManager and Permissionless Liquidity Control Map","zh-Hans":"Uniswap v4 Hooks、PoolManager 与无许可流动性控制地图"},"summary":{"en":"Uniswap v4 expands pool behavior through hooks and a singleton PoolManager design, but that flexibility is a control surface, not an endorsement of every pool.","zh-Hans":"Uniswap v4 Hooks、PoolManager 与无许可流动性控制地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Uniswap publishes developer documentation for Uniswap v4 overview material.","sourceIds":["uniswap-v4-overview"],"risk":"medium"},{"id":"c2","text":"Uniswap publishes developer documentation for v4 hook concepts.","sourceIds":["uniswap-v4-hooks"],"risk":"medium"},{"id":"c3","text":"Uniswap publishes developer documentation for v4 PoolManager concepts.","sourceIds":["uniswap-v4-poolmanager"],"risk":"medium"},{"id":"c4","text":"Hooks can change pool behavior and should be inspected as a control surface.","sourceIds":["uniswap-v4-hooks"],"risk":"low"},{"id":"c5","text":"PoolManager architecture affects how pools and liquidity interactions are organized.","sourceIds":["uniswap-v4-poolmanager"],"risk":"low"},{"id":"c6","text":"A v4 pool decision should inspect hook behavior, token contracts, approvals and routing rather than assuming all pools are equivalent.","sourceIds":["uniswap-v4-overview","uniswap-v4-hooks","uniswap-v4-poolmanager"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cftc-sec-tokenized-collateral-vs-tokenized-securities-boundary-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-04T21:10:00.000Z","updatedAt":"2026-10-04T21:10:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC Crypto FAQ and SEC Tokenized Securities Boundary Map","zh-Hans":"CFTC Crypto FAQ 与 SEC 代币化证券边界地图"},"summary":{"en":"The 2026 U.S. policy map does not collapse tokenized collateral, tokenized securities and crypto-asset trading into one rule.","zh-Hans":"CFTC Crypto FAQ 与 SEC 代币化证券边界地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"CFTC staff announced FAQs concerning registrant and registered-entity activities related to crypto assets and blockchain technologies.","sourceIds":["cftc-faq-release"],"risk":"medium"},{"id":"c2","text":"The CFTC release ties the FAQs to prior tokenized-collateral and digital-asset margin-collateral staff letters.","sourceIds":["cftc-faq-release"],"risk":"medium"},{"id":"c3","text":"SEC staff's tokenized-securities statement distinguishes issuer-sponsored, custodial and synthetic tokenized-securities models.","sourceIds":["sec-tokenized-securities"],"risk":"medium"},{"id":"c4","text":"An SEC innovation-exemption statement describes temporary, conditional relief for limited tokenized NMS stock trading venues.","sourceIds":["sec-innovation-uyeda"],"risk":"low"},{"id":"c5","text":"SEC Commissioner Peirce stated that tokenized securities are still securities.","sourceIds":["sec-tokenization-peirce"],"risk":"low"},{"id":"c6","text":"A policy update should be mapped to asset type, intermediary role, collateral use and relief condition before it becomes an operational rule.","sourceIds":["cftc-faq-release","sec-tokenized-securities","sec-innovation-uyeda"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"chainlink-ccip-cross-chain-token-standard-transfer-risk-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-04T21:10:00.000Z","updatedAt":"2026-10-04T21:10:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Chainlink CCIP Cross-Chain Token Standard and Tokenized-Asset Transfer Risk Map","zh-Hans":"Chainlink CCIP 跨链代币标准与代币化资产转移风险地图"},"summary":{"en":"Chainlink CCIP can support cross-chain token movement, but a transfer rail does not settle the legal rights of a tokenized asset by itself.","zh-Hans":"Chainlink CCIP 跨链代币标准与代币化资产转移风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Chainlink publishes CCIP documentation for cross-chain interoperability workflows.","sourceIds":["chainlink-ccip"],"risk":"medium"},{"id":"c2","text":"Chainlink publishes Cross-Chain Token Standard documentation for token movement across chains.","sourceIds":["chainlink-cct"],"risk":"medium"},{"id":"c3","text":"Chainlink publishes manual-execution documentation for CCIP recovery conditions.","sourceIds":["chainlink-manual-execution"],"risk":"medium"},{"id":"c4","text":"SEC staff describes multiple models for tokenized securities, including issuer-sponsored, custodial and synthetic structures.","sourceIds":["sec-tokenized-securities"],"risk":"low"},{"id":"c5","text":"SEC staff says tokenized form does not change the application of federal securities laws.","sourceIds":["sec-tokenized-securities"],"risk":"low"},{"id":"c6","text":"A cross-chain token movement does not by itself prove issuer records, custodian records, redemption rights or investor protections.","sourceIds":["chainlink-ccip","chainlink-cct","sec-tokenized-securities"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-advanced-trade-create-order-auth-reconciliation-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-04T21:10:00.000Z","updatedAt":"2026-10-04T21:10:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Advanced Trade Create Order, Authentication and Reconciliation Checklist","zh-Hans":"Coinbase Advanced Trade 下单、认证与对账清单"},"summary":{"en":"Coinbase Advanced Trade API onboarding should be treated as an authenticated order-control workflow, not as a generic trading shortcut.","zh-Hans":"Coinbase Advanced Trade 下单、认证与对账清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase publishes API authentication documentation for Coinbase Developer Platform consumers.","sourceIds":["coinbase-auth"],"risk":"medium"},{"id":"c2","text":"Coinbase publishes Advanced Trade API order-management guidance for order workflows.","sourceIds":["coinbase-order-management"],"risk":"medium"},{"id":"c3","text":"Coinbase publishes a Create Order endpoint in the Advanced Trade REST API reference.","sourceIds":["coinbase-create-order"],"risk":"medium"},{"id":"c4","text":"Coinbase publishes Advanced Trade WebSocket endpoint documentation for streaming workflows.","sourceIds":["coinbase-websocket"],"risk":"low"},{"id":"c5","text":"Coinbase also publishes Exchange REST authentication documentation, showing that authentication shape depends on API surface.","sourceIds":["coinbase-exchange-auth"],"risk":"low"},{"id":"c6","text":"A Coinbase API integration must separate authentication, order submission, stream events and reconciliation before live automation.","sourceIds":["coinbase-auth","coinbase-order-management","coinbase-create-order","coinbase-websocket"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-api-key-scope-ip-whitelist-expiry-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-04T21:10:00.000Z","updatedAt":"2026-10-04T21:10:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange API Key Scope, IP Whitelist and Expiry Disclosure Radar","zh-Hans":"交易所 API Key 权限、IP 白名单与过期披露雷达"},"summary":{"en":"NexuAlpha's current API-key radar finds that exchange authentication language is not interchangeable across venues.","zh-Hans":"交易所 API Key 权限、IP 白名单与过期披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance publishes request-security documentation for signed Spot API endpoints.","sourceIds":["binance-request-security"],"risk":"medium"},{"id":"c2","text":"Coinbase publishes API authentication documentation for Coinbase Developer Platform APIs.","sourceIds":["coinbase-auth"],"risk":"medium"},{"id":"c3","text":"OKX publishes API key security and REST authentication material in its API guide.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c4","text":"MEXC publishes Spot API documentation including API-key and IP whitelist guidance.","sourceIds":["mexc-spot-api"],"risk":"low"},{"id":"c5","text":"Kraken publishes Spot REST authentication guidance.","sourceIds":["kraken-rest-auth"],"risk":"low"},{"id":"c6","text":"API-key readiness requires venue-specific permission, IP, expiry, timestamp and signature checks rather than a shared credential template.","sourceIds":["binance-request-security","coinbase-auth","okx-api-guide","mexc-spot-api","kraken-rest-auth"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-onboard-uniswap-v3-liquidity-wallet-mint-and-fee-controls","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-04T21:10:00.000Z","updatedAt":"2026-10-04T21:10:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"How to Onboard a Uniswap v3 Liquidity Wallet Without Calling It Account Registration","zh-Hans":"如何上手 Uniswap v3 流动性钱包：不要把它写成开户注册"},"summary":{"en":"Uniswap v3 onboarding is wallet and smart-contract preparation, not exchange account registration.","zh-Hans":"如何上手 Uniswap v3 流动性钱包：不要把它写成开户注册：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Uniswap publishes v3 developer documentation for setting up liquidity workflows.","sourceIds":["uniswap-v3-setup"],"risk":"medium"},{"id":"c2","text":"Uniswap publishes v3 documentation for minting a liquidity position.","sourceIds":["uniswap-v3-mint"],"risk":"medium"},{"id":"c3","text":"Uniswap publishes v3 documentation for increasing liquidity.","sourceIds":["uniswap-v3-increase"],"risk":"medium"},{"id":"c4","text":"Uniswap publishes v3 documentation for collecting fees.","sourceIds":["uniswap-v3-collect"],"risk":"low"},{"id":"c5","text":"Uniswap publishes v3 documentation for single-hop swaps.","sourceIds":["uniswap-v3-swap"],"risk":"low"},{"id":"c6","text":"A Uniswap v3 onboarding tutorial must describe wallet and contract interaction boundaries rather than exchange account registration.","sourceIds":["uniswap-v3-setup","uniswap-v3-mint","uniswap-v3-increase","uniswap-v3-collect"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-coinbase-kraken-okx-websocket-order-state-controls","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-04T18:08:00.000Z","updatedAt":"2026-10-04T18:08:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Binance, Coinbase, Kraken and OKX WebSocket Order-State Control Comparison","zh-Hans":"Binance、Coinbase、Kraken 与 OKX WebSocket 订单状态控制对比"},"summary":{"en":"Binance, Coinbase, Kraken and OKX WebSocket Order-State Control Comparison maps verified source claims, interpretation and unknowns into a practical decision checklist.","zh-Hans":"Binance、Coinbase、Kraken 与 OKX WebSocket 订单状态控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance publishes User Data Stream documentation for account and order events.","sourceIds":["binance-user-data-stream"],"risk":"medium"},{"id":"c2","text":"Coinbase publishes Exchange WebSocket channel documentation for streaming exchange data.","sourceIds":["coinbase-websocket-channels"],"risk":"medium"},{"id":"c3","text":"Kraken publishes WebSocket v2 add_order documentation for order entry over WebSocket.","sourceIds":["kraken-ws-add-order"],"risk":"medium"},{"id":"c4","text":"Kraken publishes WebSocket v2 cancel_order documentation for cancellation over WebSocket.","sourceIds":["kraken-ws-cancel-order"],"risk":"medium"},{"id":"c5","text":"OKX publishes API guide material that includes a WebSocket order channel for order updates.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c6","text":"A cross-venue implementation must separate acknowledgement, final fill state, cancel failure and reconnect backfill rather than treating one event name as final truth.","sourceIds":["binance-user-data-stream","coinbase-websocket-channels","kraken-ws-add-order","kraken-ws-cancel-order","okx-api-guide"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-user-data-stream-api-reconnect-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-04T18:08:00.000Z","updatedAt":"2026-10-04T18:08:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Binance User Data Stream Reconnect and Account-Event Readiness Checklist","zh-Hans":"Binance User Data Stream 重连与账户事件准备清单"},"summary":{"en":"Binance User Data Stream Reconnect and Account-Event Readiness Checklist maps verified source claims, interpretation and unknowns into a practical decision checklist.","zh-Hans":"Binance User Data Stream 重连与账户事件准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance publishes User Data Stream documentation for private account and order events.","sourceIds":["binance-user-data-stream"],"risk":"medium"},{"id":"c2","text":"Binance User Data Stream documentation includes order-update event material for spot account activity.","sourceIds":["binance-user-data-stream"],"risk":"medium"},{"id":"c3","text":"Binance publishes REST API request-security documentation that is separate from stream consumption.","sourceIds":["binance-request-security"],"risk":"medium"},{"id":"c4","text":"Binance publishes WebSocket API general information for Spot API consumers.","sourceIds":["binance-websocket-api"],"risk":"medium"},{"id":"c5","text":"Binance publishes a Spot API changelog that should be reviewed before relying on older integration behavior.","sourceIds":["binance-api-changelog"],"risk":"medium"},{"id":"c6","text":"Operational readiness requires backfill and alerting because a stream event alone does not prove complete local state.","sourceIds":["binance-user-data-stream","binance-request-security","binance-websocket-api"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fsb-bis-cross-border-payment-crypto-stablecoin-oversight-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-04T18:08:00.000Z","updatedAt":"2026-10-04T18:08:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"FSB and BIS Cross-Border Payment Oversight Map for Crypto and Stablecoin Decisions","zh-Hans":"FSB 与 BIS 跨境支付监管地图：加密资产与稳定币决策"},"summary":{"en":"FSB and BIS Cross-Border Payment Oversight Map for Crypto and Stablecoin Decisions maps verified source claims, interpretation and unknowns into a practical decision checklist.","zh-Hans":"加密资产与稳定币支付叙事应拿主流支付系统监管框架来核验，而不应只看速度叙事。FSB 持续维护 crypto-assets and global stablecoins 工作，BIS CPMI 关于跨境连接 fast payment systems 的材料则把注意力放在 governance 与 oversight。"},"claims":[{"id":"c1","text":"FSB maintains a public workstream page on crypto-assets and global stablecoins.","sourceIds":["fsb-crypto-stablecoins"],"risk":"medium"},{"id":"c2","text":"BIS CPMI publishes material on linking fast payment systems across borders with governance and oversight considerations.","sourceIds":["bis-cpmi-fast-payments"],"risk":"medium"},{"id":"c3","text":"BIS publishes analysis on stablecoins and tokenisation in the future monetary system.","sourceIds":["bis-stablecoins-tokenisation"],"risk":"medium"},{"id":"c4","text":"Payment speed claims do not by themselves prove legal finality, consumer protection or cross-border dispute handling.","sourceIds":["fsb-crypto-stablecoins","bis-cpmi-fast-payments"],"risk":"medium"},{"id":"c5","text":"A decision framework should compare governance, oversight, interoperability, resilience, sanctions and settlement risk.","sourceIds":["fsb-crypto-stablecoins","bis-cpmi-fast-payments","bis-stablecoins-tokenisation"],"risk":"medium"},{"id":"c6","text":"Jurisdiction and entity scope remain material unknowns when an asset issuer, payment bridge or exchange is outside the user region.","sourceIds":["fsb-crypto-stablecoins"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"proof-of-reserves-liability-attestation-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-04T18:08:00.000Z","updatedAt":"2026-10-04T18:08:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Proof of Reserves, Liability Attestation and Disclosure Scope Radar","zh-Hans":"储备证明、负债证明与披露范围雷达"},"summary":{"en":"Proof of Reserves, Liability Attestation and Disclosure Scope Radar maps verified source claims, interpretation and unknowns into a practical decision checklist.","zh-Hans":"储备证明页面应被阅读为披露证据，而不是一揽子偿付能力保证。Binance、OKX 与 Kraken 都发布公开 proof-of-reserves 材料，但真正有决策价值的是细节：覆盖哪些资产、是否表示负债、用户能否验证自身纳入、快照更新频率、是否说明审计方或方法、哪些实体或产品不在范围内。"},"claims":[{"id":"c1","text":"Binance publishes a public Proof of Reserves page.","sourceIds":["binance-por"],"risk":"medium"},{"id":"c2","text":"OKX publishes a public Proof of Reserves page.","sourceIds":["okx-por"],"risk":"medium"},{"id":"c3","text":"Kraken publishes a public Proof of Reserves page.","sourceIds":["kraken-por"],"risk":"medium"},{"id":"c4","text":"FSB maintains policy work on crypto-assets and global stablecoins that keeps governance and risk controls in scope.","sourceIds":["fsb-crypto-stablecoins"],"risk":"medium"},{"id":"c5","text":"A POR page alone does not prove a specific user account state, future withdrawals, legal entity coverage or future solvency.","sourceIds":["binance-por","okx-por","kraken-por","fsb-crypto-stablecoins"],"risk":"medium"},{"id":"c6","text":"The practical comparison should ask about covered assets, liabilities, method, update frequency, verification path and exclusions.","sourceIds":["binance-por","okx-por","kraken-por"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-dtcc-tokenized-securities-official-record-rights-boundary","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-04T18:08:00.000Z","updatedAt":"2026-10-04T18:08:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"SEC and DTCC Tokenized Securities: Official Record and Rights Boundary Map","zh-Hans":"SEC 与 DTCC 代币化证券：官方记录与权利边界地图"},"summary":{"en":"SEC and DTCC Tokenized Securities: Official Record and Rights Boundary Map maps verified source claims, interpretation and unknowns into a practical decision checklist.","zh-Hans":"代币化证券分析必须把数字表示、法律记录和产品权利分开。SEC 关于 tokenized securities 的声明强调，不同 tokenized securities 的结构和权利可能不同；DTCC 则围绕 DTC 持有证券及其在 approved networks 上的数字表示描述数字资产工作。"},"claims":[{"id":"c1","text":"The SEC statement says tokenized securities may vary by structure and rights.","sourceIds":["sec-tokenized-securities"],"risk":"medium"},{"id":"c2","text":"DTCC publishes Digital Assets material for securities held at DTC and digital representation across approved networks.","sourceIds":["dtcc-digital-assets"],"risk":"medium"},{"id":"c3","text":"DTCC publishes a tokenization hub for its digital-assets work.","sourceIds":["dtcc-tokenization-hub"],"risk":"medium"},{"id":"c4","text":"DTCC Learning publishes Tokenization Service material for tokenized securities processed through DTCC infrastructure.","sourceIds":["dtcc-learning-tokenization"],"risk":"medium"},{"id":"c5","text":"A wallet-visible token is not, by itself, evidence of shareholder rights, redemption rights or settlement finality.","sourceIds":["sec-tokenized-securities","dtcc-digital-assets"],"risk":"medium"},{"id":"c6","text":"A decision framework should map official books, network approval, custody and asset servicing before comparing tokenized securities to direct securities.","sourceIds":["sec-tokenized-securities","dtcc-digital-assets","dtcc-learning-tokenization"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-coinbase-kraken-rest-api-authentication-control-comparison","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-04T12:08:00.000Z","updatedAt":"2026-10-04T12:08:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Binance, Coinbase and Kraken REST API Authentication Control Comparison","zh-Hans":"Binance、Coinbase 与 Kraken REST API 认证控制对比"},"summary":{"en":"REST API authentication should be compared as a control design, not as copy-pasted signing code.","zh-Hans":"Binance、Coinbase 与 Kraken REST API 认证控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance publishes official developer documentation for Spot API request security.","sourceIds":["binance-request-security"],"risk":"medium"},{"id":"c2","text":"Coinbase publishes official developer documentation for Exchange REST API authentication.","sourceIds":["coinbase-rest-auth"],"risk":"medium"},{"id":"c3","text":"Kraken publishes official developer documentation for Spot REST authentication.","sourceIds":["kraken-rest-auth"],"risk":"medium"},{"id":"c4","text":"MEXC Spot API documentation describes API-key authentication and signed requests for private account and trade endpoints.","sourceIds":["mexc-spot-api-intro"],"risk":"low"},{"id":"c5","text":"MEXC Futures integration guidance separates integration requirements from general public market-data access.","sourceIds":["mexc-futures-api-guide"],"risk":"low"},{"id":"c6","text":"API comparison should separate read-only access, trading authority, signature construction, timestamp or nonce handling and secret storage.","sourceIds":["binance-request-security","coinbase-rest-auth","kraken-rest-auth","mexc-spot-api-intro"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-fee-schedule-change-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-04T12:08:00.000Z","updatedAt":"2026-10-04T12:08:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange Fee Schedule Change Disclosure Radar","zh-Hans":"交易所费率表变更披露雷达"},"summary":{"en":"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.","zh-Hans":"本文最有价值的地方是克制。NexuAlpha Radar 把费率表视为会变化的来源对象。"},"claims":[{"id":"c1","text":"OKX, Kraken, Gate, MEXC and Bitget each publish official fee pages that can be rechecked directly.","sourceIds":["okx-fees","kraken-fee-schedule","gate-fee-overview","mexc-fees","bitget-fees"],"risk":"medium"},{"id":"c2","text":"Gate fee material explicitly presents spot, futures and VIP fee-rate framing in the page title.","sourceIds":["gate-fee-overview"],"risk":"medium"},{"id":"c3","text":"OKX fee material presents fee tiers in the page title.","sourceIds":["okx-fees"],"risk":"medium"},{"id":"c4","text":"MEXC fee material presents trading fees and rates in the page title.","sourceIds":["mexc-fees"],"risk":"low"},{"id":"c5","text":"Bitget fee material presents trading fees for cryptocurrency in the page title.","sourceIds":["bitget-fees"],"risk":"low"},{"id":"c6","text":"A fee-disclosure radar should record source date and product surface rather than converting a fee table into a universal cheapest-venue claim.","sourceIds":["okx-fees","kraken-fee-schedule","gate-fee-overview","mexc-fees","bitget-fees"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-compare-crypto-exchange-fee-schedules-without-missing-costs","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-04T12:08:00.000Z","updatedAt":"2026-10-04T12:08:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"How to Compare Crypto Exchange Fee Schedules Without Missing Costs","zh-Hans":"如何比较加密交易所费率表而不漏掉真实成本"},"summary":{"en":"A crypto exchange fee schedule should be read as an operating checklist, not a single headline rate.","zh-Hans":"本文最有价值的地方是克制。加密交易所费率表应被当成操作清单，而不是一个 headline rate。OKX、Kraken、Gate、MEXC 与 Bitget 都发布官方费率页面，但各页面会按不同产品界面、账户等级、市场类型或 VIP 规则组织成本信息。"},"claims":[{"id":"c1","text":"OKX publishes an official trading fee page that organizes fee rates by fee tiers and crypto exchange fee categories.","sourceIds":["okx-fees"],"risk":"medium"},{"id":"c2","text":"Kraken publishes an official fee schedule page for trading fee review.","sourceIds":["kraken-fee-schedule"],"risk":"medium"},{"id":"c3","text":"Gate publishes an official crypto fee overview page covering spot, futures and VIP fee rates.","sourceIds":["gate-fee-overview"],"risk":"medium"},{"id":"c4","text":"MEXC publishes an official trading-fees page for fees and rates.","sourceIds":["mexc-fees"],"risk":"low"},{"id":"c5","text":"Bitget publishes an official trading-fees page for cryptocurrency fee review.","sourceIds":["bitget-fees"],"risk":"low"},{"id":"c6","text":"A cross-venue fee comparison cannot be reduced to one visible rate without checking product surface, role, tier and withdrawal path.","sourceIds":["okx-fees","kraken-fee-schedule","gate-fee-overview","mexc-fees","bitget-fees"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-onboard-gate-with-kyc-fund-password-whitelist-and-cooldown-checks","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-04T12:08:00.000Z","updatedAt":"2026-10-04T12:08:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"How to Onboard Gate With KYC, Fund Password, Whitelist and Cooldown Checks","zh-Hans":"如何用 KYC、资金密码、白名单与冷却期检查完成 Gate 入门设置"},"summary":{"en":"A careful Gate onboarding path should treat deposits as the last step, not the first step. Gate US whitelist guidance says users should have a registered account, completed KYC identity verification, fund password and two-factor.","zh-Hans":"本文最有价值的地方是克制。谨慎的 Gate 入门路径应把入金放在最后，而不是第一步。Gate US 白名单指南说明，用户在设置提现地址白名单前应拥有注册账户、完成 KYC 身份核验、设置 fund password 与 two-factor authentication。"},"claims":[{"id":"c1","text":"Gate US says users should have a registered account before setting a withdrawal address whitelist.","sourceIds":["gate-us-whitelist"],"risk":"medium"},{"id":"c2","text":"Gate US says users should complete KYC identity verification and set fund password and two-factor authentication before the whitelist flow.","sourceIds":["gate-us-whitelist"],"risk":"medium"},{"id":"c3","text":"Gate US says users choose coin and network and enter the withdrawal address when adding a new whitelist address.","sourceIds":["gate-us-whitelist"],"risk":"medium"},{"id":"c4","text":"Gate US says a verification-free address can skip later verification steps.","sourceIds":["gate-us-whitelist"],"risk":"low"},{"id":"c5","text":"Gate US withdrawal FAQ says first KYC completion, Google Authenticator changes or phone-number updates can temporarily restrict withdrawals for 24 hours.","sourceIds":["gate-us-withdrawal-faq"],"risk":"low"},{"id":"c6","text":"Gate security material frames login, transaction, withdrawal and security settings as account-security surfaces.","sourceIds":["gate-security"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-okx-bybit-regional-availability-decision-map","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-04T12:08:00.000Z","updatedAt":"2026-10-04T12:08:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken, OKX and Bybit Regional Availability Decision Map","zh-Hans":"Kraken、OKX 与 Bybit 地区可用性决策地图"},"summary":{"en":"Regional availability is a current-state evidence problem, not a brand-level assumption. Kraken publishes official material about where it is licensed or regulated; OKX publishes terms of service that define user obligations and.","zh-Hans":"本文最有价值的地方是克制。地区可用性是当前状态证据问题，而不是品牌层面的假设。Kraken 发布官方许可或监管地点资料；OKX 发布定义用户义务和限制的服务条款；Bybit 发布服务受限国家帮助页。实用结论是：不要默认某地区可以开户、入金、交易或提现，应先核验平台、产品界面、司法辖区、账户居住地、文档路径和来源日期。"},"claims":[{"id":"c1","text":"Kraken publishes an official page explaining where it is licensed or regulated.","sourceIds":["kraken-licensed-regulated"],"risk":"medium"},{"id":"c2","text":"OKX publishes official terms of service that govern user obligations and restrictions.","sourceIds":["okx-terms"],"risk":"medium"},{"id":"c3","text":"Bybit publishes an official help-center page for service restricted countries.","sourceIds":["bybit-restricted-countries"],"risk":"medium"},{"id":"c4","text":"Fee or product pages do not by themselves prove regional account eligibility.","sourceIds":["kraken-fee-schedule","okx-fees"],"risk":"low"},{"id":"c5","text":"A public availability page does not prove a private account has passed identity, risk or product-specific checks.","sourceIds":["kraken-licensed-regulated","okx-terms","bybit-restricted-countries"],"risk":"low"},{"id":"c6","text":"Regional eligibility should be refreshed before onboarding or funding because venue restrictions can change.","sourceIds":["kraken-licensed-regulated","okx-terms","bybit-restricted-countries"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"stablecoin-tokenization-trust-anchor-risk-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-04T12:08:00.000Z","updatedAt":"2026-10-04T12:08:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Stablecoin and Tokenization Trust Anchor Risk Map","zh-Hans":"稳定币与代币化信任锚风险地图"},"summary":{"en":"Stablecoin and tokenization analysis should begin with the trust anchor, not with interface speed.","zh-Hans":"稳定币与代币化信任锚风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"The BIS chapter frames monetary innovation beyond stablecoins around trust in money.","sourceIds":["bis-tokenisation"],"risk":"medium"},{"id":"c2","text":"DTCC Digital Assets links digital representation to established market infrastructure.","sourceIds":["dtcc-digital-assets"],"risk":"medium"},{"id":"c3","text":"DTCC Learning says tokenized securities processed through DTCC Tokenization Service remain recorded in DTC official books and records.","sourceIds":["dtcc-learning-tokenization"],"risk":"medium"},{"id":"c4","text":"The SEC statement says tokenized securities can differ by structure and rights.","sourceIds":["sec-tokenized-securities"],"risk":"low"},{"id":"c5","text":"Venue terms remain separate from institutional trust-anchor or recordkeeping evidence.","sourceIds":["okx-terms","bis-tokenisation"],"risk":"low"},{"id":"c6","text":"A trust-anchor map should separate issuer, reserve, recordkeeper, settlement asset, redemption route and rights evidence.","sourceIds":["bis-tokenisation","dtcc-digital-assets","dtcc-learning-tokenization","sec-tokenized-securities"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"tokenized-security-official-record-vs-wallet-display-boundary","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-04T12:08:00.000Z","updatedAt":"2026-10-04T12:08:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Tokenized Security Official Record vs Wallet Display Boundary","zh-Hans":"代币化证券官方记录与钱包显示边界"},"summary":{"en":"A tokenized-security analysis should keep the legal record separate from the wallet display. DTCC Learning says tokenized securities processed through DTCC Tokenization Service remain recorded in DTC official books and records.","zh-Hans":"代币化证券官方记录与钱包显示边界：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"DTCC Learning says tokenized securities processed through DTCC Tokenization Service remain recorded in DTC official books and records.","sourceIds":["dtcc-learning-tokenization"],"risk":"medium"},{"id":"c2","text":"DTCC Digital Assets describes DTC-held securities as assets that can be represented digitally across approved networks.","sourceIds":["dtcc-digital-assets"],"risk":"medium"},{"id":"c3","text":"DTCC Digital Assets frames digital-asset representation as connected to established market protections and infrastructure.","sourceIds":["dtcc-digital-assets"],"risk":"medium"},{"id":"c4","text":"The SEC statement says tokenized securities can differ by structure and rights.","sourceIds":["sec-tokenized-securities"],"risk":"low"},{"id":"c5","text":"DTCC maintains a tokenization hub for digital-assets materials.","sourceIds":["dtcc-tokenization-hub"],"risk":"low"},{"id":"c6","text":"Institutional tokenization claims should not turn a digital representation into an unsupported rights or redemption claim.","sourceIds":["dtcc-learning-tokenization","dtcc-digital-assets","sec-tokenized-securities"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-vs-bitget-passkey-withdrawal-control-boundary","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-04T08:58:00.000Z","updatedAt":"2026-10-04T08:58:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit vs Bitget Passkey and Withdrawal Control Boundary","zh-Hans":"Bybit 与 Bitget Passkey 和提现控制边界对比"},"summary":{"en":"Bybit and Bitget both position passkeys as phishing-resistant account controls, but their operational boundaries are not identical. Bybit's passkey guide says Passkey 2.","zh-Hans":"Bybit 与 Bitget Passkey 和提现控制边界对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit describes Passkey 2.0 as a FIDO passkey using biometrics registered on the user device for secure verification.","sourceIds":["bybit-passkey"],"risk":"medium"},{"id":"c2","text":"Bybit says removing a passkey can result in a 24-hour withdrawal restriction for account and asset security.","sourceIds":["bybit-passkey"],"risk":"medium"},{"id":"c3","text":"Bybit withdrawal guidance lists multiple account-security changes that can restrict withdrawals for 24 hours.","sourceIds":["bybit-withdrawal-faq"],"risk":"medium"},{"id":"c4","text":"Bitget says passkeys use asymmetric encryption and that the private key remains on the user device.","sourceIds":["bitget-passkey"],"risk":"low"},{"id":"c5","text":"Bitget says passkeys are domain-specific and only work on official Bitget domains.","sourceIds":["bitget-passkey"],"risk":"low"},{"id":"c6","text":"Bitget withdrawal guidance says Google Authenticator is required for withdrawals and that wrong wallet addresses can be irreversible.","sourceIds":["bitget-withdraw"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-tokenization-service-official-books-collateral-controls","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-04T08:58:00.000Z","updatedAt":"2026-10-04T08:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Tokenization Service, Official Books and Collateral Control Map","zh-Hans":"DTCC Tokenization Service、官方账簿与抵押品控制地图"},"summary":{"en":"DTCC's tokenization materials are useful because they separate tokenized representation from the official post-trade record.","zh-Hans":"DTCC Tokenization Service、官方账簿与抵押品控制地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"DTCC Learning says tokenized securities processed through the Tokenization Service remain recorded in DTC official books and records.","sourceIds":["dtcc-learning-tokenization"],"risk":"medium"},{"id":"c2","text":"DTCC Learning says tokenized collateral can move high-quality assets in near real time across borders and time zones in appropriate market arrangements.","sourceIds":["dtcc-learning-tokenization"],"risk":"medium"},{"id":"c3","text":"DTCC Digital Assets says securities held at DTC can be represented as digital assets and used across approved networks.","sourceIds":["dtcc-digital-assets"],"risk":"medium"},{"id":"c4","text":"DTCC Digital Assets says the representation remains anchored to protections and resiliency market participants rely on today.","sourceIds":["dtcc-digital-assets"],"risk":"low"},{"id":"c5","text":"DTCC announced authorization to offer a new tokenization service for DTC-custodied assets.","sourceIds":["dtcc-press-tokenization-service"],"risk":"low"},{"id":"c6","text":"The SEC tokenized-securities statement says tokenized securities vary by structure and rights.","sourceIds":["sec-tokenized-securities"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-withdrawal-cooldown-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-04T08:58:00.000Z","updatedAt":"2026-10-04T08:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange Withdrawal Cooldown Disclosure Radar","zh-Hans":"交易所提现冷却期披露雷达"},"summary":{"en":"NexuAlpha's current radar scan finds that withdrawal cooldowns are not a single universal rule.","zh-Hans":"交易所提现冷却期披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit lists multiple account-security actions that can lead to 24-hour withdrawal restrictions.","sourceIds":["bybit-withdrawal-faq"],"risk":"medium"},{"id":"c2","text":"Bybit says actions considered withdrawals include on-chain withdrawal, internal transfer, fiat withdrawal, Bybit Card transactions and P2P trading.","sourceIds":["bybit-withdrawal-faq"],"risk":"medium"},{"id":"c3","text":"Gate US says first KYC completion, changing Google Authenticator or updating phone number can temporarily restrict withdrawals for 24 hours.","sourceIds":["gate-us-withdrawal-faq"],"risk":"medium"},{"id":"c4","text":"Crypto.com says a 24-hour withdrawal lock can apply when enabled for new withdrawal addresses.","sourceIds":["crypto-com-withdrawals"],"risk":"low"},{"id":"c5","text":"Kraken says certain deposits, purchases and password changes can create withdrawal holds, including a 24-hour hold for withdrawals to new addresses after a password change.","sourceIds":["kraken-withdrawal-hold"],"risk":"low"},{"id":"c6","text":"Bitget says withdrawals require Google Authenticator and other verification checks.","sourceIds":["bitget-withdraw"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"franklin-benji-official-record-wallet-transfer-boundary","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-04T08:58:00.000Z","updatedAt":"2026-10-04T08:58:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Franklin BENJI Official Record and Wallet Transfer Boundary","zh-Hans":"Franklin BENJI 官方记录与钱包转让边界"},"summary":{"en":"Franklin Templeton's BENJI materials are a useful RWA boundary case because the token and the official ownership record are described together. The Benji product page says the Franklin OnChain U.S.","zh-Hans":"Franklin BENJI 官方记录与钱包转让边界：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Franklin Templeton says the Franklin OnChain U.S. Government Money Fund uses blockchain technology for mutual fund recordkeeping.","sourceIds":["franklin-benji-product"],"risk":"medium"},{"id":"c2","text":"Franklin Templeton says the fund transfer agent maintains the official record of share ownership through the Benji platform.","sourceIds":["franklin-benji-product"],"risk":"medium"},{"id":"c3","text":"Franklin Templeton says FOBXX was the first U.S.-registered mutual fund to use a public blockchain as the official system of record for processing transactions and recording share ownership.","sourceIds":["franklin-benji-anniversary"],"risk":"medium"},{"id":"c4","text":"The Franklin prospectus says the blockchain-integrated recordkeeping system is permissioned and uses permissioned-wallet whitelisting and administrative controls.","sourceIds":["franklin-fobxx-prospectus"],"risk":"low"},{"id":"c5","text":"The SEC tokenized-securities statement says tokenized securities vary in structure and rights.","sourceIds":["sec-tokenized-securities"],"risk":"low"},{"id":"c6","text":"Commissioner Peirce states that tokenized securities are still securities.","sourceIds":["sec-peirce-tokenization"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"gate-withdrawal-whitelist-fund-password-readiness-checklist","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-04T08:58:00.000Z","updatedAt":"2026-10-04T08:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Gate Withdrawal Whitelist, Fund Password and 2FA Readiness Checklist","zh-Hans":"Gate 提现白名单、资金密码与 2FA 准备清单"},"summary":{"en":"Gate's official withdrawal-whitelist documentation turns a wallet address into an account-security decision.","zh-Hans":"Gate 提现白名单、资金密码与 2FA 准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Gate US says the withdrawal whitelist guide applies to Gate US Web.","sourceIds":["gate-us-whitelist"],"risk":"medium"},{"id":"c2","text":"Gate US says users should have completed KYC identity verification and set fund password and two-factor authentication before starting.","sourceIds":["gate-us-whitelist"],"risk":"medium"},{"id":"c3","text":"Gate US says users can mark an address as verification-free for future withdrawals.","sourceIds":["gate-us-whitelist"],"risk":"medium"},{"id":"c4","text":"Gate US warns that verification-free addresses can skip fund password and other verification steps in future withdrawals.","sourceIds":["gate-us-whitelist"],"risk":"low"},{"id":"c5","text":"Gate US withdrawal FAQ says completing KYC for the first time, changing Google Authenticator or updating phone number can restrict withdrawals for 24 hours.","sourceIds":["gate-us-withdrawal-faq"],"risk":"low"},{"id":"c6","text":"Gate UK guidance says trusted addresses can bypass the regular verification process, including SMS, email, authenticator code and fund password.","sourceIds":["gate-uk-whitelist"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-gate-account-security-and-withdrawal-whitelist","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-04T08:58:00.000Z","updatedAt":"2026-10-04T08:58:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up Gate Account Security and a Withdrawal Whitelist","zh-Hans":"如何设置 Gate 账户安全与提现白名单"},"summary":{"en":"A safe Gate onboarding flow should not start with a deposit. It should start with official-domain access, account security, identity status and withdrawal controls.","zh-Hans":"本文最有价值的地方是克制。安全的 Gate onboarding 不应从入金开始，而应从官方域名、账户安全、身份状态和提现控制开始。Gate US 提现白名单指南说明，用户在设置提现地址白名单前应拥有注册账户、KYC 身份核验、fund password 和 two-factor authentication。"},"claims":[{"id":"c1","text":"Gate US says users should have a registered Gate account before setting a withdrawal whitelist.","sourceIds":["gate-us-whitelist"],"risk":"medium"},{"id":"c2","text":"Gate US says users should have completed KYC identity verification before setting a withdrawal whitelist.","sourceIds":["gate-us-whitelist"],"risk":"medium"},{"id":"c3","text":"Gate US says fund password and two-factor authentication should be set before the whitelist flow.","sourceIds":["gate-us-whitelist"],"risk":"medium"},{"id":"c4","text":"Gate US says users choose cryptocurrency and network and enter the withdrawal address when adding a new address.","sourceIds":["gate-us-whitelist"],"risk":"low"},{"id":"c5","text":"Gate US says a verification-free address can skip later verification steps, creating a security tradeoff.","sourceIds":["gate-us-whitelist"],"risk":"low"},{"id":"c6","text":"Gate security material frames login, transaction, withdrawal and security settings as protected account surfaces.","sourceIds":["gate-security"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"mexc-api-key-ip-whitelist-permission-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-04T08:58:00.000Z","updatedAt":"2026-10-04T08:58:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"MEXC API Key IP Whitelist and Permission Readiness Checklist","zh-Hans":"MEXC API Key、IP 白名单与权限准备清单"},"summary":{"en":"MEXC's API documentation makes API readiness a permission and key-management problem, not just a coding task.","zh-Hans":"MEXC API Key、IP 白名单与权限准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"MEXC Spot API documentation says private account and trade endpoints require API Key authentication and signed requests.","sourceIds":["mexc-spot-api-intro"],"risk":"medium"},{"id":"c2","text":"MEXC Spot API documentation recommends configuring an IP access whitelist and says keys without a whitelist are valid for 90 days.","sourceIds":["mexc-spot-api-intro"],"risk":"medium"},{"id":"c3","text":"MEXC Spot API documentation says users should check required permissions when creating an API key.","sourceIds":["mexc-spot-api-intro"],"risk":"medium"},{"id":"c4","text":"MEXC Spot API documentation says users should never share API keys or secrets and should delete leaked keys immediately.","sourceIds":["mexc-spot-api-intro"],"risk":"low"},{"id":"c5","text":"MEXC Futures integration guidance says futures order-placement permissions may require completed KYC.","sourceIds":["mexc-futures-api-guide"],"risk":"low"},{"id":"c6","text":"MEXC support says API access applications for automated trading are primarily available to institutional users subject to qualification review.","sourceIds":["mexc-auto-trading"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-kraken-cancel-on-disconnect-open-order-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-04T06:14:00.000Z","updatedAt":"2026-10-04T06:14:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs Kraken Cancel-on-Disconnect and Open Order Controls","zh-Hans":"Binance 与 Kraken 断线撤单和开放订单控制对比"},"summary":{"en":"Binance and Kraken both expose order-cancellation controls, but they solve different automation risks.","zh-Hans":"Binance 与 Kraken 断线撤单和开放订单控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance documents a DELETE /api/v3/openOrders endpoint that cancels all active orders on a symbol.","sourceIds":["binance-rest-trade"],"risk":"medium"},{"id":"c2","text":"Binance says the cancel-all-open-orders endpoint is signed and requires an API key header.","sourceIds":["binance-rest-trade"],"risk":"medium"},{"id":"c3","text":"Binance's sample response includes canceled order state and order-list details.","sourceIds":["binance-rest-trade"],"risk":"medium"},{"id":"c4","text":"Kraken describes cancelAllOrdersAfter as a dead-man-switch mechanism for network malfunction, extreme latency or matching-engine downtime.","sourceIds":["kraken-cancel-disconnect"],"risk":"low"},{"id":"c5","text":"Kraken says the client must keep sending requests to push back the trigger time or set timeout 0 to disable the mechanism.","sourceIds":["kraken-cancel-disconnect"],"risk":"low"},{"id":"c6","text":"Kraken recommends a 60-second timeout refreshed every 15 to 30 seconds and disabling the timer ahead of scheduled trading-engine maintenance.","sourceIds":["kraken-cancel-disconnect"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-hidden-complexity-stablecoin-defi-data-measurement-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-04T06:14:00.000Z","updatedAt":"2026-10-04T06:14:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Hidden Complexity and Stablecoin DeFi Data Measurement Risk Map","zh-Hans":"BIS Hidden Complexity 与稳定币 DeFi 数据测量风险地图"},"summary":{"en":"The BIS working paper Hidden by complexity? makes a practical point for crypto decision content: public blockchain data is abundant, but activity measures can change materially depending on how transfers, smart contracts,.","zh-Hans":"BIS Hidden Complexity 与稳定币 DeFi 数据测量风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"BIS Working Paper 1377 studies transfer values, token issuance, decentralised exchange activity and stablecoin holdings using granular data.","sourceIds":["bis-hidden-complexity"],"risk":"medium"},{"id":"c2","text":"The BIS working paper says commonly used measures of cryptoasset and DeFi activity can differ substantially depending on how blockchain data are treated.","sourceIds":["bis-hidden-complexity"],"risk":"medium"},{"id":"c3","text":"The BIS annual economic report chapter says tokenisation integrates messaging, reconciliation and asset transfer into a single operation.","sourceIds":["bis-next-gen"],"risk":"medium"},{"id":"c4","text":"The BIS annual economic report chapter says stablecoins often trade at varying exchange rates, undermining singleness.","sourceIds":["bis-next-gen"],"risk":"low"},{"id":"c5","text":"The BIS stablecoin impact paper says widespread stablecoin use could affect the international monetary and financial system, especially in emerging markets and developing economies.","sourceIds":["bis-stablecoin-impact"],"risk":"low"},{"id":"c6","text":"The BIS tokenisation summary says settlement assets can include stablecoins, tokenised bank deposits or central bank money, each with different risk profiles.","sourceIds":["bis-tokenisation-summary"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-com-exchange-2fa-withdrawal-whitelist-readiness-checklist","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-04T06:14:00.000Z","updatedAt":"2026-10-04T06:14:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto.com 2FA, Withdrawal Whitelist and Withdrawal Readiness Checklist","zh-Hans":"Crypto.com 2FA、提现白名单与提现准备清单"},"summary":{"en":"Crypto.com official help pages frame withdrawal readiness as a security-control workflow rather than a simple send button.","zh-Hans":"Crypto.com 2FA、提现白名单与提现准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Crypto.com says 2FA is an additional security layer and is required for certain actions.","sourceIds":["crypto-com-2fa"],"risk":"medium"},{"id":"c2","text":"Crypto.com says its TOTP code is a temporary six-digit code that works for 30 seconds.","sourceIds":["crypto-com-2fa"],"risk":"medium"},{"id":"c3","text":"Crypto.com lists crypto withdrawal, fiat withdrawal and wallet address whitelist among actions tied to 2FA.","sourceIds":["crypto-com-2fa"],"risk":"medium"},{"id":"c4","text":"Crypto.com withdrawal guidance says address whitelisting is required when sending crypto to a new external address.","sourceIds":["crypto-com-withdrawals"],"risk":"low"},{"id":"c5","text":"Crypto.com says an untrusted device may require passkey, passcode and authenticator-code verification for whitelisting.","sourceIds":["crypto-com-withdrawals"],"risk":"low"},{"id":"c6","text":"Crypto.com says a withdrawal request confirmation email acknowledges the request, while a separate notification follows processing.","sourceIds":["crypto-com-withdrawals"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-create-luno-account-verify-identity-and-secure-sends","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-04T06:14:00.000Z","updatedAt":"2026-10-04T06:14:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"How to Create a Luno Account, Verify Identity and Secure Sends","zh-Hans":"如何创建 Luno 账户、完成身份核验并安全开启转币"},"summary":{"en":"A safe Luno onboarding flow should be treated as account creation plus identity, device and send-control setup, not as a reward or deposit instruction. Luno's sign-up help says web users create an account from luno.","zh-Hans":"本文最有价值的地方是克制。安全的 Luno onboarding 应被视作开户、身份、设备与转币控制设置，而不是奖励或入金指令。Luno 注册帮助说明，网页用户从 luno.com 使用邮箱和强密码创建账户，移动端用户从 app 开始；确认邮件证明用户能访问该注册邮箱。"},"claims":[{"id":"c1","text":"Luno's sign-up guide says web users go to www.luno.com, select Create Account, enter an email address and create a strong password.","sourceIds":["luno-signup"],"risk":"medium"},{"id":"c2","text":"Luno says it sends an email link to confirm access to the email address used for sign-up.","sourceIds":["luno-signup"],"risk":"medium"},{"id":"c3","text":"Luno account-safety guidance treats two-factor authentication as an important security measure.","sourceIds":["luno-account-safety"],"risk":"medium"},{"id":"c4","text":"Luno trusted-device guidance warns that Luno will not contact users and ask them to remove a trusted device, passkey or 2FA.","sourceIds":["luno-trusted-device"],"risk":"low"},{"id":"c5","text":"Luno's send guide says crypto sends are disabled by default for security reasons.","sourceIds":["luno-send-crypto"],"risk":"low"},{"id":"c6","text":"Luno says enabling sends usually has a waiting period before activation and may take longer in some supported countries.","sourceIds":["luno-send-crypto"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-crypto-custody-tokenized-security-rights-boundary-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-04T06:14:00.000Z","updatedAt":"2026-10-04T06:14:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Crypto Custody Proposal and Tokenized Security Rights Boundary Map","zh-Hans":"SEC 加密资产托管提案与代币化证券权利边界地图"},"summary":{"en":"The SEC's October 1, 2026 crypto custody proposal and its January 2026 tokenized-securities staff statement should be read together as boundary material, not as a product endorsement.","zh-Hans":"SEC 加密资产托管提案与代币化证券权利边界地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"The SEC press release says the Commission proposed rules and amendments for custody of crypto assets by registered investment advisers and regulated funds.","sourceIds":["sec-custody-press"],"risk":"medium"},{"id":"c2","text":"The SEC press release says the proposal would permit crypto assets to be held in self-custody under certain circumstances and allow state trust companies as custodians for client and regulated fund crypto assets.","sourceIds":["sec-custody-press"],"risk":"medium"},{"id":"c3","text":"Chairman Atkins' statement says the proposal is intended to provide a compliant pathway for investment advisers and funds where none existed before.","sourceIds":["sec-custody-statement"],"risk":"medium"},{"id":"c4","text":"The SEC tokenized-securities statement says a tokenized security is a security formatted as or represented by a crypto asset with ownership records maintained on or through crypto networks.","sourceIds":["sec-tokenized-securities"],"risk":"low"},{"id":"c5","text":"The SEC tokenized-securities statement says tokenized securities vary in structure and rights and generally fall into issuer-sponsored and third-party tokenized categories.","sourceIds":["sec-tokenized-securities"],"risk":"low"},{"id":"c6","text":"Commissioner Peirce's tokenization statement says tokenized securities are still securities and market participants must consider federal securities laws.","sourceIds":["sec-peirce-tokenization"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-vs-kraken-websocket-authentication-reconnect-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-04T03:12:00.000Z","updatedAt":"2026-10-04T03:12:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase vs Kraken WebSocket Authentication and Reconnect Controls","zh-Hans":"Coinbase 与 Kraken WebSocket 认证和重连控制对比"},"summary":{"en":"Coinbase Advanced Trade and Kraken both publish WebSocket authentication paths, but the operational control object is different.","zh-Hans":"Coinbase 与 Kraken WebSocket 认证和重连控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase's Advanced Trade documentation says the Advanced API supports programmatic trading and order management with REST API and WebSocket protocol.","sourceIds":["coinbase-ws-overview"],"risk":"medium"},{"id":"c2","text":"Coinbase's SDK authentication documentation describes building a JWT for connecting to the WebSocket API.","sourceIds":["coinbase-jwt-sdk"],"risk":"medium"},{"id":"c3","text":"Coinbase Help separates Exchange WebSocket feeds and Advanced Trade WebSocket feeds in its developer-platform help surface.","sourceIds":["coinbase-help-websocket"],"risk":"medium"},{"id":"c4","text":"Kraken's WebSocket FAQ says public market data feeds use wss://ws.kraken.com and private authenticated account data and trading endpoints use wss://ws-auth.kraken.com.","sourceIds":["kraken-websocket-faq"],"risk":"low"},{"id":"c5","text":"Kraken's WebSocket FAQ says authentication is not required for public market data feeds but a valid authentication token is required for private feeds.","sourceIds":["kraken-websocket-faq"],"risk":"low"},{"id":"c6","text":"Kraken's private-feed guide says the API client must request an authentication token through the REST API and provide the same token when subscribing to private feeds.","sourceIds":["kraken-private-feeds"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fatf-2026-virtual-assets-travel-rule-implementation-action-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-04T03:12:00.000Z","updatedAt":"2026-10-04T03:12:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"FATF 2026 Virtual Assets and Travel Rule Implementation Action Map","zh-Hans":"FATF 2026 虚拟资产与 Travel Rule 实施行动地图"},"summary":{"en":"FATF's 2026 virtual-assets materials frame Travel Rule implementation as a jurisdiction and VASP compliance gap, not a user-facing guarantee that every exchange transfer will carry the same data, timing or support outcome.","zh-Hans":"FATF 2026 虚拟资产与 Travel Rule 实施行动地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"FATF's July 2026 targeted update says it assesses progress and remaining gaps in implementation of Recommendation 15 across the FATF Global Network.","sourceIds":["fatf-2026-targeted-update"],"risk":"medium"},{"id":"c2","text":"FATF's July 2026 targeted update says jurisdictions have continued progress on virtual-asset risk assessments, regulatory approaches, licensing or registering VASPs, implementing the Travel Rule and advancing supervisory and enforcement action.","sourceIds":["fatf-2026-targeted-update"],"risk":"medium"},{"id":"c3","text":"FATF's Recommendations page says the FATF Recommendations were amended in June 2026.","sourceIds":["fatf-recommendations"],"risk":"medium"},{"id":"c4","text":"FATF's June 2026 R.16 consultation says the new guidance is intended to support implementation of new travel-rule requirements by the deadline of 2030.","sourceIds":["fatf-r16-consultation"],"risk":"low"},{"id":"c5","text":"FATF's virtual-assets guidance says countries should apply Recommendation 16 to virtual-asset transfers in the context commonly called the Travel Rule.","sourceIds":["fatf-va-vasp-guidance"],"risk":"low"},{"id":"c6","text":"Bitpanda's withdrawal documentation shows a platform-level example where recipient name and wallet host are requested due to Travel Rule.","sourceIds":["bitpanda-withdraw-crypto"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-bitpanda-account-verification-2fa-anti-phishing-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-04T03:12:00.000Z","updatedAt":"2026-10-04T03:12:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up Bitpanda Account Verification, 2FA and Anti-Phishing Safely","zh-Hans":"如何安全设置 Bitpanda 账户验证、2FA 和反钓鱼码"},"summary":{"en":"A safe Bitpanda onboarding flow is not just creating an account. Bitpanda's verification guide says users sign in, choose Verify now, enter personal details, confirm accuracy, enter an SMS PIN, select citizenship, preferred.","zh-Hans":"本文最有价值的地方是克制。安全的 Bitpanda 入门流程不只是创建账户。Bitpanda 验证指南说明，用户登录后选择 Verify now，输入个人信息并确认准确性，输入 SMS PIN，选择国籍、首选语言和证件类型，然后进入验证合作方流程。"},"claims":[{"id":"c1","text":"Bitpanda's verification guide says users should sign in, select Verify now, enter personal details, confirm accuracy, enter an SMS PIN and continue through a verification partner.","sourceIds":["bitpanda-verify"],"risk":"medium"},{"id":"c2","text":"Bitpanda's verification guide says personal data entered on Bitpanda must match the identity document used for verification.","sourceIds":["bitpanda-verify"],"risk":"medium"},{"id":"c3","text":"Bitpanda's 2FA guide says 2FA adds a numerical code generated by an authenticator app in addition to email and password login.","sourceIds":["bitpanda-2fa"],"risk":"medium"},{"id":"c4","text":"Bitpanda's 2FA guide tells users to secure the displayed 2FA recovery code and notes it is needed to reset 2FA if a smartphone is lost.","sourceIds":["bitpanda-2fa"],"risk":"low"},{"id":"c5","text":"Bitpanda's anti-phishing FAQ says a personalised anti-phishing code appears in official direct communications such as emails and SMS messages.","sourceIds":["bitpanda-antiphishing"],"risk":"low"},{"id":"c6","text":"Bitpanda's crypto-withdrawal guide says users must choose the correct network and provide recipient name and wallet host due to Travel Rule when sending to external wallets.","sourceIds":["bitpanda-withdraw-crypto"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-api-key-ip-allowlist-expiry-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-04T03:12:00.000Z","updatedAt":"2026-10-04T03:12:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"OKX API Key IP Allowlist and Expiry Readiness Checklist","zh-Hans":"OKX API Key IP 白名单和过期规则准备清单"},"summary":{"en":"OKX's API documentation and help center make API-key operation a permission and network-control problem, not a one-time key-creation task.","zh-Hans":"OKX API Key IP 白名单和过期规则准备清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"OKX's API guide says API-key permissions include Read, Trade and Withdraw.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c2","text":"OKX's API guide says the passphrase cannot be recovered if lost and a new API key must be created.","sourceIds":["okx-api-guide","okx-api-faq"],"risk":"medium"},{"id":"c3","text":"OKX's API guide says clients are strongly recommended to link API keys to IP addresses.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c4","text":"OKX's API guide says each API key can bind up to 20 IP addresses and supports IPv4, IPv6 and network-segment formats.","sourceIds":["okx-api-guide","okx-api-faq"],"risk":"low"},{"id":"c5","text":"OKX's API guide says API keys not linked to an IP address and having trade or withdraw permissions expire after 14 days of inactivity.","sourceIds":["okx-api-guide"],"risk":"low"},{"id":"c6","text":"OKX's API FAQ says failed API deposit, withdrawal or transfer troubleshooting should check API permissions, currency, network, destination account, address book or whitelist requirements and returned error code.","sourceIds":["okx-api-faq"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"withdrawal-address-verification-expiry-app-only-controls-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-04T03:12:00.000Z","updatedAt":"2026-10-04T03:12:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Withdrawal Address Verification Expiry and App-Only Controls Radar","zh-Hans":"提现地址验证过期与 App-only 控制雷达"},"summary":{"en":"The current venue evidence shows that withdrawal-address safety is not one uniform whitelist.","zh-Hans":"提现地址验证过期与 App-only 控制雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"OKX says allowlist lets users withdraw only to addresses saved in the address book.","sourceIds":["okx-withdraw-allowlist"],"risk":"medium"},{"id":"c2","text":"OKX says an address verified for 30 days must be used within 30 days to maintain verified status and that a withdrawal extends the expiry date 30 days after the latest withdrawal date.","sourceIds":["okx-withdraw-allowlist"],"risk":"medium"},{"id":"c3","text":"Bybit describes withdrawal-security controls including withdrawal address whitelist, daily whitelist withdrawal limit, address-book-only withdrawals, new-address lock, withdrawal protection and app-only withdrawals.","sourceIds":["bybit-withdrawal-security"],"risk":"medium"},{"id":"c4","text":"Coinbase says users can use an Address book allowlist to add and store crypto addresses they know and trust.","sourceIds":["coinbase-account-security"],"risk":"low"},{"id":"c5","text":"Kraken documents adding and confirming a new cryptocurrency withdrawal address.","sourceIds":["kraken-add-address"],"risk":"low"},{"id":"c6","text":"Bitpanda's withdrawal guide says users need recipient name and wallet host due to Travel Rule when sending crypto to external wallets.","sourceIds":["bitpanda-withdraw-crypto"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fsb-bis-stablecoin-arrangements-implementation-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-01T12:16:00.000Z","updatedAt":"2026-10-01T12:16:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"FSB and BIS Stablecoin Arrangements Implementation Risk Map","zh-Hans":"FSB 与 BIS 稳定币安排实施风险图"},"summary":{"en":"FSB and BIS materials point to the same practical conclusion for stablecoin users and platforms: a stablecoin arrangement is not only a token, reserve asset or wallet interface.","zh-Hans":"FSB 与 BIS 稳定币安排实施风险图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"FSB maintains work on crypto-assets and global stablecoins as a financial-innovation and financial-stability policy area.","sourceIds":["fsb-crypto-assets"],"risk":"medium"},{"id":"c2","text":"BIS/CPMI-IOSCO materials apply financial-market-infrastructure principles to stablecoin arrangements.","sourceIds":["bis-stablecoin-arrangements"],"risk":"medium"},{"id":"c3","text":"ESMA publishes MiCA materials covering crypto-asset regulation, issuers and crypto-asset service providers in Europe.","sourceIds":["esma-mica"],"risk":"medium"},{"id":"c4","text":"Venue transfer controls such as Travel Rule disclosures are implementation evidence, but they do not replace issuer, reserve and redemption analysis.","sourceIds":["binance-travel-rule","fsb-crypto-assets"],"risk":"low"},{"id":"c5","text":"A stablecoin route should not be treated as cash-equivalent unless issuer status, reserve mechanics, redemption rights and operational controls are current and applicable.","sourceIds":["fsb-crypto-assets","bis-stablecoin-arrangements","esma-mica"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-crypto-withdrawal-network-address-confirmation-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-01T12:16:00.000Z","updatedAt":"2026-10-01T12:16:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken Crypto Withdrawal Network and Address Confirmation Checklist","zh-Hans":"Kraken 加密提现网络与地址确认清单"},"summary":{"en":"Kraken's withdrawal documentation makes a simple but high-impact distinction: a crypto withdrawal is not ready until the destination address, network, funding two-factor check and any hold condition are all understood.","zh-Hans":"本文最有价值的地方是克制。Kraken 的提现文档有一个简单但影响很大的区分：加密提现必须同时确认目的地址、网络、funding 2FA 和任何 hold 条件，才算准备好。Kraken 提现指南要求用户选择资产、选择正确网络、添加或选择提现地址，并完成所需检查。"},"claims":[{"id":"c1","text":"Kraken's crypto withdrawal guide requires selecting the asset and the network before completing a withdrawal.","sourceIds":["kraken-withdraw-crypto"],"risk":"medium"},{"id":"c2","text":"Kraken's withdrawal guide warns that using the wrong network can result in loss of funds.","sourceIds":["kraken-withdraw-crypto"],"risk":"medium"},{"id":"c3","text":"Kraken's address-confirmation guidance says a new cryptocurrency withdrawal address must be added and confirmed before use.","sourceIds":["kraken-add-address"],"risk":"medium"},{"id":"c4","text":"Kraken's withdrawal-hold guidance describes holds caused by funding methods or security actions.","sourceIds":["kraken-withdrawal-hold"],"risk":"low"},{"id":"c5","text":"Kraken's unable-to-withdraw guidance distinguishes insufficient balance, withheld funds and other withdrawal restrictions.","sourceIds":["kraken-unable-withdraw"],"risk":"low"}],"relatedVenues":["kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-vs-kraken-proof-of-reserves-disclosure-scope-checklist","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-01T12:16:00.000Z","updatedAt":"2026-10-01T12:16:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"OKX vs Kraken Proof-of-Reserves Disclosure Scope Checklist","zh-Hans":"OKX 与 Kraken 储备证明披露范围清单"},"summary":{"en":"OKX and Kraken both publish proof-of-reserves material, but the decision should focus on disclosure scope rather than a generic trust label.","zh-Hans":"本文最有价值的地方是克制。OKX 与 Kraken 都公开储备证明材料，但用户决策应关注披露范围，而不是笼统的信任标签。OKX 的储备证明页面列出储备率、支持资产、钱包证据和用户自助验证材料。"},"claims":[{"id":"c1","text":"OKX publishes proof-of-reserves information with reserve ratios, supported assets and user-verification material.","sourceIds":["okx-por"],"risk":"medium"},{"id":"c2","text":"Kraken publishes proof-of-reserves information that describes cryptographic client-balance inclusion and reserve verification.","sourceIds":["kraken-por"],"risk":"medium"},{"id":"c3","text":"Binance also publishes a proof-of-reserves page, which makes reserve disclosures a comparable category rather than a single-venue feature.","sourceIds":["binance-por"],"risk":"medium"},{"id":"c4","text":"FSB materials frame crypto-asset and stablecoin activity as requiring risk, governance and financial-stability controls beyond a single disclosure page.","sourceIds":["fsb-crypto-assets"],"risk":"low"},{"id":"c5","text":"A proof-of-reserves snapshot does not by itself prove future liquidity, unsupported-asset coverage, complete off-chain liabilities or post-snapshot solvency.","sourceIds":["okx-por","kraken-por","fsb-crypto-assets"],"risk":"low"}],"relatedVenues":["okx","kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"reserve-proof-user-verification-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-01T12:16:00.000Z","updatedAt":"2026-10-01T12:16:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Reserve Proof User Verification Disclosure Radar","zh-Hans":"储备证明用户自助验证披露雷达"},"summary":{"en":"NexuAlpha Radar treats reserve proof as a disclosure system with several separate layers: asset list, wallet evidence, liability inclusion, user inclusion verification, method notes, timing and limitations.","zh-Hans":"本文最有价值的地方是克制。NexuAlpha Radar 把储备证明视为多层披露系统：资产列表、钱包证据、负债纳入、用户自助验证、方法说明、时间点和限制说明。OKX、Kraken 与 Binance 都公开 proof-of-reserves 页面，但有用的雷达评分不能把它们压缩成“有/没有”标签。"},"claims":[{"id":"c1","text":"OKX publishes a proof-of-reserves page with asset and verification material.","sourceIds":["okx-por"],"risk":"medium"},{"id":"c2","text":"Kraken publishes a proof-of-reserves page with cryptographic proof framing and client-balance verification material.","sourceIds":["kraken-por"],"risk":"medium"},{"id":"c3","text":"Binance publishes a proof-of-reserves page, adding a third official venue reference point for radar comparison.","sourceIds":["binance-por"],"risk":"medium"},{"id":"c4","text":"FSB materials frame crypto-asset activity as needing governance and risk controls beyond individual platform disclosures.","sourceIds":["fsb-crypto-assets"],"risk":"low"},{"id":"c5","text":"A reserve-proof disclosure should be evaluated separately from claims about future withdrawals, regulatory approval or complete financial-statement assurance.","sourceIds":["okx-por","kraken-por","binance-por","fsb-crypto-assets"],"risk":"low"}],"relatedVenues":["okx","kraken","binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"superstate-ustb-tokenized-treasury-recordkeeping-boundary","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-01T12:16:00.000Z","updatedAt":"2026-10-01T12:16:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Superstate USTB Tokenized Treasury Recordkeeping Boundary","zh-Hans":"Superstate USTB 代币化国债记录边界"},"summary":{"en":"Superstate USTB should be analyzed as a tokenized fund recordkeeping and eligibility structure, not as a generic onchain cash substitute. Superstate's USTB page presents a tokenized private fund backed by short-duration U.S.","zh-Hans":"Superstate USTB 代币化国债记录边界：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Superstate presents USTB as a tokenized private fund backed by short-duration U.S. government securities.","sourceIds":["superstate-ustb"],"risk":"medium"},{"id":"c2","text":"Superstate describes FundOS as infrastructure for bringing private funds, mutual funds and ETFs onchain.","sourceIds":["superstate-fundos"],"risk":"medium"},{"id":"c3","text":"Superstate materials describe transfer-agent and tokenization infrastructure connecting book-entry and supported blockchain records.","sourceIds":["superstate-fundos"],"risk":"medium"},{"id":"c4","text":"Superstate integrations material describes tokenized securities access within a KYC and allowlist perimeter.","sourceIds":["superstate-integrations"],"risk":"low"},{"id":"c5","text":"SEC staff tokenized-securities material says tokenization does not by itself resolve the legal rights and recordkeeping analysis for a security.","sourceIds":["sec-tokenized-securities"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-bitget-api-withdrawal-ip-allowlist-control-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-01T12:08:00.000Z","updatedAt":"2026-10-01T12:08:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs Bitget API Withdrawal IP Allowlist Control Map","zh-Hans":"Binance 与 Bitget API 提现 IP 白名单控制地图"},"summary":{"en":"Binance and Bitget both connect withdrawal-capable API use to IP restrictions, but the public control language is different.","zh-Hans":"本文最有价值的地方是克制。Binance 与 Bitget 都把可提现 API 使用和 IP 限制绑定，但公开控制语言不同。Binance 表示启用提现权限必须添加 IPv4 访问限制；Bitget 的 API 材料则把 IP 白名单作为 API 风险控制实践，并说明通过 API 提币只能经由白名单 IP。"},"claims":[{"id":"c1","text":"Binance says adding IP access restrictions in IPv4 format is mandatory to enable withdrawal permission on API keys.","sourceIds":["s1"],"risk":"medium"},{"id":"c2","text":"Binance says unrestricted-IP-access HMAC API keys cannot have permissions other than reading unless users add IP access restrictions, use self-generated keys or disable default security controls.","sourceIds":["s1"],"risk":"medium"},{"id":"c3","text":"Bitget's API Key Terms tell users to manage API keys by single purpose, necessary permissions, deletion of unused keys, IP whitelisting and avoiding insecure storage or disclosure.","sourceIds":["s3"],"risk":"medium"},{"id":"c4","text":"Bitget's REST API documentation describes Read-Only, Trade, Transfer and Withdraw permissions, and says users can withdraw coins only through a whitelisted IP address.","sourceIds":["s4"],"risk":"low"},{"id":"c5","text":"OKX's API guide provides a cross-venue control comparison by documenting API key permissions and IP binding, including expiry behavior for trade or withdraw keys not linked to IP addresses.","sourceIds":["s5"],"risk":"low"}],"relatedVenues":["binance","bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-tokenization-service-faq-governance-investor-protection-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-01T12:08:00.000Z","updatedAt":"2026-10-01T12:08:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Tokenization Service FAQ Governance and Investor Protection Map","zh-Hans":"DTCC Tokenization Service FAQ 治理与投资者保护地图"},"summary":{"en":"DTCC's tokenization materials should be read as market-infrastructure documentation, not as a blanket signal that every tokenized security product has the same rights.","zh-Hans":"DTCC Tokenization Service FAQ 治理与投资者保护地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"DTCC describes its Tokenization Service as infrastructure intended to connect traditional and blockchain-based environments for tokenized assets.","sourceIds":["s1"],"risk":"medium"},{"id":"c2","text":"DTCC says tokenized DTC assets can move between traditional and blockchain ecosystems using the same CUSIP across approved networks.","sourceIds":["s1"],"risk":"medium"},{"id":"c3","text":"DTCC states that DTC-issued tokens are designed to represent the same legal rights, economic interest and investor protections associated with the underlying securities.","sourceIds":["s1","s3"],"risk":"medium"},{"id":"c4","text":"The SEC's tokenized securities statement distinguishes issuer-sponsored tokenization from third-party tokenized securities products.","sourceIds":["s4"],"risk":"low"},{"id":"c5","text":"The SEC statement on DTC's no-action letter says DTC's program would track transfers to record tokenized entitlements for DTC's official books and records.","sourceIds":["s5"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-api-key-ip-allowlist-inactivity-expiry-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-01T12:08:00.000Z","updatedAt":"2026-10-01T12:08:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange API Key IP Allowlist and Inactivity Expiry Disclosure Radar","zh-Hans":"交易所 API Key IP 白名单与不活跃过期披露雷达"},"summary":{"en":"A practical exchange API radar should track three public disclosure fields before automation goes live: whether withdraw or trade keys require IP binding, whether inactive unbound keys expire, and whether each venue tells users.","zh-Hans":"本文最有价值的地方是克制。实用的交易所 API 雷达应在自动化上线前追踪三类公开披露字段：提现或交易 Key 是否需要 IP 绑定、未绑定 IP 的不活跃 Key 是否会过期、以及平台是否说明泄露后如何轮换或删除 Key。真正有用的输出是带日期的控制清单，而不是宣称某个平台最安全。"},"claims":[{"id":"c1","text":"OKX documents API key permissions, IP binding, and a 14-day inactivity-expiry rule for trade or withdraw keys not linked to IP addresses.","sourceIds":["s1"],"risk":"medium"},{"id":"c2","text":"OKX's API Agreement requires minimum required permissions, MFA, encrypted storage, IP allowlisting where available and rotation after suspected compromise.","sourceIds":["s2"],"risk":"medium"},{"id":"c3","text":"Binance says withdrawal permission requires IPv4 access restrictions and describes limitations on unrestricted-IP-access API keys.","sourceIds":["s3"],"risk":"medium"},{"id":"c4","text":"Bitget's REST API documentation says withdraw permission authorizes withdrawals and coin withdrawals through API require a whitelisted IP address.","sourceIds":["s4"],"risk":"low"},{"id":"c5","text":"Kraken's API security guidance supports permission minimization and other key-security controls, giving the radar a third-party cross-check for least-privilege framing.","sourceIds":["s5"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-third-party-app-ip-whitelist-broker-api-key-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-01T12:08:00.000Z","updatedAt":"2026-10-01T12:08:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"OKX Third-Party App IP Whitelist API Key Checklist","zh-Hans":"OKX 第三方应用 IP 白名单 API Key 清单"},"summary":{"en":"OKX's third-party app IP whitelist should be read as a broker-connection security control, not as a general endorsement of any app.","zh-Hans":"本文最有价值的地方是克制。OKX 的第三方应用 IP 白名单应被视为经纪商连接安全控制，而不是对任何应用的泛化背书。"},"claims":[{"id":"c1","text":"OKX says its Third Party App IP Whitelist limits API key usage to whitelisted broker servers when the broker supports the feature.","sourceIds":["s1"],"risk":"medium"},{"id":"c2","text":"OKX tells brokers to provide public server IP addresses in IPv4, IPv6 or CIDR format for whitelisting.","sourceIds":["s1"],"risk":"medium"},{"id":"c3","text":"OKX's user flow says users create an API key for the purpose of binding third-party apps and select a whitelisted third-party app from the dropdown.","sourceIds":["s1"],"risk":"medium"},{"id":"c4","text":"OKX's API Guide says API keys can be bound to IP addresses and trade or withdraw keys not linked to IP addresses may expire after 14 days of inactivity.","sourceIds":["s2"],"risk":"low"},{"id":"c5","text":"OKX's API Agreement requires commercially reasonable security measures, including minimum permissions, MFA, encrypted storage, IP allowlisting where available and rotation after suspected compromise.","sourceIds":["s3"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-innovation-exemption-permissioned-tokenized-nms-stock-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-01T12:08:00.000Z","updatedAt":"2026-10-01T12:08:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Innovation Exemption Permissioned Tokenized NMS Stock Risk Map","zh-Hans":"SEC Innovation Exemption 许可型代币化 NMS 股票风险地图"},"summary":{"en":"The SEC Innovation Exemption should be read as temporary, conditional relief for a narrow tokenized NMS stock trading model, not as a blanket approval of all tokenized-stock venues.","zh-Hans":"本文最有价值的地方是克制。SEC Innovation Exemption 应被理解为针对狭窄 tokenized NMS stock 交易模型的临时、附条件豁免，而不是所有代币化股票场所的通用批准。"},"claims":[{"id":"c1","text":"The SEC order grants temporary conditional exemptive relief from the exchange definition for Tokenized Securities Venues and from the dealer definition for certain liquidity providers.","sourceIds":["s1"],"risk":"medium"},{"id":"c2","text":"The SEC order describes permissioned trading of tokenized NMS stock using AMM liquidity pools as the covered model.","sourceIds":["s1"],"risk":"medium"},{"id":"c3","text":"Chairman Atkins's statement says anti-fraud and anti-manipulation provisions apply in full and lists conditions including sanctions compliance, permissioned access, no synthetics and issuer objection rights.","sourceIds":["s2"],"risk":"medium"},{"id":"c4","text":"Commissioner Uyeda's statement says the exemption includes public notice, transaction transparency, stoppage coordination, books and records, technology safeguards, symbol limits and volume caps.","sourceIds":["s3"],"risk":"low"},{"id":"c5","text":"The SEC's tokenized securities statement distinguishes issuer-sponsored tokenization from third-party tokenized securities structures, making product taxonomy part of the risk map.","sourceIds":["s5"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-project-pine-tokenised-monetary-operations-readiness-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-01T08:58:00.000Z","updatedAt":"2026-10-01T08:58:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Project Pine Tokenised Monetary Operations Readiness Map","zh-Hans":"BIS Project Pine 代币化货币操作准备地图"},"summary":{"en":"Project Pine is best read as central-bank infrastructure research, not as proof that public tokenized assets are ready for retail use.","zh-Hans":"本文最有价值的地方是克制。Project Pine 更适合作为央行基础设施研究来阅读，而不是公众代币化资产已可零售使用的证明。实用决策是先区分模拟货币政策操作、智能合约工具、代币化批发结算和零售 RWA 访问，再判断代币化市场的成熟度。 用户应获得一个更清楚的核验路径，而不是一个看似肯定、实则无法由公开证据承担的承诺。"},"claims":[{"id":"c1","text":"BIS describes Project Pine as a joint research study with the New York Fed on whether and how central banks can implement monetary-policy operations in a tokenised world.","sourceIds":["s1"],"risk":"medium"},{"id":"c2","text":"The Project Pine report says it developed and tested a prototype central-bank toolkit using smart contracts in a potential future tokenisation setting.","sourceIds":["s2"],"risk":"medium"},{"id":"c3","text":"BIS's Project Agora release describes tokenised central bank reserves and tokenised commercial bank deposits in wholesale cross-border payment testing.","sourceIds":["s3"],"risk":"medium"},{"id":"c4","text":"BIS's next-generation monetary system chapter says tokenised platforms can combine central bank reserves, commercial bank money and government bonds while preserving trust in central bank money.","sourceIds":["s4"],"risk":"low"},{"id":"c5","text":"The SEC tokenized-securities statement shows that tokenized security rights depend on structure, official records and transfer mechanics, not the token label alone.","sourceIds":["s5"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-trading-password-withdrawal-restriction-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-01T08:58:00.000Z","updatedAt":"2026-10-01T08:58:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange Trading Password and Withdrawal Restriction Disclosure Radar","zh-Hans":"交易所交易密码与提现限制披露 Radar"},"summary":{"en":"The radar finding is that withdrawal friction is often a security feature, not only an outage or support problem.","zh-Hans":"本文最有价值的地方是克制。本轮 radar 结论是：提现摩擦往往是安全功能，而不只是故障或客服问题。KuCoin、Gate US、Kraken 与 OKX 材料显示出交易密码、资金密码、API 权限、GSL、IP 白名单和轮换控制等不同形式，用户应在紧急提现或自动交易前先完成映射。"},"claims":[{"id":"c1","text":"KuCoin says its trading password is used to verify transactions including spot, futures, margin, withdrawals and API-related actions.","sourceIds":["s1"],"risk":"medium"},{"id":"c2","text":"KuCoin says certain security changes can temporarily suspend withdrawals for 24 hours.","sourceIds":["s2"],"risk":"medium"},{"id":"c3","text":"Gate US fund-password setup requires authenticator verification and the fund password is separate from the login password.","sourceIds":["s3"],"risk":"medium"},{"id":"c4","text":"Kraken documents a withdrawal-address API permission whose risk increases when paired with withdrawal capability.","sourceIds":["s4"],"risk":"low"},{"id":"c5","text":"OKX requires minimum permissions, MFA, IP allowlisting where available, encrypted storage and rotation after suspected API credential compromise.","sourceIds":["s5"],"risk":"low"}],"relatedVenues":["kucoin","kraken","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"gate-us-withdrawal-address-whitelist-verification-free-risk-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-01T08:58:00.000Z","updatedAt":"2026-10-01T08:58:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Gate US Withdrawal Address Whitelist Verification-Free Risk Checklist","zh-Hans":"Gate US 提现地址白名单免验证风险清单"},"summary":{"en":"Gate US withdrawal-address whitelist setup should be treated as a security-control change, not as a convenience toggle.","zh-Hans":"本文最有价值的地方是克制。Gate US 提现地址白名单设置应被视为安全控制变更，而不是便利开关。实用决策是：在把任何地址设为免验证前，先核验 KYC、资金密码、2FA、币种网络、trusted address 状态以及 24 小时限制触发条件。"},"claims":[{"id":"c1","text":"Gate US says users should complete KYC, set a fund password and enable two-factor authentication before using withdrawal-address whitelist setup.","sourceIds":["s1","s5"],"risk":"medium"},{"id":"c2","text":"Gate US describes trusted or verification-free addresses as destinations that can skip regular withdrawal verification after configuration.","sourceIds":["s1","s2"],"risk":"medium"},{"id":"c3","text":"Gate US says users should verify token, network and address accuracy before adding a trusted withdrawal address.","sourceIds":["s1","s2"],"risk":"medium"},{"id":"c4","text":"Gate US withdrawal FAQs say KYC completion, Google Authenticator changes or phone-number updates can temporarily restrict withdrawals for 24 hours.","sourceIds":["s3"],"risk":"low"},{"id":"c5","text":"Gate US fund-password guidance requires authenticator verification when setting the fund password.","sourceIds":["s4"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-kucoin-trading-password-and-withdrawal-checks-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-01T08:58:00.000Z","updatedAt":"2026-10-01T08:58:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up KuCoin Trading Password and Withdrawal Checks Safely","zh-Hans":"如何安全设置 KuCoin 交易密码与提现检查"},"summary":{"en":"A safe KuCoin setup should treat the trading password as an action gate, not as another login password.","zh-Hans":"本文最有价值的地方是克制。安全的 KuCoin 设置应把交易密码视为操作闸门，而不是另一个登录密码。入金前先设置或核验 Google 2FA 与六位交易密码，理解某些安全变更后的 24 小时提现限制，并在提现前检查币种、网络、账户类型和未成交订单状态。"},"claims":[{"id":"c1","text":"KuCoin says the trading password is a six-digit password used to verify transactions including spot, futures, margin trading, withdrawals and API-related actions.","sourceIds":["s1"],"risk":"medium"},{"id":"c2","text":"KuCoin says support will never ask for a user's trading password on any communication channel.","sourceIds":["s1"],"risk":"medium"},{"id":"c3","text":"KuCoin says withdrawals may be temporarily suspended for 24 hours after selected security changes such as changing or resetting the trading password.","sourceIds":["s2"],"risk":"medium"},{"id":"c4","text":"KuCoin's withdrawal guide says users need prepared account settings such as phone plus trading password or email plus Google 2FA plus trading password.","sourceIds":["s3"],"risk":"low"},{"id":"c5","text":"KuCoin's withdrawal guide says users should ensure funds are in the correct Funding or Trading account and check open orders if withdrawals remain unavailable.","sourceIds":["s3"],"risk":"low"}],"relatedVenues":["kucoin"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-vs-okx-api-withdrawal-address-permission-control-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-01T08:58:00.000Z","updatedAt":"2026-10-01T08:58:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken vs OKX API Withdrawal Address Permission Control Map","zh-Hans":"Kraken 与 OKX API 提现地址权限控制地图"},"summary":{"en":"Kraken and OKX both treat API credentials as high-impact account controls, but their public documentation frames the risk differently.","zh-Hans":"Kraken 与 OKX API 提现地址权限控制地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Kraken says the Add Withdrawal Addresses API permission allows an API key to add and remove withdrawal addresses on a Kraken account.","sourceIds":["s1"],"risk":"medium"},{"id":"c2","text":"Kraken warns that pairing Add Withdrawal Addresses with Withdraw Funds can let a compromised key add an address and initiate a withdrawal through the API.","sourceIds":["s1"],"risk":"medium"},{"id":"c3","text":"Kraken recommends IP whitelisting, expiry, permission separation and minimum required permissions when the permission is needed.","sourceIds":["s1","s2"],"risk":"medium"},{"id":"c4","text":"OKX's API Agreement requires commercially reasonable security measures including MFA, minimum required permissions, IP allowlisting where available, encrypted storage and rotation after suspected compromise.","sourceIds":["s3"],"risk":"low"},{"id":"c5","text":"OKX's public API guide documents request signing and authenticated account actions, but the user's private key scope and infrastructure IP state remain outside public evidence.","sourceIds":["s3","s4"],"risk":"low"}],"relatedVenues":["kraken","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-margin-collateral-ratio-update-liquidation-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-01T06:12:00.000Z","updatedAt":"2026-10-01T06:12:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Margin Collateral Ratio Update Liquidation Readiness Checklist","zh-Hans":"Binance 保证金抵押率更新与清算准备清单"},"summary":{"en":"Binance's September 2026 collateral-ratio update is best treated as a margin-risk control event, not as a token-quality signal.","zh-Hans":"本文最有价值的地方是克制。Binance 2026 年 9 月的抵押率更新应被视为保证金风控事件，而不是代币质量信号。实用决策是先核验受影响资产、借贷与转出能力、组合保证金 uniMMR 影响以及偿还路径，再考虑加杠杆或移动抵押品。 用户应获得一个更清楚的核验路径，而不是一个看似肯定、实则无法由公开证据承担的承诺。"},"claims":[{"id":"c1","text":"Binance announced collateral-ratio changes for Cross Margin and Portfolio Margin effective 2026-09-25 06:00 UTC.","sourceIds":["s1"],"risk":"medium"},{"id":"c2","text":"The official announcement states the update affects Cross Margin borrow and transfer-out collateral ratio and may affect Portfolio Margin uniMMR.","sourceIds":["s1"],"risk":"medium"},{"id":"c3","text":"Binance's margin collateral-limit help page says transfer-in or buy capacity can be capped or blocked when platform collateral limits are reached.","sourceIds":["s2"],"risk":"medium"},{"id":"c4","text":"The maximum-collateral-limit page says repayment transfers may remain possible up to the user's net debt even when transfer-in or buy capacity is blocked.","sourceIds":["s2"],"risk":"low"},{"id":"c5","text":"Binance's own risk language warns that cross-margining creates greater leverage and can lead to involuntary liquidation.","sourceIds":["s1","s5"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-vs-okx-api-key-permission-ip-allowlist-control-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-01T06:12:00.000Z","updatedAt":"2026-10-01T06:12:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase vs OKX API Key Permission and IP Allowlist Control Map","zh-Hans":"Coinbase 与 OKX API Key 权限及 IP 白名单控制对照"},"summary":{"en":"Coinbase and OKX both make API-key scope a security decision, but the controls are not identical.","zh-Hans":"Coinbase 与 OKX API Key 权限及 IP 白名单控制对照：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Exchange says API keys are tied to a single portfolio and require selecting permissions, passphrase and an IP address whitelist.","sourceIds":["s1"],"risk":"medium"},{"id":"c2","text":"Coinbase lists View, Transfer, Trade and Manage as API-key permission categories.","sourceIds":["s1"],"risk":"medium"},{"id":"c3","text":"Coinbase says the API secret and passphrase are shown only once and cannot be retrieved if lost.","sourceIds":["s1"],"risk":"medium"},{"id":"c4","text":"OKX's API Agreement requires commercially reasonable security measures including MFA, minimum required permissions, IP allowlisting where available, encrypted storage and rotation after suspected compromise.","sourceIds":["s2"],"risk":"low"},{"id":"c5","text":"OKX's API Agreement says users must notify OKX promptly if an Authorized AI Agent behaves anomalously or if an API credential security incident occurs.","sourceIds":["s2"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-collateral-appchain-tokenized-asset-mobility-readiness-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-10-01T06:12:00.000Z","updatedAt":"2026-10-01T06:12:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Collateral AppChain Tokenized Asset Mobility Readiness Map","zh-Hans":"DTCC Collateral AppChain 代币化资产流动性准备地图"},"summary":{"en":"DTCC's Collateral AppChain materials should be read as infrastructure-readiness evidence, not as a retail product launch.","zh-Hans":"本文最有价值的地方是克制。DTCC 的 Collateral AppChain 材料应被理解为基础设施准备证据，而不是面向零售用户的产品上线。关键问题是：当市场走向更连续的结算时，代币化抵押品流动能否保留记录、权益、控制、互操作性与运营治理。"},"claims":[{"id":"c1","text":"DTCC announced progress and timelines for DTC's tokenization service, including plans for initial limited production trades and an October 2026 launch plan.","sourceIds":["s1"],"risk":"medium"},{"id":"c2","text":"DTCC says the tokenization service is designed for DTC-custodied assets with the same entitlements, investor protections and ownership rights as traditional-form assets.","sourceIds":["s1"],"risk":"medium"},{"id":"c3","text":"DTCC describes the Collateral AppChain as supporting a move toward a single net pool of assets deployable across use cases.","sourceIds":["s2"],"risk":"medium"},{"id":"c4","text":"Swift says 17 banks were preparing to pilot live transactions using tokenised deposits on its blockchain-based ledger infrastructure.","sourceIds":["s4"],"risk":"low"},{"id":"c5","text":"The cited materials do not prove that a retail holder can redeem, transfer or pledge a tokenized asset outside the eligible participant and network constraints.","sourceIds":["s1","s2","s4"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-bitfinex-withdrawal-whitelist-2fa-and-kyc-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-01T06:12:00.000Z","updatedAt":"2026-10-01T06:12:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up Bitfinex Withdrawal Whitelist, 2FA and KYC Safely","zh-Hans":"如何安全设置 Bitfinex 提现白名单、2FA 与 KYC"},"summary":{"en":"A safe Bitfinex onboarding flow should separate identity verification from account-security setup.","zh-Hans":"本文最有价值的地方是克制。安全的 Bitfinex 入门流程应把身份核验和账户安全设置分开处理。先通过官方验证页面理解 KYC 要求，再在敏感账户操作前启用 2FA，谨慎锁定或禁用提现地址，并在降低提现安全性的变更后预期可能出现提现 hold。"},"claims":[{"id":"c1","text":"Bitfinex says individual verification is an AML, KYC and CTF compliance process and lists requirements for verification levels.","sourceIds":["s1"],"risk":"medium"},{"id":"c2","text":"Bitfinex says 2FA is required before users can operate account features and supports authenticator and U2F security-key methods.","sourceIds":["s2"],"risk":"medium"},{"id":"c3","text":"Bitfinex's withdrawal-whitelist guide says users should disable all currencies they do not plan to withdraw and add addresses for currencies they do use.","sourceIds":["s3"],"risk":"medium"},{"id":"c4","text":"Bitfinex says modifying an existing whitelist or turning on withdrawals for previously disabled currencies can trigger a five-day withdrawal hold.","sourceIds":["s3","s4"],"risk":"low"},{"id":"c5","text":"Bitfinex security guidance says address locking, 2FA and other settings reduce risk but do not remove the need for user-side security hygiene.","sourceIds":["s2","s5"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-cftc-crypto-asset-interpretation-jurisdiction-action-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-01T06:12:00.000Z","updatedAt":"2026-10-01T06:12:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"SEC-CFTC Crypto-Asset Interpretation Jurisdiction Action Map","zh-Hans":"SEC-CFTC 加密资产解释与管辖行动地图"},"summary":{"en":"The SEC's March 2026 interpretation, joined by the CFTC for Commodity Exchange Act administration, is useful as a jurisdiction checklist, not as blanket approval for crypto products.","zh-Hans":"本文最有价值的地方是克制。SEC 2026 年 3 月的解释文件，以及 CFTC 对商品交易法执行口径的配合，适合作为管辖清单，而不是任何加密产品的总括批准。实用决策是先分类资产、交易包装、服务中介角色和披露义务，再判断是否能声称某产品不属于证券处理范围。"},"claims":[{"id":"c1","text":"The SEC press release says the Commission issued an interpretation clarifying how federal securities laws apply to certain crypto assets and transactions.","sourceIds":["s1"],"risk":"medium"},{"id":"c2","text":"The same SEC release says the CFTC joined the interpretation to administer the Commodity Exchange Act consistent with the Commission's interpretation.","sourceIds":["s1"],"risk":"medium"},{"id":"c3","text":"The interpretation describes a token taxonomy that includes digital commodities, digital collectibles, digital tools, stablecoins and digital securities.","sourceIds":["s1"],"risk":"medium"},{"id":"c4","text":"The SEC's tokenized-securities statement says tokenized securities can vary by structure and rights afforded to holders.","sourceIds":["s2"],"risk":"low"},{"id":"c5","text":"The cited SEC statements do not eliminate the need to analyze investment contracts, intermediaries, disclosures or tokenized-security rights.","sourceIds":["s1","s2","s5"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-one-step-withdrawal-whitelist-limit-control-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-10-01T03:12:00.000Z","updatedAt":"2026-10-01T03:12:00.000Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Binance One-Step Withdrawal and Whitelist Limit Control Checklist","zh-Hans":"Binance 一步提现与白名单提现限制控制清单"},"summary":{"en":"Binance withdrawal settings should be read as several separate controls rather than one address-book switch.","zh-Hans":"本文最有价值的地方是克制。Binance 的提现设置应被理解为几组不同控制，而不是一个地址簿开关。Binance 表示，一步提现可允许向白名单地址小额提现时不完成 2FA，同时也说明仍可能被要求完成 2FA。"},"claims":[{"id":"c1","text":"Binance says one-step withdrawal can permit small withdrawals to whitelisted addresses without completing 2FA, although 2FA may still be required.","sourceIds":["binance-withdrawal-settings"],"risk":"medium"},{"id":"c2","text":"Binance says whitelist withdrawal limit suspends withdrawals to newly added whitelist addresses for a selected time period.","sourceIds":["binance-withdrawal-settings"],"risk":"medium"},{"id":"c3","text":"Binance recommends keeping whitelist withdrawal limit enabled because disabling it allows immediate withdrawals to newly added whitelisted addresses.","sourceIds":["binance-withdrawal-settings"],"risk":"medium"},{"id":"c4","text":"Binance says Travel Rule flows can require originator or beneficiary information for affected crypto transfers.","sourceIds":["binance-travel-rule"],"risk":"low"},{"id":"c5","text":"Binance says Satoshi Test and Travel Rule Address Book features can help verify or pre-validate self-hosted wallet transfer information.","sourceIds":["binance-satoshi-address-book"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bitstamp-withdrawal-whitelist-vs-kraken-global-settings-lock-control-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-10-01T03:12:00.000Z","updatedAt":"2026-10-01T03:12:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Bitstamp Withdrawal Whitelist vs Kraken Global Settings Lock Control Map","zh-Hans":"Bitstamp 提现白名单与 Kraken Global Settings Lock 控制图"},"summary":{"en":"Bitstamp withdrawal whitelisting and Kraken Global Settings Lock protect different parts of the withdrawal-risk chain.","zh-Hans":"Bitstamp 提现白名单与 Kraken Global Settings Lock 控制图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bitstamp says withdrawal address whitelisting restricts crypto withdrawals to addresses added to the whitelist.","sourceIds":["bitstamp-whitelisting"],"risk":"medium"},{"id":"c2","text":"Bitstamp says 2FA and confirmation emails help protect withdrawal attempts.","sourceIds":["bitstamp-security"],"risk":"medium"},{"id":"c3","text":"Bitstamp API documentation describes withdrawal errors tied to unverified addresses and API-key withdrawal address restrictions.","sourceIds":["bitstamp-api"],"risk":"medium"},{"id":"c4","text":"Kraken says Funding 2FA requires a code for withdrawals but does not prevent adding cryptocurrency withdrawal addresses.","sourceIds":["kraken-funding-2fa"],"risk":"low"},{"id":"c5","text":"Kraken says Global Settings Lock can prevent account-setting changes and can block an attacker from adding a withdrawal address.","sourceIds":["kraken-gsl","kraken-funding-2fa"],"risk":"low"}],"relatedVenues":["kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cftc-mention-markets-event-contract-manipulation-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-10-01T03:12:00.000Z","updatedAt":"2026-10-01T03:12:00.000Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC Mention Markets Event-Contract Manipulation Risk Map","zh-Hans":"CFTC Mention Markets 事件合约操纵风险图"},"summary":{"en":"The CFTC's September 22, 2026 mention-markets advisory matters to crypto and prediction-market users because it focuses on event-contract design, verifiability and manipulation risk rather than token price.","zh-Hans":"CFTC Mention Markets 事件合约操纵风险图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"CFTC release listings identify September 22, 2026 release 9302-26 as a staff advisory on mention markets.","sourceIds":["cftc-mention-press","cftc-press-releases"],"risk":"medium"},{"id":"c2","text":"CFTC staff-letter materials describe mention markets as event contracts tied to whether an individual says or mentions words, attends or appears at an event, or otherwise interacts with another person.","sourceIds":["cftc-staff-letters"],"risk":"medium"},{"id":"c3","text":"CFTC staff-letter materials connect the advisory to DCM obligations under Part 40 and core principles.","sourceIds":["cftc-staff-letters"],"risk":"medium"},{"id":"c4","text":"CFTC innovation materials say the advisory reminds DCMs to list only contracts not readily susceptible to manipulation.","sourceIds":["cftc-innovation"],"risk":"low"},{"id":"c5","text":"CFTC innovation materials say contract submissions should include complete, contract-specific analysis.","sourceIds":["cftc-innovation"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-enable-mexc-withdrawal-whitelist-and-kyc-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-10-01T03:12:00.000Z","updatedAt":"2026-10-01T03:12:00.000Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"How to Enable MEXC Withdrawal Whitelist and KYC Safely","zh-Hans":"如何安全启用 MEXC 提现白名单与 KYC"},"summary":{"en":"A safe MEXC withdrawal-whitelist setup should start with verified account status and official support pages, not a social-message link.","zh-Hans":"本文最有价值的地方是克制。安全启用 MEXC 提现白名单，应从已核验账户状态和官方帮助页面开始，而不是社交消息链接。MEXC 的加密充值与提现帮助页描述了 Fast Withdrawal，以及需要完成安全核验、把提现限制在白名单地址的 Withdrawal Whitelist 控制。"},"claims":[{"id":"c1","text":"MEXC's crypto deposit and withdrawal help describes a Withdrawal Whitelist control that restricts withdrawals to whitelisted addresses.","sourceIds":["mexc-deposit-withdrawal"],"risk":"medium"},{"id":"c2","text":"MEXC's withdrawal whitelist setup requires security verification.","sourceIds":["mexc-deposit-withdrawal"],"risk":"medium"},{"id":"c3","text":"MEXC materials describe Fast Withdrawal separately from whitelist restrictions and note that additional verification may still be required based on account security status.","sourceIds":["mexc-deposit-withdrawal"],"risk":"medium"},{"id":"c4","text":"MEXC KYC materials tie account functions and support escalation to verification status.","sourceIds":["mexc-kyc"],"risk":"low"},{"id":"c5","text":"MEXC Support Center provides official entries for KYC verification guides, withdrawal FAQ and online customer service.","sourceIds":["mexc-support","mexc-withdrawal-faq"],"risk":"low"}],"relatedVenues":["mexc"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"withdrawal-whitelist-waiting-period-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-10-01T03:12:00.000Z","updatedAt":"2026-10-01T03:12:00.000Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Withdrawal Whitelist Waiting-Period Disclosure Radar","zh-Hans":"提现白名单等待期披露雷达"},"summary":{"en":"NexuAlpha Radar scores withdrawal-whitelist controls by how clearly a venue discloses what happens after a new address is added, not by whether the venue uses the word whitelist.","zh-Hans":"本文最有价值的地方是克制。NexuAlpha Radar 评价提现白名单控制时，关注的是平台是否清楚披露新增地址后的限制，而不是是否使用 whitelist 这个词。Coinbase Exchange 表示，在初始白名单窗口后，新地址簿条目需要经过 48 小时等待期。"},"claims":[{"id":"c1","text":"Coinbase Exchange says new addresses added after the initial whitelisting window must go through a 48-hour hold before withdrawals.","sourceIds":["coinbase-whitelisting"],"risk":"medium"},{"id":"c2","text":"Binance says whitelist withdrawal limit can suspend withdrawals to newly added whitelist addresses for a selected time period.","sourceIds":["binance-withdrawal-settings"],"risk":"medium"},{"id":"c3","text":"OKX says a newly added recipient cannot be used for withdrawals for 24 hours when Allowlist is enabled.","sourceIds":["okx-allowlist"],"risk":"medium"},{"id":"c4","text":"Bitstamp says withdrawal whitelisting restricts crypto withdrawals to addresses added to the whitelist.","sourceIds":["bitstamp-whitelisting"],"risk":"low"},{"id":"c5","text":"Waiting-period disclosure is not the same as proof that a user's private withdrawal will succeed.","sourceIds":["coinbase-whitelisting","binance-withdrawal-settings","okx-allowlist","bitstamp-whitelisting"],"risk":"low"}],"relatedVenues":["binance","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-okx-self-trade-prevention-reconciliation-radar","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-30T23:58:00.000Z","updatedAt":"2026-09-30T23:58:00.000Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Binance and OKX Self-Trade Prevention Reconciliation Radar","zh-Hans":"Binance 与 OKX 自成交防护对账雷达"},"summary":{"en":"NexuAlpha Radar treats self-trade prevention as an order-reconciliation problem, not as a generic market-integrity badge.","zh-Hans":"Binance 与 OKX 自成交防护对账雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance defines STP as preventing a user's orders or tradeGroupId's orders from matching against their own.","sourceIds":["binance-spot-glossary"],"risk":"medium"},{"id":"c2","text":"Binance glossary describes prevented execution fields and preventedMatchId for STP events.","sourceIds":["binance-spot-glossary","binance-prevented-matches"],"risk":"medium"},{"id":"c3","text":"OKX says mandatory STP applies at master-account level across affiliated sub-accounts.","sourceIds":["okx-stp-guide"],"risk":"medium"},{"id":"c4","text":"OKX says supported STP modes include cancel_maker, cancel_taker and cancel_both.","sourceIds":["okx-stp-guide"],"risk":"low"},{"id":"c5","text":"OKX says orders may be canceled by the system for self-trade prevention and cancelSource can identify the reason.","sourceIds":["okx-order-states","okx-stp-guide"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-exchange-whitelisting-vs-kraken-funding-2fa-withdrawal-control-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-30T23:58:00.000Z","updatedAt":"2026-09-30T23:58:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Exchange Whitelisting vs Kraken Funding 2FA Withdrawal Control Map","zh-Hans":"Coinbase Exchange 允许名单与 Kraken Funding 2FA 提现控制对照图"},"summary":{"en":"Coinbase Exchange whitelisting and Kraken Funding 2FA solve related but different withdrawal-control jobs.","zh-Hans":"Coinbase Exchange 允许名单与 Kraken Funding 2FA 提现控制对照图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Exchange says Address Book entries can include supported cryptocurrency, compatible network and nickname fields.","sourceIds":["coinbase-exchange-address-book"],"risk":"medium"},{"id":"c2","text":"Coinbase Exchange says whitelisting restricts crypto withdrawals to addresses already designated in the Address Book.","sourceIds":["coinbase-exchange-address-book","coinbase-exchange-whitelist-detail"],"risk":"medium"},{"id":"c3","text":"Coinbase Exchange says new Address Book entries require a 48-hour hold period after the initial window when whitelisting is active.","sourceIds":["coinbase-exchange-address-book","coinbase-exchange-whitelist-detail"],"risk":"medium"},{"id":"c4","text":"Kraken says Funding 2FA requires a code for withdrawals and transfers to the Futures wallet.","sourceIds":["kraken-funding-2fa"],"risk":"low"},{"id":"c5","text":"Kraken says withdrawal 2FA does not prevent adding cryptocurrency withdrawal addresses and points to Global Settings Lock for that protection.","sourceIds":["kraken-funding-2fa","kraken-address-confirmation"],"risk":"low"}],"relatedVenues":["kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-tokenization-service-same-cusip-approved-network-control-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-30T23:58:00.000Z","updatedAt":"2026-09-30T23:58:00.000Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Tokenization Service Same-CUSIP Approved-Network Control Map","zh-Hans":"DTCC Tokenization Service 同 CUSIP 与批准网络控制图"},"summary":{"en":"DTCC Tokenization Service should be read as market-infrastructure plumbing with explicit control assumptions, not as a generic claim that any tokenized security can circulate freely.","zh-Hans":"本文最有价值的地方是克制。DTCC Tokenization Service 应被理解为带有明确控制假设的市场基础设施，而不是“任何代币化证券都能自由流转”的笼统表述。"},"claims":[{"id":"c1","text":"DTCC says Tokenization Service is designed to bridge traditional and blockchain-based environments.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c2","text":"DTCC says tokenized DTC assets can move using the same CUSIP across approved networks.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c3","text":"DTCC says DTC-issued tokens are designed to represent the same legal rights, economic interest and investor protections associated with the underlying securities.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c4","text":"DTCC says DTC-issued tokens include mint, burn, pause and clawback controls and LedgerScan ownership tracking.","sourceIds":["dtcc-tokenization-service"],"risk":"low"},{"id":"c5","text":"SEC Crypto@SEC records crypto-related work including tokenized securities and transfer-agent modernization materials.","sourceIds":["sec-crypto","sec-tokenized-securities"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-gate-us-withdrawal-whitelist-fund-password-authenticator-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-30T23:58:00.000Z","updatedAt":"2026-09-30T23:58:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up Gate US Withdrawal Whitelist, Fund Password and Authenticator Safely","zh-Hans":"如何安全设置 Gate US 提现白名单、资金密码与验证器"},"summary":{"en":"A safe Gate US onboarding path should finish identity and security controls before any first meaningful withdrawal. Gate US registration guidance says users create an account with email or phone and confirm a 6-digit code.","zh-Hans":"本文最有价值的地方是克制。安全的 Gate US onboarding 路径应先完成身份与安全控制，再处理第一次有意义的提现。Gate US 注册指南说明，用户可用邮箱或手机号创建账户，并输入 6 位验证码完成注册。"},"claims":[{"id":"c1","text":"Gate US registration guidance says users can register with email or phone and confirm a 6-digit code.","sourceIds":["gate-register"],"risk":"medium"},{"id":"c2","text":"Gate US identity-verification guidance says KYC is required for trading services including deposit, withdrawal and transfer.","sourceIds":["gate-kyc"],"risk":"medium"},{"id":"c3","text":"Gate US fund-password guidance says the fund password must be different from the login password.","sourceIds":["gate-fund-password"],"risk":"medium"},{"id":"c4","text":"Gate US authenticator guidance says the authenticator is required for login, withdrawals, password changes and other security operations.","sourceIds":["gate-authenticator"],"risk":"low"},{"id":"c5","text":"Gate US withdrawal-whitelist guidance says verification-free addresses can skip later withdrawal verification and should only be addresses the user controls.","sourceIds":["gate-whitelist"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-crypto-asset-faq-interpretive-release-action-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-30T23:58:00.000Z","updatedAt":"2026-09-30T23:58:00.000Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Crypto-Asset FAQ and Interpretive Release Action Map","zh-Hans":"SEC 加密资产 FAQ 与解释性发布行动图"},"summary":{"en":"The SEC Crypto@SEC page turns late-September crypto guidance into a source-routing problem for product and venue articles.","zh-Hans":"SEC 加密资产 FAQ 与解释性发布行动图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"SEC Crypto@SEC lists a September 25, 2026 FAQ related to federal securities laws for certain crypto assets and transactions.","sourceIds":["sec-crypto","sec-faq-crypto-assets"],"risk":"medium"},{"id":"c2","text":"SEC Crypto@SEC ties that FAQ to the Commission's March 17, 2026 Interpretive Release.","sourceIds":["sec-crypto","sec-interpretive-release"],"risk":"medium"},{"id":"c3","text":"SEC Crypto@SEC lists September 17, 2026 temporary conditional exemptive relief for tokenized NMS stock trading venues.","sourceIds":["sec-crypto","sec-tokenized-nms-fact-sheet"],"risk":"medium"},{"id":"c4","text":"SEC Crypto@SEC lists a September 1, 2026 transfer-agent proposal addressing electronic and blockchain-based recordkeeping.","sourceIds":["sec-crypto"],"risk":"low"},{"id":"c5","text":"The SEC items are different source types and should not be collapsed into blanket approval claims.","sourceIds":["sec-crypto","sec-faq-crypto-assets","sec-tokenized-nms-fact-sheet"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-travel-rule-address-book-satoshi-test-checklist","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-30T21:07:00.000Z","updatedAt":"2026-09-30T21:07:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Travel Rule Address Book and Satoshi Test Checklist","zh-Hans":"Binance Travel Rule 地址簿与 Satoshi Test 核验清单"},"summary":{"en":"Binance's Travel Rule material turns crypto deposits and withdrawals into an information-quality workflow, not just a wallet-address workflow.","zh-Hans":"Binance Travel Rule 地址簿与 Satoshi Test 核验清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance says Travel Rule implementation can require users to provide originator or beneficiary information during crypto deposits and withdrawals.","sourceIds":["binance-travel-rule"],"risk":"medium"},{"id":"c2","text":"Binance says self-hosted wallet verification can involve a Satoshi Test, a small transfer used to prove address control.","sourceIds":["binance-satoshi-address-book"],"risk":"medium"},{"id":"c3","text":"Binance says Travel Rule address-book information can help pre-validate stored addresses for future transfers.","sourceIds":["binance-satoshi-address-book"],"risk":"medium"},{"id":"c4","text":"Binance's deposit and withdrawal support hub separates crypto deposit, crypto withdrawal and Travel Parameters guidance.","sourceIds":["binance-deposit-withdrawal-hub"],"risk":"low"},{"id":"c5","text":"Binance's Travel Rule procedure material describes pop-up information requests for sender or beneficiary details in affected transfer flows.","sourceIds":["binance-travel-rule-procedure","binance-travel-rule"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-status-page-incident-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-30T21:07:00.000Z","updatedAt":"2026-09-30T21:07:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange Status Page Incident Disclosure Radar","zh-Hans":"交易所状态页事故披露雷达"},"summary":{"en":"NexuAlpha Radar scores exchange status pages as operational disclosure tools, not as trust badges. OKX Status says it displays system maintenance information, issue descriptions and deposit/withdrawal status.","zh-Hans":"本文最有价值的地方是克制。NexuAlpha Radar 将交易所状态页评分为运营披露工具，而不是信任徽章。OKX Status 称其展示系统维护信息、问题描述以及充提状态。"},"claims":[{"id":"c1","text":"OKX Status describes itself as a hub for system information, maintenance information, issue descriptions and deposit/withdrawal status.","sourceIds":["okx-status"],"risk":"medium"},{"id":"c2","text":"Kraken Status is the public status page for Kraken Digital Asset Exchange and lists component status and incidents.","sourceIds":["kraken-status"],"risk":"medium"},{"id":"c3","text":"Kraken publishes API documentation for programmatic access to status page elements.","sourceIds":["kraken-status-api"],"risk":"medium"},{"id":"c4","text":"Coinbase publishes a consumer status page with incidents and component information.","sourceIds":["coinbase-status"],"risk":"low"},{"id":"c5","text":"Coinbase Exchange publishes a separate status page for Coinbase Exchange services.","sourceIds":["coinbase-exchange-status"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"franklin-benji-transfer-agent-official-record-boundary","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-30T21:07:00.000Z","updatedAt":"2026-09-30T21:07:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Franklin Benji Transfer Agent Official Record Boundary","zh-Hans":"Franklin Benji 转让代理官方记录边界"},"summary":{"en":"Franklin Templeton's Benji and Franklin OnChain U.S. Government Money Fund should be read through the official-record boundary.","zh-Hans":"Franklin Benji 转让代理官方记录边界：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Franklin's Benji page describes tokenizing a traditional money market fund for mutual fund record keeping.","sourceIds":["franklin-benji"],"risk":"medium"},{"id":"c2","text":"Franklin's Benji page says one share of FOBXX equals one BENJI token.","sourceIds":["franklin-benji"],"risk":"medium"},{"id":"c3","text":"Franklin prospectus material says the transfer agent maintains the official record of share ownership through a blockchain-integrated system.","sourceIds":["franklin-prospectus","sec-edgar-fobxx"],"risk":"medium"},{"id":"c4","text":"Franklin prospectus material connects book-entry recordkeeping features with one or more public blockchain networks.","sourceIds":["franklin-prospectus"],"risk":"low"},{"id":"c5","text":"SEC tokenized-securities material says tokenization requires analysis of the associated rights, obligations and benefits, not only the token format.","sourceIds":["sec-tokenized-securities"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-verify-binance-travel-rule-address-book-satoshi-test","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-30T21:07:00.000Z","updatedAt":"2026-09-30T21:07:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"How to Verify Binance Travel Rule Address Book and Satoshi Test Safely","zh-Hans":"如何安全核验 Binance Travel Rule 地址簿与 Satoshi Test"},"summary":{"en":"To verify Binance Travel Rule address-book and Satoshi Test requirements safely, treat the flow as recipient-information onboarding rather than a normal address paste.","zh-Hans":"如何安全核验 Binance Travel Rule 地址簿与 Satoshi Test：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance says Travel Rule transfer flows can require originator or beneficiary information.","sourceIds":["binance-travel-rule"],"risk":"medium"},{"id":"c2","text":"Binance says a Satoshi Test verifies control of a self-hosted wallet through a small cryptocurrency transfer.","sourceIds":["binance-satoshi-address-book"],"risk":"medium"},{"id":"c3","text":"Binance says Travel Rule address-book information can be stored to pre-validate future transfer details.","sourceIds":["binance-satoshi-address-book"],"risk":"medium"},{"id":"c4","text":"Binance's withdrawal FAQ hub includes crypto withdrawal and Travel Parameters guidance.","sourceIds":["binance-withdrawal-faq"],"risk":"low"},{"id":"c5","text":"Binance's Travel Rule procedure material says users can be asked for additional sender or beneficiary information during deposit and withdrawal transactions.","sourceIds":["binance-travel-rule-procedure"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-transfer-agent-blockchain-recordkeeping-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-30T21:07:00.000Z","updatedAt":"2026-09-30T21:07:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Transfer Agent Blockchain Recordkeeping Risk Map","zh-Hans":"SEC 转让代理区块链记录保存风险图"},"summary":{"en":"The SEC's 2026 transfer-agent proposal matters for tokenized securities because it focuses on the ownership-record machinery, not token price narratives.","zh-Hans":"SEC 转让代理区块链记录保存风险图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"The SEC transfer-agent proposal page says the Commission is proposing updates to registered transfer-agent rules and forms.","sourceIds":["sec-transfer-agent-rules"],"risk":"medium"},{"id":"c2","text":"The SEC proposal page says the updates reflect electronic recordkeeping and the services transfer agents provide to issuers, investors and intermediaries.","sourceIds":["sec-transfer-agent-rules"],"risk":"medium"},{"id":"c3","text":"SEC Crypto@SEC summarizes the proposal as addressing technological advancements including electronic and blockchain-based recordkeeping and uncertificated securities.","sourceIds":["sec-crypto"],"risk":"medium"},{"id":"c4","text":"The SEC proposed-rule PDF discusses blockchain or distributed-ledger records in the transfer-agent recordkeeping context.","sourceIds":["sec-transfer-agent-pdf"],"risk":"low"},{"id":"c5","text":"SEC tokenized-securities material separates token form from the analysis of rights, obligations and benefits associated with the security.","sourceIds":["sec-tokenized-securities"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-cushy-tokenized-credit-shareclass-risk-boundary-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-30T12:16:00.000Z","updatedAt":"2026-09-30T12:16:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase CUSHY Tokenized Credit Shareclass Risk Boundary Map","zh-Hans":"Coinbase CUSHY 代币化信用份额风险边界图"},"summary":{"en":"Coinbase Asset Management's CUSHY announcement is a tokenized-fund access and risk-boundary story, not a retail yield promise.","zh-Hans":"Coinbase CUSHY 代币化信用份额风险边界图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Asset Management says CUSHY is the Coinbase Stablecoin Credit Strategy, a digital credit strategy for qualified investors and institutions.","sourceIds":["coinbase-cushy"],"risk":"medium"},{"id":"c2","text":"Coinbase says CUSHY offers investors the option of tokenized shares with transparency and 24/7 onchain utility powered by Superstate FundOS.","sourceIds":["coinbase-cushy"],"risk":"medium"},{"id":"c3","text":"Superstate says FundOS is a platform to bring private funds, mutual funds and ETFs onchain through transfer-agent and tokenization infrastructure.","sourceIds":["superstate-fundos"],"risk":"medium"},{"id":"c4","text":"Superstate says FundOS manages shareholder registry across book-entry and supported blockchains and uses an allowlist compliance perimeter.","sourceIds":["superstate-fundos"],"risk":"low"},{"id":"c5","text":"SEC staff says tokenized securities vary in structure and rights, so the record and rights path must be analyzed rather than inferred from token format.","sourceIds":["sec-tokenized-securities"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-exchange-prime-onchain-address-book-governance-comparison","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-30T12:16:00.000Z","updatedAt":"2026-09-30T12:16:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Exchange vs Prime vs Onchain Address Book Governance","zh-Hans":"Coinbase Exchange、Prime 与 Onchain 地址簿治理对比"},"summary":{"en":"Coinbase publishes three different address-governance surfaces that should not be merged into one generic withdrawal-safety claim.","zh-Hans":"Coinbase Exchange、Prime 与 Onchain 地址簿治理对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase Exchange Help says whitelisting is a security feature that allows withdrawals only to addresses already designated in the Address Book.","sourceIds":["coinbase-exchange-whitelist"],"risk":"medium"},{"id":"c2","text":"Coinbase Exchange Help says users have an initial 8-hour window after enabling whitelisting and a 48-hour hold for new addresses after that window.","sourceIds":["coinbase-exchange-hold"],"risk":"medium"},{"id":"c3","text":"Coinbase Prime Help says Trusted Address Book Protection is automatically enabled for all portfolios and address-book updates are subject to consensus approvals.","sourceIds":["coinbase-prime-trusted"],"risk":"medium"},{"id":"c4","text":"Coinbase Prime Onchain Wallet Help says the Onchain Wallet has a dedicated address book separate from the Vault and Trading wallet address book.","sourceIds":["coinbase-prime-onchain"],"risk":"low"},{"id":"c5","text":"Coinbase Prime Onchain Wallet Help says Destination Protection is active by default and allows transfers only to approved addresses.","sourceIds":["coinbase-prime-onchain"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-stock-trading-tokenize-platform-market-structure-readiness","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-30T12:16:00.000Z","updatedAt":"2026-09-30T12:16:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Stock Trading and Tokenize Market-Structure Readiness","zh-Hans":"Coinbase 股票交易与 Tokenize 市场结构准备度"},"summary":{"en":"Coinbase's stock-trading and Tokenize materials should be read as market-structure expansion with product-specific boundaries, not as one unified tokenized-stock launch.","zh-Hans":"Coinbase 股票交易与 Tokenize 市场结构准备度：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase's system update says stock trading began rolling out to Coinbase users and Coinbase Tokenize is planned as an institutional platform for tokenizing real-world assets.","sourceIds":["coinbase-system-update"],"risk":"medium"},{"id":"c2","text":"Coinbase Help says stock and fund trading requires a Coinbase Capital Markets brokerage account and is available to U.S. customers for stocks and funds and U.K. customers for stocks.","sourceIds":["coinbase-stocks-onboarding"],"risk":"medium"},{"id":"c3","text":"Coinbase Help says all stock trades are settled with USD and USDC held in a Coinbase wallet can be automatically converted to USD before stock purchase payment, subject to limitations.","sourceIds":["coinbase-buy-sell-stocks"],"risk":"medium"},{"id":"c4","text":"Coinbase Help says stock trading can occur 24 hours per day, five days per week across pre-market, regular, after-market and overnight sessions, while not all stocks are available outside regular hours.","sourceIds":["coinbase-trading-hours"],"risk":"low"},{"id":"c5","text":"Coinbase's U.S. User Agreement says securities services are offered by Coinbase Capital Markets and are separate from digital asset services, with Apex Clearing providing execution, clearing and custody.","sourceIds":["coinbase-user-agreement"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-account-protection-reimbursement-vs-prevention-disclosure-radar","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-30T12:16:00.000Z","updatedAt":"2026-09-30T12:16:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Account Protection Radar: Reimbursement vs Prevention Disclosures","zh-Hans":"加密账户保护雷达：赔付与预防披露边界"},"summary":{"en":"NexuAlpha Radar separates reimbursement programs from prevention controls because the user decision is different.","zh-Hans":"加密账户保护雷达：赔付与预防披露边界：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase says Account Protection may reimburse eligible Coinbase One members in supported regions for unauthorized crypto withdrawals after account takeover.","sourceIds":["coinbase-account-protection"],"risk":"medium"},{"id":"c2","text":"Coinbase says Account Protection eligibility requires a passkey or security key and can be reduced or deactivated if weaker 2-step verification is enabled.","sourceIds":["coinbase-account-protection"],"risk":"medium"},{"id":"c3","text":"Coinbase says transactions authorized by the user because of deception are not covered by Account Protection.","sourceIds":["coinbase-account-protection"],"risk":"medium"},{"id":"c4","text":"Coinbase security guidance says allowlisting restricts withdrawals to address-book destinations and new addresses require a 48-hour hold period.","sourceIds":["coinbase-address-allowlist"],"risk":"low"},{"id":"c5","text":"Kraken says certain funding methods and account actions can trigger withdrawal holds for security purposes.","sourceIds":["kraken-withdrawal-hold"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-withdrawal-hold-deposit-method-security-action-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-30T12:16:00.000Z","updatedAt":"2026-09-30T12:16:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken Withdrawal Hold: Deposit Method and Security Action Checklist","zh-Hans":"Kraken 提现 Hold：入金方式与安全操作清单"},"summary":{"en":"Kraken's withdrawal-hold documentation separates funding-source holds from address-confirmation and account-security holds.","zh-Hans":"本文最有价值的地方是克制。Kraken 的提现 hold 文档把入金来源 hold、地址确认和账户安全 hold 分开处理。Kraken 表示，首次借记卡、信用卡或数字钱包购买可能触发 72 小时提现 hold，ACH Plaid 购买有 7 天 hold，且 hold 金额对应购买金额，不一定等于整个账户余额。"},"claims":[{"id":"c1","text":"Kraken says first-time debit-card, credit-card or digital-wallet purchases can trigger a 72-hour withdrawal hold.","sourceIds":["kraken-withdrawal-hold"],"risk":"medium"},{"id":"c2","text":"Kraken says ACH Plaid purchases have a seven-day withdrawal hold and the hold can apply to cash or cryptocurrency withdrawals equal to the purchased amount.","sourceIds":["kraken-withdrawal-hold"],"risk":"medium"},{"id":"c3","text":"Kraken says crypto withdrawals require adding and confirming a withdrawal address before use.","sourceIds":["kraken-withdraw-crypto"],"risk":"medium"},{"id":"c4","text":"Kraken says users must select the same network used by the recipient because withdrawing on the wrong network can result in loss of funds.","sourceIds":["kraken-withdraw-crypto"],"risk":"low"},{"id":"c5","text":"Kraken says certain password-change scenarios without Sign-in 2FA or Master Key can hold withdrawals to new addresses for 24 hours.","sourceIds":["kraken-add-address"],"risk":"low"}],"relatedVenues":["kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-cancelreplace-vs-okx-order-state-finality-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-30T09:08:00.000Z","updatedAt":"2026-09-30T09:08:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Binance cancelReplace vs OKX Order State Finality Controls","zh-Hans":"Binance cancelReplace 与 OKX 订单状态最终性控制对比"},"summary":{"en":"Binance and OKX expose different control questions for API order repair. Binance’s Spot API upgrade says orderRateLimitExceededMode allows cancelReplace to cancel orders when the order rate limit is exceeded, but does not allow.","zh-Hans":"Binance cancelReplace 与 OKX 订单状态最终性控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance says orderRateLimitExceededMode applies when the order rate limit is exceeded.","sourceIds":["binance-cancelreplace"],"risk":"medium"},{"id":"c2","text":"Binance says orderRateLimitExceededMode allows cancelReplace to cancel orders but does not allow placing new orders.","sourceIds":["binance-cancelreplace"],"risk":"medium"},{"id":"c3","text":"Binance lists REST POST /api/v3/order/cancelReplace and WebSocket order.cancelReplace as affected endpoints.","sourceIds":["binance-cancelreplace"],"risk":"medium"},{"id":"c4","text":"OKX says failed affected post-only placement now pushes only state canceled, without state live first.","sourceIds":["okx-websocket-orders"],"risk":"low"},{"id":"c5","text":"OKX says regular limit, market, ioc and fok order types remain unchanged by the push-behavior adjustment.","sourceIds":["okx-websocket-orders"],"risk":"low"}],"relatedVenues":["binance","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-tokenized-dtc-assets-rights-controls-readiness-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-30T09:08:00.000Z","updatedAt":"2026-09-30T09:08:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Tokenized DTC Assets Rights and Controls Readiness Map","zh-Hans":"DTCC 代币化 DTC 资产权利与控制准备度地图"},"summary":{"en":"DTCC presents tokenized DTC assets as market-infrastructure workflow, not as a generic retail token claim.","zh-Hans":"DTCC 代币化 DTC 资产权利与控制准备度地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"DTCC says tokenized DTC assets can move between traditional and blockchain ecosystems using the same CUSIP across approved networks.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c2","text":"DTCC says DTC-issued tokens are designed to represent the same legal rights, economic interest and investor protections associated with the underlying securities.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c3","text":"DTCC says DTC-issued tokens include mint, burn, pause and clawback functionality, and ComposerX LedgerScan provides near real-time ownership tracking.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c4","text":"DTCC says live production trades included cross-chain transfers, collateral pledges, equity conversions and DVP transactions involving U.S. Treasury and equity assets.","sourceIds":["dtcc-live-production-trades"],"risk":"low"},{"id":"c5","text":"DTCC says about 40 firms participated in live production transactions utilizing tokenized DTC-custodied assets, paving the way for an expected October 2026 launch.","sourceIds":["dtcc-live-production-trades"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-order-acknowledgement-final-state-disclosure-radar","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-30T09:08:00.000Z","updatedAt":"2026-09-30T09:08:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange Order Acknowledgement vs Final State Disclosure Radar","zh-Hans":"交易所订单确认与最终状态披露雷达"},"summary":{"en":"NexuAlpha Radar treats order acknowledgement and final state as separate disclosure fields because API users can otherwise double-count exposure or retry into stale state.","zh-Hans":"本文最有价值的地方是克制。NexuAlpha Radar 把订单确认与最终状态拆成两个披露字段，因为 API 用户如果混淆二者，可能重复计算敞口或在旧状态上重试。"},"claims":[{"id":"c1","text":"OKX says failed affected post-only and RPI placement scenarios can emit only state canceled.","sourceIds":["okx-websocket-orders"],"risk":"medium"},{"id":"c2","text":"OKX says successful affected post-only state live is delayed until the order has successfully entered the order book.","sourceIds":["okx-websocket-orders"],"risk":"medium"},{"id":"c3","text":"OKX documentation says users should refer to order WebSocket updates for amendment and cancellation confirmation.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c4","text":"Binance says orderRateLimitExceededMode allows cancelReplace to cancel orders but not place new orders when order rate limits are exceeded.","sourceIds":["binance-cancelreplace"],"risk":"low"},{"id":"c5","text":"NexuAlpha Radar classifies acknowledgement and final state as separate operational fields for source-mapped API content.","sourceIds":["okx-websocket-orders","binance-cancelreplace"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-enable-robinhood-crypto-transfers-allowlisting-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-30T09:08:00.000Z","updatedAt":"2026-09-30T09:08:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"How to Enable Robinhood Crypto Transfers and Allowlisting Safely","zh-Hans":"如何安全启用 Robinhood 加密转账与地址白名单"},"summary":{"en":"Robinhood crypto transfer onboarding should be treated as an identity, network and withdrawal-control workflow, not merely a send button.","zh-Hans":"本文最有价值的地方是克制。Robinhood 加密转账开通应被视为身份、网络和提现控制工作流，而不是简单的发送按钮。Robinhood 表示，启用 crypto transfers 需要先验证“确实是你”，审核可能最长需要 5 个工作日；它还说明加密转账一旦发送就是最终的，不能取消或撤回。"},"claims":[{"id":"c1","text":"Robinhood says enabling crypto transfers first requires verifying it is you, and review may take up to five business days.","sourceIds":["robinhood-crypto-wallets"],"risk":"medium"},{"id":"c2","text":"Robinhood says crypto transfers are final and cannot be canceled or reversed once sent.","sourceIds":["robinhood-crypto-wallets"],"risk":"medium"},{"id":"c3","text":"Robinhood says address allowlisting restricts withdrawals to approved wallet addresses and applies to all withdrawals unless disabled.","sourceIds":["robinhood-crypto-transfers"],"risk":"medium"},{"id":"c4","text":"Robinhood says allowlisting adds a 48-hour maturation period before new addresses or configuration changes take effect.","sourceIds":["robinhood-crypto-transfers"],"risk":"low"},{"id":"c5","text":"Robinhood says block explorers can be used to inspect transaction hash, confirmations, recipients and sender details.","sourceIds":["robinhood-crypto-transfers"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-websocket-orders-state-live-finality-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-30T09:08:00.000Z","updatedAt":"2026-09-30T09:08:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"OKX WebSocket Orders State Live Finality Checklist","zh-Hans":"OKX WebSocket 订单 state live 最终性清单"},"summary":{"en":"OKX changed the practical meaning of a WebSocket order-state signal for post-only and RPI workflows. Its July 16, 2026 announcement says the “state: live” event for affected orders is pushed only after the order has successfully.","zh-Hans":"OKX WebSocket 订单 state live 最终性清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"OKX published a WebSocket orders channel push behavior adjustment on July 16, 2026.","sourceIds":["okx-websocket-orders"],"risk":"medium"},{"id":"c2","text":"OKX says affected post-only and RPI order types move “state: live” to after successful book entry, with about a one millisecond delay.","sourceIds":["okx-websocket-orders"],"risk":"medium"},{"id":"c3","text":"OKX says failed post-only order placement caused by crossing the BBO now produces only “state: canceled” rather than “state: live” followed by “state: canceled.”","sourceIds":["okx-websocket-orders"],"risk":"medium"},{"id":"c4","text":"OKX says the affected order types are post_only, mmp_and_post_only and rpi, while regular limit, market, ioc and fok behavior remains unchanged.","sourceIds":["okx-websocket-orders"],"risk":"low"},{"id":"c5","text":"OKX API documentation says successful request responses can mean acceptance, while users should refer to order WebSocket updates for amendment or cancellation confirmation.","sourceIds":["okx-api-guide"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"api-failover-cancel-control-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-28T18:06:00.000Z","updatedAt":"2026-09-28T18:06:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"API Failover and Cancel-Control Disclosure Radar","zh-Hans":"API 故障切换与撤单控制披露雷达"},"summary":{"en":"NexuAlpha Radar treats API failover as a disclosure problem with five fields: trigger, cancel scope, reconnect behavior, machine-readable state and secret boundary.","zh-Hans":"API 故障切换与撤单控制披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance said WebSocket connections may be disconnected during the 2026 Spot API infrastructure update window and users should reconnect.","sourceIds":["binance-spot-api-update-20260625"],"risk":"medium"},{"id":"c2","text":"Binance REST Spot API documents cancelReplace for canceling an existing order and placing a new order on the same symbol.","sourceIds":["binance-rest-trade-docs"],"risk":"medium"},{"id":"c3","text":"Binance REST Spot API documents orderRateLimitExceededMode behavior for cancelReplace.","sourceIds":["binance-rest-trade-docs"],"risk":"medium"},{"id":"c4","text":"Binance WebSocket Spot API documents order.cancelReplace.","sourceIds":["binance-ws-trade-docs"],"risk":"low"},{"id":"c5","text":"Kraken Futures documents a dead man switch that cancels all user orders when the timeout expires.","sourceIds":["kraken-dead-man-switch"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-spot-api-websocket-reconnect-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-28T18:06:00.000Z","updatedAt":"2026-09-28T18:06:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Spot API WebSocket Reconnect and CancelReplace Checklist","zh-Hans":"Binance Spot API WebSocket 重连与 CancelReplace 清单"},"summary":{"en":"Binance published a Spot API update notice on June 25, 2026 for an infrastructure upgrade scheduled for July 9, 2026 at 07:00 UTC with an expected one-hour duration.","zh-Hans":"Binance Spot API WebSocket 重连与 CancelReplace 清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance published the Spot API update notice on 2026-06-25 and updated it the same day.","sourceIds":["binance-spot-api-update-20260625"],"risk":"medium"},{"id":"c2","text":"Binance said the Spot API infrastructure upgrade was scheduled for 2026-07-09 07:00 UTC with an expected duration of about one hour.","sourceIds":["binance-spot-api-update-20260625"],"risk":"medium"},{"id":"c3","text":"Binance said WebSocket connections may be disconnected during the update window and users should reconnect to restore the connection.","sourceIds":["binance-spot-api-update-20260625"],"risk":"medium"},{"id":"c4","text":"Binance REST Spot API documents cancelReplace as a signed endpoint.","sourceIds":["binance-rest-trade-docs"],"risk":"low"},{"id":"c5","text":"Binance WebSocket Spot API documents the order.cancelReplace method.","sourceIds":["binance-ws-trade-docs"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-kraken-order-failover-cancel-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-28T18:06:00.000Z","updatedAt":"2026-09-28T18:06:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs Kraken Order Failover and Cancel-Control Checklist","zh-Hans":"Binance 与 Kraken 订单故障保护和撤单控制清单"},"summary":{"en":"Binance and Kraken expose different order-failover controls, so the comparison should start with the failure mode rather than the brand.","zh-Hans":"Binance 与 Kraken 订单故障保护和撤单控制清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance REST Spot API documents cancelReplace as canceling an existing order and placing a new order on the same symbol.","sourceIds":["binance-rest-trade-docs"],"risk":"medium"},{"id":"c2","text":"Binance REST Spot API says filters and order count are evaluated before cancellation and order placement are processed.","sourceIds":["binance-rest-trade-docs"],"risk":"medium"},{"id":"c3","text":"Binance documents orderRateLimitExceededMode values DO_NOTHING and CANCEL_ONLY for cancelReplace behavior.","sourceIds":["binance-rest-trade-docs"],"risk":"medium"},{"id":"c4","text":"Binance announced a 2026-07-09 Spot API infrastructure upgrade during which WebSocket connections may disconnect and should be reconnected.","sourceIds":["binance-spot-api-update-20260625"],"risk":"low"},{"id":"c5","text":"Kraken Futures documents a dead man switch endpoint that cancels all user orders when the configured timeout expires unless refreshed or deactivated.","sourceIds":["kraken-dead-man-switch"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cftc-crypto-blockchain-faq-tokenized-customer-funds-recordkeeping","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-28T18:06:00.000Z","updatedAt":"2026-09-28T18:06:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC Crypto and Blockchain FAQ Update: Tokenized Customer Funds and Recordkeeping","zh-Hans":"CFTC 加密与区块链 FAQ 更新：代币化客户资金与记录保存"},"summary":{"en":"The CFTC September 24, 2026 FAQ update is decision-relevant because it keeps tokenized collateral and blockchain recordkeeping inside regulated-market operating questions.","zh-Hans":"CFTC 加密与区块链 FAQ 更新：代币化客户资金与记录保存：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"CFTC published Release 9303-26 on 2026-09-24.","sourceIds":["cftc-faq-updates-9303-26"],"risk":"medium"},{"id":"c2","text":"CFTC said staff updated FAQs concerning registrant and registered entity activities relating to crypto assets and blockchain technologies.","sourceIds":["cftc-faq-updates-9303-26"],"risk":"medium"},{"id":"c3","text":"CFTC said the update addressed investments of customer funds in tokenized forms of permitted investments.","sourceIds":["cftc-faq-updates-9303-26"],"risk":"medium"},{"id":"c4","text":"CFTC said the update addressed the use of blockchain technologies to satisfy a registrant’s recordkeeping requirements.","sourceIds":["cftc-faq-updates-9303-26"],"risk":"low"},{"id":"c5","text":"CFTC said the FAQs were originally released on 2026-03-20 and addressed topics connected to staff letters 25-39 and 26-05.","sourceIds":["cftc-faq-updates-9303-26"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-tokenization-interoperability-collateral-appchain-readiness","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-28T18:06:00.000Z","updatedAt":"2026-09-28T18:06:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Tokenization Interoperability and Collateral AppChain Readiness Map","zh-Hans":"DTCC 代币化互操作性与 Collateral AppChain 准备度地图"},"summary":{"en":"DTCC frames institutional tokenization readiness as an interoperability and collateral-mobility problem rather than a simple token launch.","zh-Hans":"DTCC 代币化互操作性与 Collateral AppChain 准备度地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"DTCC Insights described tokenization as moving from experimentation to implementation and emphasized interoperability across assets, cash and data.","sourceIds":["dtcc-interoperability-insight"],"risk":"medium"},{"id":"c2","text":"DTCC Collateral AppChain says it supports 24/7 collateral operations.","sourceIds":["dtcc-collateral-appchain"],"risk":"medium"},{"id":"c3","text":"DTCC Collateral AppChain says it supports collateral movement across counterparties, jurisdictions and networks.","sourceIds":["dtcc-collateral-appchain"],"risk":"medium"},{"id":"c4","text":"DTCC live production trades included cross-chain transfers, collateral pledges, equity conversions and DVP transactions involving U.S. Treasury and equity assets.","sourceIds":["dtcc-live-production-trades"],"risk":"low"},{"id":"c5","text":"DTCC said the live production transactions paved the way for the expected October 2026 Tokenization Service launch.","sourceIds":["dtcc-live-production-trades"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bitget-vs-kucoin-anti-phishing-withdrawal-safety-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-28T12:08:00.000Z","updatedAt":"2026-09-28T12:08:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Bitget vs KuCoin Anti-Phishing and Withdrawal Safety Controls","zh-Hans":"Bitget 与 KuCoin 反钓鱼和提现安全控制对比"},"summary":{"en":"Bitget and KuCoin both publish account-safety controls, but they frame different operational jobs.","zh-Hans":"Bitget 与 KuCoin 反钓鱼和提现安全控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bitget says Google Authenticator is required when setting up a passkey.","sourceIds":["bitget-security-best-practices"],"risk":"medium"},{"id":"c2","text":"Bitget says anti-phishing code helps users identify official emails and SMS messages.","sourceIds":["bitget-security-best-practices"],"risk":"medium"},{"id":"c3","text":"Bitget says cross-device withdrawal verification requires mobile confirmation before a website withdrawal request is approved.","sourceIds":["bitget-security-best-practices"],"risk":"medium"},{"id":"c4","text":"KuCoin says users should set an anti-phishing safety phrase for email, login and withdrawal code.","sourceIds":["kucoin-security-notice"],"risk":"low"},{"id":"c5","text":"KuCoin says withdrawals are temporarily suspended for 24 hours after security changes such as deleting passkey, resetting Google 2FA or changing login password.","sourceIds":["kucoin-withdrawal-restrictions"],"risk":"low"}],"relatedVenues":["bitget","kucoin"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-live-production-trades-tokenized-dtc-assets-readiness","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-28T12:08:00.000Z","updatedAt":"2026-09-28T12:08:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Live Production Trades and Tokenized DTC Asset Readiness","zh-Hans":"DTCC 生产环境交易与 DTC 代币化资产准备度"},"summary":{"en":"DTCC live production trades are useful evidence of market-infrastructure workflow, not a blanket signal that every tokenized security is ready for retail use.","zh-Hans":"DTCC 生产环境交易与 DTC 代币化资产准备度：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"DTCC says July 15 live production trades demonstrated tokenized assets in live market activity.","sourceIds":["dtcc-live-trades"],"risk":"medium"},{"id":"c2","text":"DTCC says J.P. Morgan converted the Invesco QQQ Trust ETF into a tokenized real-world asset during the event.","sourceIds":["dtcc-live-trades"],"risk":"medium"},{"id":"c3","text":"DTCC says the event included U.S. Treasury and equity conversions, U.S. Treasury DVP, collateral pledges and equity DVP trades.","sourceIds":["dtcc-live-trades"],"risk":"medium"},{"id":"c4","text":"DTCC says tokenized DTC assets can move between traditional and blockchain ecosystems using the same CUSIP across approved networks.","sourceIds":["dtcc-tokenization-service"],"risk":"low"},{"id":"c5","text":"DTCC says DTC-issued tokens include controls such as mint, burn, pause and clawback and LedgerScan ownership tracking.","sourceIds":["dtcc-tokenization-service"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-official-channel-verification-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-28T12:08:00.000Z","updatedAt":"2026-09-28T12:08:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange Official Channel Verification Disclosure Radar","zh-Hans":"交易所官方渠道验证披露雷达"},"summary":{"en":"NexuAlpha Radar treats official-channel verification as a first-class risk field because users often lose funds before they reach a trading decision.","zh-Hans":"交易所官方渠道验证披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"KuCoin Official Verification Center says users can verify official wallet addresses, emails, Telegram IDs, X accounts, official websites and more.","sourceIds":["kucoin-official-verification"],"risk":"medium"},{"id":"c2","text":"KuCoin Security Notice says users should set an anti-phishing safety phrase and not proceed if the code is missing or incorrect.","sourceIds":["kucoin-security-notice"],"risk":"medium"},{"id":"c3","text":"KuCoin Security Notice says users should check the official website, URL, certificate and sender address when avoiding phishing sites.","sourceIds":["kucoin-security-notice"],"risk":"medium"},{"id":"c4","text":"Bitget says official emails and SMS messages, excluding SMS verification codes, will include the anti-phishing code after it is enabled.","sourceIds":["bitget-security-best-practices"],"risk":"low"},{"id":"c5","text":"Bitget says cross-device withdrawal verification requires mobile confirmation before a website withdrawal request is approved.","sourceIds":["bitget-security-best-practices"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kucoin-withdrawal-restriction-security-change-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-28T12:08:00.000Z","updatedAt":"2026-09-28T12:08:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"KuCoin Withdrawal Restriction and Security Change Checklist","zh-Hans":"KuCoin 提现限制与安全变更清单"},"summary":{"en":"KuCoin withdrawal restrictions should be read as a security-state checklist, not automatically as a liquidity or platform outage signal.","zh-Hans":"本文最有价值的地方是克制。KuCoin 提现限制应被视为安全状态清单，而不应自动解释为流动性问题或平台故障。"},"claims":[{"id":"c1","text":"KuCoin says withdrawals may be temporarily suspended when an account is at risk.","sourceIds":["kucoin-withdrawal-restrictions"],"risk":"medium"},{"id":"c2","text":"KuCoin says deleting passkey can trigger a 24-hour withdrawal suspension.","sourceIds":["kucoin-withdrawal-restrictions"],"risk":"medium"},{"id":"c3","text":"KuCoin says changing, unlinking or resetting Google 2FA can trigger a 24-hour withdrawal suspension.","sourceIds":["kucoin-withdrawal-restrictions"],"risk":"medium"},{"id":"c4","text":"KuCoin says changing or unlinking phone or email can trigger a 24-hour withdrawal suspension.","sourceIds":["kucoin-withdrawal-restrictions"],"risk":"low"},{"id":"c5","text":"KuCoin says users should check the remaining unlock time on the withdrawal page and ensure funds are in the Funding Account with no open orders in spot, margin, futures or lending.","sourceIds":["kucoin-withdrawal-restrictions"],"risk":"low"}],"relatedVenues":["kucoin"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-24-hour-trading-operational-readiness-crypto-market-lessons","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-28T12:08:00.000Z","updatedAt":"2026-09-28T12:08:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"SEC 24-Hour Trading Readiness and Crypto Market Lessons","zh-Hans":"SEC 24 小时交易准备与加密市场经验清单"},"summary":{"en":"The SEC roundtable makes 24-hour trading a readiness problem rather than a simple access upgrade.","zh-Hans":"本文最有价值的地方是克制。SEC 圆桌把 24 小时交易定义为准备度问题，而不是简单的开放时段升级。SEC 议程说明，讨论范围包括 overnight trading 的准备、24 小时市场的运营与韧性，以及扩展机会和挑战。"},"claims":[{"id":"c1","text":"SEC hosted a September 17, 2026 roundtable on preparations for 24-hour trading in U.S. equity markets.","sourceIds":["sec-roundtable-agenda"],"risk":"medium"},{"id":"c2","text":"The SEC agenda says the roundtable covers preparations for overnight trading, operations and resiliency, and opportunities and challenges for expansion.","sourceIds":["sec-roundtable-agenda"],"risk":"medium"},{"id":"c3","text":"The preparedness panel covers exchange and broker-dealer readiness, overnight surveillance, closing-price processes, clearance and settlement changes and investor protection practices.","sourceIds":["sec-roundtable-agenda"],"risk":"medium"},{"id":"c4","text":"The resiliency panel covers systems readiness, Regulation SCI considerations, failover, capacity planning, market-data continuity, shorter maintenance windows, cybersecurity and staffing models.","sourceIds":["sec-roundtable-agenda"],"risk":"low"},{"id":"c5","text":"Jamie Selway said DTCC began clearing equities on a 23-by-5 basis in June and market data infrastructure was set to expand to 23-by-5 on December 6.","sourceIds":["sec-selway-remarks"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-bank-triparty-usd-tbill-collateral-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-28T09:10:00.000Z","updatedAt":"2026-09-28T09:10:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit Bank Triparty USD and T-BILL Collateral Risk Map","zh-Hans":"Bybit Bank Triparty 美元与 T-BILL 抵押风险地图"},"summary":{"en":"Bybit Bank Triparty turns collateral review into a bank-custody, haircut and transfer-restriction question.","zh-Hans":"Bybit Bank Triparty 美元与 T-BILL 抵押风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit says Bank Triparty safeguards USD and T-BILL collateral through regulated banking partners while enabling USDT financing on Bybit.","sourceIds":["bybit-bank-triparty"],"risk":"medium"},{"id":"c2","text":"Bybit defines Bank Triparty risk-ratio LTV as outstanding principal divided by haircut-adjusted bank collateral value.","sourceIds":["bybit-bank-triparty"],"risk":"medium"},{"id":"c3","text":"Bybit says transfer restrictions can apply when the transfer ratio is below 15 percent.","sourceIds":["bybit-bank-triparty"],"risk":"medium"},{"id":"c4","text":"Bybit lists initial, margin-call and liquidation LTV thresholds for Bank Triparty.","sourceIds":["bybit-bank-triparty"],"risk":"low"},{"id":"c5","text":"Bybit says liquidation can involve available UTA assets first and then bank-collateral settlement if risk remains above the liquidation threshold.","sourceIds":["bybit-bank-triparty"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-vs-okx-platform-collateral-borrowing-limit-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-28T09:10:00.000Z","updatedAt":"2026-09-28T09:10:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit vs OKX Platform Collateral and Borrowing Limit Controls","zh-Hans":"Bybit 与 OKX 平台级抵押和借贷限制控制对比"},"summary":{"en":"Bybit and OKX both describe platform-level collateral or borrowing limits, but the useful comparison is how each tells the user what changes when a limit is near or reached.","zh-Hans":"Bybit 与 OKX 平台级抵押和借贷限制控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit says its platform collateral limit applies across UTA cross margin, portfolio margin, Crypto Loans and Institutional Loans for new collateral usage.","sourceIds":["bybit-platform-collateral"],"risk":"medium"},{"id":"c2","text":"Bybit says warning icons can show when platform collateral usage is approaching the limit or has reached 100 percent.","sourceIds":["bybit-platform-collateral"],"risk":"medium"},{"id":"c3","text":"Bybit says API users may check supported-asset platform collateral usage through wallet-balance or crypto-loan position endpoints.","sourceIds":["bybit-platform-collateral"],"risk":"medium"},{"id":"c4","text":"OKX says its platform-wide collateralized borrowing limit considers liquidity, trading depth, total platform volume and borrowing volume.","sourceIds":["okx-platform-limit"],"risk":"low"},{"id":"c5","text":"OKX says impact from the platform limit depends on account mode and whether borrowing is active.","sourceIds":["okx-platform-limit"],"risk":"low"}],"relatedVenues":["bybit","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-collateral-alert-liquidation-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-28T09:10:00.000Z","updatedAt":"2026-09-28T09:10:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Collateral Alert and Liquidation Disclosure Radar","zh-Hans":"加密抵押警示与清算披露雷达"},"summary":{"en":"NexuAlpha's collateral radar treats alert delivery, platform caps and liquidation formulas as separate evidence fields.","zh-Hans":"加密抵押警示与清算披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bybit says yellow and red indicators can show when platform collateral usage approaches or reaches the limit.","sourceIds":["bybit-platform-collateral"],"risk":"medium"},{"id":"c2","text":"Bybit says users should not rely solely on system notifications for platform collateral risk.","sourceIds":["bybit-platform-collateral"],"risk":"medium"},{"id":"c3","text":"Bybit Crypto Loans FAQ says margin-call and liquidation thresholds can trigger email, SMS and push alerts.","sourceIds":["bybit-crypto-loans-faq"],"risk":"medium"},{"id":"c4","text":"Bybit Crypto Loans FAQ says risk alerts may be delayed or experience glitches.","sourceIds":["bybit-crypto-loans-faq"],"risk":"low"},{"id":"c5","text":"OKX says platform-limit impact depends on account mode and whether borrowing is active.","sourceIds":["okx-platform-limit"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-htx-account-security-and-withdraw-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-28T09:10:00.000Z","updatedAt":"2026-09-28T09:10:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up HTX Account Security and Withdraw Safely","zh-Hans":"如何设置 HTX 账户安全并安全提现"},"summary":{"en":"A safe HTX onboarding flow should separate account creation, 2FA setup, identity review and withdrawal review instead of treating registration as a bonus claim.","zh-Hans":"本文最有价值的地方是克制。安全的 HTX 开户流程应把账户创建、2FA 设置、身份审核和提现审核拆开，而不是把“注册”写成奖励承诺。HTX 的账户创建指南说明，用户可用邮箱或手机号注册，完成反机器人验证并输入验证码。"},"claims":[{"id":"c1","text":"HTX support says users can create an account with email or phone and complete anti-bot and verification-code steps.","sourceIds":["htx-create-account-es"],"risk":"medium"},{"id":"c2","text":"HTX Square says phone, email and Google Authenticator are account security items and recommends binding all three.","sourceIds":["htx-security-items"],"risk":"medium"},{"id":"c3","text":"HTX KYC guidance says identity review for USD balance deposit and withdrawal normally takes minutes but can take up to seven days in some cases.","sourceIds":["htx-kyc-usd"],"risk":"medium"},{"id":"c4","text":"HTX withdrawal guidance says withdrawal to a new address can trigger identity verification and failed verification can move to manual review.","sourceIds":["htx-withdraw-app"],"risk":"low"},{"id":"c5","text":"HTX withdrawal guidance tells users not to disclose passwords, SMS codes or Google verification codes to anyone.","sourceIds":["htx-withdraw-app"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-platform-collateralized-borrowing-limit-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-28T09:10:00.000Z","updatedAt":"2026-09-28T09:10:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"OKX Platform Collateralized Borrowing Limit Checklist","zh-Hans":"OKX 平台级抵押借贷限制清单"},"summary":{"en":"OKX's platform collateralized borrowing limit is a risk-control checklist, not a signal that a user personally hit a balance limit.","zh-Hans":"OKX 平台级抵押借贷限制清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"OKX says the platform collateralized borrowing limit is platform-wide for each collateral cryptocurrency.","sourceIds":["okx-platform-limit"],"risk":"medium"},{"id":"c2","text":"OKX says the limit considers liquidity, trading depth, total platform volume and borrowing volume.","sourceIds":["okx-platform-limit"],"risk":"medium"},{"id":"c3","text":"OKX says impact depends on account mode and whether borrowing is active.","sourceIds":["okx-platform-limit"],"risk":"medium"},{"id":"c4","text":"OKX says margin-trading maximum borrowing is constrained by user-level borrowing limit, tiered position limit and flexible Simple Earn pool limit.","sourceIds":["okx-margin-intro"],"risk":"low"},{"id":"c5","text":"OKX provides an account balance API endpoint that can be used as part of a read-only check.","sourceIds":["okx-api-balance"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-uah-fiat-trade-delisting-balance-conversion-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-28T06:12:00.000Z","updatedAt":"2026-09-28T06:12:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Binance UAH Fiat Trade Closure, USDT/UAH Delisting and Balance Conversion Checklist","zh-Hans":"Binance UAH 法币通道关闭、USDT/UAH 下架与余额转换清单"},"summary":{"en":"Binance's UAH notice is a deadline-management problem for fiat balances and open orders. Binance's verified announcement says UAH deposits and withdrawals through Fiat Trade UAH will no longer be supported after September 28,.","zh-Hans":"Binance UAH 法币通道关闭、USDT/UAH 下架与余额转换清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance says UAH deposits and withdrawals via Fiat Trade UAH will no longer be supported after 2026-09-28 09:00 UTC+2.","sourceIds":["binance-uah-square"],"risk":"medium"},{"id":"c2","text":"Binance says the USDT/UAH spot trading pair will be delisted at 2026-09-28 09:00 UTC+2.","sourceIds":["binance-uah-square"],"risk":"medium"},{"id":"c3","text":"Binance says all open orders on the USDT/UAH spot pair will be automatically removed after trading ceases.","sourceIds":["binance-uah-square"],"risk":"medium"},{"id":"c4","text":"Binance says remaining eligible UAH balances will be converted to USDT by 2026-09-30 18:00 UTC+2 at 1 USDT = 46.5 UAH.","sourceIds":["binance-uah-square"],"risk":"low"},{"id":"c5","text":"Binance says no action is required from users who want their remaining eligible UAH balance converted automatically.","sourceIds":["binance-uah-square"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-vs-gemini-passkey-withdrawal-address-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-28T06:12:00.000Z","updatedAt":"2026-09-28T06:12:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase vs Gemini Passkey and Withdrawal Address Controls","zh-Hans":"Coinbase vs Gemini Passkey 与提现地址控制对比"},"summary":{"en":"Coinbase and Gemini both push users toward stronger authentication and destination controls, but they package the risk differently.","zh-Hans":"Coinbase vs Gemini Passkey 与提现地址控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase says 2-step verification is required to access an account and recommends setting up multiple 2FA methods.","sourceIds":["coinbase-2fa"],"risk":"medium"},{"id":"c2","text":"Coinbase says address-book allowlisting limits sends to addresses in the address book and a newly added address becomes available for sends after 48 hours.","sourceIds":["coinbase-allowlist"],"risk":"medium"},{"id":"c3","text":"Coinbase Exchange says API users can add or delete addresses and withdraw using whitelisted addresses, but cannot enable or disable whitelisting through the API.","sourceIds":["coinbase-exchange-whitelist"],"risk":"medium"},{"id":"c4","text":"Gemini says 2FA is required and cannot be disabled.","sourceIds":["gemini-2fa"],"risk":"low"},{"id":"c5","text":"Gemini says passkeys become the default 2FA method after opt-in, and approved-address flows can require a 7-day hold or multi-user approval.","sourceIds":["gemini-passkeys","gemini-approved-address","gemini-withdrawal-protection"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-bitstamp-2fa-and-withdrawal-whitelist-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-28T06:12:00.000Z","updatedAt":"2026-09-28T06:12:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up Bitstamp 2FA and Withdrawal Whitelisting Safely","zh-Hans":"如何安全设置 Bitstamp 2FA 与提现白名单"},"summary":{"en":"A safe Bitstamp security setup starts with authentication, then narrows withdrawal destinations, and only then considers API or Travel Rule edge cases.","zh-Hans":"如何安全设置 Bitstamp 2FA 与提现白名单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Bitstamp says users should protect both the account and registered email address with 2FA.","sourceIds":["bitstamp-security-guide"],"risk":"medium"},{"id":"c2","text":"Bitstamp says security codes are required when confirming crypto withdrawals.","sourceIds":["bitstamp-security-guide"],"risk":"medium"},{"id":"c3","text":"Bitstamp says whitelisting lets users specify trusted addresses and limits withdrawals to those addresses.","sourceIds":["bitstamp-security-guide"],"risk":"medium"},{"id":"c4","text":"Bitstamp says withdrawal address whitelisting requires a crypto withdrawal address to be added to the whitelist before withdrawal.","sourceIds":["bitstamp-whitelist-product"],"risk":"low"},{"id":"c5","text":"Bitstamp's API documentation says crypto withdrawals subject to Travel Rule may require address verification and can return an address-not-verified error.","sourceIds":["bitstamp-api"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"robinhood-stock-tokens-debt-security-rights-boundary-map","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-28T06:12:00.000Z","updatedAt":"2026-09-28T06:12:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Robinhood Stock Tokens Debt-Security Rights Boundary Map","zh-Hans":"Robinhood Stock Tokens 债务证券与股东权利边界地图"},"summary":{"en":"Robinhood's 2026 filing makes its stock-token boundary an issuer-rights question, not only an onchain trading question.","zh-Hans":"Robinhood Stock Tokens 债务证券与股东权利边界地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Robinhood says Stock Tokens launched in July 2026.","sourceIds":["robinhood-10q-2026-q2"],"risk":"medium"},{"id":"c2","text":"Robinhood says Stock Tokens are tokenized debt securities issued by Robinhood Assets (Jersey) Limited.","sourceIds":["robinhood-10q-2026-q2"],"risk":"medium"},{"id":"c3","text":"Robinhood says Stock Tokens provide economic exposure to underlying securities but do not grant legal or beneficial rights in or against the issuer of those underlying securities.","sourceIds":["robinhood-10q-2026-q2"],"risk":"medium"},{"id":"c4","text":"Robinhood says the Liechtenstein FMA approved the base prospectus as meeting EU Prospectus Regulation standards, but not as an endorsement of RHJ or product quality.","sourceIds":["robinhood-10q-2026-q2"],"risk":"low"},{"id":"c5","text":"Robinhood says Stock Tokens are not registered under U.S. securities laws and are restricted in several jurisdictions including the U.S., Canada, the United Kingdom and Switzerland.","sourceIds":["robinhood-10q-2026-q2"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-crypto-asset-faq-functional-decentralized-investment-contract-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-28T06:12:00.000Z","updatedAt":"2026-09-28T06:12:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Crypto Asset FAQ: Functionality, Decentralization and Investment-Contract Boundary Map","zh-Hans":"SEC Crypto Asset FAQ：功能性、去中心化与投资合约边界地图"},"summary":{"en":"The SEC's September 25, 2026 crypto-asset FAQ is useful only if users keep its status and scope narrow.","zh-Hans":"SEC Crypto Asset FAQ：功能性、去中心化与投资合约边界地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"The SEC Division of Corporation Finance issued crypto-asset FAQs on September 25, 2026.","sourceIds":["sec-crypto-faq"],"risk":"medium"},{"id":"c2","text":"The FAQ says the answers are staff views and have no legal force or effect.","sourceIds":["sec-crypto-faq"],"risk":"medium"},{"id":"c3","text":"The FAQ says it addresses questions related to the March 17, 2026 interpretive release.","sourceIds":["sec-crypto-faq"],"risk":"medium"},{"id":"c4","text":"The FAQ says issuer-defined functionality and decentralization matter when assessing whether represented managerial efforts have been fulfilled.","sourceIds":["sec-crypto-faq"],"risk":"low"},{"id":"c5","text":"The March 2026 interpretive release says a non-security crypto asset can be offered and sold subject to an investment contract.","sourceIds":["sec-interpretive-release"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-caas-kyc-subaccount-api-restrictions","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-28T03:08:00.000Z","updatedAt":"2026-09-28T03:08:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Binance CAAS KYC Subaccount API Restrictions and Travel Rule Endpoint Map","zh-Hans":"Binance CAAS KYC 子账户 API 限制与 Travel Rule 端点地图"},"summary":{"en":"Binance's CAAS FAQ turns subaccount operations into an entity, KYC and endpoint-routing problem.","zh-Hans":"Binance CAAS KYC 子账户 API 限制与 Travel Rule 端点地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance says CAAS subaccount Travel Rule requirements depend on the Binance entity the subaccount is tagged to, not only on registration country.","sourceIds":["binance-caas-faq"],"risk":"medium"},{"id":"c2","text":"Binance says AU-tagged CAAS subaccounts require a Travel Rule questionnaire for deposits and withdrawals with no minimum threshold.","sourceIds":["binance-caas-faq"],"risk":"medium"},{"id":"c3","text":"Binance says Travel Rule subaccounts should use the localentity withdrawal endpoint, while non-Travel-Rule entities should keep the capital withdrawal endpoint.","sourceIds":["binance-caas-faq"],"risk":"medium"},{"id":"c4","text":"Binance says newly created non-KYC subaccounts cannot create API keys and retrieve deposit addresses before completing KYC.","sourceIds":["binance-caas-faq"],"risk":"low"},{"id":"c5","text":"Binance says deposits into older non-KYC subaccounts may be rejected and an appeal through the SAPI asset recovery API may take up to 30 days.","sourceIds":["binance-caas-faq"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-okx-subaccount-api-kyc-permission-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-28T03:08:00.000Z","updatedAt":"2026-09-28T03:08:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs OKX Subaccount API, KYC and Permission Controls","zh-Hans":"Binance vs OKX 子账户 API、KYC 与权限控制对比"},"summary":{"en":"Binance and OKX both use subaccounts to separate operating surfaces, but their control questions are not the same.","zh-Hans":"Binance vs OKX 子账户 API、KYC 与权限控制对比：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance says the master account key is used for broker calls and withdrawals, while the subaccount key is used for trading, deposit address retrieval and user data streams.","sourceIds":["binance-caas-faq"],"risk":"medium"},{"id":"c2","text":"Binance says non-KYC subaccounts cannot create or permission API keys and cannot receive deposits through several broker transfer paths.","sourceIds":["binance-caas-faq"],"risk":"medium"},{"id":"c3","text":"OKX says subaccounts can separate trading strategies, manage multiple bots and control risks independently.","sourceIds":["okx-subaccounts-api"],"risk":"medium"},{"id":"c4","text":"OKX says standard users can create up to five subaccounts.","sourceIds":["okx-subaccounts-api"],"risk":"low"},{"id":"c5","text":"OKX says API permissions include Read, Trade and Withdraw, and warns that Withdraw allows withdrawals via API.","sourceIds":["okx-subaccounts-api"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"eu-casp-sanctions-coinbase-prime-transfer-restriction-map","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-28T03:08:00.000Z","updatedAt":"2026-09-28T03:08:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"EU CASP Sanctions and Coinbase Prime Transfer Restriction Map","zh-Hans":"欧盟 CASP 制裁与 Coinbase Prime 转账限制地图"},"summary":{"en":"EU CASP sanctions now matter to exchange users as a transfer-control and custody-status question, not only as a policy headline. Coinbase says that, effective May 24, 2026, Coinbase Luxembourg S.A.","zh-Hans":"欧盟 CASP 制裁与 Coinbase Prime 转账限制地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase says the EU sanctions page applies to Coinbase Prime clients with Vault wallets held with Coinbase Luxembourg S.A.","sourceIds":["coinbase-eu-sanctions"],"risk":"medium"},{"id":"c2","text":"Coinbase says the May 24, 2026 measures prohibit transactions involving Russian and Belarusian CASPs under Council Regulation (EU) No 833/2014 as amended.","sourceIds":["coinbase-eu-sanctions"],"risk":"medium"},{"id":"c3","text":"Coinbase says inbound deposits from Russian or Belarusian CASPs will be blocked and moved to a Coinbase-controlled holding account.","sourceIds":["coinbase-eu-sanctions"],"risk":"medium"},{"id":"c4","text":"Coinbase says restricted outbound withdrawals can be placed on hold in a Coinbase-controlled holding account or rejected with compliant funds remaining accessible.","sourceIds":["coinbase-eu-sanctions"],"risk":"low"},{"id":"c5","text":"The Council of the EU says the 21st sanctions package introduces the possibility of a full third-country ban for crypto-asset services used by Russia.","sourceIds":["eu-council-21st-sanctions"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-subaccount-kyc-api-restriction-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-28T03:08:00.000Z","updatedAt":"2026-09-28T03:08:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange Subaccount KYC and API Restriction Disclosure Radar","zh-Hans":"交易所子账户 KYC 与 API 限制披露雷达"},"summary":{"en":"NexuAlpha's subaccount radar treats KYC state, API scope and governance as separate evidence fields.","zh-Hans":"交易所子账户 KYC 与 API 限制披露雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance discloses subaccount service and API restrictions tied to KYC status.","sourceIds":["binance-caas-faq"],"risk":"medium"},{"id":"c2","text":"OKX discloses subaccount creation, account mode and API permission setup in one support FAQ.","sourceIds":["okx-subaccounts-api"],"risk":"medium"},{"id":"c3","text":"Kraken says API keys are not members and carry their own simpler permission model.","sourceIds":["kraken-org-api-keys"],"risk":"medium"},{"id":"c4","text":"Kraken says governed operations started by API keys enter the same pipeline as member-started requests and keys never hold Approve.","sourceIds":["kraken-org-api-keys"],"risk":"low"},{"id":"c5","text":"Kraken says the API key secret is shown once at creation and cannot be retrieved later.","sourceIds":["kraken-org-api-keys"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-gemini-passkeys-and-approved-addresses-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-28T03:08:00.000Z","updatedAt":"2026-09-28T03:08:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up Gemini Passkeys and Approved Addresses Safely","zh-Hans":"如何安全设置 Gemini Passkeys 与 Approved Addresses"},"summary":{"en":"A safe Gemini onboarding flow separates identity verification, sign-in authentication and withdrawal-destination control.","zh-Hans":"如何安全设置 Gemini Passkeys 与 Approved Addresses：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Gemini says identity verification in the app requires a clear full photo ID and enables full trading and transfer capabilities after completion.","sourceIds":["gemini-identity"],"risk":"medium"},{"id":"c2","text":"Gemini says 2FA is required and cannot be disabled.","sourceIds":["gemini-2fa"],"risk":"medium"},{"id":"c3","text":"Gemini says passkeys become the default 2FA method across web and mobile for authentication including sign-ins and withdrawals once users opt in.","sourceIds":["gemini-passkeys"],"risk":"medium"},{"id":"c4","text":"Gemini says Address Book entries are known external cryptocurrency addresses designated for specific crypto assets.","sourceIds":["gemini-address-book"],"risk":"low"},{"id":"c5","text":"Gemini says Withdrawal Protection can impose a 7-day waiting period for newly added addresses, and approved-address flows can require waiting period or multi-user approval before withdrawal use.","sourceIds":["gemini-address-book","gemini-approved-address","gemini-withdrawal-protection"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cftc-september-2026-blockchain-recordkeeping-industry-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-28T00:12:00.000Z","updatedAt":"2026-09-28T00:12:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC September 2026 Blockchain Recordkeeping Industry Map","zh-Hans":"CFTC 2026 年 9 月区块链记录保存行业地图"},"summary":{"en":"The CFTC's September 24, 2026 update is decision-relevant because it moves blockchain infrastructure into regulated operational evidence.","zh-Hans":"本文最有价值的地方是克制。CFTC 2026 年 9 月 24 日的更新有决策价值，因为它把区块链基础设施纳入受监管运营证据范围。CFTC staff 表示，更新后的 FAQ 处理两个问题：客户资金投资于 permitted investments 的代币化形式，以及使用区块链技术满足记录保存要求。"},"claims":[{"id":"c1","text":"CFTC staff released updated FAQs on September 24, 2026.","sourceIds":["cftc-faq-update"],"risk":"medium"},{"id":"c2","text":"The update addresses customer funds invested in tokenized forms of permitted investments.","sourceIds":["cftc-faq-update"],"risk":"medium"},{"id":"c3","text":"The update addresses the use of blockchain technologies to satisfy registrant recordkeeping requirements.","sourceIds":["cftc-faq-update"],"risk":"medium"},{"id":"c4","text":"The original FAQs relate to Staff Letter 25-39 on tokenized collateral and Staff Letter 26-05 on digital assets accepted as margin collateral.","sourceIds":["cftc-faq-update"],"risk":"low"},{"id":"c5","text":"CFTC says it joined an SEC interpretation in March 2026 and will administer the Commodity Exchange Act consistent with that interpretation for certain crypto-asset treatment.","sourceIds":["cftc-9198"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cftc-tokenized-collateral-customer-funds-recordkeeping-checklist","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-28T00:12:00.000Z","updatedAt":"2026-09-28T00:12:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC Tokenized Collateral, Customer Funds and Blockchain Recordkeeping Checklist","zh-Hans":"CFTC 代币化抵押品、客户资金与区块链记录保存清单"},"summary":{"en":"The CFTC's September 24, 2026 FAQ update is important because it narrows tokenization from a headline into specific regulated-entity questions: customer funds in tokenized forms of permitted investments and use of blockchain.","zh-Hans":"本文最有价值的地方是克制。CFTC 2026 年 9 月 24 日的 FAQ 更新很重要，因为它把“代币化”从标题收窄为两个受监管实体问题：客户资金是否可投资于 permitted investments 的代币化形式，以及区块链技术能否满足记录保存要求。"},"claims":[{"id":"c1","text":"CFTC staff released FAQ updates on September 24, 2026 to address customer funds in tokenized forms of permitted investments and blockchain recordkeeping.","sourceIds":["cftc-faq-update"],"risk":"medium"},{"id":"c2","text":"The CFTC says the FAQs were originally released on March 20, 2026 and related to Staff Letter 25-39 and Staff Letter 26-05.","sourceIds":["cftc-faq-update"],"risk":"medium"},{"id":"c3","text":"The FAQ says Staff Letter 26-05 has no effect on the list of eligible margin collateral for uncleared swaps under Commission Regulation 23.156.","sourceIds":["cftc-faq-pdf"],"risk":"medium"},{"id":"c4","text":"The FAQ says a swap dealer may exchange a tokenized form of an eligible collateral asset only if it satisfies applicable regulatory requirements and grants the same or functionally equivalent rights.","sourceIds":["cftc-faq-pdf"],"risk":"low"},{"id":"c5","text":"CFTC's December 2025 release says tokenized assets used as collateral in futures and swaps should be analyzed on an individual basis under the existing framework and firm policies.","sourceIds":["cftc-9146"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-statement-ledger-tax-export-retention-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-28T00:12:00.000Z","updatedAt":"2026-09-28T00:12:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange Statement, Ledger and Tax Export Retention Radar","zh-Hans":"交易所账户报表、Ledger 与税务导出留存雷达"},"summary":{"en":"Account-history exports are evidence tools, not interchangeable CSV files. Coinbase says users can download existing monthly statements in HTML, PDF or CSV, generate custom statements by asset, transaction type and date, and use.","zh-Hans":"交易所账户报表、Ledger 与税务导出留存雷达：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Coinbase says users can download monthly statements in HTML, PDF or CSV and generate custom statements by asset, transaction type and date.","sourceIds":["coinbase-statements"],"risk":"medium"},{"id":"c2","text":"Coinbase says Coinbase Taxes includes gain-loss summaries and raw transaction history with custom reports.","sourceIds":["coinbase-tax-reports"],"risk":"medium"},{"id":"c3","text":"Kraken says export types include Account Statement, Trades, Ledgers and Balances.","sourceIds":["kraken-history-export"],"risk":"medium"},{"id":"c4","text":"Kraken says export requests can take from a few minutes to up to a week and users currently need to check the Documents page manually.","sourceIds":["kraken-history-export"],"risk":"low"},{"id":"c5","text":"Kraken says ledger history and trades history answer different questions and should not be treated as the same record.","sourceIds":["kraken-ledger-trades"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-okx-subaccount-api-permissions-and-ip-binding-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-28T00:12:00.000Z","updatedAt":"2026-09-28T00:12:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up OKX Subaccount API Permissions and IP Binding Safely","zh-Hans":"如何安全设置 OKX 子账户 API 权限与 IP 绑定"},"summary":{"en":"A safe OKX subaccount API setup starts with account separation, then key creation, permission selection, passphrase custody and IP restriction.","zh-Hans":"如何安全设置 OKX 子账户 API 权限与 IP 绑定：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"OKX says subaccounts can be used to separate trading strategies, manage multiple trading bots and control risks independently.","sourceIds":["okx-subaccounts"],"risk":"medium"},{"id":"c2","text":"OKX says standard users can create up to five subaccounts.","sourceIds":["okx-subaccounts"],"risk":"medium"},{"id":"c3","text":"OKX says API key creation includes choosing the account or subaccount, selecting required permissions, creating a passphrase and confirming with 2FA.","sourceIds":["okx-subaccounts"],"risk":"medium"},{"id":"c4","text":"OKX says available API permissions include Read, Trade and Withdraw, with Withdraw allowing withdrawals via API and requiring caution.","sourceIds":["okx-subaccounts"],"risk":"low"},{"id":"c5","text":"OKX says IP addresses help secure API keys, up to 20 addresses can be linked per key, and the API passphrase cannot be recovered if lost.","sourceIds":["okx-api-faq"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-organizations-api-withdrawal-governance-controls","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-28T00:12:00.000Z","updatedAt":"2026-09-28T00:12:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken Organizations API and Withdrawal Governance Controls","zh-Hans":"Kraken Organizations API 与提现治理控制"},"summary":{"en":"Kraken Organizations separates account permissions from workflow authority, so a withdrawal-control review has to map both layers.","zh-Hans":"Kraken Organizations API 与提现治理控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Kraken says Withdraw on an account is not sufficient by itself; the member also needs Initiate or Execute on the Withdrawal Request workflow.","sourceIds":["kraken-org-permissions"],"risk":"medium"},{"id":"c2","text":"Kraken says Approve rights for withdrawal requests apply across all accounts of an Organization and are not account-scoped in the current model.","sourceIds":["kraken-org-permissions"],"risk":"medium"},{"id":"c3","text":"Kraken says the Add Withdrawal Addresses API permission can add and remove cryptocurrency and fiat withdrawal addresses.","sourceIds":["kraken-address-api"],"risk":"medium"},{"id":"c4","text":"Kraken warns that combining Add Withdrawal Addresses with Withdraw Funds can allow an attacker with the key to add an address and withdraw assets.","sourceIds":["kraken-address-api"],"risk":"low"},{"id":"c5","text":"Kraken describes API keys as sensitive credentials that can grant access to account data and actions depending on configured permissions.","sourceIds":["kraken-api-security"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-spot-api-rate-limit-websocket-order-control-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-27T21:11:00.000Z","updatedAt":"2026-09-27T21:11:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Spot API Rate Limit, WebSocket and Order Control Checklist","zh-Hans":"Binance Spot API 限速、WebSocket 与订单控制清单"},"summary":{"en":"Binance Spot API integration risk is not only an API-key problem. Binance developer documentation says the WebSocket API uses a 24-hour connection validity window, server ping/pong handling, request IDs, optional rate-limit.","zh-Hans":"Binance Spot API 限速、WebSocket 与订单控制清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance WebSocket API documentation says a single connection is valid for 24 hours and users should expect disconnection after that mark.","sourceIds":["binance-ws-api"],"risk":"medium"},{"id":"c2","text":"Binance WebSocket API documentation says rate limit status can appear in the optional rateLimits field and includes REQUEST_WEIGHT and ORDERS limit types.","sourceIds":["binance-ws-api"],"risk":"medium"},{"id":"c3","text":"Binance WebSocket API documentation says requests fail with status 429 when unfilled order count or request rate limits are violated.","sourceIds":["binance-ws-api"],"risk":"medium"},{"id":"c4","text":"Binance WebSocket API documentation says repeated rate-limit violations can result in status 418 auto-bans.","sourceIds":["binance-ws-api"],"risk":"low"},{"id":"c5","text":"Binance unfilled-order-count documentation says successful new orders increment unfilled order count while rejected or unsuccessful orders are not guaranteed to do so.","sourceIds":["binance-order-count"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"circle-cctp-v2-usdc-fast-transfer-hooks-and-finality-risk-map","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-27T21:11:00.000Z","updatedAt":"2026-09-27T21:11:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Circle CCTP V2 USDC Fast Transfer, Hooks and Finality Risk Map","zh-Hans":"Circle CCTP V2 USDC Fast Transfer、Hooks 与最终性风险地图"},"summary":{"en":"Circle frames CCTP as a permissionless onchain utility for USDC movement across blockchains through native burning and minting, not as a generic third-party bridge wrapper.","zh-Hans":"Circle CCTP V2 USDC Fast Transfer、Hooks 与最终性风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Circle Help says CCTP facilitates USDC transfers between blockchains through native burning and minting.","sourceIds":["circle-cctp-help"],"risk":"medium"},{"id":"c2","text":"Circle Help says CCTP V2 is the canonical CCTP and CCTP V1 is legacy with no new chain integrations or feature updates.","sourceIds":["circle-cctp-help"],"risk":"medium"},{"id":"c3","text":"Circle says CCTP V2 Fast Transfer can enable cross-chain transactions to settle in seconds regardless of source blockchain.","sourceIds":["circle-cctp-v2"],"risk":"medium"},{"id":"c4","text":"Circle says Hooks allow developers to automate post-transfer actions on the destination blockchain.","sourceIds":["circle-cctp-v2"],"risk":"low"},{"id":"c5","text":"Circle says Standard Transfer settles according to a blockchain's standard finality time.","sourceIds":["circle-cctp-v2"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cross-chain-stablecoin-transfer-finality-status-disclosure-radar","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-27T21:11:00.000Z","updatedAt":"2026-09-27T21:11:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Cross-Chain Stablecoin Transfer Finality and Status Disclosure Radar","zh-Hans":"跨链稳定币转账最终性与状态披露雷达"},"summary":{"en":"Cross-chain stablecoin transfer evidence has to name both the rail and the status checkpoint. Circle's USDC Bridge materials describe CCTP-powered native burn-and-mint transfers and distinguish transfer timing or status by route.","zh-Hans":"本文最有价值的地方是克制。跨链稳定币转账证据必须同时说明轨道和状态节点。"},"claims":[{"id":"c1","text":"Circle Help says the USDC Bridge uses CCTP to burn and mint native USDC across supported blockchains rather than moving wrapped or synthetic USDC.","sourceIds":["circle-usdc-bridge"],"risk":"medium"},{"id":"c2","text":"Circle Help says transfer timing and status can differ by source and destination chain and by route.","sourceIds":["circle-transfer-status"],"risk":"medium"},{"id":"c3","text":"HashKey Global withdrawal guidance says users must verify asset, network, address and other withdrawal information because errors may cause permanent loss.","sourceIds":["hashkey-withdrawal"],"risk":"medium"},{"id":"c4","text":"HashKey Global withdrawal materials describe wallet ownership verification and whitelisted withdrawal addresses.","sourceIds":["hashkey-withdrawal"],"risk":"low"},{"id":"c5","text":"HashKey Global exchange rules say deposits and withdrawals can require internal review and Travel Rule-related review in specified circumstances.","sourceIds":["hashkey-exchange-rules"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fatf-2026-defi-stablecoin-offshore-vasp-action-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-27T21:11:00.000Z","updatedAt":"2026-09-27T21:11:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"FATF 2026 DeFi, Stablecoin and Offshore VASP Action Map","zh-Hans":"FATF 2026 DeFi、稳定币与离岸 VASP 行动地图"},"summary":{"en":"FATF's 2026 virtual-asset update is decision-relevant because it turns crypto policy into implementation risk.","zh-Hans":"本文最有价值的地方是克制。FATF 的 2026 虚拟资产更新之所以有决策价值，是因为它把加密政策变成了执行风险。FATF 称，受调查司法辖区中已有 83% 通过了实施 Travel Rule 的立法，高于 2025 年的 73%，但许多地区仍需把法律框架转化为有效监管和执法。"},"claims":[{"id":"c1","text":"FATF says 83% of surveyed jurisdictions had passed legislation implementing the Travel Rule, up from 73% in 2025.","sourceIds":["fatf-va-vasp-2026"],"risk":"medium"},{"id":"c2","text":"FATF says many jurisdictions still need to translate legal frameworks into effective supervision and enforcement.","sourceIds":["fatf-va-vasp-2026"],"risk":"medium"},{"id":"c3","text":"FATF highlights offshore VASPs, DeFi platforms, unhosted wallets and stablecoins as continuing or emerging risk areas.","sourceIds":["fatf-va-vasp-2026"],"risk":"medium"},{"id":"c4","text":"FATF's 2026 update says most identified on-chain illicit activity now involves stablecoins.","sourceIds":["fatf-va-vasp-2026"],"risk":"low"},{"id":"c5","text":"FATF's DeFi materials highlight DPRK-related cyber theft and DeFi platform risk as priority concerns.","sourceIds":["fatf-defi-2026"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-open-hashkey-global-account-complete-kyc-and-withdrawal-whitelist","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-27T21:11:00.000Z","updatedAt":"2026-09-27T21:11:00.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"How to Open a HashKey Global Account, Complete KYC and Set a Withdrawal Whitelist","zh-Hans":"如何开通 HashKey Global 账户、完成 KYC 并设置提币白名单"},"summary":{"en":"A safe HashKey Global onboarding flow is eligibility check, official registration, KYC verification, then withdrawal-whitelist and ownership controls.","zh-Hans":"本文最有价值的地方是克制。安全的 HashKey Global onboarding 流程应是资格核验、官方注册、KYC 验证，然后再处理提币白名单和地址所有权控制。"},"claims":[{"id":"c1","text":"HashKey Global says individual investors can register through the official website or application and then proceed to Identity Verification.","sourceIds":["hashkey-account-opening"],"risk":"medium"},{"id":"c2","text":"HashKey Global account-opening documentation says applicants may need identification documents, proof of address, passport verification, facial recognition and liveness checks.","sourceIds":["hashkey-account-opening"],"risk":"medium"},{"id":"c3","text":"HashKey Global's registration guide says users should prepare email and phone number, complete sign-up, upload valid identification, complete facial recognition, provide proof of address where applicable, provide financial information and sign agreements.","sourceIds":["hashkey-registration-kyc"],"risk":"medium"},{"id":"c4","text":"HashKey Global's supported-regions page says the service is available only in supported regions and documents restrictions by country or region.","sourceIds":["hashkey-supported-regions"],"risk":"low"},{"id":"c5","text":"HashKey Global withdrawal materials describe ownership verification and whitelist-address handling for withdrawals.","sourceIds":["hashkey-withdrawal"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-tokenisation-governance-central-bank-money-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-27T17:52:00.000Z","updatedAt":"2026-09-27T17:52:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Tokenisation Governance and Central Bank Money Risk Map","zh-Hans":"BIS 代币化治理与中央银行货币风险地图"},"summary":{"en":"BIS and FSB materials frame tokenisation as a market-structure and financial-stability question.","zh-Hans":"本文最有价值的地方是克制。BIS 与 FSB 材料把代币化放在市场结构和金融稳定问题中理解。"},"claims":[{"id":"c1","text":"BIS says token arrangements can provide platform-based intermediation across the end-to-end lifecycle of financial assets.","sourceIds":["bis-tokenisation"],"risk":"medium"},{"id":"c2","text":"BIS says token arrangements may decrease transaction costs and enable innovative use cases, but safety and efficiency require sound governance and risk management.","sourceIds":["bis-tokenisation"],"risk":"medium"},{"id":"c3","text":"BIS says tokenisation gives central banks an opportunity to reflect on the role of central bank money in the digitalising financial system.","sourceIds":["bis-tokenisation"],"risk":"medium"},{"id":"c4","text":"FSB says crypto-asset markets, stablecoins and DeFi are closely interrelated and should be considered holistically for financial stability risks.","sourceIds":["fsb-crypto-assets"],"risk":"low"},{"id":"c5","text":"SEC staff says tokenized securities vary in structure and rights, including issuer-sponsored and third-party-sponsored models.","sourceIds":["sec-tokenized-securities"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-account-vs-coinbase-wallet-custody-recovery-boundary","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-27T17:52:00.000Z","updatedAt":"2026-09-27T17:52:00.000Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Account vs Coinbase Wallet Custody and Recovery Boundary","zh-Hans":"Coinbase 账户与 Coinbase Wallet 托管和恢复边界对比"},"summary":{"en":"A Coinbase account and Coinbase Wallet solve different custody jobs. Coinbase describes an exchange account as a custodial account where the platform holds crypto on the user's behalf and the platform manages private keys.","zh-Hans":"本文最有价值的地方是克制。Coinbase 账户与 Coinbase Wallet 解决的是不同托管任务。"},"claims":[{"id":"c1","text":"Coinbase account creation uses email or Apple/Google sign-up paths and includes verification steps before access expands.","sourceIds":["coinbase-create-account"],"risk":"medium"},{"id":"c2","text":"Coinbase says exchanges are custodial wallets where the platform holds crypto on behalf of the user and manages private keys.","sourceIds":["coinbase-custody-education"],"risk":"medium"},{"id":"c3","text":"Coinbase says self-custody wallets give direct control and that a recovery phrase should be kept confidential.","sourceIds":["coinbase-custody-education"],"risk":"medium"},{"id":"c4","text":"Coinbase Wallet supports created and imported wallets, including smart wallet, email/social log-in wallet and mnemonic wallet types.","sourceIds":["coinbase-wallet-manage"],"risk":"low"},{"id":"c5","text":"Coinbase says smart wallets and mnemonic wallets without an email or social sign-in method cannot be recovered if the user loses the passkey or recovery phrase.","sourceIds":["coinbase-wallet-manage"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-wallet-supported-network-transition-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-27T17:52:00.000Z","updatedAt":"2026-09-27T17:52:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Wallet Supported Network Transition Checklist","zh-Hans":"Coinbase Wallet 支持网络变化核验清单"},"summary":{"en":"Coinbase Wallet support documentation makes network support a wallet-type and deadline issue.","zh-Hans":"本文最有价值的地方是克制。Coinbase Wallet 支持文档把网络支持问题变成了钱包类型与截止日期问题。"},"claims":[{"id":"c1","text":"Coinbase Wallet states that some networks will no longer be supported after August 15, 2026.","sourceIds":["coinbase-wallet-supported"],"risk":"medium"},{"id":"c2","text":"Coinbase Wallet says assets on unsupported networks remain safe and accessible and can be accessed by importing the recovery phrase into another wallet.","sourceIds":["coinbase-wallet-supported"],"risk":"medium"},{"id":"c3","text":"Coinbase Wallet says smart wallets support EVM-compatible networks only.","sourceIds":["coinbase-wallet-supported"],"risk":"medium"},{"id":"c4","text":"Coinbase Wallet says email/social log-in and mnemonic wallets support EVM-compatible networks, Solana and Bitcoin.","sourceIds":["coinbase-wallet-supported"],"risk":"low"},{"id":"c5","text":"Coinbase Wallet manage-wallets documentation says up to 10 created or imported wallets can exist at a time under Coinbase Wallet.","sourceIds":["coinbase-wallet-manage"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-digital-assets-lifecycle-governance-and-tokenization-controls","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-27T17:52:00.000Z","updatedAt":"2026-09-27T17:52:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Digital Assets Lifecycle Governance and Tokenization Controls","zh-Hans":"DTCC 数字资产生命周期治理与代币化控制"},"summary":{"en":"DTCC's digital-assets page frames tokenization as market-infrastructure connectivity, not a standalone token promise.","zh-Hans":"本文最有价值的地方是克制。DTCC 的数字资产页面把代币化描述为市场基础设施连接能力，而不是孤立的代币承诺。DTCC 称，DTC 持有的证券可以被表示为数字资产，并在 approved networks 中使用，同时仍锚定既有保护和韧性；页面还强调风险管理、生命周期支持、运营效率、系统集成、访问控制和可审计活动记录。"},"claims":[{"id":"c1","text":"DTCC says securities held at DTC can be represented as digital assets and used across approved networks while remaining anchored to existing protections and resiliency.","sourceIds":["dtcc-digital-assets"],"risk":"medium"},{"id":"c2","text":"DTCC says its digital-assets work provides controls, governance and oversight for digital asset activity.","sourceIds":["dtcc-digital-assets"],"risk":"medium"},{"id":"c3","text":"DTCC says its services connect the digital asset lifecycle from creation through settlement and support auditable activity records.","sourceIds":["dtcc-digital-assets"],"risk":"medium"},{"id":"c4","text":"BIS says token arrangements can change existing market structures through platform-based intermediation across the end-to-end lifecycle of financial assets.","sourceIds":["bis-tokenisation"],"risk":"low"},{"id":"c5","text":"SEC staff says a tokenized security is a security-format financial instrument with ownership records maintained in whole or in part on crypto networks.","sourceIds":["sec-tokenized-securities"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"self-custody-wallet-recovery-passkey-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-27T17:52:00.000Z","updatedAt":"2026-09-27T17:52:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Self-Custody Wallet Recovery and Passkey Disclosure Radar","zh-Hans":"自托管钱包恢复与 Passkey 披露雷达"},"summary":{"en":"The recovery surface is different for an exchange account and a self-custody wallet. Coinbase says an exchange account can involve platform-managed private keys and account recovery, while self-custody wallets rely on the user's.","zh-Hans":"本文最有价值的地方是克制。交易所账户与自托管钱包的恢复表面不同。"},"claims":[{"id":"c1","text":"Coinbase says a self-custody wallet gives direct control and that the recovery phrase should be stored carefully and kept confidential.","sourceIds":["coinbase-custody-education"],"risk":"medium"},{"id":"c2","text":"Coinbase says if a recovery phrase is lost for a self-custody wallet, no one can help recover access.","sourceIds":["coinbase-custody-education"],"risk":"medium"},{"id":"c3","text":"Coinbase Wallet describes smart wallet, email/social log-in wallet and mnemonic wallet types with different recovery implications.","sourceIds":["coinbase-wallet-manage"],"risk":"medium"},{"id":"c4","text":"Coinbase Wallet says some smart and mnemonic wallets cannot be recovered if the passkey or recovery phrase is lost.","sourceIds":["coinbase-wallet-manage"],"risk":"low"},{"id":"c5","text":"Kraken account-creation guidance uses official-site verification, email/password entry and activation before the account is ready.","sourceIds":["kraken-create-account"],"risk":"low"}],"relatedVenues":["kraken","coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-wallet-api-withdrawal-permission-ip-whitelist-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-27T11:42:02.000Z","updatedAt":"2026-09-27T11:42:02.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Wallet API Withdrawal Permission, IP Whitelist and Network Checklist","zh-Hans":"Binance 钱包 API 提现权限、IP 白名单与网络检查清单"},"summary":{"en":"Binance's Wallet REST API documentation makes wallet automation an operational-permission decision.","zh-Hans":"Binance 的 Wallet REST API 文档把钱包自动化变成了权限运营问题。Capital API 暴露币种、网络、充值、提现、确认数和地址元数据；Binance Academy 说明，开启提现权限的 API key 只有在严格必要时才应使用，只读 key 足以查询历史，IP 白名单与最小权限可以降低风险。安全实施路径是先只读，核验网络元数据，绑定可信 IP，仅在有书面需求时添加提现权限，并记录非秘密状态码而不是盲目重试。"},"claims":[{"id":"c1","text":"Binance Wallet REST API Capital documentation lists endpoints for coin information, deposit address, deposit history, withdraw address list, withdraw quota, withdraw and withdraw history.","sourceIds":["binance-wallet-capital"],"risk":"medium"},{"id":"c2","text":"The Binance Capital API coin information response includes network-level fields such as depositEnable, withdrawEnable, withdrawFee, withdrawMin, minConfirm, unLockConfirm and withdrawTag.","sourceIds":["binance-wallet-capital"],"risk":"medium"},{"id":"c3","text":"Binance Academy says withdrawal-enabled API keys should be used with caution and only where strictly necessary.","sourceIds":["binance-wallet-academy"],"risk":"low"},{"id":"c4","text":"Binance Academy says a read-only key is sufficient for querying deposit addresses, deposit history and withdrawal history.","sourceIds":["binance-wallet-academy"],"risk":"low"},{"id":"c5","text":"Binance Academy strongly encourages IP whitelisting, minimal permission scope, key rotation and monitoring.","sourceIds":["binance-wallet-academy"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-central-bank-money-anchor-stablecoin-tokenization-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-27T11:42:02.000Z","updatedAt":"2026-09-27T11:42:02.000Z","readTime":"22 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Central Bank Money Anchor, Stablecoin and Tokenization Risk Map","zh-Hans":"BIS 中央银行货币锚定、稳定币与代币化风险地图"},"summary":{"en":"BIS materials frame tokenization and stablecoins as money-and-settlement architecture, not just faster interfaces.","zh-Hans":"BIS 材料把代币化与稳定币放在货币和结算架构中理解，而不是只看更快的界面。BIS 代币化报告称，token arrangements 可能通过平台化中介改变市场结构，但仍需要健全治理与风险管理。2026 年 BIS 演讲称，政策应强化稳定币保护措施，并把代币化纳入以中央银行货币为锚的双层体系。决策含义是：在把任何代币化支付或储备设计视为安全之前，用户应识别结算资产、发行人负债、赎回路径、治理模型与备用轨道。"},"claims":[{"id":"c1","text":"The BIS tokenisation report says token arrangements can change market structures through platform-based intermediation across the end-to-end lifecycle of financial assets.","sourceIds":["bis-tokenisation"],"risk":"medium"},{"id":"c2","text":"The BIS tokenisation report says safety and efficiency gains require sound governance and risk management, and FMI risks may apply differently.","sourceIds":["bis-tokenisation"],"risk":"medium"},{"id":"c3","text":"The BIS 2026 speech says policy recommendations focus on tightening stablecoin safeguards and integrating tokenisation into the two-tier system anchored in central bank money.","sourceIds":["bis-anchoring-trust"],"risk":"low"},{"id":"c4","text":"The FSB says crypto-asset markets, stablecoins and DeFi are closely interrelated and should be assessed holistically for financial stability risks.","sourceIds":["fsb-stablecoins"],"risk":"low"},{"id":"c5","text":"SEC staff says a tokenized security is still a security-format financial instrument with record-of-ownership implications rather than a separate magic asset class.","sourceIds":["sec-tokenized"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"blackrock-bstbl-brsrv-tokenized-money-market-reserve-readiness","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-27T11:42:02.000Z","updatedAt":"2026-09-27T11:42:02.000Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"BlackRock BSTBL and BRSRV Tokenized Money Market Reserve Readiness Map","zh-Hans":"BlackRock BSTBL 与 BRSRV 代币化货币市场储备就绪地图"},"summary":{"en":"BlackRock's August 2026 launch of BSTBL and BRSRV is a reserve-asset and recordkeeping development, not a retail stablecoin promise.","zh-Hans":"BlackRock 2026 年 8 月推出 BSTBL 与 BRSRV，是储备资产与记录系统的发展，不是面向零售用户的稳定币承诺。 BlackRock 称 BSTBL 是既有货币市场基金的 OnChain share class，可在 approved investor wallets 之间转让，并由 BNY 担任 transfer agent 与 tokenization provider。"},"claims":[{"id":"c1","text":"BlackRock says BSTBL and BRSRV combine regulated money market fund liquidity and stability with blockchain-based infrastructure.","sourceIds":["blackrock-launch"],"risk":"medium"},{"id":"c2","text":"BlackRock says BSTBL introduces a tokenized share class on Ethereum of an existing money market fund and can be transferred between approved investor wallets, subject to applicable law.","sourceIds":["blackrock-launch"],"risk":"medium"},{"id":"c3","text":"BlackRock says BNY serves as transfer agent and tokenization provider for BSTBL OnChain Shares.","sourceIds":["blackrock-launch"],"risk":"low"},{"id":"c4","text":"BlackRock says BRSRV is designed for digitally native institutional investors, has daily dividend reinvestment and multi-blockchain accessibility, and uses Securitize as transfer agent and tokenization provider.","sourceIds":["blackrock-launch"],"risk":"low"},{"id":"c5","text":"The SEC August 2026 MMF statistics identify BlackRock Daily Reinvestment Stablecoin Reserve Vehicle OnChain Shares and BlackRock Select Treasury Based Liquidity Fund OnChain Shares among tokenized MMFs.","sourceIds":["sec-mmf-stats-aug-2026"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-deposit-address-tag-memo-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-27T11:42:02.000Z","updatedAt":"2026-09-27T11:42:02.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange Deposit Address Tag and Memo Disclosure Radar","zh-Hans":"加密交易所充值地址 Tag 与 Memo 披露雷达"},"summary":{"en":"A deposit address can be incomplete without its network and tag or memo fields. Binance's Wallet REST API exposes address, tag, network metadata and withdrawTag fields; Kraken withdrawal guidance warns that the correct asset and.","zh-Hans":"充值地址如果缺少网络与 tag/memo 字段，就可能是不完整的目的地。 Binance Wallet REST API 暴露 address、tag、network metadata 和 withdrawTag 等字段；Kraken 提现说明提醒用户选择正确资产与网络，并完整复制地址；Coinbase 支持材料要求用户在排查未到账资金前确认预期网络。"},"claims":[{"id":"c1","text":"Binance Capital API deposit address response includes an address field and a tag field, and its coin metadata can include networkList and withdrawTag.","sourceIds":["binance-capital"],"risk":"medium"},{"id":"c2","text":"Binance coin metadata includes network fields such as depositEnable, withdrawEnable, addressRegex, memoRegex and minConfirm.","sourceIds":["binance-capital"],"risk":"medium"},{"id":"c3","text":"Kraken warns users to select the correct asset and network and says withdrawing from the wrong network can result in loss of funds.","sourceIds":["kraken-withdraw"],"risk":"low"},{"id":"c4","text":"Coinbase missing-transaction support asks users to verify that the transaction was sent on the right network for the asset.","sourceIds":["coinbase-missing"],"risk":"low"},{"id":"c5","text":"Coinbase send guidance separates destination address, network choice and preview confirmation before sending crypto.","sourceIds":["coinbase-send-receive"],"risk":"low"}],"relatedVenues":["binance","kraken","coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-vs-gemini-withdrawal-address-approval-hold-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-27T11:42:02.000Z","updatedAt":"2026-09-27T11:42:02.000Z","readTime":"22 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken vs Gemini Withdrawal Address Approval, Hold and Dual-Control Checks","zh-Hans":"Kraken 与 Gemini 提现地址审批、等待期与双人控制检查"},"summary":{"en":"Kraken and Gemini both document withdrawal-address controls, but the decision surface is different.","zh-Hans":"Kraken 与 Gemini 都披露了提现地址控制，但决策表面不同。Kraken 要求先添加并确认提现地址，并说明在特定密码安全状态下，新提现地址可能触发 24 小时等待。Gemini 的 approved address 文档适用于欧盟、欧洲经济区和英国客户，单用户账户有 7 天审批等待，多用户账户则涉及管理员/经理审批。真正有用的选择不是抽象地判断哪家更安全，而是核验地址控制模型、确认路径、等待期、作用范围与恢复规则是否适合当前资金动作。"},"claims":[{"id":"c1","text":"Kraken says a user must add and confirm a new cryptocurrency withdrawal address before withdrawing to that address.","sourceIds":["kraken-add-address"],"risk":"medium"},{"id":"c2","text":"Kraken says certain password changes without sign-in 2FA or a Master Key can hold withdrawals to new addresses for 24 hours.","sourceIds":["kraken-add-address"],"risk":"medium"},{"id":"c3","text":"Gemini says its approved-address article applies to EU, EEA and UK customers, while other customers should use its Address Book article.","sourceIds":["gemini-approved-address"],"risk":"low"},{"id":"c4","text":"Gemini says a single-user approved address cannot receive withdrawals until the address clears a 7-day approval hold.","sourceIds":["gemini-approved-address"],"risk":"low"},{"id":"c5","text":"Gemini says multi-user accounts require administrator or manager approval, with another administrator or manager approving the address request.","sourceIds":["gemini-approved-address"],"risk":"low"}],"relatedVenues":["kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-project-mandala-compliance-proof-tokenized-payment-readiness-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-27T08:42:15.057Z","updatedAt":"2026-09-27T08:42:15.057Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Project Mandala Compliance Proof and Tokenized Payment Readiness Map","zh-Hans":"BIS Project Mandala 合规证明与代币化支付就绪地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for BIS Project Mandala compliance proof tokenized payment readiness map. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：BIS Project Mandala is useful for tokenized-payment decisions because it shows a compliance-proof pattern, not because it proves any live venue is compliant."},"claims":[{"id":"c1","text":"BIS says Project Mandala explores encoding jurisdiction-specific policy and regulatory requirements into a common protocol for cross-border transactions.","sourceIds":["bis-project-mandala"],"risk":"medium"},{"id":"c2","text":"BIS says Mandala's envisioned compliance-by-design architecture could support digital assets including CBDCs and tokenised deposits.","sourceIds":["bis-project-mandala"],"risk":"medium"},{"id":"c3","text":"The BIS Mandala report says compliance proofs can be attached to digital settlement assets such as wholesale CBDC or to Swift credit transfer instructions.","sourceIds":["bis-mandala-report"],"risk":"medium"},{"id":"c4","text":"The BIS Mandala report says the architecture facilitates secure peer-to-peer communication, standardises regulatory inputs and outputs, and automatically generates cryptographic compliance proofs.","sourceIds":["bis-mandala-report"],"risk":"medium"},{"id":"c5","text":"BIS CPMI tokenisation work frames tokenised money and tokenised assets as designs that still require settlement, legal and operational analysis.","sourceIds":["bis-tokenisation-concepts"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-vs-okx-api-key-ip-binding-expiry-withdraw-permission-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-27T08:42:15.057Z","updatedAt":"2026-09-27T08:42:15.057Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit vs OKX API Key IP Binding, Expiry and Withdrawal Permission Controls","zh-Hans":"Bybit 与 OKX API Key IP 绑定、过期与提现权限控制对比"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Bybit vs OKX API key IP binding expiry withdrawal permission controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：Bybit and OKX both expose API-key controls, but the safety checklist is not identical."},"claims":[{"id":"c1","text":"Bybit V5 API documentation says the API-key information endpoint returns fields including readOnly, permissions, deadlineDay, expiredAt and createdAt.","sourceIds":["bybit-api-key-info"],"risk":"medium"},{"id":"c2","text":"Bybit's API FAQ says an API key created without binding IP addresses will expire after 90 days and describes a renewal flow.","sourceIds":["bybit-api-faq"],"risk":"medium"},{"id":"c3","text":"Bybit error codes include permission-denied and unmatched-IP responses that should be treated as control evidence rather than ignored retry noise.","sourceIds":["bybit-error-codes"],"risk":"medium"},{"id":"c4","text":"OKX API documentation says API keys can have Read, Trade and Withdraw permissions and recommends linking API keys to IP addresses.","sourceIds":["okx-api-docs"],"risk":"medium"},{"id":"c5","text":"OKX documentation says each API key can bind up to 20 IP addresses and that trade or withdraw keys without an IP address expire after 14 days of inactivity.","sourceIds":["okx-api-docs","okx-api-faq"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-advanced-trade-websocket-jwt-user-channel-reconnect-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-27T08:42:15.057Z","updatedAt":"2026-09-27T08:42:15.057Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Advanced Trade WebSocket JWT, User Channel and Reconnect Checklist","zh-Hans":"Coinbase Advanced Trade WebSocket JWT、用户频道与重连清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Coinbase Advanced Trade WebSocket JWT user channel reconnect checklist. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：Coinbase Advanced Trade WebSocket integration should be treated as an authenticated feed design problem, not just a URL copy task."},"claims":[{"id":"c1","text":"Coinbase Help says Advanced Trade WebSocket feeds provide real-time market data updates for orders and trades.","sourceIds":["coinbase-help-ws"],"risk":"medium"},{"id":"c2","text":"Coinbase Help lists a user channel that sends messages including the authenticated user.","sourceIds":["coinbase-help-ws"],"risk":"medium"},{"id":"c3","text":"Coinbase developer documentation says Advanced Trade supports programmatic trading and order management with REST and WebSocket protocols.","sourceIds":["coinbase-ws-overview"],"risk":"medium"},{"id":"c4","text":"Coinbase's official Python SDK overview says the SDK includes REST and WebSocket clients.","sourceIds":["coinbase-python-sdk"],"risk":"medium"},{"id":"c5","text":"Coinbase portfolio documentation says each portfolio requires a dedicated API key in Coinbase Developer Platform to limit portfolio access.","sourceIds":["coinbase-portfolios"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-active-session-device-revocation-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-27T08:42:15.057Z","updatedAt":"2026-09-27T08:42:15.057Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange Active Session and Device Revocation Disclosure Radar","zh-Hans":"加密交易所活跃会话与设备撤销披露雷达"},"summary":{"en":"A source-mapped NexuAlpha decision brief for crypto exchange active session device revocation disclosure radar. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：Active-session and device-revocation pages are a practical security signal because they show whether an exchange explains how to notice and remove unwanted access."},"claims":[{"id":"c1","text":"Coinbase Help says users can see active sessions, authorized mobile applications, web sessions and confirmed devices, and remove unauthorized access.","sourceIds":["coinbase-secure-account"],"risk":"medium"},{"id":"c2","text":"Coinbase Help says device confirmation authorizes devices and IP addresses and is different from two-step verification.","sourceIds":["coinbase-device-confirmation"],"risk":"medium"},{"id":"c3","text":"Kraken Support says Active sessions show date, time, device and location or IP and allow ending individual or all sessions.","sourceIds":["kraken-active-sessions"],"risk":"medium"},{"id":"c4","text":"Binance Academy says Device Management shows devices currently authorized to access the account and that removed devices require email confirmation again.","sourceIds":["binance-device-management"],"risk":"medium"},{"id":"c5","text":"Binance security guidance says users can go to Devices and Activities to delete unused devices after a compromise concern.","sourceIds":["binance-compromised-account"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"uk-us-transatlantic-taskforce-stablecoin-tokenization-market-readiness","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-27T08:42:15.057Z","updatedAt":"2026-09-27T08:42:15.057Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"UK-US Transatlantic Taskforce Stablecoin and Tokenization Market Readiness","zh-Hans":"英美跨大西洋工作组稳定币与代币化市场就绪清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for UK US Transatlantic Taskforce stablecoin tokenization market readiness. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：The UK-US Transatlantic Taskforce creates a policy-coordination signal, not an automatic approval for any stablecoin, exchange or tokenized asset."},"claims":[{"id":"c1","text":"HM Treasury says the UK and US published initial recommendations to deepen cross-border connectivity, reduce fragmentation and accelerate tokenisation in digital markets.","sourceIds":["hmt-ttmf-recommendations"],"risk":"medium"},{"id":"c2","text":"HM Treasury says a UK-US joint statement on stablecoins was published alongside the recommendations.","sourceIds":["hmt-ttmf-recommendations"],"risk":"medium"},{"id":"c3","text":"U.S. Treasury says the recommendations identify opportunities to enhance cross-border capital raising, update supervisory cooperation and provide clarity for tokenized financial activity.","sourceIds":["us-treasury-ttmf"],"risk":"medium"},{"id":"c4","text":"The U.S.-UK Financial Regulatory Working Group statement says authorities discussed digital finance, operational resilience, stablecoins and digital asset market structure.","sourceIds":["us-uk-frwg-2026"],"risk":"medium"},{"id":"c5","text":"The FCA says the UK cryptoasset regime brings a broad range of cryptoasset activities within the regulatory perimeter and that the full scope expands from 25 October 2027.","sourceIds":["fca-crypto-regime"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-bstocks-dividend-reinvestment-collateral-eligibility-rights-boundary","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-27T05:42:55.570Z","updatedAt":"2026-09-27T05:42:55.570Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Binance bStocks Dividend Reinvestment, Collateral Eligibility and Rights Boundary","zh-Hans":"Binance bStocks 股息再投资、抵押资格与权利边界"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Binance bStocks dividend reinvestment collateral eligibility rights boundary. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：Binance bStocks require a rights-boundary map before they are treated like direct shares."},"claims":[{"id":"c1","text":"Binance says eligible TSMB and CRMB users receive dividend benefits via reinvestment into additional units or fractions of the same underlying security after applicable withholding taxes, fees, costs and deductions.","sourceIds":["binance-tsm-crm-dividend"],"risk":"medium"},{"id":"c2","text":"Binance says on-chain holders of TSMB and CRMB receive bStock dividends through a multiplier adjustment.","sourceIds":["binance-tsm-crm-dividend"],"risk":"medium"},{"id":"c3","text":"Binance says BNCB was added as an eligible collateral asset under Cross Margin, Portfolio Margin and Portfolio Margin Pro, while borrowing was not supported at that time.","sourceIds":["binance-bncb-collateral"],"risk":"medium"},{"id":"c4","text":"Binance says bStocks margin collateral eligibility was extended to all Cross Margin and Portfolio Margin accounts with additional risk controls for Regular, VIP 1 and VIP 2 accounts.","sourceIds":["binance-bstocks-all-users"],"risk":"medium"},{"id":"c5","text":"Binance Academy says bStocks are not direct ownership of underlying shares and instead provide exposure and economic benefits through a certificate-like structure.","sourceIds":["binance-academy-bstocks"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-kraken-passkey-recovery-and-withdrawal-verification-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-27T05:42:55.570Z","updatedAt":"2026-09-27T05:42:55.570Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs Kraken Passkey Recovery and Withdrawal Verification Controls","zh-Hans":"Binance 与 Kraken Passkey 恢复和提现验证控制对比"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Binance vs Kraken passkey recovery withdrawal verification controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：Binance and Kraken both support passkeys, but the operating risk is different."},"claims":[{"id":"c1","text":"Binance Support says enabling “Must verify using passkey” requires passkey verification when logging in and making a withdrawal.","sourceIds":["binance-must-passkey"],"risk":"medium"},{"id":"c2","text":"Binance Support warns that after enabling that setting, users may be unable to log in if they lose access to passkeys and should disable it before device or passkey-environment changes.","sourceIds":["binance-must-passkey"],"risk":"medium"},{"id":"c3","text":"Binance Support says passkeys can be created with iCloud Keychain, USB or NFC security keys, device screen lock, PIN, biometrics or another device depending on platform.","sourceIds":["binance-create-passkey"],"risk":"medium"},{"id":"c4","text":"Kraken Support says passkeys are cryptographic credentials bound to a website or app and distinguishes roaming passkeys from non-roaming device-bound passkeys.","sourceIds":["kraken-passkey"],"risk":"medium"},{"id":"c5","text":"Kraken Support recommends multiple 2FA methods to reduce the chance of account access loss.","sourceIds":["kraken-2fa"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fatf-2026-virtual-asset-gaps-defi-control-and-travel-rule-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-27T05:42:55.570Z","updatedAt":"2026-09-27T05:42:55.570Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"FATF 2026 Virtual Asset Gaps, DeFi Control and Travel Rule Risk Map","zh-Hans":"FATF 2026 虚拟资产缺口、DeFi 控制权与 Travel Rule 风险地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for FATF 2026 virtual asset gaps DeFi control Travel Rule risk map. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：FATF's 2026 virtual-asset work frames the problem as implementation gaps, not as a simple pass/fail label for crypto markets."},"claims":[{"id":"c1","text":"FATF says 83% of surveyed jurisdictions had passed legislation implementing the Travel Rule, up from 73% in 2025, while some jurisdictions still had implementation under way.","sourceIds":["fatf-2026-va-update"],"risk":"medium"},{"id":"c2","text":"FATF says priority actions include risk-based supervision and enforcement, Travel Rule implementation, international cooperation and risks from stablecoins, offshore VASPs, unhosted wallets and DeFi arrangements.","sourceIds":["fatf-2026-va-update"],"risk":"medium"},{"id":"c3","text":"FATF's 2026 DeFi report says effective implementation requires a functional and risk-based approach and includes recommendations to determine the existence of control.","sourceIds":["fatf-defi-2026"],"risk":"medium"},{"id":"c4","text":"FSB says implementation of its global crypto framework has progressed but gaps and inconsistencies remain.","sourceIds":["fsb-crypto-stablecoins"],"risk":"medium"},{"id":"c5","text":"BIS Project Mandala shows a compliance-by-design approach where compliance proofs can accompany digital settlement assets or payment instructions across borders.","sourceIds":["bis-mandala"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-bitget-passkey-anti-phishing-code-and-official-channel-check","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-27T05:42:55.570Z","updatedAt":"2026-09-27T05:42:55.570Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up Bitget Passkey, Anti-Phishing Code and Official Channel Check","zh-Hans":"如何设置 Bitget Passkey、防钓鱼码与官方渠道核验"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to set up Bitget passkey anti-phishing code official channel check. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：A safe Bitget onboarding flow should bind authentication before moving funds: set up passkey where supported, enable or edit the anti-phishing code, and verify official channels before trusting links or messages."},"claims":[{"id":"c1","text":"Bitget Support says passkeys use device-based verification and public-private key encryption, with the private key saved on the user's device.","sourceIds":["bitget-passkey"],"risk":"medium"},{"id":"c2","text":"Bitget Support says passkeys are domain-specific and do not activate on fake or phishing websites.","sourceIds":["bitget-passkey"],"risk":"medium"},{"id":"c3","text":"Bitget Support says the anti-phishing code appears in genuine Bitget emails, SMS messages and on the login page after setup.","sourceIds":["bitget-antiphishing"],"risk":"medium"},{"id":"c4","text":"Bitget Support says users can verify emails, website addresses or social media accounts through the Bitget Official Verification Tool.","sourceIds":["bitget-official-check"],"risk":"medium"},{"id":"c5","text":"Bitget Support says staff will never ask for private keys, passwords or 2FA codes.","sourceIds":["bitget-scam-victim"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-offline-mode-withdrawal-protection-window-api-c2c-pay-controls","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-27T05:42:55.570Z","updatedAt":"2026-09-27T05:42:55.570Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"OKX Offline Mode Withdrawal Protection Window, API, C2C and Pay Controls","zh-Hans":"OKX Offline Mode 提现保护窗口、API、C2C 与 Pay 控制清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for OKX Offline Mode withdrawal protection window API C2C Pay controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：OKX Offline Mode is a time-window control, not an address-book substitute."},"claims":[{"id":"c1","text":"OKX Help says Offline Mode lets KYC-verified users set a daily protection window with hour-level precision up to 12 hours.","sourceIds":["okx-offline-mode"],"risk":"medium"},{"id":"c2","text":"OKX Help says withdrawals initiated during that protection window are blocked immediately regardless of amount.","sourceIds":["okx-offline-mode"],"risk":"medium"},{"id":"c3","text":"OKX Help says the feature covers crypto withdrawals, C2C selling, API withdrawals and Pay top-ups.","sourceIds":["okx-offline-mode"],"risk":"medium"},{"id":"c4","text":"OKX Help says withdrawal Allowlist restricts withdrawals to recipients saved in the withdrawal address book and can be paired with a new-address withdrawal lock.","sourceIds":["okx-allowlist-app","okx-allowlist-web"],"risk":"medium"},{"id":"c5","text":"OKX Help says new-address withdrawal lock can prevent newly added recipients from being used for withdrawals for 24 hours.","sourceIds":["okx-allowlist-app","okx-allowlist-web"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-api-key-credential-recovery-disclosure-radar-passphrase-secret-ip-allowlist","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-27T02:49:43.076Z","updatedAt":"2026-09-27T02:49:43.076Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto API Key Credential Recovery Radar: Passphrase, Secret and IP Allowlist Disclosures","zh-Hans":"加密 API Key 凭证恢复雷达：Passphrase、Secret 与 IP 白名单披露"},"summary":{"en":"A source-mapped NexuAlpha decision brief for crypto API key credential recovery passphrase secret IP allowlist disclosure radar. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：API-key safety depends on what cannot be recovered as much as what can be configured."},"claims":[{"id":"c1","text":"OKX Help says the API passphrase cannot be retrieved if forgotten and a new API key must be created.","sourceIds":["okx-api-faq"],"risk":"medium"},{"id":"c2","text":"OKX API documentation says an API key can bind up to 20 IP addresses and that unbound trade or withdrawal keys expire after 14 days of inactivity.","sourceIds":["okx-api-docs"],"risk":"medium"},{"id":"c3","text":"Coinbase Help says Exchange API keys are tied to one portfolio and require an IP address whitelist.","sourceIds":["coinbase-api-key"],"risk":"medium"},{"id":"c4","text":"Coinbase Help says the API secret and passphrase are shown only once and cannot be retrieved by Coinbase if lost.","sourceIds":["coinbase-api-key"],"risk":"medium"},{"id":"c5","text":"Coinbase Developer documentation says Advanced Trade portfolios can segregate strategies and each portfolio should have a dedicated CDP API key to limit access.","sourceIds":["coinbase-portfolios"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-com-exchange-travel-rule-address-ownership-verification-checklist","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-27T02:49:43.076Z","updatedAt":"2026-09-27T02:49:43.076Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto.com Exchange Travel Rule Address Ownership Verification Checklist","zh-Hans":"Crypto.com Exchange Travel Rule 地址所有权验证清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Crypto.com Exchange Travel Rule address ownership verification checklist. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：Crypto. com Exchange Travel Rule documentation turns address handling into an ownership-verification workflow, not merely an address-book preference. Crypto."},"claims":[{"id":"c1","text":"Crypto.com Help says Exchange users must declare ownership of deposit addresses under its Travel Rule process.","sourceIds":["crypto-com-travel-rule"],"risk":"medium"},{"id":"c2","text":"Crypto.com Help says withdrawal addresses must be whitelisted by declaring ownership or completing ownership verification through its Travel Rule compliance partner.","sourceIds":["crypto-com-travel-rule"],"risk":"medium"},{"id":"c3","text":"Crypto.com Help says deposits from unknown addresses can be put on hold until ownership is declared.","sourceIds":["crypto-com-travel-rule"],"risk":"medium"},{"id":"c4","text":"Crypto.com Help says third-party deposits and withdrawals are not permitted in the described Travel Rule workflow.","sourceIds":["crypto-com-travel-rule"],"risk":"medium"},{"id":"c5","text":"Coinbase Europe Travel Rule documentation also requires additional counterparty information for some deposits and withdrawals, showing that the operational issue is broader than one venue.","sourceIds":["coinbase-eu-travel-rule"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-ledgerscan-vs-tokenization-service-record-reconciliation-boundary","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-27T02:49:43.076Z","updatedAt":"2026-09-27T02:49:43.076Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC LedgerScan vs Tokenization Service Record and Reconciliation Boundary","zh-Hans":"DTCC LedgerScan 与 Tokenization Service：记录和对账边界"},"summary":{"en":"A source-mapped NexuAlpha decision brief for DTCC LedgerScan vs Tokenization Service record reconciliation boundary. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：DTCC LedgerScan and DTCC Tokenization Service should not be collapsed into one generic RWA claim."},"claims":[{"id":"c1","text":"DTCC says LedgerScan consolidates onchain and offchain data into a unified view and supports reconciliation across blockchain networks and traditional systems.","sourceIds":["dtcc-ledgerscan"],"risk":"medium"},{"id":"c2","text":"DTCC says the Tokenization Service supports tokenized assets through interoperability, asset mobility, market connectivity and capital-efficiency infrastructure.","sourceIds":["dtcc-tokenization"],"risk":"medium"},{"id":"c3","text":"DTCC says DTC-issued tokens include controls such as mint, burn, pause and clawback functionality.","sourceIds":["dtcc-tokenization"],"risk":"medium"},{"id":"c4","text":"The DTC Tokenization Service FAQ says LedgerScan will maintain DTC's official record of all token movements and locations.","sourceIds":["dtcc-tokenization-faq"],"risk":"medium"},{"id":"c5","text":"SEC staff says tokenized securities vary by model, structure and rights afforded to holders, so a record system does not remove rights analysis.","sourceIds":["sec-tokenized-securities"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-crypto-com-exchange-account-verification-2fa-withdrawal-whitelist","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-27T02:49:43.076Z","updatedAt":"2026-09-27T02:49:43.076Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up Crypto.com Exchange Account Verification, 2FA and Withdrawal Whitelist","zh-Hans":"如何设置 Crypto.com Exchange 账户验证、2FA 与提币白名单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to set up Crypto.com Exchange account verification 2FA withdrawal whitelist. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：A safe Crypto. com Exchange onboarding flow is account verification, device and 2FA security, then withdrawal whitelist and Travel Rule address checks. Crypto."},"claims":[{"id":"c1","text":"Crypto.com Help says Exchange account verification requires information including name, nationality, date of birth, email, mobile OTP, ID submission and photo.","sourceIds":["crypto-com-verification"],"risk":"medium"},{"id":"c2","text":"Crypto.com Help says the Exchange App supports account creation, ID verification, trusted device management, withdrawal whitelist, biometric ID, 2FA and anti-phishing code.","sourceIds":["crypto-com-exchange-app"],"risk":"medium"},{"id":"c3","text":"Crypto.com Help says 2FA is used for actions that affect assets and lists crypto withdrawal and wallet address whitelist among covered actions.","sourceIds":["crypto-com-2fa"],"risk":"medium"},{"id":"c4","text":"Crypto.com Exchange Help says withdrawal whitelisting requires entering OTP and 2FA code when prompted.","sourceIds":["crypto-com-exchange-whitelist"],"risk":"medium"},{"id":"c5","text":"Crypto.com Travel Rule Help says withdrawal addresses must be whitelisted by declaring ownership or completing ownership verification.","sourceIds":["crypto-com-travel-rule"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-vs-crypto-com-withdrawal-2fa-whitelist-lock-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-27T02:49:43.076Z","updatedAt":"2026-09-27T02:49:43.076Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken vs Crypto.com Withdrawal 2FA, Whitelist and Lock Controls","zh-Hans":"Kraken 与 Crypto.com 提币 2FA、白名单和锁定控制对比"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Kraken vs Crypto.com withdrawal 2FA whitelist lock controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：Kraken and Crypto. com both frame withdrawal security as multiple controls, but the controls attach to different objects."},"claims":[{"id":"c1","text":"Kraken Support says Funding 2FA requires a code for withdrawals and transfers to Futures, but does not prevent adding cryptocurrency withdrawal addresses.","sourceIds":["kraken-funding-2fa"],"risk":"medium"},{"id":"c2","text":"Kraken Support says Global Settings Lock is needed for Funding 2FA to be effective in the described withdrawal-address case.","sourceIds":["kraken-funding-2fa","kraken-2fa"],"risk":"medium"},{"id":"c3","text":"Crypto.com Help says crypto withdrawals can use a passkey if configured, or SMS OTP plus authenticator 2FA if a passkey is not set up.","sourceIds":["crypto-com-withdrawals"],"risk":"medium"},{"id":"c4","text":"Crypto.com Help says a newly added whitelisted address can be subject to a 24-hour withdrawal lock when that feature is enabled.","sourceIds":["crypto-com-withdrawals","crypto-com-exchange-whitelist"],"risk":"medium"},{"id":"c5","text":"Crypto.com Exchange Help says withdrawal whitelisting allows transfers only to approved wallets and requires OTP plus 2FA during the whitelisting process.","sourceIds":["crypto-com-exchange-whitelist"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-project-agora-tokenized-cross-border-payments-settlement-readiness","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-26T23:43:14.736Z","updatedAt":"2026-09-26T23:43:14.736Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Project Agora Tokenized Cross-Border Payments Settlement Readiness","zh-Hans":"BIS Project Agora 代币化跨境支付结算准备度"},"summary":{"en":"A source-mapped NexuAlpha decision brief for BIS Project Agora tokenized cross-border payments settlement readiness. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 BIS Project Agora 代币化跨境支付结算准备度 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"BIS says Project Agora demonstrated multi-currency settlement using tokenised central bank reserves and tokenised commercial bank deposits for wholesale cross-border payments.","sourceIds":["bis-agora-project"],"risk":"medium"},{"id":"c2","text":"The BIS Project Agora FAQ describes the project as a prototype to assess desirability, feasibility and viability rather than the platform of the future.","sourceIds":["bis-agora-faq"],"risk":"medium"},{"id":"c3","text":"BIS Annual Economic Report 2026 says a unified ledger could integrate tokenised central bank reserves, commercial bank money and tokenised assets if robust safeguards are in place.","sourceIds":["bis-aer-2026"],"risk":"medium"},{"id":"c4","text":"Bank of Canada says the project tested a multi-currency unified ledger for cross-border wholesale transactions combining tokenized commercial bank deposits and wholesale central bank money.","sourceIds":["bank-canada-agora"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-passkey-2fa-migration-radar-sms-authenticator-security-key","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-26T23:43:14.736Z","updatedAt":"2026-09-26T23:43:14.736Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange Passkey and 2FA Migration Radar: SMS, Authenticator and Security Key Controls","zh-Hans":"交易所 Passkey 与 2FA 迁移雷达：短信、验证器与安全密钥控制"},"summary":{"en":"A source-mapped NexuAlpha decision brief for crypto exchange passkey 2FA migration SMS authenticator security key radar. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 交易所 Passkey 与 2FA 迁移雷达：短信、验证器与安全密钥控制 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Gemini says SMS and Authy are being replaced with stronger options such as passkeys, hardware keys or authenticator apps.","sourceIds":["gemini-authy-sms"],"risk":"medium"},{"id":"c2","text":"Gemini says passkey setup can depend on iCloud, Google Password Manager or another password manager for passkeys that work across devices.","sourceIds":["gemini-passkeys"],"risk":"medium"},{"id":"c3","text":"Kraken says passkeys are bound to a website or app identity and classifies passkeys as roaming or non-roaming device-bound methods.","sourceIds":["kraken-passkey"],"risk":"medium"},{"id":"c4","text":"Coinbase says Coinbase One account protection is available to select members who have set up a passkey or security key.","sourceIds":["coinbase-account-protection"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"gemini-vs-coinbase-withdrawal-protection-vault-delay-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-26T23:43:14.736Z","updatedAt":"2026-09-26T23:43:14.736Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Gemini vs Coinbase Withdrawal Protection and Vault Delay Controls","zh-Hans":"Gemini 与 Coinbase 提币保护和金库延迟控制对比"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Gemini vs Coinbase withdrawal protection vault delay controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Gemini 与 Coinbase 提币保护和金库延迟控制对比 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Gemini Support says Withdrawal Protection prevents crypto from leaving until a newly added address has been in the Address Book for at least 7 days when the feature is enabled.","sourceIds":["gemini-withdrawal-protection"],"risk":"medium"},{"id":"c2","text":"Gemini Support says approved addresses for EU, EEA and UK users must clear a 7-day approval hold before external withdrawals can be made to that wallet.","sourceIds":["gemini-approved-address"],"risk":"medium"},{"id":"c3","text":"Coinbase Help says a Coinbase.com allowlist address becomes available for sends after 48 hours and disabling allowlisting can also take 48 hours outside the early activation window.","sourceIds":["coinbase-allowlist"],"risk":"medium"},{"id":"c4","text":"Coinbase Help says vault withdrawals need linked-email approvals and then a 48-hour waiting period before processing.","sourceIds":["coinbase-vault-pending"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-create-gemini-account-verify-identity-and-set-withdrawal-protection","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-26T23:43:14.736Z","updatedAt":"2026-09-26T23:43:14.736Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"How to Create a Gemini Account, Verify Identity and Set Withdrawal Protection","zh-Hans":"如何创建 Gemini 账户、完成身份验证并设置提币保护"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to create Gemini account verify identity set withdrawal protection. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 如何创建 Gemini 账户、完成身份验证并设置提币保护 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Gemini Support says users located within areas of availability can register using the Gemini app, while institutional accounts use the website flow.","sourceIds":["gemini-app-apply"],"risk":"medium"},{"id":"c2","text":"Gemini Support says identity verification in the app requires uploading a clear and full photo ID and that completed verification enables full trading and transfer capabilities.","sourceIds":["gemini-identity-app"],"risk":"medium"},{"id":"c3","text":"Gemini Support says verification requires a valid government-issued photo ID and biometric face scan, with accepted document types varying by residence.","sourceIds":["gemini-documents"],"risk":"medium"},{"id":"c4","text":"Gemini Support says 2FA is required and lists passkeys, authenticator apps and hardware security keys as supported methods.","sourceIds":["gemini-2fa"],"risk":"medium"},{"id":"c5","text":"Gemini Support says Withdrawal Protection imposes a 7-day waiting period for newly added addresses when enabled.","sourceIds":["gemini-withdrawal-protection"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"iosco-financial-asset-tokenization-settlement-asset-interoperability-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-26T23:43:14.736Z","updatedAt":"2026-09-26T23:43:14.736Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"IOSCO Financial Asset Tokenization Settlement Asset and Interoperability Risk Map","zh-Hans":"IOSCO 金融资产代币化：结算资产与互操作风险地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for IOSCO financial asset tokenization settlement asset interoperability risk map. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 IOSCO 金融资产代币化：结算资产与互操作风险地图 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"IOSCO's release says the report reviews commercial use cases such as tokenized money market funds and fixed income instruments and how regulators are responding.","sourceIds":["iosco-news"],"risk":"medium"},{"id":"c2","text":"IOSCO's report identifies lack of interoperability across blockchains and lack of high-quality settlement assets as key structural challenges to scaling tokenization.","sourceIds":["iosco-report"],"risk":"medium"},{"id":"c3","text":"IOSCO describes tokenization impacts across issuance, distribution, secondary trading, post-trade services, custody and collateral management.","sourceIds":["iosco-report"],"risk":"medium"},{"id":"c4","text":"SEC staff says tokenized securities vary by rights and structure and its statement has no legal force or effect, so record and rights analysis remains central.","sourceIds":["sec-tokenized-securities"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-auction-mode-new-asset-listing-phase-readiness-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-26T20:44:49.316Z","updatedAt":"2026-09-26T20:44:49.316Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Auction Mode and New Asset Listing Phase Readiness Checklist","zh-Hans":"Coinbase 拍卖模式与新资产上市阶段准备清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Coinbase auction mode new asset listing phase readiness checklist. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Coinbase 拍卖模式与新资产上市阶段准备清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Coinbase Help says Auction Mode allows customers to submit limit orders while no matches occur and only limit orders with the allow-taker flag are accepted.","sourceIds":["coinbase-auction-mode"],"risk":"medium"},{"id":"c2","text":"Coinbase Help says auction mode includes collection, match and completion phases, and the match phase should take no longer than 15 seconds.","sourceIds":["coinbase-auction-mode"],"risk":"medium"},{"id":"c3","text":"Coinbase Help says auction mode can be used to launch new order books or relaunch previously paused books and lasts at least 10 minutes or until a stable open price is established.","sourceIds":["coinbase-auction-mode"],"risk":"medium"},{"id":"c4","text":"Coinbase Help says new asset listings can move through Transfer Only, Auction, Limit Only, Full Trading and Cancel Only phases, with no fills in Transfer Only and no new orders in Cancel Only.","sourceIds":["coinbase-new-listings"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-collateral-appchain-vs-tokenization-service-custody-settlement-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-26T20:44:49.316Z","updatedAt":"2026-09-26T20:44:49.316Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Collateral AppChain vs Tokenization Service Custody and Settlement Controls","zh-Hans":"DTCC Collateral AppChain 与代币化服务的托管和结算控制"},"summary":{"en":"A source-mapped NexuAlpha decision brief for DTCC Collateral AppChain vs Tokenization Service custody settlement controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 DTCC Collateral AppChain 与代币化服务的托管和结算控制 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"DTCC says its Tokenization Service is built on market infrastructure and supports interoperability, asset mobility, market connectivity and capital efficiency.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c2","text":"DTCC says tokenized DTC assets can move between traditional and blockchain ecosystems using the same CUSIP and are designed to represent the same legal rights, economic interest and investor protections.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c3","text":"DTCC says DTC-issued tokens include mint, burn, pause and clawback controls and that ComposerX LedgerScan provides near real-time ownership tracking across traditional and blockchain ledgers.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c4","text":"DTCC describes the Collateral AppChain as moving from experiment toward production infrastructure for tokenized collateral, multichain interoperability and production-scale adoption.","sourceIds":["dtcc-appchain-production"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-create-bitfinex-account-verify-identity-and-secure-withdrawals","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-26T20:44:49.316Z","updatedAt":"2026-09-26T20:44:49.316Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"How to Create a Bitfinex Account, Verify Identity and Secure Withdrawals","zh-Hans":"如何创建 Bitfinex 账户、完成身份验证并保护提现"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to create Bitfinex account verify identity secure withdrawals. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 如何创建 Bitfinex 账户、完成身份验证并保护提现 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Bitfinex Help says users should double-check the official Bitfinex website before creating an account and complete email confirmation after sign-up.","sourceIds":["bitfinex-create-account"],"risk":"medium"},{"id":"c2","text":"Bitfinex Help says users must enable two-factor authentication during account creation before they can access Bitfinex features.","sourceIds":["bitfinex-create-account","bitfinex-secure-account"],"risk":"medium"},{"id":"c3","text":"Bitfinex verification guidance says individual accounts can apply for Basic Plus, Intermediate or Full verification and may need identity, residential and other information depending on level.","sourceIds":["bitfinex-verify-individual"],"risk":"medium"},{"id":"c4","text":"Bitfinex withdrawal-whitelist guidance says changing an existing address whitelist or enabling withdrawals for previously disabled currencies triggers an automatic five-day withdrawal hold.","sourceIds":["bitfinex-whitelist"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"order-preview-validate-amend-acknowledgement-radar-api-execution-controls","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-26T20:44:49.316Z","updatedAt":"2026-09-26T20:44:49.316Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Order Preview, Validate and Amend Acknowledgement Radar for API Execution Controls","zh-Hans":"API 执行控制雷达：订单预览、验证与改单确认"},"summary":{"en":"A source-mapped NexuAlpha decision brief for order preview validate amend acknowledgement API execution controls radar. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 API 执行控制雷达：订单预览、验证与改单确认 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Coinbase Developer Platform describes Advanced Trade API as supporting programmatic trading and order management through REST API and WebSocket protocol.","sourceIds":["coinbase-advanced-api"],"risk":"medium"},{"id":"c2","text":"Kraken says the validate input parameter for REST AddOrder or WebSocket addOrder simulates order checks and a validate call never returns an order ID.","sourceIds":["kraken-advanced-api-faq"],"risk":"medium"},{"id":"c3","text":"OKX documentation says a successful order-amend response means the request was accepted and users should refer to WebSocket order results for the amendment outcome.","sourceIds":["okx-api-guide"],"risk":"medium"},{"id":"c4","text":"Binance Developer Docs present Spot REST API endpoint definitions, request parameters, payload schemas, endpoint security types and rate-limit information for authenticated trading workflows.","sourceIds":["binance-spot-rest"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"stablecoins-vs-tokenised-deposits-bis-imf-settlement-risk-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-26T20:44:49.316Z","updatedAt":"2026-09-26T20:44:49.316Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Stablecoins vs Tokenised Deposits: BIS and IMF Settlement Risk Map","zh-Hans":"稳定币与代币化存款：BIS 和 IMF 结算风险地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for stablecoins vs tokenised deposits BIS IMF settlement risk map. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 稳定币与代币化存款：BIS 和 IMF 结算风险地图 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"BIS says stablecoins and tokenised deposits could coexist if their roles are clearly delineated and safeguards are in place.","sourceIds":["bis-frontier-speech"],"risk":"medium"},{"id":"c2","text":"BIS says tokenised deposits should carry the bulk of day-to-day payments and wholesale settlement within prudential perimeters and with settlement in central bank money.","sourceIds":["bis-frontier-speech"],"risk":"medium"},{"id":"c3","text":"IMF remarks describe tokenized deposits as a digital extension of existing bank liabilities that retain the two-tier monetary system while remaining exposed to uninsured bank credit risk where applicable.","sourceIds":["imf-tokenized-finance-money"],"risk":"medium"},{"id":"c4","text":"IMF remarks describe regulated stablecoins as privately issued reserve-backed tokens whose par convertibility depends on reserve quality, issuer operational capacity and liquidity of underlying assets.","sourceIds":["imf-tokenized-finance-money"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-wallet-system-upgrade-deposit-withdrawal-pause-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-26T17:41:37.856Z","updatedAt":"2026-09-26T17:41:37.856Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Wallet System Upgrade: Deposit and Withdrawal Pause Checklist","zh-Hans":"Binance 钱包系统升级：充值与提现暂停清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Binance wallet system upgrade deposit withdrawal pause checklist 2026. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Binance 钱包系统升级：充值与提现暂停清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Binance's English announcement says deposits and withdrawals across the platform would be suspended from 2026-09-22 06:00 UTC to support an infrastructure wallet system upgrade.","sourceIds":["binance-wallet-upgrade-en"],"risk":"medium"},{"id":"c2","text":"The same announcement says trading of tokens would not be impacted during wallet maintenance and deposits and withdrawals would reopen once the system was deemed stable.","sourceIds":["binance-wallet-upgrade-en"],"risk":"medium"},{"id":"c3","text":"The Chinese Binance announcement is the same official notice family and should be treated as localization, while the English original controls if translations differ.","sourceIds":["binance-wallet-upgrade-zh","binance-wallet-upgrade-en"],"risk":"medium"},{"id":"c4","text":"The Binance maintenance list showed adjacent network-upgrade, migration and wallet-system notices, reinforcing that users should check the exact announcement, asset and network before moving funds.","sourceIds":["binance-maintenance-list"],"risk":"medium"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-vs-coinbase-exchange-allowlist-vault-withdrawal-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-26T17:41:37.856Z","updatedAt":"2026-09-26T17:41:37.856Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase vs Coinbase Exchange Allowlist and Vault Withdrawal Controls","zh-Hans":"Coinbase 与 Coinbase Exchange 提币白名单和金库控制对比"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Coinbase vs Coinbase Exchange allowlist vault withdrawal controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Coinbase 与 Coinbase Exchange 提币白名单和金库控制对比 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Coinbase Help says allowlisting limits sends to address-book entries, requires 2-step verification to activate, deactivate and use, and new addresses become available after 48 hours.","sourceIds":["coinbase-com-allowlist"],"risk":"medium"},{"id":"c2","text":"Coinbase Exchange Help says whitelisting restricts crypto withdrawals to addresses in the Address Book and applies an 8-hour initial window followed by a 48-hour hold for new addresses.","sourceIds":["coinbase-exchange-whitelist"],"risk":"medium"},{"id":"c3","text":"Coinbase Exchange Help says disabling whitelisting has a 48-hour hold period and users cannot withdraw to an address that is not yet whitelisted.","sourceIds":["coinbase-exchange-whitelist"],"risk":"medium"},{"id":"c4","text":"Coinbase Vault guidance says only the master account holder can request a withdrawal, withdrawal approval can require multiple co-signers, and a 48-hour waiting period follows required approvals.","sourceIds":["coinbase-vault-setup","coinbase-vault-pending"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-withdrawal-hold-period-disclosure-radar-address-book-vault-allowlist","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-26T17:41:37.856Z","updatedAt":"2026-09-26T17:41:37.856Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Withdrawal Hold Period Radar: Address Book, Vault and Allowlist Disclosures","zh-Hans":"提币等待期雷达：地址簿、金库与白名单披露"},"summary":{"en":"A source-mapped NexuAlpha decision brief for crypto withdrawal hold period address book vault allowlist disclosure radar. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 提币等待期雷达：地址簿、金库与白名单披露 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Coinbase.com allowlisting says addresses become available for sends after 48 hours and disabling allowlisting can also take 48 hours unless reversed within the early activation window.","sourceIds":["coinbase-com-allowlist"],"risk":"medium"},{"id":"c2","text":"Coinbase Exchange whitelisting says already saved addresses are immediately whitelisted when the feature is turned on and later new addresses go through a 48-hour hold.","sourceIds":["coinbase-exchange-whitelist"],"risk":"medium"},{"id":"c3","text":"Coinbase Vault pending-withdrawal guidance says all approvals must be complete before the 48-hour withdrawal period starts.","sourceIds":["coinbase-vault-pending"],"risk":"medium"},{"id":"c4","text":"Bitstamp's security guidance says whitelisting restricts withdrawals to trusted addresses while also reducing day-to-day flexibility until new addresses are added.","sourceIds":["bitstamp-security-precautions"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-tokenization-service-vs-sec-tokenized-security-rights-record-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-26T17:41:37.856Z","updatedAt":"2026-09-26T17:41:37.856Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Tokenization Service vs SEC Tokenized Security Rights Record Map","zh-Hans":"DTCC 代币化服务与 SEC 代币化证券权利记录地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for DTCC tokenization service SEC tokenized security rights record map. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 DTCC 代币化服务与 SEC 代币化证券权利记录地图 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"DTCC says its Tokenization Service is designed to bridge traditional and blockchain-based environments while integrating tokenized assets with existing custody, settlement and servicing processes.","sourceIds":["dtcc-tokenization-product"],"risk":"medium"},{"id":"c2","text":"DTCC's May 2026 release says the service is designed for real-world DTC-custodied assets with the same entitlements, investor protections and ownership rights as assets held in traditional form.","sourceIds":["dtcc-tokenization-release"],"risk":"medium"},{"id":"c3","text":"SEC staff says tokenized securities vary by structure and rights and generally fall into issuer-sponsored and third-party tokenization categories.","sourceIds":["sec-tokenized-securities"],"risk":"medium"},{"id":"c4","text":"SEC staff says in an issuer-sponsored model a crypto-network transfer may result in a transfer on the master securityholder file, making the authoritative record central to the rights analysis.","sourceIds":["sec-tokenized-securities"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-create-bitstamp-account-verify-identity-and-secure-withdrawals","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-26T17:41:37.856Z","updatedAt":"2026-09-26T17:41:37.856Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"How to Create a Bitstamp Account, Verify Identity and Secure Withdrawals","zh-Hans":"如何创建 Bitstamp 账户、完成身份验证并保护提现"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to create Bitstamp account verify identity secure withdrawals. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 如何创建 Bitstamp 账户、完成身份验证并保护提现 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Bitstamp says account and registered email should be protected with two-factor authentication and that security codes are required when confirming crypto withdrawals.","sourceIds":["bitstamp-security-precautions"],"risk":"medium"},{"id":"c2","text":"Bitstamp's KYC article says financial companies use KYC to identify clients and assess risk, and basic checks may require a government-issued ID while higher-risk relationships may require more information.","sourceIds":["bitstamp-kyc"],"risk":"medium"},{"id":"c3","text":"Bitstamp's 2FA article describes two-factor authentication as requiring two different authentication factors, such as a password and a one-time code.","sourceIds":["bitstamp-2fa"],"risk":"medium"},{"id":"c4","text":"Bitstamp API documentation lists crypto withdrawal error cases including user not verified, address not verified, withdrawals disabled and an API key set for another withdrawal address.","sourceIds":["bitstamp-api"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-okx-withdrawal-allowlist-address-book-lock-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-22T05:44:42.988Z","updatedAt":"2026-09-22T05:44:42.988Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs OKX Withdrawal Allowlist, Address Book and Lock Controls","zh-Hans":"Binance 与 OKX 提币白名单、地址簿和锁定控制对比"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Binance vs OKX withdrawal allowlist address book lock controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Binance 与 OKX 提币白名单、地址簿和锁定控制对比 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Binance Support says enabling withdrawal whitelist means users can only withdraw to addresses on the whitelist and must verify the request with passkey or 2FA.","sourceIds":["binance-whitelist"],"risk":"medium"},{"id":"c2","text":"Binance Support says a whitelist withdrawal limit can suspend withdrawals to newly added whitelist addresses for a selected time period, giving more time to secure an account if an attacker adds a new address.","sourceIds":["binance-whitelist"],"risk":"medium"},{"id":"c3","text":"OKX says Allowlist restricts withdrawals to saved address-book recipients and New address withdrawal lock can prevent withdrawals to newly added recipients for 24 hours.","sourceIds":["okx-allowlist-web","okx-allowlist-app"],"risk":"medium"},{"id":"c4","text":"OKX says address-book Network scope and Token scope settings can restrict EVM or token applicability, while address filtering during withdrawal depends on the selected token and network.","sourceIds":["okx-address-type"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-advanced-trade-portfolio-api-key-scope-controls","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-22T05:44:42.988Z","updatedAt":"2026-09-22T05:44:42.988Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Advanced Trade Portfolio API Key Scope Controls","zh-Hans":"Coinbase Advanced Trade 投资组合 API Key 范围控制清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Coinbase Advanced Trade portfolio API key scope controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Coinbase Advanced Trade 投资组合 API Key 范围控制清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Coinbase Help says an Exchange API key can only be used for a single portfolio and requires an IP address whitelist during creation.","sourceIds":["coinbase-api-key"],"risk":"medium"},{"id":"c2","text":"Coinbase Help says the API secret and passphrase are shown only once and Coinbase cannot retrieve them if lost.","sourceIds":["coinbase-api-key"],"risk":"medium"},{"id":"c3","text":"Coinbase Help lists API key permissions including View, Transfer, Trade and Manage, with Transfer able to move value for accounts including deposits and withdrawals.","sourceIds":["coinbase-api-key"],"risk":"medium"},{"id":"c4","text":"Coinbase Developer documentation says Advanced Trade supports multiple portfolios and each portfolio should have a dedicated CDP API key to limit portfolio access.","sourceIds":["coinbase-portfolios"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"global-crypto-policy-calendar-transfer-agent-carf-innovation-exemption-watch","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-22T05:44:42.988Z","updatedAt":"2026-09-22T05:44:42.988Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Policy Calendar: Transfer-Agent Rules, CARF and Tokenized-Market Exemption Watch","zh-Hans":"加密政策日历：转让代理规则、CARF 与代币化市场豁免观察"},"summary":{"en":"A source-mapped NexuAlpha decision brief for crypto policy calendar transfer agent CARF tokenized market exemption watch. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 加密政策日历：转让代理规则、CARF 与代币化市场豁免观察 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"The SEC public-comments page lists Transfer Agent Rules comments due November 3, 2026.","sourceIds":["sec-comments"],"risk":"medium"},{"id":"c2","text":"The SEC Transfer Agent Rules page identifies file number S7-2026-30, release number 34-106246, SEC issue date September 1, 2026 and Federal Register publication date September 4, 2026.","sourceIds":["sec-transfer-agent-rule"],"risk":"medium"},{"id":"c3","text":"The SEC Crypto Newsroom lists September 2026 items including tokenized NMS stock exemption statements and the transfer-agent proposal.","sourceIds":["sec-crypto-newsroom"],"risk":"medium"},{"id":"c4","text":"OECD CARF material concerns tax information exchange and reporting for crypto-assets rather than exchange product approval or investment merit.","sourceIds":["oecd-carf"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-use-jupiter-connect-wallet-and-make-first-swap-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-22T05:44:42.988Z","updatedAt":"2026-09-22T05:44:42.988Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"How to Use Jupiter: Connect a Wallet and Make a First Swap Safely","zh-Hans":"如何使用 Jupiter：连接钱包并安全完成首次兑换"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to use Jupiter connect wallet first swap safely. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 如何使用 Jupiter：连接钱包并安全完成首次兑换 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Jupiter developer documentation says Metis is Jupiter routing engine powering every swap on jup.ag.","sourceIds":["jupiter-swap-guide"],"risk":"medium"},{"id":"c2","text":"Jupiter developer documentation describes a swap flow of getting a quote, building a transaction, signing it and sending it through an RPC endpoint.","sourceIds":["jupiter-swap-guide"],"risk":"medium"},{"id":"c3","text":"Jupiter documentation says quote output includes fields such as routePlan, outAmount, otherAmountThreshold and priceImpactPct, which are relevant before signing.","sourceIds":["jupiter-swap-guide"],"risk":"medium"},{"id":"c4","text":"Jupiter public wallet material presents wallet connection as the access step for swapping, making wallet permission and transaction review central to onboarding.","sourceIds":["jupiter-unified-wallet"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-transfer-agent-tokenized-securities-recordkeeping-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-22T05:44:42.988Z","updatedAt":"2026-09-22T05:44:42.988Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Transfer-Agent Proposal and Tokenized Securities Recordkeeping Risk Map","zh-Hans":"SEC 转让代理规则提案与代币化证券记录风险地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for SEC transfer agent tokenized securities recordkeeping risk map. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 SEC 转让代理规则提案与代币化证券记录风险地图 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"The SEC transfer-agent rule page says the proposal would update rules and forms for registered transfer agents and reflects electronic recordkeeping, communications and services to issuers, investors and intermediaries.","sourceIds":["sec-transfer-agent-rule"],"risk":"medium"},{"id":"c2","text":"The SEC press release says the proposal reflects transfer-agent use of blockchain technology in connection with securities offerings and transfers of shares.","sourceIds":["sec-transfer-agent-press"],"risk":"medium"},{"id":"c3","text":"The SEC tokenized-securities staff statement says tokenized securities vary in structure and rights and can include issuer-sponsored and third-party models.","sourceIds":["sec-tokenized-statement"],"risk":"medium"},{"id":"c4","text":"The SEC tokenized-securities staff statement discusses models where transfer of the crypto asset may result in a transfer on the master securityholder file, making record mapping central.","sourceIds":["sec-tokenized-statement"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"address-poisoning-transfer-history-wallet-warning-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-22T02:44:00.289Z","updatedAt":"2026-09-22T02:44:00.289Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Address Poisoning Radar: Transfer History, Wallet Warnings and Stop Rules","zh-Hans":"地址投毒雷达：转账历史、钱包警告与停止规则"},"summary":{"en":"A source-mapped NexuAlpha decision brief for address poisoning transfer history wallet warning stop rules. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 地址投毒雷达：转账历史、钱包警告与停止规则 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"MetaMask describes address poisoning as attackers sending tiny or zero-value transactions from lookalike addresses so users may copy the wrong address later.","sourceIds":["metamask-address-poisoning"],"risk":"medium"},{"id":"c2","text":"MetaMask says users should pay attention to middle characters, avoid copying from transaction history, add frequently used addresses to contacts and use hardware-wallet confirmation.","sourceIds":["metamask-address-poisoning"],"risk":"medium"},{"id":"c3","text":"MetaMask security-alert guidance says warnings should lead users to double-check URLs or contract addresses, and malicious classifications mean users should not connect, sign or proceed.","sourceIds":["metamask-security-alerts"],"risk":"medium"},{"id":"c4","text":"Binance materials describe spoofed address generation, transaction-history poisoning, full-address verification, address-book use and small test transfers as mitigation controls.","sourceIds":["binance-address-poisoning-blog","binance-address-poisoning-academy"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-stablecoin-tokenisation-trust-in-money-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-22T02:44:00.289Z","updatedAt":"2026-09-22T02:44:00.289Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Stablecoin and Tokenisation Trust-in-Money Risk Map","zh-Hans":"BIS 稳定币与代币化信任风险地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for BIS stablecoin tokenisation trust in money risk map 2026. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 BIS 稳定币与代币化信任风险地图 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"BIS says stablecoins display some tokenisation potential for faster programmable payments but current designs fall short on properties that ensure trust in money, including singleness.","sourceIds":["bis-trust-money-release"],"risk":"medium"},{"id":"c2","text":"BIS Paper 170 says stablecoins are likely to affect private-sector store-of-value and medium-of-exchange roles especially in economies facing macroeconomic instability, and notes dollar-denominated dominance.","sourceIds":["bis-paper-170"],"risk":"medium"},{"id":"c3","text":"The BIS Annual Economic Report 2026 states that policy should address shortcomings in current stablecoin arrangements while also bringing tokenisation into a two-tier system anchored by central bank money.","sourceIds":["bis-aer-2026"],"risk":"medium"},{"id":"c4","text":"BIS Working Paper 1377 says simple on-chain aggregations can mix economic activity with technical artefacts, and identifies transaction aggregation, programmability and cross-chain comparability as measurement challenges.","sourceIds":["bis-working-paper-1377"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-register-deribit-complete-kyc-and-secure-first-login","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-22T02:44:00.289Z","updatedAt":"2026-09-22T02:44:00.289Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"How to Register on Deribit, Complete KYC and Secure First Login","zh-Hans":"如何注册 Deribit、完成 KYC 并保护首次登录"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to register on Deribit complete KYC secure first login. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 如何注册 Deribit、完成 KYC 并保护首次登录 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Deribit Support says users should use www.deribit.com for the production environment and can register with email, Google or Apple.","sourceIds":["deribit-register"],"risk":"medium"},{"id":"c2","text":"Deribit Support says 2FA setup is mandatory before accessing the account, and users must complete KYC verification.","sourceIds":["deribit-register","deribit-2fa"],"risk":"medium"},{"id":"c3","text":"Deribit login guidance says email login requires the registered email address and warns users never to share a client secret.","sourceIds":["deribit-login"],"risk":"medium"},{"id":"c4","text":"Deribit KYC guidance says individual verification requires identity and proof-of-residence documentation, with compliance review for specific source-of-funds issues.","sourceIds":["deribit-kyc-individual"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-vs-coinbase-passkey-security-key-recovery-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-22T02:44:00.289Z","updatedAt":"2026-09-22T02:44:00.289Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken vs Coinbase Passkey and Security-Key Recovery Controls","zh-Hans":"Kraken 与 Coinbase Passkey 和安全密钥恢复控制对比"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Kraken vs Coinbase passkey security key recovery controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Kraken 与 Coinbase Passkey 和安全密钥恢复控制对比 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Kraken Support says passkeys can be used to satisfy sign-in 2FA and are bound to a website or app identity to reduce phishing risk.","sourceIds":["kraken-passkey"],"risk":"medium"},{"id":"c2","text":"Kraken Support says users who cannot locate a passkey can begin account recovery from the Kraken sign-in page after entering email or username and password.","sourceIds":["kraken-passkey-troubleshooting"],"risk":"medium"},{"id":"c3","text":"Coinbase Help recommends passkeys or security keys for 2-step verification and describes a passkey plus security-key backup combination.","sourceIds":["coinbase-2-step"],"risk":"medium"},{"id":"c4","text":"Coinbase Help says trusted contacts can approve account recovery requests and recommends checking account records for unauthorized recovery emails or phone numbers.","sourceIds":["coinbase-2-step","coinbase-secure-account"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-usd-usdc-spot-order-book-migration-api-bot-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-22T02:44:00.289Z","updatedAt":"2026-09-22T02:44:00.289Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"OKX USD and USDC Spot Order Book Migration: API and Bot Checklist","zh-Hans":"OKX USD 与 USDC 现货订单簿迁移：API 与交易机器人清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for OKX USD USDC spot order book migration API bot checklist. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 OKX USD 与 USDC 现货订单簿迁移：API 与交易机器人清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"OKX says corresponding USDC spot pairs are scheduled to become available on September 23, 2026 and affected USD spot pairs, except USDT-USD, are scheduled for delisting on September 30, 2026.","sourceIds":["okx-usd-migration"],"risk":"medium"},{"id":"c2","text":"OKX says all open orders on affected USD pairs will be automatically canceled and strategy orders, trading bots and API programs using affected USD pairs will no longer be able to place orders after delisting.","sourceIds":["okx-usd-migration","okx-order-book-consolidation"],"risk":"medium"},{"id":"c3","text":"OKX says requests currently using a Crypto-USD instrument ID must use the corresponding Crypto-USDC instrument ID after the change, and tradeQuoteCcy may need to be explicitly set to USD.","sourceIds":["okx-usd-migration","okx-order-book-consolidation"],"risk":"medium"},{"id":"c4","text":"The OKX API changelog repeats the September 23 and September 30 migration dates and tells API clients to adapt instrument IDs, tradeQuoteCcy handling and WebSocket subscription logic.","sourceIds":["okx-api-log"],"risk":"medium"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"basel-sco60-cryptoasset-exposure-standard-bank-capital-implementation-map","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-21T23:42:09.751Z","updatedAt":"2026-09-21T23:42:09.751Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Basel SCO60 Cryptoasset Exposure Standard: Bank Capital Implementation Map","zh-Hans":"Basel SCO60 加密资产风险暴露标准：银行资本实施地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Basel SCO60 cryptoasset exposure standard bank capital implementation map. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Basel SCO60 加密资产风险暴露标准：银行资本实施地图 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"The BIS Basel Framework page for SCO60 says the cryptoasset exposures chapter is current and effective as of 1 January 2026.","sourceIds":["bis-sco60-current"],"risk":"medium"},{"id":"c2","text":"SCO60 sets out prudential treatment for banks' exposures to cryptoassets, including classification conditions, minimum capital requirements and liquidity risk requirements.","sourceIds":["bis-sco60-current"],"risk":"medium"},{"id":"c3","text":"The Basel Committee amendments page says targeted amendments to the cryptoasset prudential standard were finalized and the final revised standard was to be implemented by 1 January 2026.","sourceIds":["bis-cryptoasset-amendments"],"risk":"medium"},{"id":"c4","text":"The original prudential treatment document and jurisdictional consultation material provide implementation context but do not prove any specific bank product is approved for a user.","sourceIds":["bis-prudential-treatment-pdf","hkma-basel-crypto-consultation-annex"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-travel-rule-withdrawal-deposit-information-disclosure-radar","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-21T23:42:09.751Z","updatedAt":"2026-09-21T23:42:09.751Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Travel Rule Radar: Withdrawal and Deposit Information Disclosure","zh-Hans":"加密 Travel Rule 雷达：提现与充值信息披露"},"summary":{"en":"A source-mapped NexuAlpha decision brief for crypto Travel Rule withdrawal deposit information disclosure radar. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 加密 Travel Rule 雷达：提现与充值信息披露 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Binance Support says the Travel Rule can require VASPs to collect and transmit names and wallet addresses about originators and beneficiaries before or during transfers.","sourceIds":["binance-travel-rule"],"risk":"medium"},{"id":"c2","text":"Binance Support says affected users may need deposit or withdrawal questionnaires, and self-hosted wallet transfers may require a micro-transaction test.","sourceIds":["binance-travel-rule"],"risk":"medium"},{"id":"c3","text":"OKX Europe says regulated-region users may need to provide the beneficiary legal name, destination type and additional information, and deposits without Travel Rule messages may be locked until more information is provided.","sourceIds":["okx-eu-travel-rule"],"risk":"medium"},{"id":"c4","text":"Coinbase Europe and Kraken regional materials describe additional counterparty information requirements for transfers involving non-platform destinations or affected jurisdictions.","sourceIds":["coinbase-eu-travel-rule","kraken-uk-eu-transfer-procedures"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-use-uniswap-connect-wallet-and-make-first-swap-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-21T23:42:09.751Z","updatedAt":"2026-09-21T23:42:09.751Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"How to Use Uniswap: Connect a Wallet and Make a First Swap Safely","zh-Hans":"如何使用 Uniswap：安全连接钱包并完成首次 Swap"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to use Uniswap connect wallet first swap safely. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 如何使用 Uniswap：安全连接钱包并完成首次 Swap 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Uniswap support says users need a wallet and tokens before swapping, and can connect an external wallet to the Uniswap web app.","sourceIds":["uniswap-start"],"risk":"medium"},{"id":"c2","text":"Uniswap support says desktop or mobile users can connect a wallet, including through WalletConnect when the wallet is not listed.","sourceIds":["uniswap-connect-wallet"],"risk":"medium"},{"id":"c3","text":"Uniswap swap guidance says users select tokens, enter amount, review swap details, approve spending when required, sign a message and confirm the swap in the wallet.","sourceIds":["uniswap-swap-web-app"],"risk":"medium"},{"id":"c4","text":"Uniswap swap-screen guidance lists fields such as fee, network cost, order routing, price impact and max slippage as items visible in the swap interface.","sourceIds":["uniswap-swap-screen"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-vs-coinbase-api-key-permission-ip-whitelist-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-21T23:42:09.751Z","updatedAt":"2026-09-21T23:42:09.751Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken vs Coinbase API Key Permission and IP Whitelist Controls","zh-Hans":"Kraken 与 Coinbase API Key 权限和 IP 白名单控制对比"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Kraken vs Coinbase API key permission IP whitelist controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Kraken 与 Coinbase API Key 权限和 IP 白名单控制对比 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Kraken support says API key permissions determine which private endpoints a key can call, including funds, orders, ledger, export and WebSocket token access.","sourceIds":["kraken-create-spot-api-key"],"risk":"medium"},{"id":"c2","text":"Kraken support says IP whitelisting restricts API key use to specific client-side IP addresses and key expiration can make a key valid only for a specific time.","sourceIds":["kraken-create-spot-api-key"],"risk":"medium"},{"id":"c3","text":"Kraken organization guidance says API keys have their own permission model, can be mapped to selected accounts, and should use the narrowest permissions, fewest accounts and tightest IP restrictions.","sourceIds":["kraken-org-api-keys"],"risk":"medium"},{"id":"c4","text":"Coinbase Help says an IP address whitelist is a required field when creating an Exchange API key, and lists View, Transfer, Trade and Manage as permission categories.","sourceIds":["coinbase-create-api-key"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"swift-tokenised-deposit-ledger-24-7-cross-border-payment-readiness","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-21T23:42:09.751Z","updatedAt":"2026-09-21T23:42:09.751Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Swift Tokenised Deposit Ledger: 24/7 Cross-Border Payment Readiness","zh-Hans":"Swift 代币化存款账本：24/7 跨境支付准备度"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Swift tokenised deposit ledger 24/7 cross-border payment readiness. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Swift 代币化存款账本：24/7 跨境支付准备度 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Swift says its blockchain-based ledger is ready for initial use and that 17 banks from six continents are preparing to pilot live tokenised-deposit transactions.","sourceIds":["swift-ledger-ready-2026"],"risk":"medium"},{"id":"c2","text":"Swift says the shared ledger provides an orchestration layer for bank-issued tokenised deposits before final settlement through existing systems.","sourceIds":["swift-ledger-ready-2026"],"risk":"medium"},{"id":"c3","text":"Swift's earlier announcement said the ledger would extend Swift's financial communication role into digital ecosystems for regulated tokenised value.","sourceIds":["swift-ledger-2025"],"risk":"medium"},{"id":"c4","text":"ECB OMG materials describe a 2026 MVP using existing bank payment applications plus a digital layer built on the Swift Ledger and banks' tokenized deposits.","sourceIds":["ecb-omg-summary-swift-ledger"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-bybit-passkey-withdrawal-verification-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-21T20:40:55.553Z","updatedAt":"2026-09-21T20:40:55.553Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs Bybit Passkey Withdrawal Verification Controls","zh-Hans":"Binance 与 Bybit Passkey 提现验证控制对比"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Binance vs Bybit passkey withdrawal verification controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Binance 与 Bybit Passkey 提现验证控制对比 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Binance support says enabling 'Must verify using passkey' requires passkey verification for login and withdrawal.","sourceIds":["binance-passkey-required"],"risk":"medium"},{"id":"c2","text":"Binance support says withdrawal whitelist settings can restrict withdrawals to whitelisted addresses and may involve passkey or 2FA verification.","sourceIds":["binance-withdrawal-whitelist"],"risk":"medium"},{"id":"c3","text":"Bybit support describes Passkey 2.0 as a FIDO passkey using biometrics or a device-backed key pair, with up to 10 passkeys.","sourceIds":["bybit-passkey"],"risk":"medium"},{"id":"c4","text":"Bybit account-security guidance links passkeys, anti-phishing code, withdrawal locks and authenticity checks as separate account protection settings.","sourceIds":["bybit-account-security"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-transfer-protection-time-delay-verification-threshold-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-21T20:40:55.553Z","updatedAt":"2026-09-21T20:40:55.553Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Transfer Protection: Time Delay, Verification and Threshold Checklist","zh-Hans":"Coinbase Transfer Protection：延迟、验证与阈值清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Coinbase Transfer Protection time delay verification threshold checklist. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Coinbase Transfer Protection：延迟、验证与阈值清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Coinbase Help says Transfer Protection can add a delay, require verification, or both for outbound transactions.","sourceIds":["coinbase-transfer-protection"],"risk":"medium"},{"id":"c2","text":"Coinbase Help says Transfer Protection delay periods can be set between 6 and 48 hours and can apply above a daily threshold.","sourceIds":["coinbase-transfer-protection"],"risk":"medium"},{"id":"c3","text":"Coinbase Help lists trusted contacts, passkey, security key, authenticator app and push notifications as verification options.","sourceIds":["coinbase-transfer-protection"],"risk":"medium"},{"id":"c4","text":"Coinbase allowlist guidance says address allowlisting limits sends to address-book entries and can involve a 48-hour availability window for new addresses.","sourceIds":["coinbase-allowlist","coinbase-exchange-whitelist"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-anti-phishing-official-channel-verification-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-21T20:40:55.553Z","updatedAt":"2026-09-21T20:40:55.553Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange Anti-Phishing Radar: Official Channel Verification Controls","zh-Hans":"加密交易所反钓鱼雷达：官方渠道核验控制"},"summary":{"en":"A source-mapped NexuAlpha decision brief for crypto exchange anti-phishing official channel verification controls radar. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 加密交易所反钓鱼雷达：官方渠道核验控制 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Bybit guidance describes checking sender information with its Authenticity Checker and warns that sender addresses can still be forged.","sourceIds":["bybit-phishing"],"risk":"medium"},{"id":"c2","text":"Bitget guidance describes using its Official Verification Tool and reporting suspicious or unofficial links from the verification result page.","sourceIds":["bitget-official-verification"],"risk":"medium"},{"id":"c3","text":"KuCoin phishing guidance references official media verification, certificate checks and anti-phishing safety phrases as user-protection measures.","sourceIds":["kucoin-phishing-faq"],"risk":"medium"},{"id":"c4","text":"Binance account-security guidance says anti-phishing codes appear in genuine Binance emails and withdrawal whitelists restrict withdrawals to whitelisted addresses.","sourceIds":["binance-account-security"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-tokenization-service-eligible-networks-wallet-registration-controls","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-21T20:40:55.553Z","updatedAt":"2026-09-21T20:40:55.553Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Tokenization Service: Eligible Networks and Wallet Registration Controls","zh-Hans":"DTCC Tokenization Service：合格网络与钱包登记控制"},"summary":{"en":"A source-mapped NexuAlpha decision brief for DTCC Tokenization Service eligible networks wallet registration controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 DTCC Tokenization Service：合格网络与钱包登记控制 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"DTCC says DTC-issued tokens are designed to represent the same legal rights, economic interest and investor protections associated with the underlying securities.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c2","text":"DTCC says tokenized DTC assets can move between traditional and blockchain ecosystems using the same CUSIP across approved networks.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c3","text":"DTCC describes controls such as mint, burn, pause and clawback functionality plus near real-time ownership tracking across traditional and blockchain ledgers.","sourceIds":["dtcc-tokenization-service"],"risk":"medium"},{"id":"c4","text":"The DTC Tokenization Service FAQ says current DTC participants need to register digital wallets for each blockchain in which they wish to receive tokenized assets.","sourceIds":["dtcc-faq"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-bybit-anti-phishing-code-and-authenticity-check","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-21T20:40:55.553Z","updatedAt":"2026-09-21T20:40:55.553Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up Bybit Anti-Phishing Code and Authenticity Check","zh-Hans":"如何设置 Bybit 反钓鱼代码并使用 Authenticity Check"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to set up Bybit anti-phishing code authenticity check. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 如何设置 Bybit 反钓鱼代码并使用 Authenticity Check 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Bybit setup guidance says an anti-phishing code is a unique code displayed in official Bybit emails and SMS messages after setup.","sourceIds":["bybit-anti-phishing-setup"],"risk":"medium"},{"id":"c2","text":"Bybit scam guidance says users should verify sender details with Authenticity Checker and remain cautious because sender addresses can be forged.","sourceIds":["bybit-phishing"],"risk":"medium"},{"id":"c3","text":"Bybit Protect guidance says users should check anti-phishing codes in emails or SMS and use Bybit Authenticity Check to verify URLs and sources.","sourceIds":["bybit-protect"],"risk":"medium"},{"id":"c4","text":"Bybit account-security guidance lists anti-phishing code, passkey, new-address withdrawal lock and authenticity check as distinct security settings.","sourceIds":["bybit-account-security"],"risk":"medium"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-coinbase-account-statement-tax-report-export-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-21T17:43:04.992Z","updatedAt":"2026-09-21T17:43:04.992Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs Coinbase Account Statements: Tax Report Export Controls","zh-Hans":"Binance 与 Coinbase 账户报表：税务导出控制对比"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Binance vs Coinbase account statement tax report export controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Binance 与 Coinbase 账户报表：税务导出控制对比 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Binance support describes generating and exporting account statements, including PDF delivery options.","sourceIds":["binance-account-statement"],"risk":"medium"},{"id":"c2","text":"Binance support describes exporting transaction records from the asset-history surface for selected time ranges.","sourceIds":["binance-transaction-history"],"risk":"medium"},{"id":"c3","text":"Coinbase help describes downloading or generating statements and reports from the Statements page.","sourceIds":["coinbase-statements"],"risk":"medium"},{"id":"c4","text":"Coinbase help says tax reports can include gain-loss summaries and raw transaction history through Coinbase Taxes.","sourceIds":["coinbase-tax-report"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"blackrock-onchain-shares-official-register-vs-wallet-token-recordkeeping-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-21T17:43:04.992Z","updatedAt":"2026-09-21T17:43:04.992Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"BlackRock OnChain Shares: Official Register vs Wallet Token Map","zh-Hans":"BlackRock OnChain Shares：官方登记簿与钱包代币映射"},"summary":{"en":"A source-mapped NexuAlpha decision brief for BlackRock OnChain Shares official register wallet token recordkeeping map. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 BlackRock OnChain Shares：官方登记簿与钱包代币映射 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"BlackRock describes tokenized money market funds as traditional money market funds whose shares are issued and represented as digital tokens on a blockchain.","sourceIds":["blackrock-tokenized-mmfs"],"risk":"medium"},{"id":"c2","text":"BlackRock's product material says the fund invests in cash, U.S. Treasury bills, notes and other short-term Treasury obligations plus secured overnight repurchase agreements.","sourceIds":["blackrock-product"],"risk":"medium"},{"id":"c3","text":"The BlackRock prospectus describes OnChain Shares digitally represented on supported blockchains and tied to offchain wallet-address and shareholder information.","sourceIds":["blackrock-prospectus"],"risk":"medium"},{"id":"c4","text":"SEC staff material distinguishes issuer-sponsored, custodial and synthetic tokenized-security models and warns that recordkeeping architecture affects rights analysis.","sourceIds":["sec-tokenized-securities"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-kucoin-anti-phishing-safety-phrase-and-official-media-check","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-21T17:43:04.992Z","updatedAt":"2026-09-21T17:43:04.992Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up KuCoin Anti-Phishing Safety Phrase and Official Media Checks","zh-Hans":"如何设置 KuCoin 反钓鱼安全短语并核验官方媒体"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to set up KuCoin anti-phishing safety phrase official media check. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 如何设置 KuCoin 反钓鱼安全短语并核验官方媒体 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"KuCoin support recommends setting a security anti-phishing code to help avoid phishing emails and phishing websites.","sourceIds":["kucoin-safety-phrase"],"risk":"medium"},{"id":"c2","text":"KuCoin support says the safety code should display in KuCoin email or the login window and that the user should not proceed if it is missing or incorrect.","sourceIds":["kucoin-safety-phrase"],"risk":"medium"},{"id":"c3","text":"KuCoin phishing guidance references official media verification, certificate checks and anti-phishing safety phrases as user-protection measures.","sourceIds":["kucoin-phishing-faq"],"risk":"medium"},{"id":"c4","text":"A safety phrase does not prove account eligibility, regional availability, asset support, withdrawal availability or recovery success.","sourceIds":["kucoin-safety-phrase","kucoin-phishing-faq"],"risk":"medium"}],"relatedVenues":["kucoin"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-api-key-expiry-ip-binding-permission-review-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-21T17:43:04.992Z","updatedAt":"2026-09-21T17:43:04.992Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"OKX API Key Expiry: IP Binding and Permission Review Checklist","zh-Hans":"OKX API Key 到期：IP 绑定与权限复核清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for OKX API key expiry IP binding permission review checklist. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 OKX API Key 到期：IP 绑定与权限复核清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"OKX API FAQ says API keys without IP binding and with transaction or withdrawal permissions are automatically deleted after 14 days of inactivity.","sourceIds":["okx-api-faq"],"risk":"medium"},{"id":"c2","text":"OKX API guide states that API keys not linked to an IP address and carrying trade or withdraw permissions expire after 14 days of inactivity.","sourceIds":["okx-api-docs"],"risk":"medium"},{"id":"c3","text":"OKX third-party-app guidance describes creating API keys with server IP whitelisting when brokers support the feature.","sourceIds":["okx-ip-whitelist"],"risk":"medium"},{"id":"c4","text":"OKX Fast API guidance describes OAuth-style authorization that can generate API keys automatically for supported broker flows.","sourceIds":["okx-fast-api"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"stablecoin-reserve-attestation-frequency-disclosure-radar","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-21T17:43:04.992Z","updatedAt":"2026-09-21T17:43:04.992Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"Stablecoin Reserve Attestation Radar: Frequency and Disclosure Scope","zh-Hans":"稳定币储备证明雷达：频率与披露范围"},"summary":{"en":"A source-mapped NexuAlpha decision brief for stablecoin reserve attestation frequency disclosure scope radar. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 稳定币储备证明雷达：频率与披露范围 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Circle says USDC reserve holdings are disclosed weekly and that a Big Four accounting firm provides monthly third-party assurance.","sourceIds":["circle-transparency"],"risk":"medium"},{"id":"c2","text":"Paxos says it publishes monthly reserve reports on Paxos-issued digital assets including PYUSD.","sourceIds":["paxos-pyusd"],"risk":"medium"},{"id":"c3","text":"Ripple says RLUSD reserve reports are provided monthly by an independent third-party accounting firm.","sourceIds":["ripple-rlusd"],"risk":"medium"},{"id":"c4","text":"Tether says reserve reports are published for transparency purposes on a quarterly basis.","sourceIds":["tether-transparency"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-kraken-api-auth-timestamp-nonce-replay-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-21T11:52:51.503Z","updatedAt":"2026-09-21T11:52:51.503Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs Kraken API Auth: Timestamp, Nonce and Replay Controls","zh-Hans":"Binance 与 Kraken API 认证：时间戳、nonce 与重放控制"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Binance vs Kraken API authentication timestamp nonce replay controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Binance 与 Kraken API 认证：时间戳、nonce 与重放控制 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Binance developer documentation describes signed requests as requiring a timestamp and allowing recvWindow to bound request validity.","sourceIds":["binance-rest"],"risk":"medium"},{"id":"c2","text":"Kraken developer documentation shows authenticated private requests using API-Key and API-Sign headers with a nonce in the submitted payload.","sourceIds":["kraken-dev"],"risk":"medium"},{"id":"c3","text":"Kraken support describes a nonce as a number that uniquely identifies each call to private REST API endpoints.","sourceIds":["kraken-nonce"],"risk":"medium"},{"id":"c4","text":"The two models create different failure modes: Binance clients must control clock drift and windowing, while Kraken clients must control monotonic nonce generation and replay after retry.","sourceIds":["binance-rest","kraken-dev","kraken-nonce"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cftc-sec-harmonization-crypto-market-structure-operational-watch","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-21T11:52:51.503Z","updatedAt":"2026-09-21T11:52:51.503Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC-SEC Harmonization Watch: Crypto Market Structure Operating Boundary","zh-Hans":"CFTC-SEC 协调观察：加密市场结构操作边界"},"summary":{"en":"A source-mapped NexuAlpha decision brief for CFTC SEC harmonization crypto market structure operating boundary. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 CFTC-SEC 协调观察：加密市场结构操作边界 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"The CFTC homepage includes a CFTC-SEC Harmonization feature describing coordination to reduce duplicative regulation and improve market clarity.","sourceIds":["cftc-home"],"risk":"medium"},{"id":"c2","text":"CFTC public material includes references to a joint SEC-CFTC harmonization event and Project Crypto in 2026 public remarks.","sourceIds":["cftc-fia-remarks"],"risk":"medium"},{"id":"c3","text":"The SEC homepage links to a Crypto Task Force surface and rulemaking activity from its public quick links.","sourceIds":["sec-home"],"risk":"medium"},{"id":"c4","text":"Agency coordination signals do not by themselves define account eligibility, product registration status, clearing access, custody treatment, margin handling or retail customer protections for a specific crypto product.","sourceIds":["cftc-home","sec-home"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-tokenized-assets-vs-nyse-tokenized-securities-rule-filing-rights-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-21T11:52:51.503Z","updatedAt":"2026-09-21T11:52:51.503Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Tokenized Assets vs NYSE Tokenized Securities Filing: Rights Map","zh-Hans":"DTCC 代币化资产与 NYSE 代币化证券备案：权利地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for DTCC tokenized assets vs NYSE tokenized securities rights map. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 DTCC 代币化资产与 NYSE 代币化证券备案：权利地图 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"DTCC announced that assets held at DTC were converted into tokens and used in real production trades on July 15, 2026.","sourceIds":["dtcc-tokenized-trades"],"risk":"medium"},{"id":"c2","text":"DTCC says more than 30 firms participated and that the milestone was ahead of a planned October 2026 DTCC Tokenization Service launch.","sourceIds":["dtcc-tokenized-trades"],"risk":"medium"},{"id":"c3","text":"The SEC page for SR-NYSE-2026-17 identifies a notice of filing and immediate effectiveness for a proposed rule change to enable trading of securities on NYSE in tokenized form.","sourceIds":["sec-nyse-filing"],"risk":"medium"},{"id":"c4","text":"The SEC page lists Release No. 34-105260, an April 17, 2026 issue date and a May 13, 2026 public-comment due date for the NYSE tokenized-securities filing.","sourceIds":["sec-nyse-filing"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-proof-of-reserves-liability-scope-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-21T11:52:51.503Z","updatedAt":"2026-09-21T11:52:51.503Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange Proof-of-Reserves Radar: Liability Scope and Disclosure Gaps","zh-Hans":"交易所储备证明雷达：负债范围与披露空白"},"summary":{"en":"A source-mapped NexuAlpha decision brief for crypto exchange proof of reserves liability scope disclosure radar. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 交易所储备证明雷达：负债范围与披露空白 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Binance maintains an official proof-of-reserves page as a user-facing reserve disclosure surface.","sourceIds":["binance-por"],"risk":"medium"},{"id":"c2","text":"Kraken maintains an official proof-of-reserves page that frames PoR as allowing clients to verify crypto balances held on the exchange are backed by assets in custody.","sourceIds":["kraken-por"],"risk":"medium"},{"id":"c3","text":"OKX maintains an official proof-of-reserves page and supporting materials around reserve verification.","sourceIds":["okx-por"],"risk":"medium"},{"id":"c4","text":"Coinbase educational material describes Proof of Reserves as a verification method showing a platform's ability to maintain users' digital assets, but education alone is not a live exchange solvency audit.","sourceIds":["coinbase-por-education"],"risk":"medium"}],"relatedVenues":["binance","kraken","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-binance-authenticator-2fa-scenario-controls-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-21T11:52:51.503Z","updatedAt":"2026-09-21T11:52:51.503Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up Binance Authenticator 2FA Scenario Controls Safely","zh-Hans":"如何安全设置 Binance Authenticator 与 2FA 场景控制"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to set up Binance Authenticator 2FA scenario controls safely. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 如何安全设置 Binance Authenticator 与 2FA 场景控制 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Binance support material describes using BAuthenticator as an account 2FA method inside the Binance app.","sourceIds":["binance-authenticator"],"risk":"medium"},{"id":"c2","text":"Binance support material describes scenario-based 2FA verification controls as account security settings rather than a trading signal.","sourceIds":["binance-2fa-scenarios"],"risk":"medium"},{"id":"c3","text":"Binance Verify is the official Binance surface for checking whether a source, link, email, phone number, WeChat or other contact is represented as official.","sourceIds":["binance-verify"],"risk":"medium"},{"id":"c4","text":"A successful 2FA setup does not prove trading eligibility, product availability, region support, withdrawal availability or account recovery success.","sourceIds":["binance-authenticator","binance-2fa-scenarios"],"risk":"medium"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-hidden-complexity-defi-data-measurement-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-21T08:43:24.237Z","updatedAt":"2026-09-21T08:43:24.237Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Hidden Complexity Study: DeFi Data Measurement Risk Map","zh-Hans":"BIS Hidden Complexity 研究：DeFi 数据度量风险地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for BIS Hidden by complexity DeFi data measurement risk map. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 BIS Hidden Complexity 研究：DeFi 数据度量风险地图 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"BIS Working Paper No. 1377 was published on September 15, 2026 and focuses on measuring stablecoin, crypto and DeFi ecosystems.","sourceIds":["bis-wp1377"],"risk":"medium"},{"id":"c2","text":"The BIS paper says common indicators can differ substantially depending on how blockchain data are treated.","sourceIds":["bis-wp1377"],"risk":"medium"},{"id":"c3","text":"The BIS paper identifies transaction aggregation, smart-contract programmability and comparability across blockchains as sources of measurement divergence.","sourceIds":["bis-wp1377"],"risk":"medium"},{"id":"c4","text":"The BIS paper says on-chain indicators should be treated as noisy approximations rather than direct measures of economic activity.","sourceIds":["bis-wp1377"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-v5-api-rate-limit-header-retry-budget-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-21T08:43:24.237Z","updatedAt":"2026-09-21T08:43:24.237Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit V5 API Rate Limit Headers: Retry Budget Checklist","zh-Hans":"Bybit V5 API 限频响应头：重试预算清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Bybit V5 API rate limit headers retry budget checklist. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Bybit V5 API 限频响应头：重试预算清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Bybit documents a default HTTP IP limit of 600 requests within a five-second window per IP for traffic to api.bybit.com and local API hostnames.","sourceIds":["bybit-rate-limit"],"risk":"medium"},{"id":"c2","text":"Bybit says an access-too-frequent 403 response means the IP exceeded allowed request frequency and the application should terminate HTTP sessions and wait at least ten minutes.","sourceIds":["bybit-rate-limit"],"risk":"medium"},{"id":"c3","text":"Bybit documents WebSocket IP limits, including not establishing more than 500 connections within a five-minute window.","sourceIds":["bybit-rate-limit"],"risk":"medium"},{"id":"c4","text":"Bybit says endpoint API limits are based on a rolling one-second window per UID and exposes X-Bapi-Limit, X-Bapi-Limit-Status and X-Bapi-Limit-Reset-Timestamp headers.","sourceIds":["bybit-rate-limit"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fatf-stablecoins-unhosted-wallets-p2p-risk-mitigation-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-21T08:43:24.237Z","updatedAt":"2026-09-21T08:43:24.237Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"FATF Stablecoins and Unhosted Wallets: P2P Risk Mitigation Map","zh-Hans":"FATF 稳定币与非托管钱包：P2P 风险缓释地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for FATF stablecoins unhosted wallets P2P risk mitigation map. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 FATF 稳定币与非托管钱包：P2P 风险缓释地图 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"FATF published the seventh targeted update on July 16, 2026 to assess progress and remaining gaps in Recommendation 15 implementation.","sourceIds":["fatf-2026-update"],"risk":"medium"},{"id":"c2","text":"FATF says jurisdictions have continued making progress in risk assessments, regulatory approaches, licensing or registration, Travel Rule implementation, supervision and enforcement.","sourceIds":["fatf-2026-update"],"risk":"medium"},{"id":"c3","text":"FATF says significant gaps remain in translating risk assessments into mitigation, operationalising licensing or registration frameworks, identifying VASP activity and ensuring effective supervision and enforcement.","sourceIds":["fatf-2026-update"],"risk":"medium"},{"id":"c4","text":"FATF highlights emerging and increasing risks involving stablecoins, P2P transactions through unhosted wallets, offshore VASPs outside effective oversight and continuing DeFi challenges.","sourceIds":["fatf-2026-update","fatf-virtual-assets"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-api-kyc-order-tagged-rate-limit-migration-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-21T08:43:24.237Z","updatedAt":"2026-09-21T08:43:24.237Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"OKX API KYC and Order-Tagged Rate Limits: Migration Checklist","zh-Hans":"OKX API KYC 与订单标签限频：迁移清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for OKX API KYC order tagged rate limit migration checklist. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 OKX API KYC 与订单标签限频：迁移清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"OKX maintains an official V5 API documentation surface with an Upcoming Changes section for API behavior changes.","sourceIds":["okx-upcoming","okx-docs"],"risk":"medium"},{"id":"c2","text":"OKX API material describes REST and WebSocket API order access as surfaces that can be affected by eligibility and endpoint rules.","sourceIds":["okx-upcoming","okx-docs"],"risk":"medium"},{"id":"c3","text":"OKX API material describes rate limits as endpoint- or action-specific rather than a single universal budget.","sourceIds":["okx-docs"],"risk":"medium"},{"id":"c4","text":"OKX order-routing clients need a documented retry and fallback path because account state, tags and endpoint categories can affect throttling behavior.","sourceIds":["okx-upcoming","okx-docs"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-tokenized-nms-stock-amm-exemption-conditions-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-21T08:43:24.237Z","updatedAt":"2026-09-21T08:43:24.237Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Tokenized NMS Stock AMM Exemption: Conditions and Risk Map","zh-Hans":"SEC 代币化 NMS 股票 AMM 豁免：条件与风险地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for SEC tokenized NMS stock AMM exemption conditions risk map. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 SEC 代币化 NMS 股票 AMM 豁免：条件与风险地图 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"The SEC order is dated September 17, 2026 and is tied to Release No. 34-106402 and File No. 4-927.","sourceIds":["sec-order"],"risk":"medium"},{"id":"c2","text":"The order concerns temporary conditional exemptive relief for certain distributed-ledger trading venues for Tokenized NMS Stock and certain liquidity providers.","sourceIds":["sec-order"],"risk":"medium"},{"id":"c3","text":"The order describes Tokenized NMS Stock separately from synthetic exposure instruments such as tokenized linked securities or tokenized security-based swaps.","sourceIds":["sec-order","sec-tokenized-statement"],"risk":"medium"},{"id":"c4","text":"The order includes conditions concerning verified or credentialed users, books and records, public notices and prohibitions on stating that the venue is SEC registered, approved or endorsed.","sourceIds":["sec-order"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-withdrawal-whitelist-vs-kraken-address-confirmation-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-21T05:45:28.520Z","updatedAt":"2026-09-21T05:45:28.520Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Withdrawal Whitelist vs Kraken Address Confirmation: Control Checklist","zh-Hans":"Binance 提现白名单与 Kraken 地址确认：控制清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Binance withdrawal whitelist vs Kraken address confirmation controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Binance 提现白名单与 Kraken 地址确认：控制清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Binance Support says enabling the withdrawal whitelist means the account can only withdraw to addresses on the whitelist.","sourceIds":["binance-withdrawal-settings"],"risk":"medium"},{"id":"c2","text":"Binance Support says modifying the withdrawal whitelist may lead to temporary withdrawal suspension for 24, 48 or 72 hours.","sourceIds":["binance-withdrawal-settings"],"risk":"medium"},{"id":"c3","text":"Binance Support suggests sending a small amount first when withdrawing to an entered address for the first time.","sourceIds":["binance-withdraw-crypto"],"risk":"medium"},{"id":"c4","text":"Kraken Support says a user can add and confirm a new withdrawal address when no address exists for the selected crypto.","sourceIds":["kraken-withdraw-crypto"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-advanced-trade-websocket-user-feed-failover-rate-limit-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-21T05:45:28.520Z","updatedAt":"2026-09-21T05:45:28.520Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Advanced Trade WebSocket User Feed: Failover and Rate-Limit Checklist","zh-Hans":"Coinbase Advanced Trade WebSocket 用户流：故障转移与限频清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Coinbase Advanced Trade WebSocket user feed failover rate limit checklist. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Coinbase Advanced Trade WebSocket 用户流：故障转移与限频清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Coinbase documents Advanced Trade as a REST and WebSocket API for programmatic trading and order management.","sourceIds":["coinbase-advanced-overview"],"risk":"medium"},{"id":"c2","text":"Coinbase documents two production WebSocket endpoints: market data and user order data.","sourceIds":["coinbase-ws-overview"],"risk":"medium"},{"id":"c3","text":"Coinbase says that if advanced-trade-ws-user is the primary connection, advanced-trade-ws is recommended as a failover.","sourceIds":["coinbase-ws-overview"],"risk":"medium"},{"id":"c4","text":"Coinbase documents WebSocket rate limits for connections and unauthenticated messages.","sourceIds":["coinbase-ws-rate-limits"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-withdrawal-address-whitelist-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-21T05:45:28.520Z","updatedAt":"2026-09-21T05:45:28.520Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange Withdrawal Address Whitelist Disclosure Radar","zh-Hans":"加密交易所提现地址白名单披露雷达"},"summary":{"en":"A source-mapped NexuAlpha decision brief for crypto exchange withdrawal address whitelist disclosure radar. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 加密交易所提现地址白名单披露雷达 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Binance discloses whitelist-only withdrawal behavior when the withdrawal whitelist is enabled.","sourceIds":["binance-withdrawal-settings"],"risk":"medium"},{"id":"c2","text":"OKX Help says allowlist enhances withdrawal security and only permits withdrawals to addresses saved in the address book when enabled.","sourceIds":["okx-allowlist-web"],"risk":"medium"},{"id":"c3","text":"OKX Help says the new address withdrawal lock can prevent withdrawals for 24 hours to newly added allowlist addresses.","sourceIds":["okx-allowlist-app"],"risk":"medium"},{"id":"c4","text":"Kraken Support describes adding and confirming a new withdrawal address before use.","sourceIds":["kraken-withdraw-crypto"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"hkma-project-ensemble-tokenised-deposit-settlement-sandbox-risk-map","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-21T05:45:28.520Z","updatedAt":"2026-09-21T05:45:28.520Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"HKMA Project Ensemble Tokenised Deposit Settlement: Sandbox Risk Map","zh-Hans":"HKMA Project Ensemble 代币化存款结算：沙盒风险地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for HKMA Project Ensemble tokenised deposit settlement sandbox risk map. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 HKMA Project Ensemble 代币化存款结算：沙盒风险地图 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"HKMA announced Project Ensemble in March 2024 to support tokenisation market development.","sourceIds":["hkma-ensemble-launch"],"risk":"medium"},{"id":"c2","text":"HKMA said the project initially focused on tokenised deposits issued by commercial banks.","sourceIds":["hkma-ensemble-launch"],"risk":"medium"},{"id":"c3","text":"HKMA launched the Project Ensemble Sandbox in August 2024 to facilitate interbank settlement using experimental tokenised money.","sourceIds":["hkma-ensemble-sandbox"],"risk":"medium"},{"id":"c4","text":"HKMA's CBDC page describes the sandbox as further research and testing of tokenisation use cases, including settlement of tokenised assets.","sourceIds":["hkma-cbdc-page"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-enable-binance-withdrawal-whitelist-address-limit-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-21T05:45:28.520Z","updatedAt":"2026-09-21T05:45:28.520Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"How to Enable Binance Withdrawal Whitelist and Address Limit Safely","zh-Hans":"如何安全启用 Binance 提现白名单与地址限制"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to enable Binance withdrawal whitelist address limit safely. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 如何安全启用 Binance 提现白名单与地址限制 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Binance Support says the withdrawal whitelist can be enabled from Settings under Withdrawal.","sourceIds":["binance-withdrawal-settings"],"risk":"medium"},{"id":"c2","text":"Binance Support says enabling the withdrawal whitelist restricts withdrawals to whitelisted addresses.","sourceIds":["binance-withdrawal-settings"],"risk":"medium"},{"id":"c3","text":"Binance Support says the whitelist withdrawal limit can suspend withdrawals to newly added whitelist addresses for a selected time period.","sourceIds":["binance-withdrawal-settings"],"risk":"medium"},{"id":"c4","text":"Binance withdrawal guidance says users should check the withdrawal address and network carefully before confirming because wrong information can permanently lose assets.","sourceIds":["binance-withdraw-crypto"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-vs-okx-self-trade-prevention-order-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-21T02:42:19.006Z","updatedAt":"2026-09-21T02:42:19.006Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase vs OKX Self-Trade Prevention: Order-Control Decision Checklist","zh-Hans":"Coinbase 与 OKX 自成交防护：订单控制决策清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Coinbase vs OKX self-trade prevention order controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Coinbase 与 OKX 自成交防护：订单控制决策清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Coinbase Exchange documentation says self-trading is not allowed and the STP instruction on the taker order takes precedence over the older resting order.","sourceIds":["coinbase-matching-engine"],"risk":"medium"},{"id":"c2","text":"Coinbase lists STP flags for decrement and cancel, cancel oldest, cancel newest and cancel both.","sourceIds":["coinbase-matching-engine"],"risk":"medium"},{"id":"c3","text":"Coinbase WebSocket documentation says STP can trigger change messages and authenticated done messages can include a cancel_reason for self-trade prevention.","sourceIds":["coinbase-websocket-channels"],"risk":"medium"},{"id":"c4","text":"OKX API documentation describes STP modes including cancel maker and cancel taker, so the venue-specific order-side consequence must be recorded before automation relies on it.","sourceIds":["okx-stp-overview"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cpmi-iosco-fmi-cyber-resilience-tokenized-settlement-third-party-controls","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-21T02:42:19.006Z","updatedAt":"2026-09-21T02:42:19.006Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"CPMI-IOSCO FMI Cyber Resilience for Tokenized Settlement: Third-Party Control Map","zh-Hans":"CPMI-IOSCO 金融市场基础设施网络韧性：代币化结算第三方控制地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for CPMI IOSCO FMI cyber resilience tokenized settlement third party controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 CPMI-IOSCO 金融市场基础设施网络韧性：代币化结算第三方控制地图 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"CPMI-IOSCO published a consultative report on cyber resilience practical considerations for financial market infrastructures on 8 September 2026.","sourceIds":["cpmi-iosco-cyber-toolkit"],"risk":"medium"},{"id":"c2","text":"CPMI-IOSCO published a discussion paper on FMIs' reliance on third-party service providers on 8 September 2026.","sourceIds":["cpmi-iosco-third-party"],"risk":"medium"},{"id":"c3","text":"BIS Project Agorá is framed as work on tokenisation and programmable technologies for wholesale cross-border payments.","sourceIds":["bis-project-agora"],"risk":"medium"},{"id":"c4","text":"A tokenized settlement claim is incomplete unless cyber resilience and third-party dependency controls are mapped alongside the asset or payment workflow.","sourceIds":["cpmi-iosco-cyber-toolkit","cpmi-iosco-third-party","bis-project-agora"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-enable-kraken-trading-funding-2fa-global-settings-lock-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-21T02:42:19.006Z","updatedAt":"2026-09-21T02:42:19.006Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"How to Enable Kraken Trading and Funding 2FA with Global Settings Lock Safely","zh-Hans":"如何安全启用 Kraken 交易与资金 2FA 及 Global Settings Lock"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to enable Kraken trading funding 2FA Global Settings Lock safely. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 如何安全启用 Kraken 交易与资金 2FA 及 Global Settings Lock 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Kraken publishes support material explaining 2FA for trading.","sourceIds":["kraken-trading-2fa"],"risk":"medium"},{"id":"c2","text":"Kraken publishes support material explaining 2FA for funding deposits and withdrawals.","sourceIds":["kraken-funding-2fa"],"risk":"medium"},{"id":"c3","text":"Kraken Support says the Global Settings Lock acts as a last line of defense if sign-in password and sign-in 2FA are compromised.","sourceIds":["kraken-gsl"],"risk":"medium"},{"id":"c4","text":"Kraken's account security guidance recommends sign-in 2FA, a Master Key, Global Settings Lock and 2FA for withdrawals, trading and API.","sourceIds":["kraken-secure-account"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-api-upcoming-changes-websocket-amend-cancel-order-controls","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-21T02:42:19.006Z","updatedAt":"2026-09-21T02:42:19.006Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"OKX API Upcoming Changes: WebSocket Amend and Cancel Order Control Checklist","zh-Hans":"OKX API 即将变更：WebSocket 改单与撤单控制清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for OKX API upcoming changes WebSocket amend cancel order controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 OKX API 即将变更：WebSocket 改单与撤单控制清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"OKX maintains an official upcoming-changes API page for changes that may affect trading clients.","sourceIds":["okx-upcoming-changes"],"risk":"medium"},{"id":"c2","text":"OKX documents WebSocket amend-order behavior as an order-book trading endpoint.","sourceIds":["okx-amend-order"],"risk":"medium"},{"id":"c3","text":"OKX documents WebSocket cancel-order behavior as an order-book trading endpoint.","sourceIds":["okx-cancel-order"],"risk":"medium"},{"id":"c4","text":"An amend/cancel migration remains unsafe until the client can reconcile the accepted, rejected, canceled and replaced states without exposing credentials or sending duplicate actions.","sourceIds":["okx-upcoming-changes","okx-amend-order","okx-cancel-order"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"onchain-activity-measurement-radar-stablecoin-defi-data-assumption-controls","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-21T02:42:19.006Z","updatedAt":"2026-09-21T02:42:19.006Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"Onchain Activity Measurement Radar: Stablecoin and DeFi Data Assumption Controls","zh-Hans":"链上活动测量雷达：稳定币与 DeFi 数据假设控制"},"summary":{"en":"A source-mapped NexuAlpha decision brief for onchain activity measurement radar stablecoin DeFi data assumption controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 链上活动测量雷达：稳定币与 DeFi 数据假设控制 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"BIS Working Paper 1377 was published on 15 September 2026 and focuses on measuring stablecoin, crypto and DeFi ecosystems.","sourceIds":["bis-wp-1377"],"risk":"medium"},{"id":"c2","text":"The BIS page says widely used indicators of DeFi activity depend on methodological choices and underlying assumptions.","sourceIds":["bis-wp-1377"],"risk":"medium"},{"id":"c3","text":"The BIS page says Bitcoin transaction values can vary by up to a factor of six across measurement approaches.","sourceIds":["bis-wp-1377"],"risk":"medium"},{"id":"c4","text":"The BIS page says onchain indicators should be treated as noisy approximations rather than direct measures of economic activity.","sourceIds":["bis-wp-1377"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-stablecoin-reserve-spillover-vs-tokenised-deposit-trust-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-20T23:43:37.711Z","updatedAt":"2026-09-20T23:43:37.711Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Stablecoin Reserve Spillover vs Tokenised Deposit Trust Map","zh-Hans":"BIS 稳定币储备外溢与代币化存款信任地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for BIS stablecoin reserve spillover vs tokenised deposit trust map. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 BIS 稳定币储备外溢与代币化存款信任地图 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"BIS Papers No 170 analyzes stablecoins' impact on the international monetary and financial system and focuses on widespread use, EMDE exposure and international currency functions.","sourceIds":["bis-paper-170"],"risk":"medium"},{"id":"c2","text":"The BIS 2026 chapter says stablecoins show tokenisation potential but current designs fall short on foundational money properties and threaten financial integrity.","sourceIds":["bis-aer-2026"],"risk":"medium"},{"id":"c3","text":"The BIS speech contrasts stablecoins with tokenised deposits through singleness, interoperability and integrity.","sourceIds":["bis-stablecoins-deposits-speech"],"risk":"medium"},{"id":"c4","text":"The BIS speech says stablecoin reserve composition affects channels of risk contagion and tokenised deposits operate within the two-tier system.","sourceIds":["bis-stablecoins-deposits-speech"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-token-bucket-vs-kraken-trading-rate-limit-counter-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-20T23:43:37.711Z","updatedAt":"2026-09-20T23:43:37.711Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Token Bucket vs Kraken Trading Rate-Limit Counter: Order-Control Checklist","zh-Hans":"Coinbase Token Bucket 与 Kraken 交易限频计数器：订单控制清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Coinbase token bucket vs Kraken trading rate limit counter controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Coinbase Token Bucket 与 Kraken 交易限频计数器：订单控制清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Coinbase Exchange documentation describes REST, FIX and WebSocket rate limits and says Exchange REST and FIX rate limiting use a lazy-fill token bucket implementation.","sourceIds":["coinbase-rate-limits"],"risk":"medium"},{"id":"c2","text":"Coinbase Exchange documentation lists separate public, private, FIX and WebSocket request ceilings plus an open-order maximum.","sourceIds":["coinbase-rate-limits"],"risk":"medium"},{"id":"c3","text":"Kraken Support says trading rate limits apply separately per currency pair and can produce an EOrder:Rate limit exceeded error.","sourceIds":["kraken-trading-rate-limits"],"risk":"medium"},{"id":"c4","text":"Kraken Support describes a counter that increases as orders are placed and cancelled and decreases over time at a fixed decay rate.","sourceIds":["kraken-trading-rate-limits"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-withdrawal-address-lifecycle-disclosure-radar-confirm-delete-hold-controls","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-20T23:43:37.711Z","updatedAt":"2026-09-20T23:43:37.711Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Withdrawal Address Lifecycle Disclosure Radar: Confirm, Delete and Hold Controls","zh-Hans":"加密提现地址生命周期披露雷达：确认、删除与冻结控制"},"summary":{"en":"A source-mapped NexuAlpha decision brief for crypto withdrawal address lifecycle disclosure radar confirm delete hold controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 加密提现地址生命周期披露雷达：确认、删除与冻结控制 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Kraken publishes support material for adding and confirming a cryptocurrency withdrawal address.","sourceIds":["kraken-add-address"],"risk":"medium"},{"id":"c2","text":"Kraken publishes support material for preventing unwanted withdrawals.","sourceIds":["kraken-prevent-withdrawals"],"risk":"medium"},{"id":"c3","text":"Coinbase Help search currently exposes an address whitelisting concept that limits crypto withdrawals to verified addresses stored in the Address Book.","sourceIds":["coinbase-allowlisting"],"risk":"medium"},{"id":"c4","text":"A reusable withdrawal address is not proven safe unless the user can also identify deletion, hold, lock and recovery behavior.","sourceIds":["kraken-add-address","kraken-prevent-withdrawals","coinbase-allowlisting"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-add-kraken-withdrawal-address-confirm-delete-and-test-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-20T23:43:37.711Z","updatedAt":"2026-09-20T23:43:37.711Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"How to Add a Kraken Withdrawal Address: Confirm, Delete and Test Safely","zh-Hans":"如何添加 Kraken 提现地址：安全确认、删除与测试"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to add Kraken withdrawal address confirm delete and test safely. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 如何添加 Kraken 提现地址：安全确认、删除与测试 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Kraken publishes a support article for adding and confirming a cryptocurrency withdrawal address.","sourceIds":["kraken-add-address"],"risk":"medium"},{"id":"c2","text":"Kraken publishes a support article for deleting a withdrawal address from an account.","sourceIds":["kraken-delete-address"],"risk":"medium"},{"id":"c3","text":"Kraken publishes support material for preventing unwanted withdrawals.","sourceIds":["kraken-prevent-withdrawals"],"risk":"medium"},{"id":"c4","text":"Kraken publishes funding 2FA support material for deposits and withdrawals.","sourceIds":["kraken-funding-2fa"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"iosco-tokenization-financial-assets-investor-protection-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-20T23:43:37.711Z","updatedAt":"2026-09-20T23:43:37.711Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"IOSCO Tokenization of Financial Assets: Investor-Protection Risk Map","zh-Hans":"IOSCO 金融资产代币化：投资者保护风险地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for IOSCO tokenization financial assets investor protection risk map. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 IOSCO 金融资产代币化：投资者保护风险地图 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"IOSCO describes tokenization of financial assets through potential implications for market integrity and investor protection.","sourceIds":["iosco-tokenization"],"risk":"medium"},{"id":"c2","text":"BIS tokenisation material says token arrangements can change existing market structures across the end-to-end lifecycle of financial assets.","sourceIds":["bis-tokenisation-context"],"risk":"medium"},{"id":"c3","text":"BIS tokenisation material says safety and efficiency gains depend on sound governance and risk management.","sourceIds":["bis-tokenisation-context"],"risk":"medium"},{"id":"c4","text":"The BIS 2026 Annual Economic Report chapter says the rising number of tokenized networks creates interoperability and governance questions.","sourceIds":["bis-aer-2026"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-local-order-book-vs-okx-checksum-depth-controls","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-20T20:44:57.341Z","updatedAt":"2026-10-11T13:30:00.000Z","readTime":"6 min","author":"NexuAlpha Research Desk","title":{"en":"How to Manage a Local Order Book: Binance vs OKX Checksum","zh-Hans":"如何管理本地订单簿：Binance 与 OKX 对比（Checksum 已停用）"},"summary":{"en":"Bootstrap from a snapshot, apply deltas in order, detect sequence gaps and rebuild before stale depth trades. OKX fixed its checksum to 0 on June 23, 2026.","zh-Hans":"本地订单簿需先取快照、按序应用增量并检测断档；OKX checksum 自 2026-06-23 起固定为 0，改用 seqId 与 prevSeqId。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"Binance Spot WebSocket documentation describes diff depth streams used to locally manage an order book.","sourceIds":["binance-spot-ws"],"risk":"medium"},{"id":"c2","text":"Binance Futures documentation describes buffering stream events, obtaining a depth snapshot, matching update IDs and reinitializing when continuity breaks.","sourceIds":["binance-local-book"],"risk":"medium"},{"id":"c3","text":"OKX API documentation exposes order-book market-data WebSocket channels; since June 23, 2026 the checksum field on books, books-l2-tbt and books50-l2-tbt is fixed to 0, and OKX says to use seqId and prevSeqId to verify data continuity.","sourceIds":["okx-orderbook","okx-changelog","okx-notice"],"risk":"medium"},{"id":"c4","text":"A working WebSocket connection alone does not prove that a local book is current, gap-free or safe for automated execution.","sourceIds":["binance-spot-ws","binance-local-book","okx-orderbook"],"risk":"medium"},{"id":"c5","text":"OKX's changelog dated 2026-06-23 says the checksum field remains in books, books-l2-tbt and books50-l2-tbt pushes but is fixed to 0 and must no longer be used for integrity verification; books5 and bbo-tbt never carried a checksum.","sourceIds":["okx-changelog","okx-notice"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"how-to-secure-a-kraken-account-passkeys-funding-2fa-verification","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-20T20:44:57.341Z","updatedAt":"2026-09-20T20:44:57.341Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"How to Secure a Kraken Account: Passkeys, Funding 2FA and Verification Checklist","zh-Hans":"如何保护 Kraken 账户：Passkey、资金 2FA 与认证核对清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to secure Kraken account passkeys funding 2FA verification checklist. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 如何保护 Kraken 账户：Passkey、资金 2FA 与认证核对清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Kraken publishes an official verification help page for account verification.","sourceIds":["kraken-verify"],"risk":"medium"},{"id":"c2","text":"Kraken describes 2FA as an additional account-security layer and recommends passkeys over other 2FA methods.","sourceIds":["kraken-2fa"],"risk":"medium"},{"id":"c3","text":"Kraken funding 2FA documentation says funding 2FA improves security for withdrawals and notes Global Settings Lock is needed for effectiveness in the described case.","sourceIds":["kraken-funding-2fa"],"risk":"medium"},{"id":"c4","text":"Kraken multiple-2FA documentation describes adding passkeys, hardware security keys and authenticator app methods after signing in.","sourceIds":["kraken-multiple-2fa"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-rest-authentication-api-signature-nonce-order-action-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-20T20:44:57.341Z","updatedAt":"2026-09-20T20:44:57.341Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken REST Authentication: API Signature, Nonce and Order-Action Checklist","zh-Hans":"Kraken REST 认证：API 签名、Nonce 与订单动作控制清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Kraken REST authentication API signature nonce order action checklist. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 Kraken REST 认证：API 签名、Nonce 与订单动作控制清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"Kraken documents Spot REST authentication and the API-Sign header as part of authenticated request construction.","sourceIds":["kraken-rest-auth"],"risk":"medium"},{"id":"c2","text":"Kraken REST authentication documentation includes nonce handling, making duplicate and ordering control part of the integration surface.","sourceIds":["kraken-rest-auth"],"risk":"medium"},{"id":"c3","text":"Kraken documents WebSocket v2 add_order as a private order action, so order submission must be separated from public market-data reading.","sourceIds":["kraken-add-order"],"risk":"medium"},{"id":"c4","text":"Kraken documents a WebSockets token endpoint, meaning authenticated WebSocket sessions need a token retrieval and session-control step.","sourceIds":["kraken-ws-token"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-innovation-exemption-tokenized-nms-stock-amm-rights-controls","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-20T20:44:57.341Z","updatedAt":"2026-09-20T20:44:57.341Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Innovation Exemption: Tokenized NMS Stock AMM Rights and Control Checklist","zh-Hans":"SEC Innovation Exemption：代币化 NMS 股票 AMM 权利与控制清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for SEC Innovation Exemption tokenized NMS stock AMM rights controls. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 SEC Innovation Exemption：代币化 NMS 股票 AMM 权利与控制清单 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"The SEC announced temporary conditional exemptive relief for Tokenized Securities Venues from the Exchange Act definition of exchange for trading tokenized NMS stock.","sourceIds":["sec-press"],"risk":"medium"},{"id":"c2","text":"The SEC release says the relief concerns permissioned automated market makers and liquidity pools used by Tokenized Securities Venues.","sourceIds":["sec-press"],"risk":"medium"},{"id":"c3","text":"The SEC release lists conditions including rights and privileges equivalent to traditional NMS stock, issuer notice for unaffiliated tokenization, public auditable smart contracts and trading-stop linkage.","sourceIds":["sec-press"],"risk":"medium"},{"id":"c4","text":"The SEC release says the exemptions are temporary and set to expire five years after publication while the SEC requests public comment.","sourceIds":["sec-press"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"tokenized-nms-stock-venue-disclosure-radar-issuer-rights-smart-contracts","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-20T20:44:57.341Z","updatedAt":"2026-09-20T20:44:57.341Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"Tokenized NMS Stock Venue Disclosure Radar: Issuer Notice, Rights and Smart Contracts","zh-Hans":"代币化 NMS 股票场所披露雷达：发行人通知、权利与智能合约"},"summary":{"en":"A source-mapped NexuAlpha decision brief for tokenized NMS stock venue disclosure radar issuer rights smart contracts. It separates verified facts, editorial interpretation and unknowns before action.","zh-Hans":"本文用来源映射核对 代币化 NMS 股票场所披露雷达：发行人通知、权利与智能合约 的可行动边界，先给出结论，再保留未知项。"},"claims":[{"id":"c1","text":"The SEC release identifies Tokenized Securities Venues and permissioned AMM liquidity pools as the relevant temporary relief surface.","sourceIds":["sec-press"],"risk":"medium"},{"id":"c2","text":"The SEC release requires rights and privileges equivalent to the traditional NMS stock of an equivalent class as a condition.","sourceIds":["sec-press"],"risk":"medium"},{"id":"c3","text":"The SEC release requires public auditable smart contracts deployed on a public permissionless distributed ledger.","sourceIds":["sec-press"],"risk":"medium"},{"id":"c4","text":"The SEC release ties tokenized-stock trading stoppage to stoppage of the underlying NMS stock on the primary listing exchange.","sourceIds":["sec-press"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-sbe-vs-coinbase-websocket-market-data-schema-control-checklist","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-20T17:48:50.058Z","updatedAt":"2026-09-20T17:48:50.058Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"Binance SBE vs Coinbase WebSocket Market Data: Schema-Control Checklist","zh-Hans":"Binance SBE 与 Coinbase WebSocket 行情数据对比：Schema 控制清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Binance SBE vs Coinbase WebSocket market data schema controls. It separates verified facts, editorial interpretation, and unknowns before action.","zh-Hans":"Binance SBE 与 Coinbase WebSocket 行情数据对比：Schema 控制清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance publishes SBE market-data documentation for Spot API users.","sourceIds":["binance-sbe"],"risk":"medium"},{"id":"c2","text":"Binance publishes an SBE FAQ, making schema support and client decoding part of the documented control surface.","sourceIds":["binance-sbe-faq"],"risk":"medium"},{"id":"c3","text":"Coinbase documents Advanced Trade WebSocket channels for market-data subscriptions.","sourceIds":["coinbase-ws-channels"],"risk":"medium"},{"id":"c4","text":"Coinbase documents endpoint separation, so public market data and private user state must not be collapsed into one integration assumption.","sourceIds":["coinbase-ws-endpoints"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"circle-cctp-v2-usdc-crosschain-finality-fee-readiness-controls","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-20T17:48:50.058Z","updatedAt":"2026-09-20T17:48:50.058Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"Circle CCTP V2 USDC Crosschain Transfers: Finality, Fee and Readiness Controls","zh-Hans":"Circle CCTP V2 USDC 跨链转移：终局性、费用与准备度控制"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Circle CCTP V2 USDC crosschain finality fee readiness controls. It separates verified facts, editorial interpretation, and unknowns before action.","zh-Hans":"Circle CCTP V2 USDC 跨链转移：终局性、费用与准备度控制：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Circle documents CCTP as crosschain infrastructure for USDC, EURC and registered assets.","sourceIds":["circle-cctp-overview"],"risk":"medium"},{"id":"c2","text":"Circle publishes a technical CCTP guide for messages, attestations and transaction details.","sourceIds":["circle-cctp-technical"],"risk":"medium"},{"id":"c3","text":"Circle publishes chain-specific USDC contract addresses.","sourceIds":["circle-usdc-addresses"],"risk":"medium"},{"id":"c4","text":"Circle's Paymaster documentation is a separate gas-fee surface, so gas abstraction should not be conflated with CCTP transfer finality.","sourceIds":["circle-paymaster","circle-cctp-overview"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-market-data-schema-versioning-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-20T17:48:50.058Z","updatedAt":"2026-09-20T17:48:50.058Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange Market-Data Schema Versioning Radar: SBE, WebSocket and Reconnect Evidence","zh-Hans":"加密交易所行情 Schema 版本雷达：SBE、WebSocket 与重连证据"},"summary":{"en":"A source-mapped NexuAlpha decision brief for crypto exchange market data schema versioning disclosure radar. It separates verified facts, editorial interpretation, and unknowns before action.","zh-Hans":"加密交易所行情 Schema 版本雷达：SBE、WebSocket 与重连证据：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Binance provides SBE market-data documentation.","sourceIds":["binance-sbe"],"risk":"medium"},{"id":"c2","text":"Binance provides WebSocket stream documentation as a separate market-data surface.","sourceIds":["binance-websocket"],"risk":"medium"},{"id":"c3","text":"Coinbase provides an Advanced Trade WebSocket overview for subscriptions and connection behavior.","sourceIds":["coinbase-ws-overview"],"risk":"medium"},{"id":"c4","text":"Kraken documents Spot WebSocket v2 for real-time channels, which makes channel semantics part of the radar score.","sourceIds":["kraken-ws-intro"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"imf-tokenization-financial-architecture-policy-risk-map","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-20T17:48:50.058Z","updatedAt":"2026-09-20T17:48:50.058Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"IMF Tokenization and Financial Architecture: Policy Risk Map for Crypto Users","zh-Hans":"IMF 代币化与金融架构：加密用户的政策风险地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for IMF tokenization financial architecture policy risk map crypto users. It separates verified facts, editorial interpretation, and unknowns before action.","zh-Hans":"IMF 代币化与金融架构：加密用户的政策风险地图：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"The IMF frames tokenization as a potential change to settlement, payments and programmable assets rather than a blanket product guarantee.","sourceIds":["imf-tokenization"],"risk":"medium"},{"id":"c2","text":"BIS public research discusses the relationship between stablecoins, tokenised deposits and financial stability considerations.","sourceIds":["bis-annual-2026"],"risk":"medium"},{"id":"c3","text":"The FSB has examined tokenised assets and crypto-asset vulnerabilities through financial-stability work.","sourceIds":["fsb-annual-2024"],"risk":"medium"},{"id":"c4","text":"A policy source can identify risk categories without proving that a specific user product is safe, liquid, redeemable or available.","sourceIds":["imf-tokenization","bis-annual-2026","fsb-annual-2024"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-websocket-token-authenticated-channel-session-reconnect-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-20T17:48:50.058Z","updatedAt":"2026-09-20T17:48:50.058Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken WebSocket Token and Authenticated Channels: Session Reconnect Checklist","zh-Hans":"Kraken WebSocket Token 与认证频道：会话重连清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Kraken WebSocket token authenticated channel reconnect checklist. It separates verified facts, editorial interpretation, and unknowns before action.","zh-Hans":"Kraken WebSocket Token 与认证频道：会话重连清单：整理官方来源中的关键事实、适用条件与操作前核对步骤。"},"claims":[{"id":"c1","text":"Kraken documents Spot WebSocket v2 as a recommended WebSocket interface.","sourceIds":["kraken-ws-intro"],"risk":"medium"},{"id":"c2","text":"Kraken documents a REST endpoint for obtaining a WebSockets token.","sourceIds":["kraken-ws-token"],"risk":"medium"},{"id":"c3","text":"Kraken documents WebSocket v2 order submission through add_order.","sourceIds":["kraken-ws-add-order"],"risk":"medium"},{"id":"c4","text":"The documented surfaces imply separate controls for token retrieval, channel subscription, private actions and reconciliation.","sourceIds":["kraken-ws-intro","kraken-ws-token","kraken-ws-add-order"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-okx-cancel-replace-amend-order-api-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-20T11:42:00.000Z","updatedAt":"2026-09-20T11:42:00.000Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Cancel-Replace vs OKX Amend Order: API Order-Control Boundaries","zh-Hans":"Binance Cancel-Replace 与 OKX Amend Order 对比：API 订单控制边界"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Binance cancel replace vs OKX amend order API controls. It separates verified facts, editorial interpretation, and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：Binance cancel-replace and OKX amend-order workflows should not be treated as interchangeable."},"claims":[{"id":"c1","text":"Binance official developer materials document cancel, query and cancel-replace style trading endpoints for Spot API workflows.","sourceIds":["binance-trade-endpoints"],"risk":"medium"},{"id":"c2","text":"Binance WebSocket trading material describes client-order-ID handling around cancel and replace operations, so ID lifecycle is part of the control surface.","sourceIds":["binance-ws-trade"],"risk":"medium"},{"id":"c3","text":"OKX official API documentation includes amend-order and cancel-order trade operations, which are separate order lifecycle actions.","sourceIds":["okx-amend-order","okx-cancel-order"],"risk":"medium"},{"id":"c4","text":"Neither venue's public API documentation proves that a user's bot handles every timeout, partial fill, reject, amend failure or duplicate retry correctly.","sourceIds":["binance-trade-endpoints","okx-amend-order"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-project-agora-real-value-testing-wholesale-tokenization-readiness","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-20T11:42:00.000Z","updatedAt":"2026-09-20T11:42:00.000Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Project Agora Real-Value Testing: Wholesale Tokenization Readiness Map","zh-Hans":"BIS Project Agora 实值测试：批发代币化支付准备度地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for BIS Project Agora real-value testing wholesale tokenization readiness. It separates verified facts, editorial interpretation, and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：BIS Project Agora evidence supports a wholesale payments conclusion, not a retail product conclusion."},"claims":[{"id":"c1","text":"BIS lists Project Agorá as an Innovation Hub project concerning wholesale cross-border payments.","sourceIds":["bis-project-agora"],"risk":"medium"},{"id":"c2","text":"BIS published a Project Agorá report describing a shared programmable platform for wholesale cross-border payments.","sourceIds":["bis-agora-report"],"risk":"medium"},{"id":"c3","text":"BIS public materials say the Project Agorá prototype demonstrates how tokenisation and programmable technologies can address long-standing cross-border payment frictions.","sourceIds":["bis-agora-media"],"risk":"medium"},{"id":"c4","text":"BIS public materials describe advancement to real-value testing, which is different from unrestricted public retail availability.","sourceIds":["bis-agora-media"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-advanced-trade-websocket-jwt-subscription-failover-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-20T11:42:00.000Z","updatedAt":"2026-09-20T11:42:00.000Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Advanced Trade WebSocket JWT Subscription and Failover Checklist","zh-Hans":"Coinbase Advanced Trade WebSocket JWT、订阅与故障切换清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Coinbase Advanced Trade WebSocket JWT subscription failover checklist. It separates verified facts, editorial interpretation, and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：Coinbase Advanced Trade WebSocket integration depends on explicit subscription messages, JWT handling for authenticated channels, endpoint separation and failover planning."},"claims":[{"id":"c1","text":"Coinbase documentation says clients must send a subscribe message after opening the feed and may be disconnected if no subscription arrives within the documented window.","sourceIds":["coinbase-ws-overview"],"risk":"medium"},{"id":"c2","text":"Coinbase documentation says a channel and JWT are supplied in subscribe messages and that JWTs expire after a short period.","sourceIds":["coinbase-ws-overview","coinbase-ws-auth"],"risk":"medium"},{"id":"c3","text":"Coinbase endpoint documentation separates public market data endpoints from the private user-order endpoint.","sourceIds":["coinbase-ws-endpoints"],"risk":"medium"},{"id":"c4","text":"Coinbase endpoint documentation describes heartbeats and notes failover guidance when the user endpoint is the primary connection.","sourceIds":["coinbase-ws-endpoints"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fsb-global-stablecoin-framework-implementation-gaps-user-risk-map","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-20T11:42:00.000Z","updatedAt":"2026-09-20T11:42:00.000Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"FSB Global Stablecoin Framework Gaps: User Risk Map for Cross-Border Crypto Activity","zh-Hans":"FSB 全球稳定币框架缺口：跨境加密活动的用户风险地图"},"summary":{"en":"A source-mapped NexuAlpha decision brief for FSB global stablecoin framework implementation gaps user risk map. It separates verified facts, editorial interpretation, and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：The FSB's current crypto and global stablecoin materials support a practical user conclusion: implementation is improving, but gaps and inconsistencies remain across jurisdictions."},"claims":[{"id":"c1","text":"The FSB says crypto-asset and stablecoin markets are fast evolving and can threaten global financial stability if scale, vulnerabilities and interconnection grow.","sourceIds":["fsb-crypto-stablecoin-hub"],"risk":"medium"},{"id":"c2","text":"The FSB states that its 2025 peer review found welcome progress but also significant gaps and inconsistencies in implementation.","sourceIds":["fsb-crypto-stablecoin-hub","fsb-thematic-review"],"risk":"medium"},{"id":"c3","text":"The FSB's key documents include recommendations for crypto-asset activities and separate recommendations for global stablecoin arrangements.","sourceIds":["fsb-crypto-stablecoin-hub","fsb-framework"],"risk":"medium"},{"id":"c4","text":"The FSB identifies broader policy issues including consumer and investor protection, market integrity, AML/CFT, sanctions, tax and capital-control circumvention.","sourceIds":["fsb-crypto-stablecoin-hub"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"visa-vtap-tokenized-deposit-platform-bank-readiness-controls","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-20T11:42:00.000Z","updatedAt":"2026-09-20T11:42:00.000Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"Visa VTAP Tokenized Deposit Platform: Bank Readiness and User Boundary Controls","zh-Hans":"Visa VTAP 代币化存款平台：银行准备度与用户边界控制"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Visa VTAP tokenized deposit platform bank readiness controls. It separates verified facts, editorial interpretation, and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：Visa VTAP is best understood as bank-facing tokenized-asset infrastructure, not as a retail stablecoin guarantee."},"claims":[{"id":"c1","text":"Visa Developer describes Visa APIs as bank and business infrastructure rather than a consumer wallet guarantee.","sourceIds":["visa-developer-center"],"risk":"medium"},{"id":"c2","text":"Visa's VTAP materials describe tooling for banks to tokenize fiat currencies on blockchain networks.","sourceIds":["visa-vtap"],"risk":"medium"},{"id":"c3","text":"Visa's public VTAP announcement framed the platform around financial institutions issuing and managing fiat-backed tokens.","sourceIds":["visa-vtap-release"],"risk":"medium"},{"id":"c4","text":"Visa Developer surfaces operational readiness topics such as onboarding, API work and certificate changes, so bank integration remains an implementation task.","sourceIds":["visa-developer-center","visa-developer-onboarding"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-websocket-stream-limits-ping-pong-reconnect-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-20T08:45:00.000Z","updatedAt":"2026-09-20T08:45:00.000Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"Binance WebSocket Stream Limits: Ping-Pong and Reconnect Checklist","zh-Hans":"Binance WebSocket Stream 限制：Ping-Pong、重连与订阅治理清单"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Binance WebSocket stream limits ping pong reconnect checklist. It separates verified facts, editorial interpretation, and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：Binance WebSocket limits are operational controls, not optional documentation details."},"claims":[{"id":"c1","text":"Binance WebSocket Streams documentation defines stream connection behavior and includes ping-pong and disconnect handling that clients must respect.","sourceIds":["binance-ws-streams"],"risk":"medium"},{"id":"c2","text":"Binance WebSocket Streams documentation describes limits on incoming control messages and combined streams, so subscription strategy is part of production design.","sourceIds":["binance-ws-streams"],"risk":"medium"},{"id":"c3","text":"Binance REST API limit documentation separately defines request-weight constraints, meaning a reconnecting bot must not repair WebSocket gaps by unlimited REST polling.","sourceIds":["binance-rest-limits"],"risk":"low"},{"id":"c4","text":"A public stream document does not prove that a user's local bot preserves order-book continuity or detects every dropped message.","sourceIds":["binance-ws-streams","binance-rest-limits"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-websocket-sequence-checksum-gap-recovery-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-20T08:45:00.000Z","updatedAt":"2026-09-20T08:45:00.000Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange WebSocket Sequence, Checksum and Gap-Recovery Disclosure Radar","zh-Hans":"交易所 WebSocket 序列号、Checksum 与断档恢复披露雷达"},"summary":{"en":"A source-mapped NexuAlpha decision brief for crypto exchange websocket sequence checksum gap recovery disclosure radar. It separates verified facts, editorial interpretation, and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：WebSocket market data is usable only when the client can prove continuity."},"claims":[{"id":"c1","text":"Binance WebSocket documentation describes diff-depth streams and the need to combine event updates with an order book snapshot.","sourceIds":["binance-ws-streams"],"risk":"medium"},{"id":"c2","text":"OKX WebSocket documentation includes an order book channel and checksum-oriented book validation material for clients consuming market data.","sourceIds":["okx-order-book"],"risk":"medium"},{"id":"c3","text":"Coinbase WebSocket documentation separates subscription transport from order-management actions, so execution logic still needs explicit order reconciliation.","sourceIds":["coinbase-websocket","coinbase-orders"],"risk":"medium"},{"id":"c4","text":"No public WebSocket page proves that a user's local process detects every sequence gap, checksum mismatch or stale-data condition.","sourceIds":["binance-ws-streams","okx-order-book","coinbase-websocket"],"risk":"low"}],"relatedVenues":["binance","okx","coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-okx-passkey-and-withdrawal-address-book-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-20T08:45:00.000Z","updatedAt":"2026-09-20T08:45:00.000Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up OKX Passkey and Withdrawal Address Book Safely","zh-Hans":"如何安全设置 OKX Passkey 与提现地址簿：登录保护、地址核对与小额测试"},"summary":{"en":"A source-mapped NexuAlpha decision brief for how to set up OKX passkey withdrawal address book safely. It separates verified facts, editorial interpretation, and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：An OKX passkey and withdrawal address book should be treated as account-control infrastructure, not a speed shortcut."},"claims":[{"id":"c1","text":"OKX help material explains passkey setup as an account-security control that depends on the user's device and authentication flow.","sourceIds":["okx-passkey"],"risk":"medium"},{"id":"c2","text":"OKX help material explains adding or removing withdrawal addresses, so address-book maintenance is a user-controlled security surface.","sourceIds":["okx-address-book"],"risk":"medium"},{"id":"c3","text":"OKX security help material separates account-protection tasks from trading decisions, so setup should not be framed as investment advice.","sourceIds":["okx-security"],"risk":"low"},{"id":"c4","text":"Public help pages do not prove a user's device, region, account state, wallet address or withdrawal network is safe for a particular transfer.","sourceIds":["okx-passkey","okx-address-book","okx-status"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-cancel-on-disconnect-vs-coinbase-order-policy-api-lifecycle-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-20T08:45:00.000Z","updatedAt":"2026-09-20T08:45:00.000Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken Cancel-on-Disconnect vs Coinbase Order Policies: API Order Lifecycle Controls","zh-Hans":"Kraken Cancel-on-Disconnect 与 Coinbase 订单策略对比：API 订单生命周期控制"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Kraken cancel on disconnect vs Coinbase order policy API lifecycle controls. It separates verified facts, editorial interpretation, and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：Kraken's cancel-on-disconnect control and Coinbase Advanced Trade order policies solve different API lifecycle problems."},"claims":[{"id":"c1","text":"Kraken documents a cancel-on-disconnect control for futures API trading, so disconnect behavior can be treated as an explicit bot design question rather than an afterthought.","sourceIds":["kraken-cancel-disconnect"],"risk":"medium"},{"id":"c2","text":"Kraken WebSocket documentation separates streaming state from trading action, which means a bot still needs its own reconciliation path after connection loss.","sourceIds":["kraken-websocket"],"risk":"medium"},{"id":"c3","text":"Coinbase Advanced Trade documentation describes fulfillment policies such as GTC, GTD and IOC and maps them to order time-in-force behavior.","sourceIds":["coinbase-orders"],"risk":"medium"},{"id":"c4","text":"Coinbase documentation states downside protection in bracket orders is not guaranteed during high market volatility, so bots cannot treat an attached order as absolute risk removal.","sourceIds":["coinbase-orders"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"ondo-stocks-tokenized-equity-economic-exposure-vs-shareholder-rights","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-20T08:45:00.000Z","updatedAt":"2026-09-20T08:45:00.000Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"Ondo Stocks: Tokenized Equity Economic Exposure vs Shareholder Rights","zh-Hans":"Ondo Stocks：代币化股票经济敞口与股东权利边界"},"summary":{"en":"A source-mapped NexuAlpha decision brief for Ondo Stocks tokenized equity economic exposure shareholder rights. It separates verified facts, editorial interpretation, and unknowns before action.","zh-Hans":"NexuAlpha 直接答案：Ondo Stocks should be read as tokenized economic exposure, not direct stock ownership."},"claims":[{"id":"c1","text":"Ondo documentation describes Ondo Stocks as a tokenization platform for onchain exposure to publicly traded securities for investors outside the US.","sourceIds":["ondo-overview"],"risk":"medium"},{"id":"c2","text":"Ondo documentation says tokenized stocks are designed to provide economic exposure to the underlying asset, not direct title to the securities.","sourceIds":["ondo-overview"],"risk":"low"},{"id":"c3","text":"Ondo documentation states tokenized stock holders do not receive shareholder voting rights, statutory information rights or other shareholder rights from the issuer of those securities.","sourceIds":["ondo-overview","ondo-rights"],"risk":"low"},{"id":"c4","text":"Ondo documentation says direct platform use requires KYC onboarding and states onboarding is currently open to institutional participants while retail onboarding is coming soon.","sourceIds":["ondo-overview","ondo-onboarding"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-vs-kraken-stock-and-etf-trading-boundary-comparison","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-19T23:45:00.000Z","updatedAt":"2026-09-19T23:45:00.000Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase vs Kraken Stock and ETF Trading: Brokerage Boundary Comparison","zh-Hans":"Coinbase 与 Kraken 股票 ETF 交易对比：券商边界、账户隔离与适用性清单"},"summary":{"en":"Coinbase and Kraken both now present stock and ETF access beside crypto products, but the key decision is not the button label.","zh-Hans":"NexuAlpha 直接答案：Coinbase and Kraken both now present stock and ETF access beside crypto products, but the key decision is not the button label."},"claims":[{"id":"c1","text":"Coinbase states that stock access is offered through Coinbase Capital Markets Corp., a FINRA/SIPC member, and that securities services are separate from Coinbase digital asset services.","sourceIds":["coinbase-home","coinbase-broker"],"risk":"medium"},{"id":"c2","text":"Kraken states that Kraken Equities is available only in the United States and may not be available in all states, with brokerage services provided by Kraken Securities LLC.","sourceIds":["kraken-home","kraken-equities"],"risk":"medium"},{"id":"c3","text":"Both platforms put securities and crypto products near each other in the user journey, so users need to separate stock brokerage protections from digital-asset account protections.","sourceIds":["coinbase-home","kraken-home"],"risk":"medium"},{"id":"c4","text":"Neither source set proves a user's personal eligibility, tax treatment, order execution quality, or future availability without checking the signed-in account.","sourceIds":["coinbase-home","kraken-equities"],"risk":"low"}],"relatedVenues":["coinbase","kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-platform-stock-access-disclosure-radar-brokerage-tokenized-perp-boundaries","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-19T23:45:00.000Z","updatedAt":"2026-09-19T23:45:00.000Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Platform Stock Access Disclosure Radar: Brokerage, Tokenized and Perp Boundaries","zh-Hans":"加密平台股票入口披露雷达：券商、代币化与永续合约边界"},"summary":{"en":"The NexuAlpha radar separates stock-access pages by what the official source actually discloses.","zh-Hans":"NexuAlpha 直接答案：The NexuAlpha radar separates stock-access pages by what the official source actually discloses."},"claims":[{"id":"c1","text":"Coinbase discloses a securities-services separation between Coinbase Capital Markets and Coinbase digital-asset services on its public product page.","sourceIds":["coinbase-home"],"risk":"medium"},{"id":"c2","text":"Kraken discloses U.S.-only Kraken Equities availability and Kraken Securities as the brokerage provider.","sourceIds":["kraken-home","kraken-equities"],"risk":"medium"},{"id":"c3","text":"Bybit's TradFi perpetual documentation and announcements frame TradFi Perps as derivative exposure rather than direct ownership.","sourceIds":["bybit-tradfi"],"risk":"medium"},{"id":"c4","text":"The radar does not score solvency, execution quality, investor suitability, tax treatment or actual user eligibility.","sourceIds":["coinbase-home","kraken-home","bybit-tradfi"],"risk":"low"}],"relatedVenues":["coinbase","kraken","bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"direct-stock-brokerage-vs-tokenized-equities-vs-tradfi-perps-rights-map","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-19T23:45:00.000Z","updatedAt":"2026-09-19T23:45:00.000Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"Direct Stock Brokerage vs Tokenized Equities vs TradFi Perps: Rights Map","zh-Hans":"直接股票券商、代币化权益与 TradFi 永续合约：用户权利边界图"},"summary":{"en":"A direct brokerage stock position, a tokenized equity product and a TradFi perpetual contract are not interchangeable.","zh-Hans":"NexuAlpha 直接答案：A direct brokerage stock position, a tokenized equity product and a TradFi perpetual contract are not interchangeable."},"claims":[{"id":"c1","text":"Bybit describes TradFi Perpetual Contracts as derivatives that do not represent ownership of the underlying asset or shareholder rights.","sourceIds":["bybit-tradfi"],"risk":"medium"},{"id":"c2","text":"Coinbase and Kraken present stock or ETF access through disclosed securities brokerage arrangements rather than as generic crypto spot tokens.","sourceIds":["coinbase-home","kraken-home"],"risk":"medium"},{"id":"c3","text":"The SEC innovation exemption discussion conditions tokenized NMS stock trading on rights, issuer notice, symbol and volume limits, public smart-contract auditability and synchronized stoppages.","sourceIds":["sec-tokenized"],"risk":"high"},{"id":"c4","text":"The user-rights map cannot infer dividends, voting, redemption or protection unless the specific product documents grant those rights.","sourceIds":["bybit-tradfi","sec-tokenized"],"risk":"low"}],"relatedVenues":["bybit","coinbase","kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-unlock-kraken-pro-stock-trading-and-verify-equities-eligibility","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-19T23:45:00.000Z","updatedAt":"2026-09-19T23:45:00.000Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"How to Unlock Kraken Pro Stock Trading and Verify Equities Eligibility","zh-Hans":"如何开通 Kraken Pro 股票交易并核验 Equities 资格：安全教程"},"summary":{"en":"Unlock Kraken Pro stock trading only after the signed-in account shows eligible equities access.","zh-Hans":"NexuAlpha 直接答案：Unlock Kraken Pro stock trading only after the signed-in account shows eligible equities access."},"claims":[{"id":"c1","text":"Kraken's public page presents stock and ETF access alongside crypto, futures and other products.","sourceIds":["kraken-home"],"risk":"medium"},{"id":"c2","text":"Kraken states that Kraken Equities is available in the United States only and may not be available in all states.","sourceIds":["kraken-home","kraken-equities"],"risk":"medium"},{"id":"c3","text":"Kraken identifies Kraken Securities LLC as the brokerage provider for Kraken Equities.","sourceIds":["kraken-home","kraken-equities"],"risk":"medium"},{"id":"c4","text":"Users should not treat a public help page as proof of personal eligibility; eligibility must be confirmed inside the signed-in account.","sourceIds":["kraken-home","kraken-equities","kraken-legal"],"risk":"low"}],"relatedVenues":["kraken","coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-coinbase-stock-trading-expansion-crypto-exchange-brokerage-readiness","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-19T23:45:00.000Z","updatedAt":"2026-09-19T23:45:00.000Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken and Coinbase Stock Trading Expansion: Crypto Exchange Brokerage Readiness","zh-Hans":"Kraken 与 Coinbase 股票交易扩展：加密交易平台的券商化准备清单"},"summary":{"en":"Stock and ETF access inside crypto platforms is an industry shift, but it should be read as a brokerage-readiness problem rather than a convenience headline.","zh-Hans":"NexuAlpha 直接答案：Stock and ETF access inside crypto platforms is an industry shift, but it should be read as a brokerage-readiness problem rather than a convenience headline."},"claims":[{"id":"c1","text":"Coinbase presents stock trading alongside crypto products and discloses that securities services are offered by Coinbase Capital Markets Corp.","sourceIds":["coinbase-home","coinbase-help-stocks"],"risk":"medium"},{"id":"c2","text":"Kraken presents stock and ETF access alongside crypto, futures and xStocks while disclosing U.S.-only Kraken Equities availability on the public page.","sourceIds":["kraken-home","kraken-equities"],"risk":"medium"},{"id":"c3","text":"Both platform families require users to distinguish securities accounts from crypto accounts before moving funds or assuming protection.","sourceIds":["coinbase-home","kraken-home"],"risk":"medium"},{"id":"c4","text":"The source set does not prove that a given user can access the product, that every security trades 24/5, or that execution quality is equal across venues.","sourceIds":["coinbase-help-stocks","kraken-equities"],"risk":"low"}],"relatedVenues":["coinbase","kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-september-24-swell-sand-lunc-usdc-pair-delisting-bot-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-19T20:45:00.000Z","updatedAt":"2026-09-19T20:45:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit September 24 SWELL, SAND and LUNC USDC Pair Delisting: Bot and Order Checklist","zh-Hans":"Bybit 9 月 24 日 SWELL、SAND 与 LUNC USDC 交易对下架：订单与机器人检查清单"},"summary":{"en":"Bybit says it will delist the SWELLUSDC, SANDUSDC and LUNCUSDC spot trading pairs on September 24, 2026 at 08:00 UTC.","zh-Hans":"Bybit 公告称，将于 2026 年 9 月 24 日 08:00 UTC 下架 SWELLUSDC、SANDUSDC 与 LUNCUSDC 现货交易对。公告说明，剩余未成交订单会由系统移除，涉及这些交易对的现货网格机器人与 DCA 机器人会终止，相关代币的充提在未另行公告前保持开放。用户应在截止前取消订单、停止受影响机器人、导出记录，并核验任何替代交易对。"},"claims":[{"id":"c1","text":"Bybit says SWELLUSDC, SANDUSDC and LUNCUSDC spot trading pairs will be delisted on September 24, 2026 at 08:00 UTC.","sourceIds":["bybit-delist"],"risk":"medium"},{"id":"c2","text":"The notice recommends canceling outstanding orders before cessation and says remaining open orders will be automatically removed by the system.","sourceIds":["bybit-delist"],"risk":"medium"},{"id":"c3","text":"The notice says active Spot Grid Bots and DCA Bots involving the listed tokens will be automatically terminated by the system.","sourceIds":["bybit-delist","bybit-spot-grid"],"risk":"low"},{"id":"c4","text":"The notice states the delisting of a spot pair does not affect the underlying tokens and that deposits and withdrawals remain open unless announced otherwise.","sourceIds":["bybit-delist"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-tradfi-cfd-leverage-upgrade-margin-release-risk-radar","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-19T20:45:00.000Z","updatedAt":"2026-09-19T20:45:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit TradFi CFD Leverage Upgrade: Margin Release and Risk Radar","zh-Hans":"Bybit TradFi CFD 杠杆升级：保证金释放与风险雷达"},"summary":{"en":"Bybit says that from September 21, 2026 it will increase TradFi CFD leverage ceilings for Gold and Forex to as much as 1:2000 and move listed 24/5 Stock CFDs to tiered leverage up to 1:100.","zh-Hans":"Bybit 称自 2026 年 9 月 21 日起，将 Gold 与 Forex TradFi CFD 最高杠杆提高至最高 1:2000，并把列出的 24/5 Stock CFD 调整为最高 1:100 的分层杠杆。运营问题不只是保证金降低。用户在重新部署释放出的资本前，应核验代码范围、敞口层级、保证金水平、释放保证金、止损设置、地区资格，以及更高杠杆是否同时改变收益与损失敏感度。"},"claims":[{"id":"c1","text":"Bybit says Gold and Forex leverage ceilings will increase to as much as 1:2000 from September 21, 2026.","sourceIds":["bybit-leverage"],"risk":"medium"},{"id":"c2","text":"Bybit says 20 listed 24/5 Stock CFDs will move from fixed leverage to tiered leverage of up to 1:100.","sourceIds":["bybit-leverage"],"risk":"medium"},{"id":"c3","text":"Bybit says surplus margin on existing open positions will be released automatically on the effective date.","sourceIds":["bybit-leverage"],"risk":"low"},{"id":"c4","text":"Bybit warns that higher leverage increases both potential returns and potential losses and recommends reviewing open positions, margin usage and margin levels.","sourceIds":["bybit-leverage"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cftc-prediction-market-incentive-program-self-certification-checklist","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-19T20:45:00.000Z","updatedAt":"2026-09-19T20:45:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC Prediction Market Incentive Program Advisory: Self-Certification Checklist","zh-Hans":"CFTC 预测市场激励计划咨询：自我认证检查清单"},"summary":{"en":"The CFTC's Division of Market Oversight issued an August 12, 2026 advisory reminding designated contract markets that market-maker, liquidity, trading and incentive programs for prediction markets must be properly submitted under.","zh-Hans":"CFTC 市场监督司在 2026 年 8 月 12 日发布咨询，提醒指定合约市场，预测市场中的做市、流动性、交易和激励计划必须按照 Regulation 40.5 与 40.6 正确提交。对用户而言，重点并不是每个激励都不安全，而是事件合约平台应公开清晰计划条款，评估核心原则合规，并避免让谁付款、谁交易、如何结算、适用哪些保护变得模糊的促销表达。"},"claims":[{"id":"c1","text":"The CFTC advisory says the Division of Market Oversight reminded designated contract markets of obligations when submitting market-maker, liquidity, trading or incentive programs under Regulations 40.5 and 40.6.","sourceIds":["cftc-advisory"],"risk":"medium"},{"id":"c2","text":"The advisory says some event-contract incentive filings contained procedural or substantive deficiencies.","sourceIds":["cftc-advisory"],"risk":"medium"},{"id":"c3","text":"The advisory says such deficiencies can impede staff evaluation of adequate notice and assessment of compliance with core principles and Commission requirements.","sourceIds":["cftc-advisory"],"risk":"low"},{"id":"c4","text":"CFTC educational material says event contracts are frequently structured as swaps and often use yes-no outcomes with fixed payouts.","sourceIds":["cftc-prediction-markets"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-use-pancakeswap-connect-wallet-and-make-first-swap-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-19T20:45:00.000Z","updatedAt":"2026-09-19T20:45:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"How to Use PancakeSwap: Connect a Wallet and Make a First Swap Safely","zh-Hans":"如何使用 PancakeSwap：安全连接钱包并完成首次兑换"},"summary":{"en":"PancakeSwap onboarding is wallet-based DEX access, not centralized-exchange account registration.","zh-Hans":"PancakeSwap 入门是基于钱包的 DEX 访问，不是中心化交易所账户注册。应只从 PancakeSwap 官方网站或文档开始，使用兼容钱包，核验网络，不把恢复短语和私钥输入网站或聊天，并在核对代币合约、链、路由、滑点、gas 与交易预览后再进行首次兑换。这条 DEX 入门路径不应收集凭据或身份文件。"},"claims":[{"id":"c1","text":"PancakeSwap documentation says users need a wallet that supports BNB Smart Chain to get started on PancakeSwap.","sourceIds":["pancake-wallet"],"risk":"medium"},{"id":"c2","text":"The wallet guide warns users to download wallets only from official sources and never share or input recovery phrases outside the wallet app.","sourceIds":["pancake-wallet"],"risk":"medium"},{"id":"c3","text":"The connection guide says users connect by clicking Connect Wallet and following the wallet pop-up instructions.","sourceIds":["pancake-connect"],"risk":"low"},{"id":"c4","text":"The connection guide says users should ensure the wallet is on the intended mainnet, such as Aptos Mainnet for PancakeSwap on Aptos.","sourceIds":["pancake-connect"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"tokenized-nms-stock-amm-liquidity-pool-exemption-operational-checklist","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-19T20:45:00.000Z","updatedAt":"2026-09-19T20:45:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Tokenized NMS Stock AMM Liquidity Pools: SEC Exemption Operational Checklist","zh-Hans":"代币化 NMS 股票 AMM 流动性池：SEC 豁免运营检查清单"},"summary":{"en":"The SEC's September 17, 2026 Innovation Exemption is temporary, conditional relief for Tokenized Securities Venues, not blanket approval for every tokenized stock interface.","zh-Hans":"SEC 2026 年 9 月 17 日的 Innovation Exemption 是给予 Tokenized Securities Venues 的临时、有条件豁免，并不是对所有代币化股票界面的笼统批准。SEC 表示，TSV 只有在满足代码与成交量限制、与等同传统 NMS 股票具有相同权利、第三方代币化前向发行人通知、智能合约可审计且公开、基础 NMS 股票停牌时同步停止交易等条件下，才可通过许可式 AMM 流动性池交易代币化 NMS 股票。"},"claims":[{"id":"c1","text":"The SEC issued an order on September 17, 2026 granting temporary conditional exemptive relief to Tokenized Securities Venues from the Exchange Act definition of exchange.","sourceIds":["sec-exemption"],"risk":"medium"},{"id":"c2","text":"The SEC release says TSVs bring together buyers and sellers through one or more permissioned AMM Liquidity Pools and standards for access to those pools.","sourceIds":["sec-exemption"],"risk":"medium"},{"id":"c3","text":"The SEC lists conditions including symbol and volume limits, same rights and privileges as equivalent traditional NMS stock, issuer notice for unaffiliated third-party tokenization and auditable public smart contracts.","sourceIds":["sec-exemption"],"risk":"low"},{"id":"c4","text":"The SEC says the exemptions are set to expire five years after publication and solicits public comment.","sourceIds":["sec-exemption"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-september-22-wallet-system-upgrade-deposit-withdrawal-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-19T17:40:22.000Z","updatedAt":"2026-09-19T17:40:22Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Binance September 22 Wallet System Upgrade: Deposit and Withdrawal Checklist","zh-Hans":"Binance 9 月 22 日钱包系统升级：充提检查清单"},"summary":{"en":"Binance lists a wallet system upgrade for September 22, 2026 in its official maintenance feed. Users should treat the maintenance notice as an operational dependency, not as proof of token delisting or insolvency.","zh-Hans":"Binance 官方维护信息流列出了 2026 年 9 月 22 日的钱包系统升级。用户应把维护通知视为运营依赖，而不是代币下架或资不抵债的证据。转移资金前，应在实时公告中核对准确维护时段，分别检查资产与网络状态，避免时间敏感的转账，保留交易标识，并等待平台实际充提状态恢复，不能只依赖 HTTP 状态码或缓存公告。"},"claims":[{"id":"c1","text":"Binance's official maintenance feed lists a wallet system upgrade for September 22, 2026.","sourceIds":["binance-maint"],"risk":"medium"},{"id":"c2","text":"The same maintenance feed distinguishes wallet work from separate token integrations, contract swaps and network upgrades.","sourceIds":["binance-maint"],"risk":"medium"},{"id":"c3","text":"A successful webpage response does not prove that deposits or withdrawals for a particular asset and network are open.","sourceIds":["binance-maint","binance-deposit"],"risk":"low"},{"id":"c4","text":"Users need to verify asset, network, address and live service status before initiating a transfer.","sourceIds":["binance-deposit"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-rpi-vs-standard-order-book-tradfi-perpetual-execution-comparison","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-19T17:40:22.000Z","updatedAt":"2026-09-19T17:40:22Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit RPI vs Standard Order Book: TradFi Perpetual Execution Comparison","zh-Hans":"Bybit RPI 与标准订单簿：TradFi 永续合约执行对比"},"summary":{"en":"Bybit will restore Retail Price Improvement eligibility for ten TradFi perpetual symbols at 10:00 UTC on September 22, 2026.","zh-Hans":"Bybit 将于 2026 年 9 月 22 日 10:00 UTC 恢复十个 TradFi 永续合约代码的零售价格改善资格。RPI 并不是标准订单簿的替代品：它是仅限挂单方、只与合格零售吃单流量匹配的流动性机制，而标准撮合、费用与订单类型保持可用。交易者应比较可执行价格、成交概率、排队规则、代码资格、费用、交易时段状态与强平风险，不能把 RPI 标签当成保证更优成交。"},"claims":[{"id":"c1","text":"Bybit scheduled restoration of RPI eligibility for 10:00 UTC on September 22, 2026.","sourceIds":["bybit-rpi"],"risk":"medium"},{"id":"c2","text":"The change covers ten named TradFi perpetual symbols, including TSLAUSDT, AAPLUSDT and SPYUSDT.","sourceIds":["bybit-rpi"],"risk":"medium"},{"id":"c3","text":"RPI orders are maker-only and can match only against eligible retail taker flow.","sourceIds":["bybit-rpi"],"risk":"low"},{"id":"c4","text":"Bybit says standard order-book matching, fees and order types for the affected symbols remain unchanged.","sourceIds":["bybit-rpi","bybit-fees"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cftc-passive-software-no-action-radar-control-and-custody-boundaries","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-19T17:40:22.000Z","updatedAt":"2026-09-19T17:40:22Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC Passive Software No-Action Radar: Control, Custody and Execution Boundaries","zh-Hans":"CFTC 被动软件不采取行动雷达：控制、托管与执行边界"},"summary":{"en":"The CFTC announced a staff no-action position for providers of passive software on September 17, 2026. A no-action position is conditional staff enforcement relief, not a statute, license or blanket approval of any interface.","zh-Hans":"CFTC 于 2026 年 9 月 17 日宣布针对被动软件提供者的工作人员不采取行动立场。不采取行动立场是有条件的执法宽免，不是成文法、许可证，也不是对任何界面的全面批准。NexuAlpha 雷达会评估提供者是否仅发布软件，还是还控制升级、路由订单、选择交易对手、托管资产、设定费用、居间执行或宣传收益。超出信函条件的主动控制都可能改变分析，需要最新法律与技术审查。"},"claims":[{"id":"c1","text":"CFTC staff announced the passive-software no-action position on September 17, 2026.","sourceIds":["cftc-release"],"risk":"medium"},{"id":"c2","text":"The relief is expressed as a staff no-action position rather than a generally applicable statutory exemption.","sourceIds":["cftc-release","cftc-letters"],"risk":"medium"},{"id":"c3","text":"The operative staff letter and its conditions control the scope of reliance.","sourceIds":["cftc-letters"],"risk":"low"},{"id":"c4","text":"Custody, execution control, order routing and discretionary intervention are material boundary questions for software providers.","sourceIds":["cftc-release","cftc-crypto-faq"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-bitnomial-kalshi-security-futures-filings-market-structure-watch","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-19T17:40:22.000Z","updatedAt":"2026-09-19T17:40:22Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase, Bitnomial and Kalshi Security-Futures Filings: Market-Structure Watch","zh-Hans":"Coinbase、Bitnomial 与 Kalshi 证券期货申报：市场结构观察"},"summary":{"en":"The SEC's September 18 what's-new feed lists separate security-futures filings from Coinbase Derivatives, Bitnomial Exchange and KalshiEX.","zh-Hans":"SEC 9 月 18 日的最新信息流分别列出 Coinbase Derivatives、Bitnomial Exchange 与 KalshiEX 的证券期货申报。这些申报涉及不同规则，包括产品规则、上市标准与客户保证金，不能被合并解释为一个统一市场已经上线。投资者与运营方应分别跟踪文件编号、监管路径、生效或批准状态、产品规格、保证金模型、合格参与者与实际上线通知，再判断可访问性和流动性。"},"claims":[{"id":"c1","text":"The SEC what's-new feed lists three security-futures-related filings dated September 18, 2026.","sourceIds":["sec-whatsnew"],"risk":"medium"},{"id":"c2","text":"The listed organizations are Coinbase Derivatives, Bitnomial Exchange and KalshiEX.","sourceIds":["sec-whatsnew"],"risk":"medium"},{"id":"c3","text":"The Coinbase filing includes cash-settled individual-equity and ETF futures, including perpetual single-stock futures.","sourceIds":["sec-coin-pdf","sec-coin-index"],"risk":"low"},{"id":"c4","text":"Filing publication, regulatory approval, product launch and customer availability are distinct milestones.","sourceIds":["sec-whatsnew","sec-coin-index"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-derivatives-cash-settled-equity-and-etf-futures-filing-explained","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-19T17:40:22.000Z","updatedAt":"2026-09-19T17:40:22Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Derivatives Equity and ETF Futures Filing: Scope, Approval and Risks","zh-Hans":"Coinbase Derivatives 股票与 ETF 期货申报：范围、审批与风险"},"summary":{"en":"Coinbase Derivatives filed proposed rules on September 18, 2026 for cash-settled futures on individual equities and ETF shares, including perpetual single-stock futures.","zh-Hans":"Coinbase Derivatives 于 2026 年 9 月 18 日提交拟议规则，涉及个股与 ETF 份额的现金结算期货，包括永续单股期货。SEC 通知说明该提案同时提交给 CFTC，且 CFTC 当时尚未批准。这是一份规则申报，不代表所有产品已经上线，也不代表所有地区都可访问。决策者应分别核验申报状态、监管批准、合约上线、客户资格、结算方法、保证金、交易时间和标的公司行动处理。"},"claims":[{"id":"c1","text":"Coinbase Derivatives filed SR-COIN-2026-002 on September 18, 2026.","sourceIds":["sec-coin-pdf","sec-coin-index"],"risk":"medium"},{"id":"c2","text":"The filing concerns cash-settled futures on individual equity securities and ETF shares, including perpetual single-stock futures.","sourceIds":["sec-coin-pdf"],"risk":"medium"},{"id":"c3","text":"The SEC notice says the filing was made concurrently with the CFTC and that CFTC approval had not yet occurred.","sourceIds":["sec-coin-pdf"],"risk":"low"},{"id":"c4","text":"The SEC rulemaking page states that comments are due 21 days after Federal Register publication.","sourceIds":["sec-coin-index","sec-comments"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-create-backpack-exchange-account-complete-kyc-and-secure-first-funding","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-18T11:38:51.000Z","updatedAt":"2026-09-18T11:38:51Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"How to Create a Backpack Exchange Account, Complete KYC and Secure First Funding","zh-Hans":"如何创建 Backpack Exchange 账户、完成 KYC 并安全首次入金"},"summary":{"en":"Go directly to backpack.exchange, select Sign Up, provide an email address you control, create a unique password, accept the current agreements and enter the email code within its validity window.","zh-Hans":"直接访问 backpack.exchange，选择注册，填写本人控制的邮箱，设置唯一密码，接受当前协议，并在有效期内输入邮箱验证码。随后进入身份认证，提供居住地、法定身份、收入来源、证件图像并完成人脸活体检查。通过后启用可用安全控制，再通过充值菜单进行网络匹配的小额首次转账。"},"claims":[{"id":"c1","text":["Domain","Backpack instructs users to verify the official backpack.exchange domain.","backpack-create"],"sourceIds":["backpack-create"],"risk":"medium"},{"id":"c2","text":["Email","The signup flow sends an email verification code with a stated validity window.","backpack-create"],"sourceIds":["backpack-create"],"risk":"medium"},{"id":"c3","text":["KYC","Individual verification includes residence, identity data, document upload and face scan.","backpack-verify"],"sourceIds":["backpack-verify"],"risk":"low"},{"id":"c4","text":["Funding","The onboarding guide places funding after account creation and KYC.","backpack-onboarding"],"sourceIds":["backpack-onboarding"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"],"qualityFlags":["template-thin"]},{"slug":"how-to-onboard-dydx-chain-connect-link-wallet-and-make-safe-first-deposit","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-18T11:38:51.000Z","updatedAt":"2026-09-18T11:38:51Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"How to Onboard to dYdX Chain: Connect, Link a Wallet and Make a Safe First Deposit","zh-Hans":"如何开始使用 dYdX Chain：连接、关联钱包并安全首次入金"},"summary":{"en":"The official dYdX onboarding flow has three stages: connect a supported wallet or choose email/social login, link or generate the dYdX Chain wallet through the required signatures, then deposit funds through the supported route.","zh-Hans":"官方 dYdX 入门流程分为三步：连接受支持钱包或选择邮箱/社交登录，通过所需签名关联或生成 dYdX Chain 钱包，然后使用受支持路由入金。EVM、SVM 与 Cosmos 钱包流程不同；社交登录会创建带24词助记词的钱包并要求2FA。应核对所选路径使用 Skip、Coinbase、dYdX Chain 还是 Noble 地址，再以小额测试。"},"claims":[{"id":"c1","text":["Stages","dYdX documents connect, link and deposit as three onboarding stages.","dydx-start"],"sourceIds":["dydx-start"],"risk":"medium"},{"id":"c2","text":["Wallet paths","The guide distinguishes EVM, SVM, Cosmos and email/social onboarding.","dydx-start"],"sourceIds":["dydx-start"],"risk":"medium"},{"id":"c3","text":["Social login","The social route creates a wallet with a 24-word seed phrase and requires 2FA.","dydx-start"],"sourceIds":["dydx-start"],"risk":"low"},{"id":"c4","text":["Funding","The guide describes deposits through supported chain flows, Coinbase or direct Noble deposits depending on wallet type.","dydx-start"],"sourceIds":["dydx-start"],"risk":"low"}],"relatedVenues":["dydx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"],"qualityFlags":["template-thin"]},{"slug":"how-to-onboard-hyperliquid-connect-wallet-enable-trading-and-test-deposit","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-18T11:38:51.000Z","updatedAt":"2026-09-18T11:38:51Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"How to Onboard to Hyperliquid: Connect a Wallet, Enable Trading and Test a Deposit","zh-Hans":"如何开始使用 Hyperliquid：连接钱包、启用交易并测试入金"},"summary":{"en":"Hyperliquid supports onboarding with a DeFi wallet or email-based login. A wallet user connects the official app, reviews the connection request, signs the gasless Enable Trading action, then chooses an officially supported asset.","zh-Hans":"Hyperliquid 支持通过 DeFi 钱包或邮箱登录入门。钱包用户连接官方应用、审查连接请求、签署免 Gas 的“启用交易”操作，然后选择官方支持的资产与网络入金。邮箱用户接收验证码并获得新的链上地址。绝不分享助记词或私钥，并在核对网络、地址和目的余额后先进行小额转账。"},"claims":[{"id":"c1","text":["Methods","Hyperliquid documents DeFi wallet and email login paths.","hyper-start"],"sourceIds":["hyper-start"],"risk":"medium"},{"id":"c2","text":["Wallet security","The guide warns that anyone with the seed phrase or private key can access funds.","hyper-start"],"sourceIds":["hyper-start"],"risk":"medium"},{"id":"c3","text":["Enable trading","Wallet onboarding includes a gasless signed Enable Trading action.","hyper-start"],"sourceIds":["hyper-start"],"risk":"low"},{"id":"c4","text":["Routes","The guide lists multiple supported deposit assets and networks and distinguishes Send from Withdrawal.","hyper-start","hyper-withdraw"],"sourceIds":["hyper-start","hyper-withdraw"],"risk":"low"}],"relatedVenues":["hyperliquid"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"],"qualityFlags":["template-thin"]},{"slug":"how-to-register-gate-account-complete-identity-verification-and-secure-access","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-18T11:38:51.000Z","updatedAt":"2026-09-18T11:38:51Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"How to Register a Gate Account, Complete Identity Verification and Secure Access","zh-Hans":"如何注册 Gate、完成身份认证并保护账户访问"},"summary":{"en":"Begin only from the official Gate domain for the correct regional entity, create a personal account with a unique password, and review the live terms for jurisdictional availability.","zh-Hans":"仅从适用于所在地区实体的 Gate 官方域名开始，使用唯一密码创建个人账户，并核对实时司法辖区条款。网页身份认证流程要求国籍、居住地、法定姓名、证件类型与号码，随后按要求完成证件与人脸检查。入金前应完成安全控制并确认充值提现资格。"},"claims":[{"id":"c1","text":["Requirement","Gate guides describe identity verification for access to platform functions.","gate-web"],"sourceIds":["gate-web"],"risk":"medium"},{"id":"c2","text":["Data","The web flow requests nationality, residence, name, ID type and number.","gate-web"],"sourceIds":["gate-web"],"risk":"medium"},{"id":"c3","text":["Documents","Official guides require a valid government-issued photo ID.","gate-eu"],"sourceIds":["gate-eu"],"risk":"low"},{"id":"c4","text":["Region","Requirements and availability depend on the Gate entity and jurisdiction.","gate-kyc"],"sourceIds":["gate-kyc"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"],"qualityFlags":["template-thin"]},{"slug":"how-to-register-mexc-account-complete-primary-kyc-and-secure-first-deposit","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-18T11:38:51.000Z","updatedAt":"2026-09-18T11:38:51Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"How to Register a MEXC Account, Complete Primary KYC and Secure the First Deposit","zh-Hans":"如何注册 MEXC、完成初级身份认证并安全进行首次充值"},"summary":{"en":"Use the official MEXC domain or app, register with a user-controlled email address or phone number, create a unique password, enter the verification code, and confirm the account before opening the Identification page.","zh-Hans":"使用 MEXC 官方域名或应用，以本人控制的邮箱或手机号注册，设置唯一密码，输入验证码并确认账户，然后进入身份认证页面。初级 KYC 需要选择证件签发国家、受支持证件类型并上传清晰证件图像。选择准确网络进行小额首次充值前，应先保护登录与恢复渠道。"},"claims":[{"id":"c1","text":["Registration","MEXC describes signup by email or mobile number and email-code verification.","mexc-signup"],"sourceIds":["mexc-signup"],"risk":"medium"},{"id":"c2","text":["Password","The current guide specifies a password with multiple character classes.","mexc-signup"],"sourceIds":["mexc-signup"],"risk":"medium"},{"id":"c3","text":["KYC","Primary KYC requires document country, ID type and document images.","mexc-kyc"],"sourceIds":["mexc-kyc"],"risk":"low"},{"id":"c4","text":["Access","MEXC says some features require completed KYC.","mexc-access"],"sourceIds":["mexc-access"],"risk":"low"}],"relatedVenues":["mexc"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"],"qualityFlags":["template-thin"]},{"slug":"bybit-september-24-collateral-tier-ratio-update-loan-health-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-18T08:39:34.000Z","updatedAt":"2026-09-18T08:39:34Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit September 24 Collateral-Tier Update: Loan-Health Checklist","zh-Hans":"Bybit 9月24日抵押层级更新：贷款健康度检查清单"},"summary":{"en":"Bybit scheduled new collateral tiers and ratios for a long list of assets across four lending products at 08:00 UTC on September 24, 2026.","zh-Hans":"Bybit 计划于2026年9月24日08:00 UTC对四类借贷产品中的大量资产启用新抵押层级与比例。公告没有给出统一结果：每个账户都必须结合详细变更表、当前余额、债务和产品规则计算。截止前应导出余额、把每项受影响资产映射到新层级、重算抵押价值并恢复有意设置的强平缓冲。"},"claims":[{"id":"c1","text":["Date","The update is effective September 24, 2026 at 08:00 UTC.","bybit-update"],"sourceIds":["bybit-update"],"risk":"medium"},{"id":"c2","text":["Products","Four loan products are named.","bybit-update"],"sourceIds":["bybit-update"],"risk":"medium"},{"id":"c3","text":["Assets","The notice provides a broad affected-asset list from 0G through ZK.","bybit-update"],"sourceIds":["bybit-update"],"risk":"low"},{"id":"c4","text":["Action","Bybit encourages users to review positions and act before effectiveness.","bybit-update"],"sourceIds":["bybit-update"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cftc-passive-software-no-action-position-scope-conditions-registration-boundary","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-18T08:39:34.000Z","updatedAt":"2026-09-18T08:39:34Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC Passive-Software No-Action Position: Scope, Conditions and Registration Boundary","zh-Hans":"CFTC 被动软件不行动立场：范围、条件与注册边界"},"summary":{"en":"CFTC Market Participants Division announced a conditional no-action position for providers of passive software, similar to Staff Letter 26-09 and broadly available to qualifying providers.","zh-Hans":"CFTC 市场参与者部门宣布一项面向被动软件提供商的有条件不行动立场，类似工作人员函26-09，并向符合条件的提供商广泛开放。工作人员表示，仅就提供和营销帮助用户与已注册 FCM、IB 和 DCM 交易的软件而言，在指定条件下不会建议因未注册为介绍经纪商或其关联人员而执法。这是工作人员层面的条件性救济，不是法律、牌照或普遍豁免。"},"claims":[{"id":"c1","text":["Issuer","The position was announced by CFTC Market Participants Division.","cftc-release"],"sourceIds":["cftc-release"],"risk":"medium"},{"id":"c2","text":["Registration","It concerns IB and associated-person registration recommendations.","cftc-release"],"sourceIds":["cftc-release"],"risk":"medium"},{"id":"c3","text":["Activity","It applies solely to software facilitating user trading with registered FCMs, IBs and DCMs.","cftc-release"],"sourceIds":["cftc-release"],"risk":"low"},{"id":"c4","text":["Conditions","The release says the position is subject to specified conditions.","cftc-release"],"sourceIds":["cftc-release"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-lending-collateral-tier-ratio-effective-date-account-impact-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-18T08:39:34.000Z","updatedAt":"2026-09-18T08:39:34Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Lending Collateral-Change Radar: Tiers, Ratios, Effective Dates and Account Impact","zh-Hans":"加密借贷抵押变更雷达：层级、比例、生效时间与账户影响"},"summary":{"en":"NexuAlpha Radar treats a collateral update as a structured change set: product, asset, old tier, new tier, old ratio, new ratio, effective timestamp, affected balance, recognized value delta and liquidation-buffer delta.","zh-Hans":"NexuAlpha 雷达把抵押更新处理为结构化变更集：产品、资产、旧层级、新层级、旧比例、新比例、生效时间、受影响余额、认可价值变化和强平缓冲变化。平台标题无法计算账户结果。Bybit 9月24日公告只有在详细表格与用户非敏感余额、债务数据结合后，才会成为可操作输入。"},"claims":[{"id":"c1","text":["State change","The notice changes both tier structure and ratios.","bybit-update"],"sourceIds":["bybit-update"],"risk":"medium"},{"id":"c2","text":["Cross-product scope","The same announcement spans four loan products.","bybit-update"],"sourceIds":["bybit-update"],"risk":"medium"},{"id":"c3","text":["Account impact","Bybit says collateral value may change.","bybit-update"],"sourceIds":["bybit-update"],"risk":"low"},{"id":"c4","text":["Action boundary","The notice directs users to review positions before effectiveness.","bybit-update"],"sourceIds":["bybit-update"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-loan-collateral-tier-vs-collateral-ratio-borrowing-capacity-comparison","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-18T08:39:34.000Z","updatedAt":"2026-09-18T08:39:34Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Loan Collateral Tier vs Collateral Ratio: Borrowing-Capacity Comparison","zh-Hans":"加密贷款抵押层级与抵押率：借贷能力对比"},"summary":{"en":"Collateral tiers and collateral ratios are related but different controls. A tier maps asset quantity into bands, while the ratio determines how much recognized collateral value that balance contributes.","zh-Hans":"抵押层级与抵押率相关但不是同一控制。层级把资产数量划分为区间，抵押率决定该余额可贡献多少认可抵押价值。任一参数变化时，即使币价和名义余额不变，借贷能力、贷款价值比与强平缓冲也可能改变。用户应在生效前把每项资产映射到产品特定层级并重算账户健康度。"},"claims":[{"id":"c1","text":["Change","Bybit announced changes to collateral tier structures and applicable collateral ratios for selected assets.","bybit-update"],"sourceIds":["bybit-update"],"risk":"medium"},{"id":"c2","text":["Products","The update covers Crypto Loans, UTA Loans, Institutional Loans and Bybit Pay Later.","bybit-update"],"sourceIds":["bybit-update"],"risk":"medium"},{"id":"c3","text":["Effective time","The stated effective time is September 24, 2026 at 08:00 UTC.","bybit-update"],"sourceIds":["bybit-update"],"risk":"low"},{"id":"c4","text":["Impact","Bybit says the updates may affect the collateral value of affected assets.","bybit-update"],"sourceIds":["bybit-update"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"tokenized-securities-real-time-inventory-management-overnight-market-readiness","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-18T08:39:34.000Z","updatedAt":"2026-09-18T08:39:34Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Tokenized Securities and Real-Time Inventory Management: Overnight-Market Readiness","zh-Hans":"代币化证券与实时库存管理：隔夜市场准备"},"summary":{"en":"SEC Chairman Atkins described tokenization as potentially improving real-time inventory management, reducing settlement failures and mitigating abusive naked short-selling risk as markets extend overnight.","zh-Hans":"SEC 主席 Atkins 表示，在市场延长至隔夜交易时，代币化可能改善实时库存管理、减少结算失败并缓解滥用裸卖空风险。这是前瞻政策观点，不是已部署运营模式的证明。机构仍需权威所有权记录、借券定位、证券借贷可用性、公司行动处理、隔夜行情、清算连续性与异常恢复，代币化库存才可能支持连续股票交易。"},"claims":[{"id":"c1","text":["Inventory","Chair Atkins said tokenization has potential to support real-time inventory management.","sec-atkins"],"sourceIds":["sec-atkins"],"risk":"medium"},{"id":"c2","text":["Settlement","The remarks connect that potential to fewer settlement failures.","sec-atkins"],"sourceIds":["sec-atkins"],"risk":"medium"},{"id":"c3","text":["Operations","The remarks identify locates, prime brokerage and securities lending as overnight support questions.","sec-atkins"],"sourceIds":["sec-atkins"],"risk":"low"},{"id":"c4","text":["Market baseline","SEC staff analyzed overnight volume, traded value and participant activity.","sec-memo"],"sourceIds":["sec-memo"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"blockchain-network-upgrade-vs-exchange-wallet-maintenance-service-impact-comparison","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-18T05:40:00.000Z","updatedAt":"2026-09-18T05:40:00Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Blockchain Network Upgrade vs Exchange Wallet Maintenance: Service-Impact Comparison","zh-Hans":"区块链网络升级与交易所钱包维护：服务影响对比"},"summary":{"en":"A blockchain network upgrade changes protocol software or consensus state at a target time or block height, while exchange wallet maintenance changes the venue's custody gateway and internal operational availability.","zh-Hans":"区块链网络升级会在目标时间或区块高度改变协议软件或共识状态；交易所钱包维护则改变平台托管网关和内部运营可用性。两者都可能暂停充值提现，但都不自动意味着交易暂停。用户转账前应分别核对链状态、平台钱包状态、入账状态、交易可用性和恢复证据。"},"claims":[{"id":"c1","text":["Network event","Bybit expected Zigchain v4.3.0 at approximately 09:00 UTC or block 12,197,000.","bybit-zig"],"sourceIds":["bybit-zig"],"risk":"medium"},{"id":"c2","text":["Wallet pause","ZIG deposits and withdrawals were scheduled to pause at 08:30 UTC.","bybit-zig"],"sourceIds":["bybit-zig"],"risk":"medium"},{"id":"c3","text":["Trading","Bybit said other activities such as trading would not be affected.","bybit-zig"],"sourceIds":["bybit-zig"],"risk":"low"},{"id":"c4","text":["Wallet infrastructure","A separate Bybit maintenance notice described internal USDC movements between old and new hot wallets.","bybit-wallet"],"sourceIds":["bybit-wallet"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-zigchain-v4-3-upgrade-deposit-withdrawal-suspension-resumption-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-18T05:40:00.000Z","updatedAt":"2026-09-18T05:40:00Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit Zigchain v4.3 Upgrade: Deposit, Withdrawal and Resumption Checklist","zh-Hans":"Bybit Zigchain v4.3 升级：充值、提现与恢复检查清单"},"summary":{"en":"Bybit said it would support Zigchain v4.3.0 at approximately 09:00 UTC on September 17, 2026, or block height 12,197,000, and suspend ZIG deposits and withdrawals from 08:30 UTC. Trading was stated to remain unaffected.","zh-Hans":"Bybit 称将支持 Zigchain v4.3.0，预计于2026年9月17日09:00 UTC左右或区块高度12,197,000进行，并从08:30 UTC起暂停 ZIG 充值提现。公告称交易不受影响。由于 Bybit 表示不会另发恢复公告，用户应使用充值或提现页面提醒，并在转账前核对实时网络状态。"},"claims":[{"id":"c1","text":["Upgrade","The notice names Zigchain v4.3.0.","bybit-zig"],"sourceIds":["bybit-zig"],"risk":"medium"},{"id":"c2","text":["Trigger","The expected trigger is 09:00 UTC or block height 12,197,000.","bybit-zig"],"sourceIds":["bybit-zig"],"risk":"medium"},{"id":"c3","text":["Suspension","Deposits and withdrawals were scheduled to pause from 08:30 UTC.","bybit-zig"],"sourceIds":["bybit-zig"],"risk":"low"},{"id":"c4","text":["Resumption","Bybit said no further announcement would be issued and directed users to set an alert.","bybit-zig"],"sourceIds":["bybit-zig"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-network-upgrade-block-height-wallet-pause-resumption-evidence-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-18T05:40:00.000Z","updatedAt":"2026-09-18T05:40:00Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange Network-Upgrade Radar: Block Height, Wallet Pause and Resumption Evidence","zh-Hans":"交易所网络升级雷达：区块高度、钱包暂停与恢复证据"},"summary":{"en":"NexuAlpha Radar models exchange support for a network upgrade as separate evidence states: version, target time, target height, deposit cutoff, withdrawal cutoff, trading impact, validator completion, venue wallet testing.","zh-Hans":"NexuAlpha 雷达把交易所支持网络升级拆分为独立证据状态：版本、目标时间、目标高度、充值截止、提现截止、交易影响、验证者完成、平台钱包测试、恢复信号与恢复后入账。Bybit Zigchain 公告说明了这种拆分的重要性：交易保持可用而钱包服务暂停，恢复信号来自账户页面提醒而不是新的公开公告。"},"claims":[{"id":"c1","text":["Dual trigger","The notice provides both approximate time and block height.","bybit-zig"],"sourceIds":["bybit-zig"],"risk":"medium"},{"id":"c2","text":["Service split","Deposits and withdrawals pause while trading is stated to continue.","bybit-zig"],"sourceIds":["bybit-zig"],"risk":"medium"},{"id":"c3","text":["Resumption signal","The notice directs users to set an account-page alert.","bybit-zig"],"sourceIds":["bybit-zig"],"risk":"low"},{"id":"c4","text":["Internal movement","Wallet maintenance can create large venue-controlled onchain transfers.","bybit-wallet"],"sourceIds":["bybit-wallet"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"gprob-rddtb-bstocks-tokenized-equity-collateral-eligibility-and-risk-boundaries","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-18T05:40:00.000Z","updatedAt":"2026-09-18T05:40:00Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"GPROB and RDDTB bStocks: Tokenized-Equity Collateral Eligibility and Risk Boundaries","zh-Hans":"GPROB 与 RDDTB bStocks：代币化股票抵押资格与风险边界"},"summary":{"en":"Binance's September 16 listing materials identify GoPro (GPROB) and Reddit (RDDTB) bStocks as tokenized securities added for spot or convert access and as collateral in specified margin modes for eligible users.","zh-Hans":"Binance 9月16日材料将 GoPro（GPROB）与 Reddit（RDDTB）bStocks 描述为新增现货或兑换访问并可在特定保证金模式下作为抵押品的代币化证券，仅面向合资格用户。这不意味着它们就是普通股票、全球可用资产或可借抵押品。决策仍需核对批准的发行文件、司法辖区、账户等级、代币权利、抵押率、指数方法和强平后果。"},"claims":[{"id":"c1","text":["Assets","The Binance registry names GoPro GPROB and Reddit RDDTB bStocks.","binance-list"],"sourceIds":["binance-list"],"risk":"medium"},{"id":"c2","text":["Collateral","Binance materials describe the two tokens as collateral assets in specified account modes.","binance-two"],"sourceIds":["binance-two"],"risk":"medium"},{"id":"c3","text":["Jurisdiction","The announcement limits bStocks availability to eligible users in permitted jurisdictions.","binance-two"],"sourceIds":["binance-two"],"risk":"low"},{"id":"c4","text":["Models","Investor.gov distinguishes issuer-sponsored, custodial and synthetic tokenized securities.","investor-tokenized"],"sourceIds":["investor-tokenized"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-24-hour-equities-trading-clearing-surveillance-resiliency-readiness-framework","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-18T05:40:00.000Z","updatedAt":"2026-09-18T05:40:00Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"SEC 24-Hour Equities Trading: Clearing, Surveillance and Resiliency Readiness Framework","zh-Hans":"SEC 24小时股票交易：清算、监控与韧性准备框架"},"summary":{"en":"The SEC's September 17 roundtable framed expanded equities trading as an infrastructure program, not merely longer market hours.","zh-Hans":"SEC 9月17日圆桌会议把延长股票交易视为基础设施计划，而不仅是延长开市时间。议程分别讨论券商准备、隔夜监控、收盘价流程、清算结算、投资者保护、系统容量、故障切换、网络安全、人员配置、流动性与发行人公司行动。当前讲话描述市场正走向每周五天、每天23小时，而24x7仍属于未来扩展议题。"},"claims":[{"id":"c1","text":["Agenda","The roundtable covered readiness, surveillance, closing prices, clearing, settlement and investor protection.","sec-roundtable"],"sourceIds":["sec-roundtable"],"risk":"medium"},{"id":"c2","text":["Resiliency","A panel addressed Regulation SCI, failover, capacity, market data, maintenance windows, cybersecurity and staffing.","sec-roundtable"],"sourceIds":["sec-roundtable"],"risk":"medium"},{"id":"c3","text":["Issuer impact","Chair Atkins invited feedback on corporate actions, material information and EDGAR filing hours.","sec-atkins"],"sourceIds":["sec-atkins"],"risk":"low"},{"id":"c4","text":["Evidence","The staff memorandum presents descriptive overnight NMS stock activity and audit-trail measures.","sec-memo"],"sourceIds":["sec-memo"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-bstocks-collateral-vs-sec-tokenized-securities-venue-market-function-comparison","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-18T02:39:50.000Z","updatedAt":"2026-09-18T02:39:50Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Binance bStocks Collateral vs SEC Tokenized Securities Venue: Market-Function Comparison","zh-Hans":"Binance bStocks 抵押品与 SEC 代币化证券平台：市场功能对比"},"summary":{"en":"A bStocks collateral program and an SEC Tokenized Securities Venue solve different jobs.","zh-Hans":"bStocks 抵押品计划与 SEC 代币化证券平台解决不同问题。前者决定合资格代币化证券能否在平台特定的资格、估值与折扣规则下支持保证金义务；后者是通过许可制 AMM 流动性池交易代币化 NMS 股票的临时、有条件框架。用户必须分别核对资产权利、交易准入、抵押价值、借贷支持、强平、发行人异议和全市场停牌，不能把任一标签当作完整产品。"},"claims":[{"id":"c1","text":["Function","Binance describes BNCB as eligible collateral in specified margin modes; the SEC describes TSVs as trading venues using permissioned AMM liquidity pools.","binance-bncb"],"sourceIds":["binance-bncb","sec-release"],"risk":"medium"},{"id":"c2","text":["Eligibility","Binance limits the feature to VIP 3 or above in permitted jurisdictions.","binance-bncb"],"sourceIds":["binance-bncb"],"risk":"medium"},{"id":"c3","text":["Borrowing","The Binance announcement says borrowing BNCB is not currently supported.","binance-bncb"],"sourceIds":["binance-bncb"],"risk":"low"},{"id":"c4","text":["Rights","The SEC condition requires tokenized NMS stock to provide the same rights and privileges as the equivalent traditional class.","sec-release"],"sourceIds":["sec-release"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-september-18-margin-pair-removal-settlement-order-cancellation-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-18T02:39:50.000Z","updatedAt":"2026-09-18T02:39:50Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Binance September 18 Margin Pair Removal: Settlement and Order-Cancellation Checklist","zh-Hans":"Binance 9月18日保证金交易对移除：结算与撤单检查清单"},"summary":{"en":"Binance scheduled selected USDC margin pairs for removal at 06:00 UTC on September 18, 2026.","zh-Hans":"Binance 计划于 2026年9月18日 06:00 UTC 移除部分 USDC 保证金交易对。比标题更重要的是操作顺序：转入限制先开始，逐仓借贷更早暂停，移除窗口会平仓、结算负债并取消挂单。用户应在截止前核对具体账户模式、负债、抵押余额与未成交订单，并在完成后复核。"},"claims":[{"id":"c1","text":["Pairs","The notice names ENJ/USDC, GENIUS/USDC, CVX/USDC, GUN/USDC and VANA/USDC for cross margin, and GENIUS/USDC for isolated margin.","binance-removal"],"sourceIds":["binance-removal"],"risk":"medium"},{"id":"c2","text":["Borrowing","Isolated margin borrowing for the named isolated pair was scheduled to stop on September 16 at 06:00 UTC.","binance-removal"],"sourceIds":["binance-removal"],"risk":"medium"},{"id":"c3","text":["Removal","At September 18 06:00 UTC, Binance says it will close positions, settle automatically and cancel pending orders.","binance-removal"],"sourceIds":["binance-removal"],"risk":"low"},{"id":"c4","text":["Other pairs","The base and quote assets may remain available through other margin pairs.","binance-removal"],"sourceIds":["binance-removal"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bstocks-tokenized-security-collateral-eligibility-index-haircut-liquidation-readiness","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-18T02:39:50.000Z","updatedAt":"2026-09-18T02:39:50Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"bStocks Tokenized-Security Collateral: Eligibility, Index, Haircut and Liquidation Readiness","zh-Hans":"bStocks 代币化证券抵押品：资格、指数、折扣与强平准备"},"summary":{"en":"Using a tokenized security as margin collateral creates a layered exposure: legal rights in the token, jurisdiction and account eligibility, collateral-index methodology, collateral ratio or haircut, margin-level calculations.","zh-Hans":"把代币化证券用作保证金抵押品会形成多层风险：代币法律权利、司法辖区与账户资格、抵押指数方法、抵押率或折扣、保证金水平计算以及强平规则。Binance 的 BNCB 公告称，该资产在特定保证金模式下可作为抵押品，仅面向获准司法辖区的 VIP 3 及以上用户，同时目前不支持借入。因此用户必须核对实时抵押率和账户页面，不能把现货可用等同于抵押或借贷支持。"},"claims":[{"id":"c1","text":["Collateral modes","BNCB was added to Cross Margin, Portfolio Margin and Portfolio Margin Pro as collateral.","binance-bncb"],"sourceIds":["binance-bncb"],"risk":"medium"},{"id":"c2","text":["Eligibility","The feature is limited to VIP 3 or above users in permitted jurisdictions.","binance-bncb"],"sourceIds":["binance-bncb"],"risk":"medium"},{"id":"c3","text":["Borrowing boundary","The announcement says borrowing is not currently supported.","binance-bncb"],"sourceIds":["binance-bncb"],"risk":"low"},{"id":"c4","text":["Structure","Investor.gov distinguishes issuer-sponsored, custodial and synthetic tokenized-security models.","investor-tokenized"],"sourceIds":["investor-tokenized"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-margin-pair-delisting-borrow-transfer-settlement-order-cancellation-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-18T02:39:50.000Z","updatedAt":"2026-09-18T02:39:50Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Margin-Pair Delisting Radar: Borrow, Transfer, Settlement and Order-Cancellation Disclosures","zh-Hans":"加密保证金交易对下架雷达：借贷、转账、结算与撤单披露"},"summary":{"en":"A margin-pair delisting should be tracked as a state machine, not one deadline. The useful disclosure sequence is: announcement, transfer restriction, borrowing suspension, user-action deadline, automatic position closure.","zh-Hans":"保证金交易对下架应被当作状态机，而不是单一截止时间。有效披露顺序包括：公告、转入限制、借贷暂停、用户操作截止、自动平仓、负债结算、撤单、处理窗口、未受影响服务恢复以及事件后账户证据。NexuAlpha 雷达分别标记每个状态，避免把交易对移除误解为资产全面下架，也避免把公开公告当作账户已完成对账的证明。"},"claims":[{"id":"c1","text":["Multiple states","The removal notice separates transfer restrictions, borrowing suspension, closure, settlement and order cancellation.","binance-removal"],"sourceIds":["binance-removal"],"risk":"medium"},{"id":"c2","text":["Account modes","The notice distinguishes cross-margin pairs from isolated-margin pairs.","binance-removal"],"sourceIds":["binance-removal"],"risk":"medium"},{"id":"c3","text":["Processing window","Binance says users cannot update positions during a process that may take approximately three hours.","binance-removal"],"sourceIds":["binance-removal"],"risk":"low"},{"id":"c4","text":["Pair versus asset","The notice says base and quote assets may remain available in other margin pairs.","binance-removal"],"sourceIds":["binance-removal"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-tokenized-nms-stock-innovation-exemption-five-year-conditions-comment-roadmap","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-18T02:39:50.000Z","updatedAt":"2026-09-18T02:39:50Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Tokenized-Stock Innovation Exemption: Five-Year Conditions and Comment Roadmap","zh-Hans":"SEC 代币化股票创新豁免：五年期限、条件与意见路线图"},"summary":{"en":"The SEC's September 17 innovation exemption is temporary and conditional, not a blanket approval of tokenized stock markets.","zh-Hans":"SEC 9月17日发布的创新豁免是临时且有条件的，并非对代币化股票市场的全面批准。合资格的代币化证券平台可在代币数量与成交量限制、同等权利核验、发行人通知与异议、公开可审计智能合约、同步停牌和公开披露等条件下使用许可制 AMM 流动性池。豁免将在发布五年后到期，SEC 同时征求意见并考虑长期规则。"},"claims":[{"id":"c1","text":["Temporary relief","The SEC describes the relief as temporary and conditional.","sec-release"],"sourceIds":["sec-release"],"risk":"medium"},{"id":"c2","text":["Trading model","TSVs may bring buyers and sellers together through permissioned AMM liquidity pools.","sec-release"],"sourceIds":["sec-release"],"risk":"medium"},{"id":"c3","text":["Protection conditions","Conditions include symbol and volume limits, same rights, issuer objection, auditable public smart contracts and synchronized halts.","sec-release"],"sourceIds":["sec-release"],"risk":"low"},{"id":"c4","text":["Expiry","The exemptions are set to expire five years after publication and the order solicits public comment.","sec-release"],"sourceIds":["sec-release"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-september-22-system-upgrade-login-2fa-transfer-service-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-17T23:41:56.000Z","updatedAt":"2026-09-17T23:41:56Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Binance September 22 System Upgrade: Login, 2FA and Transfer Checklist","zh-Hans":"Binance 9月22日系统升级：登录、2FA 与转账检查清单"},"summary":{"en":"Binance schedules a system upgrade from 06:00 to 09:00 UTC on September 22, 2026, with an estimated duration of at least three hours.","zh-Hans":"Binance 将系统升级安排在 2026 年 9 月 22 日 06:00 至 09:00 UTC，预计至少持续三小时。平台提醒登录、注册、双重认证、充值、划转、提现与支付可能出现间歇性错误，同时表示现货与期货交易应不受影响。用户与自动化运营方应提前建立已认证会话，避免紧急转账，保留备用认证方式，把交易状态与账户访问状态分开，并等待确认恢复，而不是重复提交操作。"},"claims":[{"id":"c1","text":"Binance schedules the upgrade from 06:00 to 09:00 UTC on September 22, 2026.","sourceIds":["binance-upgrade"],"risk":"medium"},{"id":"c2","text":"The estimated duration is at least three hours.","sourceIds":["binance-upgrade"],"risk":"medium"},{"id":"c3","text":"Login, registration, 2FA or MFA, deposits, transfers, withdrawals and payments may show intermittent errors.","sourceIds":["binance-upgrade"],"risk":"low"},{"id":"c4","text":"Binance states that core Spot and Futures trading will not be affected.","sourceIds":["binance-upgrade"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"circle-arc-mainnet-launch-validator-usdc-finality-institutional-readiness","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-17T23:41:56.000Z","updatedAt":"2026-09-17T23:41:56Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Circle Arc Mainnet Launch: Validators, USDC Finality and Institutional Readiness","zh-Hans":"Circle Arc 主网上线：验证者、USDC 终局性与机构准备"},"summary":{"en":"Circle announced Arc public mainnet on September 16, 2026, describing native integration with USDC and its broader platform, a founding institutional validator cohort, more than 100 applications and more than 100 institutional.","zh-Hans":"Circle 于 2026 年 9 月 16 日宣布 Arc 公共主网上线，并描述其与 USDC 及 Circle 平台原生集成、机构级创始验证者群体、超过 100 个应用和超过 100 家机构与生态建设者。上线指标不能证明每种工作负载都已具备生产准备度。机构在迁移支付或代币化资产前，应核验验证者治理、客户端与合约版本、USDC Gas 资金、确定性终局假设、隐私配置、跨链桥与交易所支持、密钥管理、监控、事件响应与退出路径。"},"claims":[{"id":"c1","text":"Circle announced Arc public mainnet on September 16, 2026.","sourceIds":["circle-arc-launch"],"risk":"medium"},{"id":"c2","text":"Circle describes USDC as the native gas token and Arc as designed for stablecoin-native financial applications.","sourceIds":["circle-arc-launch","circle-arc-design"],"risk":"medium"},{"id":"c3","text":"The launch announcement cites more than 100 applications and more than 100 institutional and ecosystem builders.","sourceIds":["circle-arc-launch"],"risk":"low"},{"id":"c4","text":"Circle describes a founding validator cohort drawn from financial institutions and ecosystem participants.","sourceIds":["circle-arc-launch"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtc-tokenization-service-vs-sec-tokenized-securities-venue-market-function-comparison","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-17T23:41:56.000Z","updatedAt":"2026-10-11T13:30:00.000Z","readTime":"8 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Order 34-106402 (TSV) vs DTC Tokenization Service","zh-Hans":"DTC 代币化服务与 SEC 代币化证券平台：市场功能对比"},"summary":{"en":"SEC Order 34-106402 defines a Tokenized Securities Venue as a permissioned AMM venue for tokenized NMS stock; DTC's service covers post-trade records.","zh-Hans":"DTC 代币化服务与 SEC 的代币化证券平台框架解决不同市场功能。DTC 正在受监管的交易后系统内开发合格证券记录、注册钱包与生命周期处理基础设施；SEC 临时豁免下的 TSV 则是使用自动做市商流动性池交易代币化 NMS 股票的许可式交易场所。机构必须分别映射发行、所有权记录、托管、交易、价格形成、清算、结算、公司行动与停牌，不能把任一标签当作完整端到端市场栈。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"DTCC announced development milestones for DTC's tokenization service and an industry working group of more than 50 firms.","sourceIds":["dtcc-service"],"risk":"medium"},{"id":"c2","text":"DTC participants are expected to register digital wallets for blockchains on which they receive tokenized assets.","sourceIds":["dtcc-faq"],"risk":"medium"},{"id":"c3","text":"The SEC order defines a TSV as a permissioned venue using one or more AMM liquidity pools for tokenized NMS stock.","sourceIds":["sec-order"],"risk":"low"},{"id":"c4","text":"The DTC service and TSV framework cover different parts of the securities lifecycle.","sourceIds":["dtcc-service","dtcc-faq","sec-order"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"dtc-tokenization-service-wallet-registration-lifecycle-operational-readiness","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-17T23:41:56.000Z","updatedAt":"2026-09-17T23:41:56Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"DTC Tokenization Service: Wallet Registration and Lifecycle Readiness","zh-Hans":"DTC 代币化服务：钱包注册与生命周期准备"},"summary":{"en":"DTCC's DTC tokenization program is designed to extend regulated securities processing to tokenized representations while retaining participant controls and lifecycle obligations.","zh-Hans":"DTCC 的 DTC 代币化项目旨在把受监管证券处理扩展到代币化表示，同时保留参与者控制与生命周期义务。实施材料表示，参与者需要为接收代币化资产的每条支持区块链注册钱包。因此，准备工作要求钱包所有权证据、密钥治理、地址审批、资产资格、权益对账、公司行动处理、转让限制、账簿记录、事件恢复，以及分布式账本与现有参与者系统之间经过测试的桥接。"},"claims":[{"id":"c1","text":"DTCC convened more than 50 firms in an industry working group for the service.","sourceIds":["dtcc-service"],"risk":"medium"},{"id":"c2","text":"DTCC described initial limited production activity and a planned broader service launch in 2026.","sourceIds":["dtcc-service","dtcc-timeline"],"risk":"medium"},{"id":"c3","text":"Participants are expected to register digital wallets for each blockchain used to receive tokenized assets.","sourceIds":["dtcc-faq"],"risk":"low"},{"id":"c4","text":"The service is intended to operate within existing regulated securities processing and participant responsibilities.","sourceIds":["dtcc-service","dtcc-faq"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-system-upgrade-login-auth-transfer-trading-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-17T23:41:56.000Z","updatedAt":"2026-09-17T23:41:56Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange System-Upgrade Disclosure Radar: Login, Authentication, Transfers and Trading","zh-Hans":"交易所系统升级披露雷达：登录、认证、转账与交易"},"summary":{"en":"NexuAlpha's system-upgrade radar separates ten service planes: login, registration, authentication, trading UI, order APIs, deposits, withdrawals, internal transfers, payments and post-window recovery.","zh-Hans":"NexuAlpha 系统升级雷达把服务分成十个平面：登录、注册、认证、交易界面、订单 API、充值、提现、内部划转、支付与窗口后恢复。Binance 9 月 22 日公告说明这种区分的重要性：现货与期货可能继续交易，而账户访问与资金移动功能出现间歇性错误。Kraken 的组件状态历史同样把 API 连接与资金网关分开。有效公告应针对每个受影响平面说明范围、UTC 窗口、预计时长、重试指引与恢复证据。"},"claims":[{"id":"c1","text":"A platform upgrade can affect authentication and transfers while core trading continues.","sourceIds":["binance-upgrade"],"risk":"medium"},{"id":"c2","text":"Binance identifies an at-least-three-hour upgrade window and lists affected service groups.","sourceIds":["binance-upgrade"],"risk":"medium"},{"id":"c3","text":"Kraken publishes component-specific status notices for API and funding functions.","sourceIds":["kraken-status"],"risk":"low"},{"id":"c4","text":"A general HTTP 200 or usable homepage does not prove that every service plane works.","sourceIds":["binance-upgrade","kraken-status"],"risk":"low"}],"relatedVenues":["binance","kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-onchain-activity-measurement-transaction-aggregation-smart-contract-crosschain-radar","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-17T20:40:01.000Z","updatedAt":"2026-09-17T20:40:01Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"BIS Onchain Activity Measurement: Transaction, Smart-Contract and Crosschain Radar","zh-Hans":"BIS 链上活动测量：交易、智能合约与跨链雷达"},"summary":{"en":"BIS Working Paper 1377 warns that simple onchain totals can mix economic activity with technical artefacts.","zh-Hans":"BIS 第 1377 号工作论文提醒，简单链上总量可能把经济活动与技术性痕迹混在一起。论文识别三类主要测量分歧：如何聚合区块链交易、可编程智能合约如何产生或转换事件，以及如何跨链比较活动。NexuAlpha 雷达因此要求在把任何数字称为用户、支付或经济交易量之前，明确观察单位、地址与合约分类、内部转账处理、跨链桥逻辑、去重、价格与时间基准、链覆盖、归因置信度与可复现查询。"},"claims":[{"id":"c1","text":"BIS published Working Paper 1377 on September 15, 2026.","sourceIds":["bis-paper","bis-pdf"],"risk":"medium"},{"id":"c2","text":"The paper studies transfer values, token issuance, decentralized-exchange activity and stablecoin holdings.","sourceIds":["bis-paper","bis-pdf"],"risk":"medium"},{"id":"c3","text":"It says simple aggregations can mix economic activity with technical artefacts.","sourceIds":["bis-paper","bis-pdf"],"risk":"low"},{"id":"c4","text":"The paper identifies transaction aggregation, smart-contract programmability and crosschain comparability as sources of measurement divergence.","sourceIds":["bis-paper","bis-pdf","bis-annual"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-1000xec-blast-gun-kgen-rpl-b2-risk-limit-buffer-liquidation-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-17T20:40:01.000Z","updatedAt":"2026-09-17T20:40:01Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit 1000XEC, BLAST, GUN, KGEN, RPL and B2 Risk Limits: Buffer Checklist","zh-Hans":"Bybit 1000XEC、BLAST、GUN、KGEN、RPL 与 B2 风险限额：缓冲清单"},"summary":{"en":"Bybit says new risk limits and leverage settings for six USDT perpetual contracts begin applying around 07:30 UTC on September 18, 2026.","zh-Hans":"Bybit 表示六个 USDT 永续合约的新风险限额与杠杆设置将在 2026 年 9 月 18 日 07:30 UTC 左右开始应用。无法满足新保证金要求的仓位可能进入只减仓状态，直到用户选择受支持设置。缓冲期于 10 月 5 日 07:30 UTC 结束后，不兼容仓位可能面临强平风险，平台也保留提前结束缓冲期的权利。跟单与交易机器人仓位同样在范围内，用户应在截止前重算保证金、补充资金或降低敞口。"},"claims":[{"id":"c1","text":"Bybit lists six affected perpetual contracts: 1000XECUSDT, BLASTUSDT, GUNUSDT, KGENUSDT, RPLUSDT and B2USDT.","sourceIds":["bybit-risk"],"risk":"medium"},{"id":"c2","text":"The adjustment begins around 07:30 UTC on September 18, 2026.","sourceIds":["bybit-risk"],"risk":"medium"},{"id":"c3","text":"Accounts that cannot satisfy the new requirement may be restricted to reducing the affected position.","sourceIds":["bybit-risk","bybit-risk-guide"],"risk":"low"},{"id":"c4","text":"The buffer period is scheduled to end at 07:30 UTC on October 5, 2026, but may end early under risk controls.","sourceIds":["bybit-risk"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-brazil-entity-migration-kyc-liquidation-fiat-conversion-deadline-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-17T20:40:01.000Z","updatedAt":"2026-09-17T20:40:01Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit Brazil Entity Migration: KYC, Liquidation and Fiat-Conversion Deadlines","zh-Hans":"Bybit 巴西实体迁移：KYC、强平与法币转换截止清单"},"summary":{"en":"Bybit's Brazil notice says affected eligible residents and companies may migrate to a local entity.","zh-Hans":"Bybit 巴西公告表示，受影响且符合条件的居民与企业可能迁移到本地实体。公告设定 2026 年 9 月 21 日的执行措施，可能包括强制平仓、把不支持的法币余额转换为 USDT，以及作废不合规优惠券或奖励；9 月 24 日则是已完成验证并接受条款的合格用户迁移完成日。用户必须以个人通知为准，核验居住地与实体范围，有计划地关闭或转移仓位，导出记录，并确认 BRL 与活体验证要求。"},"claims":[{"id":"c1","text":"Bybit's notice describes migration of eligible Brazilian residents and companies to a local entity.","sourceIds":["bybit-brazil"],"risk":"medium"},{"id":"c2","text":"Enforcement actions are scheduled for September 21, 2026.","sourceIds":["bybit-brazil"],"risk":"medium"},{"id":"c3","text":"Potential actions include force-liquidation, unsupported fiat conversion to USDT and forfeiture of non-compliant benefits.","sourceIds":["bybit-brazil"],"risk":"low"},{"id":"c4","text":"Migration completion is scheduled for September 24 for eligible users who complete verification and accept applicable terms.","sourceIds":["bybit-brazil","bybit-kyc"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"circle-cpn-managed-payments-stablecoin-settlement-responsibility-model","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-17T20:40:01.000Z","updatedAt":"2026-09-17T20:40:01Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Circle CPN Managed Payments: Stablecoin Settlement Responsibility Model","zh-Hans":"Circle CPN 托管支付：稳定币结算责任模型"},"summary":{"en":"Circle presents CPN Managed Payments as a turnkey service that lets partners use familiar fiat workflows while Circle handles on- and off-ramps, wallets, liquidity, payment orchestration, compliance and blockchain infrastructure.","zh-Hans":"Circle 将 CPN 托管支付描述为一站式服务，让合作伙伴继续使用熟悉的法币流程，同时由 Circle 处理出入金、钱包、流动性、支付编排、合规与区块链基础设施。这种抽象并不会消除责任地图的必要性。采购方应识别持牌提供方、面向客户的实体、结算资产、账户与钱包归属、筛查职责、汇率逻辑、预融资、交易终局性、异常处理、对账、数据可移植性，以及从全托管迁移到混合基础设施的路径。"},"claims":[{"id":"c1","text":"Circle describes CPN Managed Payments as an all-in-one stablecoin settlement offering.","sourceIds":["circle-managed"],"risk":"medium"},{"id":"c2","text":"Circle says the service covers on- and off-ramps, wallets, liquidity, orchestration, compliance and blockchain infrastructure.","sourceIds":["circle-managed","circle-cpn"],"risk":"medium"},{"id":"c3","text":"Partners can continue interacting through familiar fiat workflows without directly handling digital assets.","sourceIds":["circle-managed"],"risk":"low"},{"id":"c4","text":"Circle describes a path from fully managed service toward hybrid or composable infrastructure over time.","sourceIds":["circle-managed","circle-cpn"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-prime-api-maintenance-vs-blockchain-funding-delay-status-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-17T20:40:01.000Z","updatedAt":"2026-09-17T20:40:01Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken Prime API Maintenance vs Blockchain Funding Delay: Status Controls","zh-Hans":"Kraken Prime API 维护与区块链资金延迟：状态控制对比"},"summary":{"en":"Kraken's status page separates scheduled Prime API maintenance from blockchain funding incidents.","zh-Hans":"Kraken 状态页把计划内 Prime API 维护与区块链资金事件分开。短时 WebSocket 或 FIX 中断影响 API 客户端连接，而资金延迟可能让链上已确认充值尚未计入账户，或延迟特定网络的充提。用户不能根据交易界面可用推断钱包健康，也不能根据链上转账成功推断 API 正常。判断时应核对组件范围、事件状态、受影响资产、时间戳、交易标识、对账状态与官方恢复更新。"},"claims":[{"id":"c1","text":"Kraken scheduled Prime WebSocket and FIX API maintenance for September 17, 2026.","sourceIds":["kraken-status"],"risk":"medium"},{"id":"c2","text":"The maintenance notice described a short connectivity interruption for the affected APIs.","sourceIds":["kraken-status","kraken-api-docs"],"risk":"medium"},{"id":"c3","text":"Separate status incidents described delayed funding or deposits not yet credited to account balances.","sourceIds":["kraken-status","kraken-funding-guide"],"risk":"low"},{"id":"c4","text":"A component-specific status incident does not prove that unrelated exchange components are unavailable.","sourceIds":["kraken-status"],"risk":"low"}],"relatedVenues":["kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-brev-cookie-la-qnt-usdc-spot-pair-removal-bot-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-17T17:40:02.000Z","updatedAt":"2026-09-17T17:40:02Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Binance BREV, COOKIE, LA and QNT USDC Pair Removal: Bot Checklist","zh-Hans":"Binance BREV、COOKIE、LA 与 QNT USDC 交易对移除：机器人检查清单"},"summary":{"en":"Binance says BREV/USDC, COOKIE/USDC, LA/USDC and QNT/USDC spot pairs will cease trading at 03:00 UTC on September 18, 2026, and applicable Spot Trading Bots will terminate at the same time.","zh-Hans":"Binance 表示 BREV/USDC、COOKIE/USDC、LA/USDC 与 QNT/USDC 现货交易对将在 2026 年 9 月 18 日 03:00 UTC 停止交易，适用的现货交易机器人也将在同一时间终止。移除交易对不等于下架代币：基础资产与报价资产仍可能通过其他交易对可用。用户应在截止前取消或更新机器人，检查未成交订单，映射替代交易对，评估兑换与价差成本，导出记录，并单独核验代币实时充提状态。"},"claims":[{"id":"c1","text":"Binance scheduled removal of four USDC spot pairs for 03:00 UTC on September 18, 2026.","sourceIds":["binance-removal"],"risk":"medium"},{"id":"c2","text":"The affected pairs are BREV/USDC, COOKIE/USDC, LA/USDC and QNT/USDC.","sourceIds":["binance-removal"],"risk":"medium"},{"id":"c3","text":"Applicable Spot Trading Bots will terminate at the same cutoff.","sourceIds":["binance-removal"],"risk":"low"},{"id":"c4","text":"Binance states that pair removal does not by itself remove the base or quote tokens from Binance Spot.","sourceIds":["binance-removal","binance-delisting-list"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-collateral-ratio-change-borrow-transfer-unimmr-liquidation-radar","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-17T17:40:02.000Z","updatedAt":"2026-09-17T17:40:02Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Collateral-Ratio Change Radar: Borrow, Transfer, uniMMR and Liquidation","zh-Hans":"Binance 抵押率变更雷达：借款、转出、uniMMR 与强平"},"summary":{"en":"Binance scheduled collateral-ratio changes for 06:00 UTC on September 18, 2026. ARB, TAO and WLD rise from 50% to 60%, while AUCTION, BLUR, GALA, HYPER, S and SYRUP fall from 30% to 10%; WLFI Portfolio Margin Pro tiers also.","zh-Hans":"Binance 将抵押率调整安排在 2026 年 9 月 18 日 06:00 UTC。 ARB、TAO 与 WLD 从 50% 提高到 60%，AUCTION、BLUR、GALA、HYPER、S 与 SYRUP 从 30% 降到 10%，WLFI 的 Portfolio Margin Pro 分层也发生变化。 NexuAlpha 雷达把影响分成四类：全仓保证金借款能力、可转出能力、投资组合保证金抵押价值，以及 uniMMR 强平敏感度。"},"claims":[{"id":"c1","text":"Binance scheduled the collateral-ratio update for 06:00 UTC on September 18, 2026.","sourceIds":["binance-collateral"],"risk":"medium"},{"id":"c2","text":"ARB, TAO and WLD increase from 50% to 60%.","sourceIds":["binance-collateral"],"risk":"medium"},{"id":"c3","text":"AUCTION, BLUR, GALA, HYPER, S and SYRUP decrease from 30% to 10%.","sourceIds":["binance-collateral"],"risk":"low"},{"id":"c4","text":"Binance says Portfolio Margin collateral ratios and leverage affect uniMMR and may affect liquidation risk.","sourceIds":["binance-collateral","binance-margin-guide"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-stablecore-community-bank-digital-asset-infrastructure-responsibility-map","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-17T17:40:02.000Z","updatedAt":"2026-09-17T17:40:02Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase and Stablecore for Community Banks: Digital-Asset Responsibility Map","zh-Hans":"Coinbase 与 Stablecore 服务社区银行：数字资产责任地图"},"summary":{"en":"Coinbase says its Stablecore partnership is intended to let community and regional banks and credit unions offer custody, trading and stablecoin payments inside existing banking experiences.","zh-Hans":"Coinbase 表示其与 Stablecore 的合作旨在让社区与区域银行及信用合作社在现有银行体验中提供托管、交易与稳定币支付。Stablecore 负责核心银行、数字银行与合规系统之间的集成和编排，Coinbase 提供底层数字资产基础设施。公告描述的是可触达 3,000 多家机构的潜力，而不是所有机构已经完成部署。评估时应把客户归属、托管、执行、合规、账簿对账、事件响应、披露与退出可移植性分配给明确责任方。"},"claims":[{"id":"c1","text":"Coinbase announced the Stablecore partnership on September 16, 2026.","sourceIds":["coinbase-stablecore"],"risk":"medium"},{"id":"c2","text":"The described services include custody, trading and stablecoin payments through existing banking experiences.","sourceIds":["coinbase-stablecore"],"risk":"medium"},{"id":"c3","text":"Stablecore is described as managing integration across banking and compliance systems while Coinbase provides underlying infrastructure.","sourceIds":["coinbase-stablecore","coinbase-cdp"],"risk":"low"},{"id":"c4","text":"The announcement says the potential footprint reaches more than 3,000 banks and credit unions, not that all are live.","sourceIds":["coinbase-stablecore"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-xmeta-vs-sec-tokenized-nms-stock-rights-ownership-comparison","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-17T17:40:02.000Z","updatedAt":"2026-09-17T17:40:02Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"OKX xMETA vs SEC Tokenized NMS Stock: Rights and Ownership Comparison","zh-Hans":"OKX xMETA 与 SEC 代币化 NMS 股票：权利与所有权对比"},"summary":{"en":"OKX's xMETA announcement explicitly says its Tokenized Stocks provide no direct ownership or shareholder rights, while the SEC's September 17 Innovation Exemption requires a tokenized NMS stock traded by a qualifying Tokenized.","zh-Hans":"OKX 的 xMETA 公告明确说明其代币化股票不提供直接所有权或股东权利，而 SEC 9 月 17 日创新豁免要求符合条件的代币化证券平台所交易的代币化 NMS 股票，向持有人提供与同类别传统 NMS 股票相同的权利与特权。这两类产品不能互换。用户在比较价格前，必须识别法律请求权、发行或代币化主体、股息与投票权、赎回路径、交易场所、地区资格，以及该工具究竟是证券、衍生品、凭证还是其他包装。"},"claims":[{"id":"c1","text":"OKX scheduled xMETA/USDC spot trading for 10:00 UTC on September 17, 2026.","sourceIds":["okx-xmeta"],"risk":"medium"},{"id":"c2","text":"OKX states that its Tokenized Stocks provide no direct ownership or shareholder rights.","sourceIds":["okx-xmeta"],"risk":"medium"},{"id":"c3","text":"The SEC order requires eligible tokenized NMS stock to provide the same rights and privileges as equivalent traditional NMS stock.","sourceIds":["sec-release","sec-order"],"risk":"low"},{"id":"c4","text":"The SEC exemption applies to permissioned trading through qualifying Tokenized Securities Venues and is temporary and conditional.","sourceIds":["sec-release","sec-order"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-tokenized-nms-stock-innovation-exemption-rights-controls-and-limits","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-17T17:40:02.000Z","updatedAt":"2026-09-17T17:40:02Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Tokenized NMS Stock Innovation Exemption: Rights, Controls and Limits","zh-Hans":"SEC 代币化 NMS 股票创新豁免：权利、控制与限制"},"summary":{"en":"The SEC's September 17, 2026 order creates temporary, conditional relief for Tokenized Securities Venues using permissioned automated market maker pools to trade tokenized NMS stocks.","zh-Hans":"SEC 2026 年 9 月 17 日的命令为使用许可式自动做市商流动性池交易代币化 NMS 股票的代币化证券平台提供临时、有条件的豁免。关键保护包括代码与成交量限制、同等股东权利、第三方代币化时给予发行人通知与反对机会、可审计的公开智能合约、同步停牌和公开运营披露。该命令不会让所有代币化股票产品自动合规，也不取消反欺诈规则，并将在公布五年后到期，除非框架发生变化。"},"claims":[{"id":"c1","text":"The SEC issued the temporary conditional exemption on September 17, 2026.","sourceIds":["sec-release","sec-order"],"risk":"medium"},{"id":"c2","text":"Qualifying TSVs use permissioned participants and AMM liquidity pools for tokenized NMS stock.","sourceIds":["sec-release","sec-order"],"risk":"medium"},{"id":"c3","text":"Eligible tokens must provide the same rights and privileges as the equivalent traditional NMS stock.","sourceIds":["sec-release","sec-order","sec-atkins"],"risk":"low"},{"id":"c4","text":"The exemptions are set to expire five years after publication and remain subject to conditions and antifraud protections.","sourceIds":["sec-release","sec-order"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-platform-wallet-upgrade-vs-token-network-maintenance-transfer-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-17T11:42:46.000Z","updatedAt":"2026-09-17T11:42:46Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Platform Wallet Upgrade vs Token-Network Maintenance: Transfer Controls","zh-Hans":"Binance 平台钱包升级与代币网络维护：转账控制对比"},"summary":{"en":"Binance's September 22 platform wallet-system upgrade is broader than a single-token network maintenance notice: the venue says deposits and withdrawals across the platform will be suspended for about one hour from 06:00 UTC.","zh-Hans":"Binance 9 月 22 日的平台钱包系统升级比单一代币网络维护范围更广：平台表示自 06:00 UTC 起全平台充值与提现将暂停约一小时，而交易仍可进行。用户必须把交易可用性与转账可用性分开，确认实际网络和资产，在截止前预留确认时间，并等待实时充提状态恢复，不能把网页返回 200 或市场仍在交易当作转账正常的证据。"},"claims":[{"id":"c1","text":"Binance schedules the wallet-system upgrade for 06:00 UTC on September 22, 2026.","sourceIds":["binance-wallet-upgrade"],"risk":"medium"},{"id":"c2","text":"The notice says deposits and withdrawals across the platform will be suspended for about one hour.","sourceIds":["binance-wallet-upgrade"],"risk":"medium"},{"id":"c3","text":"Binance states that trading will not be affected by the wallet-system upgrade.","sourceIds":["binance-wallet-upgrade"],"risk":"low"},{"id":"c4","text":"The venue says deposits and withdrawals will reopen after the system is stable without a further announcement.","sourceIds":["binance-wallet-upgrade"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cftc-24-7-trading-clearing-settlement-operational-readiness-framework","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-17T11:42:46.000Z","updatedAt":"2026-09-17T11:42:46Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC 24/7 Trading, Clearing and Settlement: Operational-Readiness Framework","zh-Hans":"CFTC 24/7 交易、清算与结算：运营准备框架"},"summary":{"en":"The CFTC's May 29, 2026 advisory describes regulatory expectations for designated contract markets, swap execution facilities, clearing organizations and futures commission merchants considering 24/7 operations.","zh-Hans":"CFTC 2026 年 5 月 29 日的咨询文件说明了指定合约市场、掉期执行设施、清算机构与期货佣金商考虑 24/7 运营时的监管预期。文件承认连续访问可能适合数字资产市场，同时提醒产品、参与者和基础设施存在差异。可信的 24/7 模式必须让人员配置、监控、保证金、流动性、违约管理、网络韧性、供应商覆盖、客户支持与事件治理在传统营业时间之外持续运行。"},"claims":[{"id":"c1","text":"The CFTC issued the 24/7 markets advisory on May 29, 2026.","sourceIds":["cftc-247-advisory"],"risk":"medium"},{"id":"c2","text":"The advisory addresses DCMs, SEFs, DCOs and FCMs considering continuous operations.","sourceIds":["cftc-247-advisory"],"risk":"medium"},{"id":"c3","text":"The CFTC notes that 24/7 access may be suitable for digital-asset markets but not identical across asset classes.","sourceIds":["cftc-247-advisory"],"risk":"low"},{"id":"c4","text":"Continuous trading requires clearing, risk and operational controls outside traditional market hours.","sourceIds":["cftc-247-advisory","cftc-clearing"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-wallet-maintenance-disclosure-radar-cutoff-scope-reopening-evidence","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-17T11:42:46.000Z","updatedAt":"2026-09-17T11:42:46Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange Wallet-Maintenance Disclosure Radar: Cutoff, Scope and Reopening Evidence","zh-Hans":"交易所钱包维护披露雷达：截止、范围与恢复证据"},"summary":{"en":"NexuAlpha's maintenance radar treats a notice as operationally useful only when it separates ten fields: affected venue, scope, assets, networks, UTC cutoff, expected duration, deposit state, withdrawal state, trading impact and.","zh-Hans":"NexuAlpha 维护雷达只有在公告分离十项字段时才把它视为可执行信息：受影响平台、范围、资产、网络、UTC 截止、预计时长、充值状态、提现状态、交易影响与恢复证据。Binance 9 月 22 日钱包升级给出了广泛范围、截止时间、时长估计和交易影响，但恢复依赖事件而非固定时间。安全做法是在窗口后核验实时转账控制并进行小额测试，不能根据公告发布时间或首页状态推断可用性。"},"claims":[{"id":"c1","text":"Wallet maintenance can affect deposits and withdrawals while trading remains available.","sourceIds":["binance-wallet-upgrade","okx-suspension-guide"],"risk":"medium"},{"id":"c2","text":"Binance's notice gives a UTC start time and an approximate one-hour duration.","sourceIds":["binance-wallet-upgrade"],"risk":"medium"},{"id":"c3","text":"The reopening condition is system stability rather than a guaranteed clock time.","sourceIds":["binance-wallet-upgrade"],"risk":"low"},{"id":"c4","text":"A live deposit or withdrawal control is stronger operational evidence than a general site response.","sourceIds":["binance-wallet-upgrade","okx-suspension-guide"],"risk":"low"}],"relatedVenues":["binance","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-register-bybit-account-complete-kyc-and-secure-first-login","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-17T11:42:46.000Z","updatedAt":"2026-09-17T11:42:46Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"How to Register a Bybit Account, Complete KYC and Secure the First Login","zh-Hans":"如何注册 Bybit 账户、完成 KYC 并保护首次登录"},"summary":{"en":"A safe Bybit onboarding sequence is: verify that Bybit serves your jurisdiction, open the official registration page, use an email or phone number you control, create a unique password, complete the required email or SMS check.","zh-Hans":"安全的 Bybit 入门顺序是：先确认 Bybit 服务于你的司法辖区，打开官方注册页面，使用自己控制的邮箱或手机号，创建唯一密码，完成邮箱或短信验证，再用一致的国家与证件信息完成个人身份验证。充值前应启用强双重认证，检查反钓鱼与提现保护，核对账户姓名和地区，并在准确支持的网络上先做最小可行转账测试。"},"claims":[{"id":"c1","text":"Bybit supports account registration with the methods described in its official registration guide.","sourceIds":["bybit-register"],"risk":"medium"},{"id":"c2","text":"Individual verification requires country or region selection and identity information that matches the document.","sourceIds":["bybit-kyc"],"risk":"medium"},{"id":"c3","text":"Product access and verification requirements may differ by jurisdiction.","sourceIds":["bybit-kyc","bybit-getting-started"],"risk":"low"},{"id":"c4","text":"Security controls should be configured before the first deposit rather than after funds arrive.","sourceIds":["bybit-getting-started"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-register-kucoin-account-complete-identity-verification-and-secure-access","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-17T11:42:46.000Z","updatedAt":"2026-09-17T11:42:46Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"How to Register a KuCoin Account, Complete Identity Verification and Secure Access","zh-Hans":"如何注册 KuCoin 账户、完成身份验证并保护访问"},"summary":{"en":"KuCoin's official guide says users can register with an email address or phone number, verify the code and set a login password.","zh-Hans":"KuCoin 官方指南表示，用户可以用邮箱或手机号注册，验证收到的验证码并设置登录密码。新用户必须完成身份验证才能使用 KuCoin 产品与服务，流程包括选择签发国家或地区、选择证件类型、提供清晰证件图片并完成人脸验证。入金前，用户应确认地区可用性，保护邮箱或手机，启用可用账户保护，离线保存恢复信息，并用小额测试准确的充值网络。"},"claims":[{"id":"c1","text":"KuCoin's guide describes registration by email address or phone number.","sourceIds":["kucoin-register"],"risk":"medium"},{"id":"c2","text":"The registration flow includes a verification code and login-password setup.","sourceIds":["kucoin-register"],"risk":"medium"},{"id":"c3","text":"KuCoin says new users must complete Identity Verification to use its products and services.","sourceIds":["kucoin-kyc"],"risk":"low"},{"id":"c4","text":"Individual verification includes country or region selection, document images and face verification.","sourceIds":["kucoin-kyc"],"risk":"low"}],"relatedVenues":["kucoin"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-iostusd-strkusd-x-perps-launch-risk-and-availability-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-17T11:42:46.000Z","updatedAt":"2026-09-17T11:42:46Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"OKX IOSTUSD and STRKUSD X-Perps Launch: Risk and Availability Checklist","zh-Hans":"OKX IOSTUSD 与 STRKUSD X-Perps 上线：风险与可用性清单"},"summary":{"en":"OKX announced IOSTUSD and STRKUSD X-Perps for September 17, 2026, with IOST scheduled at 08:00 UTC and STRK at 08:15 UTC. Listing time does not by itself prove that a product is available in every region or appropriate for a user.","zh-Hans":"OKX 宣布于 2026 年 9 月 17 日上线 IOSTUSD 与 STRKUSD X-Perps，IOST 计划在 08:00 UTC 上线，STRK 在 08:15 UTC 上线。上线时间本身不能证明产品在所有地区都可用，也不能证明适合某个用户。交易前应核对账户司法辖区、实时工具状态、合约规格、指数来源、资金费率方法、杠杆上限、强平规则、订单簿深度，以及现货代币与衍生品仓位的区别。"},"claims":[{"id":"c1","text":"OKX scheduled IOSTUSD X-Perps for 08:00 UTC on September 17, 2026.","sourceIds":["okx-iost-strk"],"risk":"medium"},{"id":"c2","text":"OKX scheduled STRKUSD X-Perps for 08:15 UTC on September 17, 2026.","sourceIds":["okx-iost-strk"],"risk":"medium"},{"id":"c3","text":"The announcement warns that product availability may vary by region.","sourceIds":["okx-iost-strk"],"risk":"low"},{"id":"c4","text":"A perpetual derivative is a separate instrument from holding the underlying token.","sourceIds":["okx-iost-strk","okx-perpetual-guide"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"usdc-on-arc-binance-okx-network-identity-and-transfer-controls","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-17T11:42:46.000Z","updatedAt":"2026-09-17T11:42:46Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"USDC on Arc at Binance and OKX: Network Identity and Transfer Controls","zh-Hans":"Binance 与 OKX 的 Arc 网络 USDC：网络身份与转账控制"},"summary":{"en":"Binance and OKX both announced USDC support on the Arc chain on September 16, 2026, but their operational states were not identical: OKX stated that deposits and withdrawals opened at 04:00 UTC, while Binance said deposits were.","zh-Hans":"Binance 与 OKX 都在 2026 年 9 月 16 日宣布支持 Arc 链 USDC，但运营状态并不相同：OKX 表示充提在 04:00 UTC 开放，Binance 表示充值已开放，而提现将在存款充足后开放且不另行公告。因此，同一资产代码并不代表同一网络路径或转账状态。用户必须核对所选链为 Arc、平台生成的地址、合约身份、提现可用性、最低限额，并先进行小额测试。"},"claims":[{"id":"c1","text":"OKX stated that USDC deposits and withdrawals on Arc opened at 04:00 UTC on September 16, 2026.","sourceIds":["okx-usdc-arc"],"risk":"medium"},{"id":"c2","text":"Binance announced that USDC deposits on Arc were open on September 16, 2026.","sourceIds":["binance-usdc-arc"],"risk":"medium"},{"id":"c3","text":"Binance said Arc withdrawals would open after sufficient deposits without a further announcement.","sourceIds":["binance-usdc-arc"],"risk":"low"},{"id":"c4","text":"A USDC transfer must match the exact network supported by both sending and receiving services.","sourceIds":["okx-usdc-arc","binance-usdc-arc"],"risk":"low"}],"relatedVenues":["binance","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cftc-true-digital-commodity-perpetual-conversion-customer-protection-conditions","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-15T20:40:58.000Z","updatedAt":"2026-09-15T20:40:58Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC True Digital-Commodity Perpetual Conversion: Customer-Protection Conditions","zh-Hans":"CFTC 真正数字商品永续转换：客户保护条件"},"summary":{"en":"CFTC staff's June 12, 2026 no-action letter addressed designated contract markets converting existing perpetual-style digital-commodity futures into contracts without expiration dates.","zh-Hans":"CFTC 工作人员 2026 年 6 月 12 日的不行动函涉及指定合约市场把现有类永续数字商品期货转换为无到期日合约。条件包括征求持仓参与者反馈、提前通知、提供退出机会、适当风险披露、不改变其他重大条款，并按要求提交规则文件。该立场有到期日，不是对所有永续产品的全面批准。用户应核验平台、合约修订、通知、退出窗口与当前法律状态。"},"claims":[{"id":"c1","text":"CFTC staff announced the no-action letter on June 12, 2026.","sourceIds":["cftc-release","cftc-letter"],"risk":"medium"},{"id":"c2","text":"The letter addressed removal of expiration dates from existing perpetual-style digital-commodity futures.","sourceIds":["cftc-release","cftc-letter"],"risk":"medium"},{"id":"c3","text":"Conditions included participant feedback, advance notice, an exit opportunity, risk disclosures and no other material term changes.","sourceIds":["cftc-release","cftc-letter"],"risk":"low"},{"id":"c4","text":"The release says the no-action positions expired on June 30, 2026.","sourceIds":["cftc-release"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"community-bank-stablecoin-payments-custody-settlement-operating-model","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-15T20:40:58.000Z","updatedAt":"2026-09-15T20:40:58Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Community-Bank Stablecoin Payments: Custody and Settlement Operating Model","zh-Hans":"社区银行稳定币支付：托管与结算运营模型"},"summary":{"en":"Coinbase says Moov is integrating Coinbase stablecoin payment infrastructure for a network serving more than 1,000 community banks and credit unions.","zh-Hans":"Coinbase 表示 Moov 正在为其服务的 1,000 多家社区银行与信用合作社网络集成 Coinbase 稳定币支付基础设施。所述模型使用托管钱包账户与支付 API，支持接收、结算、实时资金调拨和付款。机构评估时应把客户关系与托管、编排分开，并记录发行方风险、法律请求权、钱包隔离、交易授权、结算终局性、对账、事件响应与退出可移植性。"},"claims":[{"id":"c1","text":"Coinbase says Moov serves more than 1,000 community banks and credit unions.","sourceIds":["coinbase-moov","coinbase-blog"],"risk":"medium"},{"id":"c2","text":"The partnership describes stablecoin acceptance, settlement and real-time funding.","sourceIds":["coinbase-moov"],"risk":"medium"},{"id":"c3","text":"Moov is described as using Coinbase custodial wallet accounts and Payments API.","sourceIds":["coinbase-moov","coinbase-payments"],"risk":"low"},{"id":"c4","text":"The announced use cases include consumer payments, merchant acceptance, settlement and payouts.","sourceIds":["coinbase-moov"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-token-contract-swap-suspension-reopening-address-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-15T20:40:58.000Z","updatedAt":"2026-09-15T20:40:58Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange Token Contract Swaps: Suspension, Reopening and Address Disclosure Radar","zh-Hans":"交易所代币合约置换：暂停、恢复与地址披露雷达"},"summary":{"en":"NexuAlpha's contract-swap radar requires ten fields before a migration notice is operationally complete: affected chain, old and new contract identifiers, ticker mapping, swap ratio, suspension cutoff, deposit-credit rule.","zh-Hans":"NexuAlpha 合约置换雷达要求迁移公告至少覆盖十项：受影响链、新旧合约标识、代码映射、置换比例、暂停截止、充值入账规则、交易影响、恢复触发、外部钱包兼容性与置换后测试流程。Binance 的 Optimism USDT 公告覆盖其中多项，但恢复仍依赖后续公告。这个未知必须明确保留；用户不能因为交易继续就发送资金。"},"claims":[{"id":"c1","text":"A contract swap can change token identifiers while leaving other exchange services available.","sourceIds":["binance-swap"],"risk":"medium"},{"id":"c2","text":"Binance's notice identifies a 1:1 swap and maps the new token to USDT0 and the old token to OPUSDTE.","sourceIds":["binance-swap","binance-swap-uk"],"risk":"medium"},{"id":"c3","text":"The notice gives a suspension time but says reopening will be announced separately.","sourceIds":["binance-swap"],"risk":"low"},{"id":"c4","text":"Continued trading does not prove that deposits or withdrawals are available.","sourceIds":["binance-swap","binance-maintenance"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-usdg-rlusd-daily-rewards-balance-calculation-update-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-15T20:40:58.000Z","updatedAt":"2026-09-15T20:40:58Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"OKX USDG and RLUSD Daily Rewards: Balance-Calculation Update Checklist","zh-Hans":"OKX USDG 与 RLUSD 每日奖励：余额计算更新检查清单"},"summary":{"en":"OKX says USDG and RLUSD reward payouts move from weekly to daily on September 21, 2026, with new calculation rules from September 22.","zh-Hans":"OKX 表示 USDG 与 RLUSD 奖励将于 2026 年 9 月 21 日从每周发放改为每日发放，并于 9 月 22 日启用新计算规则。交易账户合格余额取币种余额与币种权益的较低值，每日合格余额则取指定账户在快照期间记录的最低合计余额。公式使用适用 APR 除以 365，而非广告 APY。用户必须核对地区资格、当前费率、账户范围、快照窗口与奖励币种。"},"claims":[{"id":"c1","text":"OKX says daily payouts start on September 21, 2026.","sourceIds":["okx-rewards"],"risk":"medium"},{"id":"c2","text":"Updated calculation rules start on September 22, 2026.","sourceIds":["okx-rewards"],"risk":"medium"},{"id":"c3","text":"Eligible trading-account balance is the lower of coin balance and coin equity.","sourceIds":["okx-rewards"],"risk":"low"},{"id":"c4","text":"The daily reward formula uses applicable APR divided by 365, which differs from advertised APY.","sourceIds":["okx-rewards","okx-apr-apy"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"optimism-usdt0-vs-opusdte-after-binance-contract-swap-user-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-15T20:40:58.000Z","updatedAt":"2026-09-15T20:40:58Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Optimism USDT0 vs OPUSDTE After Binance's Contract Swap: User Controls","zh-Hans":"Binance 合约置换后的 Optimism USDT0 与 OPUSDTE：用户控制对比"},"summary":{"en":"After Binance's planned Optimism USDT contract swap, the new Optimism USDT is identified as USDT0 while the old contract assumes the OPUSDTE ticker.","zh-Hans":"Binance 计划完成 Optimism USDT 合约置换后，新版 Optimism USDT 标识为 USDT0，旧合约则使用 OPUSDTE 代码。平台称按 1:1 置换，并自 2026 年 9 月 17 日 02:00 UTC 起暂时停止 Optimism 网络充值与提现，而现货、保证金、期货与 Earn 不受影响。用户必须比较合约地址、代码、网络路径、钱包支持与恢复状态，熟悉的 USDT 名称不足以判断正确代币。"},"claims":[{"id":"c1","text":"Binance plans to suspend Optimism-network USDT deposits and withdrawals at 02:00 UTC on September 17, 2026.","sourceIds":["binance-swap","binance-swap-uk"],"risk":"medium"},{"id":"c2","text":"The notice states that the contract swap ratio is 1:1.","sourceIds":["binance-swap"],"risk":"medium"},{"id":"c3","text":"After completion, the new Optimism USDT is identified as USDT0 and the old token as OPUSDTE.","sourceIds":["binance-swap","binance-swap-uk"],"risk":"low"},{"id":"c4","text":"Binance says spot, margin, futures and Earn services are not affected during the swap.","sourceIds":["binance-swap"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cftc-self-custodial-wallet-no-action-letter-scope-user-boundary","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-15T17:40:19.000Z","updatedAt":"2026-09-15T17:40:19Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"CFTC Self-Custodial Wallet No-Action Letter: Scope and User Boundary","zh-Hans":"CFTC 自托管钱包不行动函：适用范围与用户边界"},"summary":{"en":"CFTC staff's March 17, 2026 no-action position concerns a specified Phantom software model facilitating user access to registered futures intermediaries and markets.","zh-Hans":"CFTC 工作人员 2026 年 3 月 17 日的不行动立场针对 Phantom 某一特定软件模式，该模式帮助用户接入受注册的期货中介与市场。在满足列明条件时，工作人员不会仅因这些活动未注册为介绍经纪商或相关人员而建议执法。这不是牌照、规则、普遍钱包豁免或安全背书。用户与开发者必须把实际托管、推荐、订单处理、收费和市场关系逐项对照函件条件。"},"claims":[{"id":"c1","text":"CFTC staff announced the no-action position on March 17, 2026.","sourceIds":["cftc-release","cftc-letter"],"risk":"medium"},{"id":"c2","text":"The request involved Phantom Technologies and self-custodial wallet software facilitating access to registered futures entities.","sourceIds":["cftc-release","cftc-letter"],"risk":"medium"},{"id":"c3","text":"Subject to conditions, staff would not recommend enforcement for failure to register as an introducing broker or associated person solely for the described activities.","sourceIds":["cftc-release","cftc-letter"],"risk":"low"},{"id":"c4","text":"The letter includes boundaries involving recommendations, order solicitation, fee relationships and trading privileges.","sourceIds":["cftc-letter"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-spot-listing-timeline-deposit-trading-withdrawal-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-15T17:40:19.000Z","updatedAt":"2026-09-15T17:40:19Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Spot Listing Timeline: Deposit, Trading and Withdrawal Disclosure Radar","zh-Hans":"加密现货上线时间线：充值、交易与提现披露雷达"},"summary":{"en":"NexuAlpha's listing-timeline radar scores whether a venue separates deposit, pre-open, trading and withdrawal milestones; identifies the exact network and token contract; explains launch price controls.","zh-Hans":"NexuAlpha 上线时间线雷达评估平台是否分别披露充值、预开盘、交易和提现节点，是否识别准确网络与代币合约，是否解释上线限价、地区资格并提供实时状态路径。OKX 的 VVV 公告是可用案例，因为它发布了四个 UTC 节点及指数限价规则。但再完整的公告，也不能替代操作当时对登录钱包和订单界面的核验。"},"claims":[{"id":"c1","text":"Venue listing announcements can separate wallet and market milestones rather than opening every function simultaneously.","sourceIds":["okx-vvv","binance-listings"],"risk":"medium"},{"id":"c2","text":"OKX's VVV notice publishes deposits, pre-open, trading and withdrawals as four distinct UTC events.","sourceIds":["okx-vvv"],"risk":"medium"},{"id":"c3","text":"The notice applies index-based price limits during pre-open and continuous trading.","sourceIds":["okx-vvv"],"risk":"low"},{"id":"c4","text":"Official announcement indexes are discovery surfaces; live authenticated controls remain necessary for execution.","sourceIds":["okx-announcements","binance-listings"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"leveraged-etf-x-perp-vs-standard-equity-perpetual-stacked-leverage-risk","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-15T17:40:19.000Z","updatedAt":"2026-09-15T17:40:19Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Leveraged-ETF X-Perp vs Standard Equity Perpetual: Stacked-Leverage Risk","zh-Hans":"杠杆 ETF X-Perp 与普通股票永续对比：叠加杠杆风险"},"summary":{"en":"A leveraged-ETF-linked perpetual can stack derivative leverage on top of an underlying fund that already targets leveraged or inverse daily exposure.","zh-Hans":"杠杆 ETF 挂钩永续可能把衍生品杠杆叠加在本身已追求每日杠杆或反向敞口的基金之上。这不同于普通股票挂钩永续，后者的参考对象本身通常不是每日重置的杠杆基金。OKX 的 KORUUSD 公告明确警告，额外杠杆会放大敞口、清算风险与损失。交易者应把基金每日重置、路径依赖、合约杠杆、资金费率、标记价格与清算缓冲放在同一模型中。"},"claims":[{"id":"c1","text":"OKX says KORUUSD UM X-Perp opened at 09:00 UTC on September 15, 2026.","sourceIds":["okx-koru"],"risk":"medium"},{"id":"c2","text":"OKX states that KORU tracks a fund already providing daily leveraged or inverse exposure.","sourceIds":["okx-koru"],"risk":"medium"},{"id":"c3","text":"OKX warns that applying leverage to the X-Perp can further amplify exposure, liquidation risk and losses.","sourceIds":["okx-koru"],"risk":"low"},{"id":"c4","text":"SEC investor materials warn that daily-reset leveraged and inverse ETFs can diverge materially from the stated multiple over periods longer than one day.","sourceIds":["sec-leveraged-etf"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-vvv-usdt-spot-listing-preopen-price-limit-transfer-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-15T17:40:19.000Z","updatedAt":"2026-09-15T17:40:19Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"OKX VVV/USDT Listing: Pre-Open, Price-Limit and Transfer Checklist","zh-Hans":"OKX VVV/USDT 上线：预开盘、限价与转账检查清单"},"summary":{"en":"OKX's VVV/USDT notice separates deposits, pre-open, continuous trading and withdrawals into four scheduled stages on September 15, 2026.","zh-Hans":"OKX 的 VVV/USDT 公告把 2026 年 9 月 15 日的充值、预开盘、连续交易和提现分成四个阶段：充值 07:00 UTC 开放，预开盘 13:00 至 14:00，现货交易 14:00 开放，提现 16:00 开放。平台还在预开盘与连续交易阶段应用指数限价。操作前应核对地区资格、实时代码、合约地址、钱包网络与当前订单控制。"},"claims":[{"id":"c1","text":"OKX published the VVV/USDT spot listing notice on September 15, 2026.","sourceIds":["okx-vvv","okx-announcements"],"risk":"medium"},{"id":"c2","text":"The notice scheduled deposits for 07:00 UTC, pre-open for 13:00-14:00, trading for 14:00 and withdrawals for 16:00.","sourceIds":["okx-vvv"],"risk":"medium"},{"id":"c3","text":"OKX says index-based price-limit rules apply during pre-open and continuous trading.","sourceIds":["okx-vvv"],"risk":"low"},{"id":"c4","text":"The notice says availability can differ by region and must be checked in the app.","sourceIds":["okx-vvv"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"payment-stablecoin-margin-collateral-issuer-eligibility-custody-haircut-framework","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-15T17:40:19.000Z","updatedAt":"2026-09-15T17:40:19Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Payment Stablecoins as Margin Collateral: Issuer, Custody and Haircut Framework","zh-Hans":"支付稳定币作为保证金抵押品：发行方、托管与折扣框架"},"summary":{"en":"CFTC Staff Letter 26-05 reissued prior no-action relief with a limited revision that can include a national trust bank as a permitted payment-stablecoin issuer for the specified margin-collateral framework.","zh-Hans":"CFTC 工作人员函 26-05 重新发布此前的不行动立场，并作有限修订，使国家信托银行在特定保证金抵押品框架下可成为许可支付稳定币发行方。这是附条件的工作人员立场，不是对所有稳定币或账户的全面批准。可决策审查仍必须确认准确发行方、赎回请求权、储备证据、FCM 接受情况、隔离、托管、估值折扣、集中度上限与清算流程。"},"claims":[{"id":"c1","text":"CFTC Staff Letter 26-05 was issued on February 6, 2026.","sourceIds":["cftc-26-05"],"risk":"medium"},{"id":"c2","text":"The letter reissues prior relief with a limited revision to the payment-stablecoin issuer definition.","sourceIds":["cftc-26-05"],"risk":"medium"},{"id":"c3","text":"The revision specifies that a national trust bank may be a permitted issuer for purposes of that no-action position.","sourceIds":["cftc-26-05"],"risk":"low"},{"id":"c4","text":"CFTC staff FAQs provide additional guidance on digital assets accepted as margin collateral.","sourceIds":["cftc-faq","cftc-faq-pdf"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-okx-spot-pair-removal-order-cancellation-migration-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-15T11:39:24.000Z","updatedAt":"2026-09-15T11:39:24Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs OKX Spot-Pair Removals: Order Cancellation and Migration Controls","zh-Hans":"Binance 与 OKX 现货交易对移除对比：撤单与迁移控制"},"summary":{"en":"A removed spot pair is not necessarily a delisted asset, and the two events require different actions.","zh-Hans":"现货交易对被移除不一定等于资产被下架，两种事件需要不同处理。Binance 与 OKX 公告会列出受影响交易对、执行时间和订单处理，但用户还必须单独确认基础资产能否通过其他计价币继续交易，以及充值或提现是否仍然开放。安全顺序是盘点未成交订单与机器人，在平台截止前主动撤单，选择已核验的替代交易对或托管路径，并在变更后对账。"},"claims":[{"id":"c1","text":"Binance and OKX publish pair-removal notices through official announcement channels.","sourceIds":["binance-announcements","okx-announcements"],"risk":"medium"},{"id":"c2","text":"OKX says selected USD pairs will be removed at 08:00 UTC on September 18, 2026.","sourceIds":["okx-usd-delisting"],"risk":"medium"},{"id":"c3","text":"OKX advises users to cancel affected orders before the deadline and says remaining orders will otherwise be canceled by the system.","sourceIds":["okx-usd-delisting"],"risk":"low"},{"id":"c4","text":"Pair removal does not by itself prove that the underlying asset, deposits or withdrawals are unavailable.","sourceIds":["binance-announcements","okx-usd-delisting"],"risk":"low"}],"relatedVenues":["binance","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"institutional-stablecoin-cash-management-governance-controls-radar","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-15T11:39:24.000Z","updatedAt":"2026-09-15T11:39:24Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Institutional Stablecoin Cash Management: Governance Controls Radar","zh-Hans":"机构稳定币现金管理：治理控制雷达"},"summary":{"en":"Coinbase and EY-Parthenon's 2026 survey reports that 85% of respondents use or are interested in stablecoins for internal cash management and money movement.","zh-Hans":"Coinbase 与 EY-Parthenon 的 2026 年调查称，85% 的受访者已经使用或有兴趣使用稳定币进行内部现金管理和资金流转。NexuAlpha 雷达把这一需求信号转化为十项控制：许可发行方与链、储备证据、直接赎回、托管、交易授权、地址控制、会计、流动性窗口、事件响应与集中度限制。兴趣不等于批准，价格稳定也不能证明赎回能力、运营韧性或法律请求权质量。"},"claims":[{"id":"c1","text":"The 2026 Coinbase and EY-Parthenon survey covered 351 institutional investors.","sourceIds":["coinbase-ey"],"risk":"medium"},{"id":"c2","text":"The survey reports 85% use or are interested in stablecoins for internal cash management and money movement.","sourceIds":["coinbase-ey"],"risk":"medium"},{"id":"c3","text":"The BIS says stablecoin outcomes depend on reserve composition, use, regulation and interactions with bank funding and capital flows.","sourceIds":["bis-aer","bis-release"],"risk":"low"},{"id":"c4","text":"The BIS assesses singleness, elasticity and financial integrity as foundational monetary-system properties.","sourceIds":["bis-aer","bis-release"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-pendleusd-x-perp-launch-contract-risk-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-15T11:39:24.000Z","updatedAt":"2026-09-15T11:39:24Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"OKX PENDLEUSD X-Perp Launch: Contract and Risk Checklist","zh-Hans":"OKX PENDLEUSD X-Perp 上线：合约与风险检查清单"},"summary":{"en":"OKX announced that PENDLEUSD UM X-Perp trading opened at 08:00 UTC on September 15, 2026, subject to regional availability. The listing notice is not a complete trading specification.","zh-Hans":"OKX 公告称 PENDLEUSD UM X-Perp 已于 2026 年 9 月 15 日 08:00 UTC 开放交易，并受地区可用性限制。上线公告不是完整交易规格。下单前，用户应在登录后的实时产品界面确认准确代码、合约面值、结算币种、指数与标记价格方法、资金费率周期、仓位档位、保证金模式、限价和清算缓冲。"},"claims":[{"id":"c1","text":"OKX published the PENDLEUSD X-Perp announcement on September 15, 2026.","sourceIds":["okx-pendle","okx-announcements"],"risk":"medium"},{"id":"c2","text":"The announcement says PENDLEUSD UM X-Perp trading opened at 08:00 UTC that day.","sourceIds":["okx-pendle"],"risk":"medium"},{"id":"c3","text":"OKX says users must check product availability in their region through the app.","sourceIds":["okx-pendle"],"risk":"low"},{"id":"c4","text":"OKX perpetual documentation describes mark price, funding and leverage as distinct contract controls.","sourceIds":["okx-perpetual"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-cftc-crypto-asset-interpretation-token-taxonomy-user-boundary","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-15T11:39:24.000Z","updatedAt":"2026-09-15T11:39:24Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"SEC-CFTC Crypto Interpretation: Token Taxonomy and the User Decision Boundary","zh-Hans":"SEC-CFTC 加密资产解释：代币分类与用户决策边界"},"summary":{"en":"The March 17, 2026 SEC-CFTC interpretation addresses how federal securities laws apply to certain crypto assets and transactions and how the CFTC will administer the Commodity Exchange Act consistently.","zh-Hans":"2026 年 3 月 17 日 SEC-CFTC 联合解释讨论联邦证券法如何适用于部分加密资产与交易，以及 CFTC 如何一致执行《商品交易法》。文件提出数字商品、数字收藏品、数字工具、稳定币和数字证券等分类，并说明非证券加密资产仍可能参与投资合同。用户不能只凭代币标签判断产品性质；交易安排、承诺、管理工作、封装方式、平台和当前法律文件仍然关键。"},"claims":[{"id":"c1","text":"The CFTC joined the SEC interpretation on March 17, 2026.","sourceIds":["cftc-joint","cftc-interpretation"],"risk":"medium"},{"id":"c2","text":"The interpretation addresses the security definition as applied to crypto assets and related transactions.","sourceIds":["cftc-joint","cftc-interpretation"],"risk":"medium"},{"id":"c3","text":"The agency summary lists digital commodities, collectibles, tools, stablecoins and digital securities in its taxonomy.","sourceIds":["cftc-joint"],"risk":"low"},{"id":"c4","text":"It says a non-security crypto asset may become subject to, and later cease to be subject to, an investment contract.","sourceIds":["cftc-joint","cftc-interpretation"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"tokenized-collateral-acceptance-reuse-rehypothecation-risk-framework","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-15T11:39:24.000Z","updatedAt":"2026-09-15T11:39:24Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Tokenized Collateral Acceptance and Reuse: A Rehypothecation Risk Framework","zh-Hans":"代币化抵押品接纳与再使用：再质押风险框架"},"summary":{"en":"Accepting a tokenized Treasury, stablecoin or other digital asset as margin collateral does not settle whether it can be reused, who bears custody risk or how quickly it can be liquidated.","zh-Hans":"把代币化国债、稳定币或其他数字资产接纳为保证金抵押品，并不能回答它能否被再使用、谁承担托管风险，或压力下能否快速变现。CFTC 工作人员材料涉及受监管实体处理和代币化抵押条件，Coinbase 研究则描述代币化基金作为链上抵押品的增长用途。可靠框架应把资格、估值折扣、法律所有权、隔离、再质押授权、流动性、赎回、预言机回退与破产处理分开。"},"claims":[{"id":"c1","text":"CFTC staff issued FAQs on registrant and registered-entity activities involving crypto assets and blockchain technologies.","sourceIds":["cftc-faq","cftc-faq-pdf"],"risk":"medium"},{"id":"c2","text":"The FAQs reference prior tokenized-collateral guidance and a no-action position concerning digital assets accepted as margin collateral.","sourceIds":["cftc-faq","cftc-faq-pdf"],"risk":"medium"},{"id":"c3","text":"Coinbase research says tokenized Treasury and money-market products are increasingly used as onchain collateral.","sourceIds":["coinbase-tokenization"],"risk":"low"},{"id":"c4","text":"Collateral eligibility, reuse authority and enforceable ownership remain separate questions.","sourceIds":["cftc-faq-pdf","coinbase-tokenization"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-bybit-network-upgrade-deposit-withdrawal-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-15T08:42:22.000Z","updatedAt":"2026-09-15T08:42:22Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs Bybit Network Upgrades: Deposit and Withdrawal Control Checklist","zh-Hans":"Binance 与 Bybit 网络升级对比：充值提现控制清单"},"summary":{"en":"Binance and Bybit both publish network-upgrade notices, but a notice is only the starting point.","zh-Hans":"Binance 与 Bybit 都会发布网络升级公告，但公告只是起点。真正影响操作的，是受影响链、暂停时间、充值入账截止、提现恢复规则、交易是否继续，以及登录后钱包页面的实时状态。用户不能因为交易界面可用，就推断链上转账可用。安全流程应保存官方公告，在转账前重新核对充值和提现控件，先做小额测试，并在确认到账后再发送余款。"},"claims":[{"id":"c1","text":"Both venues maintain official announcement channels for network upgrades and wallet maintenance.","sourceIds":["binance-maintenance","bybit-maintenance"],"risk":"medium"},{"id":"c2","text":"A network maintenance notice can suspend deposits and withdrawals while trading remains available.","sourceIds":["binance-maintenance","bybit-maintenance"],"risk":"medium"},{"id":"c3","text":"Bybit directs users to verify coin-specific deposit and withdrawal status rather than relying only on an announcement.","sourceIds":["bybit-deposit-status"],"risk":"low"},{"id":"c4","text":"Reopening language and timing can differ by event, so the live authenticated wallet control is the final operational check.","sourceIds":["binance-maintenance","bybit-maintenance","bybit-deposit-status"],"risk":"low"}],"relatedVenues":["binance","bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"institutional-tokenization-demand-vs-operational-readiness-gap-2026","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-15T08:42:22.000Z","updatedAt":"2026-09-15T08:42:22Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Institutional Tokenization Demand vs Operational Readiness: The 2026 Gap","zh-Hans":"机构代币化需求与运营准备度：2026 年差距分析"},"summary":{"en":"Institutional interest in tokenization is now measurable, but interest is not implementation readiness.","zh-Hans":"机构对代币化的兴趣已经可以量化，但兴趣不等于实施准备度。Coinbase 与 EY-Parthenon 对 351 名机构投资者的 2026 年调查显示，64% 的资产管理机构有兴趣将资产代币化，63% 有兴趣配置代币化资产。运营差距仍集中在法律请求权、托管、权威所有权记录、流动性、预言机、转让限制、公司行动、结算终局性与互操作性。机构应先把调查热度转化为分阶段的运营模型，再配置资本。"},"claims":[{"id":"c1","text":"The 2026 Coinbase and EY-Parthenon survey covers 351 institutional investors.","sourceIds":["coinbase-ey-survey"],"risk":"medium"},{"id":"c2","text":"The survey reports 64% of asset managers are interested in tokenizing assets and 63% are interested in allocating to tokenized assets.","sourceIds":["coinbase-ey-survey"],"risk":"medium"},{"id":"c3","text":"Coinbase's tokenization analysis identifies market depth, oracle design and regulatory fragmentation as continuing constraints.","sourceIds":["coinbase-tokenization-trends"],"risk":"low"},{"id":"c4","text":"SEC staff distinguishes issuer-sponsored, custodial third-party and synthetic tokenization structures because rights and intermediary risks differ.","sourceIds":["sec-tokenized"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-new-perpetual-listing-contract-risk-verification-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-15T08:42:22.000Z","updatedAt":"2026-09-15T08:42:22Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"OKX New Perpetual Listings: Contract, Index and Risk Verification Checklist","zh-Hans":"OKX 新永续合约上线：合约、指数与风险核验清单"},"summary":{"en":"A new OKX perpetual listing should be treated as a new risk configuration, not merely a new ticker.","zh-Hans":"OKX 新永续合约上线应被视为一套新的风险配置，而不只是新增代码。当前公告索引可以确认上线事件，但最小变动单位、合约面值、结算资产、指数构成、资金费率周期、杠杆档位和限价控制，必须以实时产品页与合约文档为准。交易者应在上线后逐项核验，按维持保证金而非页面显示的最高杠杆确定仓位；若指数或合约身份无法独立匹配，就应停止操作。"},"claims":[{"id":"c1","text":"OKX's announcement index is the official discovery surface for newly listed perpetual instruments.","sourceIds":["okx-announcements"],"risk":"medium"},{"id":"c2","text":"OKX perpetual futures use mark-price and funding mechanisms that are distinct from ordinary spot trading.","sourceIds":["okx-perpetual"],"risk":"medium"},{"id":"c3","text":"Position tiers can change maximum leverage and initial or maintenance margin as exposure grows.","sourceIds":["okx-position-tiers"],"risk":"low"},{"id":"c4","text":"The live instrument rules after launch are controlling because specifications and eligibility can change.","sourceIds":["okx-announcements","okx-perpetual","okx-position-tiers"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-crypto-vault-lending-strategies-securities-boundary-user-checklist","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-15T08:42:22.000Z","updatedAt":"2026-09-15T08:42:22Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Crypto Vault and Lending Strategies: A Securities-Boundary Checklist","zh-Hans":"SEC 加密金库与借贷策略：证券属性边界检查清单"},"summary":{"en":"An SEC statement on crypto vaults and lending strategies is analytical guidance, not a blanket approval or final rule.","zh-Hans":"SEC 关于加密金库与借贷策略的声明属于分析性立场，不是全面批准，也不是最终规则。证券属性判断仍取决于具体事实：用户必须识别谁控制资产、承诺哪些管理工作、收益如何产生、回报是否依赖第三方、适用哪些托管与再质押条款，以及损失由哪些披露和合同请求权约束。vault、earn、lending 或 DeFi 等产品名称不能决定法律分类，也不能消除交易对手风险。"},"claims":[{"id":"c1","text":"The SEC crypto newsroom publishes statements and releases that can have different legal weight.","sourceIds":["sec-crypto-newsroom"],"risk":"medium"},{"id":"c2","text":"A commissioner or staff statement does not by itself create a final rule or approve every product described by a similar label.","sourceIds":["sec-vault-lending","sec-crypto-newsroom"],"risk":"medium"},{"id":"c3","text":"Vault and lending analysis depends on the actual contractual arrangement, control and managerial efforts rather than branding alone.","sourceIds":["sec-vault-lending"],"risk":"low"},{"id":"c4","text":"Custody, intermediary, disclosure and insolvency questions remain separate from the classification analysis.","sourceIds":["sec-vault-lending","sec-tokenized"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"tokenized-asset-disclosure-completeness-rights-custody-redemption-radar","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-15T08:42:22.000Z","updatedAt":"2026-09-15T08:42:22Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Tokenized-Asset Disclosure Radar: Rights, Custody and Redemption Completeness","zh-Hans":"代币化资产披露雷达：权利、托管与赎回完整度"},"summary":{"en":"NexuAlpha's disclosure radar treats a tokenized asset as decision-ready only when a user can identify the legal issuer, underlying asset, authoritative ownership record, custody chain, economic and governance rights, pricing method, transfer restrictions, redemption route, corporate-action process and insolvency treatment.","zh-Hans":"NexuAlpha 的披露雷达仅在用户能够识别法律发行人、底层资产、权威所有权记录、托管链、经济与治理权利、定价方法、转让限制、赎回路径、公司行动流程和破产处理时，才把代币化资产视为可决策对象。价格图和代码远远不够。把这十项标准应用于任何平台页面，可以暴露缺失证据，而不会把熟悉品牌、HTTP 200 或链上代币误当成可执行请求权。"},"claims":[{"id":"c1","text":"SEC staff says the same tokenization label can cover issuer-sponsored, custodial and synthetic models.","sourceIds":["sec-tokenized"],"risk":"medium"},{"id":"c2","text":"Third-party structures can add intermediary and bankruptcy risks beyond direct ownership of the reference asset.","sourceIds":["sec-tokenized"],"risk":"medium"},{"id":"c3","text":"Coinbase research notes that some tokenized-equity products are derivatives or offshore economic exposure rather than direct ownership.","sourceIds":["coinbase-tokenization-trends"],"risk":"low"},{"id":"c4","text":"OKX discloses that its Unified Tokenized Stocks provide linked economic exposure and can have product-specific collateral and risk treatment.","sourceIds":["okx-unified-stocks"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-create-coinbase-account-verify-identity-securely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-15T05:36:13.878Z","updatedAt":"2026-09-15T05:36:13.878Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"How to Create a Coinbase Account and Verify Identity Securely","zh-Hans":"如何安全创建 Coinbase 账户并完成身份验证"},"summary":{"en":"Begin at Coinbase's official domain, choose the correct individual or business account type, and use contact details you control for the long term.","zh-Hans":"从 Coinbase 官方域名开始，选择正确的个人或企业账户类型，并使用自己能够长期控制的联系方式。Coinbase 当前的新客户指南把创建账户、身份验证、添加支付方式与两步验证分成不同阶段；身份验证说明要求用户从登录后的账户核对请求，并确保上传证件的页面属于 Coinbase 自有域名。姓名应与平台接受的政府证件一致，材料只能通过实时官方流程提交，不要把证件通过邮件发送。审核通过不代表所有资产、支付路径或产品都可用；任何小额测试交易以前，都应先确认登录后的账户状态并完成安全加固。"},"claims":[{"id":"c1","text":"Coinbase's new-customer guide separates account creation, identity verification, payment-method setup and two-step verification.","sourceIds":["coinbase-new-customer"],"risk":"medium"},{"id":"c2","text":"The guide says individual account creation begins with email verification and asks for a name matching government-issued identification.","sourceIds":["coinbase-new-customer"],"risk":"medium"},{"id":"c3","text":"Coinbase says identity-verification requests appear in the app or signed-in browser and warns users to check the account before following email links.","sourceIds":["coinbase-identity"],"risk":"low"},{"id":"c4","text":"Coinbase says identity documents sent by email are not accepted and document pages should use Coinbase-owned domains.","sourceIds":["coinbase-identity"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-create-kraken-account-complete-verification-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-15T05:36:13.878Z","updatedAt":"2026-09-15T05:36:13.878Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"How to Create a Kraken Account and Complete Verification Safely","zh-Hans":"如何安全创建 Kraken 账户并完成身份验证"},"summary":{"en":"Open Kraken by typing its official domain, create the account with a durable email address and unique password, accept the terms only after reading them, and activate the account through the official activation email or key.","zh-Hans":"手动输入 Kraken 官方域名，使用长期可控邮箱与唯一密码创建账户，阅读条款后再接受，并通过官方激活邮件或激活密钥完成账户激活。Kraken 当前验证指南说明，完成所需身份流程后才可使用相应资金与交易功能，而且表单会因地区而异。应在登录后填写验证表，只上传实时页面要求的政府身份证件，并在完成后检查本账户的验证等级与限额。地区限制和账户特定要求不会因为注册成功而消失。入金前先启用强验证方式，确认资产与网络以后仅做小额、受支持的转账测试。"},"claims":[{"id":"c1","text":"Kraken instructs users to confirm they are visiting the official kraken.com site before account creation.","sourceIds":["kraken-create"],"risk":"medium"},{"id":"c2","text":"Kraken's account guide describes email activation with an activation key or official email link.","sourceIds":["kraken-create"],"risk":"medium"},{"id":"c3","text":"Kraken says identity verification enables relevant funding and trading functions and that the verification screen may differ by location.","sourceIds":["kraken-verify"],"risk":"low"},{"id":"c4","text":"Kraken says users can review their verification level and transaction limits inside account settings.","sourceIds":["kraken-verify"],"risk":"low"}],"relatedVenues":["kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-open-binance-account-complete-identity-verification-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-15T05:36:13.878Z","updatedAt":"2026-09-15T05:36:13.878Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"How to Open a Binance Account and Complete Identity Verification Safely","zh-Hans":"如何安全注册 Binance 账户并完成身份验证"},"summary":{"en":"Use only Binance's official website or installed app, confirm that the service is available for the country where you ordinarily reside, create the account with a long-term email address or phone number you control, and complete the identity flow shown inside the authenticated account.","zh-Hans":"只使用 Binance 官方网站或已安装 App，先确认平台是否服务于本人通常居住的国家或地区，再使用自己长期控制的邮箱或手机号创建账户，并在登录后的官方流程中完成身份验证。Binance 当前新手指南说明注册可使用邮箱、手机号、Apple 或 Google，身份验证则是另一道流程，可能涉及个人信息、身份证件与人脸验证。注册成功不代表所有产品都可用。入金前应先加固账户安全，所有验证材料只在官方流程中提交，并在账户状态与网络都清楚以后仅做小额、受支持的充值或提现测试。"},"claims":[{"id":"c1","text":"Binance's updated beginner guide lists account registration, identity verification, funding and trading as separate onboarding stages.","sourceIds":["binance-beginner"],"risk":"medium"},{"id":"c2","text":"The guide says an account can be registered through the app or website using email, phone, Apple or Google.","sourceIds":["binance-beginner"],"risk":"medium"},{"id":"c3","text":"Binance says identity verification may require basic information, identity documentation and facial verification.","sourceIds":["binance-beginner"],"risk":"low"},{"id":"c4","text":"Binance says an account without identity verification is usually restricted from full access to platform features.","sourceIds":["binance-identity"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-register-bitget-account-complete-identity-verification","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-15T05:36:13.878Z","updatedAt":"2026-09-15T05:36:13.878Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"How to Register a Bitget Account and Complete Identity Verification","zh-Hans":"如何注册 Bitget 账户并完成身份验证"},"summary":{"en":"Download Bitget only from its official page or use the official website, then register with an email address or mobile number you control and a unique password.","zh-Hans":"只从 Bitget 官方页面下载 App 或使用官方网站，再通过本人控制的邮箱或手机号以及唯一密码注册。Bitget 当前移动端指南描述了邮箱或手机注册、六位验证码和可选推荐信息；身份验证指南则把注册与证件、人脸验证分开。推荐码属于可选字段，不能让促销覆盖资格、安全或费用检查。应在登录后的验证页面选择证件签发国家与材料类型，通过该流程提交清晰、未编辑的证件，并只在其中完成人脸识别。等待登录后账户或官方站内信的结果，加固账户安全，并在任何小额受支持转账前确认实际产品可用性。"},"claims":[{"id":"c1","text":"Bitget's mobile registration guide says users may register with an email address or mobile number and receive a six-digit verification code.","sourceIds":["bitget-register"],"risk":"medium"},{"id":"c2","text":"The guide describes the referral code as optional and recommends enabling two-factor authentication after registration.","sourceIds":["bitget-register"],"risk":"medium"},{"id":"c3","text":"Bitget's identity guide says users select the issuing country or region and document type before uploading identification.","sourceIds":["bitget-identity"],"risk":"low"},{"id":"c4","text":"The identity guide says submitted document images must clearly show required information and must not be edited, followed by facial recognition and a review result.","sourceIds":["bitget-identity"],"risk":"low"}],"relatedVenues":["bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-register-okx-account-verify-identity-safely","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-15T05:36:13.878Z","updatedAt":"2026-10-13T05:00:00.000Z","readTime":"9 min","readTimeByLocale":{"en":"9 min","zh-Hans":"9 min"},"author":"NexuAlpha Research Desk","title":{"en":"OKX Account Verification (2026): KYC in 5 Steps","zh-Hans":"如何安全注册 OKX 账户并完成身份验证"},"summary":{"en":"Verify your OKX account in 5 steps: official app or site, home region, email and phone, a unique password, then ID checks. See what KYC unlocks first.","zh-Hans":"只通过 OKX 官方网站或 App 注册，并选择本人当前且通常居住的国家或地区。OKX 注册指南说明居住地可能决定签约服务实体与可用功能，同时明确注册或身份验证成功不保证所有产品都能使用。应使用本人控制的邮箱和手机号，只在实时会话中输入验证码，创建唯一密码，并从登录后的个人资料或账户设置完成个人身份验证。不要通过选择其他地区绕过不可用选项。审核完成后，应检查账户实际显示的产品与限额，启用强验证方式，并在核对收发两端以后仅做小额、受支持的资金测试。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"OKX says users should select the country or region where they currently and ordinarily reside rather than using nationality alone.","sourceIds":["okx-register"],"risk":"medium"},{"id":"c2","text":"OKX's registration guide describes email and phone verification and says each email address and phone number can register only one account.","sourceIds":["okx-register"],"risk":"medium"},{"id":"c3","text":"OKX warns that successful registration or identity verification does not guarantee access to every trading product.","sourceIds":["okx-register"],"risk":"low"},{"id":"c4","text":"OKX says individual verification is started from the signed-in verification page on the web or Identity Verification inside app account settings.","sourceIds":["okx-verify"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"binance-bncb-bstocks-spot-listing-redemption-eligibility-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-15T02:36:57.301Z","updatedAt":"2026-09-15T02:36:57.301Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Binance BNCB bStocks Listing: Redemption, Eligibility and Trading Checklist","zh-Hans":"Binance BNCB bStocks 上线：赎回、资格与交易检查清单"},"summary":{"en":"Binance announced BNCB/USDT spot and Convert availability for eligible users on September 14, 2026, together with a separate collateral update.","zh-Hans":"Binance 公告称 BNCB/USDT 现货与 Convert 已于 2026 年 9 月 14 日向合格用户开放，并另行发布抵押品更新。该产品属于代币化证券工具，并非直接持有 CEA Industries 股票，且存在地区限制。交易前应核对登录后的产品页、发行条款、合约地址、赎回路径、公司行动处理、提现网络和当前费用。"},"claims":[{"id":"c1","text":"Binance announced the BNCB/USDT bStocks trading pair for September 14, 2026, subject to eligibility and jurisdiction.","sourceIds":["binance-bncb-listing"],"risk":"medium"},{"id":"c2","text":"Binance's announcement says bStocks are not direct stocks or shares and do not by themselves make the holder a shareholder of the referenced company.","sourceIds":["binance-bncb-listing","binance-bstocks"],"risk":"medium"},{"id":"c3","text":"Binance published a separate notice adding BNCB as collateral in selected margin account modes while stating that borrowing is not currently supported.","sourceIds":["binance-bncb-collateral"],"risk":"low"},{"id":"c4","text":"Product availability, redemption mechanics, fees and network status must be checked on the live authenticated interface because announcement terms can change.","sourceIds":["binance-bncb-listing","binance-bncb-collateral"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-pay-onchain-b402-agent-payments-business-readiness","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-15T02:36:57.301Z","updatedAt":"2026-09-15T02:36:57.301Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Pay Onchain and B402 Agent Payments: A Business Readiness Framework","zh-Hans":"Binance Pay Onchain 与 B402 智能体支付：企业准备度框架"},"summary":{"en":"Binance announced a business-facing Pay Onchain suite on September 14, 2026 covering on-ramp, onchain funding and B402 agent payments built around x402.","zh-Hans":"Binance 于 2026 年 9 月 14 日公布面向企业的 Pay Onchain 套件，涵盖入金、链上充值以及围绕 x402 构建的 B402 智能体支付。该公告提供了集成路径，但不能证明所有企业、资产或地区均已上线。企业在生产使用前应评估链与资产覆盖、托管、钱包策略、逐笔授权、结算证据、KYT/KYC 边界、退款、定价与运营支持。"},"claims":[{"id":"c1","text":"Binance's September 14 announcement describes On-ramp as a Service, Pay On-chain and Agent Pay with x402 as separate business solution paths.","sourceIds":["binance-agent-pay"],"risk":"medium"},{"id":"c2","text":"Binance says B402 is intended for AI agents and applications paying for APIs, digital services and online resources on BNB Chain.","sourceIds":["binance-agent-pay"],"risk":"medium"},{"id":"c3","text":"Binance's product material says integrations are reviewed and availability depends on the business use case, market and supported flow.","sourceIds":["binance-agent-pay","binance-payonchain-faq"],"risk":"low"},{"id":"c4","text":"Coinbase describes x402 as an open HTTP-native payment protocol with signed payloads and facilitator-based verification and settlement.","sourceIds":["x402-welcome"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-okx-tokenized-stock-collateral-haircut-liquidation-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-15T02:36:57.301Z","updatedAt":"2026-09-15T02:36:57.301Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs OKX Tokenized-Stock Collateral: Haircuts, Eligibility and Liquidation Controls","zh-Hans":"Binance 与 OKX 代币化股票抵押品对比：折扣、资格与清算控制"},"summary":{"en":"Binance and OKX both describe selected tokenized-stock products as potential margin collateral, but the usable value is not the headline market value.","zh-Hans":"Binance 与 OKX 都把部分代币化股票产品描述为可用保证金抵押品，但可计入价值并不等于名义市值。Binance 的 BNCB 公告把功能限定在特定保证金模式、VIP 3 及以上合格用户和许可地区；OKX 则说明风险折扣、抵押限额与独立风险单元。用户在依赖这类资产前，应比较资格、折后估值、借币规则、清算耦合和股东权利边界。"},"claims":[{"id":"c1","text":"Binance says BNCB became eligible collateral in Cross Margin, Portfolio Margin and Portfolio Margin Pro at 12:00 UTC on September 14, 2026.","sourceIds":["binance-bncb-collateral"],"risk":"medium"},{"id":"c2","text":"Binance says borrowing BNCB is not currently supported and the feature is limited to VIP 3+ eligible users in permitted jurisdictions.","sourceIds":["binance-bncb-collateral"],"risk":"medium"},{"id":"c3","text":"OKX says selected Unified Tokenized Stocks may count as collateral after a risk-based haircut and subject to collateral limits.","sourceIds":["okx-europe-tokenized","okx-unified-stocks"],"risk":"low"},{"id":"c4","text":"OKX says tokenized-stock spot holdings and corresponding stock perpetuals are currently assessed in separate risk units and do not automatically offset each other.","sourceIds":["okx-unified-stocks"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"custodial-vs-synthetic-tokenized-stocks-shareholder-rights-framework","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-15T02:36:57.301Z","updatedAt":"2026-09-15T02:36:57.301Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Custodial vs Synthetic Tokenized Stocks: A Shareholder-Rights Framework","zh-Hans":"托管型与合成型代币化股票：股东权利判断框架"},"summary":{"en":"A token that tracks a stock price is not automatically the stock. SEC staff distinguishes issuer-sponsored, third-party custodial and synthetic tokenization models because ownership records, claims and intermediary risk differ. S.","zh-Hans":"追踪股票价格的代币不自动等于股票。SEC 工作人员区分发行人主导、第三方托管与合成代币化模型，因为所有权记录、请求权和中介风险不同。Ondo 的美国托管型方案称持有人获得明确的股东保护与代理投票，而其他交易所分销产品可能只提供经济敞口、不直接拥有股票。用户必须逐项识别法律发行人、权威记录、托管链、投票权与赎回请求权。"},"claims":[{"id":"c1","text":"SEC staff says tokenized securities can be issuer-sponsored or third-party sponsored, and third-party structures may be custodial or synthetic.","sourceIds":["sec-tokenized"],"risk":"medium"},{"id":"c2","text":"SEC staff says third-party token holders may face intermediary bankruptcy and claim risks not faced by direct holders of the underlying security.","sourceIds":["sec-tokenized"],"risk":"medium"},{"id":"c3","text":"Ondo says its U.S. custodial model keeps underlying securities in the regulated custody chain and provides defined voting and shareholder communications through Broadridge.","sourceIds":["ondo-us-custodial"],"risk":"low"},{"id":"c4","text":"OKX says Unified Tokenized Stocks provide stock-linked economic exposure but do not represent direct ownership or voting rights unless a provider explicitly states otherwise.","sourceIds":["okx-unified-stocks"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"x402-agent-payment-verification-settlement-idempotency-recovery-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-15T02:36:57.301Z","updatedAt":"2026-09-15T02:36:57.301Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"x402 Agent Payments: Verification, Settlement and Idempotency Recovery Radar","zh-Hans":"x402 智能体支付：验证、结算与幂等恢复雷达"},"summary":{"en":"An x402 retry should not be treated like an ordinary stateless HTTP retry.","zh-Hans":"x402 重试不能按普通无状态 HTTP 重试处理。Coinbase 的协议流程把付款要求、签名授权、验证、结算与资源响应分开；故障可能发生在签名前、验证阶段、链上结算中，或结算完成但资源尚未返回时。运营方需要稳定付款标识、有限重试、权威结算查询、签名收据、网络核对，以及防止同一逻辑请求重复付款的规则。"},"claims":[{"id":"c1","text":"x402 uses HTTP 402 payment requirements, a signed payment payload and a facilitator verification and settlement flow.","sourceIds":["x402-welcome","rfc-402"],"risk":"medium"},{"id":"c2","text":"Coinbase documents distinct verification and settlement error reasons, including invalid signatures, insufficient funds, node failure and confirmation timeout.","sourceIds":["x402-troubleshooting"],"risk":"medium"},{"id":"c3","text":"The x402 extension set includes a Payment Identifier for duplicate-call handling and an Offer Receipt for signed pre-settlement terms.","sourceIds":["x402-faq"],"risk":"low"},{"id":"c4","text":"A successful onchain settlement and successful resource delivery are separate events that require separate evidence.","sourceIds":["x402-welcome","x402-troubleshooting"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-coinbase-api-client-order-id-retry-reconciliation","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-14T23:35:56.434Z","updatedAt":"2026-09-14T23:35:56.434Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs Coinbase API Client Order IDs: Retry and Reconciliation Controls","zh-Hans":"Binance 与 Coinbase API 客户端订单 ID 对比：重试与对账控制"},"summary":{"en":"Binance and Coinbase both expose caller-supplied order identifiers, but an identifier alone does not make every retry safe.","zh-Hans":"Binance 与 Coinbase 都允许调用方提供订单标识，但仅有标识并不能保证每次重试安全。Binance 在现货订单流程中说明 newClientOrderId；Coinbase Advanced Trade 创建订单时要求 client_order_id。生产客户端应生成稳定唯一 ID，在超时结果不明时先查询订单状态，对账成交与拒绝，并仅在证明首个请求未被接受后重试。"},"claims":[{"id":"c1","text":"Binance defines newClientOrderId as a caller-assigned clientOrderId for a new order or cancel message.","sourceIds":["binance-glossary"],"risk":"medium"},{"id":"c2","text":"Binance trading endpoints expose client-order identifiers in order creation and lookup workflows.","sourceIds":["binance-orders"],"risk":"medium"},{"id":"c3","text":"Coinbase Advanced Trade requires a client_order_id in the create-order request and returns success or failure details.","sourceIds":["coinbase-create-order","coinbase-orders"],"risk":"low"},{"id":"c4","text":"Neither public interface removes the need to query authoritative order state after a transport timeout with an unknown server outcome.","sourceIds":["binance-orders","coinbase-orders"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bis-2026-stablecoin-singleness-elasticity-integrity-user-framework","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-14T23:35:56.434Z","updatedAt":"2026-09-14T23:35:56.434Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"BIS 2026 Stablecoin Trust Tests: Singleness, Elasticity and Integrity","zh-Hans":"BIS 2026 稳定币信任测试：统一性、弹性与金融完整性"},"summary":{"en":"The BIS 2026 Annual Economic Report says stablecoins demonstrate programmable-payment potential but current designs fall short on foundational monetary properties.","zh-Hans":"BIS《2026 年年度经济报告》表示，稳定币展示了可编程支付潜力，但当前设计在货币基础属性上仍有不足。其框架关注不同形式能否按面值兑换、流动性能否扩张以避免支付阻塞，以及金融完整性控制能否覆盖整个系统。这是系统级政策评估，并不意味着每笔稳定币转账或每个发行人都以同样方式失败。"},"claims":[{"id":"c1","text":"The BIS 2026 report says stablecoins show tokenization's potential for faster programmable payments.","sourceIds":["bis-aer-2026"],"risk":"medium"},{"id":"c2","text":"The report says current designs fall short on foundational properties including singleness and financial integrity.","sourceIds":["bis-aer-2026","bis-release"],"risk":"medium"},{"id":"c3","text":"The report links system-level elasticity to timely liquidity that prevents payment gridlock in normal and stressed conditions.","sourceIds":["bis-aer-2026"],"risk":"low"},{"id":"c4","text":"The BIS says wider adoption effects depend on reserve composition, use, regulation and interactions with bank funding and capital flows.","sourceIds":["bis-aer-2026","bis-release"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"circle-cirbtc-wrapped-bitcoin-collateral-custody-redemption-risk","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-14T23:35:56.434Z","updatedAt":"2026-09-14T23:35:56.434Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Circle cirBTC as Wrapped Bitcoin Collateral: Custody, Redemption and Liquidation Risk","zh-Hans":"Circle cirBTC 作为封装比特币抵押品：托管、赎回与清算风险"},"summary":{"en":"Circle describes cirBTC as a tokenized representation of BTC: native BTC remains in issuer custody while a separate programmable-chain token is issued 1:1 and redeemable for it.","zh-Hans":"Circle 把 cirBTC 描述为 BTC 的代币化表示：原生 BTC 留在发行方托管中，另一枚可编程链代币按 1:1 发行并可赎回。该结构可用于链上借贷，但用户通过托管、智能合约、链、预言机与赎回多层持有请求权。因此，抵押品质量不只取决于 BTC 市价。"},"claims":[{"id":"c1","text":"Circle describes wrapped BTC as native BTC held in custody with a separate token issued 1:1 and redeemable for the underlying asset.","sourceIds":["circle-collateral","circle-cirbtc"],"risk":"medium"},{"id":"c2","text":"Circle says its wrapped-digital-asset reserve is not intended to be lent, pledged or rehypothecated under the published structure.","sourceIds":["circle-collateral","circle-terms"],"risk":"medium"},{"id":"c3","text":"Using wrapped BTC in lending adds protocol, oracle, liquidation and chain risks beyond issuer custody and redemption.","sourceIds":["circle-collateral"],"risk":"low"},{"id":"c4","text":"A token balance is not the same technical asset as native BTC on the Bitcoin ledger.","sourceIds":["circle-cirbtc"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-api-withdrawal-address-management-permission-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-14T23:35:56.434Z","updatedAt":"2026-09-14T23:35:56.434Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange API Withdrawal-Address Permissions: Blast-Radius Radar","zh-Hans":"加密交易所 API 提现地址权限：影响半径雷达"},"summary":{"en":"Address-management permission and fund-withdrawal permission should be treated as separate high-risk capabilities.","zh-Hans":"地址管理权限与资金提现权限应被视为两种独立高风险能力。Kraken 明确警告，如果把 Add Withdrawal Addresses 与 Withdraw Funds 组合，泄露的密钥可能添加攻击者地址并发送资产。Coinbase Exchange 说明地址簿 API 操作，同时不允许 API 启停白名单。运营方应拆分密钥、绑定 IP、设置过期并监控每次地址变化。"},"claims":[{"id":"c1","text":"Kraken says Add Withdrawal Addresses lets an API key add and remove crypto and fiat withdrawal destinations.","sourceIds":["kraken-address-api"],"risk":"medium"},{"id":"c2","text":"Kraken warns that combining address management with Withdraw Funds increases compromise impact.","sourceIds":["kraken-address-api"],"risk":"medium"},{"id":"c3","text":"Coinbase Exchange says APIs can add, delete, list and use address-book destinations but cannot enable or disable whitelisting.","sourceIds":["coinbase-address-api"],"risk":"low"},{"id":"c4","text":"OWASP recommends restricted access, rotation, auditing and centralized secret management.","sourceIds":["owasp-secrets"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-orclusd-equity-x-perp-contract-risk-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-14T23:35:56.434Z","updatedAt":"2026-09-14T23:35:56.434Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"OKX ORCLUSD Equity X-Perp: Contract and Risk Checklist","zh-Hans":"OKX ORCLUSD 股票 X-Perp：合约与风险检查清单"},"summary":{"en":"OKX announced that ORCLUSD UM Equity X-Perp trading opened at 09:00 UTC on September 11, 2026 across web, app and API, subject to regional availability. The announcement does not make the contract equivalent to Oracle shares.","zh-Hans":"OKX 公告称 ORCLUSD UM 股票 X-Perp 已于 2026 年 9 月 11 日 09:00 UTC 在网页、App 与 API 开放交易，并受地区可用性限制。该公告不代表合约等同于 Oracle 股票。交易前应核对实时合约规格中的指数构成、交易时段、资金费率、杠杆、结算币种、公司行动处理与暂停规则。"},"claims":[{"id":"c1","text":"OKX says ORCLUSD UM X-Perp trading opened at 09:00 UTC on September 11, 2026.","sourceIds":["okx-orcl"],"risk":"medium"},{"id":"c2","text":"OKX says the product update covers web, app and API interfaces.","sourceIds":["okx-orcl"],"risk":"medium"},{"id":"c3","text":"The announcement tells users to check regional product availability and warns about leveraged-trading risk.","sourceIds":["okx-orcl"],"risk":"low"},{"id":"c4","text":"A perpetual derivative provides contract exposure and does not by itself confer Oracle shareholder rights.","sourceIds":["okx-perpetual"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vechain-interstellar-hardfork-deposit-withdrawal-suspension","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-14T20:35:25.535Z","updatedAt":"2026-09-14T20:35:25.535Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Binance VeChain Interstellar Hard Fork: Deposit and Withdrawal Suspension Checklist","zh-Hans":"Binance 支持 VeChain Interstellar 硬分叉：充提暂停检查清单"},"summary":{"en":"Binance says it will suspend VeChain-network deposits and withdrawals around 10:15 UTC on September 16, 2026, ahead of the mandatory Interstellar hard fork at block 25,902,540 around 11:15 UTC. Trading is stated to continue.","zh-Hans":"Binance 表示将于 2026 年 9 月 16 日约 10:15 UTC 暂停 VeChain 网络充提，以支持约 11:15 UTC 在区块 25,902,540 激活的强制 Interstellar 硬分叉。公告称交易不受影响。用户应提前完成有时限的转账，并核对登录后的网络状态，因为稳定后恢复不会另行公告。"},"claims":[{"id":"c1","text":"Binance states that VeChain-network deposits and withdrawals will be suspended at approximately 10:15 UTC on September 16, 2026.","sourceIds":["binance-vet","binance-maintenance"],"risk":"medium"},{"id":"c2","text":"Binance states that trading of tokens on the network will not be affected by the suspension.","sourceIds":["binance-vet"],"risk":"medium"},{"id":"c3","text":"The signed VeChain Thor v2.5.0 release describes Interstellar as a mandatory upgrade at mainnet block 25,902,540 around 11:15 UTC.","sourceIds":["vechain-release"],"risk":"low"},{"id":"c4","text":"Binance says deposits and withdrawals will reopen after the upgraded network is deemed stable and no further reopening announcement will be posted.","sourceIds":["binance-vet"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"circle-noble-usdc-cctp-v1-winddown-exit-redemption-timeline","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-14T20:35:25.535Z","updatedAt":"2026-09-14T20:35:25.535Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Circle Noble USDC and CCTP V1 Wind-Down: Exit and Redemption Timeline","zh-Hans":"Circle Noble USDC 与 CCTP V1 退出：迁移与赎回时间线"},"summary":{"en":"Circle says new USDC minting to Noble through Circle Mint stops October 13, 2026; redemption through Circle Mint continues until January 12, 2027, when Noble USDC and CCTP routes are paused.","zh-Hans":"Circle 表示，通过 Circle Mint 向 Noble 新铸造 USDC 将于 2026 年 10 月 13 日停止；Circle Mint 赎回持续到 2027 年 1 月 12 日，届时 Noble USDC 与 CCTP 路由暂停。余额快照用于 1 月 13 日开始的人工赎回。持有人与集成方应提前选择并测试退出路径，因为 CCTP V1 销毁限额将于 10 月 31 日开始下降。"},"claims":[{"id":"c1","text":"Circle says new USDC minting on Noble through Circle Mint will be disabled on October 13, 2026.","sourceIds":["circle-noble"],"risk":"medium"},{"id":"c2","text":"Circle says Noble redemptions through Circle Mint remain available until January 12, 2027, when Noble USDC and CCTP routes pause.","sourceIds":["circle-noble"],"risk":"medium"},{"id":"c3","text":"Circle says CCTP V1 burn limits begin reducing October 31, 2026 and a manual redemption process begins January 13, 2027 after a balance snapshot.","sourceIds":["circle-noble","circle-migration"],"risk":"low"},{"id":"c4","text":"Circle's migration documentation says CCTP V2 is not deployed on Noble, so integrators cannot assume an in-place V2 route.","sourceIds":["circle-migration"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-vs-kraken-withdrawal-address-allowlist-hold-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-14T20:35:25.535Z","updatedAt":"2026-09-14T20:35:25.535Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase vs Kraken Withdrawal Address Controls: Allowlists, Holds and Recovery","zh-Hans":"Coinbase 与 Kraken 提现地址控制对比：允许名单、等待期与恢复"},"summary":{"en":"Coinbase and Kraken both require careful destination management, but their published controls are not identical. Coinbase documents an allowlist with a 48-hour wait for new addresses after the initial window.","zh-Hans":"Coinbase 与 Kraken 都要求谨慎管理提现目的地，但公开控制并不相同。Coinbase 说明允许名单在初始窗口后新增地址需等待 48 小时；Kraken 要求添加并确认新地址，并说明安全设置变更后的条件性等待期。入金前应比较产品范围、网络字段、批准方法、等待期、变更保护与恢复路径。"},"claims":[{"id":"c1","text":"Coinbase says allowlisting limits sends to addresses in the address book and requires two-step verification.","sourceIds":["coinbase-allowlist"],"risk":"medium"},{"id":"c2","text":"Coinbase says a newly added address becomes available after 48 hours outside the initial activation window.","sourceIds":["coinbase-allowlist","coinbase-exchange-whitelist"],"risk":"medium"},{"id":"c3","text":"Kraken says a new cryptocurrency withdrawal address must be added and confirmed, with device or email verification depending on context.","sourceIds":["kraken-address"],"risk":"low"},{"id":"c4","text":"Kraken says some password-change scenarios can place a 24-hour hold on withdrawals to new addresses and recommends stronger account controls.","sourceIds":["kraken-address","kraken-security"],"risk":"low"}],"relatedVenues":["coinbase","kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-api-request-timestamp-nonce-replay-protection-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-14T20:35:25.535Z","updatedAt":"2026-09-14T20:35:25.535Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange API Request-Freshness Radar: Timestamps, Nonces and Replay Protection","zh-Hans":"加密交易所 API 请求新鲜度雷达：时间戳、Nonce 与重放保护"},"summary":{"en":"Signed exchange API requests can fail or become unsafe when client clocks drift, nonces repeat, validity windows are too broad or retries replay an already accepted action.","zh-Hans":"当客户端时钟漂移、Nonce 重复、有效窗口过宽或重试重放已接受操作时，交易所签名 API 请求可能失败或变得不安全。NexuAlpha 雷达把认证与新鲜度分开：签名正确证明持有密钥，时间戳、Nonce、接收窗口和幂等控制限制请求何时以及可执行几次。生产客户端需要单调状态、时钟监控，并在重试前对账。"},"claims":[{"id":"c1","text":"Binance documents timestamp and recvWindow checks for signed requests.","sourceIds":["binance-security"],"risk":"medium"},{"id":"c2","text":"OKX documents a timestamp as part of the pre-hash string used for REST request signatures.","sourceIds":["okx-auth"],"risk":"medium"},{"id":"c3","text":"Coinbase documents short-lived authentication material and permission boundaries for CDP API keys.","sourceIds":["coinbase-auth"],"risk":"low"},{"id":"c4","text":"Kraken documents an always-increasing nonce for private Spot REST requests and warns that invalid nonce behavior can cause failures.","sourceIds":["kraken-auth"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"franklin-benji-onchain-fund-p2p-transfer-recordkeeping-controls","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-14T20:35:25.535Z","updatedAt":"2026-09-14T20:35:25.535Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Franklin BENJI Onchain Fund: P2P Transfer and Recordkeeping Controls","zh-Hans":"Franklin BENJI 链上基金：P2P 转让与记录控制"},"summary":{"en":"Franklin Templeton describes FOBXX as a registered money market fund whose official transaction and share-ownership record uses a public blockchain, represented through BENJI tokens.","zh-Hans":"Franklin Templeton 把 FOBXX 描述为使用公链处理交易并记录份额所有权的注册货币市场基金，份额以 BENJI 代币表示。P2P 转让与链上分配并未消除基金法律、资格、记录或过户代理控制。投资者应核对权威记录、许可钱包、转让条件、NAV 流程、赎回路径与司法辖区，不能把代币可移动性等同于现金自由。"},"claims":[{"id":"c1","text":"Franklin Templeton says FOBXX was the first U.S.-registered mutual fund to use a public blockchain as its official system of record for transactions and share ownership.","sourceIds":["franklin-five-years"],"risk":"medium"},{"id":"c2","text":"Franklin Templeton says BENJI supports peer-to-peer share transfers and onchain dividend distribution subject to the fund's framework.","sourceIds":["franklin-five-years"],"risk":"medium"},{"id":"c3","text":"The fund prospectus remains the controlling source for eligibility, purchase, redemption, fees and investment risk.","sourceIds":["franklin-prospectus"],"risk":"low"},{"id":"c4","text":"Franklin Templeton describes the Benji platform as blockchain-enabled recordkeeping and transfer-agency infrastructure.","sourceIds":["franklin-five-years","benji-platform"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-selected-network-deposit-withdrawal-support-removal-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-14T17:36:24.617Z","updatedAt":"2026-09-14T17:36:24.617Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Selected-Network Deposit and Withdrawal Support Removal: User Checklist","zh-Hans":"Binance 停止部分网络充提支持：用户检查清单"},"summary":{"en":"Binance published a September 14 notice that it will cease deposit and withdrawal support for tokens on selected networks.","zh-Hans":"Binance 于 9 月 14 日发布公告，将停止部分代币在特定网络上的充值与提现支持。受影响用户应在实时公告与登录后的钱包页面核对准确的资产—网络组合、截止时间和替代路径。除非发送方与接收方都明确支持另一网络，否则相同代币代码不能视为可替代通道。"},"claims":[{"id":"c1","text":"Binance's latest-articles index includes a September 14, 2026 notice about ceasing deposit and withdrawal support for tokens on selected networks.","sourceIds":["binance-latest"],"risk":"medium"},{"id":"c2","text":"Support changes are network-specific, so an asset ticker alone is insufficient to identify an eligible transfer route.","sourceIds":["binance-latest"],"risk":"medium"},{"id":"c3","text":"The authenticated deposit and withdrawal interface is the operational authority for currently selectable networks and required memos or tags.","sourceIds":["binance-deposit-status"],"risk":"low"},{"id":"c4","text":"Recovery after a wrong-network transfer is not guaranteed and may depend on technical compatibility and platform policy.","sourceIds":["binance-wrong-network"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-okx-equity-perpetuals-market-hours-funding-risk-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-14T17:36:24.617Z","updatedAt":"2026-09-14T17:36:24.617Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs OKX Equity Perpetuals: Market Hours, Funding and Risk Controls","zh-Hans":"Binance 与 OKX 股票永续合约对比：交易时段、资金费率与风险控制"},"summary":{"en":"Binance and OKX both publish equity-linked perpetual products, but a shared stock ticker does not make the contracts interchangeable.","zh-Hans":"Binance 与 OKX 都发布了股票挂钩永续产品，但相同股票代码并不代表合约可以互换。用户必须比较签约实体、地区资格、交易时段、指数方法、资金费率周期、杠杆、结算币种、公司行动处理与暂停规则。可靠结论只能针对具体合约与具体账户，不能简化为平台排名。"},"claims":[{"id":"c1","text":"Binance's announcement index lists multiple USD-margined TradFi perpetual-contract launches and related product notices.","sourceIds":["binance-announcements"],"risk":"medium"},{"id":"c2","text":"OKX's announcement index lists Equity X-Perps linked to named equities and indices.","sourceIds":["okx-equity-announcements"],"risk":"medium"},{"id":"c3","text":"Both venues describe perpetual contracts as derivatives without a fixed expiry, with funding and margin mechanics that differ from owning shares.","sourceIds":["binance-futures-guide","okx-perpetual-guide"],"risk":"low"},{"id":"c4","text":"Public product pages cannot prove that a specific signed-in account is eligible or that a contract will remain available during a future session.","sourceIds":["binance-announcements","okx-equity-announcements"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bitcoin-post-quantum-readiness-custody-migration-checklist","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-14T17:36:24.617Z","updatedAt":"2026-09-14T17:36:24.617Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Bitcoin Post-Quantum Readiness: Custody and Migration Checklist","zh-Hans":"比特币后量子准备：托管与迁移检查清单"},"summary":{"en":"Coinbase's September 9 workshop report says Bitcoin developers, cryptographers, institutions and hardware-wallet experts are evaluating post-quantum signature tradeoffs and migration paths.","zh-Hans":"Coinbase 9 月 9 日研讨会报告称，比特币开发者、密码学家、机构与硬件钱包专家正在评估后量子签名方案的取舍与迁移路径。这属于准备工作，并不证明现实中的量子盗窃正在发生，也不代表某一方案已经被选定。托管方应盘点地址暴露、密钥轮换权限、硬件与签名器依赖、升级治理和经过测试的恢复路径，同时避免无证据的紧急结论。"},"claims":[{"id":"c1","text":"Coinbase says it convened a September 2026 workshop with Bitcoin developers, cryptographers, institutions and hardware-wallet experts.","sourceIds":["coinbase-pq"],"risk":"medium"},{"id":"c2","text":"The workshop considered post-quantum signature tradeoffs, lessons from other ecosystems and operational requirements for institutional custody.","sourceIds":["coinbase-pq"],"risk":"medium"},{"id":"c3","text":"Coinbase describes the work as advancing preparation and carefully tested solutions, not declaring a selected Bitcoin migration design.","sourceIds":["coinbase-pq"],"risk":"low"},{"id":"c4","text":"NIST publishes post-quantum cryptography standards and migration resources for cryptographic systems generally.","sourceIds":["nist-pqc","nist-standards"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-network-status-deposit-withdrawal-disclosure-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-14T17:36:24.617Z","updatedAt":"2026-09-14T17:36:24.617Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange Network-Status Radar: Deposit and Withdrawal Disclosure Controls","zh-Hans":"加密交易所网络状态雷达：充值与提现披露控制"},"summary":{"en":"An exchange homepage returning HTTP 200 does not prove that a particular asset-network deposit or withdrawal path is working.","zh-Hans":"交易所首页返回 HTTP 200，并不能证明某个资产—网络的充值或提现路径正在工作。NexuAlpha 披露雷达把四层证据分开：公开故障状态、资产—网络可用性、登录后的钱包控制以及已完成的小额测试转账。当这些证据相互冲突时，应停止操作，而不是从绿色首页推断可用。"},"claims":[{"id":"c1","text":"Major venues publish separate service-status or network-status surfaces in addition to their marketing homepages.","sourceIds":["binance-network","okx-status","coinbase-status","kraken-status"],"risk":"medium"},{"id":"c2","text":"A general platform status can remain operational while one asset, network, region or wallet action is degraded or suspended.","sourceIds":["binance-network","okx-status","coinbase-status","kraken-status"],"risk":"medium"},{"id":"c3","text":"An authenticated wallet may expose account-specific network choices, minimums, fees and destination requirements not visible on a public status page.","sourceIds":["binance-network"],"risk":"low"},{"id":"c4","text":"A completed small transfer is evidence for that route at that time, not a guarantee of future availability.","sourceIds":["coinbase-status","kraken-status"],"risk":"low"}],"relatedVenues":["binance","okx","coinbase","kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-tokenized-dtc-assets-live-pilot-ownership-settlement-controls","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-14T17:36:24.617Z","updatedAt":"2026-09-14T17:36:24.617Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC Tokenized DTC Assets Live Pilot: Ownership, Settlement and Control Boundaries","zh-Hans":"DTCC 代币化 DTC 资产实盘试点：所有权、结算与控制边界"},"summary":{"en":"Public SEC materials report that DTCC processed live transactions involving tokenized DTC assets with more than 30 institutions in July 2026 ahead of a planned service launch.","zh-Hans":"SEC 公开材料称，DTCC 于 2026 年 7 月与 30 多家机构处理了涉及代币化 DTC 资产的实盘交易，为计划中的服务上线做准备。这属于运营准备证据，并不证明市场已经规模化或向散户无限制开放。关键控制仍是权威 DTC 头寸、控制账户划转、钱包资格、对账、结算终局性以及记录不一致时的恢复机制。"},"claims":[{"id":"c1","text":"SEC-hosted material states that DTCC processed live tokenized-DTC-asset transactions with more than 30 institutions on July 15, 2026.","sourceIds":["sec-wall-street"],"risk":"medium"},{"id":"c2","text":"The material frames the activity as preparation for a planned service launch rather than evidence of system-wide tokenized-market scale.","sourceIds":["sec-wall-street"],"risk":"medium"},{"id":"c3","text":"The SEC-filed Nasdaq proposal describes movement from a participant's DTC book-entry position to a DTC control account before token delivery to a registered wallet.","sourceIds":["nasdaq-proposal"],"risk":"low"},{"id":"c4","text":"The proposal describes DTC tracking and reconciliation between the control account and tokenized position.","sourceIds":["nasdaq-proposal"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"blackrock-onchain-money-market-fund-nav-redemption-wallet-controls","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-14T11:42:00.000Z","updatedAt":"2026-09-14T11:42:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"BlackRock OnChain Money Market Fund Shares: NAV, Whitelists and Redemption Controls","zh-Hans":"BlackRock 链上货币市场基金份额：NAV、白名单与赎回控制"},"summary":{"en":"BlackRock's BSTBL OnChain Shares are permissioned ERC-20 representations of a regulated money market fund share class on Ethereum, not freely transferable bearer tokens.","zh-Hans":"BlackRock 的 BSTBL OnChain Shares 是以太坊上的许可型 ERC-20 货币市场基金份额表示，并非可自由转移的不记名代币。过户代理维护官方所有权记录、核验合格钱包，并可限制、拒绝或冻结转移。工作日美东时间 17:00 前收到的申购与赎回订单适用当日 NAV；赎回需要把份额发送到管理赎回钱包，并可能产生以太坊网络费。因此，链上可转移性仍受基金规则、身份控制、市场日历与过户代理运营约束。"},"claims":[{"id":"c1","text":"The SEC-filed prospectus says BSTBL OnChain Shares are permissioned ERC-20 tokens on Ethereum and only verified wallet addresses may purchase them.","sourceIds":["blackrock-prospectus"],"risk":"medium"},{"id":"c2","text":"The transfer agent maintains the official ownership record and administers wallet whitelisting plus the ability to restrict, reject or freeze transfers.","sourceIds":["blackrock-prospectus"],"risk":"medium"},{"id":"c3","text":"Purchase and redemption orders must reach the transfer agent by 5:00 p.m. Eastern on a business day to receive that day's NAV.","sourceIds":["blackrock-prospectus","blackrock-account-resources"],"risk":"low"},{"id":"c4","text":"Redemption orders are submitted by moving OnChain Shares to an administrative redemption wallet, and investors may have to pay Ethereum network fees.","sourceIds":["blackrock-prospectus","blackrock-account-resources"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-vs-okx-subaccounts-risk-isolation-api-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-14T11:42:00.000Z","updatedAt":"2026-09-15T10:54:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit vs OKX Subaccounts: Risk Isolation, Transfers and API Controls","zh-Hans":"Bybit 与 OKX 子账户对比：风险隔离、资金划转与 API 控制"},"summary":{"en":"Bybit and OKX both use subaccounts to separate strategies and operational risk, but their control boundaries differ.","zh-Hans":"Bybit 与 OKX 都把子账户用于分离策略与风险，但控制边界不同。Bybit 表示标准子账户的盈亏与主账户分离，支持 API 交易，所有外部充值和提现必须经主账户完成。OKX 在创建 API Key 时允许选择主账户或子账户，并区分 Read、Trade 与 Withdraw 权限。决定前应比较资金划转权限、外部提现路径、API 范围、IP 限制、登录恢复与审计证据。"},"claims":[{"id":"c1","text":"Bybit says a standard subaccount's profit and loss is segregated from the main account and that standard subaccounts support API trading.","sourceIds":["bybit-subaccount-faq"],"risk":"medium"},{"id":"c2","text":"Bybit says standard subaccounts cannot make external deposits or withdrawals; those operations must be performed through the main account.","sourceIds":["bybit-subaccount-faq"],"risk":"medium"},{"id":"c3","text":"OKX says standard users can create up to five subaccounts and can select the intended account or subaccount during API-key creation.","sourceIds":["okx-subaccount-faq"],"risk":"low"},{"id":"c4","text":"OKX documents Read, Trade and Withdraw permissions, recommends trusted-IP binding, and says unbound Trade or Withdraw keys expire after 14 days of inactivity except demo-trading keys.","sourceIds":["okx-api-guide"],"risk":"low"}],"relatedVenues":["bybit","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-websocket-market-data-pricing-september-15-capacity-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-14T11:42:00.000Z","updatedAt":"2026-09-14T11:42:00.000Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase WebSocket Market Data Pricing Changes September 15: Capacity Checklist","zh-Hans":"Coinbase WebSocket 行情订阅 9 月 15 日调价：容量检查清单"},"summary":{"en":"Coinbase Exchange says new WebSocket market-data subscription prices take effect on September 15, 2026.","zh-Hans":"Coinbase Exchange 表示，WebSocket 行情订阅新价格将于 2026 年 9 月 15 日生效。每个产品、每个频道默认 10 个订阅仍为每月 0 美元；付费档位变为 15 个 300 美元、25 个 1,200 美元、50 个 2,400 美元、100 个 4,200 美元、250 个 7,800 美元、500 个 12,000 美元。团队应先盘点真实产品—频道组合、清除重复订阅、测试批量订阅与故障切换，并在 Coinbase Developer Platform 核对所选档位。"},"claims":[{"id":"c1","text":"Coinbase says revised WebSocket market-data subscription pricing takes effect on September 15, 2026.","sourceIds":["coinbase-market-data-connections"],"risk":"medium"},{"id":"c2","text":"The default tier remains 10 subscriptions per product and channel at no monthly charge, and attempts above 10 are rejected without a paid tier.","sourceIds":["coinbase-market-data-connections","coinbase-websocket-limits"],"risk":"medium"},{"id":"c3","text":"The September 15 monthly prices are $300 for 15, $1,200 for 25, $2,400 for 50, $4,200 for 100, $7,800 for 250 and $12,000 for 500 subscriptions.","sourceIds":["coinbase-market-data-connections"],"risk":"low"},{"id":"c4","text":"Coinbase says one subscription is measured per product and channel and allows multiple products and channels to be included in one subscription request.","sourceIds":["coinbase-market-data-connections"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-websocket-heartbeat-reconnect-liveness-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-14T11:42:00.000Z","updatedAt":"2026-09-14T11:42:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange WebSocket Liveness Radar: Heartbeats, Reconnects and Gap Recovery","zh-Hans":"加密交易所 WebSocket 存活雷达：心跳、重连与缺口恢复"},"summary":{"en":"A WebSocket connection being open does not prove that market or account state is complete.","zh-Hans":"WebSocket 连接仍处于打开状态，并不能证明行情或账户状态完整。Binance 说明连接每 24 小时需要轮换并要求 ping/pong；OKX 要求客户端设置小于 30 秒的存活计时器，缺少 pong 时重连；Coinbase 提供心跳计数器或序列数据，同时警告消息仍可能丢失。生产消费者必须分别控制存活性、连续性与状态对账：监控静默、响应心跳、在强制到期前轮换、发现缺口、从权威快照重建、去重事件，并在无法对账时失败关闭。"},"claims":[{"id":"c1","text":"Binance says a coin-futures market-stream connection is valid for 24 hours and its server sends a ping frame every three minutes.","sourceIds":["binance-ws-connect"],"risk":"medium"},{"id":"c2","text":"OKX says a connection may break after more than 30 seconds without subscription or pushed data and recommends client ping, pong verification and reconnect logic.","sourceIds":["okx-ws"],"risk":"medium"},{"id":"c3","text":"Coinbase Advanced Trade says heartbeats arrive every second and heartbeat counters can help identify missed messages while keeping sparse subscriptions open.","sourceIds":["coinbase-advanced-heartbeats"],"risk":"low"},{"id":"c4","text":"Coinbase Exchange says sequence gaps or out-of-order messages can occur and consumers may need logic or guaranteed-delivery channels to restore correct state.","sourceIds":["coinbase-exchange-sequences"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-24-hour-equity-trading-roundtable-overnight-market-readiness","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-14T11:42:00.000Z","updatedAt":"2026-09-14T11:42:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"SEC 24-Hour Trading Roundtable: Overnight Market and Settlement Readiness","zh-Hans":"SEC 24 小时交易圆桌会议：隔夜市场与结算准备度"},"summary":{"en":"S. equity-market infrastructure for 24-hour trading, not announcing that a universal 24/7 market is already live. The agenda separates launch readiness, operational resiliency and longer-term impacts.","zh-Hans":"SEC 于 2026 年 9 月 17 日举行的圆桌会议讨论的是美国股票市场基础设施如何为 24 小时交易做准备，并不是宣布普遍的 24/7 市场已经上线。议程分为上线准备、运营韧性与长期影响，涵盖隔夜监控、收盘价流程、清算结算、投资者保护、故障切换、容量、行情连续性、网络安全、人员配置与未来 24x7 扩展。加密与代币化资产运营方应把它视为端到端清单：交易场所可以持续开放，但参考价格、融资、结算、过户代理、银行通道或支持服务仍可能关闭。"},"claims":[{"id":"c1","text":"The SEC scheduled the roundtable for September 17, 2026 from 10:00 a.m. to 4:00 p.m. Eastern and said it would be webcast publicly.","sourceIds":["sec-agenda"],"risk":"medium"},{"id":"c2","text":"Panel One covers exchange and broker-dealer readiness, overnight surveillance, closing-price processes, clearance and settlement changes, investor protection and expected liquidity.","sourceIds":["sec-agenda"],"risk":"medium"},{"id":"c3","text":"Panel Two covers operational resiliency, Regulation SCI, failover, capacity planning, market-data continuity, shortened maintenance windows, cybersecurity and overnight staffing.","sourceIds":["sec-agenda"],"risk":"low"},{"id":"c4","text":"Panel Three covers impacts on liquidity and capital formation plus future expansion toward 24x7 trading and required infrastructure changes.","sourceIds":["sec-agenda"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-ava-gns-towns-network-support-ended-transfer-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-14T08:40:00.000Z","updatedAt":"2026-09-14T08:40:00.000Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Ends Selected AVA, GNS and TOWNS Network Support: Transfer Checklist","zh-Hans":"Binance 停止部分 AVA、GNS 与 TOWNS 网络支持：转账检查清单"},"summary":{"en":"Binance says support ended at 08:00 UTC on September 14, 2026 for AVA deposits and withdrawals through BNB Smart Chain and Solana, GNS through Polygon, and TOWNS through BNB Smart Chain and Base.","zh-Hans":"Binance 表示，自 2026 年 9 月 14 日 08:00 UTC 起，停止支持 AVA 通过 BNB Smart Chain 与 Solana、GNS 通过 Polygon、TOWNS 通过 BNB Smart Chain 与 Base 的充值和提现。截止时间后通过这些已停止路径发送的充值不会入账，并可能导致资产损失。相关代币仍可能通过 Binance 当前支持的其他网络转移，但用户每次操作前都必须在发送端与接收端核对实时资产—网络组合。"},"claims":[{"id":"c1","text":"Binance set the selected-network support cutoff at September 14, 2026 at 08:00 UTC.","sourceIds":["binance-network-notice","binance-maintenance"],"risk":"medium"},{"id":"c2","text":"The affected routes are AVA via BNB Smart Chain and Solana, GNS via Polygon, and TOWNS via BNB Smart Chain and Base.","sourceIds":["binance-network-notice"],"risk":"medium"},{"id":"c3","text":"Binance warns that deposits sent through the discontinued routes after the cutoff will not be credited and may lead to asset loss.","sourceIds":["binance-network-notice"],"risk":"low"},{"id":"c4","text":"The notice says users may still deposit or withdraw the listed tokens through other networks that Binance supports.","sourceIds":["binance-network-notice"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-secure-transaction-approval-primary-device-tutorial","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-14T08:40:00.000Z","updatedAt":"2026-09-14T08:40:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit Secure Transaction Approval Tutorial: Primary Device and Recovery Checks","zh-Hans":"Bybit 安全交易批准教程：主设备与恢复检查"},"summary":{"en":"Bybit says Secure Transaction Approval can be activated only in its mobile app and designates one phone as the primary device for reviewing supported transactions initiated from a secondary device or the website.","zh-Hans":"Bybit 表示，Secure Transaction Approval 只能在其手机 App 中启用，并把一部手机指定为主设备，用于审核从次要设备或网页发起的受支持交易。启用前应核验官方 App、账户地区与前置条件，保留可信恢复路径，在主设备上逐项检查交易详情，并拒绝任何无法识别的请求。绝不要把密码、六位验证码、通行密钥、验证器种子、API Secret、私钥、助记词或身份文件复制到笔记或聊天中。"},"claims":[{"id":"c1","text":"Bybit says Secure Transaction Approval can only be activated through the Bybit mobile app.","sourceIds":["bybit-sta"],"risk":"medium"},{"id":"c2","text":"The setup designates a specific phone as the primary device and treats other devices and the website as secondary request origins.","sourceIds":["bybit-sta"],"risk":"medium"},{"id":"c3","text":"Bybit lists identity verification and multiple authentication methods among the activation prerequisites.","sourceIds":["bybit-sta","bybit-security"],"risk":"low"},{"id":"c4","text":"The primary device can approve or reject a transaction request, and Bybit provides approval history and a removal workflow.","sourceIds":["bybit-sta"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-vs-kraken-recurring-buys-fees-schedule-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-14T08:40:00.000Z","updatedAt":"2026-09-14T08:40:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase vs Kraken Recurring Buys: Fees, Scheduling and Cancellation Controls","zh-Hans":"Coinbase 与 Kraken 定投对比：费用、计划与取消控制"},"summary":{"en":"Coinbase and Kraken both support recurring crypto purchases, but the useful comparison is the complete execution path rather than the schedule label.","zh-Hans":"Coinbase 与 Kraken 都支持定期购买加密资产，但真正有用的比较对象是完整执行路径，而不是“定投”标签。Coinbase 说明新建计划会立即执行第一次购买，修改计划需要取消后重新创建。Kraken 说明支持每日、每周、每两周和每月计划，确认前显示交易费用，并允许查看、暂停、编辑或取消受支持的计划。决定前应在同一资产、金额与支付路径下比较预览费用、价差、首次执行、失败规则与取消证据。"},"claims":[{"id":"c1","text":"Coinbase says creating a recurring buy triggers an immediate one-time purchase for the selected recurring amount.","sourceIds":["coinbase-recurring"],"risk":"medium"},{"id":"c2","text":"Coinbase says a user who wants a different recurring schedule must cancel the existing plan and create a new one.","sourceIds":["coinbase-recurring"],"risk":"medium"},{"id":"c3","text":"Kraken documents daily, weekly, biweekly and monthly recurring-order schedules and says the transaction fee is shown before confirmation.","sourceIds":["kraken-recurring"],"risk":"low"},{"id":"c4","text":"Kraken says recurring results can vary with market price and that failed transactions may result from insufficient funds, adverse market conditions or system errors.","sourceIds":["kraken-recurring"],"risk":"low"}],"relatedVenues":["coinbase","kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-stellar-tokenized-securities-multichain-lifecycle-readiness","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-14T08:40:00.000Z","updatedAt":"2026-09-14T08:40:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC and Stellar Tokenized Securities: Multi-Chain Lifecycle Readiness","zh-Hans":"DTCC 与 Stellar 代币化证券：多链全生命周期准备度"},"summary":{"en":"DTCC and the Stellar Development Foundation say they expect DTC-tokenized assets to become available on Stellar in the first half of 2027.","zh-Hans":"DTCC 与 Stellar Development Foundation 表示，预计 DTC 代币化资产将在 2027 年上半年于 Stellar 网络可用。计划覆盖传统形态快速转换及资产全生命周期，包括相关公司行动与报告；DTCC 同时表示，代币化资产保留与传统 DTC 托管证券相同的投资者保护、权益与保障。这是计划中的网络连接，不是当前普遍可用服务；准备度取决于合格资产、参与者接入、钱包控制、权威记录、生命周期处理与跨链异常管理。"},"claims":[{"id":"c1","text":"DTCC and SDF expect DTC-tokenized assets to be available on Stellar in the first half of 2027.","sourceIds":["dtcc-stellar"],"risk":"medium"},{"id":"c2","text":"The announced integration is intended to support conversion of traditional assets into tokenized form and lifecycle functions including corporate actions and reporting.","sourceIds":["dtcc-stellar"],"risk":"medium"},{"id":"c3","text":"DTCC says DTC-tokenized assets will have the same investor protections, entitlements and safeguards as traditionally held securities.","sourceIds":["dtcc-stellar","dtcc-tokenization"],"risk":"low"},{"id":"c4","text":"The parties say they will evaluate eligible asset classes including Russell 1000 constituents, major-index ETFs and U.S. Treasury securities, subject to DTC regulatory obligations.","sourceIds":["dtcc-stellar"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-api-clock-drift-request-expiry-controls-radar","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-14T08:40:00.000Z","updatedAt":"2026-09-14T08:40:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange API Clock-Drift Radar: Timestamp, Expiry and Stale-Order Controls","zh-Hans":"交易所 API 时钟漂移雷达：时间戳、过期与陈旧订单控制"},"summary":{"en":"Authenticated exchange requests are time-bound in different ways. Binance signed endpoints use a timestamp and optional recvWindow.","zh-Hans":"不同交易所用不同方式限制认证请求的有效时间。Binance 签名端点使用 timestamp 与可选 recvWindow；OKX 在客户端时间与服务器时间相差超过 30 秒时拒绝私有请求，并支持用 expTime 丢弃迟到的下单或改单请求；Coinbase JWT 认证依赖同步的 nbf 与 exp。安全客户端必须同步时钟、测量漂移与网络延迟、设置有界请求寿命、区分请求受理与最终订单状态，并在时间证据不确定时失败关闭。"},"claims":[{"id":"c1","text":"Binance signed endpoints require a current timestamp and may use recvWindow to define how long a request remains valid.","sourceIds":["binance-signed","binance-errors"],"risk":"medium"},{"id":"c2","text":"OKX says private REST requests are rejected when the timestamp differs from server time by more than 30 seconds and recommends synchronizing against its public time endpoint.","sourceIds":["okx-api"],"risk":"medium"},{"id":"c3","text":"OKX supports expTime on selected order and amendment operations so a request can be discarded after a client-defined deadline.","sourceIds":["okx-api"],"risk":"low"},{"id":"c4","text":"Coinbase documents clock-skew failures for JWT authentication because nbf and exp claims depend on synchronized timestamps.","sourceIds":["coinbase-jwt"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-usdp-delisting-september-24-product-deadline-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-14T05:42:00.000Z","updatedAt":"2026-09-14T05:42:00.000Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Binance USDP Delisting: Product Deadline Checklist for September 24","zh-Hans":"Binance 下架 USDP：9 月 24 日产品截止时间检查清单"},"summary":{"en":"Binance says it will delist USDP and stop all USDP spot trading at 03:00 UTC on September 24, 2026.","zh-Hans":"Binance 表示将下架 USDP，并于 2026 年 9 月 24 日 03:00 UTC 停止全部 USDP 现货交易。未成交现货订单计划自动移除，受影响交易对的 Trading Bots 也计划同时终止；Spot Copy Trading 的截止时间更早，为 9 月 17 日。用户应按产品盘点每一项 USDP 敞口，在最早适用截止时间前行动，导出记录，并核对登录后的实时产品界面，不能假设一个标题日期适用于所有服务。"},"claims":[{"id":"c1","text":"Binance published the USDP delisting notice on September 10, 2026 and schedules the stop of all USDP spot trading for September 24 at 03:00 UTC.","sourceIds":["binance-usdp","binance-delisting-index"],"risk":"medium"},{"id":"c2","text":"The notice says open spot orders will be automatically removed at the spot-delisting time.","sourceIds":["binance-usdp"],"risk":"medium"},{"id":"c3","text":"The notice says affected Trading Bots will terminate at the same time as spot trading.","sourceIds":["binance-usdp"],"risk":"low"},{"id":"c4","text":"Binance gives Spot Copy Trading an earlier September 17, 2026 at 03:00 UTC removal time, so product deadlines are phased.","sourceIds":["binance-usdp"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-anti-phishing-code-setup-message-verification-tutorial","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-14T05:42:00.000Z","updatedAt":"2026-09-14T05:42:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit Anti-Phishing Code Tutorial: Setup and Message Verification","zh-Hans":"Bybit 防钓鱼码教程：设置与消息核验"},"summary":{"en":"Open Bybit only through its official domain or installed app, sign in, and find Anti-phishing Code under Account Info or Security.","zh-Hans":"只通过 Bybit 官方域名或已安装 App 进入，登录后在 Account Info 或 Security 中找到 Anti-phishing Code。选择唯一但不包含秘密信息的代码，通过登录后的安全验证流程确认，然后核对后续 Bybit 官方邮件与短信是否准确显示该代码。代码缺失或不匹配就是停止信号；代码一致也不能单独证明消息真实，应独立导航、检查发件人与链接、使用 Bybit Authenticity Check，并且绝不披露密码、一次性验证码、API Secret、私钥、助记词或身份文件。"},"claims":[{"id":"c1","text":"Bybit's setup guide directs users from Account Info or Security to the Anti-phishing Code setting, then requires confirmation and security verification.","sourceIds":["bybit-setup"],"risk":"medium"},{"id":"c2","text":"Bybit says the configured code will appear in future official emails and SMS messages.","sourceIds":["bybit-setup","bybit-protect"],"risk":"medium"},{"id":"c3","text":"Bybit says a missing or incorrect code may indicate fraud and users should not click links or take action from that message.","sourceIds":["bybit-security"],"risk":"low"},{"id":"c4","text":"Bybit Protect recommends checking the anti-phishing code and separately using Bybit Authenticity Check to verify official URLs and sources.","sourceIds":["bybit-protect"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"deribit-vs-binance-crypto-options-settlement-collateral-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-14T05:42:00.000Z","updatedAt":"2026-09-14T05:42:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Deribit vs Binance Crypto Options: Settlement, Exercise and Collateral Controls","zh-Hans":"Deribit 与 Binance 加密期权对比：结算、行权与抵押控制"},"summary":{"en":"Deribit and Binance both document European-style crypto options that settle in cash and automatically resolve in-the-money positions at expiry, but they do not create the same collateral and settlement exposure.","zh-Hans":"Deribit 与 Binance 都说明其加密期权采用欧式行权、现金结算，并在到期时自动处理价内仓位，但两者形成的抵押与结算敞口并不相同。Deribit 说明反向期权以相关保证金币种计价和结算，最终交割价使用指数 30 分钟 TWAP；Binance 说明稳定币计价与结算，并区分买方和卖方保证金处理。选择前应逐项比较准确合约、结算资产、指数、到期时间、行权规则、卖方保证金、当前费用页与地区资格。"},"claims":[{"id":"c1","text":"Deribit documents European-style options that are cash-settled at expiry and automatically exercised when in the money.","sourceIds":["deribit-settlement","deribit-inverse"],"risk":"medium"},{"id":"c2","text":"Deribit says its final delivery price uses a 30-minute TWAP of the relevant index and that no physical underlying asset is delivered.","sourceIds":["deribit-settlement"],"risk":"medium"},{"id":"c3","text":"Binance documents stablecoin-priced and settled crypto options and says an option buyer pays the premium without the seller's margin obligation.","sourceIds":["binance-intro"],"risk":"low"},{"id":"c4","text":"Binance's fee documentation separates trading, exercise and liquidation fees, so current fees must be checked independently of older introductory examples.","sourceIds":["binance-fees"],"risk":"low"}],"relatedVenues":["deribit","binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"dtcc-dtc-tokenization-service-rights-interoperability-launch-readiness","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-14T05:42:00.000Z","updatedAt":"2026-09-14T05:42:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"DTCC's DTC Tokenization Service: Rights, Interoperability and October Launch Readiness","zh-Hans":"DTCC 的 DTC 代币化服务：权利、互操作性与 10 月上线准备"},"summary":{"en":"DTCC says DTC-held securities were converted into tokens and used in real production trades on July 15, 2026, ahead of a planned October service launch.","zh-Hans":"DTCC 表示，DTC 托管证券已在 2026 年 7 月 15 日转换为代币并用于真实生产交易，为计划于 10 月推出服务做准备。该设计的重要性在于，代币化表示可在传统形态与代币形态之间转换，同时保持 DTCC 所述的相同投资者保护、权益与所有权。实际准备仍取决于权威记录、钱包控制、资产服务、公司行动、互操作性、法律许可与异常处理；单独的代币余额不能证明完整权利链。"},"claims":[{"id":"c1","text":"DTCC says more than 30 firms participated in July 15 production trades using DTC-tokenized securities.","sourceIds":["dtcc-production"],"risk":"medium"},{"id":"c2","text":"The production event included collateral pledge, securities lending, Treasury repo DVP, equity DVP, equity DVD, token transfer and CCP margin workflows.","sourceIds":["dtcc-production"],"risk":"medium"},{"id":"c3","text":"DTCC says DTC-tokenized assets maintain the same investor protections, entitlements and ownership rights as traditional securities.","sourceIds":["dtcc-production"],"risk":"low"},{"id":"c4","text":"DTCC says the service supports conversion between traditional and tokenized forms and is planned to launch in October 2026.","sourceIds":["dtcc-production","dtcc-development"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"tokenized-collateral-24-7-mobility-settlement-operational-readiness","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-14T05:42:00.000Z","updatedAt":"2026-09-14T05:42:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Tokenized Collateral and 24/7 Mobility: The Operational Readiness Checklist","zh-Hans":"代币化抵押品与 24/7 流动：运营准备检查清单"},"summary":{"en":"Tokenization can shorten collateral movement, but it does not create safe 24/7 settlement by itself.","zh-Hans":"代币化可以缩短抵押品移动时间，但本身不会自动产生安全的 24/7 结算。DTCC 计划中的 Collateral AppChain 与 Chainlink 集成，旨在把资产价格、估值和移动配对，并自动化资格、保证金、优化与结算流程。生产准备仍需要权威所有权、合格资产规则、估值来源、折扣率、结算资产、法律终局性、托管、互操作性、异常处理与运营覆盖。只要任何一层周末关闭，端到端流程就不是真正连续。"},"claims":[{"id":"c1","text":"DTCC says its Collateral AppChain will use Chainlink Runtime Environment and data standards for orchestration, data and automation.","sourceIds":["dtcc-chainlink"],"risk":"medium"},{"id":"c2","text":"The planned integration is intended to pair asset prices, valuations and movement across collateral workflows.","sourceIds":["dtcc-chainlink"],"risk":"medium"},{"id":"c3","text":"DTCC identifies eligibility, valuation, margining, collateral optimization, settlement and post-trade processing as workflows requiring orchestration.","sourceIds":["dtcc-chainlink"],"risk":"low"},{"id":"c4","text":"DTCC says the shared platform is expected to go live in the fourth quarter of 2026, so current descriptions are a design and rollout plan rather than proof of continuous production service.","sourceIds":["dtcc-chainlink"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vechain-vet-network-upgrade-deposit-withdrawal-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-14T02:40:00.000Z","updatedAt":"2026-09-14T02:40:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Binance Vechain Upgrade Support: Deposit, Withdrawal and Trading Checklist for September 16","zh-Hans":"Binance 支持 Vechain 升级：9 月 16 日充值、提现与交易检查清单"},"summary":{"en":"Binance says it plans to suspend Vechain-network deposits and withdrawals at approximately 10:15 UTC on September 16, 2026, one hour before the network upgrade and hard fork expected at block 25,902,540.","zh-Hans":"Binance 表示，计划于 2026 年 9 月 16 日 10:15 UTC 左右暂停 Vechain 网络充值与提现，时间比预计在区块高度 25,902,540 发生的网络升级和硬分叉早一小时。公告称交易预计不受影响，升级后网络被认为稳定时会重新开放充值和提现，且不会另发恢复公告。因此，用户应把交易所内交易可用性与区块链转账可用性分开，并在转移 VET 前核对实时充值和提现界面。"},"claims":[{"id":"c1","text":"Binance schedules the deposit and withdrawal suspension for approximately September 16, 2026 at 10:15 UTC.","sourceIds":["binance-vet","binance-square"],"risk":"medium"},{"id":"c2","text":"The network upgrade and hard fork are expected at block 25,902,540 or approximately 11:15 UTC.","sourceIds":["binance-vet","binance-square"],"risk":"medium"},{"id":"c3","text":"The notice says trading of tokens on the Vechain network will not be impacted by the maintenance window.","sourceIds":["binance-vet"],"risk":"low"},{"id":"c4","text":"Deposits and withdrawals are to reopen after Binance considers the upgraded network stable, and the notice says no further announcement will be posted.","sourceIds":["binance-vet"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fsb-crypto-framework-implementation-gaps-cross-border-checklist","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-14T02:40:00.000Z","updatedAt":"2026-09-14T02:40:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"FSB Crypto Framework Review: What 'Regulated' Does Not Prove Across Borders","zh-Hans":"FSB 加密框架评估：跨境场景中“受监管”不能证明什么"},"summary":{"en":"The FSB's 2025 thematic review found progress in implementing its 2023 crypto framework but also significant gaps and inconsistencies, with global-stablecoin implementation lagging and uneven rules creating regulatory-arbitrage and cross-border oversight problems.","zh-Hans":"FSB 的 2025 年专题评估认为，各司法辖区落实 2023 年加密框架已经取得进展，但仍存在显著缺口和不一致，全球稳定币安排的落实更滞后，不均衡规则还会制造监管套利与跨境监督难题。因此，对用户而言，“受监管”标签只是残缺证据。真实评估必须识别准确法律实体、司法辖区、获准活动、产品、客户所在地、托管链、披露、报告义务、赎回权与跨境协作路径。"},"claims":[{"id":"c1","text":"The FSB review used information available as of August 2025 and examined implementation, data reporting, disclosures, risk monitoring and cross-border cooperation.","sourceIds":["fsb-review"],"risk":"medium"},{"id":"c2","text":"The review found progress for crypto-asset activities but less progress for global stablecoin arrangements.","sourceIds":["fsb-review","fsb-hub"],"risk":"medium"},{"id":"c3","text":"The FSB reported significant gaps and inconsistencies and said uneven implementation can enable regulatory arbitrage and complicate global oversight.","sourceIds":["fsb-review"],"risk":"low"},{"id":"c4","text":"The FSB's stablecoin recommendations cover cross-border cooperation, governance, risk management, data, recovery, disclosures and redemption rights.","sourceIds":["fsb-gsc"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"jupiter-vs-raydium-solana-swap-routing-execution-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-14T02:40:00.000Z","updatedAt":"2026-09-15T10:54:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Jupiter vs Raydium for Solana Swaps: Routing, Slippage and Execution Controls","zh-Hans":"Jupiter 与 Raydium 的 Solana 兑换对比：路由、滑点与执行控制"},"summary":{"en":"Jupiter and Raydium solve different Solana swap jobs. Compare routing, execution controls and integration status before relying on either path.","zh-Hans":"Jupiter 与 Raydium 解决的是重叠但并不完全相同的 Solana 兑换任务。Jupiter 当前报价 API 可以跨多个 DEX 来源搜索路径，并公开路由计划、价格影响、ExactIn/ExactOut 控制与中间代币限制。Raydium 路由器主要围绕 Raydium 流动性，在其资金池之间构建原子化的单跳、多跳或拆分路径。安全的选择不是一个永久赢家：签名前应在同一代币 Mint、输入规模和时间点下比较路由、最低输出、价格影响、优先费、交易模拟与失败行为。"},"claims":[{"id":"c1","text":"Jupiter recommends Swap V2 /order and /execute, where multiple routing engines compete and managed execution reports the actual result.","sourceIds":["jupiter-v2-order","jupiter-v2-execute"],"risk":"medium"},{"id":"c2","text":"Jupiter says Metis Swap V1 is no longer actively maintained and has been superseded by Swap V2.","sourceIds":["jupiter-quote","jupiter-v1-migration"],"risk":"low"},{"id":"c3","text":"Raydium documents atomic single-hop, multi-hop and split routing across its liquidity pools.","sourceIds":["raydium-router","raydium-swap"],"risk":"low"},{"id":"c4","text":"Raydium requires clients to handle stale quotes, per-hop minimum amounts and transaction failure rather than treating a displayed quote as guaranteed execution.","sourceIds":["raydium-aggregator"],"risk":"low"}],"relatedVenues":["jupiter","raydium"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-api-key-least-privilege-permissions-tutorial","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-14T02:40:00.000Z","updatedAt":"2026-09-14T02:40:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken API Key Setup Tutorial: Least Privilege, IP Restrictions and Safe Revocation","zh-Hans":"Kraken API 密钥设置教程：最小权限、IP 限制与安全撤销"},"summary":{"en":"Create a Kraken API key only after defining one integration job and verifying Kraken's official domain and current account availability. In Kraken Pro, open Settings, choose API and create a uniquely named key.","zh-Hans":"只有在明确一个集成任务、核验 Kraken 官方域名并确认当前账户可用性后，才应创建 API 密钥。在 Kraken Pro 中进入 Settings，选择 API，并创建唯一命名的密钥。只授予该任务必需的权限；只读报表工具不应交易或提现，交易工具通常也不需要 Withdraw Funds。在兼容情况下添加 IP 白名单、到期时间与 API 密钥双重验证，只把 Secret 存入加密秘密存储，先测试最小无害调用，并及时撤销闲置密钥。"},"claims":[{"id":"c1","text":"Kraken describes API keys as the API equivalent of an account username and password and says secrets must not be stored unencrypted.","sourceIds":["kraken-create","kraken-security"],"risk":"medium"},{"id":"c2","text":"Kraken's creation guide separates query, trading, funding, ledger, export and WebSocket permissions.","sourceIds":["kraken-create"],"risk":"medium"},{"id":"c3","text":"Kraken's example says a trading integration would normally need modify and cancel permissions but almost certainly not Withdraw Funds.","sourceIds":["kraken-create"],"risk":"low"},{"id":"c4","text":"Kraken documents IP whitelisting, key expiration, API-key 2FA, regular rotation and deletion of keys that are no longer relevant.","sourceIds":["kraken-create","kraken-security"],"risk":"low"}],"relatedVenues":["kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-order-book-checksum-deprecation-sequence-integrity-radar","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-14T02:40:00.000Z","updatedAt":"2026-10-13T05:00:00.000Z","readTime":"8 min","readTimeByLocale":{"en":"8 min","zh-Hans":"8 min"},"author":"NexuAlpha Research Desk","title":{"en":"OKX Order Book Checksum Removed (2026): Switch to seqId","zh-Hans":"OKX 订单簿完整性雷达：校验和弃用、序列缺口与重新同步"},"summary":{"en":"Since June 23, 2026 OKX sends checksum 0 on books, books-l2-tbt and books50-l2-tbt. Validate seqId and prevSeqId, and resync from a snapshot on any gap.","zh-Hans":"OKX 已于 2026 年 6 月 23 日在生产环境弃用 books、books-l2-tbt 与 books50-l2-tbt JSON WebSocket 频道的订单簿校验和验证。checksum 字段仍然存在，但固定为 0，不能再用于完整性检查；客户端应通过 seqId 与 prevSeqId 验证连续性。可靠的消费者必须把序列链断裂视为状态丢失事件，丢弃可疑本地订单簿，重新获取完整快照，并只在新的序列链连续后恢复使用。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"OKX's production checksum deprecation took effect on June 23, 2026 for books, books-l2-tbt and books50-l2-tbt JSON WebSocket channels.","sourceIds":["okx-notice","okx-changelog"],"risk":"medium"},{"id":"c2","text":"The checksum field remains in affected messages but is fixed to zero and is no longer an integrity signal.","sourceIds":["okx-notice","okx-api"],"risk":"medium"},{"id":"c3","text":"OKX instructs clients to use seqId and prevSeqId for continuity and accuracy checks.","sourceIds":["okx-notice","okx-api"],"risk":"low"},{"id":"c4","text":"Kraken's futures book feed also exposes a sequence number on snapshots and deltas, illustrating that ordered state application is a separate control from transport encryption.","sourceIds":["kraken-book"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"coinbase-address-allowlist-setup-network-hold-tutorial","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-13T23:39:00.000Z","updatedAt":"2026-09-15T10:54:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up a Coinbase Address Allowlist, Verify the Network and Respect the Hold","zh-Hans":"如何设置 Coinbase 地址允许名单、核对网络并遵守等待期"},"summary":{"en":"Start from the official Coinbase domain or app, then confirm the exact allowlist workflow before changing withdrawal addresses.","zh-Hans":"应从 Coinbase 官方域名或已安装 App 开始，确认准确产品中登录后的功能，并且不要把密码、两步验证码、私钥、助记词或身份文件复制到笔记或聊天。Coinbase.com 文档给出的路径是“个人资料 > 设置 > Allow list”，Coinbase Exchange 则使用独立的 Address Book 流程，两套界面不能混用。启用、关闭或新增地址可能触发等待期，同时资产和网络必须与收款端匹配。应先添加一个已核验目的地，等待界面明确显示可用，再次比较完整地址与网络，最后先做小额测试转账。"},"claims":[{"id":"c1","text":"Coinbase.com documents a signed-in path through Profile, Settings and Allow list and requires access to the user's 2-step verification method.","sourceIds":["coinbase-allowlist","coinbase-security"],"risk":"medium"},{"id":"c2","text":"Coinbase says a newly added allowlist address becomes available for sends after 48 hours in the documented Coinbase.com workflow.","sourceIds":["coinbase-allowlist"],"risk":"medium"},{"id":"c3","text":"Coinbase Exchange has a separate Address Book and whitelisting workflow with its own initial window and later hold behavior.","sourceIds":["coinbase-exchange","coinbase-holds"],"risk":"low"},{"id":"c4","text":"Coinbase troubleshooting guidance says the recipient address and expected network must match and that wrong-network sends may be unrecoverable.","sourceIds":["coinbase-send"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-staked-eth-vs-lido-steth-exit-liquidity-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-13T23:39:00.000Z","updatedAt":"2026-09-13T23:39:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Staked ETH vs Lido stETH: Exit Liquidity, Custody and Conversion Controls","zh-Hans":"Coinbase 质押 ETH 与 Lido stETH 对比：退出流动性、托管与转换控制"},"summary":{"en":"Coinbase staked ETH and Lido stETH both provide exposure to Ethereum staking, but they create different control surfaces.","zh-Hans":"Coinbase 质押 ETH 与 Lido stETH 都提供以太坊质押敞口，但控制边界不同。Coinbase 依赖符合资格的托管账户，提供标准解质押，在部分情况下提供收费的即时解质押，并在适用地区支持 cbETH 包装。Lido 通过智能合约发行可转移的流动性质押代币，协议退出采用先进先出的申请、最终确认与领取流程，同时还存在协议外的二级市场退出。选择应取决于地区、托管偏好、代币与合约风险、转换率、退出路径、费用、队列状态、税务处理，以及用户是否能安全操作自托管钱包。"},"claims":[{"id":"c1","text":"Coinbase says eligible users can request standard unstaking and may see an instant unstaking route with a fee and availability limitations.","sourceIds":["coinbase-stake","coinbase-eth"],"risk":"medium"},{"id":"c2","text":"Coinbase describes cbETH as a transferable representation of staked ETH whose market price can differ from the underlying staked ETH value.","sourceIds":["coinbase-cbeth"],"risk":"medium"},{"id":"c3","text":"Lido documents a FIFO withdrawal queue that locks stETH or wstETH, mints an unstETH NFT, finalizes the request and later allows an ETH claim.","sourceIds":["lido-queue"],"risk":"low"},{"id":"c4","text":"Lido's risk disclosure separates protocol withdrawals from secondary-market transactions and warns that withdrawal queues and market exits have different risks.","sourceIds":["lido-risk","lido-queue"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"imf-stablecoin-shocks-treasury-dollar-equity-transmission-study","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-13T23:39:00.000Z","updatedAt":"2026-09-13T23:39:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"IMF Stablecoin Shocks Study: Treasury-Yield, Dollar and Equity Transmission Without False Certainty","zh-Hans":"IMF 稳定币冲击研究：国债收益率、美元与股票传导及其证据边界"},"summary":{"en":"An IMF Working Paper published on March 6, 2026 develops event-study and structural-vector-autoregression measures of USDC and USDT demand shocks.","zh-Hans":"IMF 于 2026 年 3 月 6 日发布的一篇工作论文，使用事件研究与结构向量自回归方法构建 USDC 和 USDT 需求冲击指标。作者报告短期美国国债收益率持续下降、美元贬值，以及对加密和股票市场的渐进传导，并观察到企业层面的差异。它是研究中的工作论文，不是 IMF 政策结论，也不是交易信号。读者必须把论文的识别假设、样本、叙事事件和估计的总体响应，与对未来稳定币事件、单只证券或投资组合的预测分开。"},"claims":[{"id":"c1","text":"The IMF published Stablecoin Shocks as Working Paper 2026/044 on March 6, 2026.","sourceIds":["imf-paper","imf-pdf"],"risk":"medium"},{"id":"c2","text":"The authors combine a daily narrative dataset with movements in USDC and USDT market capitalization and use event-study and SVAR-IV methods.","sourceIds":["imf-paper","imf-pdf"],"risk":"medium"},{"id":"c3","text":"The paper reports persistent declines in short-term Treasury yields, U.S.-dollar depreciation and gradual spillovers into crypto and equity markets after identified demand shocks.","sourceIds":["imf-paper","imf-pdf"],"risk":"low"},{"id":"c4","text":"The publication page states that IMF Working Papers describe research in progress and do not necessarily represent IMF or Executive Board views.","sourceIds":["imf-paper"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"iosco-financial-asset-tokenization-interoperability-settlement-risks","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-13T23:39:00.000Z","updatedAt":"2026-09-13T23:39:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"IOSCO Financial-Asset Tokenization Report: Interoperability, Settlement Assets and Investor-Rights Boundaries","zh-Hans":"IOSCO 金融资产代币化报告：互操作、结算资产与投资者权利边界"},"summary":{"en":"IOSCO's November 2025 final report treats financial-asset tokenization as a growing but still nascent capital-markets development.","zh-Hans":"IOSCO 在 2025 年 11 月发布的最终报告把金融资产代币化视为正在增长但仍处早期的资本市场发展。报告承认效率与透明度方面的潜在价值，同时强调互操作缺口、可信结算资产不足、基础设施碎片化，以及既有的投资者保护和市场诚信风险都会限制规模化。该报告不会为某个代币化产品背书。用户仍需针对具体工具追踪法律权利、权威所有权记录、转让限制、结算资产、托管链、披露、赎回与破产处理。"},"claims":[{"id":"c1","text":"IOSCO published its final report on tokenization of financial assets in November 2025.","sourceIds":["iosco-report","iosco-release"],"risk":"medium"},{"id":"c2","text":"The report draws on commercial use cases including tokenized money market funds and fixed-income instruments.","sourceIds":["iosco-report","iosco-release"],"risk":"medium"},{"id":"c3","text":"IOSCO describes adoption as growing but still nascent and identifies interoperability challenges and limited credible settlement assets as scaling constraints.","sourceIds":["iosco-report","iosco-release"],"risk":"low"},{"id":"c4","text":"The report examines market-integrity and investor-protection implications rather than approving individual products.","sourceIds":["iosco-report","iosco-release"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kraken-vs-deribit-cancel-on-disconnect-dead-man-switch-radar","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-13T23:39:00.000Z","updatedAt":"2026-09-13T23:39:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Kraken vs Deribit Cancel-on-Disconnect Radar: Timeout, Scope and Failure-State Controls","zh-Hans":"Kraken 与 Deribit 断线撤单雷达：超时、作用域与故障状态控制"},"summary":{"en":"Kraken Futures and Deribit both document controls that can cancel resting orders after connectivity failure, but they use different activation models.","zh-Hans":"Kraken Futures 与 Deribit 都公开了连接故障后撤销挂单的控制，但激活模式不同。Kraken 的期货“死亡开关”是可续期倒计时：客户端持续推迟超时，文档建议每 15–20 秒调用一次并设置 60 秒超时。Deribit 的断线撤单仅适用于 WebSocket，可按单连接或账户作用域应用到新连接，并建议用心跳更快识别失效连接；正常 logout 是文档明确的例外。任何控制都不能单独证明所有订单已经撤销。系统必须在非生产环境测试作用域、触发时间、部分成交、重连行为和事件后的权威对账。"},"claims":[{"id":"c1","text":"Kraken Futures documents a countdown that cancels user orders when the timeout expires unless the client renews or disables it.","sourceIds":["kraken-dms"],"risk":"medium"},{"id":"c2","text":"Kraken recommends refreshing every 15 to 20 seconds with a 60-second timeout as an example operating pattern.","sourceIds":["kraken-dms"],"risk":"medium"},{"id":"c3","text":"Deribit documents WebSocket-only cancel-on-disconnect with connection and account scopes, where connection scope does not affect orders created by other connections.","sourceIds":["deribit-cod","deribit-connection"],"risk":"low"},{"id":"c4","text":"Deribit says heartbeat detection can improve triggering and that private logout does not trigger cancel-on-disconnect.","sourceIds":["deribit-cod","deribit-connection"],"risk":"low"}],"relatedVenues":["deribit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-himsb-crmb-bstocks-margin-collateral-boundaries","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-13T20:40:00.000Z","updatedAt":"2026-09-13T20:40:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Binance HIMSB and CRMB bStocks as Margin Collateral: Eligibility, Borrowing and Ownership Boundaries","zh-Hans":"Binance HIMSB 与 CRMB bStocks 保证金抵押品：资格、借贷与所有权边界"},"summary":{"en":"Binance added HIMSB and CRMB bStocks as collateral for Cross Margin, Portfolio Margin and Portfolio Margin Pro on September 9, 2026 at 12:00 UTC.","zh-Hans":"Binance 于 2026 年 9 月 9 日 12:00 UTC 把 HIMSB 与 CRMB bStocks 加入全仓杠杆、统一账户与统一账户专业版的抵押品范围。官方公告把资格限定为允许地区内符合条件的 VIP 3 级或以上用户，说明这些资产不支持借贷，并明确 bStocks 是证书而非对标的股票的直接所有权。因此，用户在把它们视为可用保证金前，必须核对地区、VIP 等级、抵押率、产品入口、发行文件与强平处理方式。"},"claims":[{"id":"c1","text":"Binance states that HIMSB and CRMB became margin collateral on September 9, 2026 at 12:00 UTC.","sourceIds":["binance-collateral","binance-collateral-verified"],"risk":"medium"},{"id":"c2","text":"The notice names Cross Margin, Portfolio Margin and Portfolio Margin Pro as the covered account modes.","sourceIds":["binance-collateral"],"risk":"medium"},{"id":"c3","text":"Eligibility is limited to VIP 3 or higher users in permitted jurisdictions, and borrowing of the two bStocks is not supported.","sourceIds":["binance-collateral"],"risk":"low"},{"id":"c4","text":"The notice describes bStocks as certificates and says holders do not directly own the underlying shares.","sourceIds":["binance-collateral","binance-spot"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"exchange-user-websocket-order-state-reconciliation-radar","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-13T20:40:00.000Z","updatedAt":"2026-09-13T20:40:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Exchange User WebSocket Order-State Radar: Binance, Coinbase and OKX Reconciliation Rules","zh-Hans":"交易所用户 WebSocket 订单状态雷达：Binance、Coinbase 与 OKX 对账规则"},"summary":{"en":"Binance, Coinbase and OKX all expose authenticated WebSocket streams for user order state, but their bootstrap and lifecycle rules differ. Coinbase's user channel sends open-order snapshots in batches before subsequent updates.","zh-Hans":"Binance、Coinbase 与 OKX 都提供经过认证的用户订单 WebSocket 流，但初始化与连接生命周期规则不同。Coinbase 的 user 频道会先分批发送未完成订单快照，再推送后续更新；Binance 公布 listenKey 过期与续期要求，并提供事件排序指引；OKX 的 orders 频道不会在订阅时推送初始快照，只在新订单或订单更新时发送消息，其交易指引也强调，请求确认只是被接收，不等于撤单或改单已经最终完成。可靠系统必须设置 REST 快照边界、去重、序列或时间戳检查、重连恢复，并且只用权威终态事件关闭订单状态机。"},"claims":[{"id":"c1","text":"Coinbase documents that its user channel sends open orders in batches of 50 before subsequent updates, with a smaller batch indicating snapshot completion.","sourceIds":["coinbase-user"],"risk":"medium"},{"id":"c2","text":"Binance documents a 60-minute listenKey lifetime, keepalive or recreation requirements and ordering guidance for the same event type.","sourceIds":["binance-user"],"risk":"medium"},{"id":"c3","text":"OKX states that its orders channel sends no initial subscription snapshot and pushes only new orders or order updates.","sourceIds":["okx-api"],"risk":"low"},{"id":"c4","text":"OKX says a successful cancel or amend acknowledgement means the request was accepted, while the orders-channel update provides the authoritative result.","sourceIds":["okx-trading","okx-api"],"risk":"low"}],"relatedVenues":["binance","coinbase","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"franklin-onchain-fund-sec-no-action-custody-record-boundary","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-13T20:40:00.000Z","updatedAt":"2026-09-13T20:40:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Franklin OnChain Fund SEC No-Action Letter: Custody, Records and the Fact-Specific Boundary","zh-Hans":"Franklin OnChain 基金 SEC 不采取行动函：托管、记录与事实特定边界"},"summary":{"en":"S. Government Money Fund and the custody framework under Section 17(f) and Rule 17f-2.","zh-Hans":"2026 年 8 月 12 日，SEC 投资管理部门工作人员就关联基金投资 Franklin OnChain U.S. Government Money Fund 以及《投资公司法》第 17(f) 条和 Rule 17f-2 下的托管安排，发布了一份基于特定事实的不采取行动答复。来函说明，正式份额记录通过集成记录系统维护，所有权采用账簿登记，并由独立会计师执行对账与核验。该答复不是对所有代币化基金或区块链托管设计的普遍监管批准；每个产品仍需单独分析法律实体、权威记录、转让、赎回、托管与异常处理。"},"claims":[{"id":"c1","text":"SEC staff published the Franklin Templeton no-action response on August 12, 2026.","sourceIds":["sec-response"],"risk":"medium"},{"id":"c2","text":"The request concerns affiliated registered funds investing in the Franklin OnChain U.S. Government Money Fund and custody under Section 17(f) and Rule 17f-2.","sourceIds":["sec-response","sec-incoming"],"risk":"medium"},{"id":"c3","text":"The incoming letter describes official share records maintained on an integrated recordkeeping system using book-entry ownership.","sourceIds":["sec-incoming"],"risk":"low"},{"id":"c4","text":"The incoming letter describes independent-accountant reconciliation and verification, while the staff response remains tied to the represented facts.","sourceIds":["sec-incoming","sec-response"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"oecd-carf-2027-crypto-reporting-implementation-readiness","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-13T20:40:00.000Z","updatedAt":"2026-09-13T20:40:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"OECD CARF 2027 Readiness: What Crypto Platforms and Users Should Verify Before First Exchanges","zh-Hans":"OECD CARF 2027 实施准备：首次信息交换前平台与用户应核对什么"},"summary":{"en":"The OECD Global Forum reports that 76 jurisdictions are formally committed to implement the Crypto-Asset Reporting Framework, with most planning to begin automatic exchange of crypto-asset transaction information by 2027.","zh-Hans":"OECD 全球论坛表示，已有 76 个司法辖区正式承诺实施《加密资产报告框架》（CARF），其中大多数计划自 2027 年开始自动交换加密资产交易信息。CARF 是报告与信息交换框架，不是统一的交易税，也不能证明所有平台、钱包和用户适用完全相同的规则。平台与用户应依据当前本地法律和官方指引，逐项确认实施司法辖区、负责报告的服务提供商、覆盖资产与交易、税收居民身份与自我证明流程、数据更正路径及首个报告期。"},"claims":[{"id":"c1","text":"The OECD Global Forum states that 76 jurisdictions are formally committed to implement CARF.","sourceIds":["oecd-forum","oecd-update"],"risk":"medium"},{"id":"c2","text":"The Global Forum says most committed jurisdictions are set to begin automatic exchanges of crypto-asset transaction information by 2027.","sourceIds":["oecd-forum","oecd-update"],"risk":"medium"},{"id":"c3","text":"The 2025 implementation update was approved by the CARF Group and adopted by Global Forum members in November 2025.","sourceIds":["oecd-update"],"risk":"low"},{"id":"c4","text":"The OECD has published a CARF XML schema and continued regional implementation capacity building in 2026.","sourceIds":["oecd-schema","oecd-capacity"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-anti-phishing-code-setup-email-verification-tutorial","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-13T20:40:00.000Z","updatedAt":"2026-09-13T20:40:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up an OKX Anti-Phishing Code and Verify Security Emails","zh-Hans":"如何设置 OKX 防钓鱼码并核验安全邮件"},"summary":{"en":"Start only from the official OKX domain or installed app and first confirm that the security feature exists for your account and region. In the app, OKX documents the path Menu > Security > Anti-phishing code.","zh-Hans":"只能从 OKX 官方域名或已安装 App 开始，并先确认该安全功能适用于你的账户和地区。OKX 文档给出的 App 路径是“菜单 > 安全 > 防钓鱼码”。选择一个不与密码、恢复信息或其他秘密重复的私人代码，在登录后的界面保存，然后核验后续官方 OKX 邮件是否准确显示该代码。缺失或不匹配应立即停止操作，但它本身不能单独证明哪个发件人真实；还要检查发件域名、链接与邮件认证结果，并且绝不能通过邮件提供密码、助记词、私钥、身份文件或一次性验证码。"},"claims":[{"id":"c1","text":"OKX documents the app path Menu, Security, Anti-phishing code for setting the control.","sourceIds":["okx-code"],"risk":"medium"},{"id":"c2","text":"OKX says official emails should include the configured anti-phishing code and a missing or mismatched code should be treated as suspicious.","sourceIds":["okx-code","okx-security"],"risk":"medium"},{"id":"c3","text":"OKX's security guide also recommends authenticator or passkey controls in addition to email verification.","sourceIds":["okx-security"],"risk":"low"},{"id":"c4","text":"OKX's phishing-email guidance recommends checking the sender domain and SPF, DKIM and DMARC results and says sensitive secrets should never be shared by email.","sourceIds":["okx-email"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-spot-order-price-protection-disclosure-audit","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-13T17:42:00.000Z","updatedAt":"2026-09-13T17:42:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Spot-Order Price Protection Audit: Binance and OKX Execution Boundaries","zh-Hans":"加密现货订单价格保护审计：Binance 与 OKX 的成交边界"},"summary":{"en":"Binance and OKX both publish spot-order price-protection controls, but the documented outcomes differ. Binance's Spot Price Range Execution Rule says taker executions outside a dynamic range expire.","zh-Hans":"Binance 与 OKX 都公开了现货订单价格保护控制，但文档中的处理结果并不相同。Binance 的现货价格区间执行规则说明，落在动态区间之外的吃单成交会失效；OKX 公布动态价格限制，并在 2026 年 6 月调整后说明，现货市价单可在允许区间内部分成交，超出区间的剩余数量会被取消。这些机制可以减少异常价格成交，但不保证一定成交、最优执行或不发生亏损。自动化系统必须读取拒绝或部分成交状态，核对剩余数量后才能重试。"},"claims":[{"id":"c1","text":"Binance announced gradual introduction of its Spot Price Range Execution Rule from April 14, 2026.","sourceIds":["binance-prer"],"risk":"medium"},{"id":"c2","text":"Binance says taker order portions outside the dynamic execution range expire rather than execute at those prices.","sourceIds":["binance-prer"],"risk":"medium"},{"id":"c3","text":"OKX documents dynamically calculated upper and lower price limits and rejection or adjustment behavior when orders breach them.","sourceIds":["okx-price","okx-orders"],"risk":"low"},{"id":"c4","text":"OKX's June 29, 2026 update says spot market orders can be partially filled within the price limit and the outside-range remainder cancelled.","sourceIds":["okx-update"],"risk":"low"}],"relatedVenues":["binance","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-flockusdt-perpetual-listing-contract-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-13T17:42:00.000Z","updatedAt":"2026-09-13T17:42:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"OKX FLOCKUSDT Perpetual Listing: Contract Terms, Funding and Eligibility Checklist","zh-Hans":"OKX 上线 FLOCKUSDT 永续合约：合约条款、资金费率与资格清单"},"summary":{"en":"OKX announced that FLOCK/USDT perpetual futures opened on September 12, 2026 at 10:00 UTC across web, app and API, subject to account and regional availability.","zh-Hans":"OKX 公告称，FLOCK/USDT 永续合约已于 2026 年 9 月 12 日 10:00 UTC 在网页、App 与 API 开放，但实际使用仍取决于账户和地区资格。公告披露其以 USDT 结算、面值为 100、杠杆范围 0.01 倍至 20 倍、通常每四小时结算资金费率；达到上限或下限时，结算周期可能缩短为每小时。上线不代表适合任何用户。下单前应在登录后的合约页核对指数构成、最小价格与数量单位、当前资金费率周期、保证金模式、强平触发价和当地产品资格。"},"claims":[{"id":"c1","text":"OKX published the FLOCK perpetual listing on September 12, 2026 with a stated opening time of 10:00 UTC.","sourceIds":["okx-flock"],"risk":"medium"},{"id":"c2","text":"The announcement lists FLOCK/USDT index exposure, USDT settlement, face value 100 and leverage from 0.01x to 20x.","sourceIds":["okx-flock"],"risk":"medium"},{"id":"c3","text":"OKX states a four-hour funding interval that can change to hourly when the funding-rate cap or floor is reached.","sourceIds":["okx-flock"],"risk":"low"},{"id":"c4","text":"The official page warns that the product and terms may not apply to every customer and directs users to verify availability in the account.","sourceIds":["okx-flock"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"paxos-securities-settlement-temporary-clearing-agency-registration","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-13T17:42:00.000Z","updatedAt":"2026-09-13T17:42:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Paxos Securities Settlement Temporary Registration: Scope, Duration and Settlement Boundaries","zh-Hans":"Paxos 证券结算临时注册：范围、期限与结算边界"},"summary":{"en":"The SEC granted Paxos Securities Settlement Company temporary registration as a clearing agency on May 27, 2026 for a period not exceeding 18 months, with specified exemptions and conditions.","zh-Hans":"SEC 于 2026 年 5 月 27 日向 Paxos Securities Settlement Company 授予临时清算机构注册，期限不超过 18 个月，并附带特定豁免与条件。该命令针对界定明确的中央证券存管与证券结算系统角色，并非对所有 Paxos 产品、代币化证券、经纪商或零售界面的全面批准。判断实际可用服务前，应分别核对注册法律实体、合资格证券、参与者要求、结算资产、托管与记录、运营条件以及临时注册到期后的路径。"},"claims":[{"id":"c1","text":"The SEC order dated May 27, 2026 grants Paxos Securities Settlement Company temporary registration as a clearing agency.","sourceIds":["sec-order","sec-docket"],"risk":"medium"},{"id":"c2","text":"The order states that the temporary registration period may not exceed 18 months.","sourceIds":["sec-order","sec-crypto"],"risk":"medium"},{"id":"c3","text":"PSSC applied to provide clearance and settlement services as a central securities depository and securities settlement system.","sourceIds":["sec-order","sec-docket"],"risk":"low"},{"id":"c4","text":"The SEC summary states that the order includes exemptions from specified Section 17A provisions, so the scope must be read with its conditions rather than treated as unrestricted approval.","sourceIds":["sec-crypto"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-regulation-crypto-assets-proposal-exemptions-safe-harbor","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-13T17:42:00.000Z","updatedAt":"2026-09-13T17:42:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Regulation Crypto Assets Proposal: Offering Exemptions, Disclosures and the Safe-Harbor Boundary","zh-Hans":"SEC 加密资产监管提案：发行豁免、信息披露与安全港边界"},"summary":{"en":"On August 18, 2026, the SEC proposed Regulation Crypto Assets; it is not final law.","zh-Hans":"SEC 于 2026 年 8 月 18 日提出《加密资产监管》规则，目前不是最终法律。提案拟为特定“受覆盖投资合同”设置两条《证券法》注册豁免：四年内最高 500 万美元，以及每 12 个月最高 7,500 万美元；两者都要求披露，较大额度路径还涉及财务报表与持续报告义务。提案另设与关键管理努力已经完成或永久停止相关的条件性安全港。这些内容不会自动决定某个代币的法律属性，不会替任何发行背书，也不会取消反欺诈义务。"},"claims":[{"id":"c1","text":"The SEC announced Regulation Crypto Assets as a proposed rule on August 18, 2026 and opened it for public comment.","sourceIds":["sec-release","sec-hub"],"risk":"medium"},{"id":"c2","text":"The proposal describes a startup exemption of up to $5 million over four years and a fundraising exemption of up to $75 million per 12 months.","sourceIds":["sec-release","sec-crypto","sec-statement"],"risk":"medium"},{"id":"c3","text":"Both proposed exemptions require narrative disclosures, while the larger route adds financial statements and ongoing reporting.","sourceIds":["sec-release","sec-crypto"],"risk":"low"},{"id":"c4","text":"The proposal includes a conditional safe harbor related to the completion or permanent cessation of represented essential managerial efforts, while antifraud and antimanipulation provisions remain relevant.","sourceIds":["sec-release","sec-crypto","sec-statement"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"uniswap-v3-vs-pancakeswap-v3-concentrated-liquidity-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-13T17:42:00.000Z","updatedAt":"2026-09-13T17:42:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Uniswap v3 vs PancakeSwap v3 Concentrated Liquidity: Range, Fees and Position Controls","zh-Hans":"Uniswap v3 与 PancakeSwap v3 集中流动性对比：价格区间、费用与头寸控制"},"summary":{"en":"Uniswap v3 and PancakeSwap v3 both let liquidity providers allocate capital to chosen price ranges, creating non-fungible positions whose liquidity becomes inactive outside the selected range.","zh-Hans":"Uniswap v3 与 PancakeSwap v3 都允许流动性提供者把资金部署在自选价格区间，并形成不可互换的头寸；价格离开区间后，流动性会停止参与成交。这个共同点不代表两边头寸可以直接互换。所在链、池部署、费率档位、tick 间距、路由、激励、头寸管理合约、Gas 成本与界面行为都可能不同。选择区间前，应先明确谁负责再平衡、多久领取费用、能承受怎样的资产偏移，以及退出路径是否已经测试；集中流动性提高资本利用率的同时，也会把被动持仓变成需要主动管理的头寸。"},"claims":[{"id":"c1","text":"Uniswap v3 documents liquidity positions bounded by lower and upper ticks, with capital inactive when the market price moves outside the selected range.","sourceIds":["uniswap-cl"],"risk":"medium"},{"id":"c2","text":"Uniswap documents multiple pool fee tiers and protocol-version-specific fee behavior rather than one universal LP fee.","sourceIds":["uniswap-fees"],"risk":"medium"},{"id":"c3","text":"PancakeSwap v3 documents non-fungible liquidity positions with user-selected ranges and manually claimable trading fees.","sourceIds":["pancake-pools"],"risk":"low"},{"id":"c4","text":"PancakeSwap says out-of-range positions consist of one token, do not participate in trading and do not earn trading fees while inactive.","sourceIds":["pancake-pools"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-september-11-perpetual-risk-limit-adjustment-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-13T11:40:00.000Z","updatedAt":"2026-09-13T11:40:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit September 11 Perpetual Risk-Limit Adjustment: What Changed and What to Recheck","zh-Hans":"Bybit 9 月 11 日永续合约风险限额调整：变化内容与复核清单"},"summary":{"en":"Bybit announced that maximum leverage for a list of crypto and equity-linked perpetual contracts changed at 08:00 UTC on September 11, 2026.","zh-Hans":"Bybit 公告称，一批加密资产与股票挂钩永续合约的最高杠杆于 2026 年 9 月 11 日 08:00 UTC 调整。界面上的杠杆上限提高既不是建议，也不保证所有持仓都能使用同一倍数。Bybit 当前风险限额文档说明，持仓价值与活动订单价值会推动账户在不同档位之间变化，并改变初始保证金与维持保证金要求。增加风险敞口前，应重新核对实时合约规则、当前档位、有效持仓价值、保证金模式、强平缓冲与未成交订单。"},"claims":[{"id":"c1","text":"Bybit published the adjustment notice on September 9, 2026 with an effective time of September 11 at 08:00 UTC.","sourceIds":["bybit-announcement"],"risk":"medium"},{"id":"c2","text":"The notice lists changed maximum-leverage ceilings for specified contracts rather than a platform-wide entitlement for every account and position.","sourceIds":["bybit-announcement"],"risk":"medium"},{"id":"c3","text":"Bybit says effective position value includes open positions and active orders and can move the account between risk-limit tiers in real time.","sourceIds":["bybit-risk-limit"],"risk":"low"},{"id":"c4","text":"Bybit says higher tiers can increase initial and maintenance margin requirements, while portfolio-margin accounts use a different portfolio-level risk calculation.","sourceIds":["bybit-risk-limit","bybit-faq"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-account-history-export-disclosure-audit","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-13T11:40:00.000Z","updatedAt":"2026-09-13T11:40:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange Account-History Export Audit: Binance, Kraken, KuCoin and MEXC","zh-Hans":"加密交易所账户历史导出审计：Binance、Kraken、KuCoin 与 MEXC"},"summary":{"en":"NexuAlpha's disclosure audit found that all four venues expose account-history export routes, but the exported object, time range, notification method and retention window differ.","zh-Hans":"NexuAlpha 的披露审计发现，四个平台都提供账户历史导出入口，但导出对象、时间范围、通知方式与文件保留期并不一致。Binance 的交易对账单存在每月生成次数限制，下载链接保留七天；Kraken 将对账单、成交、分类账与余额快照分开，并说明订单历史需要从成交记录还原；KuCoin 披露较广的记录类别、单次一年窗口与 30 天链接；MEXC 将综合账户数据与产品特定订单和资金历史分开。可靠归档必须按平台制定采集计划并做余额对账，不能依赖一个通用 CSV 流程。"},"claims":[{"id":"c1","text":"Binance documents limited monthly statement generation, possible multi-report date segmentation and download links that expire after seven days.","sourceIds":["binance-history"],"risk":"medium"},{"id":"c2","text":"Kraken offers Account Statement, Trades, Ledgers and Balances exports, notes that direct order-history export is unavailable, and says generation may take minutes to a week.","sourceIds":["kraken-history"],"risk":"medium"},{"id":"c3","text":"KuCoin documents up to 20 reports per month, a maximum one-year range per export and download links valid for 30 days.","sourceIds":["kucoin-history"],"risk":"low"},{"id":"c4","text":"MEXC exposes a general account-data export and separate product-specific export paths for spot, futures and funding records.","sourceIds":["mexc-history"],"risk":"low"}],"relatedVenues":["binance","kraken","kucoin","mexc"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"kucoin-vs-mexc-trade-history-export-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-13T11:40:00.000Z","updatedAt":"2026-09-13T11:40:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"KuCoin vs MEXC Trade-History Exports: Coverage, Limits and Reconciliation Controls","zh-Hans":"KuCoin 与 MEXC 交易历史导出对比：覆盖范围、限制与对账控制"},"summary":{"en":"KuCoin and MEXC both provide authenticated data-export paths, but their public disclosures do not support treating the files as interchangeable.","zh-Hans":"KuCoin 与 MEXC 都提供登录后的数据导出路径，但公开说明并不支持把两家的文件视为可互换。KuCoin 允许选择账户类别、市场、时间范围、时区以及是否纳入子账户，并披露单次最长一年和每月报告数量上限；MEXC 则提供账户数据、现货订单、合约订单与资金历史等导出入口，文件过大时建议拆分批次。选择时应围绕所需记录、导出窗口、字段、子账户覆盖，以及文件与余额和链上交易哈希的对账结果，而不是只看是否有 CSV 按钮。"},"claims":[{"id":"c1","text":"KuCoin says the web export can cover deposits, withdrawals, spot, margin, convert and fiat-related records and may include all sub-accounts when requested from a master account.","sourceIds":["kucoin-export"],"risk":"medium"},{"id":"c2","text":"KuCoin documents a maximum one-year span per export, up to 20 reports per month, and a 30-day download-link lifetime.","sourceIds":["kucoin-export"],"risk":"medium"},{"id":"c3","text":"MEXC separates general account-data exports from more specific Spot Orders, Futures Orders and Funding History exports.","sourceIds":["mexc-export","mexc-help"],"risk":"low"},{"id":"c4","text":"MEXC advises splitting large requests into smaller batches when a record cannot be generated.","sourceIds":["mexc-help"],"risk":"low"}],"relatedVenues":["kucoin","mexc"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"permissioned-vs-permissionless-tokenization-settlement-architecture","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-13T11:40:00.000Z","updatedAt":"2026-09-13T11:40:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Permissioned vs Permissionless Tokenization: Settlement Anchors, Governance and Interoperability","zh-Hans":"许可链与无许可链代币化：结算锚、治理与互操作性"},"summary":{"en":"Permissioned and permissionless tokenization architectures solve different coordination problems and neither label proves safety or scale.","zh-Hans":"许可链与无许可链代币化解决的是不同协调问题，任何一个标签都不能单独证明安全或规模。BIS 2026 年评估指出，无许可系统可能扩大接入，但常面对流动性碎片化、治理与运营依赖；许可系统能够嵌入身份和合规，却可能形成封闭孤岛。对受监管结算而言，关键问题是法律资产、参与规则、验证者治理、结算资产、最终性、隐私、互操作与恢复路径。没有可信结算锚和运行规则的代币化界面，并不构成完整市场基础设施。"},"claims":[{"id":"c1","text":"The BIS 2026 report distinguishes public permissionless networks from private permissioned systems and evaluates different governance and resilience trade-offs.","sourceIds":["bis-annual","bis-dlt"],"risk":"medium"},{"id":"c2","text":"The report says fragmented base and secondary networks do not seamlessly communicate and may require ad hoc bridges that introduce operational risk.","sourceIds":["bis-annual"],"risk":"medium"},{"id":"c3","text":"The BIS argues that regulated tokenized finance needs sound institutional arrangements, legal frameworks, supervision and a trusted settlement anchor.","sourceIds":["bis-annual","bis-release"],"risk":"low"},{"id":"c4","text":"BIS and Eurosystem materials describe experiments linking tokenized commercial-bank deposits, central-bank reserves and securities workflows while preserving participant and jurisdictional controls.","sourceIds":["bis-annual","bis-money"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-transfer-agent-modernization-tokenized-recordkeeping-proposal","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-13T11:40:00.000Z","updatedAt":"2026-09-13T11:40:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Transfer-Agent Modernization Proposal: Tokenized Records, Ownership and the Rulemaking Boundary","zh-Hans":"SEC 过户代理规则现代化提案：代币化记录、所有权与规则制定边界"},"summary":{"en":"On September 1, 2026, the SEC proposed—not adopted—an overhaul of federal transfer-agent rules that explicitly addresses electronic and blockchain-based recordkeeping and uncertificated securities.","zh-Hans":"SEC 于 2026 年 9 月 1 日提出——而不是已经通过——联邦过户代理规则的全面更新，提案明确涉及电子与区块链记录以及无纸化证券。过户代理仍然关键，因为其维护权威所有权记录，并处理发行、注销与转让。提案拟更新注册和报告，增加处理时限、风险管理与不活跃持有人要求，并引入合规及限制性图例规则。它并不意味着每个钱包记录都自动成为法定股东名册，也不意味着所有代币化股份可以立即自由转让；最终规则、证券文件与权威登记仍具有决定性。"},"claims":[{"id":"c1","text":"The SEC announced a proposed transfer-agent rule modernization on September 1, 2026; it remains a proposal subject to the rulemaking process.","sourceIds":["sec-release","sec-crypto-index"],"risk":"medium"},{"id":"c2","text":"The SEC says the proposal addresses electronic communications, blockchain-based recordkeeping and uncertificated securities.","sourceIds":["sec-release","sec-crypto-index"],"risk":"medium"},{"id":"c3","text":"The proposal includes changes to registration and annual reporting plus proposed requirements for turnaround, risk management, inactive holders, compliance and restrictive legends.","sourceIds":["sec-crypto-index"],"risk":"low"},{"id":"c4","text":"An SEC Commissioner described transfer agents as maintainers of the official ownership record and raised open questions about wallet identifiers and tokenized-share workflows.","sourceIds":["sec-peirce"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-ai-beta-market-insights-evidence-risk-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-13T08:45:00.000Z","updatedAt":"2026-09-13T08:45:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Binance AI Beta: Market-Insight Features, Eligibility and an Evidence-First Risk Checklist","zh-Hans":"Binance AI Beta：市场洞察功能、参与资格与证据优先风险清单"},"summary":{"en":"Binance announced a limited, rolling beta for verified users that aims to surface personalized market context and concise updates. Registration does not guarantee access.","zh-Hans":"Binance 宣布面向已验证用户分批开放一项名额有限的 AI Beta，目标是提供个性化市场背景与简明更新；登记并不保证入选。Binance 自己的公告和 AI Token Report 文档都警告，输出可能不准确、带偏差、包含合成信息或已经过时，不能作为唯一决策依据。应把 Beta 当作研究界面：所有重要结论都要回查带时间戳的第一方数据，也不能给 AI 功能超出已说明任务的账户权限。"},"claims":[{"id":"c1","text":"Binance published the beta announcement on September 7, 2026 and describes a personalized interface, AI market context and concise updates.","sourceIds":["binance-ai-beta"],"risk":"medium"},{"id":"c2","text":"The beta is limited to verified users, capacity is rolling, and registration does not guarantee whitelist placement.","sourceIds":["binance-ai-beta"],"risk":"medium"},{"id":"c3","text":"Binance says AI inputs may contain unvetted third-party content and outputs may include errors, bias, synthetic data or outdated information.","sourceIds":["binance-ai-beta","binance-ai-policy"],"risk":"low"},{"id":"c4","text":"The AI Token Report documentation exposes source labels and says users must verify the information rather than rely on it for decisions.","sourceIds":["binance-ai-report"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-api-rate-limit-disclosure-audit","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-13T08:45:00.000Z","updatedAt":"2026-09-13T08:45:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange API Rate-Limit Disclosure Audit: Binance, Coinbase, Gate and OKX","zh-Hans":"加密交易所 API 速率限制披露审计：Binance、Coinbase、Gate 与 OKX"},"summary":{"en":"Binance, Coinbase Exchange, Gate API v4 and OKX all publish rate-limit controls, but the accounting unit is not interchangeable.","zh-Hans":"Binance、Coinbase Exchange、Gate API v4 与 OKX 都公开了速率限制，但计数单位不能直接互换。Binance 组合使用请求权重、订单计数与 IP 执法；Coinbase 按 IP 或账户档案使用令牌桶；Gate 分开计算公开、私有、下单、钱包和提现请求；OKX 则混合使用 IP、用户、合约与子账户规则。安全集成必须逐端点记录计数单位、时间窗口、突发行为、响应头或错误码以及未知订单恢复，不能只复制一个每秒请求数。"},"claims":[{"id":"c1","text":"Binance documents request-weight and order-count limits, returns 429 for exceeded limits, and may issue escalating IP bans with 418 after repeated violations.","sourceIds":["binance-rest-limits"],"risk":"medium"},{"id":"c2","text":"Coinbase Exchange documents public REST limits by IP and private limits by profile using a lazy-fill token bucket with separate burst capacity.","sourceIds":["coinbase-rest-limits"],"risk":"medium"},{"id":"c3","text":"Gate API v4 publishes separate buckets for public, private, order, cancellation, wallet and withdrawal endpoints and says repeated excess traffic may be delayed or declined.","sourceIds":["gate-api-limits"],"risk":"low"},{"id":"c4","text":"OKX documents different rate-limit keys for public REST, private REST, WebSocket order management, instrument-level trading and aggregate sub-account requests.","sourceIds":["okx-api-limits"],"risk":"low"}],"relatedVenues":["binance","coinbase","gate-io","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"gate-vs-mexc-spot-order-types-control-boundaries","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-13T08:45:00.000Z","updatedAt":"2026-09-13T08:45:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Gate vs MEXC Spot Order Types: Execution Controls, Records and Availability Boundaries","zh-Hans":"Gate 与 MEXC 现货订单类型对比：执行控制、记录与可用性边界"},"summary":{"en":"Gate and MEXC both document spot market and limit orders, but their public materials expose different control sets and surfaces.","zh-Hans":"Gate 与 MEXC 都公开说明了现货市价单和限价单，但不同实体与界面披露的控制集合并不相同。Gate US 的入门指南重点说明市价单与限价单，Gate API 文档还包含有效期和条件单字段；MEXC 则公开列出限价、市价、止盈止损、OCO 与追踪止损。真正有用的比较不是谁的菜单更长，而是行动前核对签约实体、交易对、界面、触发语义、撤销行为和可导出记录。"},"claims":[{"id":"c1","text":"Gate US says its eligible spot interface supports market and limit orders, with market orders prioritizing immediate execution and limit orders using a specified price or better.","sourceIds":["gate-us-spot"],"risk":"medium"},{"id":"c2","text":"Gate API v4 documents additional execution fields and conditional-order structures, but API documentation does not prove those controls are present on every retail interface or regional entity.","sourceIds":["gate-api-spot"],"risk":"medium"},{"id":"c3","text":"MEXC documents five retail spot order types: limit, market, TP/SL, OCO and trailing stop.","sourceIds":["mexc-order-types"],"risk":"low"},{"id":"c4","text":"MEXC distinguishes open and cancelled order history from completed spot statements, so operators need both views for reconciliation.","sourceIds":["mexc-spot-records"],"risk":"low"}],"relatedVenues":["gate-io","mexc"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-kraken-global-settings-lock-safely","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-13T08:45:00.000Z","updatedAt":"2026-10-13T05:00:00.000Z","readTime":"8 min","readTimeByLocale":{"en":"8 min","zh-Hans":"9 min","tr":"5 min","id":"6 min","vi":"8 min"},"author":"NexuAlpha Research Desk","title":{"en":"Kraken Global Settings Lock (GSL): Setup, 1–30 Day Unlock","zh-Hans":"如何安全设置 Kraken 全局设置锁并保留账户恢复路径","tr":"Kraken Global Settings Lock (GSL) nasıl kurulur? Master Key ve bekleme süresi rehberi (2026)","id":"Cara Mengaktifkan Global Settings Lock (GSL) Kraken dengan Aman: Master Key dan Masa Tunggu (2026)","vi":"Cách bật Global Settings Lock (GSL) trên Kraken an toàn: Master Key và thời gian chờ mở khóa (2026)"},"summary":{"en":"Kraken's Global Settings Lock freezes account changes. Create a Master Key first: without one, unlocking waits 1–30 days and support can't speed it up.","zh-Hans":"Kraken 的全局设置锁可以阻止账户设置变更并隐藏敏感信息，但应在登录 2FA、恢复责任人与独立主密钥方案都确定后再启用。解锁等待期必须谨慎选择：如果没有可用主密钥，移除过程会遵循已配置计时器，Kraken 表示客服无法加速。应从 Kraken 官方安全页面激活，只记录非秘密设置，测试恢复责任人，并明确未来哪些变更——包括新增提现地址——会被阻止。","tr":"Kraken GSL, hesap ayarlarını dondurup hassas bilgileri gizler; Master Key olmadan kilit 24 saat ile 30 gün arasında açılır ve destek bunu hızlandıramaz. Önce Master Key ve çekim adreslerini ayarlayın.","id":"GSL Kraken membekukan pengaturan akun dan menyembunyikan data sensitif; tanpa Master Key, kunci baru terbuka setelah 24 jam hingga 30 hari dan dukungan tidak bisa mempercepat. Siapkan Master Key dulu.","vi":"GSL của Kraken đóng băng cài đặt tài khoản và ẩn thông tin nhạy cảm; không có Master Key, mở khóa mất từ 24 giờ đến 30 ngày và hỗ trợ không rút ngắn được. Hãy tạo Master Key và thêm địa chỉ rút trước."},"availableLocales":["en","zh-Hans","tr","id","vi"],"claims":[{"id":"c1","text":"Kraken says Global Settings Lock prevents account-setting changes and hides sensitive account information.","sourceIds":["kraken-gsl-setup","kraken-gsl-overview"],"risk":"medium"},{"id":"c2","text":"Kraken recommends creating a separate Master Key before enabling the lock because it can disable GSL immediately.","sourceIds":["kraken-gsl-setup","kraken-master-key"],"risk":"medium"},{"id":"c3","text":"Without a Master Key, the user must wait for the configured unlock period, and Kraken says support cannot expedite a one-to-thirty-day timer.","sourceIds":["kraken-gsl-setup","kraken-gsl-unlock"],"risk":"low"},{"id":"c4","text":"Kraken says GSL can prevent a new withdrawal address from being added, so setup should follow completion of intended account configuration.","sourceIds":["kraken-gsl-overview"],"risk":"low"}],"relatedVenues":["kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"nasdaq-tokenized-securities-approval-same-cusip-dtc-settlement","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-13T08:45:00.000Z","updatedAt":"2026-09-13T08:45:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Nasdaq Tokenized Securities Approval: Same CUSIP, DTC Settlement and the Real Rights Boundary","zh-Hans":"纳斯达克代币化证券获批：相同 CUSIP、DTC 结算与真实权利边界"},"summary":{"en":"The SEC approved Nasdaq's modified tokenized-securities rule change on March 18, 2026, but approval is not the same as immediate retail availability.","zh-Hans":"SEC 已于 2026 年 3 月 18 日批准纳斯达克修改后的代币化证券规则，但获批不等于零售用户已经能够立即使用。按照获批设计，只有在代币化股份与传统股份可互换、使用相同 CUSIP 与交易代码并赋予同等权利时，两者才进入同一订单簿并享有相同执行优先级。DTC 资产资格、参与者身份、登记钱包、支持网络和上线基础设施仍是独立门槛；不符合条件的代币化指令会回退为传统结算。"},"claims":[{"id":"c1","text":"The SEC order dated March 18, 2026 approves Nasdaq's rule change as modified by Amendment No. 2.","sourceIds":["sec-nasdaq-order","sec-nasdaq-docket"],"risk":"medium"},{"id":"c2","text":"Eligible tokenized shares must be fungible with traditional shares, use the same CUSIP and symbol, and provide equivalent shareholder rights to trade on the same order book with the same priority.","sourceIds":["sec-nasdaq-order"],"risk":"medium"},{"id":"c3","text":"The design communicates a tokenization preference to DTC after execution; if participant, asset, network or wallet requirements fail, DTC settles the trade in traditional form.","sourceIds":["sec-nasdaq-order","dtcc-tokenization"],"risk":"low"},{"id":"c4","text":"The order says implementation depends on DTC infrastructure and post-trade services, with Nasdaq required to provide at least 30 days' notice before trading begins.","sourceIds":["sec-nasdaq-order","dtcc-tokenization"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bitcoin-post-quantum-readiness-workshop-proposals-risk-boundary","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-13T05:45:00.000Z","updatedAt":"2026-09-13T05:45:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Bitcoin Post-Quantum Readiness: Workshop Findings, Draft Proposals and the Real Risk Boundary","zh-Hans":"比特币后量子准备：研讨会结论、草案提案与真实风险边界"},"summary":{"en":"Coinbase's September 9 workshop report says Bitcoin post-quantum work is early: no precise threat date is known, no perfect solution has emerged, and migration would involve protocol, wallet, custody and hardware constraints.","zh-Hans":"Coinbase 9 月 9 日的研讨会报告表明，比特币后量子准备仍处于早期阶段：威胁何时具备现实能力没有精确日期，也没有完美方案，迁移还涉及协议、钱包、托管与硬件限制。相关 BIP 草案讨论潜在输出与迁移路径，NIST 已发布通用后量子标准，但这些事实都不能证明比特币正遭受即时量子攻击，也不能证明某一提案必然被采用。"},"claims":[{"id":"c1","text":"Coinbase says its September 2026 workshop produced no consensus on one post-quantum approach and did not identify an immediate crisis.","sourceIds":["coinbase-workshop"],"risk":"medium"},{"id":"c2","text":"The workshop framed migration as a staged ecosystem process involving protocol design, wallets, custodians and hardware.","sourceIds":["coinbase-workshop"],"risk":"medium"},{"id":"c3","text":"BIP 360 and BIP 361 are draft proposals, not deployed Bitcoin consensus rules.","sourceIds":["bip360","bip361"],"risk":"low"},{"id":"c4","text":"NIST has finalized three general post-quantum cryptography standards, but Bitcoin adoption requires separate protocol and ecosystem decisions.","sourceIds":["nist-pqc","coinbase-workshop"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-vs-okx-multi-asset-collateral-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-13T05:45:00.000Z","updatedAt":"2026-09-13T05:45:00.000Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit vs OKX Multi-Asset Collateral: Haircuts, Risk Sharing and Control Boundaries","zh-Hans":"Bybit 与 OKX 多资产抵押对比：折扣率、风险共担与控制边界"},"summary":{"en":"Bybit and OKX both let eligible users contribute multiple crypto assets to account-level margin, but public terminology and control rules differ.","zh-Hans":"Bybit 与 OKX 都允许合资格用户把多种加密资产计入账户级保证金，但公开术语与控制规则不同。Bybit 在统一交易账户中使用抵押价值率，并说明了可自定义抵押资产及其限制；OKX 在多币种跨仓模式中使用调整后权益与折扣率。用户应比较登录后的资产清单、折扣、借贷状态、移除限制与清算影响，不能把钱包市值直接等同于可用保证金。"},"claims":[{"id":"c1","text":"Bybit says Unified Trading Account margin balance can reflect collateral value ratios rather than the undiscounted wallet value.","sourceIds":["bybit-uta","bybit-modes"],"risk":"medium"},{"id":"c2","text":"Bybit documents restrictions on disabling collateral, including outstanding borrowing and margin-rate constraints.","sourceIds":["bybit-collateral"],"risk":"medium"},{"id":"c3","text":"OKX says selected collateral participates in risk sharing across positions in multi-currency cross-margin mode.","sourceIds":["okx-collateral"],"risk":"low"},{"id":"c4","text":"OKX documents that removing collateral may require repayment and position or order closure, and may be blocked by maintenance-margin requirements.","sourceIds":["okx-collateral","okx-risk"],"risk":"low"}],"relatedVenues":["bybit","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-moov-stablecoin-payments-community-banks-explained","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-13T05:45:00.000Z","updatedAt":"2026-09-13T05:45:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase and Moov Stablecoin Payments for Community Banks: What the Partnership Actually Provides","zh-Hans":"Coinbase 与 Moov 面向社区银行的稳定币支付：合作究竟提供什么"},"summary":{"en":"Coinbase says Moov is integrating Coinbase stablecoin infrastructure into its existing payments platform for community banks and credit unions.","zh-Hans":"Coinbase 表示，Moov 正把 Coinbase 的稳定币基础设施接入其面向社区银行与信用合作社的现有支付平台。公告范围包括收款、结算、付款与实时资金补充，并使用 Coinbase 托管钱包账户和支付 API。这是一项基础设施合作，并不证明所有接入 Moov 的机构都已上线客户产品；可用性、支持资产、费用、托管条款与合规控制仍取决于具体实施。"},"claims":[{"id":"c1","text":"Coinbase announced the partnership on September 10, 2026 and described Moov as serving more than 1,000 community banks and credit unions.","sourceIds":["coinbase-moov","moov-blog"],"risk":"medium"},{"id":"c2","text":"The announcement names consumer payments, merchant acceptance, merchant settlement and payouts as intended use cases.","sourceIds":["coinbase-moov"],"risk":"medium"},{"id":"c3","text":"Coinbase says the integration uses CDP custodial wallet accounts and payment APIs rather than requiring each institution to build a separate crypto stack.","sourceIds":["coinbase-moov","coinbase-api"],"risk":"low"},{"id":"c4","text":"Coinbase's public business documentation shows that product availability, payment fees and supported rails depend on the account and live implementation.","sourceIds":["coinbase-business","coinbase-api"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-change-bitget-google-authenticator-safely","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-13T05:45:00.000Z","updatedAt":"2026-09-13T05:45:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"How to Change Bitget Google Authenticator Safely Without Losing Account Access","zh-Hans":"如何安全更换 Bitget Google Authenticator 且不丢失账户访问"},"summary":{"en":"Bitget documents separate paths for changing Google Authenticator when the old authenticator is available and for unbinding it when it is unavailable.","zh-Hans":"Bitget 对旧验证器仍可用和已经不可用两种情况提供了不同的 Google Authenticator 更换路径。只能从官方 Bitget 域名或 App 开始，保留可用登录会话与已验证联系方式，完成账户内安全核验，绑定新验证器，并在丢弃旧恢复材料前先测试。Bitget 表示，更换后提现与 P2P 交易会受到 24 小时限制。"},"claims":[{"id":"c1","text":"Bitget documents a change flow that first asks whether the current authenticator remains available.","sourceIds":["bitget-change-ga"],"risk":"medium"},{"id":"c2","text":"When the old authenticator is unavailable, Bitget describes an unbinding and security-verification path before a new authenticator is bound.","sourceIds":["bitget-change-ga"],"risk":"medium"},{"id":"c3","text":"Bitget's guide says withdrawals and P2P trading are disabled for 24 hours after changing Google Authenticator.","sourceIds":["bitget-change-ga"],"risk":"low"},{"id":"c4","text":"Bitget advises beginning from official channels and protecting authenticator setup keys and verification codes.","sourceIds":["bitget-change-ga","bitget-security","bitget-official"],"risk":"low"}],"relatedVenues":["bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"mint-issuer-sponsored-tokenized-shares-sec-filing-analysis","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-13T05:45:00.000Z","updatedAt":"2026-09-13T05:45:00.000Z","readTime":"15 min","author":"NexuAlpha Research Desk","title":{"en":"Mint's Issuer-Sponsored Tokenized Shares Plan: What the SEC Filing Proves and What It Does Not","zh-Hans":"Mint 发行人主导代币化股票计划：SEC 文件证明了什么、没有证明什么"},"summary":{"en":"Mint Incorporation's September 3 SEC filing includes a company release describing a plan to tokenize a portion of its Nasdaq-listed Class A shares on Ethereum and Solana.","zh-Hans":"Mint Incorporation 9 月 3 日提交给 SEC 的文件附有公司新闻稿，描述了把部分纳斯达克上市 A 类普通股在 Ethereum 与 Solana 上代币化的计划。文件同时说明，常规纳斯达克证券结算仍继续、代币没有已建立的交易市场、完成取决于监管要求，而且项目可能无法完成。可靠结论只是“已披露的发行人主导计划”，不能写成已经上线、可自由交易的链上股票市场。"},"claims":[{"id":"c1","text":"Mint's SEC-filed exhibit says the company entered a consulting agreement concerning issuer-sponsored tokenization of a portion of its Class A ordinary shares.","sourceIds":["mint-exhibit","mint-6k"],"risk":"medium"},{"id":"c2","text":"The disclosed plan names Ethereum and Solana but says ordinary share trading continues to settle through the conventional Nasdaq securities process.","sourceIds":["mint-exhibit"],"risk":"medium"},{"id":"c3","text":"The filing says there is no established trading market for the tokenized shares and no assurance one will develop or be permitted.","sourceIds":["mint-exhibit"],"risk":"low"},{"id":"c4","text":"The company identifies regulatory, custody, technology, cybersecurity and completion risks, so the filing does not prove a finished product.","sourceIds":["mint-exhibit","sec-tokenized","sec-transfer"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-okx-proof-of-reserves-disclosure-audit","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-13T02:45:00.000Z","updatedAt":"2026-09-15T10:54:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"Binance and OKX Proof of Reserves: A Disclosure and Verification Audit","zh-Hans":"币安与 OKX 储备证明：披露与自助核验审计"},"summary":{"en":"Binance and OKX publish proof-of-reserves systems with user checks, but these are dated reserve disclosures, not full audits.","zh-Hans":"币安与 OKX 都发布了带用户纳入核验和钱包所有权证据的储备证明系统，但储备快照并不等于完整财务审计，也不能保证未来提现。NexuAlpha 的审计核对范围、时间戳、负债处理、资产覆盖、证明文件、自助核验步骤与明确限制。读者应验证本人余额是否被纳入，并把未覆盖资产、链下义务与快照后变化保留为开放问题。"},"claims":[{"id":"c1","text":"Binance documents monthly account snapshots, versioned self-verification tooling and a non-real-time report boundary.","sourceIds":["binance-por","binance-por-verify"],"risk":"medium"},{"id":"c2","text":"Binance states that proof of reserves has point-in-time and off-chain-liability limitations.","sourceIds":["binance-por-method"],"risk":"medium"},{"id":"c3","text":"OKX documents monthly zk-STARK reserve and liability reports, wallet ownership evidence and separate exchange and third-party-custody balances.","sourceIds":["okx-por"],"risk":"medium"},{"id":"c4","text":"OKX says snapshot data can include debts or negative equity from borrowing while later transactions remain outside that snapshot.","sourceIds":["okx-snapshot","okx-por"],"risk":"low"}],"relatedVenues":["binance","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-vs-okx-withdrawal-allowlist-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-13T02:45:00.000Z","updatedAt":"2026-09-13T02:45:00.000Z","readTime":"21 min","author":"NexuAlpha Research Desk","title":{"en":"Binance vs OKX Withdrawal Allowlists: Address Locks, Verification and Safe Setup","zh-Hans":"Binance 与 OKX 提现白名单对比：地址锁、验证与安全配置"},"summary":{"en":"Both Binance and OKX document withdrawal address controls, but their public workflows are not interchangeable.","zh-Hans":"币安与 OKX 都公开了提现地址控制，但两套流程不能直接等同。币安说明了白名单地址与限时提现保护；OKX 则把地址簿、Allowlist、收款人验证和可选的 24 小时新地址锁分开。用户应以本人合资格账户中的实际控制为准，保留应急路径，并在依赖配置前先做小额测试。"},"claims":[{"id":"c1","text":"Binance says enabling its withdrawal whitelist limits withdrawals to addresses saved on the whitelist.","sourceIds":["binance-withdraw"],"risk":"medium"},{"id":"c2","text":"Binance documents security verification when adding addresses and a temporary protection period in parts of its whitelist workflow.","sourceIds":["binance-whitelist"],"risk":"medium"},{"id":"c3","text":"OKX says its Allowlist restricts withdrawals to recipients saved in the withdrawal address book.","sourceIds":["okx-allowlist"],"risk":"low"},{"id":"c4","text":"OKX documents an optional new-address withdrawal lock that prevents use of a newly added recipient for 24 hours.","sourceIds":["okx-allowlist","okx-address-book"],"risk":"low"}],"relatedVenues":["binance","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-odds-fixed-return-contracts-rules-risk-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-13T02:45:00.000Z","updatedAt":"2026-09-13T02:45:00.000Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit Odds Is Live: Fixed-Return Contract Rules, Fees and Risk Checklist","zh-Hans":"Bybit Odds 上线：固定回报合约规则、费用与风险清单"},"summary":{"en":"Bybit describes Odds as a fixed-return product funded from a Trading Account, with Up/Down, Price Target and Price Range contracts.","zh-Hans":"Bybit 将 Odds 描述为从交易账户出资的固定回报产品，包含 Up/Down、Price Target 与 Price Range 三类合约。方向错误或恰好落在边界的平局都可能损失全部投入金额，费用另行收取，目前不支持 API；在跨仓或组合保证金模式下还可能自动借入 USDT。投入前必须在登录账户中核对资格与实时条款。"},"claims":[{"id":"c1","text":"Bybit documents three Odds product types: Up/Down, Price Target and Price Range.","sourceIds":["bybit-intro","bybit-faq"],"risk":"medium"},{"id":"c2","text":"The FAQ says the entire allocated amount is forfeited when the selected outcome is incorrect or a contract resolves as a draw.","sourceIds":["bybit-faq"],"risk":"medium"},{"id":"c3","text":"Bybit publishes a taker-fee formula based on fill value, product fee rate and payout ratio.","sourceIds":["bybit-intro","bybit-faq"],"risk":"low"},{"id":"c4","text":"The FAQ says Odds does not support demo trading or API trading and may use automatic USDT borrowing under eligible margin modes.","sourceIds":["bybit-faq"],"risk":"low"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"esma-mica-register-how-to-check-casp-issuer-status","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-13T02:45:00.000Z","updatedAt":"2026-09-13T02:45:00.000Z","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"ESMA MiCA Interim Register: How to Check a CASP or Token Issuer Without Mistaking Listing for Approval","zh-Hans":"ESMA MiCA 临时登记表：如何核验 CASP 或代币发行人且不把列名误当批准"},"summary":{"en":"ESMA's MiCA Interim Register provides downloadable records for white papers, ART and EMT issuers, authorised crypto-asset service providers and non-compliant entities.","zh-Hans":"ESMA 的 MiCA 临时登记表提供白皮书、ART 与 EMT 发行人、获授权加密资产服务提供商以及不合规实体的可下载记录。列入登记表只是核验输入，并非背书；ESMA 明确说明，登记表中的白皮书没有经过国家主管机关审核或批准。用户应匹配法定名称、标识符、母国、服务范围与更新时间，再向国家主管机关交叉确认。"},"claims":[{"id":"c1","text":"ESMA groups the interim-register data into crypto-asset white papers, ART issuers, EMT issuers, authorised CASPs and non-compliant entities.","sourceIds":["esma-register"],"risk":"medium"},{"id":"c2","text":"The ESMA page identifies September 9, 2026 as the latest update visible during this review.","sourceIds":["esma-register"],"risk":"medium"},{"id":"c3","text":"ESMA warns that white papers recorded in the register have not been reviewed or approved by national competent authorities.","sourceIds":["esma-register"],"risk":"low"},{"id":"c4","text":"MiCA authorisation and transitional arrangements require reading the legal entity, jurisdiction, service scope and applicable dates rather than relying on a brand name.","sourceIds":["esma-transition","eurlex-mica"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-binance-anti-phishing-code","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-13T02:45:00.000Z","updatedAt":"2026-10-11T13:30:00.000Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"How to Create a Binance Anti-Phishing Code (6–8 Characters)","zh-Hans":"如何设置币安反钓鱼码并安全核验消息"},"summary":{"en":"Create your Binance anti-phishing code on the signed-in Security page: 6–8 characters from at least three of upper, lower, digits and underscore.","zh-Hans":"币安反钓鱼码是用户自行设置的标记，启用后应出现在真实的币安邮件与短信中。只能从登录后的 Security 页面创建，选择容易识别但不是密码或恢复码的值，完成 2FA 或通行密钥验证；如果标记缺失或错误，应视为警告，但不能把它当成唯一真伪标准。登录前还要独立核对发件域名与目标网址。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"Binance says the anti-phishing code is a user-defined marker included in genuine Binance emails and SMS after activation.","sourceIds":["binance-antiphishing"],"risk":"medium"},{"id":"c2","text":"Binance requires 6 to 8 characters using at least three of uppercase letters, lowercase letters, digits and underscores, with no other special characters, followed by 2FA or passkey confirmation.","sourceIds":["binance-antiphishing"],"risk":"medium"},{"id":"c3","text":"Binance advises users to treat a missing or incorrect code as suspicious and inspect the actual sender domain.","sourceIds":["binance-antiphishing","binance-phishing-examples"],"risk":"low"},{"id":"c4","text":"Binance also provides an official-verification tool for checking claimed official contact details, but no single signal replaces full message and URL verification.","sourceIds":["binance-verify","binance-account-safety"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"coinbase-advanced-vs-kraken-pro-order-controls","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-12T23:47:00.000Z","updatedAt":"2026-09-13T07:47:00+08:00","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Advanced vs Kraken Pro Order Controls: A Decision Guide","zh-Hans":"Coinbase Advanced 与 Kraken Pro 订单控制对比：决策指南"},"summary":{"en":"Coinbase Advanced and Kraken Pro both expose professional order controls, but the correct choice depends on the exact market, region, account and failure behavior rather than the longest feature list.","zh-Hans":"Coinbase Advanced 与 Kraken Pro 都提供专业订单控制，但选择不能只看功能列表长度，而要看具体市场、地区、账户与失败行为。Coinbase 公布了市价、限价、止损限价、组合单及时效选项；Kraken 公布了市价、限价、止损、止盈、追踪与组合单流程。真正下单前仍应在登录后的订单票据中核对触发基准、部分成交、撤单逻辑、费用与产品资格。"},"claims":[{"id":"c1","text":"Coinbase describes Coinbase Advanced as the order-book interface for users who want direct control over pricing and timing.","sourceIds":["coinbase-advanced"],"risk":"medium"},{"id":"c2","text":"Coinbase's current order documentation includes market, limit, stop-limit, bracket and time-in-force behavior, subject to product and account availability.","sourceIds":["coinbase-order-types"],"risk":"medium"},{"id":"c3","text":"Kraken's order documentation separates basic order types from conditional, trailing and bracket controls.","sourceIds":["kraken-order-types"],"risk":"low"},{"id":"c4","text":"Kraken says partial fills of a primary bracket order create corresponding take-profit and stop-loss quantities, with one closing side canceling the other.","sourceIds":["kraken-bracket"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-okx-self-trade-prevention-disclosure-audit","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-12T23:47:00.000Z","updatedAt":"2026-09-13T07:47:00+08:00","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Self-Trade Prevention on Coinbase and OKX: A Disclosure and API Audit","zh-Hans":"Coinbase 与 OKX 自成交保护：披露与 API 审计"},"summary":{"en":"Coinbase Exchange and OKX both document self-trade prevention, but their public control models are not identical.","zh-Hans":"Coinbase Exchange 与 OKX 都披露了自成交保护，但公开控制模型并不相同。Coinbase 为 Exchange 订单说明了四种 STP 行为，默认是减量并撤单；OKX 则说明其按主账户维度强制执行 STP，默认撤销 maker，并为 API 提供另外两种模式。多策略交易系统上线前，必须核对账户范围、默认模式、支持的订单类型、部分成交后果、事件消息与历史订单证据。"},"claims":[{"id":"c1","text":"Coinbase Exchange says orders from the same user cannot fill one another and the taker order's STP instruction takes precedence.","sourceIds":["coinbase-matching"],"risk":"medium"},{"id":"c2","text":"Coinbase documents decrement-and-cancel, cancel-oldest, cancel-newest and cancel-both behaviors for the Exchange matching engine.","sourceIds":["coinbase-matching","coinbase-create-order"],"risk":"medium"},{"id":"c3","text":"OKX says mandatory STP applies at master-account scope, including the master and its affiliated subaccounts across order-book trading products.","sourceIds":["okx-stp","okx-api-stp"],"risk":"low"},{"id":"c4","text":"OKX documents cancel-maker as the default, with cancel-taker and cancel-both available through the API for supported orders.","sourceIds":["okx-api-stp"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-coinbase-passkey-and-backup-method","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-12T23:47:00.000Z","updatedAt":"2026-09-13T07:47:00+08:00","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up a Coinbase Passkey and an Independent Backup Method","zh-Hans":"如何设置 Coinbase 通行密钥与独立备用验证方式"},"summary":{"en":"Start only from Coinbase's official domain or app, then confirm that the relevant Coinbase service is available for your location and account.","zh-Hans":"只从 Coinbase 官方域名或 App 开始，并先确认相应服务对所在地区和账户开放。进入安全设置后，通过设备原生提示添加通行密钥，再保留独立备用路径，例如单独保管的硬件安全钥匙、由不同设备或保管体系持有的第二个通行密钥，或 Coinbase 当前支持的其他恢复方式。删除旧方式前先测试备用路径，绝不要在聊天中提供密码、验证码、生物识别信息、恢复短语或身份证件。"},"claims":[{"id":"c1","text":"Coinbase lists passkeys and physical security keys among stronger two-step verification options and recommends keeping multiple methods.","sourceIds":["coinbase-2step"],"risk":"medium"},{"id":"c2","text":"Coinbase explains that passkeys may be stored on a device, in a platform keychain or through another supported credential provider.","sourceIds":["coinbase-2step"],"risk":"medium"},{"id":"c3","text":"Coinbase's troubleshooting flow treats access recovery as account-specific and may require identity or device checks inside the official workflow.","sourceIds":["coinbase-troubleshoot","coinbase-phone"],"risk":"low"},{"id":"c4","text":"Coinbase availability and product access vary by country, legal entity and account state, so a public help page is not proof of eligibility.","sourceIds":["coinbase-countries"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"stablecoin-usage-crypto-trading-payments-measurement","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-12T23:47:00.000Z","updatedAt":"2026-09-13T07:47:00+08:00","readTime":"20 min","author":"NexuAlpha Research Desk","title":{"en":"What Stablecoins Are Used For: Trading, Payments and the Measurement Problem","zh-Hans":"稳定币到底用来做什么：交易、支付与统计口径问题"},"summary":{"en":"Stablecoins are used for several different jobs: crypto trading and collateral, movement between venues and wallets, dollar-denominated savings or treasury operations, cross-border transfer, payments, and settlement for tokenized assets.","zh-Hans":"稳定币承担多种不同任务：加密交易与抵押品、交易所和钱包之间调拨、美元计价储值或资金管理、跨境转移、支付，以及代币化资产结算。原始链上金额不能直接说明终端商业支付规模，因为一次经济行为可能产生多笔转账，机器人、交易所内部调仓与智能合约路由也可能占据大量记录。因此，任何采用率结论都应注明数据日期、分类方法，并区分转账额、活跃用户、商户支付与赎回。"},"claims":[{"id":"c1","text":"Official policy research treats stablecoin activity as a mixture of crypto-market, transfer, payment and store-of-value uses rather than one uniform category.","sourceIds":["bis-annual-2026","imf-stablecoins"],"risk":"medium"},{"id":"c2","text":"IMF analysis describes stablecoins as potentially useful for payments and cross-border transfer while emphasizing issuer, reserve, run and regulatory risks.","sourceIds":["imf-stablecoins"],"risk":"medium"},{"id":"c3","text":"The FSB recommendations focus on governance, redemption, reserve management, data and cross-border oversight for global stablecoin arrangements.","sourceIds":["fsb-gsca"],"risk":"low"},{"id":"c4","text":"BIS analysis warns that on-chain transfer totals and rapid growth do not by themselves prove broad, frictionless retail payment adoption.","sourceIds":["bis-annual-2026","bis-framing"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"stablecoins-vs-tokenized-deposits-money-claim-redemption","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-12T23:47:00.000Z","updatedAt":"2026-09-13T07:47:00+08:00","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Stablecoins vs Tokenized Deposits: Money Claim, Redemption and Settlement","zh-Hans":"稳定币与代币化存款：货币债权、赎回与结算差异"},"summary":{"en":"A stablecoin and a tokenized bank deposit can both move on programmable infrastructure, but they are not the same claim.","zh-Hans":"稳定币与代币化银行存款都可以在可编程基础设施上转移，但二者不是同一种债权。代币化存款通常是银行资产负债表中存款负债的数字表示；稳定币则通常取决于发行人的储备、赎回与法律结构。把任何一种代币视为现金等价物之前，都应比较债务人、按面值转换权、储备或资产负债表支持、结算资产、转移规则、破产处理与运行时段。"},"claims":[{"id":"c1","text":"BIS analysis distinguishes tokenized commercial-bank deposits from stablecoins by issuer liability, convertibility and monetary-system integration.","sourceIds":["bis-bull73","bis-annual-2026"],"risk":"medium"},{"id":"c2","text":"The BIS argues that singleness of money depends on payment instruments exchanging at par rather than fragmenting into issuer-specific prices.","sourceIds":["bis-bull73","bis-framing"],"risk":"medium"},{"id":"c3","text":"Stablecoin usefulness depends on an issuer's reserve, redemption, governance and legal arrangements, not the token label alone.","sourceIds":["bis-annual-2026","bis-framing"],"risk":"low"},{"id":"c4","text":"Central-bank surveys treat tokenized deposits, wholesale CBDC and fast-payment infrastructure as separate design paths that may coexist.","sourceIds":["bis-survey"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-deposit-confirmation-disclosure-audit","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-12T20:36:39.604Z","updatedAt":"2026-09-12T20:36:39.604Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange Deposit Confirmations: A Binance, Kraken and Coinbase Disclosure Audit","zh-Hans":"加密交易所充值确认数：Binance、Kraken 与 Coinbase 披露审计"},"summary":{"en":"Binance, Kraken and Coinbase all describe network confirmation as only one layer of deposit completion. A transaction can be broadcast, confirmed on-chain, credited for trading and available for withdrawal at different times.","zh-Hans":"Binance、Kraken 与 Coinbase 都把网络确认视为充值完成过程中的一个层级。交易广播、链上确认、入账可交易与可提现可能发生在不同时间。可靠比较不应只抄一个静态确认数，而要核对平台是否清楚披露资产、网络、所需状态、交易哈希、账户状态、异常路径与当前地区支持。"},"claims":[{"id":"c1","text":"Binance says required confirmations vary by cryptocurrency and warns that unsupported assets, networks, addresses or memos can prevent crediting.","sourceIds":["binance-pending","binance-deposit"],"risk":"medium"},{"id":"c2","text":"Kraken distinguishes confirming, credited and successful deposit states, including a state where trading is available before withdrawal.","sourceIds":["kraken-status"],"risk":"medium"},{"id":"c3","text":"Kraken publishes asset-specific confirmation and approximate processing-time information but says network execution time can vary.","sourceIds":["kraken-times"],"risk":"low"},{"id":"c4","text":"Coinbase tells users to use the transaction hash and correct network explorer, then distinguish on-chain confirmation from account crediting.","sourceIds":["coinbase-pending","coinbase-hash"],"risk":"low"}],"relatedVenues":["binance","kraken","coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"ecb-pontes-tokenized-securities-settlement-explained","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-12T20:36:39.604Z","updatedAt":"2026-09-12T20:36:39.604Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"ECB Pontes and Tokenized Securities Settlement: What the Cash Leg Changes","zh-Hans":"ECB Pontes 与代币化证券结算：现金端到底改变了什么"},"summary":{"en":"Pontes is the Eurosystem's DLT settlement solution for linking market DLT platforms with TARGET Services so eligible wholesale transactions can settle their cash leg in central bank money.","zh-Hans":"Pontes 是欧元体系连接市场 DLT 平台与 TARGET Services 的结算方案，使符合条件的批发交易能够以中央银行货币完成现金端结算。它不会自动把所有代币变成安全证券，也不等于向零售用户开放。分析时仍要识别法律资产、运营方、资格、证券记录、现金代币或 T2 路径、最终性时点与失败处理。"},"claims":[{"id":"c1","text":"The ECB describes Pontes as a DLT solution linking market DLT platforms and TARGET Services for settlement in central bank money.","sourceIds":["ecb-pontes"],"risk":"medium"},{"id":"c2","text":"The published design offers a dual settlement model using cash tokens on the Eurosystem DLT platform or settlement in T2.","sourceIds":["ecb-pontes"],"risk":"medium"},{"id":"c3","text":"The ECB says finality for the T2 cash leg occurs when the corresponding transaction is completed in T2.","sourceIds":["ecb-pontes"],"risk":"low"},{"id":"c4","text":"Project Agora tested atomic settlement with tokenized central-bank reserves and tokenized commercial-bank deposits in a prototype.","sourceIds":["ecb-agora","bis-agora"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"fatf-2026-crypto-travel-rule-implementation-user-impact","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-12T20:36:39.604Z","updatedAt":"2026-09-12T20:36:39.604Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"FATF 2026 Travel Rule Update: What Uneven Implementation Means for Crypto Transfers","zh-Hans":"FATF 2026 旅行规则更新：实施不均对加密转账意味着什么"},"summary":{"en":"FATF reported in July 2026 that 83% of surveyed jurisdictions had passed Travel Rule legislation, up from 73% in 2025, while implementation and supervision remained uneven. For users, that does not create one global transfer form.","zh-Hans":"FATF 在 2026 年 7 月报告称，83% 的受访司法管辖区已通过旅行规则立法，高于 2025 年的 73%，但落地执行与监管仍不均衡。对用户而言，这不代表全球出现统一转账表单，而是解释了为何交易所会根据实体、司法管辖区、资产、路径与风险审查，要求不同的汇款人、收款人、钱包所有权或对手方信息。"},"claims":[{"id":"c1","text":"FATF reported that 83% of surveyed jurisdictions had passed Travel Rule legislation in 2026, compared with 73% in 2025.","sourceIds":["fatf-update"],"risk":"medium"},{"id":"c2","text":"FATF said legislation has progressed faster than effective implementation, supervision and enforcement in some jurisdictions.","sourceIds":["fatf-update"],"risk":"medium"},{"id":"c3","text":"The update identifies offshore VASPs, stablecoins, unhosted wallets and DeFi arrangements among continuing risk areas.","sourceIds":["fatf-update"],"risk":"low"},{"id":"c4","text":"FATF frames the Travel Rule as part of Recommendation 15's risk-based controls for virtual assets and service providers.","sourceIds":["fatf-update","fatf-guidance"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-set-up-multiple-passkeys-on-kraken","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-12T20:36:39.604Z","updatedAt":"2026-09-12T20:36:39.604Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"How to Set Up Multiple Passkeys on Kraken Without Creating a Single-Device Trap","zh-Hans":"如何在 Kraken 设置多个通行密钥，并避免单设备锁死"},"summary":{"en":"Use only Kraken's official sign-in domain, confirm that Kraken services are available for your residence, and enter Security settings from the authenticated account.","zh-Hans":"只使用 Kraken 官方登录域名，先确认居住地能够使用相应服务，再从已登录账户进入 Security 设置。Kraken 说明首个登录 2FA 必须是可漫游方式；之后可添加受支持的跨设备或硬件密钥通行密钥，并在当前规则允许时添加一个设备绑定通行密钥。至少保留两条独立恢复路径，绝不要在聊天中提供验证码、秘密值或身份证件。"},"claims":[{"id":"c1","text":"Kraken identifies https://id.kraken.com/sign-in as its official sign-in URL in its phishing guidance.","sourceIds":["kraken-phishing"],"risk":"medium"},{"id":"c2","text":"Kraken says the first sign-in 2FA method must be a roaming method before a device-bound passkey can be added.","sourceIds":["kraken-multiple"],"risk":"medium"},{"id":"c3","text":"Kraken's current multiple-2FA guidance says an account can enable up to five passkeys and one authenticator app after the initial method.","sourceIds":["kraken-multiple"],"risk":"low"},{"id":"c4","text":"Kraken's legal page says terms and service availability differ by residence and that geographic restrictions may apply.","sourceIds":["kraken-legal"],"risk":"low"}],"relatedVenues":["kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-flockusdt-perpetual-listing-user-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-12T20:36:39.604Z","updatedAt":"2026-09-12T20:36:39.604Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"OKX FLOCKUSDT Perpetual Listing: Contract Checks Before Trading","zh-Hans":"OKX 上线 FLOCKUSDT 永续合约：交易前的合约核对清单"},"summary":{"en":"OKX announced that FLOCK/USDT perpetual futures opened on September 12, 2026 at 10:00 UTC across web, app and API surfaces. That listing notice confirms availability in principle, not suitability for a particular account.","zh-Hans":"OKX 公告称 FLOCK/USDT 永续合约已于 2026 年 9 月 12 日 10:00 UTC 在网页、App 与 API 端开放。公告只能证明产品原则上上线，不能证明它适合某个具体账户。交易前仍需核对地区资格、实时合约参数、标记与指数价格、资金费率、杠杆、保证金模式、订单控制与强平风险。"},"claims":[{"id":"c1","text":"OKX's September 12 notice states that FLOCK/USDT perpetual futures opened at 10:00 UTC that day.","sourceIds":["okx-flock"],"risk":"medium"},{"id":"c2","text":"The notice says the launch covers the web and app interfaces as well as the API.","sourceIds":["okx-flock"],"risk":"medium"},{"id":"c3","text":"OKX labels the update as potentially inapplicable to some customers and directs users to check regional availability in the app.","sourceIds":["okx-flock"],"risk":"low"},{"id":"c4","text":"OKX's product documentation separates perpetual contract rules, funding, margin calculations and risk management from the short listing announcement.","sourceIds":["okx-futures"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-vs-bitget-fees-products-risk-controls","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-12T17:36:42.721Z","updatedAt":"2026-09-12T17:36:42.721Z","readTime":"19 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit vs Bitget: Fees, Product Scope, Risk Controls and User Fit","zh-Hans":"Bybit 与 Bitget 对比：费用、产品范围、风险控制与用户适配","ja":"BybitとBitgetを比較：手数料、商品範囲、リスク管理と利用者への適合性","ko":"Bybit와 Bitget 비교: 수수료, 상품 범위, 위험 관리와 사용자 적합성","tr":"Bybit ve Bitget karşılaştırması: Ücretler, ürün kapsamı, risk kontrolleri ve kullanıcı uyumu","es":"Bybit frente a Bitget: comisiones, productos, controles de riesgo y adecuación","pt-BR":"Bybit vs. Bitget: taxas, produtos, controles de risco e adequação","fr":"Bybit et Bitget : frais, produits, contrôles des risques et adéquation","de":"Bybit und Bitget im Vergleich: Gebühren, Produkte, Risikokontrollen und Eignung","ar":"مقارنة Bybit وBitget: الرسوم والمنتجات وضوابط المخاطر والملاءمة","ru":"Bybit и Bitget: комиссии, продукты, контроль рисков и соответствие пользователю","id":"Perbandingan Bybit dan Bitget: biaya, produk, kontrol risiko, dan kecocokan","vi":"So sánh Bybit và Bitget: phí, sản phẩm, kiểm soát rủi ro và mức phù hợp","it":"Bybit e Bitget a confronto: costi, prodotti, controlli del rischio e adeguatezza"},"summary":{"en":"Bybit and Bitget both publish spot and derivatives services, but there is no universal winner.","zh-Hans":"Bybit 与 Bitget 都提供现货和衍生品服务，但不存在适用于所有人的统一赢家。可靠选择应基于具体产品、账户实时费率、市场可用性、资金费率机制、提现路径、地区资格与入金前可核验的安全控制，而不是依赖宣传口号。","ja":"BybitとBitgetの公開条件を、手数料、商品、リスク管理、地域・口座条件の観点から比較します。最終条件は各公式アカウントで確認してください。","ko":"Bybit와 Bitget의 공개 조건을 수수료, 상품, 위험 관리와 지역·계정 조건별로 비교합니다. 최종 조건은 공식 계정에서 확인하세요.","tr":"Bybit ve Bitget için yayımlanan koşulları ücret, ürün, risk kontrolü ve bölgesel hesap şartlarıyla karşılaştırıyoruz. Nihai koşulları resmî hesapta doğrulayın.","es":"Comparamos las condiciones públicas de Bybit y Bitget por comisiones, productos, controles de riesgo y requisitos regionales. Verifica las condiciones finales en la cuenta oficial.","pt-BR":"Comparamos as condições públicas da Bybit e da Bitget por taxas, produtos, controles de risco e requisitos regionais. Confirme as condições finais na conta oficial.","fr":"Comparaison des conditions publiques de Bybit et Bitget selon les frais, produits, contrôles des risques et contraintes régionales. Vérifiez les conditions finales sur le compte officiel.","de":"Wir vergleichen die veröffentlichten Bedingungen von Bybit und Bitget nach Gebühren, Produkten, Risikokontrollen und regionalen Anforderungen. Die finalen Bedingungen gelten im offiziellen Konto.","ar":"نقارن الشروط المنشورة لدى Bybit وBitget من حيث الرسوم والمنتجات وضوابط المخاطر والقيود الإقليمية. تحقق من الشروط النهائية في الحساب الرسمي.","ru":"Сравниваем опубликованные условия Bybit и Bitget по комиссиям, продуктам, рискам и региональным требованиям. Финальные условия проверяйте в официальном аккаунте.","id":"Bandingkan ketentuan publik Bybit dan Bitget berdasarkan biaya, produk, kontrol risiko, dan persyaratan wilayah. Verifikasi syarat akhir di akun resmi.","vi":"So sánh điều kiện công khai của Bybit và Bitget theo phí, sản phẩm, kiểm soát rủi ro và yêu cầu khu vực. Xác minh điều kiện cuối cùng tại tài khoản chính thức.","it":"Confrontiamo le condizioni pubbliche di Bybit e Bitget per costi, prodotti, rischi e requisiti regionali. Verifica le condizioni finali nell’account ufficiale."},"claims":[{"id":"c1","text":"Bybit's published fee structure says actual rates may vary by region and directs users to the authenticated My Fee Rate page after identity verification.","sourceIds":["bybit-fees"],"risk":"medium"},{"id":"c2","text":"Bitget's fee FAQ states standard reference rates but also directs users to the live fee schedule because VIP status, holdings, and promotions can change the effective rate.","sourceIds":["bitget-fees"],"risk":"medium"},{"id":"c3","text":"Both venues distinguish maker and taker execution, while derivatives add funding, margin, and liquidation considerations beyond the headline trading fee.","sourceIds":["bybit-costs","bitget-agreement"],"risk":"low"},{"id":"c4","text":"CoinGecko market pages are independent snapshots useful for market-presence context, not proof of account eligibility or executable liquidity for a particular order.","sourceIds":["cg-bybit","cg-bitget"],"risk":"low"}],"relatedVenues":["bybit","bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-api-key-security-controls-audit","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-12T17:36:42.721Z","updatedAt":"2026-09-12T17:36:42.721Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange API-Key Security Controls: A Disclosure Audit","zh-Hans":"加密交易所 API 密钥安全控制：披露审计","ja":"暗号資産取引所のAPIキー安全管理：公開情報の監査","ko":"암호화폐 거래소 API 키 보안 관리: 공개 정보 감사","tr":"Kripto borsası API anahtarı güvenlik kontrolleri: Açıklama denetimi","es":"Seguridad de las claves API de exchanges: auditoría de divulgación","pt-BR":"Controles de segurança de chaves API em exchanges: auditoria de divulgação","fr":"Sécurité des clés API des exchanges : audit des contrôles publiés","de":"Sicherheitskontrollen für Exchange-API-Schlüssel: Offenlegungsprüfung","ar":"ضوابط أمان مفاتيح API في منصات التداول: تدقيق الإفصاحات","ru":"Безопасность API-ключей криптобирж: аудит раскрытых мер защиты","id":"Audit kontrol keamanan kunci API bursa kripto","vi":"Kiểm toán kiểm soát an toàn khóa API sàn crypto","it":"Controlli di sicurezza delle chiavi API degli exchange: audit"},"summary":{"en":"A safe exchange API key should begin read-only, use the narrowest permissions, bind trusted IP addresses when supported, avoid withdrawal authority, stay outside source code and chat, and be rotated or deleted when its job ends.","zh-Hans":"安全的交易所 API 密钥应从只读权限开始，采用最小授权，在支持时绑定可信 IP，避免开放提现权限，不把秘密写进源代码或聊天记录，并在任务结束后轮换或删除。NexuAlpha 的披露审计比较的是公开文档中的控制措施，不代表对任何私人账户、集成程序或不可见实现做过安全认证。","ja":"取引所APIキーは読み取り専用から始め、権限を最小化し、出金権限を避け、必要がなくなれば削除・更新します。","ko":"거래소 API 키는 읽기 전용으로 시작하고 권한을 최소화하며 출금 권한을 피하고 사용이 끝나면 폐기하거나 교체해야 합니다.","tr":"Borsa API anahtarlarını salt okunur başlatın, izinleri sınırlayın, çekim yetkisini kapatın ve iş bitince anahtarı döndürün veya silin.","es":"Empieza con permisos de solo lectura, limita el alcance, evita retiros y rota o elimina las claves cuando ya no sean necesarias.","pt-BR":"Comece com acesso somente leitura, limite as permissões, evite saques e remova ou altere as chaves quando não forem mais necessárias.","fr":"Commencez en lecture seule, limitez les permissions, évitez les retraits et supprimez ou renouvelez les clés à la fin de leur usage.","de":"Beginnen Sie mit Leserechten, begrenzen Sie Berechtigungen, vermeiden Sie Auszahlungen und löschen oder rotieren Sie Schlüssel nach Gebrauch.","ar":"ابدأ بصلاحيات القراءة فقط، قلّل الأذونات، تجنب صلاحية السحب واحذف المفاتيح أو بدّلها بعد انتهاء استخدامها.","ru":"Начинайте с режима только чтение, ограничивайте разрешения, отключайте вывод и удаляйте или меняйте ключи после использования.","id":"Mulai dengan akses baca saja, batasi izin, hindari izin penarikan, lalu hapus atau rotasi kunci setelah selesai digunakan.","vi":"Bắt đầu bằng quyền chỉ đọc, giới hạn quyền, tránh quyền rút tiền và xóa hoặc thay khóa khi không còn cần thiết.","it":"Inizia con permessi di sola lettura, limita le autorizzazioni, evita i prelievi e ruota o elimina le chiavi dopo l’uso."},"claims":[{"id":"c1","text":"Binance documentation recommends IP restrictions and limits unrestricted HMAC keys to reading unless security controls are changed.","sourceIds":["binance-api"],"risk":"medium"},{"id":"c2","text":"OKX documentation describes Read, Trade, and Withdraw permissions, IP allowlists, and deletion of certain inactive unbound keys.","sourceIds":["okx-api"],"risk":"medium"},{"id":"c3","text":"Coinbase developer documentation separates API-key authentication from permissions and secret handling for developer applications.","sourceIds":["coinbase-api"],"risk":"low"},{"id":"c4","text":"OWASP recommends centralized secrets management, restricted access, rotation, auditing, and avoiding secrets in source code.","sourceIds":["owasp-secrets"],"risk":"low"}],"relatedVenues":["binance","okx","coinbase","kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"issuer-sponsored-vs-third-party-tokenized-securities","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-12T17:36:42.721Z","updatedAt":"2026-09-12T17:36:42.721Z","readTime":"18 min","author":"NexuAlpha Research Desk","title":{"en":"Issuer-Sponsored vs Third-Party Tokenized Securities: Rights, Records and Redemption","zh-Hans":"发行人主导与第三方代币化证券：权利、记录与赎回差异","ja":"発行体主導型と第三者型のトークン化証券：権利、記録、償還","ko":"발행자 주도형과 제3자형 토큰화 증권: 권리, 기록과 상환","tr":"İhraççı destekli ve üçüncü taraf tokenleştirilmiş menkul kıymetler: Haklar, kayıtlar ve itfa","es":"Valores tokenizados del emisor frente a terceros: derechos, registros y reembolso","pt-BR":"Títulos tokenizados do emissor e de terceiros: direitos, registros e resgate","fr":"Titres tokenisés de l’émetteur ou de tiers : droits, registres et rachat","de":"Emittenten- und Drittanbieter-Tokenpapiere: Rechte, Register und Rückzahlung","ar":"الأوراق المالية المرمّزة من المُصدر أو من طرف ثالث: الحقوق والسجلات والاسترداد","ru":"Токенизированные ценные бумаги эмитента и третьих лиц: права, записи и погашение","id":"Sekuritas bertokenisasi dari penerbit dan pihak ketiga: hak, catatan, dan penebusan","vi":"Chứng khoán token hóa do tổ chức phát hành và bên thứ ba: quyền, hồ sơ và hoàn trả","it":"Titoli tokenizzati dell’emittente e di terzi: diritti, registri e rimborso"},"summary":{"en":"The token format alone does not identify what an investor owns.","zh-Hans":"仅凭代币形式无法判断投资者实际拥有的权利。SEC 工作人员区分发行人主导的代币化证券与第三方代币化模式；第三方模式可能代表托管权益、挂钩工具或其他请求权，并不当然等同于发行人证券本身。投资者应追溯权威持有人记录、法律请求权、转让限制、中介机构、赎回路径与破产隔离安排。","ja":"同じトークン形式でも、保有者の権利、発行体記録、償還経路は異なります。公開資料に基づいて確認項目を整理します。","ko":"같은 토큰 형식이라도 보유자의 권리, 발행자 기록과 상환 경로는 다를 수 있습니다. 공개 자료를 기준으로 확인 항목을 정리합니다.","tr":"Aynı token biçimi farklı sahiplik hakları, ihraççı kayıtları ve itfa yolları taşıyabilir. Kontrol noktalarını kamuya açık kaynaklarla ayırıyoruz.","es":"El mismo formato de token puede representar derechos, registros del emisor y vías de reembolso diferentes. Separamos los puntos de verificación con fuentes públicas.","pt-BR":"O mesmo formato de token pode representar direitos, registros do emissor e caminhos de resgate diferentes. Organizamos os pontos de verificação com fontes públicas.","fr":"Un même format de token peut donner des droits, registres et voies de rachat différents. Nous séparons les points à vérifier à partir de sources publiques.","de":"Dasselbe Tokenformat kann unterschiedliche Rechte, Emittentenregister und Rückzahlungswege bedeuten. Wir ordnen die Prüfpunkte anhand öffentlicher Quellen.","ar":"قد يمثل الشكل نفسه حقوقاً وسجلات مُصدر ومسارات استرداد مختلفة. نحدد نقاط التحقق من المصادر العامة.","ru":"Одинаковый формат токена может означать разные права, записи эмитента и пути погашения. Разбираем точки проверки по открытым источникам.","id":"Format token yang sama dapat memiliki hak, catatan penerbit, dan jalur penebusan berbeda. Kami memisahkan titik pemeriksaan dari sumber publik.","vi":"Cùng một dạng token có thể có quyền sở hữu, hồ sơ phát hành và đường hoàn trả khác nhau. Tách các điểm cần kiểm tra từ nguồn công khai.","it":"Lo stesso formato token può rappresentare diritti, registri dell’emittente e percorsi di rimborso diversi. Separiamo i punti da verificare con fonti pubbliche."},"claims":[{"id":"c1","text":"SEC staff describes tokenization as creating a digital representation of an asset using distributed-ledger technology.","sourceIds":["sec-tokenized"],"risk":"medium"},{"id":"c2","text":"The staff statement separates securities tokenized by or for an issuer from models created by unaffiliated third parties.","sourceIds":["sec-tokenized"],"risk":"medium"},{"id":"c3","text":"In issuer-sponsored models, distributed-ledger records may be integrated with the issuer's master securityholder file.","sourceIds":["sec-tokenized"],"risk":"low"},{"id":"c4","text":"A third-party token may instead embody a custodial entitlement, linked instrument, or other arrangement whose rights must be read from its own legal documents.","sourceIds":["sec-tokenized"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-icxusdt-perpetual-delisting-settlement-checklist","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-12T17:36:42.721Z","updatedAt":"2026-09-12T17:36:42.721Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"OKX ICXUSDT Perpetual Delisting: Settlement Timeline and User Checklist","zh-Hans":"OKX 下架 ICXUSDT 永续合约：结算时间线与用户检查清单","ja":"OKX ICXUSDT無期限契約の上場廃止：決済日程と利用者チェックリスト","ko":"OKX ICXUSDT 무기한 계약 상장폐지: 결제 일정과 사용자 체크리스트","tr":"OKX ICXUSDT sürekli sözleşme delistingi: Takvim ve kullanıcı kontrol listesi","es":"Retirada del perpetuo ICXUSDT de OKX: calendario de liquidación y checklist","pt-BR":"Delisting do perpétuo ICXUSDT na OKX: cronograma e checklist","fr":"Retrait du perpétuel ICXUSDT d’OKX : calendrier et checklist","de":"OKX nimmt ICXUSDT-Perpetual aus dem Handel: Zeitplan und Checkliste","ar":"إزالة عقد ICXUSDT الدائم من OKX: الجدول وقائمة التحقق","ru":"Делистинг бессрочного ICXUSDT на OKX: сроки расчётов и чек-лист","id":"Delisting perpetual ICXUSDT di OKX: jadwal penyelesaian dan checklist","vi":"OKX hủy niêm yết hợp đồng vĩnh cửu ICXUSDT: lịch và checklist","it":"Delisting del perpetuo ICXUSDT su OKX: calendario e checklist"},"summary":{"en":"OKX says ICXUSDT perpetual trading will stop on September 17, 2026 at 08:00 UTC.","zh-Hans":"OKX 公告称 ICXUSDT 永续合约将在 2026 年 9 月 17 日 08:00 UTC 停止交易。届时未成交订单会被取消，持仓按照下架前一小时 OKX 指数的算术平均值结算，交易机器人会在下架前一小时逐步关闭。用户应提前核对杠杆、机器人状态、交易记录与资金划转安排。","ja":"OKXの公開告知に基づき、取引停止、注文取消、ポジション決済、利用者が確認すべき期限を整理します。","ko":"OKX 공지를 기준으로 거래 중단, 주문 취소, 포지션 결제와 사용자가 확인해야 할 기한을 정리합니다.","tr":"OKX duyurusuna göre işlem durdurma, emir iptali, pozisyon uzlaşması ve kullanıcıların kontrol etmesi gereken tarihleri özetliyoruz.","es":"A partir del aviso de OKX, resumimos la suspensión, cancelación de órdenes, liquidación de posiciones y fechas que deben revisar los usuarios.","pt-BR":"Com base no aviso da OKX, resumimos a suspensão, o cancelamento de ordens, a liquidação de posições e os prazos para os usuários.","fr":"À partir de l’avis d’OKX, nous résumons l’arrêt des échanges, l’annulation des ordres, le règlement des positions et les échéances.","de":"Auf Grundlage der OKX-Mitteilung fassen wir Handelsstopp, Auftragsstornierung, Positionsabrechnung und wichtige Fristen zusammen.","ar":"نلخص من إعلان OKX إيقاف التداول وإلغاء الأوامر وتسوية المراكز والمواعيد التي يجب على المستخدم مراجعتها.","ru":"По объявлению OKX разбираем остановку торгов, отмену ордеров, расчёт позиций и важные сроки для пользователей.","id":"Berdasarkan pengumuman OKX, rangkum penghentian perdagangan, pembatalan order, penyelesaian posisi, dan tenggat yang perlu diperiksa.","vi":"Dựa trên thông báo OKX, tóm tắt việc dừng giao dịch, hủy lệnh, tất toán vị thế và thời hạn người dùng cần kiểm tra.","it":"Sulla base dell’avviso OKX, riassumiamo stop al trading, cancellazione ordini, regolazione delle posizioni e scadenze."},"claims":[{"id":"c1","text":"OKX's September 10 notice names September 17, 2026 at 08:00 UTC as the ICXUSDT perpetual delisting time.","sourceIds":["okx-notice"],"risk":"medium"},{"id":"c2","text":"The notice says open orders will be canceled and remaining positions settled from the arithmetic average of the OKX index during the hour before delisting.","sourceIds":["okx-notice"],"risk":"medium"},{"id":"c3","text":"OKX says bots will gradually close within the final hour and warns that users concerned about fees or slippage may stop them manually.","sourceIds":["okx-notice"],"risk":"low"},{"id":"c4","text":"The notice states a temporary 30-minute transfer restriction after delisting for positions with notional value above 10,000 USDT.","sourceIds":["okx-notice"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"stablecoin-multichain-fragmentation-user-risk","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-12T17:36:42.721Z","updatedAt":"2026-09-12T17:36:42.721Z","readTime":"17 min","author":"NexuAlpha Research Desk","title":{"en":"Stablecoin Multichain Fragmentation: Why the Same Ticker Is Not the Same Transfer","zh-Hans":"稳定币多链碎片化：为什么同一代码不代表同一条转账路径","ja":"ステーブルコインのマルチチェーン分断：同じティッカーでも同じ送金経路とは限らない","ko":"스테이블코인 멀티체인 분절: 같은 티커가 같은 전송 경로를 뜻하지 않는 이유","tr":"Stablecoin çoklu zincir parçalanması: Aynı ticker aynı transfer yolu değildir","es":"Fragmentación multicadena de las stablecoins: el mismo ticker no es la misma ruta","pt-BR":"Fragmentação multichain de stablecoins: o mesmo ticker não é a mesma rota","fr":"Fragmentation multichaîne des stablecoins : un ticker ne définit pas la route","de":"Multichain-Fragmentierung von Stablecoins: Gleiches Ticker, anderer Transferweg","ar":"تجزئة العملات المستقرة متعددة السلاسل: الرمز نفسه لا يعني المسار نفسه","ru":"Мультичейн-фрагментация стейблкоинов: один тикер не означает один путь","id":"Fragmentasi stablecoin multichain: ticker sama bukan berarti jalur transfer sama","vi":"Phân mảnh stablecoin đa chuỗi: cùng ticker không có nghĩa cùng đường chuyển","it":"Frammentazione multichain delle stablecoin: stesso ticker, percorso diverso"},"summary":{"en":"A stablecoin with the same ticker on two networks is not automatically transferable between them.","zh-Hans":"同一稳定币代码出现在两条网络上，并不意味着它们可以直接互转。BIS 指出，不同链上的代币分别存在于彼此不能原生通信的账本中，因此用户需要交易所支持路径、发行人机制或跨链桥。实际风险包括资产与网络不匹配、流动性碎片化、桥接依赖以及误转后的恢复不确定性。","ja":"同じティッカーでもネットワークが違えば互換性はありません。入出金ネットワーク、対応状況、復旧条件を確認します。","ko":"같은 티커라도 네트워크가 다르면 호환되지 않습니다. 입출금 네트워크, 지원 여부와 복구 조건을 확인하세요.","tr":"Aynı ticker farklı ağlarda uyumlu olmayabilir. Yatırma/çekme ağı, destek durumu ve kurtarma koşullarını doğrulayın.","es":"El mismo ticker puede no ser compatible entre redes. Comprueba la red de depósito y retiro, la compatibilidad y las condiciones de recuperación.","pt-BR":"O mesmo ticker pode não ser compatível entre redes. Verifique a rede de depósito e saque, o suporte e as condições de recuperação.","fr":"Un même ticker peut être incompatible entre réseaux. Vérifiez le réseau de dépôt et retrait, le support et les conditions de récupération.","de":"Dasselbe Ticker-Symbol ist zwischen Netzwerken nicht automatisch kompatibel. Prüfen Sie Ein- und Auszahlungsnetz, Support und Wiederherstellungsbedingungen.","ar":"قد لا يكون الرمز نفسه متوافقاً بين الشبكات. تحقق من شبكة الإيداع والسحب والدعم وشروط الاسترداد.","ru":"Один тикер может быть несовместим между сетями. Проверяйте сети ввода и вывода, поддержку и условия восстановления.","id":"Ticker yang sama belum tentu kompatibel antarjaringan. Periksa jaringan deposit dan penarikan, dukungan, serta pemulihan.","vi":"Cùng ticker có thể không tương thích giữa các mạng. Kiểm tra mạng nạp/rút, hỗ trợ và điều kiện khôi phục.","it":"Lo stesso ticker può non essere compatibile tra reti. Verifica rete di deposito e prelievo, supporto e condizioni di recupero."},"claims":[{"id":"c1","text":"The BIS 2026 report describes stablecoins circulating across a growing range of layer-1 and layer-2 networks.","sourceIds":["bis-2026"],"risk":"medium"},{"id":"c2","text":"The report explains that a coin on one chain is not equivalent to a same-named coin on another chain because the ledgers do not natively communicate.","sourceIds":["bis-2026"],"risk":"medium"},{"id":"c3","text":"The BIS warns that unsupported cross-network transfers can fail and risk permanent loss.","sourceIds":["bis-2026"],"risk":"low"},{"id":"c4","text":"FSB recommendations address governance, risk management, data, redemption, and cross-border cooperation for global stablecoin arrangements.","sourceIds":["fsb-gsc"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"tokenized-asset-custody-redemption-risk-checklist","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-10T18:20:00.000Z","updatedAt":"2026-09-10T18:20:00Z","readTime":"28 min","author":"NexuAlpha Research Desk","title":{"en":"Tokenized Asset Custody and Redemption: A Practical Risk Checklist","zh-Hans":"代币化资产托管与赎回：实用风险清单","ja":"トークン化資産の保管と償還：実務リスクチェックリスト","ko":"토큰화 자산 보관과 상환: 실무 위험 체크리스트","tr":"Tokenleştirilmiş varlık saklama ve itfa: Pratik risk kontrol listesi","es":"Custodia y reembolso de activos tokenizados: checklist de riesgos","pt-BR":"Custódia e resgate de ativos tokenizados: checklist de riscos","fr":"Garde et rachat d’actifs tokenisés : checklist des risques","de":"Verwahrung und Rückzahlung tokenisierter Vermögenswerte: Risiko-Checkliste","ar":"حفظ واسترداد الأصول المرمّزة: قائمة مخاطر عملية","ru":"Хранение и погашение токенизированных активов: чек-лист рисков","id":"Kustodi dan penebusan aset bertokenisasi: daftar risiko","vi":"Lưu ký và hoàn trả tài sản token hóa: checklist rủi ro","it":"Custodia e rimborso degli asset tokenizzati: checklist dei rischi"},"summary":{"en":"Before treating a tokenized asset as redeemable or safely held, verify the controlling legal record, issuer or vehicle, custodian and broker chain, asset segregation, transfer restrictions, redemption windows, fees, suspension rights, insolvency remedies and technical dependencies.","zh-Hans":"在把一个代币化资产视为“安全持有”或“可以可靠赎回”之前，先核验十件事：合同链条、发行人或特殊目的实体、法定或官方持有人记录、托管人和经纪链条、底层资产隔离、转让限制、赎回窗口、赎回费用、暂停或限制赎回条款、破产和救济路径，以及预言机、链、桥、钱包白名单和管理员权限这些技术依赖。","ja":"トークン化資産の保管、償還、発行体記録、移転制限、破綻時の救済とチェーンリスクを確認します。","ko":"토큰화 자산의 보관, 상환, 발행자 기록, 이전 제한, 파산 구제와 체인 위험을 확인합니다.","tr":"Tokenleştirilmiş varlıkların saklama, itfa, ihraççı kayıtları, transfer kısıtları ve zincir risklerini kontrol edin.","es":"Revisa custodia, reembolso, registros del emisor, restricciones de transferencia y riesgos de cadena.","pt-BR":"Revise custódia, resgate, registros do emissor, restrições de transferência e riscos de rede.","fr":"Vérifiez la garde, le rachat, les registres de l’émetteur, les restrictions de transfert et le risque de chaîne.","de":"Prüfen Sie Verwahrung, Rückzahlung, Emittentenregister, Transferbeschränkungen und Chain-Risiken.","ar":"تحقق من الحفظ والاسترداد وسجلات المُصدر وقيود النقل ومخاطر الشبكة.","ru":"Проверьте хранение, погашение, записи эмитента, ограничения и риски сети.","id":"Periksa kustodi, penebusan, catatan penerbit, batas transfer, dan risiko jaringan.","vi":"Kiểm tra lưu ký, hoàn trả, hồ sơ phát hành, hạn chế chuyển và rủi ro mạng.","it":"Verifica custodia, rimborso, registri dell’emittente, limiti e rischio di rete."},"claims":[{"id":"c1","text":"SEC staff describe tokenized securities as securities represented by crypto assets where ownership records are maintained in whole or in part through crypto networks, and distinguish issuer-sponsored, custodial-entitlement and synthetic models.","sourceIds":["sec-tokenized-securities-2026"],"risk":"high"},{"id":"c2","text":"The SEC staff statement says the format of a security does not change application of federal securities laws and the statement is not a Commission rule, regulation, guidance or legally binding statement.","sourceIds":["sec-tokenized-securities-2026"],"risk":"high"},{"id":"c3","text":"The DTC no-action package describes tokenized entitlements held only by DTC Participants in Registered Wallets, with securities moved into a Digital Omnibus Account and de-tokenization performed by token burn plus account credit.","sourceIds":["sec-dtc-no-action-2025"],"risk":"high"},{"id":"c4","text":"The DTC no-action package says LedgerScan records Tokenized Entitlements for DTC official books and records, registered ownership remains in Cede & Co., and DTC requires controls for erroneous entries, lost tokens and reversals.","sourceIds":["sec-dtc-no-action-2025"],"risk":"high"},{"id":"c5","text":"BIS/Basel classification of tokenised traditional assets requires digital representation plus the same legal rights and same credit and market risk as the non-tokenised asset; banks must still assess liquidity, collateral eligibility and legal certainty separately.","sourceIds":["bis-sco60-cryptoasset-exposures"],"risk":"medium"},{"id":"c6","text":"BIS Project Agorá treats tokenised reserves and deposits as a technical mechanism for recording and effectuating account debits and credits, with rights arising from underlying account relationships and with reconciliation to other books as necessary.","sourceIds":["bis-project-agora-2026"],"risk":"medium"},{"id":"c7","text":"Franklin's 2026 summary prospectus says FOBXX's transfer agent maintains the official record of share ownership through a blockchain-integrated system under the transfer agent's full control and with permissioned-wallet restrictions and administrative controls.","sourceIds":["franklin-fobxx-summary-prospectus-2026","franklin-fobxx-sec-prospectus-2025"],"risk":"high"},{"id":"c8","text":"Franklin's summary prospectus discloses that the fund seeks to maintain a stable $1 share price but cannot guarantee it, is not FDIC or government insured, and has blockchain, cybersecurity and large-redemption risks.","sourceIds":["franklin-fobxx-summary-prospectus-2026"],"risk":"high"},{"id":"c9","text":"The BlackRock/Securitize agreement appoints Securitize as transfer agent and registrar for BUIDL, identifies BNY Mellon as custodian, defines shares as digital securities authenticated and recorded as blockchain tokens, and ties issuance to subscription documents plus receipt or crediting of funds to the custodian.","sourceIds":["blackrock-buidl-securitize-agreement","blackrock-buidl-form-d"],"risk":"high"},{"id":"c10","text":"The BlackRock/Securitize agreement says transfer and redemption requests must comply with the offering memorandum and legal authorization, and Securitize may delay or refuse transfers that appear improper, unauthorized or not legally in order.","sourceIds":["blackrock-buidl-securitize-agreement"],"risk":"high"},{"id":"c11","text":"Ondo documentation for qualified-access products says users can invest after onboarding by connecting a wallet and depositing stablecoins or wiring USD, redemption timing depends on the product, and OUSG eligibility includes accredited-investor and qualified-purchaser criteria plus jurisdiction restrictions.","sourceIds":["ondo-docs-welcome-2026","ondo-ousg-eligibility-2026","ondo-ousg-kyc-2026"],"risk":"high"},{"id":"c12","text":"A practical custody and redemption checklist should separate legal record, issuer or vehicle, custodian and intermediary chain, asset segregation, transfer restrictions, redemption windows and fees, suspension rights, insolvency remedies, and oracle/chain/bridge dependencies.","sourceIds":["sec-tokenized-securities-2026","sec-dtc-no-action-2025","dtcc-tokenization-initiative-2026","bis-sco60-cryptoasset-exposures","franklin-fobxx-summary-prospectus-2026","blackrock-buidl-securitize-agreement","ondo-docs-welcome-2026"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-account-security-controls-audit","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-10T18:05:00.000Z","updatedAt":"2026-09-10T18:05:00Z","readTime":"22 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange Account Security Controls Audit: Passkeys, Anti-Phishing Codes and Withdrawal Safeguards","zh-Hans":"加密交易所账户安全控制披露审计：通行密钥、反钓鱼码与提现防护","ja":"暗号資産取引所のアカウント安全管理監査：パスキー、フィッシング対策、出金保護","ko":"암호화폐 거래소 계정 보안 감사: 패스키, 피싱 방지 코드와 출금 보호","tr":"Kripto borsası hesap güvenliği denetimi: Passkey, kimlik avı kodları ve çekim koruması","es":"Auditoría de seguridad de cuentas de exchanges: passkeys y protección de retiros","pt-BR":"Auditoria de segurança de contas em exchanges: passkeys e proteção de saques","fr":"Audit de la sécurité des comptes : passkeys et protection des retraits","de":"Audit der Exchange-Kontosicherheit: Passkeys und Auszahlungsschutz","ar":"تدقيق أمان حسابات منصات التداول: مفاتيح المرور وحماية السحب","ru":"Аудит безопасности аккаунтов бирж: ключи доступа и защита вывода","id":"Audit keamanan akun bursa: passkey dan perlindungan penarikan","vi":"Kiểm toán bảo mật tài khoản sàn: passkey và bảo vệ rút tiền","it":"Audit della sicurezza degli account exchange: passkey e protezione dei prelievi"},"summary":{"en":"A crypto exchange account-security audit should separate disclosed controls from proven protection.","zh-Hans":"评估加密交易所的账户安全，不能只问“哪一家最安全”。更可靠的问题应该窄一点：在公开官方文档里，每个平台有没有把用户可以启用的关键控制讲清楚？用户在入金、保存地址、发起提现之前，能不能看到足够明确的防护路径、等待期、恢复边界和限制条件？","ja":"公開情報に基づき、パスキー、2FA、フィッシング対策コード、出金許可リスト、端末管理を確認します。","ko":"공개 자료를 바탕으로 패스키, 2FA, 피싱 방지 코드, 출금 허용 목록과 기기 통제를 확인합니다.","tr":"Kamuya açık açıklamalara göre passkey, 2FA, kimlik avı kodları, çekim izin listeleri ve cihaz kontrollerini inceleyin.","es":"Revisa passkeys, 2FA, códigos antiphishing, listas de retiros y controles de dispositivos.","pt-BR":"Revise passkeys, 2FA, códigos antiphishing, listas de saque e controles de dispositivos.","fr":"Vérifiez les passkeys, la 2FA, les codes anti-hameçonnage, les listes de retrait et les appareils.","de":"Prüfen Sie Passkeys, 2FA, Anti-Phishing-Codes, Auszahlungsfreigaben und Gerätekontrollen.","ar":"راجع مفاتيح المرور والمصادقة الثنائية ورموز مكافحة التصيد وقوائم السحب.","ru":"Проверьте passkey, 2FA, антифишинг, разрешения на вывод и устройства.","id":"Tinjau passkey, 2FA, kode anti-phishing, izin penarikan, dan perangkat.","vi":"Xem xét passkey, 2FA, mã chống lừa đảo, quyền rút và thiết bị.","it":"Controlla passkey, 2FA, codici anti-phishing, permessi di prelievo e dispositivi."},"claims":[{"id":"c1","text":"All six sampled venues publish account-security guidance, but the audit measures public documentation clarity only; it does not test logged-in enforcement, incident response, or real account safety.","sourceIds":["binance-security-tips","okx-account-security","coinbase-two-step","kraken-two-factor","bybit-protect","bitget-security-best-practices"],"risk":"medium"},{"id":"c2","text":"Binance, OKX, Coinbase, Kraken, Bybit and Bitget each disclose passkey or hardware-security-key style authentication in official public material, although scope and product labeling differ by venue.","sourceIds":["binance-passkey-must","okx-passkeys-web","okx-hardware-key","coinbase-two-step","kraken-two-factor","bybit-passkey","bitget-security-best-practices"],"risk":"medium"},{"id":"c3","text":"Binance, OKX, Bybit and Bitget explicitly document anti-phishing-code controls; Coinbase and Kraken emphasize email, official-domain or phishing hygiene in the captured sources, but no anti-phishing-code feature was identified in those official pages.","sourceIds":["binance-security-tips","okx-account-security","coinbase-secure-account","kraken-secure-life","bybit-anti-phishing","bitget-security-best-practices"],"risk":"medium"},{"id":"c4","text":"Binance, Kraken, Bybit and Bitget clearly disclose withdrawal-destination controls such as whitelist/address-book/GSL/new-address mechanisms; Coinbase's captured consumer-security pages did not expose an equivalent general consumer withdrawal-address allowlist feature.","sourceIds":["binance-withdrawal-settings","coinbase-lock-account","kraken-funding-2fa","kraken-add-address","bybit-protect","bybit-account-security","bitget-security-best-practices","bitget-advanced-security"],"risk":"medium"},{"id":"c5","text":"Time-lock disclosures vary: Binance describes 24/48/72-hour whitelist withdrawal-limit windows, Coinbase describes disabled transfers while locked and a 24-hour crypto-send pause after unlocking, Kraken describes a 12-hour new-address hold after some password changes, Bybit describes 24-hour withdrawal restrictions after passkey removal or new-address addition, and Bitget describes 24-hour holds after several security changes.","sourceIds":["binance-withdrawal-settings","coinbase-lock-account","kraken-add-address","bybit-passkey","bybit-account-security","bitget-advanced-security"],"risk":"medium"},{"id":"c6","text":"Device/session controls are not documented at the same granularity: Binance, Bybit and Bitget clearly mention account activity or trusted-device review in the captured pages; Coinbase emphasizes device hygiene and device sign-out when locked; Kraken's captured security guidance is stronger on GSL, Master Key and email/account hardening than on a consumer device-management screen.","sourceIds":["binance-security-tips","coinbase-secure-account","coinbase-lock-account","kraken-secure-life","bybit-account-security","bitget-security-best-practices","bitget-advanced-security"],"risk":"medium"},{"id":"c7","text":"Recovery boundaries are material: several venues warn or imply that losing passkeys, hardware keys or authenticators can trigger account recovery, reset, waiting-period or support workflows rather than instant self-service restoration.","sourceIds":["binance-passkey-must","okx-passkeys-web","coinbase-two-step","coinbase-lock-account","kraken-secure-life","bybit-passkey","bitget-google-authenticator"],"risk":"medium"},{"id":"c8","text":"A public disclosure matrix is useful for due diligence only when paired with a logged-in check before moving funds, because regional availability, account state, KYC status, app version and product eligibility can change the actual controls presented to a user.","sourceIds":["binance-security-tips","okx-account-security","coinbase-two-step","kraken-two-factor","bybit-protect","bitget-security-best-practices"],"risk":"medium"}],"relatedVenues":["binance","okx","coinbase","kraken","bybit","bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"sec-transfer-agent-rules-tokenized-securities","status":"PUBLISHED","category":"regulation","categoryName":{"en":"Regulation","zh-Hans":"监管动态","zh-Hant":"監管動態"},"publishedAt":"2026-09-10T17:52:00.000Z","updatedAt":"2026-09-10T17:52:00Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"SEC Transfer-Agent Proposal: What It Could Change for Tokenized Securities","zh-Hans":"SEC 过户代理规则提案：代币化证券的权属记录与链上运营可能怎样变化","ja":"SECの証券移転代理人提案：トークン化証券への影響","ko":"SEC 증권 이전대리인 제안: 토큰화 증권에 미칠 변화","tr":"SEC transfer acentesi önerisi: Tokenleştirilmiş menkul kıymetleri nasıl etkileyebilir","es":"Propuesta de agentes de transferencia de la SEC: impacto en valores tokenizados","pt-BR":"Proposta da SEC para agentes de transferência: impacto em títulos tokenizados","fr":"Proposition SEC sur les agents de transfert : effets sur les titres tokenisés","de":"SEC-Vorschlag zu Transferagenten: Auswirkungen auf tokenisierte Wertpapiere","ar":"اقتراح SEC لوكلاء نقل الأوراق المالية وتأثيره على الأصول المرمّزة","ru":"Предложение SEC о трансфер-агентах и токенизированные бумаги","id":"Usulan agen transfer SEC dan dampaknya pada sekuritas bertokenisasi","vi":"Đề xuất đại lý chuyển nhượng SEC và tác động đến chứng khoán token hóa","it":"Proposta SEC sugli agenti di trasferimento e titoli tokenizzati"},"summary":{"en":"The SEC's September 2026 transfer-agent proposal does not legalize a particular tokenized-security model or make blockchain records automatically controlling.","zh-Hans":"美国证券交易委员会在 2026 年 9 月提出的过户代理规则现代化方案，与代币化证券直接相关，因为过户代理并不只是“帮人转一张股票”。它们承担或支持证券持有人正式记录、发行与注销、转让处理、限制性图例、资金与证券保护、记录保存以及连接发行人、投资者、经纪商、托管人和结算基础设施等职责。","ja":"SEC提案がブロックチェーン記録、所有権ファイル、サイバーセキュリティ、ウォレット識別子に与える影響を整理します。","ko":"SEC 제안이 블록체인 기록, 공식 소유권 파일, 사이버 보안과 지갑 식별자에 미칠 영향을 정리합니다.","tr":"SEC teklifinin blok zinciri kayıtları, resmî sahiplik dosyaları, siber güvenlik ve cüzdan tanımlayıcılarına etkisini özetliyoruz.","es":"Resume posibles cambios para registros blockchain, archivos de propiedad y controles de seguridad.","pt-BR":"Resume possíveis mudanças em registros blockchain, arquivos de propriedade e controles de segurança.","fr":"Synthèse des effets possibles sur les registres blockchain, la propriété et la cybersécurité.","de":"Mögliche Änderungen bei Blockchain-Registern, Eigentumsdateien und Sicherheitskontrollen.","ar":"نلخص تأثير المقترح المحتمل على السجلات والملكية والأمن.","ru":"Разбираем возможные изменения для реестров, собственности и безопасности.","id":"Ringkas dampak potensial pada catatan, kepemilikan, dan keamanan.","vi":"Tóm tắt tác động có thể tới hồ sơ, quyền sở hữu và an ninh.","it":"Sintesi dei possibili effetti su registri, proprietà e sicurezza."},"claims":[{"id":"c1","text":"On September 1, 2026, the SEC issued a proposal, not a final rule, to modernize the rules and forms for registered transfer agents.","sourceIds":["sec-rule-page-s7-2026-30","sec-press-release-2026-81","sec-proposing-release-34-106246"],"risk":"high"},{"id":"c2","text":"The proposal addresses electronic and blockchain-based recordkeeping and describes tokenized securities, distributed ledgers, smart contracts, cybersecurity and operational risk as part of the modern transfer-agent environment.","sourceIds":["sec-proposing-release-34-106246","sec-transfer-agent-fact-sheet","sec-press-release-2026-81"],"risk":"high"},{"id":"c3","text":"The fact sheet says proposed amendments would modernize recordkeeping and retention rules for electronic systems and third-party recordkeepers and align prompt posting to master securityholder files with the modern settlement cycle.","sourceIds":["sec-transfer-agent-fact-sheet","sec-proposing-release-34-106246"],"risk":"high"},{"id":"c4","text":"The proposal would reframe Rule 17ad-12 as a comprehensive risk-management requirement and would require written policies, a separate bank account for certain funds and a business continuity plan.","sourceIds":["sec-transfer-agent-fact-sheet","sec-proposing-release-34-106246"],"risk":"high"},{"id":"c5","text":"Proposed new Rule 17ad-30 addresses compliance policies and procedures, while proposed Rule 17ad-31 addresses restrictive legends and reasonable-basis requirements.","sourceIds":["sec-transfer-agent-fact-sheet","sec-proposing-release-34-106246"],"risk":"high"},{"id":"c6","text":"Commissioner Peirce asked commenters whether transfer-agent requirements should adapt for onchain securities, including possible use of email or digital wallet addresses as holder identifiers.","sourceIds":["sec-peirce-time-to-transfer"],"risk":"medium"},{"id":"c7","text":"Commissioner Uyeda described the proposal as the start of a public-feedback process for modernizing securities settlement infrastructure, not a final compliance outcome.","sourceIds":["sec-uyeda-transfer-agent-statement","sec-rule-page-s7-2026-30"],"risk":"medium"},{"id":"c8","text":"The rule page says comments are due 60 days after Federal Register publication, so the deadline and final text must be checked against the live docket.","sourceIds":["sec-rule-page-s7-2026-30","sec-proposing-release-34-106246"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-choose-crypto-withdrawal-network","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-10T17:45:00.000Z","updatedAt":"2026-09-10T17:45:00Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"How to Choose a Crypto Withdrawal Network: Fees, Support, Finality and Recovery","zh-Hans":"加密货币提现网络怎么选：费用、支持范围、确认终局与误转恢复","ja":"暗号資産の出金ネットワーク選び：手数料、対応、確定性、復旧","ko":"암호화폐 출금 네트워크 선택법: 수수료, 지원, 확정성과 복구","tr":"Kripto çekim ağı nasıl seçilir: Ücret, destek, kesinlik ve kurtarma","es":"Cómo elegir una red de retiro cripto: tarifas, soporte y recuperación","pt-BR":"Como escolher uma rede de saque cripto: taxas, suporte e recuperação","fr":"Choisir un réseau de retrait crypto : frais, support et récupération","de":"Das richtige Krypto-Auszahlungsnetz wählen: Gebühren, Support und Wiederherstellung","ar":"كيف تختار شبكة سحب العملات الرقمية: الرسوم والدعم والاسترداد","ru":"Как выбрать сеть вывода криптовалюты: комиссии и восстановление","id":"Cara memilih jaringan penarikan kripto: biaya dan pemulihan","vi":"Cách chọn mạng rút crypto: phí, hỗ trợ và khôi phục","it":"Come scegliere la rete di prelievo crypto: costi e recupero"},"summary":{"en":"Choose the withdrawal network only after the receiving destination shows that it supports the same asset on that exact network.","zh-Hans":"选择加密货币提现网络时，要从“接收端”倒推，而不是先看发送端哪个网络最便宜。先在接收交易所或钱包里打开该资产的充值页面，确认它此刻明确支持哪些网络；再回到发送端，选择同一个资产、同一个网络。随后逐项核对完整地址、是否需要 Tag/Memo、实时手续费、最低提现额、预计到账净额和确认要求。金额较大且平台规则允许时，先做一笔能够被正常入账的小额测试，确认接收端已经显示到账，再处理剩余金额。","ja":"入出金ネットワーク、手数料、確定性、タグやメモ、少額テストと復旧限界を確認する判断ガイドです。","ko":"입출금 네트워크, 수수료, 확정성, 태그·메모, 테스트 전송과 복구 한계를 비교하는 가이드입니다.","tr":"Yatırma ve çekme ağlarını, ücretleri, kesinliği, memo/tag gerekliliklerini ve kurtarma sınırlarını karşılaştıran rehberdir.","es":"Compara redes, tarifas, finalidad, etiquetas, transferencias de prueba y límites de recuperación.","pt-BR":"Compare redes, taxas, finalização, tags, transferências de teste e limites de recuperação.","fr":"Comparez réseaux, frais, finalité, tags, tests de transfert et limites de récupération.","de":"Vergleichen Sie Netzwerke, Gebühren, Finalität, Tags, Testtransfers und Wiederherstellungsgrenzen.","ar":"قارن الشبكات والرسوم والوسوم والتحويل التجريبي وحدود الاسترداد.","ru":"Сравните сети, комиссии, теги, тестовый перевод и восстановление.","id":"Bandingkan jaringan, biaya, tag, transfer uji, dan pemulihan.","vi":"So sánh mạng, phí, tag, giao dịch thử và giới hạn khôi phục.","it":"Confronta reti, costi, tag, trasferimenti di prova e recupero."},"claims":[{"id":"c1","text":"A safe withdrawal network is one that the sending and receiving systems both support for the exact asset and transaction direction at the time of transfer.","sourceIds":["binance-withdrawal-guide","okx-network-selection","coinbase-troubleshooting","kraken-address-formats"],"risk":"high"},{"id":"c2","text":"A low displayed withdrawal fee does not make an incompatible network safe, and fees and minimums can change with network and platform conditions.","sourceIds":["binance-withdrawal-fees","bybit-onchain-withdrawal"],"risk":"high"},{"id":"c3","text":"Some custodial destinations require both a blockchain address and a destination tag or memo to credit the correct user account.","sourceIds":["okx-tag-memo","coinbase-destination-tags"],"risk":"high"},{"id":"c4","text":"Completion on a sending platform, blockchain confirmation and credit by the receiving platform are separate operational milestones.","sourceIds":["binance-transaction-status","coinbase-troubleshooting","kraken-withdrawal-status"],"risk":"medium"},{"id":"c5","text":"Recovery after a wrong-network or wrong-tag transfer is conditional and often depends on the receiving platform or wallet, with no guarantee of success.","sourceIds":["okx-withdrawal-error","coinbase-troubleshooting","bitget-uncredited-deposit"],"risk":"high"},{"id":"c6","text":"A small test transfer can reduce operational uncertainty but does not prove that later transfers will have identical fees, limits, availability or processing times.","sourceIds":["coinbase-destination-tags","binance-withdrawal-fees","bybit-onchain-withdrawal"],"risk":"medium"},{"id":"c7","text":"Users should preserve the asset, network, address, tag or memo, amount, timestamp and transaction ID because these fields determine troubleshooting and possible recovery paths.","sourceIds":["okx-withdrawal-error","binance-transaction-status","bitget-uncredited-deposit"],"risk":"medium"},{"id":"c8","text":"This guide does not verify live account eligibility, network uptime, fees, minimums, confirmation thresholds or recovery availability for any individual user.","sourceIds":["binance-withdrawal-fees","bybit-onchain-withdrawal","coinbase-troubleshooting"],"risk":"low"}],"relatedVenues":["binance","okx","coinbase","kraken","bybit","bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"bybit-l3-vic-delisting-withdrawal-deadlines","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-10T17:35:00.000Z","updatedAt":"2026-09-10T17:35:00Z","readTime":"14 min","author":"NexuAlpha Research Desk","title":{"en":"Bybit L3 and VIC Delisting: Spot, Convert, Bot, Deposit and Withdrawal Deadlines","zh-Hans":"Bybit 下架 L3 与 VIC：现货、Convert、机器人、充值与提现时间线","ja":"Bybit L3・VIC上場廃止：現物、Convert、Bot、入出金の期限","ko":"Bybit L3·VIC 상장폐지: 현물, Convert, 봇, 입출금 마감","tr":"Bybit L3 ve VIC delistingi: Spot, Convert, bot ve yatırma-çekme tarihleri","es":"Bybit retira L3 y VIC: plazos de spot, Convert, bots y retiros","pt-BR":"Delisting de L3 e VIC na Bybit: prazos de spot, Convert, bots e saques","fr":"Retrait de L3 et VIC chez Bybit : échéances spot, Convert, bots et retraits","de":"Bybit nimmt L3 und VIC aus dem Handel: Fristen für Spot, Convert, Bots und Auszahlungen","ar":"إزالة L3 وVIC من Bybit: مواعيد التداول والتحويل والسحب","ru":"Делистинг L3 и VIC на Bybit: сроки спота, бота и вывода","id":"Delisting L3 dan VIC di Bybit: batas spot, bot, dan penarikan","vi":"Bybit hủy niêm yết L3 và VIC: thời hạn spot, bot và rút tiền","it":"Delisting L3 e VIC su Bybit: scadenze per spot, bot e prelievi"},"summary":{"en":"Bybit's September 10, 2026 notice says it will delist L3 and VIC.","zh-Hans":"Bybit 在 2026 年 9 月 10 日发布公告，称在最新审核后将下架 L3 与 VIC。公告点名的现货交易对是 L3USDT 与 VICUSDT。L3 与 VIC 的充值将在 2026 年 9 月 16 日 08:00 UTC 之后关闭；L3USDT 与 VICUSDT 的现货交易将在 2026 年 9 月 17 日 08:00 UTC 之后结束，未成交挂单会被自动移除；L3 与 VIC 也将在同一时间之后从 Bybit Convert 移除。若用户在 L3USDT 或 VICUSDT 上仍有 DCA Bot 或 Spot Grid Bot，Bybit 要求在 9 月 17 日 08:00 UTC 前主动关闭，否则系统会自动终止。","ja":"Bybit告知に基づき、現物・Convert・Botの停止、入金終了、出金期限と利用者確認事項を整理します。","ko":"Bybit 공지를 기준으로 현물·Convert·봇 중단, 입금 종료, 출금 기한과 사용자 확인 사항을 정리합니다.","tr":"Bybit duyurusuna göre spot, Convert ve bot kapanışlarını, yatırma sonunu, çekim tarihlerini ve kullanıcı kontrollerini özetliyoruz.","es":"Resume el aviso de Bybit, los cierres de depósitos y las fechas que deben revisar los usuarios.","pt-BR":"Resume o aviso da Bybit, o encerramento de depósitos e as datas que os usuários devem verificar.","fr":"Résumé de l’avis Bybit, de la fermeture des dépôts et des dates à vérifier.","de":"Zusammenfassung der Bybit-Mitteilung, der Einzahlungsstopps und der wichtigen Fristen.","ar":"نلخص إشعار Bybit ونهايات الإيداع ومواعيد السحب المهمة.","ru":"Разбираем уведомление Bybit и важные сроки депозитов и вывода.","id":"Ringkas pemberitahuan Bybit serta tenggat deposit dan penarikan.","vi":"Tóm tắt thông báo Bybit và các hạn nạp, rút quan trọng.","it":"Sintesi dell’avviso Bybit e delle scadenze di deposito e prelievo."},"claims":[{"id":"c1","text":"Bybit published a September 10, 2026 notice saying it will delist L3 and VIC after its latest review.","sourceIds":["bybit-l3-vic-delisting-20260910"],"risk":"medium"},{"id":"c2","text":"The affected Bybit Spot pairs named in the announcement are L3USDT and VICUSDT.","sourceIds":["bybit-l3-vic-delisting-20260910"],"risk":"high"},{"id":"c3","text":"Bybit says Spot trading for L3USDT and VICUSDT will end after 2026-09-17 08:00 UTC and open orders will be automatically removed.","sourceIds":["bybit-l3-vic-delisting-20260910"],"risk":"high"},{"id":"c4","text":"Bybit says L3 and VIC will be removed from Bybit Convert after 2026-09-17 08:00 UTC.","sourceIds":["bybit-l3-vic-delisting-20260910"],"risk":"medium"},{"id":"c5","text":"Bybit says deposits for L3 and VIC will close after 2026-09-16 08:00 UTC.","sourceIds":["bybit-l3-vic-delisting-20260910"],"risk":"high"},{"id":"c6","text":"Bybit says active DCA Bots or Spot Grid Bots on L3USDT and VICUSDT should be closed before 2026-09-17 08:00 UTC or they will be automatically terminated.","sourceIds":["bybit-l3-vic-delisting-20260910"],"risk":"high"},{"id":"c7","text":"Bybit says users can continue withdrawing assets after L3 trading pairs are closed, while recommending early withdrawal.","sourceIds":["bybit-l3-vic-delisting-20260910"],"risk":"medium"},{"id":"c8","text":"Bybit says VIC withdrawals will no longer be available after 2026-12-16 08:00 UTC.","sourceIds":["bybit-l3-vic-delisting-20260910"],"risk":"high"},{"id":"c9","text":"Bybit says VIC tokens may be converted into stablecoins on users' behalf after the withdrawal function closes, but the conversion is not guaranteed.","sourceIds":["bybit-l3-vic-delisting-20260910","bybit-spot-delisting-mechanism"],"risk":"high"},{"id":"c10","text":"Bybit's general Spot Delisting Mechanism says a delisted token may have associated trading pairs, deposits and withdrawals suspended, and describes a withdrawal buffer before withdrawal suspension.","sourceIds":["bybit-spot-delisting-mechanism"],"risk":"medium"},{"id":"c11","text":"Layer3 describes its ecosystem as omnichain infrastructure for distribution, identity and incentives, while CoinGecko tracked L3 across 19 exchanges and 19 markets at the snapshot.","sourceIds":["layer3-foundation-overview","coingecko-layer3-20260910"],"risk":"medium"},{"id":"c12","text":"Viction documentation describes masternodes securing the network and receiving rewards in VIC, while CoinGecko still listed Bybit among VIC markets at the snapshot.","sourceIds":["viction-docs-getting-started","coingecko-viction-20260910"],"risk":"medium"}],"relatedVenues":["bybit"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"tokenized-securities-settlement-records-finality","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-09T23:55:00.000Z","updatedAt":"2026-09-09T23:55:00Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Tokenized Securities Settlement: What Moves Onchain, What Remains Offchain","zh-Hans":"代币化证券交收：哪些东西上链，哪些仍然留在链下","ja":"トークン化証券の決済：オンチェーンで動くもの、オフチェーンに残るもの","ko":"토큰화 증권 결제: 온체인으로 이동하는 것과 오프체인에 남는 것","tr":"Tokenleştirilmiş menkul kıymet takası: Zincir üstünde hareket edenler ve zincir dışında kalanlar","es":"Liquidación de valores tokenizados: qué se mueve onchain y qué queda fuera de la cadena","pt-BR":"Liquidação de valores mobiliários tokenizados: o que se move onchain e o que fica off-chain","fr":"Règlement de titres tokenisés : ce qui circule onchain et ce qui reste off-chain","de":"Abwicklung tokenisierter Wertpapiere: Was onchain bewegt wird und offchain bleibt","ar":"تسوية الأوراق المالية المرمّزة: ما يتحرك على السلسلة وما يبقى خارجها","ru":"Расчёты по токенизированным ценным бумагам: что движется onchain, а что остаётся offchain","id":"Penyelesaian sekuritas bertoken: apa yang bergerak onchain dan apa yang tetap off-chain","vi":"Thanh toán chứng khoán token hóa: thứ gì chạy onchain và thứ gì vẫn off-chain","it":"Regolamento di titoli tokenizzati: cosa si muove onchain e cosa resta off-chain"},"summary":{"en":"Tokenized securities settlement is not just a blockchain transfer.","zh-Hans":"一笔区块链交易确认，不等于一笔证券交收已经完整完成。","ja":"ブロックチェーンの移転と発行体記録、DTC帳簿、現金決済、DvP、最終性、照合、カストディリスクを出典付きで整理します。","ko":"블록체인 이전과 발행사 기록, DTC 장부, 현금 결제, DvP, 최종성, 대사와 수탁 위험을 출처와 함께 구분합니다.","tr":"Blok zinciri transferlerini ihraççı kayıtları, DTC defterleri, nakit bacağı, DvP, kesinleşme, mutabakat ve saklama riskiyle ayıran kaynaklı açıklama.","es":"Explicación basada en fuentes que separa las transferencias de tokens de los registros del emisor, libros DTC, pagos en efectivo, DvP, finalidad, conciliación y riesgo de custodia.","pt-BR":"Explicação baseada em fontes que separa transferências de tokens, registros do emissor, livros da DTC, liquidação em dinheiro, DvP, finalização, conciliação e risco de custódia.","fr":"Explication sourcée séparant les transferts de tokens des registres de l’émetteur, livres DTC, jambe cash, DvP, finalité, rapprochement et risque de conservation.","de":"Quellenbasierte Erklärung zu Tokenübertragungen, Emittentenregistern, DTC-Büchern, Cash-Leg, DvP, Finalität, Abstimmung und Verwahrungsrisiko.","ar":"شرح قائم على المصادر يميز بين نقل الرموز وسجلات المُصدر ودفاتر DTC والمدفوعات النقدية وDvP والنهائية والتسوية ومخاطر الحفظ.","ru":"Разбор на основе источников: переводы токенов, записи эмитента, книги DTC, денежная часть, DvP, финальность, сверка и риск хранения.","id":"Penjelasan berbasis sumber yang memisahkan transfer token dari catatan penerbit, buku DTC, pembayaran tunai, DvP, finalitas, rekonsiliasi, dan risiko kustodi.","vi":"Bài giải thích dựa trên nguồn, tách chuyển token khỏi hồ sơ tổ chức phát hành, sổ DTC, phần tiền mặt, DvP, tính chung cuộc, đối soát và rủi ro lưu ký.","it":"Spiegazione basata su fonti che separa trasferimenti di token, registri dell’emittente, libri DTC, gamba cash, DvP, finalità, riconciliazione e rischio di custodia."},"claims":[{"id":"c1","text":"The SEC staff statement describes a tokenized security as a security represented by a crypto asset where the ownership record is maintained in whole or in part through crypto networks.","sourceIds":["sec-tokenized-securities-2026"],"risk":"high"},{"id":"c2","text":"In issuer-sponsored models, a token transfer may be integrated with the issuer or agent's master securityholder file; in other models, the token transfer may only notify an offchain record update.","sourceIds":["sec-tokenized-securities-2026"],"risk":"high"},{"id":"c3","text":"The SEC staff statement says third-party tokenization can include custodial tokenized security entitlements and synthetic linked securities or security-based swaps, with different holder rights and third-party risks.","sourceIds":["sec-tokenized-securities-2026"],"risk":"high"},{"id":"c4","text":"The SEC staff statement is not a Commission rule, regulation, guidance or Commission statement, and it has no legal force or effect.","sourceIds":["sec-tokenized-securities-2026"],"risk":"high"},{"id":"c5","text":"DTCC says DTC's tokenization service will tokenize eligible securities only from a Participant's traditional DTC account after instruction and risk-control checks, then hold the underlying traditional securities in a DTC Digital Omnibus Account.","sourceIds":["dtcc-tokenization-faq"],"risk":"high"},{"id":"c6","text":"DTCC says LedgerScan will maintain DTC's official record of token movements and locations, and DTC will reconcile tokenized security entitlements against traditional securities entitlements held in its omnibus account.","sourceIds":["dtcc-tokenization-faq"],"risk":"high"},{"id":"c7","text":"DTCC says the custody relationship between DTC and its Participant does not change whether assets are held in traditional or tokenized form.","sourceIds":["dtcc-tokenization-faq"],"risk":"high"},{"id":"c8","text":"DTCC says digitized settlement will not be offered at the launch of the tokenization service and may be included in future phases depending on DTC rules and regulatory approval.","sourceIds":["dtcc-tokenization-faq"],"risk":"high"},{"id":"c9","text":"Commissioner Peirce's statement says the DTC pilot is subject to operational limitations and will let registered DTC participants transfer tokenized entitlements while DTC tracks transfers for official books and records.","sourceIds":["sec-peirce-dtc-no-action-2025"],"risk":"medium"},{"id":"c10","text":"BIS settlement research describes DvP as coordinating the securities leg and the cash leg, with atomic settlement able to transfer both tokens simultaneously when both legs exist on one ledger.","sourceIds":["bis-future-securities-settlement"],"risk":"medium"},{"id":"c11","text":"BIS research says cross-ledger DvP can introduce a failure mode where one leg is delivered and the other is not, exposing participants to principal risk unless governance or arbitration resolves disputes.","sourceIds":["bis-future-securities-settlement"],"risk":"medium"},{"id":"c12","text":"BIS's next-generation monetary and financial system chapter says tokenized systems can use smart contracts for access rights, collateral eligibility and token exchange, but also flags interoperability, booking, reconciliation and fragmentation challenges.","sourceIds":["bis-next-generation-monetary-system-2025"],"risk":"medium"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-brazil-morpho-usdc-defi-earn","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-09T23:50:00.000Z","updatedAt":"2026-09-09T23:50:00Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase Brazil DeFi Earn: What the Morpho USDC Rollout Actually Changes","zh-Hans":"Coinbase 在巴西上线 Morpho USDC DeFi Earn：真正变化、风险与未知项","ja":"Coinbase Brazil DeFi Earn：Morpho USDC展開で変わること","ko":"Coinbase Brazil DeFi Earn: Morpho USDC 출시가 바꾸는 점","tr":"Coinbase Brazil DeFi Earn: Morpho USDC lansmanı neyi değiştiriyor?","es":"Coinbase Brazil DeFi Earn: qué cambia realmente con Morpho USDC","pt-BR":"Coinbase Brazil DeFi Earn: o que o lançamento de Morpho USDC realmente muda","fr":"Coinbase Brazil DeFi Earn : ce que change réellement le déploiement Morpho USDC","de":"Coinbase Brazil DeFi Earn: Was der Morpho-USDC-Rollout tatsächlich ändert","ar":"Coinbase Brazil DeFi Earn: ما الذي يغيره إطلاق Morpho USDC فعلياً؟","ru":"Coinbase Brazil DeFi Earn: что на самом деле меняет запуск Morpho USDC","id":"Coinbase Brazil DeFi Earn: apa yang sebenarnya berubah dari peluncuran Morpho USDC","vi":"Coinbase Brazil DeFi Earn: đợt triển khai Morpho USDC thực sự thay đổi điều gì?","it":"Coinbase Brazil DeFi Earn: cosa cambia davvero con il lancio Morpho USDC"},"summary":{"en":"Coinbase's Brazil DeFi Earn update is a progressive rollout for eligible Brazil customers who want to allocate USDC from the Coinbase app into Morpho-powered lending vaults.","zh-Hans":"Coinbase 在 2026 年 9 月 9 日宣布，面向巴西合格用户渐进开放 Morpho 驱动的 USDC DeFi Earn。用户可以在 Coinbase App 的 Lending 入口分配 USDC，但资金路径不是普通交易所余额生息，而是通过自托管钱包进入 Base 上的 Morpho 借贷协议，并进入 Steakhouse Financial 策略方相关的金库。奖励率是可变的，提款通常可以立即进行但受流动性影响，协议漏洞、坏账、清算失败和按比例亏损都属于 Coinbase 官方帮助中心披露的风险。","ja":"ブラジルの対象ユーザーに広がるMorphoベースのUSDC DeFi Earnについて、自主管理ウォレット、変動報酬、流動性リスクを説明します。","ko":"브라질 일부 고객에게 제공되는 Morpho 기반 USDC DeFi Earn의 자기 수탁 경로, 변동 보상과 유동성 위험을 설명합니다.","tr":"Brezilya’daki uygun müşterilere 제공되는 Morpho tabanlı USDC DeFi Earn için öz saklama yolu, değişken getiriler ve likidite risklerini açıklar.","es":"Coinbase está desplegando DeFi Earn basado en Morpho para USDC a clientes elegibles en Brasil. Explicamos autocustodia, recompensas variables y riesgos de liquidez.","pt-BR":"A Coinbase está levando o DeFi Earn com Morpho para USDC a clientes elegíveis no Brasil. Explicamos autocustódia, recompensas variáveis e riscos de liquidez.","fr":"Coinbase déploie DeFi Earn basé sur Morpho pour l’USDC auprès de clients éligibles au Brésil. Nous expliquons l’autoconservation, les rendements variables et la liquidité.","de":"Coinbase führt Morpho-basiertes USDC DeFi Earn für berechtigte Kunden in Brasilien ein. Wir erklären Selbstverwahrung, variable Erträge und Liquiditätsrisiken.","ar":"تشرح هذه المراجعة مسار الحفظ الذاتي والمكافآت المتغيرة ومخاطر السيولة في منتج USDC القائم على Morpho للعملاء المؤهلين في البرازيل.","ru":"Разбираем самостоятельное хранение, переменное вознаграждение и риски ликвидности в Morpho DeFi Earn для подходящих клиентов в Бразилии.","id":"Menjelaskan jalur self-custody, imbal hasil variabel, dan risiko likuiditas DeFi Earn berbasis Morpho untuk pelanggan Brasil yang memenuhi syarat.","vi":"Giải thích mô hình tự lưu ký, phần thưởng biến động và rủi ro thanh khoản của DeFi Earn dựa trên Morpho cho khách hàng đủ điều kiện tại Brazil.","it":"Spieghiamo autocustodia, ricompense variabili e rischi di liquidità del DeFi Earn basato su Morpho per i clienti idonei in Brasile."},"claims":[{"id":"c1","text":"Coinbase announced on September 9, 2026 that DeFi Earn is progressively rolling out to eligible customers in Brazil.","sourceIds":["coinbase-blog-brazil-morpho-20260909"],"risk":"medium"},{"id":"c2","text":"The product lets eligible users allocate USDC through the Lending tab in the Coinbase app and routes deposits to Morpho, an onchain lending protocol.","sourceIds":["coinbase-blog-brazil-morpho-20260909","coinbase-help-lending-usdc-en"],"risk":"medium"},{"id":"c3","text":"Coinbase says funds are routed from customers' self-custodial wallets to Morpho on Base and into vaults curated by Steakhouse Financial.","sourceIds":["coinbase-blog-brazil-morpho-20260909","coinbase-help-lending-intro-en"],"risk":"high"},{"id":"c4","text":"Depositing through the feature requires creating a self-custodial wallet to sign transactions and send funds to Morpho vaults.","sourceIds":["coinbase-help-lending-intro-en","coinbase-help-lending-usdc-en","coinbase-help-lending-intro-ptbr","coinbase-help-lending-usdc-ptbr"],"risk":"high"},{"id":"c5","text":"Coinbase describes lending rates as variable or market-driven, based on onchain supply and demand, vault type and app-displayed rates.","sourceIds":["coinbase-blog-brazil-morpho-20260909","coinbase-help-lending-intro-en","coinbase-help-lending-intro-ptbr"],"risk":"high"},{"id":"c6","text":"Coinbase says lenders can typically withdraw immediately, but its help pages identify liquidity delays or waiting periods as exceptions during high withdrawal demand.","sourceIds":["coinbase-blog-brazil-morpho-20260909","coinbase-help-lending-intro-en","coinbase-help-lending-intro-ptbr"],"risk":"high"},{"id":"c7","text":"Coinbase's USDC lending help page says borrowers pay interest, rewards accrue in real time, and non-USDC rewards such as MORPHO or other tokens may need to be claimed manually.","sourceIds":["coinbase-help-lending-usdc-en","coinbase-help-claim-rewards-en","coinbase-help-lending-usdc-ptbr","coinbase-help-claim-rewards-ptbr"],"risk":"medium"},{"id":"c8","text":"Coinbase identifies protocol risk, bad debt risk and liquidity risk for USDC lending through Morpho, including smart-contract failures, liquidation failures and proportional loss allocation.","sourceIds":["coinbase-help-lending-intro-en","coinbase-help-lending-intro-ptbr"],"risk":"high"},{"id":"c9","text":"Coinbase's terms note says that when users access Morpho through the Coinbase app, transactions are executed on a decentralized third-party network and Coinbase does not control the smart contracts or protocol terms.","sourceIds":["coinbase-help-lending-intro-en","coinbase-help-lending-intro-ptbr"],"risk":"high"},{"id":"c10","text":"Coinbase says USDC lending availability depends on jurisdiction or location and users should check their individual Coinbase account for regional availability.","sourceIds":["coinbase-help-lending-intro-en","coinbase-help-lending-intro-ptbr"],"risk":"high"},{"id":"c11","text":"This NexuAlpha article does not verify live eligibility, live vault liquidity, account-specific access, tax outcome, protocol solvency or future reward rates.","sourceIds":["coinbase-blog-brazil-morpho-20260909","coinbase-help-lending-intro-en","coinbase-help-defi-risks-en","coinbase-help-lending-intro-ptbr"],"risk":"low"}],"relatedVenues":["coinbase"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-status-page-disclosure-audit","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-09T23:49:42.411Z","updatedAt":"2026-09-09T23:49:42.411Z","readTime":"13 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange Status Page Audit: Coinbase, Kraken and OKX Compared","zh-Hans":"加密货币交易所状态页披露审计：Coinbase、Kraken 与 OKX 对比","ja":"暗号資産取引所のステータスページ監査：Coinbase・Kraken・OKX比較","ko":"암호화폐 거래소 상태 페이지 감사: Coinbase·Kraken·OKX 비교","tr":"Kripto borsası durum sayfası denetimi: Coinbase, Kraken ve OKX karşılaştırması","es":"Auditoría de páginas de estado de exchanges: Coinbase, Kraken y OKX","pt-BR":"Auditoria de páginas de status de exchanges: Coinbase, Kraken e OKX","fr":"Audit des pages de statut des exchanges : Coinbase, Kraken et OKX","de":"Audit der Exchange-Statusseiten: Coinbase, Kraken und OKX im Vergleich","ar":"تدقيق صفحات حالة منصات العملات: مقارنة Coinbase وKraken وOKX","ru":"Аудит страниц статуса криптобирж: сравнение Coinbase, Kraken и OKX","id":"Audit halaman status bursa kripto: perbandingan Coinbase, Kraken, dan OKX","vi":"Kiểm toán trang trạng thái sàn crypto: so sánh Coinbase, Kraken và OKX","it":"Audit delle pagine di stato degli exchange: confronto tra Coinbase, Kraken e OKX"},"summary":{"en":"Coinbase and Kraken exposed Statuspage-style JSON endpoints in this audit, while OKX provided human-readable status and help surfaces among the checked URLs.","zh-Hans":"本次审计只看官方公开表面。Coinbase 和 Kraken 在本次检查中都暴露了 Statuspage 风格的机器可读 JSON 端点，包括 overall status、summary、incidents 和 components。OKX 在本次检查的公开表面中提供了可访问的状态页和若干帮助页，但在这些被检查的 OKX URL 上，没有发现与 Coinbase、Kraken 相同形态的 Statuspage JSON API。这个表述必须非常克制：不是断言 OKX 全网不存在机器可读接口，而是说本次检查的这些公开页面没有发现同类端点。","ja":"Coinbase、Kraken、OKXの障害情報をAPIの深さ、コンポーネント詳細、履歴、購読、入出金の注意点で比較します。","ko":"Coinbase, Kraken, OKX의 상태 공개를 API 깊이, 구성요소 상세도, 장애 이력, 구독과 입출금 주의사항으로 비교합니다.","tr":"Coinbase, Kraken ve OKX durum açıklamalarını API derinliği, bileşen ayrıntısı, olay geçmişi, abonelikler ve yatırma-çekme uyarılarıyla karşılaştırır.","es":"Auditoría basada en fuentes de las páginas de estado de Coinbase, Kraken y OKX sobre profundidad de API, componentes, incidentes, suscripciones y avisos de depósitos y retiros.","pt-BR":"Auditoria baseada em fontes das páginas de status de Coinbase, Kraken e OKX sobre profundidade de API, componentes, incidentes, assinaturas e avisos de depósitos e saques.","fr":"Audit sourcé des pages de statut de Coinbase, Kraken et OKX sur la profondeur API, les composants, les incidents, les abonnements et les réserves sur dépôts et retraits.","de":"Quellenbasierter Audit der Statusseiten von Coinbase, Kraken und OKX zu API-Tiefe, Komponenten, Vorfällen, Abos sowie Hinweisen zu Ein- und Auszahlungen.","ar":"تدقيق قائم على المصادر لإفصاحات الحالة لدى Coinbase وKraken وOKX من حيث عمق API وتفاصيل المكونات والحوادث والاشتراكات وتنبيهات الإيداع والسحب.","ru":"Проверяем раскрытие статуса Coinbase, Kraken и OKX: глубина API, компоненты, инциденты, подписки и оговорки по вводу и выводу.","id":"Audit berbasis sumber atas status Coinbase, Kraken, dan OKX: kedalaman API, detail komponen, insiden, langganan, serta catatan deposit dan penarikan.","vi":"Kiểm toán dựa trên nguồn về công bố trạng thái Coinbase, Kraken và OKX, gồm độ sâu API, thành phần, sự cố, đăng ký nhận tin và lưu ý nạp rút.","it":"Audit basato su fonti delle pagine di stato di Coinbase, Kraken e OKX su profondità API, componenti, incidenti, iscrizioni e avvisi su depositi e prelievi."},"claims":[{"id":"c1","text":"At 2026-09-09T23:49:42.411Z, Coinbase's checked Statuspage API status endpoint returned indicator none and description All Systems Operational.","sourceIds":["coinbase-status-api","coinbase-summary-api"],"risk":"medium"},{"id":"c2","text":"The same Coinbase capture returned 174 components from summary/components and 50 incident records from the incidents endpoint; those counts describe the returned API payload, not a guarantee about every account or network.","sourceIds":["coinbase-summary-api","coinbase-incidents-api","coinbase-components-api"],"risk":"medium"},{"id":"c3","text":"At 2026-09-09T23:49:42.411Z, Kraken's checked Statuspage API status endpoint returned indicator minor and description Partially Degraded Service.","sourceIds":["kraken-status-api","kraken-summary-api"],"risk":"medium"},{"id":"c4","text":"The Kraken capture returned 830 components from summary/components, 50 incident records from the incidents endpoint, and non-operational funding samples including Digital Currency Funding and selected asset funding components.","sourceIds":["kraken-summary-api","kraken-incidents-api","kraken-components-api"],"risk":"medium"},{"id":"c5","text":"Kraken's captured summary showed Moonbeam and Moonriver Funding Delays as an investigating incident and Digital Currency Funding as degraded_performance.","sourceIds":["kraken-summary-api","kraken-components-api"],"risk":"medium"},{"id":"c6","text":"The checked OKX public surfaces returned HTTP 200 HTML pages, including the status page and deposit, withdrawal, and supported-network help articles, but this audit did not find a Statuspage-style public JSON endpoint on the checked OKX surfaces.","sourceIds":["okx-status-page","okx-cant-withdraw","okx-deposit-withdrawal-suspended","okx-supported-tokens-networks"],"risk":"medium"},{"id":"c7","text":"A human-readable HTTP 200 status or help page is not equivalent to account-specific deposit, withdrawal, network, compliance, or risk-control availability.","sourceIds":["coinbase-status-page","kraken-status-page","okx-status-page","okx-cant-withdraw","okx-deposit-withdrawal-suspended","okx-supported-tokens-networks"],"risk":"high"},{"id":"c8","text":"Statuspage component counts may include groups and child components; they should not be interpreted as a count of independently available exchange products.","sourceIds":["coinbase-summary-api","coinbase-components-api","kraken-summary-api","kraken-components-api"],"risk":"medium"},{"id":"c9","text":"This audit is a point-in-time disclosure review; status pages can change after capture and do not substitute for logged-in checks before transfers or trades.","sourceIds":["coinbase-status-api","kraken-status-api","okx-status-page","okx-cant-withdraw","okx-supported-tokens-networks"],"risk":"high"}],"relatedVenues":["coinbase","kraken","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"okx-dex-tokenized-stock-interface-fee","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-09T00:18:00.000Z","updatedAt":"2026-09-09T00:18:00Z","readTime":"8 min","author":"NexuAlpha Research Desk","title":{"en":"OKX DEX Tokenized Stock Interface Fee Update: What Group 2 Means","zh-Hans":"OKX DEX 调整 tokenized stocks interface fee：Group 2 到底意味着什么","ja":"OKX DEXのトークン化株式インターフェース手数料：Group 2とは","ko":"OKX DEX 토큰화 주식 인터페이스 수수료 업데이트: Group 2의 의미","tr":"OKX DEX tokenleştirilmiş hisse arayüzü ücreti: Group 2 ne anlama geliyor?","es":"Actualización de la tarifa de la interfaz de acciones tokenizadas de OKX DEX: qué significa Group 2","pt-BR":"Atualização da taxa da interface de ações tokenizadas da OKX DEX: o que significa Group 2","fr":"Mise à jour des frais de l’interface d’actions tokenisées OKX DEX : que signifie Group 2 ?","de":"Gebührenupdate der OKX-DEX-Schnittstelle für tokenisierte Aktien: Was bedeutet Group 2?","ar":"تحديث رسوم واجهة الأسهم المرمّزة في OKX DEX: ماذا يعني Group 2؟","ru":"Обновление комиссии интерфейса токенизированных акций OKX DEX: что означает Group 2","id":"Pembaruan biaya antarmuka saham bertoken OKX DEX: apa arti Group 2?","vi":"Cập nhật phí giao diện cổ phiếu token hóa OKX DEX: Group 2 nghĩa là gì?","it":"Aggiornamento della commissione dell’interfaccia per azioni tokenizzate OKX DEX: cosa significa Group 2?"},"summary":{"en":"OKX's September 7 update says stock token trades on X Layer moved to the standard Group 2 OKX DEX interface fee rate at 15:00 UTC+8, and that stock token trades across all OKX DEX supported networks are subject to the standard Group 2 interface fee rate.","zh-Hans":"OKX 在 2026-09-07 发布公告，称 OKX DEX 将在 2026 年 9 月 7 日 15:00（UTC+8）调整 X Layer 上 stock tokens 的 interface fee rate。调整后，X Layer 上的 stock token trades 将适用标准 Group 2 interface fee rate。OKX DEX Fees 页面进一步写明，OKX DEX 支持的所有区块链网络上的 tokenized stocks 都被归类为 Group2 tokens，并适用标准 Group 2 interface fee rate。","ja":"OKX DEXの手数料変更を、ガス代、プロトコル手数料、スリッページとの違いとともに説明します。","ko":"OKX DEX의 수수료 변경과 가스비, 프로토콜 수수료, 슬리피지의 차이를 설명합니다.","tr":"OKX DEX’in ücret değişikliğini gaz, protokol ücreti ve kaymadan ayıran birinci taraf açıklaması.","es":"Una actualización de OKX explica el cambio de tarifa de interfaz del 7 de septiembre y cómo se diferencia del gas, las comisiones de protocolo y el deslizamiento.","pt-BR":"Uma atualização da OKX explica a mudança de 7 de setembro e a diferença entre a taxa de interface, gas, taxa de protocolo e slippage.","fr":"Une mise à jour officielle d’OKX explique la modification du 7 septembre et la différence entre frais d’interface, gas, frais de protocole et slippage.","de":"Ein offizielles OKX-Update erklärt die Änderung vom 7. September und den Unterschied zu Gas, Protokollgebühren und Slippage.","ar":"يوضح تحديث رسمي من OKX تغيير رسوم الواجهة في 7 سبتمبر والفرق بينها وبين الغاز ورسوم البروتوكول والانزلاق.","ru":"Официальное обновление OKX объясняет изменение 7 сентября и отличие комиссии интерфейса от газа, протокольной комиссии и проскальзывания.","id":"Pembaruan resmi OKX menjelaskan perubahan biaya 7 September dan bedanya dengan gas, biaya protokol, serta slippage.","vi":"Bản cập nhật chính thức của OKX giải thích thay đổi phí ngày 7 tháng 9 và sự khác nhau giữa phí giao diện, gas, phí giao thức và trượt giá.","it":"Un aggiornamento ufficiale di OKX spiega la modifica del 7 settembre e la differenza tra commissione d’interfaccia, gas, protocollo e slippage."},"claims":[{"id":"c1","text":"OKX announced that OKX DEX would adjust the interface fee rate for stock tokens on X Layer at 15:00 on September 7, 2026 UTC+8.","sourceIds":["okx-interface-fee-update-0907"],"risk":"medium"},{"id":"c2","text":"After the adjustment, stock token trades on X Layer are subject to the standard Group 2 interface fee rate.","sourceIds":["okx-interface-fee-update-0907"],"risk":"medium"},{"id":"c3","text":"OKX says fee rates for stock token trades on other blockchain networks remain unchanged and continue to follow the standard Group 2 interface fee rate.","sourceIds":["okx-interface-fee-update-0907"],"risk":"medium"},{"id":"c4","text":"OKX says that following the adjustment, stock token trades across all networks supported by OKX DEX are subject to the standard Group 2 interface fee rate.","sourceIds":["okx-interface-fee-update-0907","okx-dex-fees"],"risk":"medium"},{"id":"c5","text":"The OKX DEX Fees page says OKX DEX charges a flat user interface fee for using the OKX DEX interface to access and conduct transactions on third-party DEXs.","sourceIds":["okx-dex-fees"],"risk":"medium"},{"id":"c6","text":"The OKX Web3 DEX Interface User Agreement distinguishes gas fees, third-party protocol fees and service fees.","sourceIds":["okx-web3-dex-interface-user-agreement"],"risk":"medium"},{"id":"c7","text":"The OKX Web3 DEX Interface User Agreement says proposed routes can be generated using estimated output amount, gas costs, price impact, liquidity depth and user slippage tolerance.","sourceIds":["okx-web3-dex-interface-user-agreement"],"risk":"medium"},{"id":"c8","text":"OKX states that OKX Web3 Wallet is a self-custody wallet software service, not all products are offered in all regions, and OKX Web3 Wallet and ancillary services are not offered by OKX Exchange.","sourceIds":["okx-interface-fee-update-0907"],"risk":"high"},{"id":"c9","text":"The article does not verify live routes, gas, third-party protocol fees, liquidity, slippage, issuer terms, legal rights or regional availability.","sourceIds":["okx-interface-fee-update-0907","okx-dex-fees","okx-web3-dex-interface-user-agreement"],"risk":"low"}],"relatedVenues":[],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"coinbase-vs-kraken","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-08T23:44:42.000Z","updatedAt":"2026-09-08T23:44:42Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"Coinbase vs Kraken: custody, fee disclosure, products and user fit","zh-Hans":"Coinbase vs Kraken：托管、费用披露、产品范围与用户适配","ja":"CoinbaseとKraken：カストディ、手数料開示、商品、利用者適合性","ko":"Coinbase와 Kraken: 수탁, 수수료 공개, 상품과 사용자 적합성","tr":"Coinbase ve Kraken: saklama, ücret açıklaması, ürünler ve kullanıcı uyumu","es":"Coinbase frente a Kraken: custodia, comisiones, productos y encaje para el usuario","pt-BR":"Coinbase vs. Kraken: custódia, taxas, produtos e adequação ao usuário","fr":"Coinbase et Kraken : conservation, frais, produits et adéquation utilisateur","de":"Coinbase und Kraken: Verwahrung, Gebühren, Produkte und Nutzerprofil","ar":"مقارنة Coinbase وKraken: الحفظ والرسوم والمنتجات وملاءمة المستخدم","ru":"Coinbase и Kraken: хранение, комиссии, продукты и соответствие пользователю","id":"Coinbase vs Kraken: kustodi, biaya, produk, dan kecocokan pengguna","vi":"Coinbase và Kraken: lưu ký, phí, sản phẩm và mức độ phù hợp","it":"Coinbase e Kraken: custodia, commissioni, prodotti e aderenza all’utente"},"summary":{"en":"Coinbase is usually easier to frame as an ecosystem choice: Coinbase app, Advanced Trade, Exchange, Prime, non-custodial wallet infrastructure, staking APIs and derivatives surfaces under different eligibility rules.","zh-Hans":"如果你最在意“还没登录之前，我能不能把费用结构看清楚”，Kraken 更容易做公开核验。它的官方 fee schedule 把 instant buy/sell、自定义订单、Kraken Pro 现货阶梯、稳定币/锚定币/外汇交易对、质押佣金说明以及部分产品费用集中在一个页面。这个优势不是“Kraken 一定更便宜”，而是“公开费用披露更集中、更容易检查”。","ja":"手数料開示、カストディと自己管理、商品範囲、ステーキング、デリバティブ、地域条件を出典付きで中立比較します。","ko":"수수료 공개, 수탁·자기 보관, 상품 범위, 스테이킹, 파생상품과 지역 조건을 중립적으로 비교합니다.","tr":"Ücret açıklaması, saklama ve öz saklama, ürün kapsamı, staking, türevler ve bölgesel koşulları tarafsızca karşılaştırır.","es":"Comparación neutral y basada en fuentes sobre comisiones, custodia y autocustodia, productos, staking, derivados, condiciones regionales y perfil de usuario.","pt-BR":"Comparação neutra e baseada em fontes sobre taxas, custódia e autocustódia, produtos, staking, derivativos, condições regionais e perfil de usuário.","fr":"Comparaison neutre et sourcée des frais, de la conservation et de l’autoconservation, des produits, du staking, des dérivés et des conditions régionales.","de":"Ein neutraler, quellenbasierter Vergleich von Gebühren, Verwahrung und Selbstverwahrung, Produkten, Staking, Derivaten und regionalen Bedingungen.","ar":"مقارنة محايدة وموثقة للرسوم والحفظ والحفظ الذاتي والمنتجات والتخزين والمشتقات والشروط الإقليمية وملاءمة المستخدم.","ru":"Нейтральное сравнение на основе источников: комиссии, хранение и самостоятельное хранение, продукты, стейкинг, деривативы и региональные условия.","id":"Perbandingan netral berbasis sumber tentang biaya, kustodi dan self-custody, produk, staking, derivatif, kondisi wilayah, dan kecocokan pengguna.","vi":"So sánh trung lập dựa trên nguồn về phí, lưu ký và tự lưu ký, sản phẩm, staking, phái sinh, điều kiện khu vực và mức độ phù hợp.","it":"Confronto neutrale basato su fonti su commissioni, custodia e autocustodia, prodotti, staking, derivati, condizioni regionali e profilo utente."},"claims":[{"id":"c1","text":"Coinbase exposes authenticated maker and taker fee rates plus 30-day trailing USD volume through the Coinbase Exchange API, and the quoted rates are subject to change.","sourceIds":["coinbase-exchange-fees"],"risk":"medium"},{"id":"c2","text":"Coinbase Prime trading fees are applied at execution using negotiated basis-points rates, with All In and Cost Plus structures; examples on the documentation page are illustrative and not client-specific quotes.","sourceIds":["coinbase-prime-trading-fees"],"risk":"medium"},{"id":"c3","text":"Coinbase Advanced Trade API covers programmatic trading and order management for spot, US futures and Global Derivatives, with eligibility and product availability limits.","sourceIds":["coinbase-advanced-trade-api"],"risk":"high"},{"id":"c4","text":"Coinbase CDP non-custodial wallets are described as user-custodied, with users maintaining control of assets and the ability to export keys, while system wallets can use API key authentication and secure infrastructure.","sourceIds":["coinbase-noncustodial-wallets"],"risk":"medium"},{"id":"c5","text":"Coinbase Prime staking APIs support eligible wallets and currently list ETH and SOL for Stake and Unstake API support, while some functionality is gated or beta.","sourceIds":["coinbase-prime-staking"],"risk":"high"},{"id":"c6","text":"Kraken's fee schedule presents instant buy/sell, custom order, Kraken Pro spot, stablecoin/FX and several product-specific fee sections on one official page, while noting spreads, payment fees and availability limits.","sourceIds":["kraken-fee-schedule"],"risk":"medium"},{"id":"c7","text":"Kraken Wallet is presented as a self-custody wallet with seed phrase wallets, embedded wallet options and multichain portfolio, DeFi, swap and bridge features.","sourceIds":["kraken-wallet"],"risk":"medium"},{"id":"c8","text":"Kraken presents staking and perpetual futures as available product categories, but its pages include risk, geographic, eligibility and jurisdictional caveats that prevent a universal availability conclusion.","sourceIds":["kraken-staking","kraken-perps","kraken-fee-schedule"],"risk":"high"},{"id":"c9","text":"A responsible Coinbase vs Kraken comparison should separate fee-disclosure style, custody model, product set and user fit rather than declaring a universal winner.","sourceIds":["coinbase-exchange-fees","coinbase-prime-trading-fees","coinbase-advanced-trade-api","coinbase-noncustodial-wallets","coinbase-prime-staking","kraken-fee-schedule","kraken-wallet","kraken-staking","kraken-perps"],"risk":"low"}],"relatedVenues":["coinbase","kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"crypto-exchange-fee-disclosure-audit","status":"PUBLISHED","category":"research","categoryName":{"en":"Source-Backed Research","zh-Hans":"源头核验研究"},"publishedAt":"2026-09-08T23:43:40.000Z","updatedAt":"2026-09-08T23:43:40Z","readTime":"16 min","author":"NexuAlpha Research Desk","title":{"en":"Crypto Exchange Fee Disclosure Audit: What Six Public Fee Pages Actually Show","zh-Hans":"加密货币交易所费率披露审计：六个官方公开页面到底写清了什么？","ja":"暗号資産取引所の手数料開示監査：6社の公式ページで分かること","ko":"암호화폐 거래소 수수료 공개 감사: 공개 수수료 페이지 6곳의 실제 내용","tr":"Kripto borsası ücret açıklaması denetimi: Altı resmi sayfa ne gösteriyor?","es":"Auditoría de comisiones de exchanges: qué muestran seis páginas públicas","pt-BR":"Auditoria de taxas de exchanges: o que mostram seis páginas públicas","fr":"Audit des frais des exchanges : ce que montrent six pages publiques","de":"Audit der Exchange-Gebühren: Was sechs öffentliche Seiten tatsächlich zeigen","ar":"تدقيق إفصاح رسوم منصات العملات: ماذا تظهر ست صفحات عامة؟","ru":"Аудит раскрытия комиссий криптобирж: что показывают шесть публичных страниц","id":"Audit pengungkapan biaya bursa kripto: isi enam halaman publik","vi":"Kiểm toán công bố phí sàn crypto: sáu trang công khai cho thấy gì?","it":"Audit delle commissioni degli exchange: cosa mostrano sei pagine pubbliche"},"summary":{"en":"A public crypto exchange fee page can show whether trading fees are disclosed, but it rarely gives the full cost by itself.","zh-Hans":"本次样本限定为六家主流中心化交易所：Binance、OKX、Coinbase、Kraken、Bybit、Bitget。审计时间为 2026-09-08 23:43:40 UTC。选择这六家，是因为它们在加密货币用户的日常比较中出现频率很高，并且都存在至少一个无需登录即可访问的官方 fee、pricing 或 help 页面。","ja":"6社の公式手数料ページをMaker/Taker、VIP階層、出金手数料、更新日、地域条件で監査します。","ko":"6개 거래소의 공식 수수료 페이지를 메이커·테이커, VIP 등급, 출금 수수료, 업데이트 날짜와 지역 조건으로 점검합니다.","tr":"Altı resmi ücret sayfasını maker/taker, VIP kademeleri, çekim ücretleri, güncelleme tarihleri ve bölgesel koşullarla inceler.","es":"NexuAlpha revisa las páginas oficiales de Binance, OKX, Coinbase, Kraken, Bybit y Bitget sobre maker/taker, niveles VIP, retiros, fechas de actualización y condiciones regionales.","pt-BR":"A NexuAlpha audita as páginas oficiais de Binance, OKX, Coinbase, Kraken, Bybit e Bitget sobre maker/taker, níveis VIP, saques, datas de atualização e condições regionais.","fr":"NexuAlpha examine les pages officielles de Binance, OKX, Coinbase, Kraken, Bybit et Bitget sur maker/taker, niveaux VIP, retraits, dates de mise à jour et conditions régionales.","de":"NexuAlpha prüft die offiziellen Gebührenseiten von Binance, OKX, Coinbase, Kraken, Bybit und Bitget auf Maker/Taker, VIP-Stufen, Auszahlungen, Aktualisierungen und regionale Bedingungen.","ar":"تدقيق لصفحات الرسوم الرسمية لدى Binance وOKX وCoinbase وKraken وBybit وBitget من حيث maker/taker ودرجات VIP ورسوم السحب والتحديث والشروط الإقليمية.","ru":"Проверяем официальные страницы Binance, OKX, Coinbase, Kraken, Bybit и Bitget: maker/taker, уровни VIP, выводы, даты обновления и региональные условия.","id":"NexuAlpha mengaudit halaman biaya resmi Binance, OKX, Coinbase, Kraken, Bybit, dan Bitget untuk maker/taker, tingkat VIP, biaya penarikan, tanggal pembaruan, dan kondisi wilayah.","vi":"NexuAlpha kiểm tra các trang phí chính thức của Binance, OKX, Coinbase, Kraken, Bybit và Bitget về maker/taker, bậc VIP, phí rút, ngày cập nhật và điều kiện khu vực.","it":"NexuAlpha esamina le pagine ufficiali di Binance, OKX, Coinbase, Kraken, Bybit e Bitget per maker/taker, livelli VIP, prelievi, aggiornamenti e condizioni regionali."},"claims":[{"id":"c1","text":"All six sampled exchanges exposed at least one official public fee or pricing surface, but public page access does not prove that a product is available to a specific user or region.","sourceIds":["binance-fee-trading","okx-trading-fee-faq","coinbase-fees","kraken-fee-schedule","bybit-trading-fee-structure","bitget-trading-fees-faq"],"risk":"medium"},{"id":"c2","text":"Binance, OKX, Kraken, Bybit and Bitget publicly show or explain maker/taker structures; Coinbase's captured public help page emphasizes order preview, spread, jurisdiction and product factors rather than exposing a complete logged-out maker/taker ladder.","sourceIds":["binance-fee-trading","okx-trading-fee-faq","okx-eea-spot-fees","coinbase-fees","kraken-fee-schedule","bybit-trading-fee-structure","bitget-trading-fees-faq"],"risk":"medium"},{"id":"c3","text":"Fee tiers are not directly comparable because venues use different qualifying variables, including trading volume, token balances, account assets, product setup, region, promotions and logged-in account state.","sourceIds":["binance-fee-trading","okx-trading-fee-faq","okx-eea-spot-fees","coinbase-fees","kraken-fee-schedule","bybit-trading-fee-structure","bitget-spot-trading-fees"],"risk":"medium"},{"id":"c4","text":"Withdrawal and network fees are often separate from trading fee tables and may require per-asset, per-network or transaction-preview checks.","sourceIds":["binance-fee-crypto","okx-deposit-withdrawal-fees","coinbase-fees","kraken-pricing","bybit-fees-you-need-to-know","bitget-trading-fees-faq","bitget-understanding-fees"],"risk":"medium"},{"id":"c5","text":"OKX explicitly warns that logged-out fee information may differ from the rates applying to a user's own account and that products or rules may not apply to all customers.","sourceIds":["okx-trading-fee-faq","okx-eea-spot-fees","okx-deposit-withdrawal-fees"],"risk":"low"},{"id":"c6","text":"Bybit states that actual fee rates may vary by region and directs verified users to their My Fee Rate page; its help pages also separate deposit, withdrawal, fiat and trading fees.","sourceIds":["bybit-trading-fee-structure","bybit-fees-you-need-to-know"],"risk":"low"},{"id":"c7","text":"Bitget's support pages disclose base maker/taker rates and explain VIP/BGB discounts, while also directing readers to the live Fee Schedule or withdrawal confirmation page for current details.","sourceIds":["bitget-trading-fees-faq","bitget-spot-trading-fees","bitget-understanding-fees"],"risk":"low"},{"id":"c8","text":"A responsible fee audit should avoid naming a cheapest exchange from public pages alone because product scope, account status, withdrawal route, spread, execution quality and region can change the paid cost.","sourceIds":["coinbase-fees","okx-trading-fee-faq","kraken-fee-schedule","bybit-trading-fee-structure","bitget-trading-fees-faq"],"risk":"medium"}],"relatedVenues":["binance","okx","coinbase","kraken","bybit","bitget"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"custodial-vs-self-custody-crypto","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-08T11:55:00.000Z","updatedAt":"2026-09-08T11:55:00Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"Custodial vs Self-Custody Crypto: Who Controls the Keys, Recovery and Trading Access?","zh-Hans":"托管钱包 vs 自托管钱包：谁控制私钥、恢复方式和交易入口？","ja":"カストディ型と自己管理型暗号資産：鍵、復旧、取引アクセスを誰が管理するか","ko":"수탁형과 자기 보관형 암호화폐: 키, 복구와 거래 접근을 누가 통제하는가","tr":"Saklamalı ve öz saklamalı kripto: Anahtarları, kurtarmayı ve işlem erişimini kim kontrol eder?","es":"Cripto con custodia o autocustodia: quién controla las claves, la recuperación y el acceso","pt-BR":"Cripto com custódia ou autocustódia: quem controla as chaves, a recuperação e o acesso","fr":"Crypto custodial ou en autoconservation : qui contrôle les clés, la récupération et l’accès ?","de":"Verwahrte oder selbstverwahrte Kryptowährungen: Wer kontrolliert Schlüssel, Wiederherstellung und Handel?","ar":"العملات المحفوظة والمنفصلة ذاتياً: من يسيطر على المفاتيح والاسترداد والتداول؟","ru":"Кастодиальные и самостоятельные криптоактивы: кто контролирует ключи, восстановление и торговлю?","id":"Kripto kustodian vs self-custody: siapa mengendalikan kunci, pemulihan, dan akses trading?","vi":"Crypto lưu ký hay tự lưu ký: ai kiểm soát khóa, khôi phục và quyền giao dịch?","it":"Crypto custodial o in autocustodia: chi controlla chiavi, recupero e accesso al trading?"},"summary":{"en":"Custodial crypto means an exchange or custodian manages the private keys and gives the user account-based trading and recovery access.","zh-Hans":"Investor.gov 在加密资产托管教育材料里讲得很清楚：钱包通常不是把加密资产本身“装进去”，而是保存访问和授权交易所需的私钥或口令。私钥能够授权交易，公钥用于接收和验证。也就是说，钱包真正管理的是访问权和签名权。","ja":"鍵の管理、復旧、取引アクセス、運用負担、相手方リスク、送金リスクを比較し、用途別に考えます。","ko":"키 통제, 복구, 거래 접근, 운영 부담, 상대방 위험과 전송 위험을 비교해 선택 기준을 제시합니다.","tr":"Anahtar kontrolü, kurtarma, işlem erişimi, operasyon yükü, karşı taraf riski ve transfer riskini dengeli biçimde karşılaştırır.","es":"Guía equilibrada sobre control de claves, recuperación, acceso al trading, carga operativa, riesgo de contraparte, riesgo de transacción y casos de uso.","pt-BR":"Guia equilibrado sobre controle de chaves, recuperação, acesso à negociação, carga operacional, risco de contraparte, risco de transação e usos adequados.","fr":"Guide équilibré sur le contrôle des clés, la récupération, l’accès au trading, la charge opérationnelle, le risque de contrepartie et le risque de transaction.","de":"Ausgewogener Leitfaden zu Schlüsselkontrolle, Wiederherstellung, Handelszugang, Betriebsaufwand, Gegenpartei- und Transaktionsrisiko.","ar":"دليل متوازن يقارن التحكم بالمفاتيح والاسترداد والوصول إلى التداول والعبء التشغيلي ومخاطر الطرف المقابل ومخاطر المعاملات.","ru":"Сбалансированный разбор контроля ключей, восстановления, доступа к торговле, операционной нагрузки, риска контрагента и риска транзакций.","id":"Panduan seimbang tentang kendali kunci, pemulihan, akses trading, beban operasional, risiko pihak lawan, dan risiko transaksi.","vi":"Hướng dẫn cân bằng về quyền kiểm soát khóa, khôi phục, truy cập giao dịch, gánh nặng vận hành, rủi ro đối tác và rủi ro giao dịch.","it":"Guida equilibrata su controllo delle chiavi, recupero, accesso al trading, onere operativo, rischio di controparte e rischio di transazione."},"claims":[{"id":"c1","text":"Crypto wallets generally store private keys or passcodes rather than the crypto assets themselves; control of the private key is central to authorizing transactions and access.","sourceIds":["investor-gov-custody-basics","kraken-custodial-non-custodial"],"risk":"low"},{"id":"c2","text":"Self-custody gives the user direct or sole control over private keys, but also puts recovery, seed phrase protection, device protection and transaction-signing responsibility on the user.","sourceIds":["investor-gov-custody-basics","coinbase-exchanges-self-custody","kraken-custodial-non-custodial"],"risk":"medium"},{"id":"c3","text":"Custodial crypto access, including exchange wallets, means a third party manages private keys and can provide account recovery and trading convenience, but it introduces platform, custodian, withdrawal, insolvency and safeguard questions.","sourceIds":["investor-gov-custody-basics","coinbase-exchanges-self-custody","kraken-custodial-non-custodial"],"risk":"medium"},{"id":"c4","text":"Recovery diagnostics are a useful distinction: if access can be restored by contacting or resetting credentials with a platform, it is custodial; if access depends on a recovery phrase or private key, it is self-custody.","sourceIds":["coinbase-exchanges-self-custody"],"risk":"low"},{"id":"c5","text":"Hot and cold wallet choices exist across custody models; cold storage can reduce internet exposure but introduces physical loss, damage, theft, backup and usability tradeoffs.","sourceIds":["investor-gov-custody-basics","kraken-custodial-non-custodial"],"risk":"medium"},{"id":"c6","text":"There is no single custody winner for every user: many holders combine custodial and non-custodial wallets for different purposes, such as active trading, long-term holding, DeFi access and operational recovery.","sourceIds":["kraken-custodial-non-custodial","investor-gov-custody-basics"],"risk":"medium"}],"relatedVenues":["coinbase","kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"binance-september-11-spot-margin-pair-removals","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-08T11:48:00.000Z","updatedAt":"2026-09-08T11:48:00Z","readTime":"7 min","author":"NexuAlpha Research Desk","title":{"en":"Binance September 11 Pair Removals: Spot Bots, Margin Positions and Collateral Deadlines","zh-Hans":"Binance 9 月 11 日交易对移除：现货机器人、杠杆仓位与 USDP 抵押截止时间","ja":"Binance 9月11日ペア削除：現物ボット、マージンポジション、担保期限","ko":"Binance 9월 11일 거래쌍 제거: 현물 봇, 마진 포지션과 담보 기한","tr":"Binance 11 Eylül parite kaldırmaları: Spot botlar, marjin pozisyonları ve teminat tarihleri","es":"Eliminaciones de pares de Binance del 11 de septiembre: bots spot, margen y plazos de garantía","pt-BR":"Remoções de pares da Binance em 11 de setembro: bots spot, margem e prazos de colateral","fr":"Suppressions de paires Binance du 11 septembre : bots spot, positions sur marge et garanties","de":"Binance-Paarentfernungen am 11. September: Spot-Bots, Margin-Positionen und Sicherheiten","ar":"إزالة أزواج Binance في 11 سبتمبر: روبوتات السبوت ومراكز الهامش ومواعيد الضمان","ru":"Удаление пар Binance 11 сентября: спотовые боты, маржинальные позиции и сроки обеспечения","id":"Penghapusan pasangan Binance 11 September: bot spot, posisi margin, dan batas jaminan","vi":"Binance gỡ cặp ngày 11 tháng 9: bot spot, vị thế margin và hạn tài sản thế chấp","it":"Rimozioni di coppie Binance dell’11 settembre: bot spot, posizioni margin e scadenze del collaterale"},"summary":{"en":"Binance will remove OPEN/FDUSD, SAGA/FDUSD and VELODROME/USDC spot pairs and terminate affected Spot Trading Bots at 2026-09-11 03:00 UTC.","zh-Hans":"Binance 在 2026-09-08 发布了两条和 9 月 11 日有关的公告，但它们影响的用户不完全一样。第一条是现货交易对移除：OPEN/FDUSD、SAGA/FDUSD、VELODROME/USDC 会在 2026-09-11 03:00 UTC 停止交易；如果用户在这些交易对上使用 Spot Trading Bots，相关机器人服务也会在同一时间终止。第二条是杠杆交易对和抵押资产调整：Binance Margin 会在 2026-09-11 06:00 UTC 移除多组 USDC 杠杆交易对，并移除 USDP 作为 Cross Margin 和 Portfolio Margin 抵押资产。","ja":"現物ペア削除、現物取引ボット終了、マージン上場廃止、USDP担保削除に関する公式通知を整理します。","ko":"9월 11일 현물 거래쌍 제거, 현물 봇 종료, 마진 상장폐지와 USDP 담보 제거에 대한 공식 공지를 정리합니다.","tr":"11 Eylül spot parite kaldırmalarını, Spot Trading Bot sonlandırmasını, marjin delist işlemlerini ve USDP teminat kaldırılmasını özetler.","es":"Resumen del aviso oficial de Binance sobre eliminaciones spot, cierre de bots de trading, bajas de margen y retirada de USDP como garantía.","pt-BR":"Resumo do aviso oficial da Binance sobre remoções de pares spot, encerramento de bots, delistagens de margem e retirada do USDP como colateral.","fr":"Résumé de l’avis officiel de Binance sur les suppressions spot, l’arrêt des bots, les retraits de marge et la suppression du collatéral USDP.","de":"Zusammenfassung der offiziellen Binance-Mitteilung zu Spot-Paarentfernungen, dem Ende von Spot-Bots, Margin-Delistings und dem Wegfall von USDP als Sicherheit.","ar":"ملخص لإشعار Binance الرسمي حول إزالة أزواج السبوت وإنهاء روبوتات التداول وإزالة أزواج الهامش وUSDP كضمان.","ru":"Разбор официального уведомления Binance об удалении спотовых пар, прекращении ботов, делистинге маржи и удалении USDP из обеспечения.","id":"Ringkasan pengumuman resmi Binance tentang penghapusan pasangan spot, penghentian bot, delisting margin, dan penghapusan USDP sebagai jaminan.","vi":"Tóm tắt thông báo chính thức của Binance về gỡ cặp spot, dừng bot, delist margin và loại USDP khỏi tài sản thế chấp.","it":"Sintesi dell’avviso ufficiale Binance su rimozione di coppie spot, stop dei bot, delisting margin e rimozione di USDP come collaterale."},"claims":[{"id":"c1","text":"Binance will remove and cease trading on OPEN/FDUSD, SAGA/FDUSD and VELODROME/USDC spot trading pairs at 2026-09-11 03:00 UTC.","sourceIds":["binance-spot-pair-removal-20260911"],"risk":"medium"},{"id":"c2","text":"Binance states that spot pair removal does not affect the availability of the underlying tokens on Binance Spot.","sourceIds":["binance-spot-pair-removal-20260911"],"risk":"medium"},{"id":"c3","text":"Binance will terminate Spot Trading Bots services for the affected spot trading pairs at 2026-09-11 03:00 UTC where applicable.","sourceIds":["binance-spot-pair-removal-20260911"],"risk":"medium"},{"id":"c4","text":"Binance Margin will delist Cross Margin pairs API3/USDC, COOKIE/USDC, PROVE/USDC, QNT/USDC, SHELL/USDC and TLM/USDC at 2026-09-11 06:00 UTC.","sourceIds":["binance-margin-pair-collateral-removal-20260911"],"risk":"high"},{"id":"c5","text":"Binance Margin will delist Isolated Margin pairs COOKIE/USDC, PROVE/USDC, SHELL/USDC and TLM/USDC at 2026-09-11 06:00 UTC.","sourceIds":["binance-margin-pair-collateral-removal-20260911"],"risk":"high"},{"id":"c6","text":"Binance says isolated borrowing for affected isolated margin pairs will be suspended at 2026-09-09 06:00 UTC.","sourceIds":["binance-margin-pair-collateral-removal-20260911"],"risk":"high"},{"id":"c7","text":"At 2026-09-11 06:00 UTC, Binance says affected margin positions will be closed, automatic settlement will occur, pending orders will be canceled and the pairs will be removed from Margin.","sourceIds":["binance-margin-pair-collateral-removal-20260911"],"risk":"high"},{"id":"c8","text":"Binance says the margin delisting and collateral removal process may take approximately three hours.","sourceIds":["binance-margin-pair-collateral-removal-20260911"],"risk":"medium"},{"id":"c9","text":"Binance will remove USDP as Cross Margin and Portfolio Margin collateral at 2026-09-11 06:00 UTC.","sourceIds":["binance-margin-pair-collateral-removal-20260911"],"risk":"high"},{"id":"c10","text":"The notices include regional availability caveats and state that the original English version should control if translated versions differ.","sourceIds":["binance-spot-pair-removal-20260911","binance-margin-pair-collateral-removal-20260911"],"risk":"low"}],"relatedVenues":["binance"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"how-to-read-crypto-proof-of-reserves","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-08T11:45:41.000Z","updatedAt":"2026-09-08T11:45:41Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"How to Read Crypto Exchange Proof of Reserves Without Mistaking It for a Full Audit","zh-Hans":"如何阅读加密交易所储备证明：别把 PoR 当成完整审计","ja":"暗号資産取引所のProof of Reservesを読む方法：完全監査と混同しないために","ko":"암호화폐 거래소 Proof of Reserves 읽는 법: 완전한 감사와 혼동하지 않기","tr":"Kripto borsalarının Proof of Reserves raporu nasıl okunur? Tam denetim sanmayın","es":"Cómo leer la prueba de reservas de un exchange sin confundirla con una auditoría completa","pt-BR":"Como ler a prova de reservas de uma exchange sem confundi-la com uma auditoria completa","fr":"Lire une preuve de réserves sans la confondre avec un audit complet","de":"Proof of Reserves richtig lesen, ohne sie mit einer vollständigen Prüfung zu verwechseln","ar":"كيف تقرأ إثبات الاحتياطيات من دون اعتباره تدقيقاً كاملاً","ru":"Как читать Proof of Reserves криптобиржи и не путать его с полным аудитом","id":"Cara membaca Proof of Reserves tanpa menganggapnya audit penuh","vi":"Cách đọc Proof of Reserves mà không nhầm với kiểm toán đầy đủ","it":"Come leggere la Proof of Reserves senza scambiarla per un audit completo"},"summary":{"en":"A crypto exchange Proof of Reserves page can help users check whether selected customer balances were included in a point-in-time reserve process and whether disclosed wallets appear to hold enough on-chain assets for covered coins.","zh-Hans":"加密交易所的 Proof of Reserves，通常被翻译成“储备证明”或 PoR。它有价值，但它回答的问题比很多人想象得窄。一个做得比较完整的 PoR 页面，可以帮助用户检查几个点：某些客户余额是否被纳入某次快照，公开钱包里是否能看到覆盖特定币种的链上资产，用户自己的账户是否出现在 Merkle tree 中，以及某些零知识证明约束是否通过。","ja":"資産スナップショット、負債、Merkle inclusion、zk証明、ウォレット所有権、時間差、監査の限界を解説します。","ko":"자산 스냅샷, 부채, Merkle 포함 증명, zk 증명, 지갑 소유권, 시점 차이와 감사의 한계를 설명합니다.","tr":"Varlık anlık görüntüsü, yükümlülükler, Merkle dahil oluşu, zk kanıtları, cüzdan sahipliği, zaman farkları ve denetim sınırlarını açıklar.","es":"Guía basada en fuentes sobre instantáneas de activos, pasivos, inclusión Merkle, pruebas zk, control de wallets, desfases temporales y límites de auditoría.","pt-BR":"Guia baseada em fontes sobre snapshots de ativos, passivos, inclusão Merkle, provas zk, controle de carteiras, defasagens temporais e limites de auditoria.","fr":"Guide sourcé sur les instantanés d’actifs, les passifs, l’inclusion Merkle, les preuves zk, le contrôle des wallets, les décalages temporels et les limites de l’audit.","de":"Quellenbasierter Leitfaden zu Asset-Snapshots, Verbindlichkeiten, Merkle-Nachweisen, zk-Beweisen, Wallet-Kontrolle, Zeitlücken und Prüfungsgrenzen.","ar":"دليل قائم على المصادر يشرح لقطات الأصول والالتزامات وإثبات Merkle وأدلة zk وملكية المحافظ وفجوات التوقيت وحدود التدقيق.","ru":"Разбор снимков активов, обязательств, включения Merkle, zk-доказательств, владения кошельками, временных разрывов и ограничений аудита.","id":"Panduan berbasis sumber tentang snapshot aset, kewajiban, inklusi Merkle, bukti zk, kepemilikan wallet, jeda waktu, dan batas audit.","vi":"Hướng dẫn dựa trên nguồn về ảnh chụp tài sản, nợ phải trả, Merkle inclusion, bằng chứng zk, quyền sở hữu ví, độ trễ thời gian và giới hạn kiểm toán.","it":"Guida basata su fonti a snapshot degli asset, passività, inclusione Merkle, prove zk, proprietà dei wallet, ritardi temporali e limiti dell’audit."},"claims":[{"id":"c1","text":"Binance describes its Proof of Reserves as evidence that assets held in custody for users cover user assets 1:1, including reserves, and says users can verify inclusion in aggregate net account balances through a Merkle tree and zk-SNARK mechanism.","sourceIds":["binance-por-page"],"risk":"medium"},{"id":"c2","text":"Binance's verification FAQ says monthly PoR snapshots are taken on the first day of each month at 00:00 UTC and released by the seventh day, and it warns the report is a snapshot, not real-time assets.","sourceIds":["binance-verify-faq"],"risk":"medium"},{"id":"c3","text":"Binance's FAQ lists verifier tool v1.2.1 for the 2026-08-01 to current PoR verification cycle and describes user configuration fields such as account index, account ID hash, total equity, total debt, total collateral, assets, root and proof.","sourceIds":["binance-verify-faq"],"risk":"medium"},{"id":"c4","text":"OKX United States' public PoR page claims its 46th Proof of Reserves covers August 2026, displays $22.96B in primary assets, lists 22 coins, and describes zk-STARK upgrade and public on-chain wallet ownership verification.","sourceIds":["okx-por-page"],"risk":"high"},{"id":"c5","text":"OKX's page separates account assets and wallet assets and includes exchange-wallet and third-party-custody components; the third-party custody caveat means page totals should be read as OKX page claims, not independently audited balances by this article.","sourceIds":["okx-por-page"],"risk":"high"},{"id":"c6","text":"The SEC Chief Accountant's 2023 statement warns that crypto non-audit assurance work should not be marketed as equivalent to financial-statement audits because such suggestions can mislead investors.","sourceIds":["sec-munter-assurance"],"risk":"high"},{"id":"c7","text":"The PCAOB investor advisory says PoR reports are inherently limited, are not audits, may not address liabilities, rights and obligations, borrowed assets, internal controls, governance or future asset availability.","sourceIds":["pcaob-por-advisory"],"risk":"high"},{"id":"c8","text":"A useful PoR review should separate asset snapshot, customer balance or liability snapshot, inclusion proof, zero-knowledge constraints, wallet ownership attestation, timing, scope and independence before drawing any conclusion.","sourceIds":["binance-por-page","binance-verify-faq","okx-por-page","sec-munter-assurance","pcaob-por-advisory"],"risk":"medium"},{"id":"c9","text":"This article does not prove Binance, OKX or any exchange is solvent, fully audited, risk-free, regulated in every jurisdiction, or able to satisfy all future withdrawals.","sourceIds":["sec-munter-assurance","pcaob-por-advisory"],"risk":"low"}],"relatedVenues":["binance","okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"verify-official-crypto-exchange-website","status":"PUBLISHED","category":"guide","categoryName":{"en":"Guides","zh-Hans":"教程","zh-Hant":"教學"},"publishedAt":"2026-09-07T23:48:00.000Z","updatedAt":"2026-09-07T23:48:00Z","readTime":"10 min","author":"NexuAlpha Research Desk","title":{"en":"How to Verify the Official Crypto Exchange Website Before Clicking, Signing In or Depositing","zh-Hans":"点击、登录或入金前，如何核验加密交易所官方网站","ja":"クリック、ログイン、入金の前に公式暗号資産取引所サイトを確認する方法","ko":"클릭·로그인·입금 전에 공식 암호화폐 거래소 사이트 확인하기","tr":"Tıklamadan, giriş yapmadan veya para yatırmadan önce resmi kripto borsası sitesi nasıl doğrulanır?","es":"Cómo verificar el sitio oficial de un exchange antes de hacer clic, iniciar sesión o depositar","pt-BR":"Como verificar o site oficial de uma exchange antes de clicar, entrar ou depositar","fr":"Vérifier le site officiel d’un exchange avant de cliquer, se connecter ou déposer","de":"Die offizielle Exchange-Website prüfen, bevor Sie klicken, sich anmelden oder einzahlen","ar":"كيفية التحقق من موقع منصة العملات الرسمي قبل النقر أو تسجيل الدخول أو الإيداع","ru":"Как проверить официальный сайт криптобиржи до клика, входа или депозита","id":"Cara memverifikasi situs resmi bursa kripto sebelum klik, login, atau deposit","vi":"Cách xác minh website sàn crypto chính thức trước khi nhấp, đăng nhập hoặc nạp tiền","it":"Come verificare il sito ufficiale di un exchange prima di cliccare, accedere o depositare"},"summary":{"en":"Verify an exchange website by using a saved or typed official route, reading the registrable domain, requiring HTTPS and cross-checking urgent prompts.","zh-Hans":"在点击链接、登录账户、安装 App 或入金之前，最重要的不是看页面漂不漂亮，而是确认你进入的是交易所真正控制的官方路径。更可靠的做法是：手动输入已经核验过的域名、使用保存过的书签、从官方 App 内进入帮助中心，或从交易所官方文档交叉核对域名与支持渠道。搜索广告、邮件发件人显示名、网上搜到的客服电话、浏览器地址栏里的小锁，以及一个做得很像真的登录页，都不能单独证明这个网站是真的。","ja":"リンク、ログイン、アプリのインストール、入金の前に公式ドメインを確認する実用的なチェックリストです。","ko":"링크를 누르거나 로그인·앱 설치·입금하기 전에 공식 도메인을 확인하는 실용적인 체크리스트입니다.","tr":"Bağlantı, giriş, uygulama kurulumu veya para yatırma öncesi resmi alan adını doğrulamak için kaynaklı kontrol listesi.","es":"Lista práctica y basada en fuentes para verificar el dominio oficial antes de abrir enlaces, iniciar sesión, instalar apps o depositar fondos.","pt-BR":"Checklist prático e baseado em fontes para verificar o domínio oficial antes de abrir links, fazer login, instalar apps ou depositar fundos.","fr":"Checklist pratique et sourcée pour vérifier le domaine officiel avant d’ouvrir un lien, de se connecter, d’installer une application ou de déposer des fonds.","de":"Praktische, quellenbasierte Checkliste zur Prüfung der offiziellen Domain vor Links, Login, App-Installation oder Einzahlungen.","ar":"قائمة تحقق عملية وموثقة للتحقق من النطاق الرسمي قبل فتح الروابط أو تسجيل الدخول أو تثبيت التطبيقات أو إيداع الأموال.","ru":"Практический чек-лист на основе источников для проверки официального домена перед ссылкой, входом, установкой приложения или депозитом.","id":"Checklist praktis berbasis sumber untuk memverifikasi domain resmi sebelum membuka tautan, login, memasang aplikasi, atau melakukan deposit.","vi":"Checklist thực tế dựa trên nguồn để xác minh tên miền chính thức trước khi mở liên kết, đăng nhập, cài ứng dụng hoặc nạp tiền.","it":"Checklist pratica e basata su fonti per verificare il dominio ufficiale prima di aprire link, accedere, installare app o depositare fondi."},"claims":[{"id":"c1","text":"CISA defines phishing as social engineering that uses email or malicious websites to solicit personal information while posing as a trustworthy organization.","sourceIds":["cisa-social-engineering"],"risk":"low"},{"id":"c2","text":"CISA identifies spoofed hyperlinks and lookalike websites as common phishing indicators, including URLs with spelling variations or different domains.","sourceIds":["cisa-social-engineering","cisa-recognize-report"],"risk":"low"},{"id":"c3","text":"HTTPS and a lock icon are necessary connection checks, but they do not alone prove that a crypto exchange domain is the real exchange.","sourceIds":["cisa-social-engineering","binance-url-spoof"],"risk":"medium"},{"id":"c4","text":"The FBI warns that fake cryptocurrency investment platforms can be promoted through social media, online advertisements and app-store searches.","sourceIds":["fbi-crypto-investment-fraud"],"risk":"medium"},{"id":"c5","text":"The FBI's 2025 Internet Crime Report press release states that cyber-enabled crimes caused nearly $21 billion in reported losses, and cryptocurrency complaints totaled more than $11 billion.","sourceIds":["fbi-2025-internet-crime-report"],"risk":"medium"},{"id":"c6","text":"Coinbase tells users not to rely on sender display names alone and to go directly to Coinbase instead of clicking email links when concerned about account activity.","sourceIds":["coinbase-email"],"risk":"medium"},{"id":"c7","text":"Coinbase states that its service agents will not ask for passwords, two-step verification codes, seed phrases, remote device access or transfers to new addresses.","sourceIds":["coinbase-phishing"],"risk":"medium"},{"id":"c8","text":"Binance warns that phishing sites can be encountered through search results, browser extensions, third-party applications and emails.","sourceIds":["binance-url-spoof"],"risk":"medium"},{"id":"c9","text":"Binance recommends Binance Verify, 2FA, anti-phishing codes, updated browsers and trusted download sources as phishing mitigations.","sourceIds":["binance-prevent-phishing","binance-account-security"],"risk":"medium"},{"id":"c10","text":"Kraken recommends bookmarking its sign-in page, enabling passkeys and using official apps, and warns that fake apps and lookalike search-result flows are phishing risks.","sourceIds":["kraken-secure-account","kraken-report-phishing"],"risk":"medium"},{"id":"c11","text":"Kraken explains that FIDO2 hardware security keys verify the legitimate website before authenticating and can prevent entry of valid codes on a site imitating Kraken.","sourceIds":["kraken-security-key"],"risk":"medium"},{"id":"c12","text":"If a user believes a crypto investment fraud or phishing incident occurred, the FBI and IC3 emphasize reporting with transaction details, domains, apps, contact identifiers and timelines where possible.","sourceIds":["fbi-crypto-investment-fraud","ic3-home","kraken-report-phishing"],"risk":"low"}],"relatedVenues":["coinbase","binance","kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"tokenized-treasuries-structure-access-risks","status":"PUBLISHED","category":"rwa","categoryName":{"en":"RWA & Tokenization","zh-Hans":"代币化资产","zh-Hant":"代幣化資產"},"publishedAt":"2026-09-07T23:42:33.000Z","updatedAt":"2026-09-22T01:35:23.602Z","readTime":"7 min","author":"NexuAlpha Research Desk","title":{"en":"Tokenized Treasuries: BUIDL, BENJI, Ownership, Redemption and Access Risks","zh-Hans":"代币化美债：产品结构、准入方式与必须核验的风险","tr":"Tokenize ABD Hazine tahvilleri nedir? BUIDL, BENJI ve gerçekte neye sahip olduğunuz (2026)","id":"Apa Itu Surat Utang AS yang Ditokenisasi? BUIDL, BENJI, dan Apa yang Sebenarnya Anda Miliki (2026)","vi":"Trái phiếu Kho bạc Mỹ token hóa là gì? BUIDL, BENJI và bạn thực sự nắm giữ thứ gì (2026)"},"summary":{"en":"Understand what a tokenized Treasury represents: compare BUIDL and BENJI ownership records, eligibility, fees, wallet controls and redemption conditions.","zh-Hans":"代币化美债是一种以数字化或链上记录方式呈现的美债相关敞口，但代币这个标签本身不等于直接持有美国短期国债。它可能是直接政府证券记录、链上表示的受监管基金份额、私募基金权益、中介权益，也可能是带储备安排的产品。","tr":"Tokenize Hazine ürünü sizi doğrudan ABD hazine bonosu sahibi yapmaz; fon payı, özel fon payı veya aracı alacağı olabilir. BUIDL ve BENJI'yi ihraççı, kayıt, itfa ve transfer kontrolleriyle karşılaştırın.","id":"Token Treasury AS tidak otomatis berarti Anda memiliki surat utang secara langsung; bisa berupa unit reksa dana atau klaim. Bandingkan BUIDL dan BENJI dari penerbit, pencatatan, penebusan, dan pengalihan.","vi":"Token Kho bạc Mỹ không có nghĩa bạn sở hữu trực tiếp tín phiếu; đó có thể là chứng chỉ quỹ hoặc khoản phải đòi. So sánh BUIDL và BENJI qua tổ chức phát hành, sổ sở hữu, mua lại và chuyển nhượng."},"availableLocales":["en","zh-Hans","tr","id","vi"],"claims":[{"id":"c1","text":"Direct ownership of a marketable U.S. Treasury is acquired through TreasuryDirect or a bank, broker, or dealer at auction, with Treasury bills, notes, bonds, TIPS, and FRNs identified by CUSIP and minimum bids of $100.","sourceIds":["treasurydirect-buying","treasurydirect-bills","treasurydirect-notes"],"risk":"low"},{"id":"c2","text":"Tokenized Treasury products are not a single legal structure; as described in an SEC staff statement and FINRA investor material, tokenized securities can be issuer-sponsored records or third-party/intermediary structures, and tokenization does not change the underlying asset's legal character.","sourceIds":["sec-tokenized-securities-2026","sec-peirce-tokenization-2025","finra-crypto-assets"],"risk":"high"},{"id":"c3","text":"BUIDL is associated with BlackRock USD Institutional Digital Liquidity Fund Ltd.; SEC filings identify the issuer and describe Securitize services around investor onboarding, transfer-agent/registrar functions, token issuances and burns, redemptions, distributions, smart-contract maintenance, and shareholder records.","sourceIds":["blackrock-buidl-addresses","sec-buidl-form-d","sec-buidl-securitize-agreement","securitize-buidl-page"],"risk":"high"},{"id":"c4","text":"Franklin's BENJI represents shares of the Franklin OnChain U.S. Government Money Fund; its prospectus says the transfer agent maintains official share ownership through a blockchain-integrated, permissioned recordkeeping system and can correct unauthorized transactions or limit transferability.","sourceIds":["franklin-fobxx-page","franklin-prospectus-9001-psum","franklin-benji-platform","franklin-benji-five-years"],"risk":"high"},{"id":"c5","text":"Tokenized Treasury fund yield generally comes from fund holdings such as government securities, cash, and repurchase agreements, minus fund and service economics; it is not the same as the holder directly receiving coupon or bill-discount income from a Treasury security.","sourceIds":["franklin-prospectus-9001-psum","franklin-fobxx-page","blackrock-liquidity-disclosures"],"risk":"high"},{"id":"c6","text":"Important risk checks include eligibility and jurisdiction, fund documents, transfer-agent controls, redemption windows, liquidity, smart-contract and key-management risk, cyber risk, counterparty/service-provider risk, and the possibility that a stable $1.00 share price is not guaranteed.","sourceIds":["franklin-prospectus-9001-psum","franklin-fobxx-page","blackrock-liquidity-disclosures","finra-crypto-assets"],"risk":"high"},{"id":"c7","text":"Tokenized Treasuries should be distinguished from stablecoins and crypto yield products: stablecoins aim to track a reference price, while tokenized securities/funds depend on securities-law documentation, fund governance, and transfer-agent or intermediary records.","sourceIds":["finra-crypto-assets","sec-tokenized-securities-2026","franklin-prospectus-9001-psum"],"risk":"medium"}],"relatedVenues":["coinbase","kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"okx-usd-to-usdc-spot-pair-migration","status":"PUBLISHED","category":"exchange-update","categoryName":{"en":"Exchange Updates","zh-Hans":"交易所动态","zh-Hant":"交易所動態"},"publishedAt":"2026-09-07T23:41:35.000Z","updatedAt":"2026-10-13T05:00:00.000Z","readTime":"9 min","readTimeByLocale":{"en":"9 min","zh-Hans":"11 min"},"author":"NexuAlpha Research Desk","title":{"en":"OKX USD to USDC Spot Pairs (2026): Orders, Bots, API Fixes","zh-Hans":"OKX 美元现货交易对迁移到 USDC：时间表、订单、机器人与 API 影响"},"summary":{"en":"OKX moved affected Crypto-USD spot pairs to Crypto-USDC in September 2026. See which orders, bots, API instId and tradeQuoteCcy settings to update.","zh-Hans":"一份基于来源的 OKX USD 迁移至 USDC 操作清单，覆盖适用范围、时间表、下架影响、挂单、保证金仓位、机器人、策略订单、API instId、tradeQuoteCcy 和 USDC order book 启用。"},"availableLocales":["en","zh-Hans"],"claims":[{"id":"c1","text":"OKX United States announced a migration in which affected Crypto-USD spot pairs move to corresponding Crypto-USDC instruments, with new replacement pairs available from 8:00 UTC on September 23, 2026.","sourceIds":["okx-us-migration","okx-us-changes"],"risk":"medium"},{"id":"c2","text":"At 8:00 UTC on September 30, 2026, affected Crypto-USD spot pairs except USDT-USD are scheduled to be delisted; affected open orders are automatically canceled and affected margin positions may be closed under the regional checklist.","sourceIds":["okx-us-migration","okx-us-changes"],"risk":"high"},{"id":"c3","text":"Trading bots using affected USD pairs are scheduled to close during the hour before delisting, and OKX tells users to stop and recreate bots on replacement USDC pairs before the deadline if needed.","sourceIds":["okx-us-migration","okx-us-changes"],"risk":"high"},{"id":"c4","text":"API clients must migrate from affected Crypto-USD instrument IDs to corresponding Crypto-USDC instrument IDs; OKX says old instrument IDs will not be mapped and may fail or return no data after delisting.","sourceIds":["okx-api-changelog"],"risk":"high"},{"id":"c5","text":"Changing instId from Crypto-USD to Crypto-USDC also changes the default quote currency behavior; users who want to keep trading with USD must explicitly set tradeQuoteCcy to USD when supported.","sourceIds":["okx-us-migration","okx-api-changelog"],"risk":"high"},{"id":"c6","text":"Before trading a Crypto-USDC instrument, API clients may need to call POST /api/v5/account/activate-feature with feature=1 to activate USDC order book trading unless the account already trades USDC instruments.","sourceIds":["okx-api-changelog"],"risk":"medium"},{"id":"c7","text":"OKX describes the Unified USD Orderbook as available in certain jurisdictions and supporting USD, USDC and other selected dollar-pegged stablecoins; the regional announcement says users should log in to check applicability.","sourceIds":["okx-unified-usd-orderbook","okx-us-migration","okx-us-changes"],"risk":"high"},{"id":"c8","text":"Circle describes USDC as fully backed by highly liquid cash and cash-equivalent assets and redeemable 1:1 for U.S. dollars, subject to Circle terms, eligibility and third-party-platform price risk.","sourceIds":["circle-transparency","circle-usdc-terms"],"risk":"medium"},{"id":"c9","text":"This article does not verify user-specific eligibility, tax treatment, OKX account configuration, live pair availability, current balances, or whether a particular user is inside the affected cohort.","sourceIds":["okx-us-migration","okx-us-changes","circle-usdc-terms"],"risk":"low"}],"relatedVenues":["okx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"hyperliquid-vs-dydx","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-07T11:43:01.000Z","updatedAt":"2026-10-13T05:00:00.000Z","readTime":"7 min","readTimeByLocale":{"en":"7 min","zh-Hans":"7 min","tr":"6 min","id":"7 min","vi":"9 min"},"author":"NexuAlpha Research Desk","title":{"en":"Hyperliquid vs dYdX (2026): Fees, Funding and Liquidations","zh-Hans":"Hyperliquid vs dYdX：永续合约 DEX 的费用、资金费率、保证金与强平机制对比","tr":"Hyperliquid mi dYdX mi? Komisyon, fonlama, teminat ve likidasyon farkları (2026)","id":"Hyperliquid vs dYdX: Beda Biaya, Funding, Margin, dan Likuidasi di Dua Perp DEX (2026)","vi":"Hyperliquid hay dYdX? So sánh phí, funding, ký quỹ và thanh lý trên hai sàn perp DEX (2026)"},"summary":{"en":"Hyperliquid prices fees on 14-day volume and pays funding hourly; dYdX uses 30-day taker volume. Compare fees, funding, margin and liquidation.","zh-Hans":"Hyperliquid 和 dYdX 都是以永续合约为核心的 DEX 交易场景，但来源支持的决策字段不同：Hyperliquid 使用滚动 14 天费率等级，并记录 HyperCore 保证金和先通过订单簿处理强平的机制；dYdX 使用过去 30 天 Taker 成交量计算逻辑，并记录流动性等级、预言机和协议生成的强平机制。","tr":"Hyperliquid komisyon kademesini 14 günlük hacme göre belirler, fonlamayı her saat öder ve likidasyonda önce emir defterini kullanır; dYdX ise 30 günlük taker hacmine, yönetişimle değişen parametrelere ve sigorta fonuna dayanır.","id":"Hyperliquid menentukan tingkat biaya dari volume 14 hari, membayar funding setiap jam, dan melikuidasi lewat order book lebih dulu; dYdX memakai volume taker 30 hari, parameter tata kelola, dan dana asuransi.","vi":"Hyperliquid xếp bậc phí theo khối lượng 14 ngày, trả funding mỗi giờ và thanh lý qua sổ lệnh trước; dYdX tính phí taker theo 30 ngày, tham số do cộng đồng quản trị và lời lỗ thanh lý đi qua quỹ bảo hiểm."},"availableLocales":["en","zh-Hans","tr","id","vi"],"claims":[{"id":"c1","text":"Hyperliquid uses a rolling 14-day weighted volume system for fee tiers, with separate perp and spot schedules and additional staking-tier discounts.","sourceIds":["hl-fees"],"risk":"medium"},{"id":"c2","text":"dYdX describes a maker-taker model in which taker fees are based on trailing 30-day USD volume across perpetual order books, and the current schedule is surfaced through the dYdX interface or linked docs.","sourceIds":["dydx-fees"],"risk":"medium"},{"id":"c3","text":"Hyperliquid funding is paid hourly, uses a premium component against the spot oracle price, has a fixed interest component described in the docs, and is capped at 4% per hour.","sourceIds":["hl-funding"],"risk":"medium"},{"id":"c4","text":"dYdX funding in the default v4 software is calculated from premium samples and is subject to governance-controlled parameters.","sourceIds":["dydx-funding"],"risk":"medium"},{"id":"c5","text":"Hyperliquid liquidations occur when equity falls below maintenance margin, first route liquidation attempts through market orders on the book, and may use the liquidator vault as a backstop.","sourceIds":["hl-liquidations"],"risk":"high"},{"id":"c6","text":"dYdX Chain liquidations use protocol-generated matches and an insurance-fund mechanism under default v4 software assumptions; official documentation warns that up to the entire remaining account value may be taken as a liquidation penalty.","sourceIds":["dydx-liquidations"],"risk":"high"},{"id":"c7","text":"Hyperliquid oracle prices are published by validators every three seconds and are used for funding, mark price, margining, liquidations, and TP/SL triggers.","sourceIds":["hl-oracle"],"risk":"medium"},{"id":"c8","text":"dYdX oracle prices are validator-determined aggregated prices used for collateralization, liquidation checks, and triggerable order types.","sourceIds":["dydx-oracle"],"risk":"medium"},{"id":"c9","text":"dYdX liquidity tiers group markets into standardized risk parameters and can affect initial margin fraction, maintenance margin fraction, impact notional, and safety-tier handling.","sourceIds":["dydx-liquidity"],"risk":"medium"},{"id":"c10","text":"The comparison does not verify overall liquidity, volume leadership, security superiority, or user eligibility by jurisdiction; those remain outside this source set.","sourceIds":["hl-fees","hl-liquidations","dydx-fees","dydx-liquidations"],"risk":"low"}],"relatedVenues":["hyperliquid","dydx"],"sourceStatus":"PUBLIC_SOURCE_MAPPED"},{"slug":"tokenized-stocks-vs-stock-perpetuals","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-07T11:42:15.000Z","updatedAt":"2026-09-07T11:42:15Z","readTime":"11 min","author":"NexuAlpha Research Desk","title":{"en":"Tokenized Stocks vs Stock Perpetuals: What Do You Actually Own?","zh-Hans":"代币化股票与股票永续合约：你到底拥有什么？","ja":"トークン化株式と株式Perpetual：実際に何を保有するのか","ko":"토큰화 주식과 주식 무기한 선물: 실제로 무엇을 보유하는가","tr":"Tokenleştirilmiş hisseler ve hisse perpetual’ları: Gerçekte neye sahipsiniz?","es":"Acciones tokenizadas frente a perpetuos de acciones: ¿qué posees realmente?","pt-BR":"Ações tokenizadas vs. perpétuos de ações: o que você realmente possui?","fr":"Actions tokenisées ou perpetuals sur actions : que possédez-vous réellement ?","de":"Tokenisierte Aktien vs. Aktien-Perpetuals: Was besitzen Sie tatsächlich?","ar":"الأسهم المرمّزة مقابل العقود الدائمة للأسهم: ماذا تملك فعلياً؟","ru":"Токенизированные акции и бессрочные фьючерсы: чем вы владеете на самом деле?","id":"Saham bertoken vs perpetual saham: apa yang sebenarnya Anda miliki?","vi":"Cổ phiếu token hóa và perpetual cổ phiếu: bạn thực sự sở hữu gì?","it":"Azioni tokenizzate vs perpetual sulle azioni: cosa possiedi davvero?"},"summary":{"en":"Tokenized stocks usually aim to provide economic exposure to a real equity or ETF through a blockchain token, but the holder's legal rights depend on the issuer and product terms.","zh-Hans":"代币化股票和股票永续合约经常被放在同一个话题里，因为它们都可能让用户通过加密市场基础设施获得股票价格敞口。但它们不是同一种东西。代币化股票产品通常试图用链上代币承载某只股票或 ETF 的经济敞口；股票永续合约则是衍生品仓位，它参考某个市场价格，通过保证金、资金费率和强平机制运行，并不会让交易者变成股东。","ja":"トークン化株式、xStocks、株式Perpetualで、保有権、移転しない権利、レバレッジと清算リスクを整理します。","ko":"토큰화 주식, xStocks와 주식 무기한 선물에서 보유권, 이전되지 않는 권리, 레버리지와 청산 위험을 설명합니다.","tr":"Tokenleştirilmiş hisseler, xStocks ve hisse perpetual vadeli işlemlerinde sahiplik, devredilmeyen haklar, kaldıraç ve likidasyon risklerini açıklar.","es":"Guía basada en fuentes sobre acciones tokenizadas, xStocks y futuros perpetuos: propiedad, derechos que no se transfieren, apalancamiento y liquidación.","pt-BR":"Guia baseada em fontes sobre ações tokenizadas, xStocks e perpétuos: o que é possuído, quais direitos podem não passar e onde entram alavancagem e liquidação.","fr":"Guide sourcé sur actions tokenisées, xStocks et perpetuals : propriété, droits non transmis, levier et risque de liquidation.","de":"Quellenbasierter Leitfaden zu tokenisierten Aktien, xStocks und Aktien-Perpetuals: Eigentum, nicht übertragene Rechte, Hebel und Liquidation.","ar":"دليل قائم على المصادر حول الأسهم المرمّزة وxStocks والعقود الدائمة، وما ينتقل من حقوق وأين تظهر الرافعة ومخاطر التصفية.","ru":"Разбор токенизированных акций, xStocks и бессрочных фьючерсов: права собственности, непередаваемые права, плечо и риск ликвидации.","id":"Panduan berbasis sumber tentang saham bertoken, xStocks, dan perpetual: kepemilikan, hak yang mungkin tidak berpindah, leverage, dan risiko likuidasi.","vi":"Hướng dẫn dựa trên nguồn về cổ phiếu token hóa, xStocks và perpetual: quyền sở hữu, quyền không chuyển giao, đòn bẩy và rủi ro thanh lý.","it":"Guida basata su fonti ad azioni tokenizzate, xStocks e perpetual: proprietà, diritti non trasferiti, leva e rischio di liquidazione."},"claims":[{"id":"c1","text":"Kraken describes xStocks as tokenized representations of U.S. stocks and ETFs, with access limited by jurisdiction and product eligibility.","sourceIds":["kraken-xstocks","kraken-xstocks-start","kraken-xstocks-availability"],"risk":"medium"},{"id":"c2","text":"xStocks and similar tracker-style tokenized equity products should not be presented as ordinary share ownership; shareholder rights such as voting may not pass through.","sourceIds":["kraken-xstocks","xstocks-faq","backed-legal","sec-tokenized-securities"],"risk":"high"},{"id":"c3","text":"xStocks materials describe one-to-one economic exposure and collateralization, but the exact legal rights come from the issuer documentation and final terms, not the token label alone.","sourceIds":["xstocks-faq","backed-legal","kraken-xstocks-risk","sec-tokenized-securities"],"risk":"high"},{"id":"c4","text":"Perpetual futures are derivative contracts without a fixed expiry, and funding payments help anchor contract prices to the reference spot market.","sourceIds":["kraken-us-perps","cftc-perpetual-policy","federal-register-perps"],"risk":"medium"},{"id":"c5","text":"Perpetual exposure can carry leverage, funding-cost, maintenance-margin, and liquidation risk that does not exist in the same form for unlevered tokenized spot exposure.","sourceIds":["kraken-us-perps","cftc-perpetual-policy"],"risk":"high"},{"id":"c6","text":"Tokenized stocks, stock perpetuals, and traditional brokerage shares answer different user jobs: ownership-rights checking, transferable exposure, short-term hedging, and leveraged trading must be evaluated separately.","sourceIds":["kraken-xstocks-risk","xstocks-faq","sec-tokenized-securities","kraken-us-perps"],"risk":"medium"}],"relatedVenues":["kraken"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]},{"slug":"cex-vs-dex-vs-perp-dex","status":"PUBLISHED","category":"comparison","categoryName":{"en":"Comparisons","zh-Hans":"平台对比","zh-Hant":"平台對比"},"publishedAt":"2026-09-07T11:41:13.000Z","updatedAt":"2026-09-07T11:41:13Z","readTime":"12 min","author":"NexuAlpha Research Desk","title":{"en":"CEX vs DEX vs Perp DEX: Which Crypto Trading Venue Fits Which Job?","zh-Hans":"CEX、DEX 和 Perp DEX 怎么选：一篇按任务拆解的交易场所指南","ja":"CEX・DEX・Perp DEX：どの取引場所がどの仕事に向くか","ko":"CEX·DEX·Perp DEX: 어떤 거래 장소가 어떤 목적에 맞는가","tr":"CEX, DEX ve Perp DEX: Hangi işlem mekanı hangi işe uygun?","es":"CEX, DEX y Perp DEX: qué mercado encaja con cada objetivo","pt-BR":"CEX, DEX e Perp DEX: qual ambiente de negociação serve para cada objetivo?","fr":"CEX, DEX ou Perp DEX : quelle place de marché convient à quel usage ?","de":"CEX, DEX oder Perp DEX: Welche Handelsumgebung passt zu welchem Zweck?","ar":"CEX وDEX وPerp DEX: أي منصة تناسب أي هدف؟","ru":"CEX, DEX и Perp DEX: какая площадка подходит для какой задачи?","id":"CEX, DEX, dan Perp DEX: venue mana cocok untuk tujuan apa?","vi":"CEX, DEX hay Perp DEX: nền tảng nào phù hợp với mục đích nào?","it":"CEX, DEX o Perp DEX: quale ambiente è adatto a quale obiettivo?"},"summary":{"en":"A CEX is usually best for fiat onboarding, account recovery, and regulated account services; a spot DEX is best for self-custodial token swaps and onchain access; a Perp DEX is best reserved for experienced users who need long or short derivatives exposure and can manage leverage, collateral, funding, and liquidation risk.","zh-Hans":"如果你的主要任务是法币入金、账户服务、找回账户、使用相对熟悉的订单簿界面，CEX 通常更顺手。如果你的主要任务是自托管、链上结算、直接兑换某个链上资产，现货 DEX 更匹配。如果你的主要任务是做多、做空、对冲或使用杠杆，那属于 Perp DEX 的场景，但它不是普通买币工具，而是带有保证金、资金费率、抵押品和强平风险的衍生品工具。","ja":"カストディモデル、執行、レバレッジ、リスク、手数料と利用者適合性で比較する意思決定ガイドです。","ko":"수탁 모델, 체결, 레버리지, 위험, 수수료와 사용자 적합성을 비교하는 의사결정 가이드입니다.","tr":"Saklama modeli, yürütme, kaldıraç, risk, ücretler ve kullanıcı uyumunu karşılaştıran kaynaklı karar rehberi.","es":"Guía de decisión basada en fuentes que compara custodia, ejecución, apalancamiento, riesgo, comisiones y encaje del usuario.","pt-BR":"Guia de decisão baseada em fontes comparando custódia, execução, alavancagem, risco, taxas e adequação ao usuário.","fr":"Guide de décision sourcé comparant le modèle de conservation, l’exécution, le levier, le risque, les frais et l’adéquation utilisateur.","de":"Quellenbasierter Entscheidungsleitfaden zu Verwahrungsmodell, Ausführung, Hebel, Risiko, Gebühren und Nutzerprofil.","ar":"دليل قرار قائم على المصادر يقارن نموذج الحفظ والتنفيذ والرافعة والمخاطر والرسوم وملاءمة المستخدم.","ru":"Руководство по выбору на основе источников: хранение, исполнение, плечо, риск, комиссии и соответствие пользователю.","id":"Panduan keputusan berbasis sumber yang membandingkan model kustodi, eksekusi, leverage, risiko, biaya, dan kecocokan pengguna.","vi":"Hướng dẫn quyết định dựa trên nguồn, so sánh mô hình lưu ký, khớp lệnh, đòn bẩy, rủi ro, phí và mức độ phù hợp.","it":"Guida decisionale basata su fonti che confronta custodia, esecuzione, leva, rischio, commissioni e aderenza all’utente."},"claims":[{"id":"claim-dex-direct-trading","text":"A DEX is a peer-to-peer marketplace where crypto traders transact directly, typically through smart contracts and blockchain settlement rather than an exchange-controlled internal ledger.","sourceIds":["coinbase-dex-learn"],"risk":"low"},{"id":"claim-cex-custody","text":"On a custodial exchange model, the venue or custodian manages access to private keys for assets held in the account; the user does not directly control those keys.","sourceIds":["coinbase-custody-wallets","investor-custody-2025"],"risk":"medium"},{"id":"claim-self-custody-risk","text":"With self-custody, the user controls private keys and also carries responsibility for key loss, seed phrase compromise, device security, and recovery failures.","sourceIds":["coinbase-custody-wallets","investor-custody-2025"],"risk":"medium"},{"id":"claim-perps-no-expiry","text":"Crypto perpetual contracts are derivative futures-style instruments that do not have a fixed expiration date and allow long or short exposure without holding the underlying token.","sourceIds":["dydx-perpetuals-assets"],"risk":"medium"},{"id":"claim-perp-risks","text":"Perpetual trading introduces margin, leverage, funding, liquidation, and collateral-management risks that do not exist in the same form for ordinary spot ownership.","sourceIds":["dydx-perpetuals-assets","hyperliquid-funding","hyperliquid-contract-specs"],"risk":"high"},{"id":"claim-choice-framework","text":"The most useful venue choice is job-based: fiat onboarding and account recovery favor a CEX, direct token access favors a DEX, and leveraged hedging or directional exposure favors a Perp DEX only for users who understand derivatives risk.","sourceIds":["coinbase-dex-learn","coinbase-custody-wallets","investor-custody-2025","dydx-perpetuals-assets"],"risk":"medium","claimType":"editorial_judgment"}],"relatedVenues":["coinbase","dydx","hyperliquid"],"sourceStatus":"PUBLIC_SOURCE_MAPPED","availableLocales":["en","zh-Hans"]}]}