Return-Path: <daniele.pinna@gmail.com> Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id D807B19FE for <bitcoin-dev@lists.linuxfoundation.org>; Fri, 2 Oct 2015 08:31:54 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-vk0-f53.google.com (mail-vk0-f53.google.com [209.85.213.53]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5F4CAEC for <bitcoin-dev@lists.linuxfoundation.org>; Fri, 2 Oct 2015 08:31:54 +0000 (UTC) Received: by vkat63 with SMTP id t63so55618703vka.1 for <bitcoin-dev@lists.linuxfoundation.org>; Fri, 02 Oct 2015 01:31:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=0uulkCZIwhRZbWMTl0qk9UQYo8ZWEEvjQ+m3PpowvCY=; b=VLofCumt2L+aZsjzTA4UpGBbmmOFJXutkdA+WwkMHIjSdNy1xvHXze/fqdTwTALVHf hrNoGlZ0lXhIDt8aHzNY737Loft3JFKWuzc2gak23oG552Pi0aw1XbZeF35RWkmkAEt2 E78X+VHjcZOXRIesQZsWxqIWSKs0nBgDcwK6oTlVFkOOtd+DGN1771WQLKT1Zz1V1hvW DKLom+hZGRq134/d2iLpoVXahWDTgy5v2/dbNhJeNvNzKMz2YZ0bGJFQINvpVkh8CZMy HTLLLYGsJi6Cjoio2TI6MaDn5a/hxCZWVU110/jNZY+QemolKVP//VNlKSgE+LneIwgE ierA== X-Received: by 10.31.190.6 with SMTP id o6mr9748468vkf.120.1443774713711; Fri, 02 Oct 2015 01:31:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.1.69 with HTTP; Fri, 2 Oct 2015 01:31:34 -0700 (PDT) In-Reply-To: <CABm2gDrOt2m6xfYjtVJne6Cm2nawXtA2-a4y7kaEA1fEgkUUUA@mail.gmail.com> References: <CAEgR2PFQtr78B3t147=3Ko4VnTGevb0QCySk=hDSqeFHZk=MPQ@mail.gmail.com> <CABm2gDrOt2m6xfYjtVJne6Cm2nawXtA2-a4y7kaEA1fEgkUUUA@mail.gmail.com> From: Daniele Pinna <daniele.pinna@gmail.com> Date: Fri, 2 Oct 2015 10:31:34 +0200 Message-ID: <CAEgR2PFwmeWQFCVX-Na9Lf4S1zoLAE57cDGteiyaYQ-GLjssqg@mail.gmail.com> To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc> Content-Type: multipart/alternative; boundary=001a11c019c0f2558905211afe14 X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org> Subject: Re: [bitcoin-dev] Dev-list's stance on potentially altering the PoW algorithm X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org> List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> X-List-Received-Date: Fri, 02 Oct 2015 08:31:55 -0000 --001a11c019c0f2558905211afe14 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Interesting! I didn't notice BIP 99's anti-miner hardfork proposal.... thanks for pointing it out to me. Dpinna Daniele Pinna, Ph.D On Fri, Oct 2, 2015 at 10:20 AM, Jorge Tim=C3=B3n <jtimon@jtimon.cc> wrote: > > On Oct 2, 2015 10:03 AM, "Daniele Pinna via bitcoin-dev" < > bitcoin-dev@lists.linuxfoundation.org> wrote: > > > > should an algorithm that guarantees protection from ASIC/FPGA > optimization be found. > > This is demonstrably impossible: anything that can be done with software > can be done with hardware. This is computer science 101. > And specialized hardware can always be more efficient, at least > energy-wise. > > On the other hand, BIP99 explicitly contemplates "anti-miner hardforks" > (obviously not for so called "ASIC-resistance" [an absurd term coined to > promote some altcoins], but just for restarting the ASIC and mining marke= t > in case mining becomes too centralized). > --001a11c019c0f2558905211afe14 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Interesting! I didn't notice BIP 99's anti-mi= ner hardfork proposal.... thanks for pointing it out to me.<br><br></div>Dp= inna<br></div><div class=3D"gmail_extra"><br clear=3D"all"><div><div class= =3D"gmail_signature"><div dir=3D"ltr"><div>Daniele Pinna, Ph.D</div></div><= /div></div> <br><div class=3D"gmail_quote">On Fri, Oct 2, 2015 at 10:20 AM, Jorge Tim= =C3=B3n <span dir=3D"ltr"><<a href=3D"mailto:jtimon@jtimon.cc" target=3D= "_blank">jtimon@jtimon.cc</a>></span> wrote:<br><blockquote class=3D"gma= il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef= t:1ex"><span class=3D""><p dir=3D"ltr"><br> On Oct 2, 2015 10:03 AM, "Daniele Pinna via bitcoin-dev" <<a h= ref=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitc= oin-dev@lists.linuxfoundation.org</a>> wrote:<br> ><br> > should an algorithm that guarantees protection from ASIC/FPGA optimiza= tion be found.</p> </span><p dir=3D"ltr">This is demonstrably impossible: anything that can be= done with software can be done with hardware. This is computer science 101= .<br> And specialized hardware can always be more efficient, at least energy-wise= . </p> <p dir=3D"ltr">On the other hand, BIP99 explicitly contemplates "anti-= miner hardforks" (obviously not for so called "ASIC-resistance&qu= ot; [an absurd term coined to promote some altcoins], but just for restarti= ng the ASIC and mining market in case mining becomes too centralized).</p> </blockquote></div><br></div> --001a11c019c0f2558905211afe14--