|
Title: Time? Post by: benjamindees on May 19, 2011, 01:19:29 AM 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?
Title: Re: Time? Post by: 1bitc0inplz on May 19, 2011, 01:22:09 AM 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. Title: Re: Time? Post by: kjj on May 19, 2011, 01:42:08 AM 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. Title: Re: Time? Post by: 1bitc0inplz on May 19, 2011, 01:47:44 AM 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. Title: Re: Time? Post by: kjj on May 19, 2011, 02:01:51 AM 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. |