Time? | Bitcointalksearch.org

kjj

legendary

Activity: 1302

Merit: 1026

Quote from: 1bitc0inplz on May 18, 2011, 08:47:44 PM

That would be true if he is mining solo.

If he is part of a pool, I do not believe it is required as the pool is generating the timestamps he would be hashing.

Ahh, good point.

1bitc0inplz

member

Activity: 112

Merit: 10

Quote from: kjj on May 18, 2011, 08:42:08 PM

The spec says that a node should refuse a block if the timestamp is more than 2 hours into the future. If the timestamp is too far into the past, I'm guessing that most nodes will also reject it (since it would appear to be older than a block already accepted as valid).

That would be true if he is mining solo.

If he is part of a pool, I do not believe it is required as the pool is generating the timestamps he would be hashing.

kjj

legendary

Activity: 1302

Merit: 1026

The spec says that a node should refuse a block if the timestamp is more than 2 hours into the future. If the timestamp is too far into the past, I'm guessing that most nodes will also reject it (since it would appear to be older than a block already accepted as valid).

Which brings me to an interesting question. Why the hell isn't accurate NTP timekeeping required of nodes? If your clock is even 5 minutes into the future, you don't belong on the internet, much less participating in a distributed cryptocurrency.

1bitc0inplz

member

Activity: 112

Merit: 10

Quote from: benjamindees on May 18, 2011, 08:19:29 PM

How important is it that the time on my mining rig be accurate? If it's off by a few minutes, would that affect anything like number of rejected blocks for instance?

nope. you should be good.

benjamindees

legendary

Activity: 1330

Merit: 1000

How important is it that the time on my mining rig be accurate? If it's off by a few minutes, would that affect anything like number of rejected blocks for instance?

Topic: Time? (Read 1063 times)