When Moondance activities resume, hopefully soon, I will be rebooting it under a new model. The writing will be much less about general DeFi risk analysis and education and much more about hands-on experimentation with DeFi operations on Solana for fun and profit.

The new model, explained roughly:

1. Use AI to identify a new or novel way to use Solana DeFi to achieve a meaningful short term profit. The idea is to build predictable, repeatable on-chain investment processes that involve $100 going in → >$105 coming back out in < 1 month. This was the original concept behind the Moondance business idea, and I have regretted letting myself be talked out of having that core frame as the primary driver of the business.

2. Publish a free post on the currently under-investigation investment mechanism. Explain in detail how and why it might work. Explain the setup of how the experiment will be executed.

3. Execute the experiment exactly as described and see how it goes. This will involve investing small amounts of Moondance’s own business budget in these experiments. They may sometimes end up running longer than 1 month, while sometimes (if they succeed early), I may take profits off the table sooner.

4. Publish a paid post describing the outcome of each experiment in detail. Deep dive into the mechanics, choices, on-chain and off-chain variables that resulted in the success or failure of the experiment. Give the strategy an official thumbs-up/down with rationale. Give notes on what I would change in the future if I were to repeat the experiment.

5. Rinse and Repeat. Frequently. Gain an audience. Sell subscriptions.

So, stand by for more good times, and thank you for your loyalty and patience.

As previously discussed, an audit badge does real work. It signals that someone examined the code. It tells you the team cared enough to pay for external scrutiny. It pre-empts some categories of obvious failure.

But an audit answers a narrow question: did the code behave correctly under inspection?

That is not the same question as: will the system survive a real crisis?

Experienced operators know the difference. They evaluate protocols using a stack of known security signals rather than a single badge.

Here is how that evaluation goes.

Reminder: What an Audit Covers

An audit is a snapshot of the code at one moment in time. It says nothing about what happens when real capital enters the system, when governance actors disagree, or when market conditions that designers didn’t anticipate arise to create new attack surfaces.

Audits test smart contract logic against known vulnerability patterns. They check access controls. They verify that the code does what it claims to do.

They don’t (and essentially can’t) test for economic incentives, governance capture, oracle manipulation, upgrade risks, or operational mistakes.

The point is… correct code can still be involved in catastrophic user outcomes.

Several major exploits in DeFi occurred without any bugs in the code at all.

The Strongest Signal: Survival

Battle-tested code is the strongest security signal available.

Experienced DeFi Operators ask: how long has this system been running? Has it processed billions in real transactions? Has it survived liquidation cascades, market crashes, protocol stress?

Attackers probe deployed systems continuously. Time in production creates adversarial pressure no audit team can replicate. Uniswap, MakerDAO, and Aave have been attacked, probed, and manipulated by people whose entire job is to find exploits. They are still running.

Survival is information.

A protocol with six weeks of TVL and a clean audit has not been tested. It has been glanced at.

Risk Categories

An audit cannot tell whether a system’s economic incentives will survive adversarial conditions. Deeper analysis is required.

Two categories of risk exist almost entirely outside the scope of an audit.

The first is governance and upgrade risk. If a protocol has admin keys, upgradeable proxy contracts, or concentrated governance voting, the currently deployed code matters a lot less than you might assume.

A system that can be rewritten overnight carries fundamentally different risk from a system that cannot change. An audit of last month’s code tells you nothing about what the code will look like next month.

Experienced DeFi operators ask these (political and structural) questions:

· Who controls upgrade keys?

· Can parameters change overnight?

· How concentrated is governance voting power?

The second category is economic design. Several of history’s largest DeFi exploits have not been driven by hacks in any traditional sense. They have included things like:

· logical attacks

· oracle manipulation

· liquidity drain mechanisms

· governance vote capture

These types of attacks exploit incentive structures rather than buggy code. Contracts can execute exactly as written, and outcomes can be catastrophic anyway.

Continuous Testing vs. a Snapshot

Bug bounty programs have a much bigger real-world impact than most people realize.

Audits are one-time events. Bounty programs are permanent pressure. A meaningful bug bounty (large enough to attract serious researchers and running on a credible security platform) means the protocol is being actively tested at all times by people with financial incentive to find problems.

The size of the bounty is also valuable information to factor into analysis. A $100,000 maximum payout signals a different security posture than a $10,000,000 cap.

Audits test code once. Bounties test code forever.

Serious Protocols Visibility

There is a final signal that receives less attention than it deserves: operational transparency.

Protocols that have clear governance documentation, public incident response procedures, active on-chain monitoring, and open communication after problems occur demonstrate organizational discipline (separate and distinct from technical discipline).

A protocol that goes dark after an incident, or that has no documented process for handling one, is a different level of risk compared to a protocol that communicates openly and upgrades its procedures.

Transparency does not guarantee safety. But its absence often indicates higher risk.

Final Thoughts

Most retail participants stop digging after glancing at a protocol’s audit badge because it’s visible and assumed to carry a certain authority. It fits neatly on a webpage. It is psychologically effective at quickly converting anxiety into confidence.

Experienced DeFi operators ask a different set of questions:

· Has this system survived real attacks?

· Who can change it, and under what conditions?

· What incentives shape behavior when things go wrong?

· How does the team respond when something breaks?

The difference between those two approaches is not sophistication for its own sake. It is the difference between true measurement and false confidence.

Operators who survive multiple cycles treat security as a stack, not a badge. The stack includes longevity, continuous testing, governance design, economic incentive modeling, and operational transparency. And audits, which are useful but not sufficient, and live at the bottom of the stack.

Thank you for reading.

Unclear on something? Want a topic covered? Submit Your Questions Here

I read everything. Good questions may become future posts.

If this analysis was useful, Moondance Research goes deeper.

I publish one paid piece each week focused on structural risk, capital protection, and honest yield literacy.

Paid subscribers receive the full archive, reference-grade frameworks, and downloadable artifacts designed to reduce the probability of getting financially wrecked.

Founding 100 subscribers receive permanent preferred pricing as recognition for supporting Moondance in its earliest phase.

→ You can learn more or subscribe here.

Most people mentally file governance tokens as participation badges. You vote on proposals, participate in the community, and maybe the token goes up someday.

Governance is the ability to change setpoints that determine who gets paid, who gets diluted, and who takes a loss when something goes wrong. The token is the handle you hold. The handle is connected to actual economic plumbing.

A governance token is not a coupon. It is a control surface.

After reading this post, you should be able to look at any governance token and answer two questions: what economic levers can it actually move, and when those levers move, who wins and who silently pays.

The Control Theory Lens (in Plain English)

A control surface is something that changes the behavior of a system by adjusting a small set of parameters.

Thermostats and steering wheels are control surfaces. The important part is understanding what changes when you move them.

In DeFi, the parameters that governance can adjust are things like fees, reserve factors, emission schedules, collateral rules, interest rate curves, and supply caps.

The system has three components:

1. Sensors: what the protocol reads. Price, utilization, peg, TVL, liquidity depth, etc.

2. Actuators: what governance can change. Parameter updates, fee switches, emission gauges, treasury routing, etc.

3. The Plant: the actual economy, meaning the behavior that emerges after the parameter values change. User behavior, leverage demand, LP allocation, insolvency risk, etc.

Governance is not “community vibes” on Discord. It is change control over the money machine.

Moondance Governance Classifications

The question is not whether a token has governance rights. The question is what the governance actually controls.

Not all governance tokens control the same things, and the risk profile changes depending on which lever(s) you’re holding.

Class A: Parameter tokens

