On 03/02/2016 03:02 PM, Peter Todd wrote: > On Wed, Mar 02, 2016 at 11:01:36AM -0800, Eric Voskuil via bitcoin-dev wrote: >>> A 6 month investment with 3 months on the high subsidy and 3 months on low >>> subsidy would not be made… >> >> Yes, this is the essential point. All capital investments are made based on >> expectations of future returns. To the extent that futures are perfectly >> knowable, they can be perfectly factored in. This is why inflation in >> Bitcoin is not a tax, it’s a cost. These step functions are made continuous >> by their predictability, removing that predictability will make them -- >> unpredictable. > > You know, I do agree with you. > > But see, this is one of the reasons why we keep reminding people that > strictly speaking a hardfork *is* an altcoin, and the altcoin can change > any rule currently in Bitcoin. > > It'd be perfectly reasonable to create an altcoin with a 22-million-coin > limit and an inflation schedule that had smooth, rather than abrupt, > drops. It'd also be reasonable to make that altcoin start with the same > UTXO set as Bitcoin as a means of initial coin distribution. > > If miners choose to start mining that altcoin en-mass on the halving, > all the more power to them. It's our choice whether or not we buy those > coins. We may choose not to, but if 95% of the hashing power decides to > go mine something different we have to accept that under our current > chosen rules confirmations might take a long time. > > Of course, personally I agree with Gregory Maxwell: this is all fairly > unlikely to happen, so the discussion is academic. But we'll see. > I agree, this is a perfectly rational interpretation. I also agree that this particular instance is academic. But I see more to this than accepting what is possible.
In the case of Federal Reserve Notes the gold obligation was abrogated. This was (at least) a contract default, implemented by force of arms. This contentious hard fork was clearly an attack. But in a system with no authority and in which nobody has formed a contractual obligation with anyone else, what would constitute an attack on the money? There is no difference between state attacks on (or collusion with) miners and miners acting on self interest. One answer is that nothing is an attack, it's up to the market to decide. But to the extent that there can be an attack on the money, the attempt to move the value of the coin to an altcoin (hard fork) is it. Though the choice of the term "attack" isn't essential. The importance of recognizing an attack is that it affords one the opportunity to defend against it. People holding "dollars" in 1933 were ill equipped to defend against a system level attack (monetary policy), in part because many did not recognize it as such, and in part because there was insufficient preparation by those who did. I see us building the tools and awareness necessary for defense. As you say, nobody has to buy into an altcoin forked from their coin. This much is simple to achieve. The more difficult problem is preserving the utility of the original coin. Clearly the purpose of a hard fork (as opposed to a new coin) is to transfer this value. We've all seen arguments for contentious hard fork deployment that explicitly depend on the fear of monetary loss to drag people to acceptance. While this may be the nature of the technology, it's important that we develop effective defense against it. Ultimately the only defense is individual validation. The collusion of banks (web wallets) with miners in attacking consensus is obvious. But even without active collusion, the surrender of validation leaves people just as defenseless as *being* unarmed while retaining a right to *become* armed. Even if every person mines at the same level, the system amounts to little more than majority rule if validation is not decentralized. There are people perfectly willing to exploit this weakness. e
Description: OpenPGP digital signature
_______________________________________________ bitcoin-dev mailing list email@example.com https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev