Bitcoin Forum
December 08, 2016, 04:32:29 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: 0 second block!  (Read 918 times)
deepceleron
Legendary
*
Offline Offline

Activity: 1470



View Profile WWW
July 16, 2011, 05:09:07 PM
 #1

Block 136583:

{
  "hash":"00000000000001d7635c5037bd97519b583cd995a56edc0018dfb9a39106f758",
  "ver":1,
  "prev_block":"000000000000003f767918da359ac0dd5728edc90552b0e4f4af59419d1b70f5",
  "mrkl_root":"2d9712cefa0f81ac0fb6cb0812567c5f572ab9f0309e803fb01b039e1938fdf6",
  "time":1310829862,


Block 136584:

{
  "hash":"000000000000035ac219a1a52dde48ccd7348deed858b1da47b0f16b7ac70ea2",
  "ver":1,
  "prev_block":"00000000000001d7635c5037bd97519b583cd995a56edc0018dfb9a39106f758",
  "mrkl_root":"61e5c0c6a611568131217f21b69a4ac96c5bb5598a704627a3aecf8584d1ff9c",
  "time":1310829862,


Is this a first? Did deepbit just figure out the ultimate hack to avoid invalid blocks?  Tongue



Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481171549
Hero Member
*
Offline Offline

Posts: 1481171549

View Profile Personal Message (Offline)

Ignore
1481171549
Reply with quote  #2

1481171549
Report to moderator
1481171549
Hero Member
*
Offline Offline

Posts: 1481171549

View Profile Personal Message (Offline)

Ignore
1481171549
Reply with quote  #2

1481171549
Report to moderator
1481171549
Hero Member
*
Offline Offline

Posts: 1481171549

View Profile Personal Message (Offline)

Ignore
1481171549
Reply with quote  #2

1481171549
Report to moderator
casascius
Mike Caldwell
VIP
Legendary
*
Offline Offline

Activity: 1344


The Casascius 1oz 10BTC Silver Round (w/ Gold B)


View Profile WWW
July 16, 2011, 05:12:19 PM
 #2

What's invalid?  The fact that the timestamp is the same doesn't mean that the blocks happened at the exact same time.  The time stamp of the later block can actually be earlier than the earlier one.  Why?  Because the timestamp is taken from the system clock of the computer doing the mining, which is likely not synchronized with atomic time.

Bitcoin doesn't validate the timestamps to precision - it only validates them to be within a reasonable window, like two hours.

Companies claiming they got hacked and lost your coins sounds like fraud so perfect it could be called fashionable.  I never believe them.  If I ever experience the misfortune of a real intrusion, I declare I have been honest about the way I have managed the keys in Casascius Coins.  I maintain no ability to recover or reproduce the keys, not even under limitless duress or total intrusion.  Remember that trusting strangers with your coins without any recourse is, as a matter of principle, not a best practice.  Don't keep coins online. Use paper wallets instead.
deepceleron
Legendary
*
Offline Offline

Activity: 1470



View Profile WWW
July 16, 2011, 05:32:08 PM
 #3

What's invalid?  The fact that the timestamp is the same doesn't mean that the blocks happened at the exact same time.  The time stamp of the later block can actually be earlier than the earlier one.  Why?  Because the timestamp is taken from the system clock of the computer doing the mining, which is likely not synchronized with atomic time.

Bitcoin doesn't validate the timestamps to precision - it only validates them to be within a reasonable window, like two hours.

I see: A timestamp is accepted as valid if it is greater than the median timestamp of previous 11 blocks, and less than the network-adjusted time + 2 hours. "Network-adjusted time" is the median of the timestamps returned by all nodes connected to you.

So there is no joy in this statistic... either miner's time could have been off - and a clock time could be up to ~1 hour negative and still be valid depending on the previous blocks.

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!