Token holders can adjust knobs that directly alter user yields, borrowing costs, and risk levels. Reserve factors, LTV ratios, liquidation thresholds, interest rate curves. If governance raises a reserve factor from 10% to 25%, every supplier on that market immediately earns less interest. That is a real economic event, triggered by a vote.

Read more

Gross yield is easy. Net yield computation integrity is the work.

Most often in crypto, APR is a protocol emission rate, not an accurate reflection of net return.

Staking analysis tends to stop at a headline APR (due diligence done… yeah, not so much). That number is the starting point. Between it and what actually arrives in your wallet sit a series of structural leakages: fees, MEV dynamics, liquidity conditions, exit timing, and dilution effects. Each is measurable. None of them are disclosed on the same dashboard page as the APR.

And liquid staking doesn’t remove friction. It relocates it.

If you’ve never computed your realized yield through exit, you haven’t measured the product. This post names the leaks and builds a framework for measuring them.

What you should measure: Net Economic Yield

There’s a number that matters. It’s never advertised. By anybody. You have to build it yourself.

Call it Net Economic Yield (NEY). It’s the return that survives the full round trip from entry to exit.

The construction looks like this:

Net Economic Yield = Gross validator reward rate

• protocol and operator fees +/- MEV capture share (infrastructure-dependent and regime-sensitive)

• dilution adjustment (what portion of yield is simply inflation compensation)

• slippage or discount on entry and exit

• time-to-liquidity drag (queues, epoch delays)

• integration leakage (position design, accounting drift)

Ordering matters: account for validator-layer frictions first, macro dilution next, and exit frictions last.

Baseline: “APR” is not one thing

Before naming the leaks, I’ll establish what the underlying product actually is, because ETH and SOL staking are structurally different.

Ethereum validator rewards are a blend of two distinct sources: consensus layer issuance (protocol-determined, stable, based on total active stake and validator duties) and execution layer income (priority fees plus MEV, paid by users, highly variable). In early 2026, aggregate validator APY is being cited at roughly 3.5 to 4.2% annualized. The consensus layer often contributes ~2–3% in this regime; the execution layer component, fees and MEV, accounts for the remainder.

Execution-layer rewards are market-dependent. They are paid by users, not minted by protocol schedule. That distinction matters. Consensus rewards are deterministic. Execution rewards are not.

Solana staking yield is more dominated by scheduled inflation. The protocol started at 8% annual inflation, reduces that rate by 15% per year toward a long-term floor of 1.5%, and directs the vast majority of inflationary issuance to staked accounts and validators, net of commission and performance variance. As of early 2026, inflation fluctuates between 4-to-6%. Staking APY figures in the 6-to-7% range are consistent with that inflation rate, adjusted for staking participation, validator uptime, and commission.

If you don’t separate issuance yield from fee and MEV yield, you’re not doing yield analysis. You’re reading marketing copy.

Leak #1: Fees are a permanent skim on rewards

Every liquid staking protocol takes a cut. The structure varies; the result does not. The protocol skims a portion of what the underlying validators earn before any of it reaches you.

You are not just staking. You are entering a revenue-sharing agreement.

Lido charges 10% of staking rewards, split between node operators and the Lido DAO treasury. Rocket Pool charges variable commission at the minipool level, with the protocol taking a portion as well. Marinade charges a fee on rewards and on delayed unstaking. The specific numbers matter less than the structural fact: the protocol and its operators are rent-takers on your reward stream.

Two things make this more significant than it appears.

First, it compounds: a 10% skim is applied to every reward period, forever. The cost accumulates.

Second, fee policy is governed, not fixed. Any change made by a protocol results from a governance decision and can be changed again by another governance decision. This is not hypothetical. Multiple major liquid stacking token (LST) protocols have active or recently resolved governance proposals altering fee structures. The yield integrity of a staking position is only as stable as the governance environment it operates in.

This is why Moondance tracks fee-policy drift and incentive regime changes as yield events.

Leak #2: MEV is either yield uplift or yield siphon, depending on structure

MEV (maximal extractable value) has become a meaningful component of staking returns. It is also the most structurally opaque component.

On Ethereum, validators using MEV-Boost outsource block construction to specialized builders. Builders compete for inclusion by bidding a portion of the MEV they extract. Research suggests validators capture a majority of extracted MEV through this system. For Lido validators, MEV that reaches the validator is routed into Lido’s Execution Rewards Vault and then included in the rebasing mechanism that distributes rewards to stETH holders after protocol and node operator fees.

For Rocket Pool, MEV earned by participating validators enters a Smoothing Pool and is distributed to rETH stakers and node operators at checkpoint intervals. Neither protocol publishes a specific percentage of MEV that ultimately arrives at the holder level versus being retained by operators and DAOs.

On Solana, the numbers are more concrete. Jito infrastructure, a modified validator client and an off-chain block engine that runs auctions where MEV searchers bid for transaction inclusion, has been widely adopted. One institutional validator operator reported that Jito MEV infrastructure contributed 13 to 15%1 of total staking rewards in Q2 2025. Several analyses suggest MEV accounts for roughly 14% of total staking returns on average, with peaks of 20 to 30% during high-activity periods. Approximately 92% of stake weight on Solana runs on MEV-enabled clients as of early 2025, meaning MEV capture is nearly universal across the validator set.

MEV-funded yield is paid for by other network participants (i.e., it’s not free money). It’s redistributed edge: value extracted from traders and DeFi users, redirected to validators and delegators. The staker who benefits from MEV-boosted APY is, in an accounting sense, receiving a transfer from someone else’s transaction.

This doesn’t make MEV yield inferior. It makes it structurally different. And it makes the infrastructure that captures and distributes it a first-class variable. The yield is only as durable as the auction mechanism that routes it.

Moondance treats MEV policy and capture infrastructure as primary yield variables. When that infrastructure changes, the yield changes.

Leak #3: “Liquid” is a conditional claim

The liquidity in “liquid staking” is real. It is not guaranteed at par. A 1% exit discount can easily erase multiple months of staking yield.

LSTs trade on secondary markets at prices that are close to, but not always equal to the underlying staked asset. Over the past 18 months, major LSTs have generally traded near parity: stETH/ETH has ranged tightly around 0.995 to 1.002, rETH tends to trade at a small persistent premium of roughly 1 to 2% (reflecting supply constraints), and mSOL has shown deviations under 2% during SOL volatility. Under normal conditions, the peg holds.

One relevant question is: what happens when conditions are not normal?

The historical record is instructive. stETH traded at discounts of up to 6%2 during the 2022 stress period driven by leveraged unwinds and Curve pool imbalances. That discount was not a protocol failure. The 1:1 backing was intact. It was a secondary market failure driven by liquidity dynamics, the same dynamics that can recur in any stress environment where more holders want to exit than the available market depth can absorb.

Exit queues are another observable dimension. Ethereum’s native validator exit queue extended to approximately 38 days during a November 2025 stress window. Marinade’s delayed unstake on Solana runs 2 to 4 days, spanning 1 to 2 epochs. These durations are not emergencies. They are structural features that can become costs when the exit decision is time-sensitive.

During normal conditions, the discount and the queue are not noticeable. During stress, which is exactly when you are most likely to want to exit, both expand. The liquidity is real. It is also priced to protect the protocol, not the holder. Under stress, liquidity prioritizes system stability over individual profits.

Leak #4: Plain old yield dilution

This is the most uncomfortable point in the analysis and the one most staking commentary avoids entirely.

Staking rewards are denominated in the asset you’re staking. If the supply of that asset is expanding, a portion of what you call “yield” is not income. It is dilution offset. You are earning tokens to keep pace with issuance, not to build real buying power.

