From: Luke Dashjr <luke@dashjr.org>
To: Kristov Atlas <kristovatlas.lists@gmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] RFC for BIP: Best Practices for Heterogeneous Input Script Transactions
Date: Thu, 26 May 2016 00:00:37 +0000 [thread overview]
Message-ID: <201605260000.39848.luke@dashjr.org> (raw)
In-Reply-To: <CAGH37SLBesCESaAY60UUc=B=0szZjL1KS6=oqWDBeTbdYKqEfw@mail.gmail.com>
On Thursday, May 19, 2016 4:18:15 AM Kristov Atlas via bitcoin-dev wrote:
> BIP: TBD
This is assigned BIP 126.
> * '''Heterogenous input script transaction (HIT)''': A transaction
> containing multiple inputs where not all inputs have identical scripts
> (e.g. a transaction spending from more than one Bitcoin address)
Transactions are never from Bitcoin addresses, and inputs almost never have
identical scripts (although the UTXOs they are spending often do).
Luke
prev parent reply other threads:[~2016-05-26 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 21:36 [bitcoin-dev] RFC for BIP: Best Practices for Heterogeneous Input Script Transactions Kristov Atlas
2016-05-19 4:18 ` Kristov Atlas
2016-05-23 17:44 ` T. DeV D
2016-05-26 0:00 ` Luke Dashjr [this message]
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=201605260000.39848.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=kristovatlas.lists@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