On Fri, Jul 18, 2014 at 4:53 PM, Gavin Andresen <gavinandre...@gmail.com> wrote: > Two more half-baked thoughts: > > We should be able to assume that the majority of transaction data (except > for coinbase) has already been propagated. As Jeff said, incentivizing nodes > to propagate transactions is a very good thing (the signature cache already > gives a small incentive to miners to propagate and not 'hoard' > transactions).
Maybe a stupid idea - but couldn't we make that assumption a surety by starting the 'set synchronization process' as soon as the miner starts crunching on a certain block, instead of when it broadcasts it? So the peers are prepared, and the actual block broadcast is just the header + coinbase tx. Wladimir ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
