public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Jan Vornberger" <jan@uos.de>
To: "Bitcoin Dev" <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Determine input addresses of a transaction
Date: Thu, 27 Oct 2011 15:37:43 +0200 (CEST)	[thread overview]
Message-ID: <55928.134.106.52.172.1319722663.squirrel@webmail.uni-osnabrueck.de> (raw)
In-Reply-To: <CABsx9T2v4uhUdsWEg58Xs2OhOf3ED0Q2LGmkrRpdJDxvVMexdQ@mail.gmail.com>

Am Mo, 24.10.2011, 16:55, schrieb Gavin Andresen:
> Green addresses could be implemented as a second signature in the
> scriptSig.  You'd have to hack your bitcoin client, but you could
> generate a transaction that had <greensig> <sig> <pubKey>  ... as the
> input instead of <sig> <pubKey>.
>
> The <greensig> will be ignored by old clients.  The transactions is
> still considered 'standard'.  But you could teach bitcoin to look for
> <greensig> signatures in wallet transactions...

I played around with this a little bit and managed to generate such
transactions. However, I ran into the problem that IsStandard() also
checks that the size of scriptSig is not above 200. Adding an extra
signature there triggers this limit. I guess there is no way around
that?

Regards,
Jan



  parent reply	other threads:[~2011-10-27 13:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24  8:29 [Bitcoin-development] Determine input addresses of a transaction Jan Vornberger
2011-10-24 11:09 ` Pieter Wuille
2011-10-27 14:12   ` Jan Vornberger
2011-10-24 14:55 ` Gavin Andresen
2011-10-24 16:25   ` Mike Hearn
2011-10-24 18:52     ` Simon Barber
2011-10-24 17:14   ` Michael Hendricks
2011-10-27 13:37   ` Jan Vornberger [this message]
2011-10-27 14:50   ` Jan Vornberger
2011-10-25  9:45 Jan Vornberger
2011-10-25 10:03 ` Joel Joonatan Kaartinen
2011-10-25 10:42 ` Mike Hearn

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=55928.134.106.52.172.1319722663.squirrel@webmail.uni-osnabrueck.de \
    --to=jan@uos.de \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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