A 6% staking yield in a 5% inflation regime is not a 6% economic return.

On Solana, the inflation schedule is explicit and documented (see Solana Foundation documentation on inflation schedule and epoch issuance3). Inflation in 2026 sits in the mid-single-digit range, between 4-to-6% depending on measurement window. Staking APY in the 6-to-7% range implies a thin in-token margin, before fees, MEV variability, and commission are considered.

Several analyses frame Solana’s real staking yield in 2026 as 0 to 3% after accounting for this inflation. Validators are producing those numbers. After their commission comes out, the delegator receives less.

On Ethereum, the picture is regime-dependent. EIP-1559 introduced a fee-burning mechanism that makes the ETH supply dynamic: in high-activity periods, the supply can be deflationary; in low-activity periods, it can be modestly inflationary. Staking commentary often references whichever regime supports the preferred narrative. The honest answer is that you have to check the current supply dynamic, not repeat a slogan.

In some regimes, staking is insurance against dilution, not income.

If you ignore the dilution context, you misunderstand rate. This is among the many reasons why Moondance treats yield in net economic terms rather than trusting headline APR.

A worked example: what the math actually looks like

Take a hypothetical ETH staking position through an LST.

Gross validator rate, inclusive of average MEV capture: 4.0% annualized.

Assume a protocol plus operator fee of 10% of rewards. That’s a 0.4% drag. Post-fee rate: 3.6%.

Apply an exit discount. Assume a secondary market exit at 0.5% below the underlying, which is well within the historical normal range and well below stress-period discounts. Over a 12-month holding period, that’s a 50 basis point drag on realized return.

0.5% isn’t much, right? Wrong. That 0.5% exit discount erased roughly two months of supposedly lucrative yield.

Realized Net Economic Yield: approximately 3.1%. Assuming no further possible leaks (e.g. liquidity crunch or exit queue delay).

4.0% – 0.4% fee – 0.5% exit discount ≈ 3.1%

This is not a scandal. It’s math. The gap between 4.0% and 3.1% represents fees, exit friction, and structural realities that the headline number obscures. The point is not that 3.1% is a bad outcome. The point is that you should compute it before sizing the position. Don’t let it catch you off guard after the fact.

(Also note: this is not a one-and-done calculation. The variables move.)

The Questions You Should Be Asking:

What is my expected Net Economic Yield under normal conditions?

What about under stress?

How does this affect my plans?

What Moondance tracks

My monitoring thesis is simple: gross yield is stable and easy to observe. Net yield integrity requires ongoing attention because the variables between gross and net are not static.

Moondance tracks these as first-class yield determinants:

• Fee policy drift: protocol and operator fee changes via governance

• MEV capture and distribution regime: client infrastructure, auction structure, staker share

• Liquidity depth and discount behavior: secondary market conditions, pool depth, stress-period signals

• Exit friction: native validator queues, LST redemption mechanics, epoch timing

• Dilution regime shifts: supply dynamics for ETH and SOL relative to stated staking yield

Gross yield is easy. Net yield integrity is the work. If you don’t monitor leaks, you work blind against the wrong number.

Thank you for reading.

Unclear on something? Want a topic covered? Submit Your Questions Here

I read everything. Good questions may become future posts.

If this analysis was useful, Moondance Research goes deeper.

I publish one paid piece each week focused on structural risk, capital protection, and honest yield literacy.

Paid subscribers receive the full archive, reference-grade frameworks, and downloadable artifacts designed to spot opportunities and reduce the probability of getting financially wrecked.

Founding 100 subscribers receive permanent preferred pricing as recognition for supporting Moondance in its earliest phase.

→ You can learn more or subscribe here.

Most DeFi participants treat yield as a dashboard number, something that strictly moves with utilization, incentives, and market conditions. You check the rate. You decide whether it’s attractive. What rarely enters the picture is that a governance vote can change that number just as directly as utilization can.

In traditional markets, no serious operator ignores what a board of directors does. Dividend declarations change cash flows. Buybacks alter capital structure. Rights offerings shift ownership. Reserve policy changes affect what gets distributed to whom.

These are called corporate actions, and they have entire infrastructure built around them: standardized feeds, disclosure frameworks, indexed databases. Everyone understands that when a board acts, the financial reality for every holder changes.

In DeFi, the equivalent events happen constantly. They just aren’t often called by the same names.

The Argument in One Place

Governance parameter changes are corporate actions.

Corporate actions alter yield.

Therefore governance events are yield events.

This sounds obvious once stated. It isn’t treated as obvious in practice. Most DeFi operators experience yield changes after they happen, not in anticipation of them. The reason is structural: the information exists, but it’s distributed across governance forums, timelock logs, configuration contracts, and explorer transactions. It has not been normalized. It has not been indexed the way corporate actions data is indexed for equities.

An asymmetry exists. Operators who understand governance as a yield variable can reason about their positions more clearly. Operators who do not are reading metrics from a dashboard already impacted by parameter changes.

Defining “Corporate Actions”

The formal definition matters here. Corporate actions are events initiated by a corporation that affect its securities and their holders. The standard taxonomy includes cash and stock dividends, stock splits and reverse splits, rights offerings, tender offers and buybacks, and mergers or reorganizations.

What they share is this: they change the financial reality for holders. Cash flow distribution shifts. Capital structure changes. Ownership stakes are diluted or concentrated. Risk profiles move.

Yield shifts when these happen. This is considered basic market literacy.

DeFi has the same class of events.

When governance adjusts emissions, reserve factors, or caps, the yield surface changes. Not probabilistically. Mechanically.

Most operators discover those changes after the fact.

This piece introduces a governance-to-yield framework — and the monitoring discipline that follows from it.

Read more

There is always a screenshot.

Someone posts their wallet balance. Five figures, sometimes more. “Just for using the protocol.” The comments fill with questions about how to replicate this great success. The next round of activity begins.

What the screenshot fails to show is the pile of attempts that paid nothing. Gas fees. Bridging costs. Hours spent qualifying for eligibility criteria that turned out to be retroactive, opaque, or quietly sybil-filtered. Tokens that were claimed, held far too long, and sold for a pittance into a market that had already moved on.

Airdrops are not gifts from benevolent protocols. They are marketing budgets, paid out in freshly minted tokens instead of dollars. It is calculated.

Airdrop chasing can be a rational activity for crypto holders, but most avid “hunters” approach them irrationally and get burned.

Defining “Airdrop”

Protocols distribute tokens to accomplish something specific: stimulate usage, seed governance participation, reward early adopters, and/or generate liquidity. The “payment” isn’t cash. It’s token supply, newly created, with a market price that exists strictly because someone else is willing to buy it.

Arbitrum’s airdrop in early 2023 is an example worth discussing. The protocol distributed 12.75% of overall total supply via their initial TGE (token generation event), split between users and DAOs.

Eligibility based on points/activity/ heuristics was announced retroactively. The unfortunate implication is simple. You could have been active for months and still received the minimum 625 tokens, or nothing at all, depending on behavior patterns that weren’t announced in advance.

That’s not a windfall. It’s an audition you didn’t know you were in. With a payout structure you had no way to predict in advance.

Expected Value

Expected value is not a complex concept. It is:

1) the probability of a good outcome,

2) times the value of that outcome,

3) minus costs.

Most airdrop analysis quietly skips the first and third parts entirely, focusing only on hope of “number go up.”

Probability of qualifying. Eligibility is not guaranteed. As in the case of Arbitrum’s airdrop, criteria are often retroactive. Sybil filters err on the side of disqualifying a large number of wallets, meaning interactions that “should” count sometimes do not.

