mirror of
https://github.com/bitcoin/bips.git
synced 2025-01-18 21:35:13 +01:00
fix spacing
This commit is contained in:
parent
4cd4e53752
commit
db117ef473
@ -1,5 +1,4 @@
|
|||||||
<pre>
|
<pre>
|
||||||
|
|
||||||
BIP: 301
|
BIP: 301
|
||||||
Layer: Consensus (soft fork)
|
Layer: Consensus (soft fork)
|
||||||
Title: Blind Merged Mining (Consensus layer)
|
Title: Blind Merged Mining (Consensus layer)
|
||||||
@ -11,10 +10,8 @@
|
|||||||
Type: Standards Track
|
Type: Standards Track
|
||||||
Created: 2019-07-23
|
Created: 2019-07-23
|
||||||
License: BSD-2-Clause
|
License: BSD-2-Clause
|
||||||
|
|
||||||
</pre>
|
</pre>
|
||||||
|
|
||||||
|
|
||||||
==Abstract==
|
==Abstract==
|
||||||
|
|
||||||
|
|
||||||
@ -27,7 +24,6 @@ Our goal here, is to allow mainchain miners to trustlessly "sell" the act of fin
|
|||||||
|
|
||||||
==Motivation==
|
==Motivation==
|
||||||
|
|
||||||
|
|
||||||
Regular "Merged-Mining" (MM) allows miners to reuse their hashing work to secure other chains (for example, as in Namecoin). However, traditional MM has two drawbacks:
|
Regular "Merged-Mining" (MM) allows miners to reuse their hashing work to secure other chains (for example, as in Namecoin). However, traditional MM has two drawbacks:
|
||||||
|
|
||||||
# Miners must run a full node of the other chain. (This is because [while miners can effortlessly create the block] miners will not create a valid payment to themselves, unless the block that they MM is a valid one. Therefore, miners must assemble a *valid* block first, then MM it.)
|
# Miners must run a full node of the other chain. (This is because [while miners can effortlessly create the block] miners will not create a valid payment to themselves, unless the block that they MM is a valid one. Therefore, miners must assemble a *valid* block first, then MM it.)
|
||||||
@ -38,7 +34,6 @@ BMM addresses both shortcomings.
|
|||||||
|
|
||||||
==Specification==
|
==Specification==
|
||||||
|
|
||||||
|
|
||||||
Note: This document uses the notation side:\* and main:\* in front of otherwise-ambiguous words (such as "block", "node", or "chain"), to distinguish the mainchain version from its sidechain counterpart. We also use "Simon" to refer to a Sidechain Full Node, and "Mary" to refer to a mainchain miner.
|
Note: This document uses the notation side:\* and main:\* in front of otherwise-ambiguous words (such as "block", "node", or "chain"), to distinguish the mainchain version from its sidechain counterpart. We also use "Simon" to refer to a Sidechain Full Node, and "Mary" to refer to a mainchain miner.
|
||||||
|
|
||||||
|
|
||||||
@ -194,8 +189,6 @@ As a soft fork, older software will continue to operate without modification. As
|
|||||||
(As a matter of fact, the only people receiving money here all happen to be miners. So there is less reason than ever to expect compatibility problems.)
|
(As a matter of fact, the only people receiving money here all happen to be miners. So there is less reason than ever to expect compatibility problems.)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
==Deployment==
|
==Deployment==
|
||||||
|
|
||||||
This BIP will be deployed by "version bits" BIP9 with the name "blindmm" and using bit 4.
|
This BIP will be deployed by "version bits" BIP9 with the name "blindmm" and using bit 4.
|
||||||
@ -217,7 +210,6 @@ Also, for interest, see an example sidechain here: https://github.com/drivechain
|
|||||||
|
|
||||||
==References==
|
==References==
|
||||||
|
|
||||||
|
|
||||||
* http://www.drivechain.info/literature/index.html
|
* http://www.drivechain.info/literature/index.html
|
||||||
* http://www.truthcoin.info/blog/blind-merged-mining/
|
* http://www.truthcoin.info/blog/blind-merged-mining/
|
||||||
* https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-July/014789.html
|
* https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-July/014789.html
|
||||||
|
Loading…
Reference in New Issue
Block a user