Urgent.News

What's breaking now, across thousands of outlets.

Tech

South Korea urges exchanges to boost cold storage after Binance hack

South Korean crypto exchanges are already required to hold at least 80% of customer crypto in cold wallets, but the regulator is urging more.

South Korea urges exchanges to boost cold storage after Binance hack

South Korean regulators are urging cryptocurrency exchanges to enhance their security measures following the recent $6.3 billion hack of Binance, according to a statement released on Monday. The Financial Services Commission (FSC) convened an emergency meeting with key industry players and oversight bodies to assess the impact of the attack on the local crypto market and evaluate existing security protocols.

The FSC highlighted the need for exchanges to increase the percentage of assets stored in offline cold wallets, which are less susceptible to hacking attempts, and to review IT access controls, withdrawal procedures, and administrator privileges. Currently, South Korean law mandates that exchanges maintain at least 80% of user assets in cold storage, although this varies among different platforms.

Recent data from the Financial Supervisory Service shows that Upbit, Bithumb, and Coinone have notably high cold wallet ratios of 99.17%, 94.76%, and 85%, respectively. The regulator also recommended exchanges to bolster their incident response capabilities, promptly report unusual access attempts, and set aside additional reserves.

This advisory follows a separate review conducted by the Bank of Korea, which is assessing the vulnerability of 18 banks and 13 brokerages to crypto-related risks, including significant exchange hacks and prolonged market downturns.

Written by urgent.news from Cointelegraph's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at cointelegraph.com →

More in Tech

Webhook Follow-Up Task Scheduling: One Hour Later with Queues or Cron Explained

Webhook Follow-Up Scheduling: Delayed Messages vs Per-Event Timers Explained Short answer: for a logistics webhook that must run about an hour later, put a durable due time in a queue-backed table and…

  • Store webhook event details in a durable FollowUp table with runAt timestamp
  • Use poller with FOR UPDATE SKIP LOCKED to claim ready rows without blocking transactions
  • Compare delayed queues and cron sweeps for trade-offs between convenience and inspectability

Why your n8n Gmail Trigger is not working (and how to fix it)

You connected Gmail. The node is green in the editor. Then production stays quiet—or every poll returns nothing—while new mail sits in the inbox.

  • Workflow must be published and active, not draft
  • Self-hosted n8n needs Google Cloud OAuth client with Gmail API enabled
  • Check filters, poll interval, and downstream nodes for failures

More from Tuesday 3 November →