Cowrie Research

incentive-and-market-making-quarantine-for-partially-independent-successors

13 min read

Incentive and Market-Making Quarantine for Partially Independent Successors

  • Name: incentive and market-making quarantine for partially independent successors
  • Category: lifecycle reference / successor-review note / subsidy-policy companion / residual-policy graduation checklist
  • Summary: A successor can become independent enough to permit bounded user exits or limited fresh routing before it is healthy enough for protocol-sponsored liquidity mining, market-maker support, treasury inventory seeding, or top-level growth campaigns. Those programs are not neutral discoverability; they are active balance-sheet and signaling choices that can re-normalize a still-transitional surface faster than its remaining trust edges deserve. This note exists to preserve the narrower graduation question after partial successor independence: when a replacement object has severed some old dependencies but not all of them, how should incentives, MM programs, and treasury-supplied liquidity stay quarantined so limited fresh flow allowed does not quietly become protocol wants everyone here now?
  • Why this note exists:
    • partial-successor-independence-and-graduated-residual-policy-lifting already preserves the broader graduation rule that route, treasury, collateral, and discovery privileges should come back edge by edge rather than in one binary flip.
    • residual-liquidity-segregation-and-active-tvl-hygiene already preserves the accounting-side question of how leftover balances should stop masquerading as active TVL or healthy venue depth.
    • machine-readable-residual-status-publication already preserves the policy-distribution question of how downstream systems should consume one canonical residual-status object.
    • What still deserves its own note is the subsidy and market-structure layer after some routing has already returned. A venue can be safe enough for bounded user access while still being too transitional for protocol-paid APR, treasury inventory commitments, MM loss-sharing, or liquidity-mining campaigns.
    • The analytical win is to separate some fresh flow is acceptable from the protocol should now spend money, inventory, and reputation to accelerate that flow.

The core design rule

Incentives and market-making support are stronger endorsements than route availability. Partial successor independence should not automatically unlock subsidy.

Healthy systems should not let these remain equivalent:

  • users may access this successor in bounded ways
  • the protocol should pay to attract inventory, orderflow, and growth here

The main separations healthy subsidy quarantine should preserve

  1. Bounded user accessibility versus protocol-sponsored growth

    • A successor may be acceptable for manual exits, bounded swaps, or low-priority routing before it deserves emissions, rebates, LP mining, or launch campaigns.
    • Healthy systems treat subsidy as an explicit growth decision, not as a side effect of merely re-enabling access.

  2. Third-party liquidity presence versus protocol balance-sheet commitment

    • Organic or opportunistic market makers choosing to quote a venue is different from the protocol lending them inventory, backstopping losses, or guaranteeing spreads.
    • Healthy systems distinguish someone will make a market here from the protocol itself should underwrite that market.

  3. Route eligibility versus incentive eligibility

    • A successor can deserve low-priority route inclusion while still being too dependent on old governance, release, oracle, or custody edges for incentive support.
    • Healthy systems keep can be used separate from should be promoted.

  4. Discoverability versus legitimacy-by-subsidy

    • APR banners, liquidity-mining programs, and market-maker partnerships do not just improve execution; they tell users that the protocol is comfortable concentrating more capital there.
    • Healthy systems treat subsidy as reputational endorsement, not just mechanical depth provisioning.

  5. Exit assistance versus fresh inventory accumulation

    • Sometimes a successor needs help to unwind legacy users safely.
    • That does not imply the protocol should seed large standing inventory or reward net-new deposits that increase exposure to unresolved dependency edges.
    • Healthy systems distinguish support orderly exit and migration from accumulate fresh TVL and maker inventory.

  6. Temporary transitional support versus normal venue economics

    • A transitional venue may justify a tightly bounded, time-boxed support program with explicit downgrade rules.
    • Healthy systems keep that distinct from ordinary long-run emissions, liquidity league tables, and treasury deployment assumptions.

What sound design looks like

1. Treat subsidy unlock as a later graduation stage than route unlock

  • A useful default order is:
    • manual or exit-only access
    • bounded fresh routing
    • ordinary discoverability
    • tightly capped transitional support
    • normal incentive / MM policy
  • The point is not bureaucracy. The point is recognizing that paying for flow is a stronger trust decision than merely tolerating flow.

