As long as it is on by default, that is critical.

 +5%

Quote from: bytemaster on July 14, 2014, 12:33:08 PM
The blockchain supports this mode of operation, it is simply a matter of exposing it in the user interface.

very good, intergrate this mode in GUI client is better.

 +5%

The blockchain supports this mode of operation, it is simply a matter of exposing it in the user interface.

It sounds reasonable

good idea

Quote from: Webber on July 14, 2014, 09:53:18 AM
As we all know TITAN is real anonymous on blockchain,so no one can know receiver and sender of one trasaction by default.But I think set TITAN become optional is reasonable.For example,I make a deal with A ,and I want to open to pay 100XTS to A ,so A can't not to admit this deal because this transaction is open to everyone.
Moreover,sometimes we need to create a open account that every receive and send can open to everyone. I think TITAN is redundant for some  account that need to monitor by public .Like bts from AGS before 2.28.
So,if  receiver/sender anonymous or account anonymous optional function is very pratical.

+5%

As we all know TITAN is real anonymous on blockchain,so no one can know receiver and sender of one trasaction by default.But I think set TITAN become optional is reasonable.For example,I make a deal with A ,and I want to open to pay 100XTS to A ,so A can't not to admit this deal because this transaction is open to everyone.
Moreover,sometimes we need to create a open account that every receive and send can open to everyone. I think TITAN is redundant for some  account that need to monitor by public .Like bts from AGS before 2.28.
So,receiver/sender anonymous or account anonymous optional function is very pratical.