@Dusk_Foundation
I have been reading about Dusk Network lately and one thing I wanted to understand better was Moonlight.
Moonlight is Dusk’s transparent account-based transaction model. The easiest way I understand it is that it works more like the account systems we already know from many blockchains. Each account has a balance and transactions update that balance when funds are sent or received.
What I find interesting is that Moonlight gives Dusk a clear and familiar way to handle public transactions. You can see the account activity and understand how funds move without needing to think about a hidden balance model.
For me this matters because Dusk is not built around privacy alone. It is trying to support different needs within the same network. Some activity may need transparency while other use cases can benefit from stronger privacy.
Moonlight is basically the transparent side of that design. Dusk also has Phoenix for shielded transactions. So instead of forcing every transaction into one model Dusk provides different options depending on what the application needs.
The more I read about it the more this balance between transparency and privacy makes sense to me.
#dusk $DUSK
I have been reading about Dusk Network lately and one thing I wanted to understand better was Moonlight.
Moonlight is Dusk’s transparent account-based transaction model. The easiest way I understand it is that it works more like the account systems we already know from many blockchains. Each account has a balance and transactions update that balance when funds are sent or received.
What I find interesting is that Moonlight gives Dusk a clear and familiar way to handle public transactions. You can see the account activity and understand how funds move without needing to think about a hidden balance model.
For me this matters because Dusk is not built around privacy alone. It is trying to support different needs within the same network. Some activity may need transparency while other use cases can benefit from stronger privacy.
Moonlight is basically the transparent side of that design. Dusk also has Phoenix for shielded transactions. So instead of forcing every transaction into one model Dusk provides different options depending on what the application needs.
The more I read about it the more this balance between transparency and privacy makes sense to me.
#dusk $DUSK