Turns out sent the first $TST buy tx to private RPC, but that tx still got leaked somehow.
CZ's buy tx ( set the minimum output to 363,225 TST, while at that block, he can receive up to 365,564 TST (~0.7% slippage). If this tx is not sent to
btc
(
bscscan.com
)
Turns out @cz_binance sent the first $TST buy tx to private RPC, but that tx still got leaked somehow.
CZ's buy tx (https://t.co/WTwfc2X9x1) set the minimum output to 363,225 TST, while at that block, he can receive up to 365,564 TST (~0.7% slippage). If this tx is not sent to the private RPC, then it can lead to a $200+ profit for the sandwich bot, and the sandwich bot must sandwich it. However, none did and the block builder payment was much lower than $200 at that block, so it is apparent that CZ used private RPC.
The reason that CZ's buy tx failed was due to someone buying TST ahead of CZ (https://t.co/7K8KpWLIvd). Unfortunately, this guy got sandwiched. Block builder prioritized this tx with sandwich txs over CZ's tx because the sandwich bot made $0.2 payments to block builder. If CZ set his gas price to 1.5gwei, his tx would likely be prioritized and succeed.
The real suspicious thing is why would 0xB2d57876271eA8684e7c521c1265b87703d9A0DA (B1) know CZ is buying $TST in advance. The bot explicitly checked CZ's TST balance (if it succeeds) and attempted to backrun his transaction. Is the private orderflow shared with this bot? Maybe I am retarded and missed something, or I guess only the bot owner/block builder/relay knows.
点击图片查看原图
