public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Version 0.6 release candidate 1 plan
Date: Tue, 7 Feb 2012 10:04:36 -0500	[thread overview]
Message-ID: <201202071004.37615.luke@dashjr.org> (raw)
In-Reply-To: <201202061054.26448.luke@dashjr.org>

On Monday, February 06, 2012 10:54:25 AM Luke-Jr wrote:
> > 769 : Make transactions with extra data in scriptSig non-standard
> 
> If this affects relaying, it will significantly harm the ability to replace
> the current spammy "green address" scheme with a sensible extra signature
> system. On the miner end, it could significantly harm adoption of such a
> system.

FWIW, at least MtGox was OK with the plan to move to non-blockchain-spam
0-confirmation via an extra signature. Why do you ignore this possibility, and 
merge stuff that will break it? Do you have an alternative solution to the 
problem of green addresses spamming the blockchain? As I noted in the pull 
request, stripping extra data has no negative impact on normal transactions, 
and clients creating these can be written to expect the txnid to change (or 
simply not care what the txnid is).



  reply	other threads:[~2012-02-07 15:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 15:44 [Bitcoin-development] Version 0.6 release candidate 1 plan Gavin Andresen
2012-02-06 15:54 ` Luke-Jr
2012-02-07 15:04   ` Luke-Jr [this message]
2012-02-07 16:14     ` Luke-Jr
2012-02-07 16:14     ` Gavin Andresen

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=201202071004.37615.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gavinandresen@gmail.com \
    /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