[PRC #4] Deprecate Cronos Support

Governance
1

TL;DR

Proposal to deprecate Cronos chain support. Given the small traction and limited ecosystem/API/RPC support, I believe maintaining Cronos integration no longer provides sufficient value for our development resources.

Voting

  • Mode: Stewards
  • Duration: 7 days
  • Veto Threshold: 10% of total voting power

Proposal

Currently, maintaining Cronos support requires ongoing development hours that I believe could be better allocated to other priorities. With minimal user adoption on Cronos and no active ecosystem partnerships in the pipeline, I see limited strategic value in continuing this integration. Additionally, the limited RPC and API support on Cronos make development and maintenance more time-consuming than on other chains.

Rather than completely removing Cronos support, I propose deprecating it by:

  1. Hiding Cronos-related features from our platform interface
  2. Pausing protocol upgrades on the Cronos chain

This approach preserves our ability to quickly reactivate Cronos support should compelling opportunities emerge in the future. If the Cronos ecosystem develops stronger infrastructure and API support, we could revisit this decision.

On-chain actions

TBC

5 Likes
2

I’d be in favor of this!

3

@ashhanai could you please help me here to specify the on-chain actions needed? is there any we need to do or we just leave it deployed/functional there from the contract perspective for the time being?

4

As PWN DAO currently governs only Ethereum, you cannot really specify any on-chain actions for Cronos. But even after it will, we can remove tags and block new loan creation, but imo it’s enough to stop supporting it on the platform.

2 Likes
5

Given the absence of traffic on Cronos, I’d be in favor of discontinuing it.

6

Executed on the platform side

2 Likes