Dirty industry secret: in competitive farming environments, the people who maximize allocation are usually the ones who somehow understood the evaluation model before it was public. Everyone else gets to guess and play catch up.

Value of the tokens you receive. Opening price is not realized price. It’s the first moment of price discovery, usually on thin liquidity, usually at peak attention. Supply coming online after that initial moment matters a lot. Not primarily from recipients selling, but from the unlock schedules.

Optimism’s token distribution illustrates this structure. Roughly 29 to 31% of OP supply is insider allocation, with multi-year vesting behind a relatively small initial float. The airdropped portion looked meaningful in isolation. Against total supply and the tokens still locked, it is simply not. When this pattern plays out, you see the fallout months later, as price weakens while supply keeps coming.

Costs. This is the least visible part of the calculation.

Transaction fees. Bridging costs. Slippage. Opportunity cost of capital tied up in protocols while you wait. Time spent monitoring, qualifying, executing. Smart contract risk of immature, unproven protocols. And the devastating hidden cost of holding tokens through a drawdown hoping for “number go back up.”

A few dollars per interaction on an Ethereum L2 adds up fast when repeated dozens of times. And most attempts don’t pay out. The winning screenshot is averaging across a lot of blank rows and zeroes that don’t get publicized.

Incentive Traps

There are three patterns worth naming.

Behavior rent. Protocols use token emissions to rent the behavior they need: trading volume, liquidity, governance participation. BLUR ran multiple seasons of airdrop emissions that drove massive NFT trading volume. Once emissions tapered and NFT volumes normalized, holders absorbed the resulting sell pressure and eventually paid for it. BLUR’s governance structure also included a 180-day freeze on fee switch voting after launch, which meant holders were prevented from enforcing mechanisms that might have boosted token value. The observable outcome: BLUR opened around $0.71 in early 2023 and was trading around $0.02 by early 2026.

Unlock shocks. Even if the initial airdrop was priced fairly, later supply arrivals can reset the price people are willing to pay. PYTH, the Pyth Network oracle token, experienced an unlock in May 2024 that increased circulating supply by approximately 105% in a single event. This unlock wasn’t hidden. It was in the tokenomics documentation the whole time. But it rarely appears in the screenshots that circulate when a token first launches. And it is simply not often properly researched and evaluated by hunters.

Distribution-day mechanics. When a large user base receives liquid inventory at once, many of them immediately sell. This is not irrational. It is the predictable outcome of distributing tokens to people whose primary interest was profiting from the tokens, not the protocol itself. Wormhole’s token fell approximately 24% within hours of its airdrop opening. It partially recovered. But the person who claimed at open and held through the initial drop did not experience the “free money” experience that many flashy screenshots imply.

These examples are common enough in the industry that they should change your default set of assumptions.

Re-evaluating

Certain conditions improve potential airdrop math: low interaction costs (i.e. per-transaction gas fees), explicit and stable eligibility criteria, transparent supply schedules with no large backloaded cliffs. And most importantly, a clear mental limit on how much time and capital you’re willing to commit before the outcome is known.

In other words: if interaction costs are near zero and supply is largely circulating at launch, the calculus changes.

Opposing conditions that destroy expected value are also readily observable: opaque and/or retroactive criteria, heavy insider allocations vesting after the TGE, repeated high transaction costs against uncertain claims, and the bad habit of treating opening price as a reference point when it is actually the most optimistic moment in the token’s life.

Final Thoughts

A calmer posture is to model an event before treating it as potential profit. If you haven’t estimated expected value, you’re not farming. You’re hoping at best, gambling at worst.

The bottom line: the math always looks better in a braggart’s screenshot than it does in a rational evaluation spreadsheet. Airdrops can be rational. Most airdrop hunting, as practiced, is not.

A note on what this post doesn’t claim

There is no standardized, peer-reviewed dataset showing exactly what percentage of major token launches trade below opening price at six months. That work requires computing from raw price and on-chain data, and the methodology varies enough that no clean public number exists. The examples above are real and sourced. They suggest a pattern. They do not prove a universal law.

That distinction matters. The goal here is to change your default assumptions, not to give you false precision to argue from.

Thank you for reading.

Unclear on something? Want a topic covered? Submit Your Questions Here

I read everything. Good questions may become future posts.

If this analysis was useful, Moondance Research goes deeper.

I publish one paid piece each week focused on structural risk, capital protection, and honest yield literacy.

Paid subscribers receive the full archive, reference-grade frameworks, and downloadable artifacts designed to spot opportunities and reduce the probability of getting financially wrecked.

Founding 100 subscribers receive permanent preferred pricing as recognition for supporting Moondance in its earliest phase.

→ You can learn more or subscribe here.

Most yield systems fail because they were built to attract capital, not to survive stress. The difference hides in plain sight until the first big deleveraging event inevitably occurs.

Protocols designed for growth have flashy marketing and optimize for optics. Protocols designed for survival have guardrails and optimize for fortitude. The first looks impressive until real-world stress arrives. The second looks boring until all hell breaks loose in the market.

This post will explain the structural features that separate yield systems that remain operational across market regimes from those that collapse, pause, or require emergency intervention when volatility arrives.

What “Operational Viability” Means

A yield system is operationally viable if it can continue functioning through a major deleveraging event without:

• Emergency governance overrides

• Pausing user withdrawals or core functionality

• Rule changes introduced after losses begin to pile up

• External bailouts or propping up by sponsors

This is not about safety of user funds. Viable systems can still harm users badly. Aave remained operational during March 2020 while liquidating users at scale. MakerDAO continued functioning while allowing vault holders to lose everything to zero-bid auctions.

So… “operational viability” does not mean users are protected. It means the machine keeps running. The mechanism executes under high stress levels instead of short-circuiting.

This matters because most yield in crypto is implicitly or explicitly conditional. It exists only because certain assumptions hold. If/when those assumptions break down, users quickly discover whether they were participating in a durable financial protocol or a subsidy program that required stable conditions to stay afloat.

Read more

Most crypto projects fail the same way.

A team raises money through a token. They promise governance rights and future utility. They pay early users in emissions. The token launches at an inflated valuation.

Eighteen months later, the token is down >80%. The team blames “market conditions.” Users realize the yield was always temporary.

I’ve watched this pattern repeat since I got into crypto in 2017. It is now documented at scale.

In 2025, 84.7% of major token launches traded below their opening price. The median drawdown was 71%. Over half of all tokens launched since 2021 no longer trade at all.

The SEC has named governance tokens (including BNB, ADA, MATIC, etc.) as unregistered securities in active enforcement cases. Courts have repeatedly ruled that when buyers expect profit from a team’s ongoing efforts, that’s an investment contract under U.S. securities law.

The regulatory risk isn’t theoretical. It’s being litigated right now in federal court.

A Simple Durability Test

When evaluating a DeFi system, four basic questions apply:

1. Does revenue exist without issuance of a new token?

2. Does yield persist if token emissions stop tomorrow?

3. Would the system survive an 80% token drawdown?

4. Could it function and profit without custody of user funds?

If the answer to any of these is no, the design is dependent on a variable outside its control. Dependency is not automatically fatal, but it must be acknowledged.

Durability in crypto rarely comes from clever token design. It comes from boring economics:

• Fee revenue

• Clear ownership boundaries

• Limited regulatory exposure

• Incentives that survive price volatility

What I Won’t Build, Part 1: A Governance Token

I will not issue a token to raise capital or reward early supporters.

Many governance tokens function economically as investment contracts, regardless of how teams label them. The economic structure creates securities risk whether or not founders acknowledge it.

