Bitcoin Forum
July 28, 2017, 06:45:03 PM *
News: BIP91 seems stable: there's probably only slightly increased risk of confirmations disappearing. You should still prepare for Aug 1.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Time?  (Read 855 times)
benjamindees
Legendary
*
Offline Offline

Activity: 1330


View Profile
May 19, 2011, 01:19:29 AM
 #1

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?

Civil Liberty Through Complex Mathematics
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1bitc0inplz
Member
**
Offline Offline

Activity: 112


View Profile
May 19, 2011, 01:22:09 AM
 #2

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.

Mine @ http://pool.bitp.it - No fees, virtually 0 stales, what's not to love!
Chat with us @ #bitp.it on irc.freenode.net
Learn more about our pool @ http://forum.bitcoin.org/index.php?topic=12181.0
kjj
Legendary
*
Offline Offline

Activity: 1302



View Profile
May 19, 2011, 01:42:08 AM
 #3

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.

p2pcoin: a USB/CD/PXE p2pool miner - 1N8ZXx2cuMzqBYSK72X4DAy1UdDbZQNPLf - todo
I routinely ignore posters with paid advertising in their sigs.  You should too.
1bitc0inplz
Member
**
Offline Offline

Activity: 112


View Profile
May 19, 2011, 01:47:44 AM
 #4

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.

Mine @ http://pool.bitp.it - No fees, virtually 0 stales, what's not to love!
Chat with us @ #bitp.it on irc.freenode.net
Learn more about our pool @ http://forum.bitcoin.org/index.php?topic=12181.0
kjj
Legendary
*
Offline Offline

Activity: 1302



View Profile
May 19, 2011, 02:01:51 AM
 #5

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.

p2pcoin: a USB/CD/PXE p2pool miner - 1N8ZXx2cuMzqBYSK72X4DAy1UdDbZQNPLf - todo
I routinely ignore posters with paid advertising in their sigs.  You should too.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!