SDK v0.53 Update: Terra Classic Rebel 2 Testnet Runs With Stable Core Services
The Terra Classic rebel 2 testnet has been running on Cosmos SDK v0.53.x for approximately three weeks, according to the latest developer update. During this period, core chain services have remained stable, while the network continues to undergo active testing.
This testnet configuration moves Terra Classic onto Cosmos SDK version 0.53.4 and IBC go version 10.3.0, also referred to as IBC v2. These versions represent the latest upstream releases within the Cosmos ecosystem and are widely adopted across multiple networks.
Testnet Status and Stability
The update confirms that the rebel 2 testnet has been operating continuously with the new SDK for several weeks. Core blockchain services are functioning as expected, indicating a stable test environment. However, testing remains ongoing, and the network has not yet completed the full evaluation process.
This extended testnet phase is intended to validate behavior changes introduced by the newer Cosmos SDK and IBC versions before any future production level decisions are made.
Transaction Output Behavior Change
The only ecosystem visible change identified during testing relates to transaction output behavior. With the introduction of Cosmos SDK v0.53 and ABCI 2.0, the SDK no longer constructs transaction logs. Instead, events are now defined as the canonical and protocol level transaction output.
This behavior change originates from upstream Cosmos SDK development and applies across the broader Cosmos ecosystem.
Events Replace Logs as Canonical Output
Under the new SDK behavior, both logs and raw log fields are deprecated and are no longer constructed by default. Events now serve as the official source of transaction information.
Smart contracts continue to emit events as before, and these events remain indexed and fully queryable. Blockchain explorers and indexers that already rely on events are not affected by this change.
Terra Classic Compatibility Handling
To reduce ecosystem disruption while aligning with upstream SDK behavior, Terra Classic has implemented a compatibility layer for transaction query endpoints. When transactions are queried after inclusion, legacy logs are reconstructed from events to support existing applications.
Broadcast transaction responses now follow upstream behavior and do not include logs.
Developer Impact
Applications that query transaction results after block inclusion continue to function without changes. Indexers and applications that consume events are also unaffected, as are smart contract event subscriptions.
Applications that rely on transaction logs returned at broadcast time must update their workflow. These applications are required to wait for transaction inclusion, query the transaction by hash, and read data from events or reconstructed logs.
Recommended Developer Approach
Developers are encouraged to treat events as the canonical source of transaction data and to adopt query based transaction result handling. This approach aligns Terra Classic with Cosmos SDK v0.53 and IBC v2 standards and supports long term compatibility across the Cosmos ecosystem.
Conclusion
The Terra Classic rebel 2 testnet continues to run Cosmos SDK v0.53.x with stable core services while active testing remains underway. The primary visible change involves transaction output behavior, reflecting upstream Cosmos SDK updates. Ongoing testing will further validate stability and compatibility as development progresses.
