From: Anthony Towns <aj@erisian.com.au>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] "Changes without unanimous consent" talk at Scaling Bitcoin
Date: Mon, 6 Nov 2017 03:50:33 +1000 [thread overview]
Message-ID: <20171105175033.GB23915@erisian.com.au> (raw)
Hi,
Paper (and slides) for my talk in the Consensus stream of Scaling Bitcoin
this morning are at:
https://github.com/ajtowns/sc-btc-2017/releases
Some analysis for split-related consensus changes, and (code-less)
proposals for generic replay protection (a la BIP 115) and providing a
better level of price discovery for proposals that could cause splits.
Cheers,
aj
reply other threads:[~2017-11-05 17:50 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=20171105175033.GB23915@erisian.com.au \
--to=aj@erisian.com.au \
--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