In MultiChain, miners must prove their identity when creating a block

Mining in MultiChain

Details to follow. For now, please consult the MultiChain White Paper.

Miner block signatures

Miner signatures are embedded inside the OP_RETURN metadata of the coinbase transaction, using a regular bitcoin-style signature format. The payload signed by the miner is the full block header, with the following modifications:

  • The merkle_root is recalculated based on the txid of the coinbase transaction with the OP_RETURN removed. This prevents a dependency loop from miner signature → coinbase txid → merkle root → block header → miner signature.
  • The nonce field is set to 0. This avoids having to recalculate the miner signature for every attempt at finding a block hash to match the target difficulty. However it does lead to some malleability in that a user without mining permissions could generate a block with the same content as a valid block, but with a different nonce. Seeing as the nonce serves no purpose other than to randomize the block’s content for its hash, this should not be a source of concern.