From: Christopher Gilliard <christopher.gilliard@gmail•com>
To: Jeremy <jlrubin@mit•edu>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP - limiting OP_RETURN / HF
Date: Fri, 16 Apr 2021 17:05:12 +0000 [thread overview]
Message-ID: <CAK=nyAwbWbEkL29J-teW-NJ+28pgrCVEvP5csH65uzCWfP=9KA@mail.gmail.com> (raw)
In-Reply-To: <CAD5xwhiAPkxRxvgJNU3uG7LLToa-+9j7CdXYWvOYOpZKz-p7Hw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
Hah! Very funny! 😁 I 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 to find those
keys for a unit test.
On Fri, Apr 16, 2021 at 4:32 PM Jeremy <jlrubin@mit•edu> 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 <https://twitter.com/JeremyRubin>
> <https://twitter.com/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
>>
>
[-- Attachment #2: Type: text/html, Size: 2678 bytes --]
next prev parent reply other threads:[~2021-04-16 17:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 7:45 Christopher Gilliard
2021-04-16 13:56 ` Russell O'Connor
2021-04-16 15:34 ` Christopher Gilliard
2021-04-16 15:55 ` Andrew Poelstra
2021-04-16 23:52 ` ZmnSCPxj
2021-04-17 3:57 ` Christopher Gilliard
2021-04-17 15:50 ` Peter Todd
2021-04-17 16:57 ` Christopher Gilliard
2021-04-16 13:59 ` Clark Moody
2021-04-16 15:33 ` Christopher Gilliard
2021-04-16 16:32 ` Jeremy
2021-04-16 17:05 ` Christopher Gilliard [this message]
2021-04-16 18:00 ` Jeremy
2021-04-16 19:15 ` Kostas Karasavvas
2021-04-16 20:12 ` Christopher Gilliard
2021-04-17 7:41 ` Kostas Karasavvas
2021-04-16 20:30 ` Ruben Somsen
2021-04-16 21:09 ` Christopher Gilliard
2021-04-20 1:23 ` yanmaani
2021-04-20 8:45 ` Zach Greenwood
2021-04-20 17:12 ` Christopher Gilliard
2021-04-20 19:07 ` Ruben Somsen
2021-05-03 5:17 ` ZmnSCPxj
2021-05-04 12:51 ` Ruben Somsen
2021-04-20 1:22 ` yanmaani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK=nyAwbWbEkL29J-teW-NJ+28pgrCVEvP5csH65uzCWfP=9KA@mail.gmail.com' \
--to=christopher.gilliard@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jlrubin@mit$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox