According to BlockBeats news on June 29, as per @pandajackson42's data panel, on June 28, Binance Alpha recorded a trading volume of 469 million USD, still maintaining a low level.

Among them, the trading volume of BR is 329 million USD, ranking first.

In fact, the trading volume of Alpha is basically proportional to liquidity. ZKJ's highest LP reached about 50 million USD, but the proportion of tokens is higher, while BR's LP has more USDT. Moreover, the tokens BR (Bedrock) and ZKJ have significant differences in mechanism and market performance.

1. The liquidity structure differs from the motivations of the project team.

- The collapse of ZKJ was mainly due to the highly concentrated liquidity, and the project team along with major holders harvested the market through liquidity withdrawal and price dumping. Its liquidity pool design has structural flaws, leading to a rapid collapse in price once liquidity is withdrawn.

- The liquidity pool of BR has reached 40 million USD (of which USDT accounts for 33 million), and the project team adopts protocol-owned liquidity (POL), reducing the risk of malicious liquidity withdrawal. In addition, the main profit model of the BR project team is to earn transaction fees, rather than short-term pump and dump, which makes them more inclined to maintain long-term ecological stability.

2. Transaction wear and user strategy optimization

- ZKJ and KOGE were used to inflate Alpha points, with users frequently trading leading to increased market vulnerability.

- BR provides transaction fee rebates, reducing user wear costs, making it more suitable for stable Alpha point acquisition rather than short-term speculation. Additionally, BR's deep liquidity reduces slippage risk, making it less likely to cause severe fluctuations due to large trades.

So, in the short term, BR seems relatively stable, but for a short-term price increase of double, everyone should still do small transactions, avoid using thousands of U in one go. Even if you initiate MEV, you can't avoid getting squeezed; it's best to control the amount per transaction to be less than t-64.