From: Neiman <neiman.mail@gmail.com>
To: Gregory Maxwell <greg@xiph.org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] How accurate are the Bitcoin timestamps?
Date: Tue, 30 Jan 2018 11:53:41 +0100 [thread overview]
Message-ID: <CACRYg-6_Zaw8aQ_mJarMiGJ184EYcYvAbVptAznoP1FQngFakg@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgRLMnpu5JHTxxJJvEQc8rj2Ox=cKCWcsvVdY06G0kKXJw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
On Mon, Jan 29, 2018 at 10:54 PM, Gregory Maxwell via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> On Mon, Jan 29, 2018 at 9:40 PM, Tier Nolan via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> if there were tighter time requirements in the protocol
> miners would address them by running NTP which as an _astounding_ lack
> of security in terms of how it is commonly deployed.
>
Could you say a few more words about this lack of security? Or share a link
if you have one. I know very little about NTPs.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 1555 bytes --]
next prev parent reply other threads:[~2018-01-30 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 13:34 [bitcoin-dev] How accurate are the Bitcoin timestamps? Neiman
2018-01-29 21:40 ` Tier Nolan
2018-01-29 21:54 ` Gregory Maxwell
2018-01-30 7:27 ` Peter Todd
2018-01-30 10:53 ` Neiman [this message]
2018-01-30 10:52 ` Neiman
2018-01-29 21:53 ` George Balch
2018-01-29 22:23 ` Bryan Bishop
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=CACRYg-6_Zaw8aQ_mJarMiGJ184EYcYvAbVptAznoP1FQngFakg@mail.gmail.com \
--to=neiman.mail@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=greg@xiph.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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