Implementing Confidential Transactions in extension blocks

There was a proposal on bitcoin-dev to implement Confidential Transactions in extension blocks.

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 coins because the coins move from normal block to normal block as public transactions

  • Legal: Exchanges can use public transactions so regulators can monitor their activity

  • Capacity increase: the CT signature is stored in the extension block, so CT transactions increase the maximum number of transactions per block

ZmnSCPxj agreed that capacity increase can boost network capacity for all full nodes, he thinks extension blocks are not real soft forks but rather “evil” soft forks as older nodes have to upgrade in order to function optimally, which makes extension blocks worse than soft forks.

For safety, he believes it can be achieved with non-extension block approach (hard forks) by implementing a globally-verified publicly-visible counter of the total amount in all confidential transaction outputs.

Follow the discussion here

Resources

Support us and the authors of this article by donating to the following address:

3Jv15g4G5LDnBJPDh1e2ja8NPnADzMxhVh

Comments powered by Talkyard.