Many people think that the hardest part on the chain is how to protect privacy.
In reality, the difficulty is not confidentiality at all, but how to confirm things clearly without exposing people completely.
This distinction is significant.
You go to投一个白名单, the project party doesn't want to know what all your wallets have done in the past three years, it just wants to confirm whether you are an old user, active enough, and look like a batch number.
You go to do a background check, and the company doesn't necessarily want to uncover all your collaboration experiences, it just wants to know if you have done this kind of thing and whether the results are reliable.
When you apply for a claim, what the platform really needs to confirm is whether you meet the conditions, not to take away all your private materials.
But the most common practices on-chain are very crude.
If you want to verify, first get the address to the bottom.
If you want to filter qualifications, first clean up the trajectory.
In the end, the things were verified, and people were more or less seen through.
@MidnightNetwork What this line is really doing is breaking this step apart.
What needs to be handed over is the result.
It's not the entire process.
Whether you meet the standards can be proven.
Whether you are an old user can be proven.
Whether you meet a certain condition can also be proven.
But having these proofs established does not mean you have to hand over the entire underlying records.
This is what it has been talking about: selective disclosure.
Many people see these four words and feel it's still the old rhetoric of privacy. In fact, it's not. It’s more like changing a very rough verification method. In the past, to prove something, you had to lay everything bare. Now you only take out that small piece that must be proven, keeping the rest to yourself.
This feeling changes, and many scenarios become smoother.
The whitelist will no longer turn into a box opening.
Background checks will no longer turn into skin peeling.
On-chain identity no longer equals public records.
Going further down, $NIGHT and this set of DUST is not just for show.
$NIGHT is placed at the capital layer, and DUST is responsible for transactions and contract execution. The system needs to run verification, auditing, and qualification updates for a long time, so costs cannot drift randomly. Separating these two layers makes it easier to create real services, rather than one-time demonstrations.
So @MidnightNetwork what is truly valuable is not how deep the data is hidden.
Instead, it starts to refine the roughest step on-chain in a way more acceptable to people.
If you really want to bring Web3 into more real scenarios, someone has to do this step sooner or later.
Looking at it now, Midnight is at least seriously working on this.
@MidnightNetwork $NIGHT #night
