From: Troy Benjegerdes <hozer@hozed•org>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
Ron OHara <ron.ohara54@gmail•com>
Subject: Re: [Bitcoin-development] Time
Date: Mon, 28 Jul 2014 12:33:30 -0500 [thread overview]
Message-ID: <20140728173330.GC22640@nl.grid.coop> (raw)
In-Reply-To: <CANEZrP2N6zf7RUtPzA+7-X5+UKBmrY-D_8Md+_=8nssoFNng9A@mail.gmail.com>
On Fri, Jul 25, 2014 at 12:30:11PM +0200, Mike Hearn wrote:
> >
> > Ok... 'time' on the blockchain could be 'gamed' ... but with great
> > difficulty.
>
>
> Unfortunately not: miners have in the past routinely gamed the timestamp in
> order to use it as an extra nonce and squeeze some more gigahashes out of
> their hardware/pool.
>
>
> Also remember that currently the chain could be dominated by a coalition of
> just two pools.
There's a solution to both of these problems..
https://github.com/CatcoinOfficial/CatcoinRelease/commit/0d03a5b3d8bb7bc3c935e7196c5d807da997cf9c
If you want a really reliable time source, use at least three block chains and
make sure they all agree within an hour.
>
> > An application presented with a fake blockchain can use
> > quite a few heuristics to test the 'validity' of the block chain.
> >
>
> The app cannot tell if it was given a truncated chain. You could keep such
> an app stuck in the past forever. This is often a problem.
>
>
> > Reliable 'time' has been impossible up until now - because you need to
> > trust the time source, and that can always be faked. Using the
> > blockchain as an approximate time source gives you a world wide
> > consensus without direct trust of any player.
> >
>
> Much though I hate to be a party pooper, you could currently get
> Bitcoin-level trusted time by just polling at least two or three
> independent servers e.g. google.com, baidu.cn, yandex.ru (they all serve
> time via HTTPS headers).
Well, being as how I don't trust Bitcoin anyway because it includes SSL, yes,
you could get 'bitcoin-level' trust.
> If we crack the mining decentralisation problem then this argument becomes
> a lot stronger, but for now ......
But if you actually want something secure, you look at the altcoin space
which solved the mining decentralization problem when Litecoin came out,
and this also solves the having to trust a single source code base. There
is lots of code diversity out there in altcoins, and what appears to me to
be a really strong cryptographically sound time source, but only if you use
multiple diverse sources.
--
----------------------------------------------------------------------------
Troy Benjegerdes 'da hozer' hozer@hozed•org
7 elements earth::water::air::fire::mind::spirit::soul grid.coop
Never pick a fight with someone who buys ink by the barrel,
nor try buy a hacker who makes money by the megahash
prev parent reply other threads:[~2014-07-28 18:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 1:14 Ron OHara
2014-07-25 1:41 ` Jeff Garzik
2014-07-25 2:35 ` Aaron Voisine
2014-07-25 2:39 ` Gregory Maxwell
2014-07-25 3:21 ` William Yager
2014-07-25 5:56 ` Aaron Voisine
2014-07-25 10:26 ` Mike Hearn
2014-07-25 14:45 ` Aaron Voisine
2014-07-25 16:03 ` Mike Hearn
2014-07-25 16:22 ` Natanael
2014-07-25 18:14 ` Aaron Voisine
2014-07-25 10:30 ` Mike Hearn
2014-07-27 22:22 ` Peter Todd
2014-07-28 17:33 ` Troy Benjegerdes [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140728173330.GC22640@nl.grid.coop \
--to=hozer@hozed$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
--cc=ron.ohara54@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox