From: Gregory Maxwell <gmaxwell@gmail.com>
To: Roy Badami <roy@gnomon.org.uk>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 0.8.1 ideas
Date: Wed, 13 Mar 2013 14:27:01 -0700 [thread overview]
Message-ID: <CAAS2fgSLmjhMmmrxjKQ0KOX5EEM4=+Wwebuaw4NHE9LdtLSP6Q@mail.gmail.com> (raw)
In-Reply-To: <20130313212243.GQ96148@giles.gnomon.org.uk>
On Wed, Mar 13, 2013 at 2:22 PM, Roy Badami <roy@gnomon.org.uk> wrote:
> The idea of the client detecting/warning about not-trivial forking
> seems worthwhile too, though, assuming it doesn't already (AIUI it
> doesn't).
It does warn— if its heard the fork and its on the lower difficulty
side. Extending that to also alert if its on the winning side and the
fork is long enough might be wise, though I have a little concern that
it'll be mistaken to be more dependable than it would be.
next prev parent reply other threads:[~2013-03-13 21:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 12:56 [Bitcoin-development] 0.8.1 ideas Luke-Jr
2013-03-13 13:14 ` Gregory Maxwell
2013-03-13 15:05 ` Peter Todd
2013-03-13 15:18 ` Gregory Maxwell
2013-03-13 15:26 ` Luke-Jr
2013-03-13 16:04 ` Peter Todd
2013-03-13 17:41 ` Mark Friedenbach
2013-03-13 17:58 ` Pieter Wuille
2013-03-13 18:27 ` Mark Friedenbach
2013-03-13 18:35 ` slush
2013-03-13 18:38 ` Pieter Wuille
2013-03-13 19:30 ` Gregory Maxwell
[not found] ` <16B6728E-4220-4DA6-B740-FA38A7C19CCB@thelibertyportal.com>
2013-03-13 20:24 ` Gregory Maxwell
2013-03-13 20:18 ` Luke-Jr
2013-03-13 18:04 ` Luke-Jr
2013-03-13 21:06 ` Andy Parkins
2013-03-13 21:14 ` Luke-Jr
2013-03-13 21:22 ` Roy Badami
2013-03-13 21:27 ` Gregory Maxwell [this message]
2013-03-13 21:36 ` Roy Badami
2013-03-14 0:18 ` Cameron Garnham
2013-03-15 17:06 ` Benjamin Lindner
2013-03-15 19:23 ` Luke-Jr
2013-03-15 19:52 ` Gregory Maxwell
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='CAAS2fgSLmjhMmmrxjKQ0KOX5EEM4=+Wwebuaw4NHE9LdtLSP6Q@mail.gmail.com' \
--to=gmaxwell@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=roy@gnomon.org.uk \
/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