From: "Eric Lombrozo" <elombrozo@gmail•com>
To: bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Segregated Witness BIPs
Date: Wed, 23 Dec 2015 15:22:30 +0000 [thread overview]
Message-ID: <em3b62e758-afbe-4aed-a08d-eb85b252efc4@platinum> (raw)
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
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
The other two BIPS will be drafted soon.
---
Eric
[-- Attachment #2: Type: text/html, Size: 1709 bytes --]
next reply other threads:[~2015-12-23 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 15:22 Eric Lombrozo [this message]
2015-12-24 14:22 ` jl2012
2015-12-27 8:26 ` jl2012
2016-01-05 5:43 ` jl2012
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=em3b62e758-afbe-4aed-a08d-eb85b252efc4@platinum \
--to=elombrozo@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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