From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 98BEEF3C for ; Fri, 19 Jan 2018 20:55:06 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-io0-f172.google.com (mail-io0-f172.google.com [209.85.223.172]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4B206FD for ; Fri, 19 Jan 2018 20:55:06 +0000 (UTC) Received: by mail-io0-f172.google.com with SMTP id 25so3514686ioj.9 for ; Fri, 19 Jan 2018 12:55:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:from:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=HkCCw78HpxWNrPMaMQFF2SIn5iGpyZ6QnCamCo0BejQ=; b=D2MkXks54kDh5AtqhUbtLIgqJJwqMxGidT8KH9My665hrXsppMnuDj/RHMhKEYqNGZ ZXgJvQj8tp0jZQk0cvZkIK94N7OwUHf0qL/4t+hrARIOo+LwnAH07LHjCx3EBZdMdH9I A74TmQTcTMsXWxhQTSVQOqUxU3HhW76doH8bnx1rlwgpz4okos9I//VkX+ijN44mXnQm We9zCNC73kNChKBA7+t7RY74nmE95L5N75Pt/3ukEtcvZcNv/mjlt8Vt+Xo3e+F+EKyP wTv/QI3HlRgMgSdHLsPLXoAjbGRZ+pdqT6W4oZLWq1AbyA7Bk6ty0eKA4l3Ttp/cDObQ wFhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=HkCCw78HpxWNrPMaMQFF2SIn5iGpyZ6QnCamCo0BejQ=; b=OQ6b5nuWkLY72yNM4gX20tl7r+rY8DaWXBrtqVpoRea3ZStI2ca/uUokH+EtfQ8KEr bl9sfVzZrSvSjSlvI9Reec5MmoK6o6Xuzw2Q7eSTzCW6G/N7UcSLVw9snYh2H2yjqhcK /p1RCUCa7rWR0pEHGiQBAgJSYtQCnbhD+KeKUSzvqXptmY7ejRM+c4eLoofrWEYz3XND GljGjA/IkkLkNMScErG+sXZDGMH1+sZoKRHg1NNS6rxdB6I4jeozV8MCo+/5UIX2A+Yk aPqRNCprwmOTAIzVWhIScGNhJonsBABj88RxFuybgpAqUY1x8s4kFzt3tI6dHbK3dPhD 8hLg== X-Gm-Message-State: AKwxyteZzYAk5YDowKnWohyNevi+VZIBGlMjeTCUWOiPfEk39gqINncz g2/4YEodE6sKDukeFP6wPuI+kQwE X-Google-Smtp-Source: ACJfBouZo+LRw/s/2AfGoB5iztCe0UMa/p1uoERWER01uO8K0ziC9v3oo8dSMhekJ7kDhmZ9o0rC/Q== X-Received: by 10.107.128.232 with SMTP id k101mr19787535ioi.152.1516395305055; Fri, 19 Jan 2018 12:55:05 -0800 (PST) Received: from ?IPv6:2601:441:8680:4631:c825:cb03:bee3:43f5? ([2601:441:8680:4631:c825:cb03:bee3:43f5]) by smtp.gmail.com with ESMTPSA id d189sm5299814iog.77.2018.01.19.12.55.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Jan 2018 12:55:03 -0800 (PST) From: Jefferson Carpenter To: Bitcoin Protocol Discussion References: <58fa85b8-cba3-ee34-8c96-41c6c7bfbf9c@gmail.com> Message-ID: <374ee97c-dae9-786f-5fc6-6fb6920360cb@gmail.com> Date: Fri, 19 Jan 2018 14:54:52 -0600 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <58fa85b8-cba3-ee34-8c96-41c6c7bfbf9c@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Fri, 19 Jan 2018 21:03:55 +0000 Subject: Re: [bitcoin-dev] Upgrading PoW algorithm X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jan 2018 20:55:06 -0000 Actually here's something we could possibly do: Fork off a blockchain that accepts Bitcoin blocks with strictly less than max difficulty. Because it does not accept max-difficulty blocks, it is a soft fork. Additionally, if difficulty of a block is set to max, then the difficulty field is extended so that it represents a higher max difficulty under a different hashing function, maybe SHA512. Because this blockchain also accepts differently-formatted blocks, it is also a hard fork. The idea is that this blockchain is identical to Bitcoin until the difficulty goes too high, at which point it diverges. Transitioning from the current SHA256 to a higher-difficulty hashing function could be difficult, since they might be solvable at proportionally different hashrates. In other words, max difficulty for SHA256 might be significantly faster than forcing the first 256 bits of a SHA512 hash... On 1/17/2018 4:31 PM, Jefferson Carpenter wrote: > Bitcoin's difficulty will be maxed out within about 400 years, by > Moore's law.  (After that - supposing the software does not crash when > difficulty overflows - block time will start decreasing, and it will not > take long before blocks are mined faster than photons can be sent across > the planet). > > Bitcoin is the dominant cryptocurrency today, as the first mover: the > perfectly fair worldwide game of inventing the cryptocurrency has been > played and won.  However, unfortunately, it has a built-in end date: > about 400 years from now.  After that, it won't necessarily be clear > what the dominant cryptocurrency is.  It might be a lot like VHS vs > Betamax, and a lot of people could lose a lot of money.  It seems to me, > this could be mitigated by planning today for what we are going to do > when Bitcoin finally breaks 400 years from now. > > Are there any distinct plans today for migrating to a PoW supporting an > even higher difficulty?