Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 39E16BF3 for ; Tue, 18 Apr 2017 14:52:06 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-ua0-f179.google.com (mail-ua0-f179.google.com [209.85.217.179]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7F57B1CE for ; Tue, 18 Apr 2017 14:52:05 +0000 (UTC) Received: by mail-ua0-f179.google.com with SMTP id q26so92787908uaa.0 for ; Tue, 18 Apr 2017 07:52:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jamin-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=h3tykOAsrn4UKJHLr/M6V+sCeFrBEalg3UiEJiq7i6A=; b=ABTeFcDt11aoXXZmW5GUPmDNKYwFf4p4809aOm77Ufk4Gxe7CO7yV94uYdKjUxag5Y VhXmW7UwkI+PC+6Zh3BJJ6x0qH1hLfrJh/Tm5RR8SFdaCGELgUH+UazQhkhqrSKXwwUa i4muAzDBway8Mb4NHJZQSWLJ5KVyTPXUZt8SCI29fSaudEOkOtrTHf0ZkXzAc3zg4QvG A7jSQeLE8O7iQWT1x22TuYt7FdehNqxJvJdGuesGkkSjLtJqaa7N6AogVTstzCvo2mAM eEwlWnXjBf8wwTT+lIHqAPST2veXQ2baGXkOkFWx6pzgxst5obaKgCmob8PcnavLkwDv 01Tw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=h3tykOAsrn4UKJHLr/M6V+sCeFrBEalg3UiEJiq7i6A=; b=YuGoiN0kkcsCeqkesvEVVANB2nkmpWTY2dxYC9KBP/XTsyAKMayyhMPlV15Ty4m81K mU8/PsO6WiQNEdQuJgbFOeSwI3UHOCfjMUkwUMi7UqXxPMSqWBJw+OLfgLCxJa/FRYvG pvoVaGHkDxfIztJkIgW/V+X07QzypfRk6qJ+8jk507B3IVPYPKQAFWPxtyPdzxZAuakf dNACd8mxB+ucahwW4AS3T0AC54pwCqZUcJOozp330KrN6DWeWbVxykxhBw/75kO9wQYJ YSTEOtFT16m6ROBJR2rL1xN5xbGLGfol0Cd8sC9NFSmpLBieiM1L+d0HCUKRrQCZ6LVT 9Dyw== X-Gm-Message-State: AN3rC/6sA0c6o8QAR+oUJixHErUSapSZl3Pw+qeSdZnki5Ow4cAwrVjX 3Mepe7xVX7N5rTCEs1XetT86cdscP5D/RKE= X-Received: by 10.176.86.19 with SMTP id y19mr2726923uaa.88.1492527124488; Tue, 18 Apr 2017 07:52:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.144.202 with HTTP; Tue, 18 Apr 2017 07:52:04 -0700 (PDT) In-Reply-To: References: From: Marcel Jamin Date: Tue, 18 Apr 2017 16:52:04 +0200 Message-ID: To: Erik Aronesty Content-Type: text/plain; charset=UTF-8 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,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: Tue, 18 Apr 2017 16:40:33 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Transaction signalling 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: Tue, 18 Apr 2017 14:52:06 -0000 Probably a bad idea for various reasons, but tagging (fee paying) transactions with info about the capabilities of the node that created it might be interesting? Might be useful to gauge economic support for certain upgrades, especially if excluding long transaction chains, etc. In the very least it would be a far better indicator than simply counting reachable nodes. On 17 April 2017 at 17:50, Erik Aronesty via bitcoin-dev wrote: > If users added a signal to OP_RETURN, might it be possible to tag all > validated input addresses with that signal. > > Then a node can activate a new feature after the percentage of tagged input > addresses reaches a certain level within a certain period of time? > > This could be used in addition to a flag day to trigger activation of a > feature with some reassurance of user uptake. > > > > > > > > > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >