BTC $74,381.31 -1.99%
ETH $2,112.58 -5.64%
BNB $683.97 -2.03%
XRP $1.08 -7.04%
SOL $86.21 -3.84%
TRX $0.3174 -0.91%
DOGE $0.0690 -3.19%
ADA $0.1768 -2.18%
BCH $242.96 -1.38%
LINK $10.56 -2.01%
HYPE $73.31 -5.28%
AAVE $131.54 +0.75%
SUI $0.8283 -3.01%
XLM $0.1463 -3.23%
ZEC $1,211.57 -5.14%
AAPL $344.85 +0.77%
AMZN $266.38 +2.36%
GOOGL $290.77 +1.94%
MSFT $541.79 +2.07%
META $629.11 +2.85%
NVDA $175.22 -6.64%
TSLA $361.95 +1.03%
SNDK $823.05 -1.34%
INTC $56.25 -0.12%
SPCX $137.69 +1.86%
MU $688.57 -0.79%
AMD $469.69 +4.92%
BTC $74,381.31 -1.99%
ETH $2,112.58 -5.64%
BNB $683.97 -2.03%
XRP $1.08 -7.04%
SOL $86.21 -3.84%
TRX $0.3174 -0.91%
DOGE $0.0690 -3.19%
ADA $0.1768 -2.18%
BCH $242.96 -1.38%
LINK $10.56 -2.01%
HYPE $73.31 -5.28%
AAVE $131.54 +0.75%
SUI $0.8283 -3.01%
XLM $0.1463 -3.23%
ZEC $1,211.57 -5.14%
AAPL $344.85 +0.77%
AMZN $266.38 +2.36%
GOOGL $290.77 +1.94%
MSFT $541.79 +2.07%
META $629.11 +2.85%
NVDA $175.22 -6.64%
TSLA $361.95 +1.03%
SNDK $823.05 -1.34%
INTC $56.25 -0.12%
SPCX $137.69 +1.86%
MU $688.57 -0.79%
AMD $469.69 +4.92%

developer

All
Article
Flash

Developers say that the Binance hacker may have made a mistake and could potentially be located through MetaMask IP

Smart contract developer Justin Kalland posted on X, indicating that the Binance hacker may have made a potential mistake, and MetaMask should retain any Web2 logs it can access as much as possible. He stated that the hacker sent 175 million USDT to a new wallet, and about 2.5 minutes later, that wallet received 2 ETH, likely used to pay for gas fees, which aligns with the usage pattern of other attack wallets.Kalland noted that exactly two minutes later, the wallet used MetaMask's Gas Station service, even though there were already gas fees at that time. Three consecutive transactions appeared in the same block, including an ETH deposit from the Gas Station, an unlimited USDT authorization to the Kyber Network router, and a payment of 127.67 USDT to the Gas Station. The amount of this ETH deposit perfectly matched the maximum gas budget after combining the Kyber authorization and USDT payment, down to the wei.Kalland stated that the ETH held by the wallet at that time was sufficient to cover the aforementioned fees, reasonably inferring that the user was using the MetaMask wallet and mistakenly selected USDT to pay for gas fees due to haste. Using the MetaMask Gas Station requires going through MetaMask Sentinel, and the transaction is broadcasted by it rather than through conventional RPC, meaning that related interactions likely left off-chain records that may contain IP metadata. Among the checked attacker wallets, this is the only one that showed the use of the Gas Station, with the address 0xAa246BF639586a6Ba46762D378CE50cA4fc654a0.

XRP Ledger developers test a zero-balance account creation plan, which is proposed to be funded by the sponsor to cover the 1 XRP reserve requirement

According to CoinDesk, XRP Ledger developers are testing a new feature that aims to allow the creation of blockchain accounts with an initial balance of zero, with existing accounts bearing the reserve required for new accounts, thereby lowering the financial threshold for payment applications and automated software to create wallets on a large scale. This proposal was submitted on October 15 in the form of a SponsoredAccountCreate transaction proposal.According to current XRP Ledger rules, each account must reserve at least 1 XRP as a reserve, meaning that creating 100,000 independent accounts would require locking up 100,000 XRP. The new proposal intends for sponsored accounts to bear this reserve requirement, and a broader fee sponsorship mechanism in the future could also allow applications to pay transaction fees on behalf of users, but the overall reserve requirement for the network will not be eliminated. This feature is expected to lower the usage threshold for scenarios such as embedded wallets, RLUSD stablecoin payments, and AI agent automated payments.However, the related code is still under review, and the sponsorship mechanism it relies on has not yet gone live on the mainnet. As of October 19, the mechanism has only received 11 votes out of the 35 required validator votes, still falling short of the 29 votes needed for approval.
app_icon
ChainCatcher Building the Web3 world with innovations.