[bitcoin-dev] Built in encryption

[bitcoin-dev] Built in encryption

[Ilan Oh]

[-- Attachment #1: Type: text/plain, Size: 463 bytes --]

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,

[-- Attachment #2: Type: text/html, Size: 766 bytes --]

Re: [bitcoin-dev] Built in encryption

[Lucas Clemente Vella]

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