Release v0.112.0

[doitian]

RC Date: 2023-10-16
Release Date: 2023-10-30

Features

• feat(rpc): Introduce the new method generate_epochs in the IntegrationTest module #4128 rpc: Introduce the new method generate_epochs in the IntegrationTest module (@EthanYuan)
• Tx pool Replace-by-fee #4079: Tx pool Replace-by-fee (@chenyukang)
• Add feature of Replace-by-fee for tx-pool #4108: Add feature of Replace-by-fee for tx-pool (@chenyukang)
• Backport: RBF will also replace tx not in Pending  #4232: RBF will also replace tx not in Pending (@chenyukang)

Bug Fixes

• Fix ckb-hash depends blake2b-ref multiple times #4172: Fix ckb-hash depends blake2b-ref multiple times (@eval-exec)
• fix(light-client): could not check MMR for fork chains #4171 light-client: Could not check MMR for fork chains (@yangby-cryptape)
• fix: should only return main chain data #4182: Should only return main chain data (@quake)
• Backport: Fix orphan pool issue for long pending tx #4208: Fix orphan pool issue for long pending tx (@chenyukang)

Improvements

• Tx pool rewrite with multi_index_map #3993: Tx pool rewrite with multi_index_map (@chenyukang)
• Upgrade CKB's rust-toolchain from 1.67.1 to 1.71.1 #4146: Upgrade CKB's rust-toolchain from 1.67.1 to 1.71.1 (@eval-exec)
• Remove useless --cfg disable_faketime from RUSTFLAGS #4160: Remove useless --cfg disable_faketime from RUSTFLAGS (@eval-exec)
• Remove useless non_owning_clone method for ChainController and NetworkController #4158: Remove useless non_owning_clone method for ChainController and NetworkController (@eval-exec)
• Remove #[derive(Clone)] from Synchronizer #4161: Remove #[derive(Clone)] from Synchronizer (@eval-exec)
• molecule: Remove deprecated SyncMessage union items. #4113 (molecule): Remove deprecated SyncMessage union items. (@eval-exec)
• Remove Consensus.dao_type_hash's Option wrapper #4186: Remove Consensus.dao_type_hash's Option wrapper (@eval-exec)

[doitian]

New changes since Oct 9th:

Bug Fixes

• fix: should only return main chain data #4182: Should only return main chain data (@quake)

Improvements

• Remove Consensus.dao_type_hash's Option wrapper #4186: Remove Consensus.dao_type_hash's Option wrapper (@eval-exec)

[doitian]

New changes in RC2

• Backport: Fix orphan pool issue for long pending tx #4208: Fix orphan pool issue for long pending tx (@chenyukang)

[chenyukang]

Breakchange notes

We introduce a huge code refactor on the transaction pool module and added the feature of RBF(Replace by Fee) in this release.

Here are two points need to be noted:

1. Double-spending check now will work before any transaction is added to the transaction pool, a transaction that conflicts with current transactions in the pool will be rejected, the only way to add the new transaction into the pool is by improving the fee and if RBF checking passed, transaction pool will remove old conflicted transactions, then add the new one into pool.

2. The RBF feature enables users to replace a transaction with a higher fee rate when pending in tx-pool, which is useful when the transaction is stuck in the tx-pool. More details about RBF:

The most important rule is fee, you need to pay an extra fee to replace old transactions with the new one. The default min_rbf_rate in ckb.toml is 1500, which means the minimum extra fee rate for RBF, the unit is shannons/KB.

min_replace_fee = sum(replaced_tx_fee) + (min_rbf_rate * size)

The replaced transaction will be removed from tx-pool and with the status Rejected. The RBF may replace a transaction in the status of Pending or Proposed, but the old transaction may still be committed if it was in Proposed.

[doitian]

Release rc3 for #4232 which reverts the default behavior introduced in #4181 (comment)

[doitian]

Breakchange notes

We introduce a huge code refactor on the transaction pool module and added the feature of RBF(Replace by Fee) in this release.

Here are two points need to be noted:

1. Double-spending check now will work before any transaction is added to the transaction pool, a transaction that conflicts with current transactions in the pool will be rejected, the only way to add the new transaction into the pool is by improving the fee and if RBF checking passed, transaction pool will remove old conflicted transactions, then add the new one into pool.
2. The RBF feature enables users to replace a transaction with a higher fee rate when pending in tx-pool, which is useful when the transaction is stuck in the tx-pool. More details about RBF:

The most important rule is fee, you need to pay an extra fee to replace old transactions with the new one. The default min_rbf_rate in ckb.toml is 1500, which means the minimum extra fee rate for RBF, the unit is shannons/KB.

min_replace_fee = sum(replaced_tx_fee) + (min_rbf_rate * size)

The replaced transaction will be removed from tx-pool and with the status Rejected.

@chenyukang Is this note up-to-dated after applying #4232 ?

[doitian]

Use v0.112.1 since v0.112.0 has been used to publish crates and cannot be reverted.

[chenyukang]

Breakchange notes

We introduce a huge code refactor on the transaction pool module and added the feature of RBF(Replace by Fee) in this release.
Here are two points need to be noted:

1. Double-spending check now will work before any transaction is added to the transaction pool, a transaction that conflicts with current transactions in the pool will be rejected, the only way to add the new transaction into the pool is by improving the fee and if RBF checking passed, transaction pool will remove old conflicted transactions, then add the new one into pool.
2. The RBF feature enables users to replace a transaction with a higher fee rate when pending in tx-pool, which is useful when the transaction is stuck in the tx-pool. More details about RBF:

The most important rule is fee, you need to pay an extra fee to replace old transactions with the new one. The default min_rbf_rate in ckb.toml is 1500, which means the minimum extra fee rate for RBF, the unit is shannons/KB.
min_replace_fee = sum(replaced_tx_fee) + (min_rbf_rate * size)
The replaced transaction will be removed from tx-pool and with the status Rejected.

@chenyukang Is this note up-to-dated after applying #4232 ?

I update with add a note:

The RBF may replace a transaction in the status of Pending or Proposed, but the old transaction may still be committed if it was in Proposed.

[doitian]

https://github.com/nervosnetwork/ckb/releases/tag/v0.112.1