What continued to annoy me was that Midnight is not paying usage in the concealed friction the friction is going through.

It is that which befalls power the instant you shift the supporting NIGHT.

That is the part people skip.

The DUST of Midnight is attached to a given NIGHT UTXO. It develops with time and that NIGHT is there. However, after that support NIGHT usage, the associated DUST begins to go to waste and whenever only a portion of the NIGHT is transferred, the transformation will be a new NIGHT UTXO that will initiate new DUST production with zero.

That transforms an ordinary treasury process into a workflow issue.

Rebalance excessively, switch funds or divide reserves in an inappropriate time, and the application will silently transition the state of being ready to use sponsorship capabilities to being waiting to capacity to restore. It was midnight, but there I did not have the same click. It is not simply that it is difficult to make private execution. It is maintaining the fuel layer stationary as the capital layer continues to move.

It is also there that the symbolism of $NIGHT ceases. NIGHT does not stand adjacently to the system. It is higher than DUST and DUST is actually what the transactions consume. When the NIGHT side is churned, then the one in use can go bad easily.

The only thing I continue to observe is this: Does @MidnightNetwork have the ability to make it seem like a disciplined infrastructure, rather than tattered, shaky concealment of the treasury?

Since, in Midnight, any attempt to move the reserve will wound the battery quietly. #night