summaryrefslogtreecommitdiff
path: root/5d/da71e4de1b3fcf2f6ff1fa2b66ba75a4afe39d
blob: ba2d32918ee8d95c68b5779f0fcbe1f579994ee3 (plain)
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
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
Return-Path: <tensiam@hotmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 83DE6C1A1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri,  8 Feb 2019 10:12:11 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from EUR01-HE1-obe.outbound.protection.outlook.com
	(mail-oln040092065108.outbound.protection.outlook.com [40.92.65.108])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 60AA027B
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri,  8 Feb 2019 10:12:08 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com;
	s=selector1;
	h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
	bh=BF0aUTcis16xtTYG1ovtt2+CKp3zG7YCevcMUFfj/o4=;
	b=iydq+960eQbsM6vyPiZ/GpK0MyPnliCwiuCSvAUINet+AYXkj6zBxBItqna5flO4IIXAhB5f+DmuG9WULVyUy9RwlOVwDbPQnM4cLF0WjxwgqyMs990qOT5RVg81hkKxgNxK47f2jUmIhjhdF3a6OYZJnhGlnd+OB1gpncQvF+uQS8YiAc4up63Tuy2gGwjmPZrTx7P1cviDCo5318veQx6g29k6zbXmFBIR3AY/K7gYIMNxRqb1VBERWLrgD0R46zetpIfqy/eo0zWLlittuEafXCkpTFIlny1c76oGuQ9tJbqELQx7pj6Hd1QERWTGlAdUMEZlEeCA88CcgpBmgQ==
Received: from VE1EUR01FT041.eop-EUR01.prod.protection.outlook.com
	(10.152.2.53) by VE1EUR01HT191.eop-EUR01.prod.protection.outlook.com
	(10.152.3.236) with Microsoft SMTP Server (version=TLS1_2,
	cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1580.10;
	Fri, 8 Feb 2019 10:12:06 +0000
Received: from DB6PR10MB1832.EURPRD10.PROD.OUTLOOK.COM (10.152.2.55) by
	VE1EUR01FT041.mail.protection.outlook.com (10.152.3.103) with Microsoft
	SMTP
	Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id
	15.20.1580.10 via Frontend Transport; Fri, 8 Feb 2019 10:12:06 +0000
Received: from DB6PR10MB1832.EURPRD10.PROD.OUTLOOK.COM
	([fe80::85e1:a698:7b7c:a02c]) by
	DB6PR10MB1832.EURPRD10.PROD.OUTLOOK.COM
	([fe80::85e1:a698:7b7c:a02c%6]) with mapi id 15.20.1601.016;
	Fri, 8 Feb 2019 10:12:06 +0000
From: "Kenshiro []" <tensiam@hotmail.com>
To: "bitcoin-dev@lists.linuxfoundation.org"
	<bitcoin-dev@lists.linuxfoundation.org>
Thread-Topic: Implementing Confidential Transactions in extension blocks
Thread-Index: AQHUv5aqK9doshwpj0CV+ZeZH4q9cg==
Date: Fri, 8 Feb 2019 10:12:06 +0000
Message-ID: <DB6PR10MB183228F27750132F9A6A3542A6690@DB6PR10MB1832.EURPRD10.PROD.OUTLOOK.COM>
Accept-Language: en-US, es-ES
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-incomingtopheadermarker: OriginalChecksum:2BB7065EB7BD8AB33770D3A92C4B501ECB1866E98B9D5141C28D9A656CE65509;
	UpperCasedChecksum:9B199E4705E9748A3A07B85F990374BB6EF82021B205E7F44D1C8CCCA62836F4;
	SizeAsReceived:6803; Count:42
x-tmn: [TPbSxCn6DCurKmLAF0zQEhRvPBZ2W1b5]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VE1EUR01HT191;
	6:ZSj0A6Ihf1ms19Blr7knZ8gt8XHvKVPPNBRqFO3Vvlyjjig+71LHamq64dOnfqBEO8hwPu7K/28Mm20VoHRADkh0l69JWCX+MDQh1lg/9mV1VNiHFrtAdJ0znB3V1OqgmVKgrbaWIC6b4oatzsfXkkKFLGQP7LPvpZMR+vfVNy9FKMlq66l28Ci68ScDK8P3YfHnU8u1C15a7f1PYqv4oTYhOL6yGFZdng8pvXbbKunMAIMv+4ujoKL2DET26FgGwdhBV3C+p5ESqJj+VZ9epiHvQKz7CkNAfPZUWklruvuTgv8JSNEIUlI0OO7FWTGuWsmhrMzj/HjtDKQ/ZQCFCMydspmuUxYg/B9a/0lKlv53FUDXbZdQp9xtCpZTSF3KZLU+6O3vuAXCVG9LwS9C6g8rQtpmuc3rJGojIlYJXG6uMUpKFfYctWeCvMkPFDcehPzpGKDw2kLSlMEQZV6dZg==;
	5:yRq1MLFTZl4IhpXUwSyVFvdZ5R1Z6cJDDla8SrLn2CF3T4i21VJW+EMyMn3evKgr7w6VqKLbOLOVJYTiSr7NtHKfNROlim44BsBo28Mca3BfWrrDD4nqzjZk9ihGNQNoSlCAZ1YAI9WwosoX4y9kgsg5/7krD4BQFf8yesYouGzSKylmp4poAymcdbS+H826SGQ8pWEQij0kQ5d1REEhvw==;
	7:1Lown/eWMzYW/3FXQ5f+vHiDDTbM42Uf/OxR4M8VYvnhTwmCavkxb9ux/TVfsgmGLRdIln6dAhbCSxz5s6+aHTQ9a9JEIucF0m0KXa6x7Go+2J9k0W3tOnTK1BAZpnIVz6/XdrAyJtuL3GxQc/MGBA==
x-incomingheadercount: 42
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0;
	RULEID:(2390118)(7020095)(20181119070)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031323274)(2017031324274)(2017031322404)(1601125500)(1603101475)(1701031045);
	SRVR:VE1EUR01HT191; 
