Merge branch 'dev' into add-gas-atom

Author: smk762

.github/workflows/get_data_lint_files_deploy.yml

@@ -65,6 +65,10 @@ jobs:
       - name: Prepare data files for GPTs
         run: node utils/js/create_data_for_gpts.js
 
+      - name: Ensure change logs are updated
+        if: github.base_ref == 'main' || github.ref == 'refs/heads/main'
+        run: node utils/js/ensure_changelog_update.js
+
       - name: Set lint-fix branch name
         id: vars
         shell: bash

data-for-gpts/all-content.txt

@@ -14073,7 +14073,7 @@ ROGUE_satoshis = gold * gold * dungeon_level_on_exit * 10
 ROGUE_satoshis = gold * gold * dungeon_level_on_exit * 20
 ```
 
-The conversion is facilitated using globally locked `ROGUE` coins. The funds in this global vault automatically accrue through asset-chain activity. In the event that there are not enough globally locked funds at the time the method is executed, the player must simply wait until the funds are generated via automated methods. You can encourage this fund to grow more quickly by encouraging other players and people to transact using ROGUE, as transactions feed the fund.
+The conversion is facilitated using globally locked `ROGUE` coins. The funds in this global vault automatically accrue through smart-chain activity. In the event that there are not enough globally locked funds at the time the method is executed, the player must simply wait until the funds are generated via automated methods. You can encourage this fund to grow more quickly by encouraging other players and people to transact using ROGUE, as transactions feed the fund.
 
 The method returns a `hex` value. While most methods in the Komodo API require the user/developer to broadcast the `hex` value using [sendrawtransaction](/smart-chains/api/rawtransactions/#sendrawtransaction), the Rogue module broadcasts automatically.
 
@@ -14308,7 +14308,7 @@ In multi-player mode, the `highlander` method is available either to the charact
 
 The character that successfully executes the `highlander` method receives an increased ratio of conversion from in-game gold to `ROGUE` coins. The ratio depends upon the mode of gameplay; see below for further details.
 
-The conversion is facilitated using globally locked `ROGUE` coins. The funds in this global vault automatically accrue through asset-chain activity. In the event that there are not enough globally locked funds at the time the `highlander` method is executed, the player must wait until the funds are generated via automated methods. You can encourage this fund to grow more quickly by encouraging other players and people to transact using ROGUE, as transactions feed the fund.
+The conversion is facilitated using globally locked `ROGUE` coins. The funds in this global vault automatically accrue through smart-chain activity. In the event that there are not enough globally locked funds at the time the `highlander` method is executed, the player must wait until the funds are generated via automated methods. You can encourage this fund to grow more quickly by encouraging other players and people to transact using ROGUE, as transactions feed the fund.
 
 #### Rewards in Single-Player Mode
 
@@ -22516,7 +22516,7 @@ Make sure that the total `ac_supply` of this Smart Chain is fairly large. `77777
 
 Recall also that a user must have a `pubkey` enabled when interacting with an Antara-related Smart Chain. [View this linked material for an explanation.](/antara/tutorials/understanding-antara-addresses/)
 
