From: ZmnSCPxj <ZmnSCPxj@protonmail•com>
To: Ben Kloester <benkloester@gmail•com>
Cc: Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Scott Roberts <zawy@yahoo•com>
Subject: Re: [bitcoin-dev] New difficulty algorithm needed for SegWit2x fork? (reformatted text)
Date: Tue, 10 Oct 2017 22:48:13 -0400 [thread overview]
Message-ID: <3gKnWsuNvEzNfEElWCweCKECVgKqukJcpMC5Oy-3YbEsJxGxVFKNg8PPCk2sP-3SblJAJb4wG9q83qvi0tmy4c1xXyeFisutguJDF5uC7QY=@protonmail.com> (raw)
In-Reply-To: <CANgJ=T827Z=epjFvhSGNg32X3mXH3XyMNcvuXSLYjf369X1gjA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2639 bytes --]
Good morning Ben,
I am not Mark, and I am nowhere near being a true Core developer yet, but I would like to point out that even under a 51% attack, there is a practical limit to the number of blocks that can be orphaned. It would still take years to rewrite history from the Genesis block, for instance.
What little data we have (BT1 / BT2 price ratio on BitFinex) suggests that tokens solely on the 2X chain will not be valued as highly as tokens solely on the Core chain. As miners generate tokens that are only for a specific chain, they will have higher incentive to gain tokens on the Core chain rather than the 2X chain.
As is commonly said, hodling is free, whereas mining is not. Hodlers have much greater power in hardfork situations than miners have: simply by selling their tokens on the 2X chain and not in the Core chain, hodlers can impose economic disincentives for mining of the 2X chain.
Miners can switch to BCH, but that is valued even less than BT2 tokens are, and thus even less attractive to mine on.
We should also pay attention, that BCH changed its difficulty algorithm, and it is often considered to be to its detriment due to sudden hashpower oscillations on that chain. We should be wary of difficulty algorithm changes, as it is the difficulty which determines the security of the chain.
--
If we attempt to deploy a difficulty change, that is a hardfork, and hodlers will be divided on this situation. Some will sell the tokens on the difficulty-change hardfork, some will sell the tokens on the non-difficulty-change hardfork. Thus the economic punishment for mining the 2X chain will be diluted due to the introduction of the difficulty-change hardfork, due to splitting of the hodler base that passes judgment over development.
Thus, strategy-wise, it is better to not hardfork (whether difficulty adjustment, PoW change, or so on) in response to a contentious hardfork, as hodlers can remain united against or for the contentious hardfork. Instead, it is better to let the market decide, which automatically imposes economic sanctions on miners who choose against the market's decision. Thus, it is better to simply let 2X die under the hands of our benevolent hodlers.
Later, when it is obvious which fate is sealed, we can reconsider such changes (difficulty adjustment, PoW change, block size) when things are calmer. However, such changes cannot be safely done in response to a contentious hardfork.
--
If indeed the Core chain is eradicated, then Bitcoin indeed has failed and I would very much rather sell my hodlings and find some other means to amuse myself.
Regards,
ZmnSCPxj
[-- Attachment #2: Type: text/html, Size: 3064 bytes --]
next prev parent reply other threads:[~2017-10-11 2:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1213518291.4328204.1507589852818.ref@mail.yahoo.com>
2017-10-09 22:57 ` Scott Roberts
2017-10-10 2:19 ` Mark Friedenbach
2017-10-10 2:57 ` Ben Kloester
2017-10-10 10:34 ` greg misiorek
2017-10-11 1:44 ` Ben Kloester
2017-10-11 2:48 ` ZmnSCPxj [this message]
2017-10-11 4:08 ` Mark Friedenbach
2017-10-11 15:28 ` Moral Agent
[not found] <1885357.5164984.1507685394910.ref@mail.yahoo.com>
2017-10-11 1:29 ` Scott Roberts
2017-10-12 8:51 Scott Roberts
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='3gKnWsuNvEzNfEElWCweCKECVgKqukJcpMC5Oy-3YbEsJxGxVFKNg8PPCk2sP-3SblJAJb4wG9q83qvi0tmy4c1xXyeFisutguJDF5uC7QY=@protonmail.com' \
--to=zmnscpxj@protonmail$(echo .)com \
--cc=benkloester@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=zawy@yahoo$(echo .)com \
/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