Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id C0596C000A for ; Fri, 16 Apr 2021 17:05:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id BAAF484B23 for ; Fri, 16 Apr 2021 17:05:28 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp1.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I8pMwwIXwE0W for ; Fri, 16 Apr 2021 17:05:24 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com [IPv6:2607:f8b0:4864:20::232]) by smtp1.osuosl.org (Postfix) with ESMTPS id 9584B84B20 for ; Fri, 16 Apr 2021 17:05:24 +0000 (UTC) Received: by mail-oi1-x232.google.com with SMTP id k25so28538703oic.4 for ; Fri, 16 Apr 2021 10:05:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8UvccYbH0fAWDaEEWwtpKvCTB8/rey7tWlZEqyDyLDs=; b=OuonFeZw5J0Vb5dIP4cAPYb/IQ9GlXUGU8JFNUJNNhoiZqrN6r4YEEpNo2CE5LmtE5 LeEp13pVeV3YuLB7jtNNWZLpRourmZ5oddLlTCAzolMdQhhjiQ94ZGC3EoVgZ8spJyVh xCGkWNChzUczCqosfwllp47ub4DSYet99YYrB3LPkZGHBf5Vd6Ui+upXOIsEJAqfb6/i XboWpuPbC7xlJjaZRQ5xKQUCcIjMSdyNpjE0R4nRdwbqfa8umRNAtvNsyPi4zcgtzrLP NIg1F8WOs4Vhl7NaZK0vCXv4SI9WO3MKjJ2TQ7hsHaNM26Dztb/FKoPjywc0dPdC+6Pv 9zmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8UvccYbH0fAWDaEEWwtpKvCTB8/rey7tWlZEqyDyLDs=; b=TEp7WGwMh0JVNgPa0cDtSeEkZ1yELopyLfRd4tswQeAa/Z3IHjCbvkPNQZTLdF+8Ff VYLzyhC22222/+U7GrWbaljTNDJgHTY8W1u4YuQdQybaEpcTfu6wpR0ip+07uA/IHums YqgADt7lcUTz/MNrpFbOWZhV/v4JnB65IVWRWBfe9CJ1A3guvZFg9Lfbscs2+OhqQCHF 0fJjrgB7HJ/uWxqtkSmLvIAHkfsSN9+SEZEvLQsdQVITehLv62fIfooi5ukPxCa5cmXg WgKU9kK5XFFBC7dim7uLXUpfs0bVbWiert8wtva9TxQhs7jYn958P/qd5dglOTFRaIWg x+rQ== X-Gm-Message-State: AOAM532bIqKDJEbP98BrQ/bagD9VbZXdH4/1kBUIN/d1YF3UB46dnddS 1QhYEwahhb6MbJJKF8zWGNGeh08bTsV40ZGNyCg= X-Google-Smtp-Source: ABdhPJw7u8GkBKXLwnjt00+y5UaCr7KzRdbsptD5O+sWEb6yJFojTVkNaO4oOeaNQFI1zAWRz0DM7l1QF9JKU3Pg/WU= X-Received: by 2002:aca:5e55:: with SMTP id s82mr7170455oib.9.1618592723642; Fri, 16 Apr 2021 10:05:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Christopher Gilliard Date: Fri, 16 Apr 2021 17:05:12 +0000 Message-ID: To: Jeremy Content-Type: multipart/alternative; boundary="000000000000542ee305c019fcb4" X-Mailman-Approved-At: Fri, 16 Apr 2021 17:16:43 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] BIP - limiting OP_RETURN / HF X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Apr 2021 17:05:28 -0000 --000000000000542ee305c019fcb4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hah! Very funny! =F0=9F=98=81 I am certain that this proposal can be implem= ented in a way that doesn't confiscate your "long lost" stash and I may even be willing to fund a bounty for a deep sea diving expedition to find those keys for a unit test. On Fri, Apr 16, 2021 at 4:32 PM Jeremy wrote: > NACK -- I happen to have a vault where I made emergency backup pre-signed > transactions containing two OP_RETURN outputs and have subsequently lost > the private key in an unfortunate boating incident. > > This proposed rule change would serve to confiscate my funds. > -- > @JeremyRubin > > > > On Fri, Apr 16, 2021 at 6:32 AM Christopher Gilliard via bitcoin-dev < > bitcoin-dev@lists.linuxfoundation.org> wrote: > >> I have created a BIP which can be found here: >> https://github.com/cgilliard/bips/blob/notarization/bip-XXXX.mediawiki >> >> I'm sending this email to start the discussion regarding this proposal. >> If there are any comments/suggestions, please let me know. >> >> Regards, >> Chris >> _______________________________________________ >> bitcoin-dev mailing list >> bitcoin-dev@lists.linuxfoundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >> > --000000000000542ee305c019fcb4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hah! Very funny!=C2=A0=F0=9F=98=81=C2=A0I am certain that = this proposal can be implemented in a way that doesn't confiscate your = "long lost" stash and I may even be willing to fund a bounty for = a deep sea diving expedition=C2=A0to find those keys for a unit test.
=
On Fri= , Apr 16, 2021 at 4:32 PM Jeremy <jlr= ubin@mit.edu> wrote:
NACK -- I = happen to have a vault where I made emergency backup pre-signed transaction= s containing two OP_RETURN outputs and have subsequently lost the private k= ey in an unfortunate boating incident.

This proposed rule chang= e would serve to confiscate my funds.


On Fri, Apr 16, 2021 at 6:3= 2 AM Christopher Gilliard via bitcoin-dev <bitcoin-dev@lists.linuxfounda= tion.org> wrote:
I have created a BIP which can be found here:=C2= =A0https://github.com/cgilliard/bips/blob/notariz= ation/bip-XXXX.mediawiki

I'm sending this email = to start the discussion regarding this proposal. If there are any comments/= suggestions, please let me know.

Regards,
Chris
_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--000000000000542ee305c019fcb4--