-If desired, the reader may use an existing Smart Chain instead of a temporary educational chain. [Follow this link](https://github.com/komodoplatform/komodo/blob/master/src/assetchains.old) for a list of asset-chain launch parameters.
+If desired, the reader may use an existing Smart Chain instead of a temporary educational chain. [Follow this link](https://github.com/komodoplatform/komodo/blob/master/src/assetchains.old) for a list of smart-chain launch parameters.
 
 #### Create a Token to Represent an External Cryptocurrency
 

data-for-gpts/antara-content.txt

@@ -2020,7 +2020,7 @@ ten minutes, and the Bitcoin hash rate’s protection in approximately twenty to
 minutes.
 
 Another difference between the KMD main chain and an asset chain is that the
-notary nodes only mine the KMD main chain. Asset-chain developers are responsible
+notary nodes only mine the KMD main chain. smart-chain developers are responsible
 to create any required network of miners to process the asset chain’s transactions.
 This does not need to be a full network of mining farms, such as those in Bitcoin.
 Rather, it only needs to be enough computing power to process transactions, and
@@ -2328,7 +2328,7 @@ will wait for the next few steps to occur.
 The reason for the wait is that a blockchain’s essence depends upon existing not
 in isolation, but in a network of multiple devices connected. This is the nature of
 decentralization. Komodod will wait until it receives a signal from another device,
-thus indicating that it has a peer with which to form the asset-chain network.
+thus indicating that it has a peer with which to form the smart-chain network.
 
 #### The Entire Coin Supply is Distributed in the Genesis Block
 
@@ -3543,7 +3543,7 @@ necessary. We are putting all PAX endeavors on hold at this time.
 ## Smart Contracts on the Komodo Platform
 
 There are several smart-contract options available in the Komodo ecosystem. The
-options based on the Bitcoin protocol have been included with our technology, and indeed even with Bitcoin, since the beginning. We also recently released Crypto Conditions, Merkle Root of Merkle Root (MoM) notarizations, and Asset Chain Customizations. These provide enhanced smart-contract and asset-chain functionality. All are
+options based on the Bitcoin protocol have been included with our technology, and indeed even with Bitcoin, since the beginning. We also recently released Crypto Conditions, Merkle Root of Merkle Root (MoM) notarizations, and Asset Chain Customizations. These provide enhanced smart-contract and smart-chain functionality. All are
 still in beta stages.
 
 ### Bitcoin-protocol Based Smart Contracts

data-for-gpts/atomicdex-content.txt

@@ -3638,7 +3638,7 @@ Activating coins in 'lite mode' means you don't need to have a native coin daemo
 KomoDeFi is a true cross chain, cross protocol Decentralized Exchange (DEX), allowing for trades between coins and tokens across many platforms and ecosystems, such as:
 
 *   UTXO based coins (e.g. DOGE, BTC, ZEC, LTC, DASH, DGB)
-*   [Ethereum (ETH)](https://ethereum.org/en/) & [ERC20 tokens](https://etherscan.io/tokens)
+*   [Ethereum (ETH)](https://ethereum.org/) & [ERC20 tokens](https://etherscan.io/tokens)
 *   [Binance Coin (BNB)](https://coinmarketcap.com/currencies/bnb/) & [BEP20](https://www.coingecko.com/en?asset_platform_id=binance-coin) tokens
 *   [QTUM](https://qtum.org) & [QRC20 tokens](https://qtum.info/qrc20)
 *   [Polygon (MATIC)](https://polygon.technology/) & [PLG20 tokens](https://polygonscan.com/tokens)

data-for-gpts/historical-content.txt

@@ -1347,7 +1347,7 @@ Activating coins in 'lite mode' means you don't need to have a native coin daemo
 KomoDeFi is a true cross chain, cross protocol Decentralized Exchange (DEX), allowing for trades between coins and tokens across many platforms and ecosystems, such as:
 
 *   UTXO based coins (e.g. DOGE, BTC, ZEC, LTC, DASH, DGB)
-*   [Ethereum (ETH)](https://ethereum.org/en/) & [ERC20 tokens](https://etherscan.io/tokens)
+*   [Ethereum (ETH)](https://ethereum.org/) & [ERC20 tokens](https://etherscan.io/tokens)
 *   [Binance Coin (BNB)](https://coinmarketcap.com/currencies/bnb/) & [BEP20](https://www.coingecko.com/en?asset_platform_id=binance-coin) tokens
 *   [QTUM](https://qtum.org) & [QRC20 tokens](https://qtum.info/qrc20)
 *   [Polygon (MATIC)](https://polygon.technology/) & [PLG20 tokens](https://polygonscan.com/tokens)

data-for-gpts/komodefi-api/all-api-content.txt

@@ -13480,9 +13480,116 @@ export const description = "Find the Changelogs of various versions of Komodo da
 
 # Change Log
 
-Version 0.5.0 of the Komodo daemon includes the following changes.
-
-## List of Changes
+## v0.8.1 \[Falkor]
+
+*   This update is mandatory and includes several security fixes, code refactoring, optimizations, and other improvements.
+*   Update Rust compiler to 1.69.
+*   Add notarisations specific unit tests.
+*   Refactoring the legacy code that is associated with PAX, KV, and ratification transactions has resulted in a slight decrease in block verification and overall synchronization time.
+*   Bump libcurl to 8.4.0 ([CVE-2023-38545](https://github.com/advisories/GHSA-7xw9-w465-6x42), [CVE-2023-38546](https://github.com/advisories/GHSA-x3qx-m3c2-qfhx) fix).
+*   Fix the value pools (sprout, sapling) calculation issue.
+*   Minor fixes and updates.
+
+## v0.8.0-beta1 \[Viserion]
+
+*   This is a mandatory update, Komodo Season 7 HF planned on height `3484958` for KMD, and timestamp `1688132253` (`Fri Jun 30 2023 13:37:33 GMT+0000`) for assetchains. All wallets/nodes should be updated to the latest (`0.8.0`) software to continue following mainnet.
+*   Reduce AUR 5% -> 0.01% (start from S7), as it announced in [KIP-0001](https://github.com/KomodoPlatform/kips/blob/main/kip-0001.mediawiki).
+*   Memory Usage Improvement: The memory usage of `komodod` has been reduced by not keeping Equihash solutions for all block headers in memory.
+*   Node Startup Performance Improvements.
+*   Security fixes.
+*   Upgrade project dependencies (libevent).
+*   Add `z_gettreestate` rpc.
+*   Minor fixes and updates.
+
+## v0.7.2 \[Longpan]
+
+*   This is a mandatory update, Komodo Season 6 HF planned on height 2963330 for KMD, and timestamp 1656077853 (Fri Jun 24 2022 13:37:33 GMT+0000) for assetchains. All wallets/nodes should be updated to the latest (0.7.2) software to continue following mainnet.
+*   Fix build with new glibc 2.34 on Linux platforms.
+*   Fix unoptimized depends build (bdb, boost, protobuf, zeromq).
+*   Remove Verus (VRSC) legacy code: VerusHash, VerusHash 1.1, Verus POS/stake, etc. Chains which used VerusHash as primary algo, like LUMBER will be incompatible with new version of daemon.
+*   Code refactoring. Perfomance boost on some operations.
+*   Restore -exchange command line arg for an exchanges (this will disable interest/reward calculations and will set nLockTime in newly created transactions to zero).
+*   Fix / refactor komodo\_block\_prg and komodo\_block\_unlocktime internals logic, get rid of VerusHash usage in it. Starting from this release all chains using -ac\_timeunlockfrom, -ac\_timeunlockto, -ac\_timelockgte will be incompatible with new daemon (there was no well-known public blockchains using these features). Newly created blockchains (ACs) using these parameters will work without any limitations on 0.7.2 and higher versions of software.
+*   hf22 / hfnet consensus changes and fixes, related to well-known issues of long-gaps between blocks, disappearing txes from mempool in-case of big gaps between blocks, etc. These changes aimed to improve the network stability, help to get rid of such gaps, and make txes propagation more reliable and stable.
+*   Minor fixes and updates.
+*   version bump
+
+## v0.7.1 \[Hydra]
+
+*   general refactoring
+*   general enhancements
+*   update dns seed
+*   rm dead chains
+*   bump version
+
+## v0.7.0 \[Medusa]
+
+*   disable vSolutions size > 1 after HF
+*   fix -disablewallet arg on getblocktemplate caused daemon crash
+*   add zHTLC functionality
+*   update assetchains file
+*   add S5 pubkeys and HF bits
+*   update CI
+*   bump version
+*   general enhancements
+
+Pools and miners please note:
+
+*   we recommend running your KMD mining node with `-minrelaytxfee=0.000035 -opretmintxfee=0.004`
+
+## v0.6.1 \[Draconic Serpent]
+
+*   CC improvements
+*   Bump deprecation height
+*   added asmap utility
+*   remove inactive ACs
+*   tar: unpack as current user
+*   bump version
+
+## v0.6.0 \[Draconic Serpent]
+
+*   fix initial sync
+*   rm template matching and pseudo opcodes
+*   fix notarization test segfault
+*   update CI/CD
+*   disable THROW\_IF\_SYNCING
+*   added CBufferedFile fix (thx LarryRuane)
+*   added unit test (streams\_tests.cpp rewritten for Google C++ Testing Framework)
+*   additional komodo\_block\_load test
+*   remove invalid TXs (reward related) from mempool
+*   update openssl
+*   avoid duplicate getheaders requests
+*   fix linearize tool
+*   fix fingerprint encoding
+*   remove time adjustment
+*   add dPoW S4 array and activation height/timestamp
+*   bump KMD version
+
+Pools and miners please note:
+
+*   we recommend running your KMD mining node with `-minrelaytxfee=0.000035 -opretmintxfee=0.004`
+
+## v0.5.2 \[Obsidian Dragon]
+
+*   Update boost
+*   Update libcurl
+*   Update ccache
+*   Update proton
+*   Update seeds
+*   Bump min protocol version
+*   Bump protocol version
+*   Remove old seeds
+*   Add tests and CI
+*   Update univalue
+*   Bump KMD version
+*   Remove CEAL, CHAIN, COMMOD, DSEC, KMDICE, BNTN, EQL, DION, PRLPY
+*   Add `opretmintxfee` parameter
+
+Pools and miners please note:
+
+*   we recommend restarting your KMD mining node with `-minrelaytxfee=0.000035 -opretmintxfee=0.004`
+
+## v0.5.0 \[Obsidian Dragon]
 
 *   zMempool fix
 *   KMDnuke fix
@@ -13491,11 +13598,6 @@ Version 0.5.0 of the Komodo daemon includes the following changes.
 *   CC fixes and additions
 *   add season 3.5 pubkey array
 *   protocol version bump
-*   update libsodium 1.0.18
-*   update libgmp URL
-*   update libsnark URL
-*   update channelsCC test
-*   use kmd metrics art
 export const title = "Introduction to Smart Chain Documentation";
 export const description =
   "Discover the comprehensive Smart Chain technical documentation, covering installation, setup, tutorials, and API commands for developers.";
@@ -17969,7 +18071,7 @@ export const description =
 *   The purpose of this document is to give a better understanding of Smart Chain parameters via examples. These chains are grouped simply by the number of parameters used in customizing each. As new parameters are added, the new combinations will be tested and added here.
 *   Please see [Creating a new Blockchain using Komodo Platform](./create-a-default-smart-chain.html) and [Parameters to customize Blockchains created using Komodo Platform](/antara/setup/antara-customizations) if you haven't already.
 *   All chains must have at least `ac_name` and `ac_supply` set. The `ac_pubkey` parameter can be used with any of these chains. If `ac_perc` is not set, the only effect `ac_pubkey` has is to have the genesis block be mined to the pubkey that has been specified. The parameters `ac_name` , `ac_supply` , `ac_pubkey` are not counted when grouping based on the `Number of parameters`.
-*   The values of parameters other than `ac_name` in these examples are completely arbitrary. The names of these example-asset-chains are assigned based on how a chain is customized and its grouping.
+*   The values of parameters other than `ac_name` in these examples are completely arbitrary. The names of these example-smart-chains are assigned based on how a chain is customized and its grouping.
 
 ## Number of parameters: 1
 

data-for-gpts/komodefi-api/legacy-api-content.txt

@@ -1503,7 +1503,7 @@ We invite the reader to consider that as each Smart Chain can support thousands
 
 Naturally, as each level of notarization takes time to perform, there is an additional delay for Smart Chains as compared to the KMD main chain. A Smart Chain’s history is notarized into the KMD main chain approximately every ten minutes, assuming constant activity. This notarization will then be pushed through the notarization process into the chosen PoW network (Bitcoin). We estimate that a transaction performed on a Smart Chain will receive the KMD main chain’s protection within approximately ten minutes, and will receive the Bitcoin hash rate’s protection in approximately twenty to thirty minutes.
 
-Another difference between the KMD main chain and a Smart Chain is that the notary nodes only mine the KMD main chain. Asset-chain developers are responsible to create any required network of miners to process their Smart Chain’s transactions.
+Another difference between the KMD main chain and a Smart Chain is that the notary nodes only mine the KMD main chain. smart-chain developers are responsible to create any required network of miners to process their Smart Chain’s transactions.
 
 This does not need to be a full network of mining farms, such as those in Bitcoin/Litecoin. Rather, power only needs to be of a level necessary to process transactions, and to provide any desired level of hash-rate security. For a small business with intermittent periods of transaction activity, a single, dedicated, full-time server may be enough. Larger businesses can scale as desired and can also work to attract a network of freelance miners.