1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
Return-Path: <ilansky.sharkson@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id C7462DE6
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 19 Feb 2018 09:21:35 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-it0-f46.google.com (mail-it0-f46.google.com
[209.85.214.46])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 707D1FE
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 19 Feb 2018 09:21:35 +0000 (UTC)
Received: by mail-it0-f46.google.com with SMTP id o13so8392021ito.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 19 Feb 2018 01:21:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
bh=J39VemOeMA0ROj4s1O0j1s202Mtldv6MI/Nkb8I9J6o=;
b=akq8Drvmp74TLfvv9PNz/O0Dqpg4V7A3010yd1lsdqfxbODizPLhU1Kis2YhQb+qG9
Zxo6Xk2SHZ6RuVC9uo1fQ7kwmPkzCPAV5bQpfK+SvNvunhm0Bgfg2i94Bnv4F5gNzknB
wiWAjK//DK63LHn/EKZw08WI7hU6u1d8cAGCyNVkzFUkMwGcV/5qZtKur+Lr53Sju81Z
fHUwSlbPbFp5BKxBKrblXSROg9e0+6gcxj2VL4Cs2JD5rOJ/kburxHW7MSKmN0dRkRTT
9YHivz4Blq7Vw6NefMIJ/rqgYREHfZcKgyPGlF9XocRaZZFmWW6QP2hpGE0vNbDeGUB3
/wFg==
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;
bh=J39VemOeMA0ROj4s1O0j1s202Mtldv6MI/Nkb8I9J6o=;
b=ni1/gOIh+E6we2vbK8OZThDPbpCLTtAbk4ZTA9MlNfC5fpLGPLNKB5WYzsotQ1NwjC
jfW9vXkuS9usq5jOgfipw3Grajf5wCAlUrJnJlgxlVsY/N6CA/lvlgroC6kmbilxGU1/
MuO1bTQKgcycO6szO1b3aUfteeV95Me2Wg5JxsXd8WUhgpMtR6qVpDbhFoJWdcXsg9VZ
AVs2PoMwQr+TRan3LMJuPz/uWfWbylmswjXNyr1lcNqsjWxN1nu290l8JcS+wOTBhtd3
Z25u7BfueMqKJtm1iL2nN8hweh4eUgr6feHz4ChdvlopTXCnLzN/FfHGwuGOypN6bNEa
f01g==
X-Gm-Message-State: APf1xPDmhOVgBf49jcG8SllkQRw3JYge1bSBFHh7IfYb4/C9GT1GYGAF
71eTH68Pbe/lzhgRT2KFYhZDwy8i8WdtQChuVYo=
X-Google-Smtp-Source: AH8x226QaFeU9ha1XPwgCpuqi8xZwWkhQDHq2xQjT4Tg4BzCHGx6kwWsC/BkHn2FxmoKprppeNtCeEhncp2IA/Nw6EI=
X-Received: by 10.36.176.11 with SMTP id d11mr18304396itf.20.1519032094588;
Mon, 19 Feb 2018 01:21:34 -0800 (PST)
MIME-Version: 1.0
Received: by 10.2.146.12 with HTTP; Mon, 19 Feb 2018 01:21:34 -0800 (PST)
Received: by 10.2.146.12 with HTTP; Mon, 19 Feb 2018 01:21:34 -0800 (PST)
In-Reply-To: <CALTsm7jS+z=NJO+WPK5VtEONsD7h1m0_yQq-0EmnYiG4hXKb2Q@mail.gmail.com>
References: <CALTsm7idtSXy=tUR_ahWj8qq9Ux-vYyeLdsKFoZoJx0biPdY=A@mail.gmail.com>
<CALTsm7jS9gQ=i5NqCT1ZJ1_o_sE302gNauwae=VSQ9-=QN7QXQ@mail.gmail.com>
<CALTsm7j8jF4HTbPX2s2rnUTpe7MbPagA2W-fZb+KPGN9ioxtvw@mail.gmail.com>
<CALTsm7gB9oMWbXg5iOXgK5POeZE-wQv+JgrE2BPFWD4gvhrwFg@mail.gmail.com>
<CALTsm7h3CEEeStGKpOqwudZ4oo1dvA91XFbEsO0U0i78-kuJog@mail.gmail.com>
<CALTsm7jS+z=NJO+WPK5VtEONsD7h1m0_yQq-0EmnYiG4hXKb2Q@mail.gmail.com>
From: Ilan Oh <ilansky.sharkson@gmail.com>
Date: Mon, 19 Feb 2018 10:21:34 +0100
Message-ID: <CALTsm7gcnBfgGzxVwGSOdcvC-8HE+42wiVCyd2utAxcEv0iejA@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="089e0822f27866845105658d38de"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
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: Mon, 19 Feb 2018 14:28:44 +0000
Subject: [bitcoin-dev] Built in encryption
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Feb 2018 09:21:35 -0000
--089e0822f27866845105658d38de
Content-Type: text/plain; charset="UTF-8"
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,
--089e0822f27866845105658d38de
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto">Hey guys,<div dir=3D"auto"><br></div><div dir=3D"auto">Fe=
atures info,</div><div dir=3D"auto">I know we can add text to a btc transac=
tion and it is pretty easy,</div><div dir=3D"auto"><br></div><div dir=3D"au=
to">However is it possible to encrypt the data in a way that only the recei=
ver would be able to read it in clear.=C2=A0</div><div dir=3D"auto">And of =
course without having to exchange info off the network.=C2=A0</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">And if not possible on bitcoin would =
it be possible on a sidechain or on rsk or else</div><div dir=3D"auto"><br>=
</div><div dir=3D"auto">I have few ideas of concrete uses of it, I'm su=
re you guys may also think of something interesting,</div><div dir=3D"auto"=
><br></div><div dir=3D"auto">Thanks,</div></div>
--089e0822f27866845105658d38de--
|