When you buy a token expecting the founding team to build the protocol, grow the ecosystem, and create value that accrues to token holders, you’re participating in an investment contract. The spin doesn’t matter. The economic reality and the law very much do matter.

Courts have repeatedly ruled that governance tokens structured as investment contracts violate securities law. No new token design can change that reality.

What I Won’t Build, Part 2: An Inflationary Yield Protocol

I will not build a protocol that pays 50+% APY in its own token while diluting holders.

Real yield comes from real, well-executed economic opportunity: fees, trading activity, lending spreads, arbitrage, etc. Fake yield comes from printing tokens faster than economic activity can support. When demand slows, dilution dominates.

This publication will explore and explain where sustainable yield exists and how to identify it. I won’t participate in creating temporary yield to bootstrap a product, leaving users holding worthless tokens six months later.

What I Won’t Build, Part 3: Centralized Custody

I will never hold user funds or operate as an intermediary.

Any yield-related products I build will either be self-hosted tools users can run on their own infrastructure or read-only intelligence surfaces. Users will always control their keys, their configuration, their execution, and their decisions.

Moondance will avoid operating in regulatory categories that carry custody or intermediary liability.

What I’m Exploring Instead

Solana tooling and analytics infrastructure are maturing fast, but there are still significant gaps in how operators track risk, monitor governance changes, identify sustainable yield opportunities across protocols, see the full (non-protocol-dashboard) truth behind positions and transactions, etc.

Beyond my commitment to writing Moondance Research, I’m actively investigating the feasibility of building novel DeFi tooling to fill those gaps in the Solana ecosystem.

The idea is to make Solana DeFi safer and more transparent for operators who want to participate in good faith. I’m exploring areas like governance monitoring, risk aggregation, and incentive transparency.

What This Means

Future Moondance ecosystem products will follow the same model as Moondance Research: my income will accrue from users who decide that paying for intelligence/capability is in their own self-interest. Not from shared speculation on a new token.

A large, successful, sustainable blockchain intelligence industry already runs this way. Real companies make money by providing new value to the market, not by issuing governance tokens. That same structure will translate and work for advanced Solana DeFi tooling.

Moondance Research will continue to focus on:

• Where legitimate crypto yield comes from

• How to identify structural risks before deploying hard-earned capital

• Why nearly all high-APY opportunities are actually extraction schemes

• Which DeFi mechanisms produce sustainable returns and which do not

My writing assumes that you’re an adult who can handle nuance. I don’t tell you what to buy or promise returns. I expose you to frameworks for thinking deeply about opportunity and risk.

Subscribers will be among the first to know about new projects as they come to fruition.

Thank you for reading.

Unclear on something? Want a topic covered? Submit Your Questions Here

I read everything. Good questions may become future posts.

If this analysis was useful, Moondance Research goes deeper.

I publish one paid piece each week focused on structural risk, capital protection, and honest yield literacy.

Paid subscribers receive the full archive, reference-grade frameworks, and downloadable artifacts designed to spot opportunities and reduce the probability of getting financially wrecked.

Founding 100 subscribers receive permanent preferred pricing as recognition for supporting Moondance in its earliest phase.

→ You can learn more or subscribe here.

Most DeFi systems go out with a whimper rather than a bang. They don’t explode. They decay quietly, while functioning as designed.

This is not a problem code audits will catch. It is not primarily a governance failure. It is structural.

Users watch total value locked (TVL) rise, fees accumulate, and dashboards confirm system health while the returns they’re bragging about become steadily unsustainable. By the time decay is obvious, value has already transferred. The system worked. The users lost.

Failure vs. Decay: Two Different Threat Models

People expect DeFi failure to look like:

• exploits

• oracle manipulation

• governance attacks

• smart contract bugs

Those are visible events. Media post-mortems abound. Users gossip about what all broke.

Decay looks different:

• yields compress gradually

• token incentives taper

• liquidity migrates

• participation economics shift

The system continues operating. Users continue earning. But the economic foundation erodes beneath stable surface metrics.

Audits provide confidence in code correctness. Uptime proves chain/protocol reliability. But neither metric can measure whether your returns will look the same in six months.

Code Correctness Does Not Ensure Outcome Durability

A protocol can execute flawlessly while the economics supporting it shift under your feet.

Consider:

• Lending markets function perfectly while auto-calculated interest rates compress to unworkable levels

• Liquidity pools execute swaps correctly while impermanent loss (IL) accumulates

• Governance votes pass while voter turnout collapses

• Yield aggregators compound rewards while those rewards lose purchasing power

The system behaves as programmed. User outcomes deteriorate anyway. These are not exceptions.

Incentives outlive initial conditions.

Early participants receive subsidized returns funded by token emissions or promotional budgets. Late participants receive whatever the underlying activity generates, often far less.

The protocol did not lie. The initial design assumptions expired. The subsidies, as they always do, went away.

Design assumptions have shelf lives.

Protocols launch assuming sustained user growth, stable or increasing token prices, predictable fee generation, and continued liquidity provision.

When these assumptions don’t hold up under real-world stress, the system (i.e. “the code”) continues executing. Returns decay to match the new reality.

No exploit occurred. No governance vote failed. The environment changed. The protocol adapted mechanically. When this happens, users absorb the financial loss.

Read more

Moondance Research Special Bulletin. Feb 7, 2026.
Event-driven analysis outside the regular publishing cadence.

February 5, 2026 was the largest single-day Bitcoin drawdown since November 2022.
This post will examine mechanical stress propagation, not sentiment. The focus will be price action, leverage unwinds, ETF flows, infrastructure behavior, and yield mechanics.

This is not a failure analysis. It is a stress-routing analysis.

Price Action: Just the Facts

Bitcoin’s intraday price range on February 5 extended from a high near $70,000 to a low between $60,000 and $61,000, depending on the exchange and timestamp used.

Reported single-day declines range from approximately 11% to 17%, depending on the measurement window used.

MarketWatch (FactSet) reported an 11% decline measured from the prior close. Yahoo Finance and CNBC reported declines near 13%. Bloomberg referenced prices falling below $61,000, corresponding to approximately 15–17% from intraday highs.

These figures are not contradictory. They reflect different reference points within a continuous 24/7 market.

Sources: MarketWatch (FactSet), CNBC, Bloomberg, Yahoo Finance, Reuters¹

Full news summary and deep dive analysis available to paid subscribers after the jump.

→ Subscribe here.

Read more

Understanding where yield comes from is step one.
Understanding how/when it can persist is step two.
That’s what I’ll be discussing in this post.

Many naive, starry-eyed crypto participants (including me - back in the day) evaluate yield by looking at APY.
Some more savvy investors study protocol mechanics or source code.
But very few know to ask the most important question:

What has to stay true for this to keep working?

That question is the key difference between exposure that adapts with conditions vs. exposure that is sadly dependent on fragile mechanisms.

(You may have heard the Sunday school song about the wise man who built his house upon the rock and the foolish man who built his house upon the sand. If the metaphor fits…)

This post will identify three common conditions to watch for when trying to assess whether your DeFi yield will persist or falter. And how to recognize which of them you - and your money - are operating under.

The Three Conditions

Condition A: Demand-Funded Continuity

What it is
Yield persists as long as there is ongoing demand for the underlying service.

Structural characteristics

• payment comes from users who require the service

• yield does not depend on inflationary token emissions

• continuation of yield does not require new participants

• yield scales with usage rather than growth

When it persists
As long as the underlying activity continues to be valued by the market.
If people trade less, borrow less, or use the network less, yield declines proportionally.

