Scan to download
BTC $60,538.08 -1.99%
ETH $1,555.66 -2.73%
BNB $572.47 -0.75%
XRP $1.08 -2.08%
SOL $61.64 -4.44%
TRX $0.3230 +0.45%
DOGE $0.0812 -1.95%
ADA $0.1562 -2.78%
BCH $215.32 -0.51%
LINK $7.35 -1.57%
HYPE $56.20 -6.39%
AAVE $60.24 -4.96%
SUI $0.7110 -0.10%
XLM $0.2101 +3.45%
ZEC $350.17 -6.68%
BTC $60,538.08 -1.99%
ETH $1,555.66 -2.73%
BNB $572.47 -0.75%
XRP $1.08 -2.08%
SOL $61.64 -4.44%
TRX $0.3230 +0.45%
DOGE $0.0812 -1.95%
ADA $0.1562 -2.78%
BCH $215.32 -0.51%
LINK $7.35 -1.57%
HYPE $56.20 -6.39%
AAVE $60.24 -4.96%
SUI $0.7110 -0.10%
XLM $0.2101 +3.45%
ZEC $350.17 -6.68%

uta

Coinbase reviews the May outage incident: AWS cascading failure exposes architectural risks

Coinbase released a retrospective report on the large-scale service interruption event on May 7, 2026.The outage lasted approximately 8 hours, with full recovery taking about 12 hours. During this time, trading, deposits, withdrawals, and most core services were unavailable or severely degraded. Coinbase stated that the outage was caused by multiple cooling units failing simultaneously in the cooling system of a data center in one availability zone (use1-az4) in the AWS us-east-1 region, triggering cabinet thermal protection shutdowns, which led to EC2 instances and EBS volumes going offline, affecting multiple internet services.During the recovery process, the Coinbase trading matching engine lost quorum due to the cluster architecture deployed in a single AWS data center losing most nodes. It required urgent code adjustments and the reconstruction of a new node group to restore operation, gradually restarting market trading during the recovery.Additionally, the AWS-managed Kafka (MSK) service experienced control plane failures, preventing the automatic re-election of partition leaders, further blocking quotes, fees, and some settlement and data flow systems, which expanded the overall impact.After manual partition migration in collaboration with the AWS engineering team, the system gradually returned to normal. Coinbase stated that this incident exposed its shortcomings in cross-availability zone automatic switching capabilities and disaster recovery for managed middleware. The company will upgrade its cross-region hot backup architecture, strengthen regular failure drills, and migrate the Kafka system from dual availability zones to a three availability zone deployment, while also working with AWS to advance root cause fixes and improvements.

Analysis: Bhutan denies selling Bitcoin, on-chain data points to approximately $1 billion in suspected BTC outflows causing controversy

According to CoinDesk, on-chain analysis firm Arkham Data shows that over the past year, wallets associated with Bhutan have seen outflows of approximately $1 billion in Bitcoin, with funds flowing to multiple trading platforms and trading institutions, reducing their holdings from about 13,000 BTC to around 3,100 BTC.Arkham speculates that there may be ongoing selling behavior, and if the trend continues, the relevant addresses may be cleared of holdings before October 2026. However, Bhutan's sovereign fund Druk Holding and Investments (DHI) stated that "they do not recall any recent Bitcoin sales," did not respond to specific changes in on-chain addresses, and did not confirm the current holding size, only emphasizing that there are no additional comments.The report points out that some of the fund inflow paths are related to institutions such as Galaxy Digital and OKX, leading the market to interpret this as selling or over-the-counter trading behavior, but there are also possibilities of transfers into custody, collateralization, or structured trading that do not involve selling. Additionally, some trading institution personnel stated that there has been no clear selling recently.Furthermore, Bhutan's previous commitment to a reserve of 10,000 BTC for the "Gelephu Mindfulness City" project has also been questioned due to potential sell-offs. Currently, there is still significant disagreement regarding its actual holdings and mining operations.

Three Possible Responses to the rsETH Hacker Incident: Balancing Bad Debt and Reputation, Testing KelpDAO's Credibility and Aave's Risk Tolerance

