301 - Blind Merged Mining (Consensus layer)
BIP: 301 Layer: Consensus (soft fork) Title: Blind Merged Mining (Consensus layer) Author: Paul Sztorc CryptAxe Comments-Summary: No comments yet. Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0301 Status: Draft Type: Standards Track Created: 2019-07-23 License: BSD-2-Clause ==Abstract== Blind Merged Mining (BMM) allows miners to mine a Sidechain/Altcoin, without running its node software (ie, without "looking" at it, hence "blind"). Instead, a separate sidechain user runs their node and constructs the block, paying himself the transaction fees. He then uses an equivalent amount of money to "buy" the right to find this block, from the conventional layer1 Sha256d miners. ==Motivation== "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(s). (Thus, they must run "non-Bitcoin" software wh...
300 - Hashrate Escrows (Consensus layer)
BIP: 300 Layer: Consensus (soft fork) Title: Hashrate Escrows (Consensus layer) Author: Paul Sztorc CryptAxe Comments-Summary: No comments yet. Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0300 Status: Draft Type: Standards Track Created: 2017-08-14 License: BSD-2-Clause Post-History: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014364.html ==Abstract== In Bip300, txns are not signed via cryptographic key. Instead, they are "signed" by hashpower, over time. Like a big multisig, 13150-of-26300, where each block is a new "signature". Bip300 emphasizes slow, transparent, auditable transactions which are easy for honest users to get right and very hard for dishonest users to abuse. The chief design goal for Bip300 is ''partitioning'' -- users may safely ignore Bip300 txns if they want to (or Bip300 entirely). See [http://www.drivechain.info/ this site] for more information. ==Motivation== As Reid Hoffman [https://blocks...