From: Sancho Panza <sanch0panza@protonmail.com>
To: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Reference implementation (wip) of bip-genvbvoting (generalized version bits)
Date: Thu, 20 Apr 2017 16:56:45 -0400 [thread overview]
Message-ID: <O_LZ72OAX3MqjySQ39s5sFTu5TIQaUrAMR89a6-F-3XlkG8k8itR28ZkZolWGjs2btFcxcoWZlIz8hVsRU0Kkq3QwM0i9AZTojy4pUvXck0=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
Dear all,
An initial reference implementation of bip-genvbvoting (spec: [1]) is now available at
https://github.com/sanch0panza/bitcoin/commits/genvbvoting-bu-dev-clean1
starting at commit fdd83383436ee43b072c258d4a6feb713902c77e .
This development is based against the Bitcoin Unlimited 'dev' branch, and has been submitted as PR458 to BU [2].
The naming of the new 'bipgenvb_forks' output section in the 'getblockchain' RPC interface is to be considered temporary while the BIP has no formal number.
I would be happy to get any feedback while I implement a corresponding pull request for a reference implementation on Bitcoin Core. Due to other commitments this may come at a later stage - if someone else is eager to port it over, please feel free.
Regards,
Sancho
[1] https://github.com/sanch0panza/bips/blob/bip-genvbvoting/bip-genvbvoting.mediawiki
[2] https://github.com/BitcoinUnlimited/BitcoinUnlimited/pull/458
P.S. The revised "unknown version check" code is considered an implementation specific and not part of core functionality, and is consequently not fully covered by regression tests.
[-- Attachment #2: Type: text/html, Size: 1651 bytes --]
reply other threads:[~2017-04-20 20:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='O_LZ72OAX3MqjySQ39s5sFTu5TIQaUrAMR89a6-F-3XlkG8k8itR28ZkZolWGjs2btFcxcoWZlIz8hVsRU0Kkq3QwM0i9AZTojy4pUvXck0=@protonmail.com' \
--to=sanch0panza@protonmail.com \
--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