On Mon, Nov 4, 2013 at 3:26 AM, Mike Hearn <m...@plan99.net> wrote: > I'm wondering about an alternative protocol change that perhaps has less > subtle implications than their suggested change. Rather than address the > problem by assuming the network is full of sybil nodes and changing the > rules for selecting the chain to build on, how about if we wrote code to > automatically build a miner backbone by having IP addresses of nodes > embedded into coinbases, then having any bitcoind that is creating work > automatically connect to IPs that appeared in enough recent blocks?
Yea, I've proposed this too (both in the past and in the context of this). I don't think, however, that the announcements need to be the miners themselves— but instead just need to be nodes that the miners think are good (and, for their own sake— ones they're well connected to). Miner's could keep a list of address messages nodes they like/are-connected to, perhaps prioritizing their own nodes, than exclude ones which are already in the most recent blocks, and include the best remaining. Of course, if it's using address messages (or perhaps a new address message syntax) it would automatically support hidden services. They should probably be included as OP_RETURN outputs in coinbase transactions, maybe only limited (by what other clients pay attention to) to one or two per block. This should make it harder to get partitioned from the majority hashrate (or partition the majority hashrate from itself), though these hosts would be DOS targets, so it isn't a silver bullet. Making the majority hashrate self-unpartitionabilty stronger is possible— have miners add an encryption key to their coinbase transactions, then have subsequent miners mine encrypted addr messages to single other block sources to automatically weave a miner darknet with access controlled by successful block creation. But I doubt it's worth the complexity of bandwidth. ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
