$GOOG Alphabet's earnings are out. On the $200B capex guide, 82% cloud growth, the first negative free-cash-flow quarter since going public, and how depreciation is handled — plus which AI hardware companies this capex curve is actually paying. Alphabet Q2 2026, examined:

Bought some SK hynix. $SKHY My reasoning: all three major memory makers are pouring capex into HBM back-end capacity — but none of them is expanding DRAM front-end wafer capacity anywhere near as fast. HBM eats a huge amount of DRAM wafers. So in theory, even two or three years out, the DRAM supply-demand imbalance gets worse, not better. The more wafers get diverted to HBM, the fewer are left to produce conventional DRAM for everything else. And a single AI server needs a massive amount of HBM. HBM is the key bottleneck for token output speed on inference chips. It's not just NVIDIA — AMD, Google, and every big player building inference silicon is scrambling to secure supply. Full deep-dive here:

Aave unfroze WETH on Ethereum Core V3 on April 21. Opening exits before a loss-allocation plan is finalized creates a dynamic that is structurally disadvantageous to retail. Each withdrawal reduces the liquidity pool and enlarges each remaining supplier's pro-rata exposure to bad debt. By the time losses are socialized, the fewer WETH LPs remain, the larger the haircut each must bear. This does not disperse risk — it concentrates it on whoever exits last. The dynamic is amplified by asymmetric information access. Participants with technical tooling monitor repayment queues in real time and exit within seconds. Retail depositors cannot match that response speed. In scenarios of this kind, time advantage translates directly into loss avoidance. Kelp still holds substantial restaking ETH reserves, LayerZero remains solvent, and Arbitrum has frozen 30,766 ETH. Initiating a partial unfreeze before upstream responsibility is settled shifts the cost of that negotiation onto the slowest depositors to react — who are, overwhelmingly, retail.

Strongly agree, but LayerZero’s statement is clearly deflecting responsibility, and Aave doesn’t want to take the main blame either. They’ve probably already been arguing about it in the TG group.