2. Bind incentive policy to the same dependency-edge map as successor review

  • Teams should ask which old edges still remain before approving:
    • liquidity mining
    • fee rebates
    • MM inventory loans or guarantees
    • treasury LP seeding
    • foundation or DAO-owned liquidity
    • partner incentives and launch campaigns
  • If old governance, release, oracle, migration-certifier, or residual-custody edges still survive, subsidy policy should stay capped accordingly.

3. Prefer exit-completion support over growth-maximizing support

  • When a partially independent successor still needs help, the first acceptable subsidies are usually the ones that reduce harm to legacy users, such as:
    • bounded unwind liquidity
    • temporary spread support for exits
    • migration completion tooling
    • carefully scoped market-making that narrows, rather than expands, net exposure
  • Healthy systems avoid jumping straight from users still need a path out to let's farm net-new deposits here.

4. Keep protocol inventory and loss-sharing quarantined

  • Treasury-owned liquidity, MM guarantees, and inventory loans should remain separate from ordinary venue support.
  • Healthy systems cap:
    • total protocol inventory committed
    • per-market maker exposure
    • duration of support
    • asset pairs allowed
    • whether fresh borrowed demand can lean on the subsidized books
  • Otherwise the protocol turns a transitional successor into a balance-sheet concentration point before independence is really proven.

5. Publish subsidy state in the same machine-readable policy object

  • Downstream systems should not infer subsidy status from forum posts or campaign pages.
  • A strong policy object should say whether a successor is:
    • ineligible for incentives
    • eligible only for unwind / migration support
    • eligible for tightly capped transitional market-making support
    • eligible for ordinary incentive programs
  • This matters because front ends, dashboards, route scorers, and treasury tools otherwise re-normalize the venue just because a campaign exists.

6. Make transitional support time-boxed, reviewable, and reversible

  • Healthy systems name:
    • the dependency edges still blocking full normalization
    • the reason limited support is justified anyway
    • the exposure caps
    • the review date
    • the downgrade triggers
  • Transitional support should expire or re-review automatically rather than drifting into permanent normal treatment.

What sound subsidy quarantine should prove

A strong partially-independent successor regime should be able to answer:

  • Which old dependency edges still survive on this successor?
  • Why is the venue eligible for bounded routing, and why is that not yet enough for ordinary incentive support?
  • Are any support programs limited to exit completion or migration safety rather than net-new growth?
  • How much protocol inventory, treasury capital, or MM loss-sharing is still permitted?
  • Which machine-readable policy fields tell front ends, dashboards, and treasury tools that subsidy remains capped or forbidden?
  • What review event upgrades, downgrades, or ends the transitional support?

Failure-prevention checklist

  • Treat subsidy unlock as a stronger privilege than route unlock. Re-enabling bounded access, manual exits, or low-priority routing should not automatically enable emissions, maker support, rebates, or treasury seeding.
  • Bind every support program to the same dependency-edge map used for successor review. Remaining custody, oracle, migration-certifier, governance, operator, or residual-cash-out edges should directly cap what incentives are allowed.
  • Publish subsidy state as a machine-readable policy field, not a vibes-based campaign fact. Downstream routers, dashboards, treasury tools, and venue-quality views should be able to tell ineligible, exit-support only, capped transitional support, and ordinary incentives apart.
  • Distinguish unwind support from growth support. Programs justified as help old users leave safely should not quietly reward net-new deposits, leverage, or maker inventory growth that increases exposure to unresolved successor dependencies.
  • Quarantine protocol balance-sheet commitment explicitly. Treasury-owned liquidity, MM inventory loans, spread guarantees, and loss-sharing facilities should have tighter caps, shorter duration, and stronger review than ordinary user-access permissions.
  • Keep transitional support time-boxed and review-triggered. Every subsidy exception should name its cap, reason, review date, downgrade trigger, and terminal event instead of drifting into normal venue treatment.
  • Keep active-TVL and venue-quality metrics honest. Protocol-seeded transitional books should not be counted or narrated as proof of healthy independent demand while the successor still sits behind residual edges.
  • Make downstream systems share one policy story. If governance says transitional unwind support only while UIs, dashboards, or route scorers still market the venue like a normal incentivized destination, the quarantine is not real.
  • Fail closed on stale or ambiguous support status. If downstream systems cannot confirm whether a venue is still subsidy-quarantined, they should default to no fresh incentive endorsement rather than silently normalizing it.
  • Treat full incentive restoration as a new risk admission. Returning a partially independent successor to ordinary mining, treasury deployment, or MM support should require explicit proof that the old dependency story no longer justifies special quarantine.

