diff options
| author | GoodDaisy <90915921+GoodDaisy@users.noreply.github.com> | 2023-10-13 09:05:19 +0800 |
|---|---|---|
| committer | GoodDaisy <90915921+GoodDaisy@users.noreply.github.com> | 2023-10-13 09:05:19 +0800 |
| commit | 6fd7de46b79898cff9dd1ada44fb65bd22b41f6c (patch) | |
| tree | b1640b0bfe0d0d31c03ad08aed1d2066e04084ad /bip-0300.mediawiki | |
| parent | e918b50731397872ad2922a1b08a5a4cd1d6d546 (diff) | |
| download | bips-6fd7de46b79898cff9dd1ada44fb65bd22b41f6c.tar.xz | |
Fix typos
Diffstat (limited to 'bip-0300.mediawiki')
| -rw-r--r-- | bip-0300.mediawiki | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/bip-0300.mediawiki b/bip-0300.mediawiki index ab81c32..e5048e7 100644 --- a/bip-0300.mediawiki +++ b/bip-0300.mediawiki @@ -290,7 +290,7 @@ For example: if there are two sidechains, and we wish to upvote the 7th bundle o The version number allows us to shrink the upvote vector in many cases. Version 0x00 omits the upvote vector entirely (ie, 6 bytes for the whole M4) and sets this block's M4 equal to the previous block's M4. Version 0x01 uses one byte per sidechain, and can be used while all ACKed withdrawals have an index under 256 (ie, 99.99%+ of the time). -Version 0x02 uses a full two bytes per sidechain (each encoded in little endian), but it always works no matter how many withdrawl proposals exist. +Version 0x02 uses a full two bytes per sidechain (each encoded in little endian), but it always works no matter how many withdrawal proposals exist. Version 0x03 omits the upvote vector, and instead upvotes only those withdrawals that are leading their rivals by at least 50 votes. If a sidechain has no pending bundles, then it is skipped over when M4 is created and parsed. @@ -465,7 +465,7 @@ M2: 1 get, 1 delete, 1 create M3: 3 get, 1 delete, 2 create, 2 hash for each coinbase output: search for prior M3 for this sidechain lookup if M3 was ever rejected or paid in the past - for each prior proposed withdrawl: (included in 1 get+delete+create) + for each prior proposed withdrawal: (included in 1 get+delete+create) M4: 1 get + for every proposed withdraw, 1 get, 1 delete, 1 create, 1 add v0 needs to read and parse previous block |