x-ms-traffictypediagnostic: VE1EUR01HT191:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(4566010)(82015058);
	SRVR:VE1EUR01HT191; BCL:0; PCL:0; RULEID:; SRVR:VE1EUR01HT191; 
x-microsoft-antispam-message-info: iOWnxZO+SLpHA+CrmhbzOuk8UXSMzjJNYwKJ37I76I5qv8r7MYKXhFWiSfjpcDYm
Content-Type: multipart/alternative;
	boundary="_000_DB6PR10MB183228F27750132F9A6A3542A6690DB6PR10MB1832EURP_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: d4d70346-2c10-4f39-8c00-e767963926d9
X-MS-Exchange-CrossTenant-Network-Message-Id: dc64635c-2cb0-489e-0d0f-08d68dade0e1
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: d4d70346-2c10-4f39-8c00-e767963926d9
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Feb 2019 10:12:06.0847 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR01HT191
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: Fri, 08 Feb 2019 20:17:04 +0000
Subject: [bitcoin-dev] Implementing Confidential Transactions in extension
	blocks
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: Fri, 08 Feb 2019 10:12:11 -0000

--_000_DB6PR10MB183228F27750132F9A6A3542A6690DB6PR10MB1832EURP_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Greetings,

What do you think about implementing Confidential Transactions in extension=
 blocks? CT transactions go from extension block to extension block passing=
 through normal blocks. It looks the perfect solution:

- Soft fork: old nodes see CT transactions as "sendtoany" transactions
- Safe: if there is a software bug in CT it's impossible to create new coin=
s because the coins move from normal block to normal block as public transa=
ctions
- Legal: Exchanges can use public transactions so regulators can monitor th=
eir activity
- Capacity increase: the CT signature is stored in the extension block, so =
CT transactions increase the maximum number of transactions per block

Regards

--_000_DB6PR10MB183228F27750132F9A6A3542A6690DB6PR10MB1832EURP_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<span>Greetings,<br>
</span>
<div><br>
</div>
<div>What do you think about implementing Confidential Transactions in exte=
nsion blocks? CT transactions go from extension block to extension block pa=
ssing through normal blocks. It looks the perfect solution:<br>
</div>
<div><br>
</div>
<div>- Soft fork: old nodes see CT transactions as &quot;sendtoany&quot; tr=
ansactions<br>
</div>
<div>- Safe: if there is a software bug in CT it's impossible to create new=
 coins because the coins move from normal block to normal block as public t=
ransactions<br>
</div>
<div>- Legal: Exchanges can use public transactions so regulators can monit=
or their activity<br>
</div>
<div>- Capacity increase: the CT signature is stored in the extension block=
, so CT transactions increase the maximum number of transactions per block
<br>
</div>
<div><br>
</div>
<span>Regards</span><br>
</div>
</body>
</html>

--_000_DB6PR10MB183228F27750132F9A6A3542A6690DB6PR10MB1832EURP_--