The mechanism itself does not break simply because demand declines.

When it falters
When a system becomes obsolete, a network or protocol ceases to operate, or when alternatives emerge that cause material disruption.

Examples (illustrative structures, not endorsements)

• validator staking rewards (persist for as long as the network operates and staking rewards are legal)

• swap fees in active trading pairs (persist for as long as traders keep trading)

• borrowing interest in lending protocols (persist for as long as borrowing demand exists)

Key insight
Demand-funded yield does not require infinite growth.
It does require continued use.

Condition B: Incentive-Driven Temporality

What it is
Yield persists as long as a protocol chooses and is economically able to effectively subsidize participation.

Structural characteristics

• payment comes from inflationary token emissions or limited treasury assets

• yield often depends on protocol-defined incentive schedules

• continuation is a policy decision, not a metrics-driven outcome

• yield magnitude can fluctuate independently of activity or usage levels

When it persists
As long as incentive programs remain active under current parameters.

When it falters
When emissions taper as scheduled, when incentive budgets are exhausted, or when governance removes subsidies.

Examples (illustrative structures, not endorsements)

• liquidity mining programs paying for deposits in a separate token

• bonus yields associated with staking derivatives

• protocol launch incentives during bootstrap phases

Key insight
Incentive-driven yield is (most often) intentionally temporary.
It is designed to influence behavior to establish traction during a specific phase, not to function indefinitely.

The relevant questions do not revolve around whether subsidies are “sustainable,” but rather around how long the protocol intends to pay them, and the long-term tokenomics of what is paid out.

Condition C: Flow-Dependent Fragility

What it is
Yield persists only for as long as new participants continue depositing.

Structural characteristics

• payment comes from new deposits rather than from service fees or protocol budgets

• continuation depends on user-base growth rather than feature usage levels

• mechanisms destabilize rapidly when new inflows slow or collapse

When it persists
Only for as long as new participants enter at a rate sufficient to fund payouts to existing participants.

When it falters
When new user deposits slow, when market conditions change, or when participant confidence declines.

Failure is often non-linear: the system can appear stable until conditions suddenly shift.

Examples (illustrative structures, not endorsements)

• reflexive token models where prospective APY depends on price appreciation

• yield structures tied directly to TVL (total value locked) growth

• mechanisms where yield depends on expanding leverage parameters and liquidation activity

Key insight
Flow-dependent mechanisms require continuous expansion.
Because growth is finite, these structures are inherently fragile.

The relevant question is not whether the yield is currently working, but what happens when inflows stop.

Applying the Framework

Same Protocol, Different Conditions

Many protocols contain multiple yield components operating under different conditions.

Example: a lending protocol (illustrative structure)

• Borrowing interest — Condition A (demand-funded continuity)
  Persists as long as borrowing demand exists.

• Protocol incentive rewards — Condition B (incentive-driven temporality)
  Persist only while emissions or incentive programs remain active.

Separating these components allows persistence to be evaluated independently.

Same Mechanism, Different Contexts

The same mechanism can exhibit different persistence characteristics depending on context.

Example: liquidity provision (illustrative structure)

• In an established, high-volume pool:
  Swap fees reflect ongoing trading demand (Condition A).

• In a new or low-volume pool with incentives:
  Most yield derives from emissions rather than fees (Condition B).

The action is the same.
The persistence profile is not.

Questions to Ask

When evaluating yield persistence, ask:

• What funds the yield?
  Service fees, protocol incentives, or participant inflows?

• What has to stay true for it to continue?
  Continued usage, continued subsidies, or continued growth?

• What happens if conditions change?
  Will yield decline gradually, or will the mechanism fail rapidly?

• What stops if incentives end?
  Can temporary and durable yield be cleanly and logically separated?

If these questions cannot be answered, the persistence profile of the yield is not understood.

How This Framework Is Used

This framework does not predict outcomes.
It classifies persistence conditions.

It allows yield to be evaluated based on:

• dependency structure

• continuation requirements

• observable failure modes

This enables clearer analysis without reliance on price forecasts or performance projections.

Final Thought

Crypto yield operates under one of three structural conditions:

• Demand-funded continuity — persists with ongoing usage

• Incentive-driven temporality — persists with active subsidies

• Flow-dependent fragility — persists only with continued inflows of users and/or capital

Each behaves differently as conditions change.

Understanding which condition(s) govern a yield mechanism allows persistence to be evaluated explicitly. Not by headline APY, but by structural resilience.

Thank you for reading.

Unclear on something? Want a topic covered? Submit Your Questions Here

I read everything. Good questions may become future posts.

If this analysis was useful, Moondance Research goes deeper.

I publish one paid piece each week focused on structural risk, capital protection, and honest yield literacy.

Paid subscribers receive the full archive, reference-grade frameworks, and downloadable artifacts designed to spot opportunities and reduce the probability of getting financially wrecked.

Founding 100 subscribers receive permanent preferred pricing as recognition for supporting Moondance in its earliest phase.

→ You can learn more or subscribe here.

In modern crypto, user risk is the dominant risk.

Not exploits.
Not bugs.
Not protocols.

Users lose money because they misunderstand how systems work. And systems do work.

Why This Sounds Wrong

Most assume that protocol risk is primary.
That audits equal safety.
That exploits (supposedly executed by a team of super-coders in a dark room) are the main danger.

This is a visibility problem.

Exploits are dramatic and legible when they do happen.
They generate headlines and post-mortems.

User error is diffuse and boring.
It happens one wallet at a time.
It hides in aggregate statistics.

The industry measures what appears dangerous.
It ignores the real losses.

The Evidence

In September 2024, Radiant Capital lost roughly $50 million.

The protocol was audited.
The code behaved as designed.
No smart contract bug was exploited.

Developers received a malicious PDF via Telegram.
The file contained malware.
Transaction signatures were captured.
Funds were drained.

Code: correct.
Audits: passed.
Users: drained.

Radiant is not an outlier.

Read more

Most people treat a security audit of a crypto protocol like a gold-star safety certification.

It is not.

An audit is a report on code behavior at a specific moment in time.
It describes whether the code behaves as specified under the conditions tested.

It does not tell you:

• whether the business model is sustainable

• whether incentives remain aligned over time

• whether the team will change the code later

• whether the economic design creates hidden risks

• whether users will interact with the system as intended

• whether any affiliated token introduces regulatory exposure

Confusion on these points costs people money.

Why the Misconception Persists

Security audits in traditional finance carry regulatory weight.
They are tied to enforceable standards and ongoing accountability.

In crypto (as of this writing in Jan. 2026), things… don’t work that way.

Anyone can commission an audit.
The scope is defined by the party paying for it.
Auditors carry no ongoing liability if the protocol fails.
The code can change immediately after the report is published.

The word “audited“ signals professionalism.
It implies oversight.

In practice, it merely means:

• The team paid for third-party review

• The code matched the specification at the time

• No critical vulnerabilities were found within the tested scope

That last part matters. The tested scope is almost always narrower than users assume.

What an Audit Actually Covers

A typical smart contract audit examines:

• Code correctness

• Known vulnerabilities

• Behavior under some edge case inputs

Auditors do not evaluate:

• Economic sustainability

• Governance control and upgrade risk

• Incentive design and extraction paths

• External dependencies

• User behavior under stress

• Regulatory exposure

An audit might confirm that a liquidation mechanism executes as written.

It does not tell you whether collateral assets are correlated.
It does not tell you whether liquidations will clear during a crash.
It does not tell you whether an oracle price feed will fail when volatility spikes.

Those are system design and integration questions.
Audits are just code reviews.

The Scope Problem

