Security

<div class="wublock"> 
 <div dir="auto" class="body markup"> 
  <div class="captioned-image-container"> 
   <figure> 
    <div class="image2-inset"> <picture> 
      <source type="image/webp" srcset="https://substackcdn.com/image/fetch/w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2ff28103-ebd9-4c80-be81-13999ab9b01e_1200x800.png 424w, https://substackcdn.com/image/fetch/w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2ff28103-ebd9-4c80-be81-13999ab9b01e_1200x800.png 848w, https://substackcdn.com/image/fetch/w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2ff28103-ebd9-4c80-be81-13999ab9b01e_1200x800.png 1272w, https://substackcdn.com/image/fetch/w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2ff28103-ebd9-4c80-be81-13999ab9b01e_1200x800.png 1456w" sizes="100vw"> 
      <img src="https://substackcdn.com/image/fetch/w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2ff28103-ebd9-4c80-be81-13999ab9b01e_1200x800.png" width="1200" height="800" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/2ff28103-ebd9-4c80-be81-13999ab9b01e_1200x800.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:800,&quot;width&quot;:1200,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:615596,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:null}" class="sizing-normal" alt srcset="https://substackcdn.com/image/fetch/w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2ff28103-ebd9-4c80-be81-13999ab9b01e_1200x800.png 424w, https://substackcdn.com/image/fetch/w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2ff28103-ebd9-4c80-be81-13999ab9b01e_1200x800.png 848w, https://substackcdn.com/image/fetch/w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2ff28103-ebd9-4c80-be81-13999ab9b01e_1200x800.png 1272w, https://substackcdn.com/image/fetch/w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2ff28103-ebd9-4c80-be81-13999ab9b01e_1200x800.png 1456w" sizes="100vw" fetchpriority="high"> 
     </picture> 
     <div class="image-link-expand"> 
      <svg xmlns="//www.w3.org/2000/svg" width="16" height="16" viewbox="0 0 24 24" fill="none" stroke="#FFFFFF" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2"> <polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line> 
      </svg> 
     </div> 
    </div> 
   </figure> 
  </div> 
  <p><strong>Author: Haotian</strong></p> 
  <p>Original Link: </p> 
  <p>https://twitter.com/tmel0211/status/1704869126949539947</p> 
  <p>Exchanges manage a large number of EOA Deposit recharge addresses. Every time a user deposits cryptocurrencies, the assets are transferred to these fragmented small addresses. Exchanges typically need to perform “aggregation” of these addresses to facilitate unified asset management.</p> 
  <p>There are typically two choices for the aggregation of exchange addresses:</p> 
  <p>1. Whenever a user deposits cryptocurrencies, the program immediately transfers the corresponding assets to a hot wallet address. However, the issue with this approach is that when a user has multiple deposit demands, they may split it into multiple transactions. For example, whales might first deposit a small amount for security reasons and then gradually transfer the rest. Obviously, this approach can result in more transactions (TXS), and if the exchange uses this aggregation method, it may have to deal with high gas fees during periods of high gas prices. However, the benefit is that the entire aggregation process is decentralized, and users do not notice it. For the exchange, it is just a normal operational expense.</p> 
  <p>2. After users deposit cryptocurrencies, the fragmented small EOA addresses remain unchanged for some time. When users withdraw, they directly withdraw from a large hot wallet, and then aggregation of addresses is performed at fixed intervals. This allows for easier accounting and unified asset management. Additionally, it allows the exchange to choose a time when gas prices are relatively low for the transaction operations. However, there is a challenge with as performing a large number of operations within a short timeframe can easily drive up gas prices and, if noticed by the media, could lead to public relations issues. It is difficult to explain to the public why the exchange needs to centralize asset aggregation, especially when it results in significant gas expenditure.</p> 
  <p>Clearly, Binance has adopted the second method of address aggregation. From the perspective of the exchange’s business logic, regardless of the chosen method, there will be a significant expense in managing business funds. Different exchanges may have varying asset management strategies.</p> 
  <p>To help understand this, I have analyzed two addresses, Binance14 and OKX3. Binance14 uses the second method, while OKX3 likely uses the first method. However, due to the vast difference in asset volume and transaction volume between the two, the data is for reference only.</p> 
  <p>In Figure 1, Binance14 manages nearly 110,000 ETH in total assets, and as a receiving address, it has historically consumed 10,000 ETH in gas. For example, on September 13th, during a significant aggregation, 388 ETH in gas was consumed in a single day. The highest daily gas consumption in history was 871 ETH. Therefore, it is normal business expenditure for address aggregation to consume several million dollors in gas.</p> 
  <p>In Figure 2, OKX3 has a smaller scale of managed assets, but as a receiving address, it has historically consumed 1,530 ETH in gas. From the data, it can be seen that OKX’s daily consumption is relatively balanced, with a peak of only 15 ETH in a single day. This illustrates that the first aggregation method incurs costs during regular operations.</p> 
  <p>As for which method is better, exchanges will undoubtedly calculate and select the most suitable and optimized choice for themselves. Cost optimization is just one key factor but not the absolute factor.</p> 
  <p>Although Binance is wealthy, it also does not neglect optimization.</p> 
  <p>Furthermore, everyone needs to understand that exchange asset consolidation management involves multiple issues such as cost optimization, security risk control, internal approval processes, fund efficiency, and more. Cost optimization is just one key factor, but not an absolute one.</p> 
  <p>Cost Optimization: If we look closely, optimization is certainly possible. I checked the data, and over 140,000 transactions were sent in just one hour between 5–6 pm Beijing time. People naturally wonder, can’t this be spread out over 1–2 days? Can’t the program be stopped during Gas congestion? From an engineering standpoint, it’s certainly possible, but spreading the time over 1–2 days or even 1–2 months won’t cause Gas congestion issues, and it can save money. However, it could potentially introduce other risks, similar to the first method.</p> 
  <p>Security Risk: The biggest consideration should be security. Exchanges manage a large number of private keys for addresses, and permissions are likely controlled by a system. Engineers performing aggregation effectively gain high-level system access (access to private key signatures). Assuming it’s a HSM cold wallet system, such systems should be as offline as possible. Compared to having the permission open for 2 days, having it open for 2 hours significantly reduces the attack surface, preventing potential hacker attacks. Therefore, rapid aggregation is a core consideration for security risk control. Spending 300 ETH to effectively prevent 300,000 ETH from being attacked seems reasonable, doesn’t it?</p> 
  <p>Internal Control Process: Exchanges operate as large organizations, involving management and execution levels. To regulate asset usage processes internally, there is an approval process. For tens of thousands of EOA addresses and private keys, the most efficient approach is for the boss to have the highest authority, followed by unified signatures for one-time processing. If it is divided into smaller portions and processed in batches, it will involve the distribution of management authority, which may inevitably lead to the risk of some employees being single points of failure. If managed centrally by the boss, the ideal solution would be to consolidate at a specific time, requiring approval only once. If multiple addresses are split and multiple batches require consolidation approval, it would tie up the boss’s energy in asset consolidation. Is that appropriate?</p> 
  <p>Issues related to fund efficiency and preventing unexpected situations are also possible.</p> 
  <p>In conclusion, the issue of exchange asset consolidation is not solely a cost issue. It involves a very complex range of factors. Looking back at Binance’s history, cases like high Gas consolidation are not isolated incidents. It is evident that this is a consistent balancing solution arrived at by Binance after considering various factors.</p> 
  <p><span>Follow us</span><br><span>Twitter: </span>https://twitter.com/WuBlockchain<br><span>Telegram: </span>https://t.me/wublockchainenglish</p> 
 </div> 
</div> 
<p>Source: <a rel="noopener noreferrer nofollow" target="_blank" href="https://thebittimes.com/why-does-binance-wallet-s-gas-skyrocket-exploring-the-technical-and-security-factors-tbt63751.html">https://thebittimes.com/why-does-binance-wallet-s-gas-skyrocket-exploring-the-technical-and-security-factors-tbt63751.html</a></p>

Why Does Binance Wallet's Gas Skyrocket? Exploring the Technical and Security Factors

TheBitTimes

2023년 9월 23일에 게재된 다른 기사

Blockbuster Crypto Wall Street Memes Token to List on Binance in 3 Days Claims Source, Next Pepe ...

Payments shouldn’t be handled on the Ethereum and Bitcoin networks | Opinion

Why debt financing is so important for the African business market

SHIB, BONE Now Fully Integrated by This Top Crypto Jobs Platform for Payments

Most Costly AI-Powered Cyber Attacks & Prevention (Exclusive Report)

Ethereum's 0.25% Price Decline to $1,593.41: Key Takeaways for September 23, 2023

무료 뉴스레터에 가입하여 매일 최신 암호화폐 소식을 받아보세요!