DefiLlama founder 0xngmi has outlined three possible courses of action that KelpDAO may take following the rsETH hacking incident. Each of the three paths has significant flaws, and the final decision will test KelpDAO's credibility and Aave's risk tolerance.Path One: All users share the losses. KelpDAO will uniformly deduct 18.5% of the losses from all rsETH holders proportionally. Currently, there are about 666,000 rsETH collateralized across the Aave network, primarily highly leveraged on the mainnet and L2 (assuming all are at a 95% liquidation LTV). Once socialized losses occur, the equity of all positions on the mainnet will be completely wiped out, resulting in approximately $216 million in bad debt. The Umbrella protocol can cover $55 million in bad debt, and the Aave treasury will additionally bear $85 million, leaving a gap of about $76 million. KelpDAO may fill this gap by borrowing or selling Aave tokens (currently valued at about $51 million), but this would still put significant pressure on Aave, and all users would need to share the losses.Path Two: Directly rug the rsETH holders on L2. KelpDAO will only guarantee the mainnet rsETH and consider the rsETH on L2 as worthless. Currently, Aave L2 has about $359 million in rsETH collateral (calculated at current oracle prices), and if all are calculated at maximum leverage, it would result in approximately $341 million in bad debt, which cannot be covered by the Umbrella protocol at all. Aave can only use the treasury or borrowing to save part of the market, most likely abandoning chains like Arbitrum, Mantle, and Base, which have the largest losses, leading to a collapse of these L2 markets. This option has a minor impact on the Aave mainnet but would severely damage the credibility of the L2 ecosystem and could trigger a chain reaction.Path Three: Attempt to refund only the holders based on a snapshot taken before the hack, which is extremely difficult to execute. KelpDAO tries to fully refund only the rsETH holders based on the snapshot taken before the hack, while subsequent buyers or transfer holders would bear the losses themselves. However, since funds have significantly flowed after the attack, and the nature of DeFi protocols is liquidity pools, it is impossible to truly distinguish between different batches of depositors, making technical execution very challenging. The hacker borrowed $124 million on the Aave mainnet and $18 million on Arbitrum, and after deducting the coverage from the Umbrella protocol, there remains about $91 million in losses. Although this plan theoretically minimizes the spread of impact, its practical implementation is nearly impossible and could easily lead to legal and community disputes.

ChainCatcher "From Cryptocurrency to Smart Economy" Roundtable: AI Agents are shifting from conversational to executable, with trust and verifiability becoming key bottlenecks for scalability

At the "Crypto 2026: From Cryptocurrency to Smart Economy" themed forum held in Hong Kong, guests including KiteAI's Asia Pacific head Laughing, Sentient's Asia Pacific head Anita, Brevis content director Nic Tang, Mentis product head Jerry, and Predict.fun's Asia Pacific BD head Ah Huang Ricardo engaged in a roundtable discussion on the theme "AI × Crypto --- The Foundation of the Next Generation Digital Economy."Regarding whether the outbreak of open-source AI Agents (such as "raising lobsters") is a short-term sentiment or a long-term trend, Laughing believes this marks a paradigm shift of AI from "conversational" to "executive," signaling the beginning of a long-term trend. However, Agents lack a physical identity, making it difficult for merchants to trust their trading behavior, and issues of data leakage and uncontrollability remain obstacles that must be overcome for scaling. Jerry pointed out, based on his own usage experience, that current Agents face security risks such as memory fuzziness, token consumption in dead loops, and accidental file deletion. Although newly emerged Agents have improvements, they still have shortcomings. Ah Huang Ricardo stated that behind the short-term sentiment is real user demand, but truly reproducible profitable trading Agents are still very rare, and there is a long way to go.Addressing core bottlenecks such as trust, security, and verifiability, Nic Tang emphasized that the current execution process of Agents is like a black box, where users cannot verify whether their decisions are executed as promised. Zero-knowledge proof technology can mathematically prove the source of an Agent's output and compliance with behavior, while not exposing privacy. Anita added that Sentient is committed to building an open and collaborative AI agent network, promoting the deep integration of AI and blockchain in identity, data, and incentive layers, providing foundational support for the next generation digital economy.Regarding the application scenarios that are likely to scale first, the guests generally believe that the programming field is relatively mature, and Agents in prediction markets perform better than humans in specific tracks due to their rationality and lack of emotions. In the short term, they are optimistic about API Marketplace and cross-platform consumer shopping Agents, while in the medium term, they are optimistic about content creation AI (such as AI influencers). Agent-to-Agent interaction and the Agent/Skill Marketplace are seen as important future trends.
app_icon
ChainCatcher Building the Web3 world with innovations.