# ⚠️ SDK v0.53 Notice: Transaction `logs` Deprecated (Compatibility Update) With the upgrade to **Cosmos SDK v0.53 (ABCI 2.0 / CometBFT)**, the SDK no longer constructs `sdk.TxLogs`. This is an upstream change introduced with ABCI 2.0. ## What changed upstream * `logs` and `raw_log` are **deprecated and no longer constructed by default**. References: * Cosmos SDK: [https://github.com/cosmos/cosmos-sdk/pull/15845](https://github.com/cosmos/cosmos-sdk/pull/15845) * CosmJS changelog: [https://github.com/cosmos/cosmjs/blob/main/CHANGELOG.md#deprecated-4](https://github.com/cosmos/cosmjs/blob/main/CHANGELOG.md#deprecated-4) * The canonical output is now **`events`** (protocol-level ABCI events). ## What did not change * Contracts still emit events. * Events are still indexed and queryable. * **Explorers and indexers that already consume `events` are not affected.** ## ✅ Terra Classic resolution To reduce ecosystem breakage while aligning with upstream behavior: * We have added a **compatibility layer on transaction queries (`getTx`)** to reconstruct legacy `logs` from `events`. * **Broadcast responses remain unchanged** and continue to follow upstream SDK behavior (no `logs`). ## What this means * ✅ Apps that use **tx queries** should **not be affected**. They can continue to work, but are **strongly encouraged to migrate to `events`** as the canonical source of truth. * ⚠️ Apps that rely on **`logs` from broadcast responses** **will be affected**. **Resolution path:** → wait for tx inclusion → query the tx by hash → read from `events` (or reconstructed `logs` via the query compatibility layer) ## New expected usage Instead of: ```ts tx.logs[0].events ``` Use: ```ts tx.events ``` ## Impact * Legacy apps depending on `logs` from **tx queries** should continue to function. * Only apps depending on `logs` from **broadcast results** must migrate to a query-based flow. — Orbit Labs / Terra Classic Devs