Title: Taproot inside coinbase transaction? Post by: ertil on July 30, 2020, 06:36:46 PM Now we are mining using "winner takes all" scheme. Every miner have to mine in pool or create the whole block alone with all transactions. But instead, we could use taproot on coinbase outputs and produce blocks a bit differently. First, miners could create merkle trees having all non-coinbase transactions and one coinbase with taproot output created by first miner. There could be many such trees available in the network and all of these trees would compete trying to produce lowest hashes, highest total block rewards, etc.
In this way each miner could choose some tree, validate it, and then start working on it. Each miner could attach to coinbase transaction having taproot output. This coinbase transaction would be built by all miners and when going down the tree, the difficulty would be halved each time. For example we could have something like this: Code: target: 00000000ffffff00...0 Code: target: 00000000ffffff00...0 Title: Re: Taproot inside coinbase transaction? Post by: gmaxwell on July 31, 2020, 02:06:22 AM This doesn't really have anything to do with taproot. Taproot isn't a way to have additional outputs on transactions, each taproot output is still just a single output.
Coinbase transactions can already have multiple outputs, and miners can collaborate to create blocks that pay each other directly rather than the the value going to one party. P2Pool is an example of this, unfortunately it was undermined by Bitmain which produced mining hardware which wouldn't work with p2pool or anything like it. |