From: Joel Joonatan Kaartinen <joel.kaartinen@gmail•com>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: Dev <bitcoin-development@lists•sourceforge.net>, Bitcoin
Subject: Re: [Bitcoin-development] multisig, op_eval and lock_time/sequence...
Date: Wed, 09 Nov 2011 23:32:00 +0200 [thread overview]
Message-ID: <1320874320.27400.89.camel@mei> (raw)
In-Reply-To: <CABsx9T2fGcLk477QagbyyPd3cFsOrLKRqG9_GKLf9nirh=Nocg@mail.gmail.com>
It's propably best to create a separate p2p network for off-band
information like this. No need to involve the blockchain with it.
- Joel
On Wed, 2011-11-09 at 16:18 -0500, Gavin Andresen wrote:
> One more thought on putting arbitrary stuff in the scriptSig:
>
> Miners could decide to revolt and remove the extra scriptSig
> information before including the transaction in their blocks. They'd
> still get the full transaction fee, and the transaction would still
> validate so the block would be accepted by everybody else.
>
> Come to think of it, if a node relaying transactions wanted to save
> bandwidth costs or be annoying, it could also strip off the extra
> information before forwarding it, so this isn't a reliable
> communication mechanism. It is probably a much better idea to use
> another protocol to gather signatures.
>
next prev parent reply other threads:[~2011-11-09 21:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 10:22 Michael Grønager
2011-11-09 14:43 ` Alan Reiner
2011-11-09 15:22 ` Alan Reiner
2011-11-09 19:13 ` Gavin Andresen
2011-11-09 20:02 ` Gavin Andresen
2011-11-09 20:31 ` Michael Grønager
2011-11-09 21:18 ` Gavin Andresen
2011-11-09 21:32 ` Joel Joonatan Kaartinen [this message]
2011-11-09 22:13 ` theymos
2011-11-09 20:03 ` Michael Grønager
2011-11-10 3:00 ` Alan Reiner
2011-11-10 9:55 ` Michael Grønager
2011-11-10 12:56 ` Alan Reiner
2011-11-12 16:58 ` Mike Hearn
2011-11-12 17:10 ` Alan Reiner
2011-11-12 17:16 ` Mike Hearn
2011-11-12 17:25 ` Alan Reiner
2011-11-12 17:38 ` 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=1320874320.27400.89.camel@mei \
--to=joel.kaartinen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@gmail$(echo .)com \
/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