From: Luke Dashjr <luke@dashjr.org>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] SegWit GBT updates
Date: Sat, 30 Jan 2016 18:50:02 +0000 [thread overview]
Message-ID: <201601301850.03469.luke@dashjr.org> (raw)
I've completed an initial draft of a BIP for updating getblocktemplate for
segregated witness here:
https://github.com/luke-jr/bips/blob/segwit_gbt/bip-segwit-gbt.mediawiki
Please review and comment (especially with regard to the changes in the
sigoplimits handling).
(Note: libblkmaker's reference implementation is at this time incompatible
with the "last output" rule in this BIP.)
Thanks,
Luke
next reply other threads:[~2016-01-30 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 18:50 Luke Dashjr [this message]
2016-02-01 18:41 ` [bitcoin-dev] SegWit GBT updates Cory Fields
2016-02-01 19:46 ` Luke Dashjr
2016-02-01 21:43 ` Cory Fields
2016-02-01 23:08 ` Luke Dashjr
2016-02-02 1:40 ` Cory Fields
2016-02-02 2:30 ` Luke Dashjr
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=201601301850.03469.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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