Privatization on @Dusk is not a Feature It is an Assumption of Protocol.
Privacy silently fails in many blockchain systems in the area of settlement. Although some execution may be partially secured, final settlement is frequently done on a publicly traded ledger, giving counterparty, move movement, and timing information the most sensitive lifecycle stage. This is not a small problem as far as regulated finance is concerned, it is a structural failure.
Settlement is not an exemption on @Dusk Foundation. Its design is subject to privacy and compliance assumptions as is the case in executing it. Change of ownership, transfers, and finality are made without pushing sensitive information to the public eye.
This is important since settlement is the place where legal and financial ramifications are solidified. Publication of data at this point of time exposes the business to heightened regulatory risk, competitive leakage, and operational complexity. Dusk evades this by making sure that privacy does not vanish when the transactions are made.
In the case of institutions, this eliminates the requirement of separate layers of private settlement or post-settlement obfuscation. It does not presuppose that privacy is added to Settlement on @Dusk , but presupposed. It is that architectural decisions that enable regulated assets to move on-chain without affecting confidentiality at the time when it is needed the most.
