When I saw the project team publish the treasury spending breakdown, I honestly got pretty fired up—not because I’m doing any deep analysis, but simply because I wanted to see what they’re actually spending the money on. Some projects just keep shouting “milestones,” but there’s no real activity on-chain; on the books, it’s all operational fees. To be frank, I end up with a big question mark in my head. Anyway, my own principle is to add to my position slowly—once I see the actual testnet working or the updated logic in the code runs through, then I’ll decide.

These days, with that mainstream chain upgrade plus the downtime, the group chat has started speculating about whether the ecosystem might be moving. I’m not too anxious, because the batches I built earlier weren’t all targeting that chain. As for migration—if the project team truly wants to do it seriously, they should have set aside and planned the treasury in advance. I don’t really believe in this “last-minute, clutching-at-straws” kind of approach. I’ll treat it like burning firewood in the mountains—slow-cooking over a low flame. I’m not expecting it to flare up overnight, and I don’t want to get burned by sudden sparks. Others can choose however they want—I’ll just watch first.