mirror of
https://github.com/dashpay/dash.git
synced 2024-12-24 19:42:46 +01:00
## Issue being fixed or feature implemented ## What was done? Added release notes for #5262. ## How Has This Been Tested? ## Breaking Changes ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [x] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_ --------- Co-authored-by: PastaPastaPasta <6443210+PastaPastaPasta@users.noreply.github.com> Co-authored-by: thephez <thephez@users.noreply.github.com> Co-authored-by: UdjinM6 <UdjinM6@users.noreply.github.com>
This commit is contained in:
parent
252f71dbf2
commit
0566ed7e95
15
doc/release-notes-5262.md
Normal file
15
doc/release-notes-5262.md
Normal file
@ -0,0 +1,15 @@
|
||||
Coinbase Changes
|
||||
------------------------
|
||||
|
||||
Once v20 activates, Coinbase transactions in all mined blocks must be of version 3.
|
||||
|
||||
Version 3 of Coinbase will include the following two fields:
|
||||
- bestCLHeightDiff (uint32)
|
||||
- bestCLSignature (BLSSignature)
|
||||
|
||||
bestCLSignature will hold the best Chainlock signature known at the moment of mining.
|
||||
bestCLHeightDiff is equal to the diff in heights from the mined block height to the actual Chainlocked block height.
|
||||
|
||||
Although miners are forced to include a version 3 Coinbase, the actual real-time best Chainlock signature isn't required as long as blocks contain a bestCLSignature equal to (or newer than) the previous block.
|
||||
|
||||
Note: Until the first bestCLSignature is included in a Coinbase once v20 activates, null bestCLSignature and bestCLHeightDiff values are perfectly valid.
|
Loading…
Reference in New Issue
Block a user