Governance

Anchor document

https://raw.githubusercontent.com/WillNorrisDRep/CaradanoDRepWillNorris/main/StrikeNoVote.json
Hash matches the chain Open original

Rationale

I am voting NO on the Strike Finance Liquidity Deployment proposal. This is not a vote against Strike Finance, Cardano DeFi, perpetual futures, or productive treasury thinking. Strike has built a real product with meaningful traction, and I recognise the argument that deeper stablecoin liquidity could support more Cardano-native trading activity. However, I do not believe this is the right use of the Cardano Treasury at this time. The proposal requests 9,000,000 ADA to be sold for USDM and deployed into Strike Finance V2 liquidity infrastructure for 12 months. Although the proposal is structured as a returnable deployment rather than a grant, it still exposes treasury assets to material risk, including ADA price appreciation risk, stablecoin risk, smart-contract risk, yield underperformance, custody risk and market-making risk. My concern is also one of precedent. I am not comfortable with the Cardano Treasury becoming an active liquidity allocator into a derivatives venue. That is a materially different function from funding open-source public goods, security-critical infrastructure, developer tooling, wallet maintenance, protocol readiness or clearly scoped ecosystem infrastructure. In the current NCL environment, I believe DReps need to be especially disciplined. The NCL is a ceiling, not a spending target. Treasury capacity should be prioritised for proposals with broad public-good value, direct ecosystem utility, limited downside risk and clear long-term benefit to Cardano. Strike may be valuable to the ecosystem, but this proposal asks the Treasury to take on risk that I do not think is appropriate for a public treasury at this stage. The potential return does not outweigh the governance, precedent and capital-risk concerns for me. For these reasons, I vote NO.

Document

Hash (BLAKE2b-256)
8ff2442d6477cd7267cb363842c44bab7d168ca5397bcd861a0dccf94e3dfced
Hash on chain
8ff2442d6477cd7267cb363842c44bab7d168ca5397bcd861a0dccf94e3dfced
Raw JSON-LD
{
  "type": "FuegoIQDRepVoteRationale",
  "version": 1,
  "drepId": "drep1ytuufvd6maykgfcp20fxgpx7g6a9z2suchqehfejwdsx8cgpx80yg",
  "governanceAction": {
    "id": "gov_action1suskjc6c4nw58c6wtmv77xe79gwj47wp4gvh9cqhhxujwxmam3cqqkz5nwj",
    "title": "Strike Finance Liquidity Deployment",
    "type": "TreasuryWithdrawals",
    "lifecycle": "Live",
    "expiryEpoch": 644,
    "url": "ipfs://QmYM4nuNZTVMiMmvCr7mntct7YE1VgWyLgxGhyfWptgFgC"
  },
  "vote": {
    "choice": "No"
  },
  "body": {
    "rationale": "I am voting NO on the Strike Finance Liquidity Deployment proposal.\n\nThis is not a vote against Strike Finance, Cardano DeFi, perpetual futures, or productive treasury thinking. Strike has built a real product with meaningful traction, and I recognise the argument that deeper stablecoin liquidity could support more Cardano-native trading activity.\n\nHowever, I do not believe this is the right use of the Cardano Treasury at this time.\n\nThe proposal requests 9,000,000 ADA to be sold for USDM and deployed into Strike Finance V2 liquidity infrastructure for 12 months. Although the proposal is structured as a returnable deployment rather than a grant, it still exposes treasury assets to material risk, including ADA price appreciation risk, stablecoin risk, smart-contract risk, yield underperformance, custody risk and market-making risk.\n\nMy concern is also one of precedent. I am not comfortable with the Cardano Treasury becoming an active liquidity allocator into a derivatives venue. That is a materially different function from funding open-source public goods, security-critical infrastructure, developer tooling, wallet maintenance, protocol readiness or clearly scoped ecosystem infrastructure.\n\nIn the current NCL environment, I believe DReps need to be especially disciplined. The NCL is a ceiling, not a spending target. Treasury capacity should be prioritised for proposals with broad public-good value, direct ecosystem utility, limited downside risk and clear long-term benefit to Cardano.\n\nStrike may be valuable to the ecosystem, but this proposal asks the Treasury to take on risk that I do not think is appropriate for a public treasury at this stage. The potential return does not outweigh the governance, precedent and capital-risk concerns for me.\n\nFor these reasons, I vote NO."
  },
  "status": "published-rationale"
}