Source from:

• https://validator.info/terra-classic/governance/12162
• https://station.terraclassic.community/proposal/columbus-5/12162
• https://common.xyz/terra-luna-classic-lunc/discussion/26630

SDK v0.50.X Upgrade by Antier Solutions

Following orbit labs unfork we propose a chain upgrade to most recent SDK

https://common.xyz/terra-luna-classic-lunc/discussion/26630

By cookie FrgValidator and Luncvers3

SDK 0.50.x upgrade Final

Document Updated Proposal:

Terra Classic SDK & Wasm Upgrade Executive Summary This proposal outlines a secure, backward-compatible upgrade of Terra Classic’s core infrastructure to Cosmos SDK v0.50.9 and Wasm Module v0.53.2, addressing unresolved issues from the v0.47 upgrade, enhancing security, and ensuring long-term sustainability. The upgrade is contingent on Orbit Labs’ unforking completion and includes fixes for technical debt, mitigation of breaking changes, and developer-focused improvements. The proposal ensures full backward compatibility for existing dApps. Technical Specifications & Implications

1. Cosmos SDK Upgrade Current: v0.47.14 Proposed: v0.50.9 Rationale: The current version contains some security vulnerabilities. Upgrading to v0.50.9 addresses these issues comprehensively. Changes: x/params module updates (requires migration to new governance-driven parameters). x/authz and x/feegrant updates (impacts dApps using delegation/allowances). Custom module adjustments (e.g., Oracle, Market, Staking) due to SDK refactoring. Terra Classic Considerations: Ensures full backward compatibility with existing chain features and functionalities.
2. Wasm Module & Virtual Machine Current: v0.46.0 / wasmvm v1.5.8 Proposed: v0.53.2 / wasmvm v2.1.4 dApp Impact: Existing CosmWasm contracts remain functional. Contracts will adhere to the latest standards while maintaining backward compatibility with existing constraints. Terra Classic Custom Wasm Bindings Compatibility: Custom bindings for oracle, tax, and market modules will be maintained.
3. IBC-GO IBC-GO: v7.4.0 → v8.4.0 Preserves cross-chain compatibility without introducing IBC-breaking changes. Performance enhancements, optimizing relayer performance and reducing transaction latency. Future-proofing, ensuring compatibility with upcoming Cosmos chains adopting IBC v8.4.0. Security Enhancements in IBC-GO v8.4.0: Fixes a critical reentrancy attack vulnerability in IBC hooks, ensuring secure packet lifecycle management to prevent fund loss or unintended token minting. Upgrading mitigates these risks, strengthening Terra Classic’s cross-chain security
4. Terra Classic Custom Modules & Upgrade Plan Terra Classic’s custom modules require careful handling during this upgrade: Oracle Module: Manages exchange rate feeds for stablecoins. Requires compatibility testing with the new SDK structure to ensure validator price submissions remain accurate. Market Module: Facilitates stablecoin swaps. Needs parameter validation and optimization for performance under the new SDK execution model. Treasury Module: Governs economic policies, including tax rates. Must be preserved with no loss of functionality and tested under new governance-driven parameters. All the other customization that has been done in different modules like staking, slashing, mint etc., will also be upgraded. Upgrade Strategy: Detailed Unit Testing & Refactoring: Conduct unit tests on Oracle, Market, and Treasury modules to verify proper functionality under the new SDK. Identify areas needing refactoring to align with SDK v0.50.9. Backward Compatibility Layer Implementation: Develop temporary compatibility shims for x/treasury and x/market modules to avoid dApp disruptions. Ensure that existing governance parameters remain unchanged during the upgrade. Why This Upgrade?
5. Terra Classic-Specific Research Unforking Synergy: Orbit Labs’ unforking removes Terra-original patches, allowing seamless SDK v0.50 integration.
6. Risk Mitigation Backward Compatibility Layer: Temporary shims for deprecated modules to prevent dApp disruption. Security Measures: Audit by Oak Security (focusing on v0.47 → v0.50 migration). Workflow & Timeline Phase 1: Pre-Upgrade Preparation (2 Weeks) Tasks: Code audit (post-unforking), legacy issue fixes, backward compatibility documentation, testnet setup. Phase 2: Core Upgrade Execution (5 Weeks) Tasks: SDK v0.50.9 integration. Wasm Module v0.53.2 update. Custom module migration for Terra Classic’s unique features. Ensuring CosmWasm 1.0-1.5 contracts remain functional. Phase 3: Progressive Upgrades, Testing & Validation (9 Weeks) Tasks:  Setup the chain on version that supports 0.16 contracts,instantiate those contracts and then upgrade the chain progressively to v0.50.9 followed by mock testing.progressive upgrades to the chain till v0.50.9 followed by mock testing Security audits, validator dry runs, dApp migration tests, bug bounties. Phase 4: Testnet Deployment (2 Weeks) Tasks: Public testnet launch, validator/dApp onboarding, monitoring. Phase 5: Mainnet Deployment (2 Weeks) Tasks: Governance vote, CEX coordination, mainnet upgrade, post-launch monitoring. Total Timeline: 20 Weeks (~5 Months) Phase Duration Key Activities Cost

Phases

• Pre-Upgrade : 2 Weeks Audit code post-unforking, fix SDK v0.47 bugs, document breaking changes, testnet setup. $6,000
• Core Upgrade : 5 Weeks Integrate SDK v0.50.9, Wasm v0.53.2, CometBFT v0.38.11, backward compatibility layers. $25,000
• Testing & Validation : 9 Weeks Security audits, validator dry runs, dApp migration tests, bug bounties. $12,000
• Testnet Deployment : 2 Weeks Public testnet launch, validator/dApp onboarding, monitoring. $8,000
• Mainnet Deployment : 2 Weeks Governance vote, CEX coordination, mainnet upgrade, post-launch monitoring. $6,000

Following this 48h discussion this proposal will go to voting.

This proposal is being proposed by #Cookie #FRGValidator and #LUNCVERS3 team for luna classic

Upgrade being implemented by Antier Solutions

Important consideration: The wasmd upgrade can only start after the Orbit Labs “wasmd unfork” has been conducted, or alternatively in coordination with Orbit labs as part of a joint effort in combining the wasmd unfork with the sdk and wasmd upgrade.

A new Spend proposal will be submitted following Each Milestone