BitcoinCash/2021-CHIPs
1
Fork 0
Code Issues Pull Requests Releases Activity

Clarifications from BigBlockIfTrue

Browse Source 
This makes things more clear about this being != 64 bytes.
This commit is contained in:
TomZ
2021-03-14 08:59:59 +01:00
parent 641f18b6cd
commit 31b66363d2
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHIP-2021-01-Allow Smaller Transactions.md
+3 -3
View File
@@ -9,7 +9,7 @@ This proposal updates the rule for minimum transation size to clean up technical
> Type: Consensus > Type: Consensus
> Status: Draft > Status: Draft
> Version: 0.3 > Version: 0.3
> Last edit: 2021-03-11 > Last edit: 2021-03-14
> Owner: Tom Zander > Owner: Tom Zander
> History: https://gitlab.com/bitcoin.cash/chips > History: https://gitlab.com/bitcoin.cash/chips
@@ -39,7 +39,7 @@ Developers of libraries and software will hit this limit in many cases as well i
The impact on the ecosystem is split into full nodes and others. The impact on the ecosystem is split into full nodes and others.
* Full nodes need to change the current test for minimum size of a transaction from 100-bytes to 65 bytes. This is a widening of the allowed transactions and therefore should be scheduled for a future protocol upgrade. * Full nodes need to change the current test for minimum size of a transaction to now check the transaction is any size other than 64 bytes. This is a widening of the allowed transactions and therefore should be scheduled for a future protocol upgrade.
* All the players that are not full nodes do not have to change anything, as anything they generated before is still allowed. * All the players that are not full nodes do not have to change anything, as anything they generated before is still allowed.
@@ -49,7 +49,7 @@ This CHIP is mostly aimed at cleaning up technical debt. The result is less rule
To solve the unintended side-effects of the 100-bytes minimum, we simply remove this limit. To solve the unintended side-effects of the 100-bytes minimum, we simply remove this limit.
To avoid the weakness in merkle-blocks we introduce the limit that transactions shall not be 64 bytes in size. To avoid the weakness in merkle-blocks we introduce the rule that transactions shall not be 64 bytes in size.
## References: ## References: