Author: Chris Stewart 2017-06-18 14:36:24
Published on: 2017-06-18T14:36:24+00:00
The discussion on the bitcoin-dev mailing list revolves around the commitment structure for the coinbase transaction in drivechain implementation. The OP_RETURN is considered redundant and can be implicitly assumed as there is a fixed set of drivechains with specific indexes defined. It is suggested to include a version byte to enable future upgradation of the commitment structure. The concern is raised that if OP_BRIBE_VERIFY takes an argument, then it may take away the blindness from BMM. The proposal is to add a rule that only the first hash with a particular sidechain ID counts and that forces the miner to accept the bribe from only one miner per sidechain per block. In case multiple bribes are accepted by the miner, then only the first one counts. The transactions can be serialized into a single push to reduce the number of drops, and subsequently, OP_BRIBE_VERIFY can operate as discussed. The propagation of these transactions over the network can be facilitated by requiring that they are near the current block height and should be removed from the memory pool once the block height has arrived to allow losing miners to re-spend those outputs.
Updated on: 2023-06-12T00:57:51.581696+00:00