Canto Core Devs Meeting 10 Agenda

[bebekim]

Updating roadmap as migration into Polygon CDK has been approved.

Decisions

Need to make decision on 2 things:

1. Whether to upgrade cosmos-sdk version:

• v0.47 (upgrade)

• bring Cronos’ fork of ethermint back home a.k.a vanilla Ethermint

  • absent of stateful precompile contract
  • no custom patch on cometbft-db, cosmos-sdk

• Pro

  • MEV (additional revenue)
  • Optimistic block processing (sub 1s)

• Con

  • will not last long, less than a 0.5 year

• v0.45 (no upgrade, current-version)

  • Pro
    • Bring decentralised Polygon CDK into light faster
    • Work to bring existing Canto functionality into Polygon CDK earlier
  • Con
    • No additional features

2. Whether to put measures to mitigate security risk

• Limit outflow of capital through IBC/bridge for the benefit of RWA

Update

FYI our progress with Polygon CDK:
Polygon CDK provides L2 tech stack, allowing zk proof of L1 and trustless bridge to L1

• Shortcomings
  • sequencer is centralised
  • no verification of L2 consensus by L1
• B-Harvest’s improvement
  • decentralised block creation via cometBFT
  • L2 consensus verified by L1 zkEVM proof
  • enhanced performance and scalability

Our progress has been received favourably by Polygon CTO so far and we are confident moving forward in this direction.

Requesting update

• Any update progress of security audit on liquid staking module ?
• When's onboarding module going Mainnet?