Audit prompts

  • Which exact old dependency edges still survive on the successor today, and which of those edges specifically block normal incentive or MM treatment?
  • What support is currently enabled: exit-completion assistance, capped transitional market making, treasury inventory seeding, fee rebates, liquidity mining, or ordinary growth campaigns?
  • For each enabled support path, what is the concrete justification, cap, review date, and downgrade trigger?
  • Does the public rationale for the program say help users unwind while the actual mechanics still reward net-new deposits, larger inventory, or stronger route preference?
  • Which downstream systems consume the same subsidy-state object: front ends, route scorers, venue rankings, treasury dashboards, governance reporting, and collateral or incentive engines?
  • Are protocol-owned balances or MM-supported books still being counted as healthy independent depth, active TVL, or organic market validation?
  • If the successor lost one remaining dependency edge tomorrow, which support tier would unlock next, and what proof would be required before that happened?
  • If a hidden fallback, shared operator, or residual release path were rediscovered tonight, which programs would shut off automatically or on explicit review?
  • Could a user or integrator mistake some bounded support exists for a claim that the venue is now fully healthy, collateral-worthy, or treasury-normalized?
  • What exact event ends transitional subsidy treatment altogether rather than letting it decay into permanent normal policy by inertia?

Lessons that should already be standard

  • Subsidy is not neutral plumbing. Paying for flow, seeding inventory, or underwriting makers is a stronger endorsement than merely allowing users to access a venue.
  • Some fresh flow is acceptable and the protocol should accelerate fresh flow are different risk decisions. Healthy systems do not let route admissibility silently become growth policy.
  • Treasury inventory and MM guarantees are balance-sheet decisions, not marketing garnish. Transitional support that touches protocol capital deserves stricter review than ordinary discoverability.
  • Exit assistance and growth assistance are different products. If a venue still needs support because users are unwinding old exposure, that is usually evidence against ordinary incentive treatment, not evidence for it.
  • Market-quality storytelling can counterfeit independence. Once dashboards, APR pages, or venue rankings celebrate subsidized transitional books as healthy demand, unresolved successor risk gets socially normalized.
  • Transitional support should expire by design. If nobody can say when and why subsidy quarantine ends, teams will eventually treat the exception as the baseline.
  • One policy object matters as much here as one technical object. If campaign pages, routers, dashboards, and governance logs tell different stories about support status, the most permissive surface will quietly win.
  • Restoring ordinary incentives is a fresh admission of trust. It should require proof that the successor no longer depends on the old residual boundary in the ways that made quarantine necessary.

High-signal contrast cases

  • partial-successor-independence-and-graduated-residual-policy-lifting is the immediate upstream companion because subsidy policy should inherit the same edge-specific graduation logic rather than inventing its own looser standard.
  • residual-liquidity-segregation-and-active-tvl-hygiene is the accounting companion because subsidized books and DAO-seeded liquidity should not quietly turn transitional balances into healthy TVL storytelling.
  • machine-readable-residual-status-publication is the policy-distribution companion because subsidy eligibility has to be published as structured downstream policy, not implied by marketing or governance chatter.
  • aUSD is the rewards-side caution that supposedly marginal or deprecated incentive machinery can still carry live issuance authority and therefore deserves stricter lifecycle review than ordinary growth tooling language suggests.
  • Moonwell Moonriver is the remnant-deployment caution that a sleepy or secondary venue can still sit behind fragile governance, making any treasury or MM endorsement much stronger than its apparent strategic importance.
  • Aztec Connect is the residual-system caution that an old path may still control meaningful withdrawal truth, so downstream support should stay exit-oriented rather than growth-oriented while that residual authority survives.
  • bridge-bounded-release-design is a useful analogue because it likewise separates path remains live from path deserves uncapped value and throughput; subsidy quarantine should separate venue remains usable from venue deserves protocol-accelerated scale.

Red flags that usually mean subsidy quarantine is fake

  • APR or liquidity-mining campaigns launch as soon as a successor is no longer fully paused
  • MM support, DAO-owned liquidity, or treasury inventory appears before anyone can name the surviving dependency edges
  • route inclusion and incentive eligibility flip at the same time despite very different trust stakes
  • dashboards count protocol-seeded transitional liquidity as evidence of healthy independent demand
  • support programs reward net-new deposits even though the public rationale is still help legacy users unwind
  • no review date or downgrade trigger exists once transitional incentives start

How to use this note with the exploit corpus

Internal linkages

Control surface

Graph View

Backlinks