What continued to bother me was that Midnight has its covert transaction that is not the secret deal.
It is the time the privacy is coming to demand that you be a local operator. The wallet flow still relies upon a proof server operating within the background and the existing configuration is based upon Docker and a beta Midnight wallet path within Lace. Even the development assistance is now Linux and Mac, not Windows. That is not a tiny setup note. That is a workflow tax that is on the brink of adoption.
That is the part people skip.
You do not simply open the app and sign. You run the proof server alive, you have the wallet path turned on, the environment set and you wish that the quiet machine under your click is still in good health so that the proof will be created locally. This angle is more important to me in that midnight is facing the ugly side that most privacy systems attempt to conceal: somebody has to shoulder the operational burden, before the story of the easy UX becomes real.
And it is there that $NIGHT mechanically belongs. NIGHT creates DUST, DUST creates execution, but the ability to use it is only possible when the proving path is really running when the user requires it. A dead local proving path cannot be saved by the use of a clean token design.
The question I continue to follow is straightforward: is it possible that MidnightNetwork can make this background operator burden fade away before the general users can ever notice it?
Since there is no privacy like the price of the silence of the local prover, the actual point of contact is not secrecy.
It is operational tolerance.
$NIGHT #night @MidnightNetwork
It is the time the privacy is coming to demand that you be a local operator. The wallet flow still relies upon a proof server operating within the background and the existing configuration is based upon Docker and a beta Midnight wallet path within Lace. Even the development assistance is now Linux and Mac, not Windows. That is not a tiny setup note. That is a workflow tax that is on the brink of adoption.
That is the part people skip.
You do not simply open the app and sign. You run the proof server alive, you have the wallet path turned on, the environment set and you wish that the quiet machine under your click is still in good health so that the proof will be created locally. This angle is more important to me in that midnight is facing the ugly side that most privacy systems attempt to conceal: somebody has to shoulder the operational burden, before the story of the easy UX becomes real.
And it is there that $NIGHT mechanically belongs. NIGHT creates DUST, DUST creates execution, but the ability to use it is only possible when the proving path is really running when the user requires it. A dead local proving path cannot be saved by the use of a clean token design.
The question I continue to follow is straightforward: is it possible that MidnightNetwork can make this background operator burden fade away before the general users can ever notice it?
Since there is no privacy like the price of the silence of the local prover, the actual point of contact is not secrecy.
It is operational tolerance.
$NIGHT #night @MidnightNetwork