From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org,
Jeremy Rubin <jeremy.l.rubin.travel@gmail.com>
Subject: Re: [bitcoin-dev] BIP Draft: Minimum Viable TXIn Hash
Date: Sat, 25 Jul 2015 19:51:53 +0000 [thread overview]
Message-ID: <201507251951.53970.luke@dashjr.org> (raw)
In-Reply-To: <CAJ+8mENU5kQuKg=-UAh05qGEPS1OuiKTgXFVGcF0Z0gsRo+Czw@mail.gmail.com>
On Thursday, July 23, 2015 8:12:19 PM Jeremy Rubin via bitcoin-dev wrote:
> Please see the following draft BIP which should decrease the amount of
> bytes needed per transaction. This is very much a draft BIP, as the design
> space for this type of improvement is large.
>
> This BIP can be rolled out by a soft fork.
>
> Improvements are around 12% for standard "one in two out" txn, and even
> more with more inputs hashes.
>
> https://gist.github.com/JeremyRubin/e175662d2b8bf814a688
This looks like just a p2p protocol optimisation, which doesn't even need a
softfork. You do need to document the suggested protocol changes more
specifically, however.
Luke
next prev parent reply other threads:[~2015-07-25 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 20:12 [bitcoin-dev] BIP Draft: Minimum Viable TXIn Hash Jeremy Rubin
2015-07-25 19:51 ` Luke Dashjr [this message]
2015-07-25 22:05 ` Jorge Timón
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=201507251951.53970.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jeremy.l.rubin.travel@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