Weekly Updates · Archive restoration
Weekly Recap: May 21, 2022 — Reading the UST/LUNA Shock
The surviving excerpt says the UST/LUNA collapse had dominated the preceding two weeks and that the author was still watching the situation after holding investments in the ecosystem.
The recovered record
The archive preserves the title, publication date, category, and opening fragment of this weekly recap. The surviving text reads: “UST/LUNA has been all encompassing these past 2 weeks. Still watching this situation closely as I had investments in the ecosystem. The one good thing in all of this is…” The remainder of the original body was not available from the restored public copy. This version does not invent the missing sentences. It rebuilds the article around the information that survived and labels the analytical material as retrospective context.
The fragment is revealing because it places the writer inside the event rather than outside it. The update was not a detached market summary. It was a portfolio journal written while an ecosystem position was under stress and while the consequences were still unfolding. That perspective matters. During a fast collapse, balances, redemption routes, exchange access, bridge liquidity, and protocol interfaces can change faster than a weekly publishing schedule. A useful recap must therefore separate confirmed facts, personal exposure, and unresolved questions.
Why the UST mechanism mattered
UST was designed as an algorithmic stablecoin linked to the LUNA token through a mint-and-burn relationship. The system relied on market participants being willing and able to exchange value between the two assets around the intended one-dollar price. That design differed from a straightforward reserve model in which a claim is backed by cash or short-duration instruments held by an issuer. Its stability depended on market incentives, liquidity, confidence, and the capacity of the paired token to absorb pressure.
Once confidence weakened, the mechanism faced a reflexive problem. Selling pressure on the stablecoin created more pressure on the balancing asset, while weakness in the balancing asset reduced confidence in the stabilizing process. Incentives that appear effective in normal conditions can break when everyone tries to exit at once. The lesson is broader than one protocol: a peg is not a property that exists by declaration. It is an outcome produced by reserves, redemption rights, market depth, settlement mechanics, and the behavior of participants during stress.
Portfolio questions that should have been asked immediately
The first task in a crisis is an exposure map. How much capital is directly in the affected tokens? How much sits in liquidity pools, lending markets, farms, bridges, derivatives, or custodial accounts that depend on them? Is collateral denominated in the same asset that supports the loan? Are rewards locked? Can the position be withdrawn, or does an unbonding period apply? A wallet list alone is not enough because one token can carry several layers of protocol and counterparty dependency.
The second task is to distinguish liquidity from solvency. A platform may temporarily delay withdrawals while still holding sufficient assets, or it may continue displaying balances while the underlying position is impaired. Users cannot infer one from the interface alone. Evidence should include on-chain positions where available, contractual withdrawal terms, official notices, and independent market prices. In a highly connected ecosystem, the status of bridges, oracles, validators, and major trading venues can determine whether an apparently hedged position can actually be closed.
What not to do during a fast-moving failure
A portfolio journal should avoid converting uncertainty into certainty. Statements such as “the peg will recover” or “the token is going to zero” may express a view, but they are not operational plans. A better update states the observable condition, the threshold that changes the plan, and the action available at each threshold. It also records transaction constraints. Network congestion, exchange maintenance, slippage, and rapidly changing collateral factors can make an intended exit materially different from the executed one.
Adding capital solely because a price has fallen is another dangerous shortcut. A lower price does not necessarily mean a better value when the mechanism supporting the asset has changed. Averaging down increases exposure to the same thesis at the moment that thesis is under challenge. Before adding, the investor must restate why the asset should recover, what evidence would disprove that view, and how much loss the portfolio can absorb. If those answers cannot be written clearly, reducing complexity is usually more useful than increasing position size.
A better weekly-recap format
A resilient weekly update can be organized into five blocks: position changes, realized income, mark-to-market changes, operational risks, and decisions pending. Each block should name the evidence used and the time at which it was observed. For a stablecoin position, the update should show the actual trading price, available redemption path, liquidity depth, and protocol dependencies. For a leveraged or pooled position, it should show liquidation levels, pool composition, and the cost of unwinding under current conditions.
The May 21 fragment also supports a human lesson. Admitting that the author held ecosystem investments gives readers important context about incentives and possible bias. That disclosure should be standard. Portfolio writing is more credible when the author states exposure, referral relationships, and uncertainty before discussing a conclusion. The restored version preserves the surviving words and the date, while the reconstruction focuses on the risk questions that a reader would have needed at that moment. It is a historical analysis, not a current recommendation concerning any token or platform.
Recovery and post-mortem discipline
After immediate exposure is contained, the portfolio needs a post-mortem. Reconstruct the timeline from transaction identifiers, exchange statements, protocol notices, and market prices. Record which warning signals were visible, which assumptions failed, and which actions were impossible because liquidity or access disappeared. Calculate losses by mechanism rather than by token alone: depeg, slippage, liquidation, custody delay, bridge exposure, and fees. This turns a painful event into evidence that can improve future position limits.
The review should also preserve what worked. Perhaps a small allocation limited the loss, independent wallet records made reconciliation possible, or a tested withdrawal route allowed part of the position to exit. Controls that worked should be retained instead of discarded with the failed thesis. The final output is a revised policy with specific thresholds, not a promise to be more careful. A good post-mortem changes how the next position is sized, monitored, and exited.