If difficulty is X, range for adjustment is X/4 to X*4. On Sat, Sep 13, 2014 at 12:45 PM, s7r <s...@sky-ip.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > On 9/13/2014 7:34 PM, Jeff Garzik wrote: >> Why not on mainnet? It is simply much lower priority for bitcoin >> today than other problems. It tends not to happen at higher >> difficulties for a variety of reasons. >> >> The difficulty adjustment is capped at a factor of 4, up or down, >> to address some other attacks that can happen in mining. >> > Capped at a factor of 4, up or down? How exactly in a simple example? > >> Personally, I think there needs to be a mainnet safety rule such >> as "if 24 hours goes by without a block, you may mine a block" etc. >> But I readily admit I've not thought through all the ramifications >> of such a policy. >> >> >> >> On Sat, Sep 13, 2014 at 12:00 PM, s7r <s...@sky-ip.org> wrote: >> >> >> On 9/13/2014 5:04 PM, Jeff Garzik wrote: >>>>> This is why testnet has a special rule: If 20 minutes >>>>> passes without a block, you may mine a diff-1 block. >>>>> >> >> Thanks for your point of view Mr. Garzik. Why aren't we using this >> in the real bitcoin network too? If it's good for balancing the >> functionality of the network in the context of sudden hashrate >> moves? Specially down moves, since if the hash power goes UP, the >> network will see blocks are created more often than at every 10 >> minutes and adjust the difficulty directly proportional, correct? >> >>>>> >>>>> On Sat, Sep 13, 2014 at 9:15 AM, s7r <s...@sky-ip.org> wrote: >>>>> Hi there, >>>>> >>>>> I have an contradictory discussion with an altcoin supporter >>>>> and want to bring some solid arguments in a public talk, so >>>>> require little help to respond to a question with simplest >>>>> answer. >>>>> >>>>> The problem is within the difficulty adjustment mechanism, >>>>> that it happens at every 2016 blocks. In case the hash power >>>>> will suddenly decrease, the 2016 blocks will take a lot of >>>>> time to solve, therefor freeze the network in a >>>>> non-operational way. I know by far this is just a joke, >>>>> because this is very unlikely to happen anytime (people paid >>>>> for mining equipment and make money) but for the sake of >>>>> discussion, let's just assume it 'could' happen. >>>>> >>>>> Can this really freeze the network for unlimited time and >>>>> bitcoin has no mechanism to balance it back? A resourceful >>>>> party with the intent to attack the network in an irrational >>>>> way, brings lot of hashing power and keeps it for 2016 >>>>> blocks, then removes it leaving the other 2016 blocks to >>>>> solve at very high difficulty but with low hash power in the >>>>> network causing a 'blackout'? Thank you in advance for your >>>>> answers. >>>>> >>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> >>>>>> >> >>>>>> > Want excitement? >>>>>> Manually upgrade your production database. When you want >>>>>> reliability, choose Perforce Perforce version control. >>>>>> Predictably reliable. >>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk >>>>>> >>>>>> >> >>>>>> > _______________________________________________ >>>>>> bitcoin-list mailing list >>>>>> bitcoin-list@lists.sourceforge.net >>>>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-list >>>>> >>>>> >>>>> >> >> >> > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (MingW32) > > iQEcBAEBAgAGBQJUFHSeAAoJEIN/pSyBJlsRQ7gH/3iB0sy4PRi03dbcq5mKiwc4 > aBlG2zt8rVRqX6KkCoeijY4lysg3KYzhyBBUna4bwGAhpvBe0jjybEWFAMqM2h6+ > 7JzUdcZ9K5HuOtQUY2/4jHAz6jg3LOCBvtJUmLtC1HGSGHSl0tFiRVc2bzWrIOsT > zkq87G3ocfSNiQSRSKqhxM1W4tc1BUHBr6T0ZS2EyArZljnIN5WVfw3ueTPZizdM > q51+krxBjIW5iEkS4pVNChlsMaMca6JLVOY8jJpEWDf0vTX9zsheMdDg0MyDfMn5 > ObywubBmV+tawNsHU7DWwliIiCoMr2h2G7KpV8V/np1iVyaSribaIj1hM/rWvh8= > =Q1i9 > -----END PGP SIGNATURE-----
-- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/ ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ bitcoin-list mailing list bitcoin-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-list
