Recently, I've come across a bunch of "yield stacking" involving re-staking and shared security. To put it simply, the yields can be stacked, but the risks are also compounded. Many people treat it as if it's a costless stacking package. When I make a task list, I force myself to clearly write down: what exactly does this step verify? Is it helping to improve the protocol's security, or am I just bearing the tail risk on its behalf? Without understanding this clearly, it's easy to fall into the illusion of stacking.

And then there are those large on-chain transfers and hot/cold wallet movements on exchanges being interpreted as "smart money coming/going." After seeing this too many times, it really gets tiresome. For someone like me who is meticulous and frugal, I prefer to keep actions clean based on interaction frequency and cost, leaving permissions, revocations, and unlocking paths well-managed. Whether I profit or not is another matter; at least I won't lock myself out by stacking one layer too many. Anyway, I'm now more concerned about exitability, not betting on legends.