Reading Dusk’s Moonlight docs and I had to stop and re-read this part about note expiration.
So, you have these shielded notes. They're private. But if you don't "refresh" them within a specific window, the chain just... makes them public again.
Wait. So privacy isn't a permanent state? It's a recurring gas fee? You literally have to pay up every few months just to keep your history from getting dumped into the transparent pool.
That hit me wrong.
Imagine an institution gets hit with a compliance freeze for a couple months, or a dev has a hardware failure and goes offline.$DUSK They finally boot the node back up and find their entire historical transaction data is just... out there. Because a timer ran out.
I get the state-bloat argument. I do. They need to clean up old UTXOs or the chain gets fat and slow.
But the trade-off feels brutal. You basically can't rely on the cryptography alone—you need a 24/7 bot or a relayer running constantly just to maintain your default state of privacy. That's a massive assumption about how people actually behave.
Honestly, I'm torn. Is this a clever engineering hack to keep the chain lean, or is it a UX nightmare waiting to happen? It shifts the security model from "math is hard" to "hope your cron job doesn't fail."
@Dusk_Foundation #dusk #DUSK $DUSK
So, you have these shielded notes. They're private. But if you don't "refresh" them within a specific window, the chain just... makes them public again.
Wait. So privacy isn't a permanent state? It's a recurring gas fee? You literally have to pay up every few months just to keep your history from getting dumped into the transparent pool.
That hit me wrong.
Imagine an institution gets hit with a compliance freeze for a couple months, or a dev has a hardware failure and goes offline.$DUSK They finally boot the node back up and find their entire historical transaction data is just... out there. Because a timer ran out.
I get the state-bloat argument. I do. They need to clean up old UTXOs or the chain gets fat and slow.
But the trade-off feels brutal. You basically can't rely on the cryptography alone—you need a 24/7 bot or a relayer running constantly just to maintain your default state of privacy. That's a massive assumption about how people actually behave.
Honestly, I'm torn. Is this a clever engineering hack to keep the chain lean, or is it a UX nightmare waiting to happen? It shifts the security model from "math is hard" to "hope your cron job doesn't fail."
@Dusk_Foundation #dusk #DUSK $DUSK