What stood out to me in Midnight was that Preview can treat the same click as three different prep jobs.

Before anything is submitted, the wallet’s balancing step can route the flow three ways: prove it, rebalance then prove it, or just send it. Same button. Same intent. Different hidden workload. The rebalance branch is the revealing part. If the action is not already in a state the wallet can prove cleanly with spendable DUST ready, Preview inserts extra preparation before the user ever sees a result.

That creates a real UX burden. One submit can feel instant. The next can pause for no visible reason because the wallet first had to prepare DUST and only then move into the prove path. From the user side, that does not feel like good design. It feels like the flow changed its behavior without warning.

That is what made Midnight feel serious to me. The hard problem is not only private execution. It is hiding three prep realities inside one stable action.

That is also where $NIGHT stops feeling decorative. NIGHT sits upstream, DUST is what execution actually spends, and the wallet has to keep enough DUST available no matter which branch Preview selects. If that readiness shifts from one action to the next, identical clicks can still feel uneven even when the fee model looks smooth on paper.

What I’m still watching is whether Midnight can hide that branching well enough that users never notice when one action was ready immediately and another had to be rebalanced first. #night $NIGHT @MidnightNetwork