v2.3
Key Information | Details |
---|---|
Version | Conflux v2.3.0 |
Hardfork Introduced | Yes |
Incompatible Changes | Yes (CIP-107, CIP-112, CIP-113, CIP-118, CIP-119) |
Introduction
Conflux v2.3.0 introduces a new hardfork, which update includes incompatible changes and several RPC improvements.
Incompatible Changes
CIP-107
CIP-107, the major change of the hard fork, introduces "storage point", a burning mechanism of storage collateral. When a sponsor adds storage collateral for a contract, a proportion of the CFX tokens will be burned and a corresponding amount of "storage point" will be minted. The "storage point" cannot be transferred and will not generate storage interest, but it can pay for storage collateral as CFX tokens. This is to introduce some burning scenarios and mechanisms to mitigate the continuous inflation of CFX tokens, thereby improving the tokenomics of Conflux.
Corresponding Changes
- RPC changes:
- Add a new RPC
cfx_getCollateralInfo
to return chain collateral info. cfx_getSponsorInfo
returns 2 extra fields:usedStoragePoints
andavailableStoragePoints
.
- Add a new RPC
- Internal contract
SponsorWhitelistControl
changes- new interfaces:
getAvailbaleStoragePoints
(introduced by CIP-118) - Collateral sponsor replacement threshold is changed
- previous:
tx.value > sponsor_balance_for_collateral + collateral_for_storage
- current:
tx.value > sponsor_balance_for_collateral + (collateral_for_storage - used_storage_points / 1024)
- previous:
- Burn for collateral sponsored before CIP-107:
- p(defined by CIP-107, started at 0.5) proportion of
sponsor_balance_for_collateral + collateral_for_storage
will be burnt and converted to storage points. The conversion will be carried out lazily.
- p(defined by CIP-107, started at 0.5) proportion of
- new interfaces:
- DAO vote changes
- new vote option to change
STORAGE_POINT_PORP
that defines burn ratio p (STORAGE_POINT_PORP / (STORAGE_POINT_PORP + 1)
)
- new vote option to change
Refer the original CIP-107 document for more details.
CIP-112
CIP-112 fixes the incorrect encoding and decoding implementation of the custom field of block headers. Currently, in the block header RLP encoding, each element in the custom list is appended to the RLP list as raw bytes, where its RLP-encoded data should be appended instead. This change is protocol breaking as it changes the block header encoding and decoding in P2P transmission.
CIP-113
CIP-113 makes the PoS finalization faster by shortening the PoS consensus round time and the pivot decision signing wait time. The PoS round time is reduced from 60 seconds to 30 seconds. The defer time for validators to wait to sign a PoS-confirmed pivot block is reduced from 50 epochs to 20 epochs.
Corresponding Changes
It is estimated that this CIP will shorten the finalization interval from the previous 6-8 minutes to 4-5 minutes, a reduction of 120 to 180 seconds. This optimization will benefit products that utilize the PoS finalization.
CIP-118
CIP-118 introduced getAvailableStoragePoints
interface for SponsorWhitelistControl
. Refer CIP-107 for more information.
CIP-119
CIP-119 introduce the PUSH0 (0x5f) instruction as EIP-3855. Supporting this opcode can achieve maximum compatibility with Ethereum.
Releases
Testnet
Key Information | Details |
---|---|
Release | Conflux v2.3.0-testnet Pre-release |
Anouncement | Conflux v2.3.0-testnet Testnet Hardfork Upgrade Announcement |
Deadlines |
|
Key Information | Details |
---|---|
Release | Conflux v2.3.0-3-testnet Pre-release |
Anouncement | - |
Deadlines |
|
Mainnet
Key Information | Details |
---|---|
Release | Conflux v2.3.0 |
Anouncement | Conflux v2.3.0 Hardfork Upgrade Announcement |
Deadlines |
|