Dusk $DUSK has a design choice I keep coming back to: it runs two transaction models side by side instead of picking one.#Dusk @Dusk Moonlight is the transparent, account-based layer balances and history are public, easy to audit, basically what you'd expect from a normal chain. Phoenix (or whatever they're calling the shielded rail these days) does the confidential side, so a transfer can be shielded or plain depending on what the app actually needs. Most privacy chains I've looked at make you commit to one model for the whole network, then bolt on workarounds when institutions need auditability. Dusk instead lets the choice happen per transaction, which sounds small until you think about what it means for something like Dusk Trade — a regulated venue could keep settlement private while still exposing whatever a regulator needs to see, without forking logic or running a second chain. I haven't found numbers yet on how often Moonlight vs the shielded path actually gets used on mainnet, or whether most integrations default to one over the other. Anyone seen real usage splits