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
Content-Type: multipart/alternative;
	boundary="_000_DB6PR10MB183228F27750132F9A6A3542A6690DB6PR10MB1832EURP_"
MIME-Version: 1.0
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_--