BTC $77,587.42 +0.44%
ETH $2,504.16 -0.69%
BNB $723.37 -0.70%
XRP $1.36 -0.25%
SOL $100.85 -1.10%
TRX $0.3389 -0.41%
DOGE $0.0839 -1.23%
ADA $0.2079 +0.05%
BCH $224.00 -0.66%
LINK $11.37 -1.25%
HYPE $79.06 -0.42%
AAVE $126.19 -0.52%
SUI $0.7151 -1.63%
XLM $0.1807 +0.33%
ZEC $1,094.93 -2.75%
AAPL $329.21 -1.16%
AMZN $255.06 -0.77%
GOOGL $336.29 -1.61%
MSFT $494.22 -0.30%
META $641.47 -1.11%
NVDA $215.18 -1.27%
TSLA $361.50 -1.64%
SNDK $1,568.65 -3.58%
INTC $99.11 -2.32%
SPCX $148.77 -1.00%
MU $942.07 -2.63%
AMD $502.37 -2.36%
BTC $77,587.42 +0.44%
ETH $2,504.16 -0.69%
BNB $723.37 -0.70%
XRP $1.36 -0.25%
SOL $100.85 -1.10%
TRX $0.3389 -0.41%
DOGE $0.0839 -1.23%
ADA $0.2079 +0.05%
BCH $224.00 -0.66%
LINK $11.37 -1.25%
HYPE $79.06 -0.42%
AAVE $126.19 -0.52%
SUI $0.7151 -1.63%
XLM $0.1807 +0.33%
ZEC $1,094.93 -2.75%
AAPL $329.21 -1.16%
AMZN $255.06 -0.77%
GOOGL $336.29 -1.61%
MSFT $494.22 -0.30%
META $641.47 -1.11%
NVDA $215.18 -1.27%
TSLA $361.50 -1.64%
SNDK $1,568.65 -3.58%
INTC $99.11 -2.32%
SPCX $148.77 -1.00%
MU $942.07 -2.63%
AMD $502.37 -2.36%

calculation

Tất cả
Bài viết
Tin nhanh

Security Agency: The Balancer attacker conducted an invariant attack on the BPT price calculation or is the main reason for the asset theft

The security agency BlockSec's on-chain tracking platform BlockSec Phalcon posted on platform X, stating, "Balancer and several of its fork projects were attacked a few hours ago, resulting in losses exceeding $120 million across multiple chains. This was an extremely complex attack.Preliminary analysis indicates that the root cause was the attacker's manipulation of the invariant calculation for BPT prices, distorting the BPT price calculation and allowing the attacker to profit from a single batch transaction from a specific stablecoin pool.Taking the attack transaction on Arbitrum as an example, the batch swap operation can be broken down into three stages: 1. The attacker exchanges BPT for the underlying asset to precisely adjust the balance of one token (cbETH) to bring it close to the rounding boundary (amount = 9). This creates conditions for precision loss in the next step; 2. The attacker then uses a pre-constructed amount (= 8) to swap between another underlying token (wstETH) and cbETH. Due to rounding down when scaling the token amount, the calculated Δx slightly decreases (8 0.918 to 8), resulting in an underestimated Δy, which causes the invariant (D) in Curve's StableSwap model to also decrease. Since BPT price = D / total supply, the BPT price is artificially suppressed; 3. The attacker then reverses the exchange of the underlying assets back to BPT, restoring balance while profiting from the drop in BPT price.

Jupiter co-founders released a supplementary statement on last week's platform issues: Priority fee calculation errors became a major problem during severe congestion

ChainCatcher message, Jupiter co-founder meow released a supplementary statement regarding some issues faced by the Jupiter platform last week. He expressed sincere gratitude to users and community members, apologized for technical and communication errors, and committed to continuous improvement of the platform experience.Details of the supplementary statement:Priority fee calculation error: There was an error in estimating the priority fee when calculating the gas required for front-end execution. Although this is not common under normal circumstances, it became a major issue during severe congestion. The team takes full responsibility for this.DCA downtime issue: Due to an estimation error by CU, the platform's DCA function was down for about 6 hours, resulting in user orders not being executed. The team expressed deep apologies for this and will review operations to improve vigilance.Low liquidity tokens: To ensure the safe execution of DCA, the platform conducts price and slippage checks before trading. However, the marked price of low liquidity tokens may differ significantly from the execution price, preventing the engine from executing trades. The team will improve the user interface, add more information, and optimize safety check methods.Future plans: The team plans to add more information to the user interface and gradually implement intelligent safety checks to address existing issues.
app_icon
ChainCatcher Building the Web3 world with innovations.