From: jl2012 <jl2012@xbt•hk>
To: Eric Lombrozo <elombrozo@gmail•com>
Cc: bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Segregated Witness BIPs
Date: Tue, 05 Jan 2016 00:43:41 -0500 [thread overview]
Message-ID: <18f27064f026b117d6dc6fc95b57891f@xbt.hk> (raw)
In-Reply-To: <77ba13602b2d9e3c0f56a41a9799021a@xbt.hk>
A new BIP, as part of the SW softfork, is pending BIP number assignment:
https://github.com/bitcoin/bips/pull/270
This proposal defines a new transaction digest algorithm for signature
verification in version 0 and version 1 witness program, in order to
minimize redundant data hashing in verification (solving the O(n^2)
issue), and to cover the input value by the signature (a frequently
requested feature for cold wallet).
jl2012 via bitcoin-dev 於 2015-12-24 09:22 寫到:
> The SW payment address format BIP draft is ready and is pending BIP
> number assignment:
> https://github.com/bitcoin/bips/pull/267
>
> This is the 3rd BIP for segwit. The 2nd one for Peer Services is being
> prepared by Eric Lombrozo
>
> Eric Lombrozo via bitcoin-dev 於 2015-12-23 10:22 寫到:
>> I've been working with jl2012 on some SEGWIT BIPs based on earlier
>> discussions Pieter Wuille's implementation. We're considering
>> submitting three separate BIPs:
>>
>> CONSENSUS BIP: witness structures and how they're committed to blocks,
>> cost metrics and limits, the scripting system (witness programs), and
>> the soft fork mechanism.
>>
>> PEER SERVICES BIP: relay message structures, witnesstx serialization,
>> and other issues pertaining to the p2p protocol such as IBD,
>> synchronization, tx and block propagation, etc...
>>
>> APPLICATIONS BIP: scriptPubKey encoding formats and other wallet
>> interoperability concerns.
>>
>> The Consensus BIP is submitted as a draft and is pending BIP number
>> assignment: https://github.com/bitcoin/bips/pull/265 [1]
>> The other two BIPS will be drafted soon.
>>
>> ---
>> Eric
>>
>> Links:
>> ------
>> [1] https://github.com/bitcoin/bips/pull/265
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists•linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
prev parent reply other threads:[~2016-01-05 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 15:22 Eric Lombrozo
2015-12-24 14:22 ` jl2012
2015-12-27 8:26 ` jl2012
2016-01-05 5:43 ` jl2012 [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=18f27064f026b117d6dc6fc95b57891f@xbt.hk \
--to=jl2012@xbt$(echo .)hk \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=elombrozo@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