I think the most misunderstood part of how DUST works is what happens when the connection between NIGHT and a DUST address gets broken. people assume it just stops generating. but the full picture is more precise than that — and the mechanics of what happens after the cut matters for anyone trying to understand how the resource actually behaves.
The association between a NIGHT address and a DUST address is called designation. once designated, DUST generates linearly — block by block — until the cap is reached. but this association isnt permanent. the whitepaper identifies three specific ways a NIGHT holder can sever it.
The first is transferring the associated NIGHT tokens to another address. when NIGHT moves away from the originating address, the link between that NIGHT and the DUST address breaks immediately. the NIGHT is gone from that address — so is the generation. the whitepaper is clear that the recipient of the transferred NIGHT will have to issue a new designation to resume DUST generation at a new address. the old DUST address is now disconnected.
The second is redesignation — explicitly pointing the DUST generation to a different DUST address. the NIGHT stays in the same wallet. only the destination changes. the old DUST address loses its association and stops receiving new generation. the new address starts accumulating from zero.
The third is undesignation — explicitly stopping DUST production entirely without redirecting it anywhere. the NIGHT stays put. the generation just stops.
In all three cases, what happens next to the DUST already sitting in the disconnected address is the same: it starts to decay. not immediately to zero — linearly, with each passing block, at the same rate it was being generated. the whitepaper describes this as a finite shelf life. the DUST that accumulated before the severance doesnt vanish instantly. it drains slowly.
This decay mechanic is also a double-spend prevention mechanism. from what i understand, it prevents a NIGHT holder from redesignating generation rapidly across multiple addresses to try and accumulate DUST beyond their cap. for a given amount of NIGHT, the aggregate DUST across all associated addresses can never exceed the cap — because for every unit generated in the new address, a unit decays in the old one. the cap is always enforced, regardless of how many times the designation changes.
The whitepaper also covers what happens when the NIGHT balance itself changes without severing the designation. if a NIGHT holder sends some — not all — of their NIGHT to another address, the DUST cap at the designated address decreases proportionally. the existing DUST balance then decays to meet the new lower cap. if all NIGHT is sent away, the DUST at that address decays entirely to zero.
There is no punitive element to any of this. the decay is just the system maintaining the invariant that DUST cant exist independently of the NIGHT generating it. once the source is gone, the resource winds down. the rate is predictable. the outcome is always the same.
Three ways to cut the connection. one outcome every time — the DUST that was there starts counting down.
If you held NIGHT and decided to transfer it tomorrow — would you know what happens to your DUST address before you do it?
#night #NIGHT $NIGHT @MidnightNetwork
