Re: [bitcoin-dev] Implementing Confidential Transactions in extension blocks

2019-02-12 Thread Trey Del Bonis via bitcoin-dev
>Under this point-of-view, then, extension block is "not" soft fork. >It is "evil" soft fork since older nodes are forced to upgrade as their >intended functionality becomes impossible. >In this point-of-view, it is no better than a hard fork, which at least is >very noisy about how older

Re: [bitcoin-dev] Implementing Confidential Transactions in extension blocks

2019-02-12 Thread Kenshiro [] via bitcoin-dev
Good morning ZmnSCPxj, Thank you for your answer. There is a position that fullnodes must be able to get a view of the UTXO set, and extension blocks (which are invisible to pre-extension-block fullnodes) means that fullnodes no longer have an accurate view of the UTXO set. I think old nodes

Re: [bitcoin-dev] Implementing Confidential Transactions in extension blocks

2019-02-12 Thread ZmnSCPxj via bitcoin-dev
Good morning Kenshiro, > - Soft fork: old nodes see CT transactions as "sendtoany" transactions There is a position that fullnodes must be able to get a view of the UTXO set, and extension blocks (which are invisible to pre-extension-block fullnodes) means that fullnodes no longer have an

Re: [bitcoin-dev] Safer NOINPUT with output tagging

2019-02-12 Thread Anthony Towns via bitcoin-dev
On Sun, Feb 10, 2019 at 12:48:40AM +0800, Johnson Lau wrote: > In a 3 parties channel, let’s say the balance for A, B, C is 2, 3, 6BTC > respectively, there are few ways they could make the settlement tx. The way I look at this is: * you can have a "channel factory" of 3 or more members