v0.2.14

• Add WASM SDK for Download
• Fix issue #21

v0.2.12

Fixed an issue with block difficulty checks that prevented blocks of insufficient difficulty from being broadcast.

---

Solve the problem that when multiple blocks are validated at the same time, the transaction pool and the highest bid record do not match, resulting in miners generating invalid blocks.

---

Fixed a bug in the tx pool that would cause transactions with small bidding fee gaps to not be able to enter the transaction pool, resulting in blocks generated by honest miners not containing the highest bid.

All miners must be updated.

Fixed this: #10

v0.2.9

v0.2.9 solve the vulnerability problem of highest bid checking and avoid generating invalid block from multiple block producers.

---

v0.2.8 fixed HACD auto bidding bugs.

---

【Important】The biggest problem affecting the consensus of honest miners was found: the invalid nodes that were originally forked were widely distributed in the network, and they occupied the channels that nodes connected to each other, but did not broadcast valid blocks, resulting in honest miners not being able to broadcast valid blocks to each other.

Please upgrade to v0.2.7 as soon as possible so that all nodes of this version can connect to each other to avoid being isolated from the network by a large number of invalid nodes. If you find that your node is unable to connect to a boot road node, update the full node software immediately.

This version will be relatively stable.

---

Fixed the issue of sorting HACD bidding tx in the transaction pool, and enabled saving and broadcasting bidding transactions on all types of full nodes.

---

If you encounter a hard fork and need to manually restore and synchronize with the org node, to prevent other nodes from interfering with the synchronization data, perform the following steps:

1. Delete or move the chunk data directory hacash_mainnet_data elsewhere to resync the chunk from height 0

2. Modify the two items in configuration group [node] in configuration file hacash.config.ini:
   ; not_find_nodes = true change to not_find_nodes = true

; not_accept_nodes = true change to not_accept_nodes = true
   
   Removing the previous semicolon indicates that these two items are turned on in order to connect to other hard forked nodes on the whole network, or to prevent other nodes from connecting to themselves, thus interfering with block synchronization.

3. If mining is enabled, then during the synchronization period, you need to temporarily close the '[miner]' item and suspend mining

4. Wait for all blocks to be synchronized, restore the modified configurations such as miner and not_find_nodes (start node find, mining, etc.), and then restart the node.

Because of the highest bid detection problem during block synchronization, the judgment of node validity of the block is inconsistent, resulting in a split between miners, which is manifested as a long-term offline in some hashrates.

This release fixes the following two issues:

1. When synchronizing the current block branch, the bidding record is cleared, causing the highest price check to be invalid. The new version will keep a record of the last 5 HACD for the consensus system to check.

2. Miners who have newly joined or restarted nodes have not pulled the highest HACD bidding record, resulting in their newly mined blocks being rejected by other nodes with the highest bidding records, resulting in offline computing power, which is the main reason why some miners cannot continue mining. The new version will push and pull the latest HACD bidding transactions in both directions when connecting nodes, so that the highest bid will always be packed into the block.

---

Fixed a panic bug by invalid block and fixed the situation where an invalid block caused the HACD bidding check to be invalid.

Solve the problem of generating invalid blocks. Fix issue #6

---

HIP-18 and HIP-19 full node versions released.

HIP-18 setting: sets the minimum bid for HACD as the number of HAC rewards for a block, which is currently 8 HAC. Effective from number 107000, all HACD miners will need to modify their minimum bid parameters, and bids below 8HAC will not be accepted by the network.

HIP-19 setting: Starting from HACD number 107000, the full node will record the current valid highest bid, and blocks below the recorded maximum bid will be rejected by the full node.

All full nodes must be updated to the latest full node software before HACD number 107000. If you encounter any block synchronization issues, delete all block data and resync from block height 0.