From: Lucas Clemente Vella <lvella@gmail.com>
To: Ilan Oh <ilansky.sharkson@gmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Built in encryption
Date: Mon, 19 Feb 2018 17:11:56 -0300 [thread overview]
Message-ID: <CAGCathxmsUHhucXajmAp=2i=-F=heYj3AEOCdty8Nzy4SmGTsg@mail.gmail.com> (raw)
In-Reply-To: <CALTsm7gcnBfgGzxVwGSOdcvC-8HE+42wiVCyd2utAxcEv0iejA@mail.gmail.com>
Theoretically, if the recipient address had already disclosed the
public key (i.e. already spent from that address), or shared it with
you instead of (or alongside with) the address, then you can use
recipient's ECDSA key to encrypt the message with ECC, as both ECDSA
and ECC share the same kind of public/private key pair, according to
the this link: https://crypto.stackexchange.com/questions/14662/using-ecdsa-keys-for-encryption
In practice, I am not sure the nodes would broadcast such non-standard
transaction (but it can be mined, nonetheless).
2018-02-19 6:21 GMT-03:00 Ilan Oh via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org>:
> Hey guys,
>
> Features info,
> I know we can add text to a btc transaction and it is pretty easy,
>
> However is it possible to encrypt the data in a way that only the receiver
> would be able to read it in clear.
> And of course without having to exchange info off the network.
>
> And if not possible on bitcoin would it be possible on a sidechain or on rsk
> or else
>
> I have few ideas of concrete uses of it, I'm sure you guys may also think of
> something interesting,
>
> Thanks,
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--
Lucas Clemente Vella
lvella@gmail.com
prev parent reply other threads:[~2018-02-19 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALTsm7idtSXy=tUR_ahWj8qq9Ux-vYyeLdsKFoZoJx0biPdY=A@mail.gmail.com>
[not found] ` <CALTsm7jS9gQ=i5NqCT1ZJ1_o_sE302gNauwae=VSQ9-=QN7QXQ@mail.gmail.com>
[not found] ` <CALTsm7j8jF4HTbPX2s2rnUTpe7MbPagA2W-fZb+KPGN9ioxtvw@mail.gmail.com>
[not found] ` <CALTsm7gB9oMWbXg5iOXgK5POeZE-wQv+JgrE2BPFWD4gvhrwFg@mail.gmail.com>
[not found] ` <CALTsm7h3CEEeStGKpOqwudZ4oo1dvA91XFbEsO0U0i78-kuJog@mail.gmail.com>
[not found] ` <CALTsm7jS+z=NJO+WPK5VtEONsD7h1m0_yQq-0EmnYiG4hXKb2Q@mail.gmail.com>
2018-02-19 9:21 ` [bitcoin-dev] Built in encryption Ilan Oh
2018-02-19 20:11 ` Lucas Clemente Vella [this message]
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='CAGCathxmsUHhucXajmAp=2i=-F=heYj3AEOCdty8Nzy4SmGTsg@mail.gmail.com' \
--to=lvella@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=ilansky.sharkson@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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