From: Daniel Wilczynski <wilczynski.dan.dw@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] hypothetical: Could soft-forks be prevented?
Date: Mon, 18 Sep 2017 16:10:18 +0930 [thread overview]
Message-ID: <CAOC2iYWUX8cbUE=wqNUBOLY2egcO3d16=UzDn97uxGPthgFckg@mail.gmail.com> (raw)
Hi Dan.
What might be better aim is to have built in wipeout protection? In
softfork scenario this would protect a majority threatening a minority
with a wipeout if they do not opt in to some soft-fork consensus
change.
This could be partly done done by having automoated consensus critical
checkpoints, for example at 100 blocks deep. Maybe there are better
ways?
This would in effect turn softforks into hardforks.
Regards,
Daniel Wilczynski
next reply other threads:[~2017-09-18 6:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 6:40 Daniel Wilczynski [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-13 9:50 Dan Libby
2017-09-15 4:01 ` ZmnSCPxj
2017-09-15 9:14 ` Adam Back
2017-09-15 11:47 ` Tier Nolan
2017-09-15 20:01 ` Dan Libby
2017-09-15 19:55 ` Dan Libby
2017-09-15 20:40 ` Simone Bronzini
2017-09-15 21:48 ` Dan Libby
2017-09-16 1:42 ` Andrew Poelstra
2017-09-16 3:38 ` ZmnSCPxj
[not found] ` <CADSvpf7sC-Rh0qoGKgagQV7Mo_BV6ymeadgfMzJ_oXPCTyJ6Mw@mail.gmail.com>
2017-09-15 20:15 ` Dan Libby
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='CAOC2iYWUX8cbUE=wqNUBOLY2egcO3d16=UzDn97uxGPthgFckg@mail.gmail.com' \
--to=wilczynski.dan.dw@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