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 0F7CBB88 for ; Mon, 19 Jun 2017 20:24:32 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 95BE5212 for ; Mon, 19 Jun 2017 20:24:29 +0000 (UTC) Received: by mail-oi0-f50.google.com with SMTP id p66so28270283oia.0 for ; Mon, 19 Jun 2017 13:24:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=friedenbach-org.20150623.gappssmtp.com; s=20150623; h=from:content-transfer-encoding:mime-version:date:subject:message-id :references:in-reply-to:to; bh=5ps40d+euPGeLUcA3iwxvC+L/7+a1s1wxIen1b1sXjg=; b=xiJhM0siC+5fv5IOKaLBPCDwt/PXv78KvGC9XXkbt1a9Xzw07r8Wl9r93yj1eJKrsT zKH66kJqNhhlVXIY/aoezij5mfho8kWhwY3EiEYj4AzaPyFEMKcDKbrM3VjZIOwZK7TU Ffwhb9ZJdWlbUUL6E9g3xhG6YVnsEKZy4ywsvmgxKWcwX7CoTPMwiqDcFjkz0hBnf6uu EYKfY3EK5lh6Y5d5O6jE2WS9plTrWm7p28UaPN2v02kNCKokGYCAQemw3QrSZD0bURtW aqPrXHGFquXtIVLSKq74GQFBf4NNpPfIq9edEaYRWIiIKb2OG52HsLm4sE8XIY0IV1ry XYKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:message-id:references:in-reply-to:to; bh=5ps40d+euPGeLUcA3iwxvC+L/7+a1s1wxIen1b1sXjg=; b=gxMGENhFxOklBalV5DIwSSjLbF9Hrid4aUxX6DDh1BA/tzon7mfQ6ZnA82IrhcTdzs HNTE/TGDVGtoaKikw1/sIDG4Ey3GdvxXzSOT7rg+hg2IPlC/L4/DJ4Ob2qFqL4Ft0Oiw hM0qlZ9GuE//udyTx56KFtIrSw6CQIguP3n4klMEFPEd38CkhBT5mGCzYo+d56TQvhGk nGAxctIFoXFiwK156FsC8+cxxdXIqeo6KpkFVyhB/FKDF/H5T4rxCe3hFHKTNaVp2/if AN9gYQvPlsEYOp7yjpx6hufGBtB6Ydj8b+4Lt3IvfiuXBCe2PF3JeuMOIGZnBSUrM86V al/g== X-Gm-Message-State: AKS2vOw+4svLj7b8O9f0kRemRqLWpixBqz5JOpevDC6WMEV+BcilchV2 uRcR4iSblCSPfmpB0PtBBg== X-Received: by 10.202.48.193 with SMTP id w184mr8016320oiw.67.1497903868795; Mon, 19 Jun 2017 13:24:28 -0700 (PDT) Received: from [100.168.240.0] ([172.56.6.223]) by smtp.gmail.com with ESMTPSA id 14sm6130346oth.10.2017.06.19.13.24.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Jun 2017 13:24:27 -0700 (PDT) From: Mark Friedenbach Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Mon, 19 Jun 2017 13:24:25 -0700 Message-Id: References: <201706191926.25006.luke@dashjr.org> <3654399.ZkJ0Jlgova@cherry> In-Reply-To: <3654399.ZkJ0Jlgova@cherry> To: Tom Zander , bitcoin-dev@lists.linuxfoundation.org X-Mailer: iPhone Mail (14F89) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, MIME_QP_LONG_LINE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Mon, 19 Jun 2017 20:27:31 +0000 Subject: Re: [bitcoin-dev] BIP148 temporary service bit (1 << 27) 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: Mon, 19 Jun 2017 20:24:32 -0000 It is essential that BIP-148 nodes connect to at least two other BIP-148 nod= es to prevent a network partition in August 1st. The temporary service but i= s how such nodes are able to detect each other. > On Jun 19, 2017, at 12:46 PM, Tom Zander via bitcoin-dev wrote: >=20 >> On Monday, 19 June 2017 21:26:22 CEST Luke Dashjr via bitcoin-dev wrote: >> To ease the transition to BIP148 and to minimise risks in the event miner= s >> choose to perform a chain split attack, at least Bitcoin Knots will be >> using the temporary service bit (1 << 27) to indicate BIP148 support. >>=20 >> Once the transition is complete, this will no longer be necessary, and th= e >> bit will be (manually) returned for reuse. >>=20 >> I encourage other software implementing BIP148 (both full and light nodes= ) >> to set and use this service bit to avoid network partitioning risks. >=20 > I'm curious what you action on the finding (or not) of a peer with this bi= t=20 > set (or not). > Can you link to the github commit where you implemented this? > --=20 > Tom Zander > Blog: https://zander.github.io > Vlog: https://vimeo.com/channels/tomscryptochannel > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev