From: Matt Corallo <bitcoin-list@bluematt•me>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] DS Deprecation Window
Date: Mon, 27 Oct 2014 20:17:34 +0000 [thread overview]
Message-ID: <544EA85E.8010400@bluematt.me> (raw)
In-Reply-To: <544EA3D7.2050901@thinlink.com>
It is a very bad idea to delay relaying/accepting blocks based on
information which is only local to your node (ie would create the
ability for people to split the network by sending out lots of
double-spends to different parts of the network at the same time). Thus,
miners are incentivized to go connect to everyone on the network and
look for double-spends, not including them in their blocks to avoid
being delayed (which is OK, except having to connect to everyone is bad).
There is a related concept of "discouraging" blocks which generally only
refers to mining on a previous block, but you have to be careful doing
that so you dont break consensus.
On 10/27/14 19:58, Tom Harding wrote:
> Greetings Bitcoin Dev,
>
> This is a proposal to improve the ability of bitcoin users to rely on
> unconfirmed transactions. It can be adopted incrementally, with no hard
> or soft fork required.
>
> https://github.com/dgenr8/out-there/blob/master/ds-dep-win.md
>
> Your thoughtful feedback would be very much appreciated.
>
> It is not yet implemented anywhere.
>
> Cheers,
> Tom Harding
> CA, USA
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
next prev parent reply other threads:[~2014-10-27 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 19:58 Tom Harding
2014-10-27 20:17 ` Matt Corallo [this message]
2014-10-28 2:26 ` Tom Harding
2014-10-28 2:36 ` Gregory Maxwell
2014-10-28 17:38 ` Tom Harding
2014-11-06 23:50 ` Tom Harding
2014-10-28 6:24 ` Thomas Zander
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=544EA85E.8010400@bluematt.me \
--to=bitcoin-list@bluematt$(echo .)me \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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