Thank you for your thoughts. > The earlier, larger block A will only become stale if *two* blocks are > found in the extra time it takes for block A to propagate the network. > That is a substantially different risk, and probably a negligible > concern to most miners.
I really like Mark’s suggestion but one concern is that it might tip the needle too far. Currently, there is a private cost to include more transactions, which might be too high, but limit the amount of negative externalities that this creates on other miners. If I am able to create blocks that are very likely to be on the main chain with the maximum number of transactions then this makes imposing negative externalities on other miners less costly. Other nodes that are closely connected to me would experience a positive externality through this as well. Would have do some more thinking here but it seems that there is a balance to strike. > If anything, looks like a threat to the current situation with huge > mining subsidies coming from the seigniorage, not a problem that you > would have when the the seigniorage is gone. The incentives remain so long as the ratio of the seignorage revenues to transaction fees remain very high. Even though the dollar price does not change that relationship it does mean that Bitcoin becomes more expensive in USD terms as the USD price of Bitcoin rises. > I think the most important part is that nodes can reliably decide on > "first received", regardless of how they subsequently act on it. If we want to limit the amount of network time spent on redundant problems it would be best for miners to act on this information? What is the benefit of serialisation? Is it that the miner would consider it more likely to make it into the main chain rather than the block that came second? > But I don't see how miners mining headers first would result in empty > blocks either. I guess it is due to the fact that this is the only way a miner can be certain that none of the transactions have been spent already resulting in an orphan block. On 21 Apr 2014, at 17:00, Mark Friedenbach <m...@monetize.io> wrote: > That wasn't what I was saying. Right now the primacy of a block is > determined by the time at which the `block` message is received, which > is delays due to both the time it takes to transmit the block data and > the time it takes to validate. Headers-first, on the other hand, has the > option of basing primacy on the time the block header is received, which > is O(1) time to transmit and to SPV-validate. Mining on that block > doesn't actually commence until the full block is received and validated. > > To see how this works, take an example: two blocks with a common parent > are found relatively close to each other, block A and block B. A is > found first but is a large block with the maximum block size and many > slow scripts. B is found a few seconds later and is an empty block. In > the current regime it is entirely possible that block B, the later but > smaller block, would get received and processed first by more mining > peers than the larger block A, exactly as described in Jonathan Levin's > email. > > With headers-first, however, the cost of propagation of the block header > is the same and we should expect block A to win out over block B nearly > every time. Miners will continue working on the old, known valid parent > block until the contents of block A are received and processed. So the > smaller block B is still found, and since it's data moves across the > network faster, miners even briefly mine on block B. But as soon as they > receive and process the contents of block A, they switch to that. > > The earlier, larger block A will only become stale if *two* blocks are > found in the extra time it takes for block A to propagate the network. > That is a substantially different risk, and probably a negligible > concern to most miners. > > On 04/20/2014 09:06 PM, Peter Todd wrote: >> That is mistaken: you can't mine on top of just a block header, >> leaving small miners disadvantaged as they are earning no profit >> while they wait for the information to validate the block and update >> their UTXO sets. This results in the same problem as before, as the >> large pools who mine most blocks can validate either instantly - the >> self-mine case - or more quickly than the smaller miners. >> >> Of course, in reality smaller miners can just mine on top of block >> headers and include no transactions and do no validation, but that is >> extremely harmful to the security of Bitcoin.
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------ Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform
_______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
