Does every client have the same list of orphan blocks? Is everyone's blk0001.dat file identical?
Nope, not all orphan block / forks are the same.
Topic: Orphan blocks - how to reduce (Read 2265 times)
Nope, not all orphan block / forks are the same.
Does every client have the same list of orphan blocks? Is everyone's blk0001.dat file identical?
I'm trying to investigate the "wasted block generation" issue and it's fairly obvious that my client doesn't have all the orphan blocks. What I'd really need to generate good data is the orphan blocks extracted from the blk001.dat file of clients that have been running continuously for a long time. Better still would be orphan blocks from miners.
I believe that the blocks are only relayed after checks have been carried out and after it has been written to disk. The checks are necessary to avoid relaying junk in the event of an attack but the relaying should happen before writing to disk to keep the latency down and to avoid block loss.
ByteCoin
I'm trying to investigate the "wasted block generation" issue and it's fairly obvious that my client doesn't have all the orphan blocks. What I'd really need to generate good data is the orphan blocks extracted from the blk001.dat file of clients that have been running continuously for a long time. Better still would be orphan blocks from miners.
I believe that the blocks are only relayed after checks have been carried out and after it has been written to disk. The checks are necessary to avoid relaying junk in the event of an attack but the relaying should happen before writing to disk to keep the latency down and to avoid block loss.
ByteCoin
Jump to: