Bitcoin Forum
April 23, 2018, 05:02:09 AM *
News: Latest stable version of Bitcoin Core: 0.16.0  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Timestamps going backwards - why ?  (Read 971 times)
Forp
Full Member
***
Offline Offline

Activity: 198
Merit: 100


View Profile
June 27, 2011, 12:13:45 AM
 #1

Once in a while timestamps are moving backwards. Shocked

Block 32649 is from 09:49:06 and the next block 32650 is from the same day 2 hours earlier, 7:50:31.  Shocked

This is not the only example, there are quite many - and it is also not just 3 or 6 minutes but hours.

I am trying to understand that phenomenon - but I don't. even if there is a chain reorganization, the chains mut be built in sequence - and the code shoulod check linearity in time.

Where is my mistake?
1524459729
Hero Member
*
Offline Offline

Posts: 1524459729

View Profile Personal Message (Offline)

Ignore
1524459729
Reply with quote  #2

1524459729
Report to moderator
The forum strives to allow free discussion of any ideas. All policies are built around this principle. This doesn't mean you can post garbage, though: posts should actually contain ideas, and these ideas should be argued reasonably.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1524459729
Hero Member
*
Offline Offline

Posts: 1524459729

View Profile Personal Message (Offline)

Ignore
1524459729
Reply with quote  #2

1524459729
Report to moderator
kjj
Legendary
*
Offline Offline

Activity: 1302
Merit: 1000



View Profile
June 27, 2011, 12:20:38 AM
 #2

The network doesn't require that a block be newer than the previous block, just that it be newer than the median time of the last several blocks.

17Np17BSrpnHCZ2pgtiMNnhjnsWJ2TMqq8
I routinely ignore posters with paid advertising in their sigs.  You should too.
MoonShadow
Legendary
*
Offline Offline

Activity: 1708
Merit: 1000



View Profile
June 27, 2011, 12:23:58 AM
 #3


Where is my mistake?


There is no mistake, the timestamp is provided by the machine that submits the block.  The client permits a great deal of variation for the timestamp before it rejects it, because the only reason that it's in there at all is to determine the retarget value once every 2016 blocks, and it only needs to be so accurate.  It wouldn't be necessary to reject incorrect timestamps at all, if not for the possibility of manipulation of the retarget.

"The powers of financial capitalism had another far-reaching aim, nothing less than to create a world system of financial control in private hands able to dominate the political system of each country and the economy of the world as a whole. This system was to be controlled in a feudalist fashion by the central banks of the world acting in concert, by secret agreements arrived at in frequent meetings and conferences. The apex of the systems was to be the Bank for International Settlements in Basel, Switzerland, a private bank owned and controlled by the world's central banks which were themselves private corporations. Each central bank...sought to dominate its government by its ability to control Treasury loans, to manipulate foreign exchanges, to influence the level of economic activity in the country, and to influence cooperative politicians by subsequent economic rewards in the business world."

- Carroll Quigley, CFR member, mentor to Bill Clinton, from 'Tragedy And Hope'
Forp
Full Member
***
Offline Offline

Activity: 198
Merit: 100


View Profile
June 27, 2011, 08:44:07 AM
 #4

Thanx a lot - this was very helpful.

The bitcoin client is actually constructed in a very smart manner.  Smiley
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!