Binance Commingled User Funds Daily In Silvergate Bank Accounts: Reuters

Binance Commingled User Funds Daily In Silvergate Bank Accounts: Reuters

The world’s largest crypto exchange Binance commingled billions in user funds with its revenue in 2020 and 2021, three sources familiar with the matter. The exchange earlier admitted to mistakenly mixing consumer funds with B-token reserves.

The commingling of funds happened almost daily in accounts held at US-based crypto-friendly bank Silvergate Bank. The sums of funds ran into billions of dollars, as per an insider with direct knowledge of Binance’s group finances.

Binance failed to comply with U.S. financial rules that require keeping customer money separate from the company’s accounts. There’s a lack of internal controls to differentiate customer funds from company revenues.

Reuters didn’t verify exact figures or frequency. However, it reviewed a bank record dated February 10, 2021, showing Binance mixed $20 million in corporate funds with $15 million from an account that received customer money.

John Reed Stark, a former chief of the Securities and Exchange Commission’s Office of Internet Enforcement, said “Binance customers shouldn’t need a forensic accountant to find where their money is.”

Varinder has 10 years of experience in the Fintech sector, with over 5 years dedicated to blockchain, crypto, and Web3 developments. Being a technology enthusiast and analytical thinker, he has shared his knowledge of disruptive technologies in over 5000+ news, articles, and papers. With CoinGape Media, Varinder believes in the huge potential of these innovative future technologies. He is currently covering all the latest updates and developments in the crypto industry.

The presented content may include the personal opinion of the author and is subject to market condition. Do your market research before investing in cryptocurrencies. The author or the publication does not hold any responsibility for your personal financial loss.

Share

Leave a Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!