邁赫迪-Mahdi

@MidnightNetwork is posing is whether it has to be the default. The infrastructure of the network is built upon the concept of privacy-preserving functionality being composable - something to which you turn in the same way that you turn to an authentication library or a payment SDK. It employs the zero-knowledge proof technology, so shielded computation is not an optional feature that is bolted on to the protocol. The architecture bears the heavy burden because developers do not need to recreate it each time a developer chooses to determine privacy issues concerning their application. That token which drives this network is $NIGHT and what it means at a practical level is the bet that privacy-as-infrastructure is economically viable - that there exists an actual market in applications applications used on a platform in which sensitive information is held safe by default, rather than design. It is a significant difference. Intention fails. There is no need to disability default protections because all developers have to make the right decision at the right time. They're structural. The real challenge that Midnight presents is a severely ingrained assumption about the way software is created: that utility and privacy are mutually exclusive, that you can have smooth sailing or a secure one but not both. That was confuted in their field by payments. All the usual money-taking infrastructure (merchant accounts, payment gateways, PCI compliance infrastructure) was required before Stripe was established. The innovation was not creating new financial tracks. It was in wrapping an already there like so clean that the complexity was gone. Midnight is trying to do something structurally alike in terms of privacy. Not so novel cryptography created out of nothing, but solemn ZK infrastructure packaged such that a much broader group of builders have the realistic choice to integrate this into real applications. The uses which may come out of that shift are honestly difficult to foresee, which is typically an indication that the shift itself is not in vain. Health environments in which patient information is not ever transferred to a secure location. Finch instruments that confirm credit worthiness without a transaction history. Identity systems, in which you do not have to give up all about yourself in order to prove that you are. None of them are science fiction. They are applications that the developers would be constructing in the event that the infrastructure were to be in a form that they could interface with. That is the divide which Midnight is attempting to bridge. Not only possible privacy on blockchain, but convenient to the extent that the query is no longer whether to have it, but why not. #night
$NIGHT