Crypto audits are almost always scoped by the client.

Scope often excludes:

• the frontend users interact with

• governance modules controlling upgrades and parameters

• funds routed through third-party routines

• dependencies inherited from other protocols

Even within scope, time and budget are constraints.

Auditors may have days or weeks to review code written over months.
High-severity issues are flagged.
Lower-priority issues are documented.

What actually gets fixed is entirely up to the team.

The presence of an audit tells you nothing about what may have been omitted.

What Changes After the Audit

Code often does change after an audit.

Upgradeable contracts allow teams to modify logic and/or parameters without triggering a new review.

The original audit language may remain public even when production code no longer matches it.

This is not automatically malicious; upgrades can be necessary.

But it means the touted audit may describe a system that no longer exists.

Even without upgrades, protocol behavior may change based on:

• governance votes

• market regime shifts

• userbase changes

• liquidity migration

Audits capture a snapshot.
They do not model system evolution.

The Incentive Layer

Most protocol failures are not code exploits. They are incentive collapses.

Examples:

• yield driven by emissions that decay faster than trust

• liquidity structures that depend on continuous inflows

• governance systems vulnerable to concentration

• treasury extraction framed as “community decisions”

These are design failures.
They reflect shady human behavior.
They are invisible to static code review.

Code audits do not catch them because they are not bugs.

How to Think About Audits

Crypto audits are useful.

They reduce the probability of catastrophic code failure.
They indicate a minimum threshold of seriousness.

They are not guarantees.

An audit should be treated as one input among many.

Other inputs matter more:

• who is in control of upgrades and pauses

• how parameters are changed

• which external systems the protocol depends on

• how value flows to the team

• whether the protocol has survived stress

• what happens when growth stops

Audits answer a narrow question.
They do not answer the primary question: “Is this safe?”

What This Means Practically

“Audited” is baseline hygiene.
It is not evidence of safety.

Before interacting with a protocol:

• read the audit and check the scope

• verify whether the code has been changed since

• identify who owns the code

• evaluate the economic model separately

• consider whether it has operated under high-stress conditions

• look for evidence of compliance with applicable laws and regulations

If any of this information is unavailable, that is itself a signal.

Categorical Error

An audit reduces one class of risk.
It does not eliminate risk.

Treating “audited” as synonymous with “safe” is a categorical error.
It assumes that code correctness is the dominant failure mode in crypto systems.

It rarely is.

Most losses come from incentives, governance, economics, or user behavior.
Audits are not designed to evaluate those.

Crypto audits are tools.
And tools only function when used with sound judgement.

Thank you for reading.

Unclear on something? Want a topic covered? Submit Your Questions Here

I read everything. Good questions may become future posts.

If this analysis was useful, Moondance Research goes deeper.

I publish one paid piece each week focused on structural risk, capital protection, and honest yield literacy.

Paid subscribers receive the full archive, reference-grade frameworks, and downloadable artifacts designed to reduce the probability of getting financially wrecked.

Founding 100 subscribers receive permanent preferred pricing as recognition for supporting Moondance in its earliest phase.

→ You can learn more or subscribe here.

Most crypto risk frameworks are useless.

They list categories then stop.

No weighting. No interaction effects. No operational guidance.

People don’t lose money to “risk” in the abstract.

They lose it to specific, recurring failure modes.

Between 2020 and 2024, counterparty failures alone destroyed over $50 billion in user funds. Code exploits were a rounding error by comparison.

This post classifies those modes so you can name what you’re actually exposed to.

The Three Risk Layers

Crypto risk operates on three distinct layers:

Read more

Yield is the gravitational center of crypto.

It is how DeFi systems attract users.

It is how risk is softened.

It is how fragility is often ignored.

Most people never ask a basic question:

Where does yield actually come from?

Before you can evaluate yield, you have to classify it.

Definition

For readers new to the term: “yield” is the return you receive over time for allowing someone else to use your money or assets.

What “Yield” Usually Means

Outside of crypto, yield is boring.

It comes from:

• lending money

• business activity

• fees for real services

It usually corresponds to:

• time

• risk

• or economic output

Crypto uses the same word, but it often means something else entirely.

A Note on Speculation

Speculation is the most common source of returns in crypto.

It is also the most misunderstood.

Buying something with the expectation that it can be sold later for more is not yield.
It is a belief about future transfer.

Speculation is not fake.

It is just not a consistent or predictable source of returns.

When returns depend on someone else paying more later, new value is not being created. It is being passed along from one holder to the next.

With that distinction in mind, we can talk about where crypto “yield” actually comes from.

The Three Sources of Crypto Yield

Almost all crypto yield falls into one of three categories.

1. Transfer

Transfer-based yield comes from other participants.

It includes:

• trading losses

• liquidation penalties

• forced exits

• uneven fee distribution

This is common in:

• leveraged trading venues

• liquidation-driven lending systems

• fee redistribution models

In these systems, one person’s yield is another person’s loss.

Transfer-based yield is not fake.

It is competitive.

Examples of transfer-based yield (structural examples, not endorsements or recommendations):

• Uniswap v3 LP fees (funded by trader losses to volatility and slippage)

• Aave liquidation penalties (paid by over-leveraged borrowers)

• GMX trader losses (redistributed to liquidity providers)

2. Subsidy

Subsidized yield is paid for, not earned.

It comes from:

• token emissions

• treasury reserves

• investor capital used to buy usage or liquidity

Subsidies are often used to bootstrap activity in a protocol’s earliest days.

The problem arises when temporary subsidies are mistaken as permanent.

Subsidized yield can look identical to real yield at first.

It feels stable until it isn’t.

When the subsidy ends, yield often disappears with it.

Examples of subsidized yield (structural examples, not endorsements or recommendations):

• Curve’s CRV token emissions (paying LPs to attract liquidity)

• Blur’s BLUR token rewards (paying traders to use the platform over competitors)

• Most “liquidity mining” programs (temporary incentives funded by treasuries)

3. Extraction

Extraction-based yield comes from asymmetry.

It relies on:

• uneven information

• opaque fee structures

• preferential access or exits

• governance arrangements that favor some participants over others

This shows up in systems where:

• insiders exit differently

• operators have priority

• risk is distributed unevenly

Extraction often looks like yield until you ask who is paying.

Examples of extraction-based yield (structural examples, not endorsements or recommendations):

• Tokens with asymmetric vesting (insiders unlock early, retail locked long-term)

• Protocols with admin keys that can change fee structures mid-flight

• Systems where governance voters extract value from non-voting token holders

Where Real Yield Actually Exists

Real yield does exist in crypto.

It is usually:

• smaller

• capacity-constrained

• sensitive to conditions

• tied to real fees or demand

It tends to compress over time as competition increases.

It rarely scales cleanly.

It is rarely exciting.

Real yield often looks disappointing next to advertised yield.

That is usually the point.

Why High APY Is the Wrong Signal

High APY is easy to display.

The better questions are:

• Who is paying this?

• Why are they paying it?

• What changes when conditions change?

Most DeFi systems blend multiple sources.

A pool might offer:

• 2% from real activity

• 8% from subsidies

• 15% from governance token speculation

The dashboard shows 25%.

The real return might be negative.

Understanding yield explains why people enter systems.

It does not explain why they lose money.

What to Ask

Before evaluating yield, classify it:

• Where does this come from?

• Who is paying for it?

• What happens when conditions change?

Most high yield is subsidy or transfer dressed as sustainability.

Understanding the difference is the first filter that matters.

Thank you for reading.

Unclear on something? Want a topic covered? Submit Your Questions Here

I read everything. Good questions may become future posts.

