BTC $64,582.07 +0.51%
ETH $1,809.41 -0.38%
BNB $591.40 +0.29%
XRP $0.9835 +2.99%
SOL $74.80 +3.60%
TRX $0.3086 +0.86%
DOGE $0.0593 +1.14%
ADA $0.1535 +0.67%
BCH $208.31 +0.34%
LINK $9.23 +1.20%
HYPE $68.90 -0.80%
AAVE $111.74 -0.29%
SUI $0.7299 +1.66%
XLM $0.1409 +2.76%
ZEC $957.15 +5.22%
AAPL $350.45 -0.64%
AMZN $259.02 +0.65%
GOOGL $281.61 -0.71%
MSFT $507.76 -1.78%
META $619.44 -0.38%
NVDA $158.31 +0.78%
TSLA $383.36 +1.25%
SNDK $822.28 +1.61%
INTC $55.96 +2.94%
SPCX $142.32 +3.42%
MU $732.46 +1.57%
AMD $514.11 +1.06%
BTC $64,582.07 +0.51%
ETH $1,809.41 -0.38%
BNB $591.40 +0.29%
XRP $0.9835 +2.99%
SOL $74.80 +3.60%
TRX $0.3086 +0.86%
DOGE $0.0593 +1.14%
ADA $0.1535 +0.67%
BCH $208.31 +0.34%
LINK $9.23 +1.20%
HYPE $68.90 -0.80%
AAVE $111.74 -0.29%
SUI $0.7299 +1.66%
XLM $0.1409 +2.76%
ZEC $957.15 +5.22%
AAPL $350.45 -0.64%
AMZN $259.02 +0.65%
GOOGL $281.61 -0.71%
MSFT $507.76 -1.78%
META $619.44 -0.38%
NVDA $158.31 +0.78%
TSLA $383.36 +1.25%
SNDK $822.28 +1.61%
INTC $55.96 +2.94%
SPCX $142.32 +3.42%
MU $732.46 +1.57%
AMD $514.11 +1.06%

ema

All
Article
Flash

first_img Coinbase batches the failed INR withdrawals in India, and the in-app channel remains closed

Cryptocurrency exchange Coinbase stated that withdrawals in Indian Rupees (INR) for Indian users have been unavailable for the past week due to a failure with its banking partner, which affected payments for all customers of that bank, not just Coinbase. Coinbase assured that user funds have remained secure during this period. The platform has now begun processing all failed INR withdrawals in batches through alternative banking channels since November 9. The first batch has been completed, and affected users are expected to receive their funds in their bank accounts within a few hours, with subsequent batches to be processed thereafter.Coinbase indicated that users affected by the aforementioned failed withdrawals do not need to take any further action, as the platform will handle it on their behalf; once the withdrawal is initiated, users will receive push notifications and email confirmations. The in-app withdrawal option will remain unavailable while the banking partner continues to address the failure. If users need to withdraw INR during this period, they can contact the Coinbase support team and specify the withdrawal amount, and the platform will send the funds to the linked bank account within 48 to 72 hours. Coinbase also mentioned that in light of this banking failure, it is strengthening its banking arrangements in India and will announce more information soon.

first_img Users claim that Aster misappropriated keys and transferred 4.56 million USD, demanding compensation for the original assets

User furongfei (@fuhuahuai) posted on November 16 that an abnormal transfer occurred in their account on the decentralized perpetual trading platform Aster in the early morning of November 13, 2026, Beijing time, resulting in a total loss of 4.56 million USD. According to the UTC times listed by the user, on November 12, 2026, at 16:22, someone registered a new account using their web proxy key, and from 16:24 to 17:08, the system executed 7 consecutive transfers to other users based on that key's signature, transferring 4,564,675.50 USDT to the new account. During the same period, 33 BTC in the account were transferred between contracts and spot 9 times, and from 16:49 to 16:59, they were split into 17 market sell orders.The user stated that the Aster signature records show that the signature address for the aforementioned 7 transfers was the proxy key 0x647E, and none of the transfers came from their main wallet. They cited the docking records stating that Aster's CEO's preliminary conclusion was that the proxy key was exposed, not the private key of the address itself; it was later confirmed in writing that this key was a temporary private key created locally in the browser after the user clicked to enable trading and completed wallet authorization, named aster-desktop, and was not the user's wallet private key. The user also mentioned that according to Aster's documentation, transferring to other users is classified as a withdrawal-level operation, and this key does not have withdrawal permissions, and the account had enabled a user privacy mode that prohibits internal transfers, yet the 7 transfers were still allowed by the system.The user claimed that the new account subsequently withdrew 4,564,674.38 USDT in 10 transactions. After the funds were cross-chain, 1,000 ETH entered Tornado Cash, and 768.1 ETH along with 993,999.67 USDT entered NEAR Intents confidential exchange. The user requested Aster to provide a written processing timeline, stating that they would not wait for recovery and would compensate according to the original assets, with the listed scope including 33 BTC, 2,200,134.21 USDT, and forced liquidation fees, and stated that any subsequently recovered funds would belong to the platform, while also requesting an explanation of the basis for the release and preservation of server logs. Reports indicate that Aster's relevant account responded under the post that an investigation team has been established.

Vitalik: EIP-8037 is a realistic option for Ethereum's secure scaling, and developers should not assume that the Gas mechanism will remain unchanged forever

Vitalik Buterin published an article explaining the design rationale behind the Ethereum proposal EIP-8037 and its impact on application developers. He stated that while scaling Ethereum's computational capacity is relatively easy, scaling state size is much more challenging. Simply raising the Gas limit could lead to significant state size inflation, increasing the storage, synchronization, and execution burdens on nodes.EIP-8037 aims to align resource pricing with the actual network burden by increasing the Gas costs for operations such as creating new accounts, storage slots, and contracts. This is a more realistic solution that balances scalability with decentralized security. Vitalik pointed out that this proposal may still affect some existing applications, especially contracts that rely on hardcoded Gas limits or specific call parameters. Rather than making more protocol layer modifications that could introduce new risks, it is currently more important to collaborate with application developers to identify and fix compatibility issues before the Glamsterdam upgrade goes live. He also advised developers not to view the Gas mechanism as an unchanging rule and called on core developers to clearly outline potential changes to protocol features in the future to minimize unexpected impacts from subsequent upgrades.
app_icon
ChainCatcher Building the Web3 world with innovations.