From: Sancho Panza <sanch0panza@protonmail.com>
To: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Proposed CSV configuration file format for bip-genvbvoting
Date: Tue, 11 Apr 2017 09:11:19 -0400 [thread overview]
Message-ID: <oSJNwoymxRpAmalBAK3TJ02P5l3GrrAIaJjefWSkjLZwCJIFaS7QeeWWB9448L4h1_2xuDg3haLf8cC6iXLrppt0O0B8EZWR0ZEzUjJNs8k=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
Hi,
The link below includes documentation about a proposed CSV-based file format for fork deployment data (tentative config filename: forks.csv). This is planned to be used by my reference implementation of bip-genvbvoting (which is still in development - TBA later).
Other BIP9 improvement proposals are of course encouraged to use this format, and I'm happy to discuss extensions of it for things like supporting flag days or direct-to-activation transitions.
Regards,
Sancho
https://raw.githubusercontent.com/sanch0panza/bitcoin/genvbvoting-bu-dev/doc/genvbvoting.md
[-- Attachment #2: Type: text/html, Size: 807 bytes --]
reply other threads:[~2017-04-11 13:11 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='oSJNwoymxRpAmalBAK3TJ02P5l3GrrAIaJjefWSkjLZwCJIFaS7QeeWWB9448L4h1_2xuDg3haLf8cC6iXLrppt0O0B8EZWR0ZEzUjJNs8k=@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