If this analysis was useful, Moondance Research goes deeper.

I publish one paid piece each week focused on structural risk, capital protection, and honest yield literacy.

Paid subscribers receive the full archive, reference-grade frameworks, and downloadable artifacts designed to reduce the probability of getting financially wrecked.

Founding 100 subscribers receive permanent preferred pricing as recognition for supporting Moondance in its earliest phase.

→ You can learn more or subscribe here.

Most crypto writing starts with eyes on investment opportunity.

Moondance Research starts by asking why and how systems fail.

Not because crypto system failure is interesting (though it often is).
Because it is predictable.

For every crypto project or platform that has achieved some degree of “success,” many hundreds or thousands have failed.

This page explains how Moondance methodically thinks about risk and how our thinking informs our practical research/evaluations.

The First Question

What will break first?

Not in the whitepaper.
Under pressure.
With real users’ real money.

If you cannot answer that cleanly, nothing else matters.

Five Filters

1. Who gets hurt if this is misunderstood?

Good systems survive confusion.
Bad systems punish it.

If ordinary use/misuse leads to liquidation, loss, or slow bleed of user funds, that is not user error. That is structural design.

Example: Borrowing against volatile collateral where a 10% price drop triggers automatic liquidation. Users think they're "lending," but they're actually betting they can exit before the market moves.

2. What incentives are actually doing the work?

Ignore flashy dashboards. Ignore gaudy APRs.

Ask instead:

• Who gets paid early?

• Who bears downside quietly?

• Who can easily leave when conditions change?

Incentive structures predict outcomes better than narratives.

Example: A protocol offers 50% APY in its own governance token. Early participants earn and sell. Late participants hold bags when the token price collapses. The yield wasn't real. It was a transfer from latecomers to early exiters.

3. Where will this fail under stress?

Most systems appear reasonable under calm market conditions.

It takes stress to reveal what needs to be known about structure and design.

Liquidity dries up. Governance freezes. Oracles wobble. Subsidies vanish.

Bank runs happen in crypto.

If a system needs perfect conditions to function, it was already broken at launch.

Example: A "stable" pool works fine until everyone tries to withdraw at once. Suddenly there's not enough liquidity to honor exits, and users who move slowly lose 20-40% trying to get out.

4. How will yield decay over time?

Time is the least discussed risk in crypto.

Yield compresses. Attention moves on. Governance centralizes. Complexity accumulates.

If a design assumes permanent user excitement, it is riskily borrowing future credibility from the present.

Example: A new protocol launches with 80% APY funded by token emissions. Six months later, the tokens are worth 70% less and user deposits have dried up. The nominal yield is still "80%," but the real return is deeply negative.

5. What is being left unsaid?

This is often the loudest signal.

Vague language. Missing downside scenarios. Deferred decisions. Hand-waved governance.

When something important is omitted, it is usually intentional.

Example: Documentation explains how to deposit and earn, but never mentions withdrawal delays, lockup periods, or what happens if the protocol's partner chain goes offline. The gaps tell you where the risk lives.

Our Defaults

These are not hot takes. They are starting assumptions for how the crypto universe functions.

• Most yield is temporary or cosmetic

• Some yield is real but fragile

• User behavior determines outcome

• Governance rarely has the muscle to fix structural flaws in design/code

• Time will expose what incentives hide

We are skeptical first, curious second, and impressed last.

How to Read Moondance Research

My posts are not written to convince you to take any particular action.

I want to help you think clearly enough to decide when not to act.

If a post leaves you calmer, slower, or more selective, it worked.

If it makes something feel less urgent, that is not an accident.

What to Expect

Free posts go out Thursdays. Paid intelligence briefs go out Sundays.

This framework will inform upcoming posts on protocol sustainability, yield decay patterns, and governance failure modes.

Final Note

Moondance Research is not about being first at the table to feast on new yield “innovations.”

It’s about being able to say that I (and you) were wrong as seldom as possible when we look back.

If that matches your interest, you are in the right place.

If this analysis was useful, Moondance Research goes deeper.

I publish one paid piece each week focused on structural risk, capital protection, and honest yield literacy.

Paid subscribers receive the full archive, reference-grade frameworks, and downloadable artifacts designed to reduce the probability of getting financially wrecked.

Founding 100 subscribers receive permanent preferred pricing as recognition for supporting Moondance in its earliest phase.

→ You can learn more or subscribe here.

Not because everything in the space is useless, but because hype, false certainty, and rapid launches are rewarded more than good judgment and sober protocol design. Moondance Research exists for those of us who are done settling for that tradeoff.

This is a publication about capital protection, structural risk, and honest yield literacy in crypto.

It’s worth being explicit about what this is - and what it is not.

What This Is

Moondance Research is a paid crypto intelligence publication focused on capital protection, structural risk, and honest yield literacy.

I help readers:

• avoid losses driven by hype, bad incentives, and hidden risks

• understand where crypto yield actually comes from when it’s real

• think clearly about structure, incentives, and failure modes

• develop judgment instead of chasing narratives

My outlook is deliberately risk-first and incentive-aware.

Complexity is treated as risk.
Incentives are examined closely.
Attractive possibilities are questioned before they’re accepted.

When something looks appealing, the first question is not “what’s the potential return?”

It’s “what all has to go right for this not to crash and burn?”

How Yield Is Treated Here

Making money matters. Understanding how it’s made matters more.

Most crypto yield exists because someone else is paying for it. Often temporarily. Often indirectly. Often under assumptions that don’t hold for long.

Riding waves of speculation is not a sustainable strategy.

Here, yield is analyzed with a simple framework:

• Where does it actually come from?

• Who bears the risk?

• What changes over time?

• Under what circumstances will it stop working?

Sometimes the conclusion will be: this makes sense under certain conditions.
More often, the conclusion will be: this will work until it doesn’t.

Both outcomes are useful for building crypto literacy.

What Subscribers Get

Free subscribers receive weekly explanatory posts on crypto and DeFi fundamentals.

Paid subscribers receive one intelligence brief per week, plus deeper essays and risk memos.

The goal is not entertainment.
The goal is clarity you can use to protect capital and make better decisions.

What This Is Not

Moondance Research is not:

• financial advice

• investment recommendations

• a signal service

• a token promotion outlet

• a prediction engine

You will not see:

• sponsored token shilling

• price targets

• portfolio allocations

• performance screenshots

• urgency language

• promises of access, returns, or upside

If those are the things you’re looking for, this is not the right publication.

Tone and Approach

This publication is intentionally calm.

There is no urgency language, because urgency is how investors stop thinking clearly.
There are no predictions, because false confidence about the future is cheap and common.
There is no hype, because hype is always a liability when real money is involved.

The goal is not to go viral.
The goal is to become a trusted resource for those who prefer making money over losing it.

Who This Is For

This is for people who:

• want to understand crypto without getting caught up in tribalism

• care more about not losing money than getting rich quick

• value clarity and insight over entertainment

How to Subscribe

Moondance Research’s success will be measured by trust and retention, not virality.

If this resonates, you’re welcome to subscribe. If it doesn’t, that’s fine too.

Clarity matters more to me than conversion.

-Dean
Founder / Editor, Moondance Research

If this analysis was useful, Moondance Research goes deeper.

I publish one paid piece each week focused on structural risk, capital protection, and honest yield literacy.

Paid subscribers receive the full archive, reference-grade frameworks, and downloadable artifacts designed to reduce the probability of getting financially wrecked.

Founding 100 subscribers receive permanent preferred pricing as recognition for supporting Moondance in its earliest phase.

→ You can learn more or subscribe here.