GITBOOK-334: change request with no subject merged in GitBook

SUMMARY.md

@@ -163,7 +163,9 @@
     * [0.6.x](network/network-upgrades/2022/0.6.x.md)
   * [2023](network/network-upgrades/2023/README.md)
     * [1.x](network/network-upgrades/2023/1.x.md)
-  * [2024](network/network-upgrades/2024.md)
+  * [2024](network/network-upgrades/2024/README.md)
+    * [2.x](network/network-upgrades/2024/2.x.md)
+    * [3.x](network/network-upgrades/2024/3.x.md)
   * [Root Cause Analysis of outages](network/network-upgrades/root-cause-analysis-of-outages/README.md)
     * [v1.x upgrade RCA](network/network-upgrades/root-cause-analysis-of-outages/v1.x-upgrade-rca.md)
 

network/network-upgrades/2024/2.x.md

@@ -0,0 +1,21 @@
+# 2.x
+
+## Dependency Upgrades:
+
+* Upgrade Go version to at least v1.20, with v1.21 as the targeted latest stable.
+* Upgrade Cosmos SDK from v0.46.x (being a fork at v0.46.10, applying Barberry vulnerability patch on top, along with IAVL forked at v0.19.5 applying pruning logic patch on top) to v0.47.x (latest: v0.47.8), including relevant cosmossdk.io indirect dependencies and IAVL package.
+* The ideal outcome is removing all forks, upgrading direct, indirect dependencies to latest v0.47.x release line covering the set requirements to follow.
+* Update Comet BFT (Tendermint v0.34.26) to match Cosmos SDK’s associated version (latest: v0.37.4).
+* Update IBC from v6.1.1 to v7.x (latest: v7.3.2).
+* Test suite updates in Ginkgo BDD for connecting to the latest Osmosis, transferring tokens, and querying DID-Linked Resources through IBC.
+
+### Fixes:
+
+* Address non-operational state sync issue by assessing remediation strategies used in similar contexts.
+* Resolve non-operational pruning while retaining the panic-exit fix introduced in the forked v0.46.x compatible IAVL, exploring options for a permanent solution.
+
+### CI + Tests:
+
+* Update build, test, and release CI actions to target the latest Ubuntu LTS (latest: 22.04.3).
+* Update build, release CI actions to target latest GoReleaser (latest: v1.24.0, requires Go v1.20+).
+* Resolve possible testing suite adjustments derived from the aforementioned dependency upgrades, notably upgrade tests written in Ginkgo BDD testing framework.

network/network-upgrades/2024/3.x.md

@@ -0,0 +1,7 @@
+# 3.x
+
+The upgrade is broken down into three primary areas of development:
+
+1. **EIP-1559-Style Burn Mechanism**: Inspired by Ethereum’s model, any network transaction—whether a transfer, proof-of-stake delegation, or identity ledger update—will burn $CHEQ tokens, including “credential payments,” ensuring consistent protocol revenue via token burns.
+2. **Fee Abstraction**: Anyone with a Cosmos token can now pay for transactions on the cheqd network, with these tokens converted into $CHEQ as needed. This feature enables stable payments using tokens like USDC, EUROe, or EURC, providing greater payment flexibility.
+3. **General Burn Transaction**: A new option to burn $CHEQ tokens on demand, expanding use cases for token management.

network/network-upgrades/README.md

@@ -21,4 +21,4 @@ To ensure we upgrade all nodes on the network in the most efficient way whilst m
 
 Take a look at our network upgrades across the years, including Root Cause Analysis of any Network outage. 
 
-<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>2021</strong></mark></td><td>View our network ugrades from 2021.</td><td><a href="2021/">2021</a></td></tr><tr><td><mark style="color:blue;"><strong>2022</strong></mark></td><td>View our network ugrades from 2022.</td><td><a href="2022/">2022</a></td></tr><tr><td><mark style="color:blue;"><strong>2023</strong></mark></td><td>View our network ugrades from 2023.</td><td><a href="2023/">2023</a></td></tr><tr><td><mark style="color:blue;"><strong>2024</strong></mark></td><td>View our network ugrades from 2024.</td><td><a href="2024.md">2024.md</a></td></tr><tr><td><mark style="color:blue;"><strong>RCAs</strong></mark></td><td>View our Root Cause Analysis of Network outages.</td><td><a href="root-cause-analysis-of-outages/">root-cause-analysis-of-outages</a></td></tr></tbody></table>
+<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>2021</strong></mark></td><td>View our network ugrades from 2021.</td><td><a href="2021/">2021</a></td></tr><tr><td><mark style="color:blue;"><strong>2022</strong></mark></td><td>View our network ugrades from 2022.</td><td><a href="2022/">2022</a></td></tr><tr><td><mark style="color:blue;"><strong>2023</strong></mark></td><td>View our network ugrades from 2023.</td><td><a href="2023/">2023</a></td></tr><tr><td><mark style="color:blue;"><strong>2024</strong></mark></td><td>View our network ugrades from 2024.</td><td><a href="2024/">2024</a></td></tr><tr><td><mark style="color:blue;"><strong>RCAs</strong></mark></td><td>View our Root Cause Analysis of Network outages.</td><td><a href="root-cause-analysis-of-outages/">root-cause-analysis-of-outages</a></td></tr></tbody></table>