diff options
Diffstat (limited to 'bip-0300.mediawiki')
| -rw-r--r-- | bip-0300.mediawiki | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/bip-0300.mediawiki b/bip-0300.mediawiki index e5048e7..fb2070a 100644 --- a/bip-0300.mediawiki +++ b/bip-0300.mediawiki @@ -213,7 +213,7 @@ M2 is invalid if: * An M2 is already in this block. * It tries to ACK two different M1s for the same slot. -Otherwise: +Otherwise: * The sidechain is "ACK"ed and does NOT get a "fail" for this block. (As it otherwise would.) @@ -242,7 +242,7 @@ Sidechain withdrawals take the form of "Bundles" -- named because they "bundle u Sidechain full nodes aggregate the withdrawal-requests into a big set. The sidechain calculates what M6 would have to look like, to pay all of these withdrawal-requests out. Finally, the sidechain calculates what the hash of this M6 would be. This 32-byte hash identifies the Bundle. -This 32-byte hash is what miners will be slowly ACKing over 3-6 months, not the M6 itself (nor any sidechain data, of course). +This 32-byte hash is what miners will be slowly ACKing over 3-6 months, not the M6 itself (nor any sidechain data, of course). A bundle either pays all its withdrawals out (via M6), or else it fails (and pays nothing out). @@ -283,7 +283,7 @@ M4 is a coinbase OP Return output containing the following: 1-byte - Version n-byte - The "upvote vector" -- describes which bundle-choice is "upvoted", for each sidechain. -The upvote vector will code "abstain" as 0xFF (or 0xFFFF); it will code "alarm" as 0xFE (or 0xFFFE). Otherwise it simply indicates which withdrawal-bundle in the list, is the one to be "upvoted". +The upvote vector will code "abstain" as 0xFF (or 0xFFFF); it will code "alarm" as 0xFE (or 0xFFFE). Otherwise it simply indicates which withdrawal-bundle in the list, is the one to be "upvoted". For example: if there are two sidechains, and we wish to upvote the 7th bundle on sidechain #1 plus the 4th bundle on sidechain #2, then the upvote vector would be { 07, 04 }. And M4 would be [0x6A,D77D1776,00,0006,0003]. @@ -313,7 +313,7 @@ Important: Within a sidechain-group, upvoting one Bundle ("+1") automatically do For example: -{| class="wikitable" +{| class="wikitable" |- ! SC# ! Bundle Hash @@ -350,7 +350,7 @@ For example: ...in block 900,000 could become... -{| class="wikitable" +{| class="wikitable" |- ! SC# ! Bundle Hash @@ -414,7 +414,7 @@ M6 is invalid if: * The txn fee of M6 is NOT exactly equal to the amount of the previous bullet point. * There are additional OP_DRIVECHAIN outputs after the first one. -Else, M6 is valid. +Else, M6 is valid. (The point of the latter two bullet points, is to allow the bundle hash to cover the L1 transaction fee.) @@ -485,7 +485,7 @@ As a soft fork, older software will continue to operate without modification. No ==Deployment== -This BIP will be deployed via UASF-style block height activation. Block height TBD. +This BIP will be deployed via UASF-style block height activation. Block height TBD. ==Reference Implementation== |