Dr Roosh

I went looking for how Citadel actually handles a revoked credential. Turns out the answer isn't "the chain checks it." Dusk Network's Citadel protocol $DUSK #dusk lets a user prove a session is cryptographically valid — that a real License Provider signed a real license — but per the docs, that proof does not decide service policy.
That call sits with the Service Provider. Per @Duskfoundation's own documentation, the SP decides which License Providers it trusts, which attributes it accepts, whether a session is expired or revoked, and whether the session cookie can be reused. None of that is written into the on-chain verification itself.
What changed for me was realizing "privacy-preserving KYC" here doesn't mean the chain enforces compliance. Personal attributes are never written to the blockchain — that part's explicit in the docs. But expiry, revocation, and trust in the issuer are policy decisions each Service Provider makes independently, off-chain, with nothing on-chain forcing consistency between them.
@Dusk

Wait — the thing "protecting" your DuskEVM trade from bots right now isn't even the fancy tech.
Everyone talks about Hedger, DuskEVM's ($DUSK #dusk @DuskFoundation) privacy engine — homomorphic encryption plus ZK proofs, encrypted balances, real cryptography. That's not what's stopping front-running today though.
I checked the docs. DuskEVM currently runs sequencer-only. No public mempool. One sequencer, nothing for bots to watch and jump ahead of. That's the actual mechanism.
So there are two different "privacy" stories stacked on top of each other, and it's easy to credit the wrong one. Hedger is real cryptographic privacy, audit-ready by design. Front-running protection is something else — a side effect of having one sequencer with nothing exposed.
Here's what I haven't found yet: any doc or roadmap saying whether DuskEVM's sequencer stays single or opens up over time. If it ever becomes multi-party or public, this specific protection would need something to replace it. That's not confirmed anywhere I've seen — just a question the current setup raises.
Curious if anyone's tracked DuskEVM's actual sequencer roadmap. Genuinely don't know the answer here.
@Dusk

Spent the afternoon poking around Dusk's repos instead of just reading the pitch deck. #Dusk $DUSK @DuskFoundation — "privacy on a public chain" is the whole TradFi hook, so I wanted to see what's actually moving, not what's being said.
Here's the thing that stuck: duskevm-genesis, the repo holding the genesis block and rollup config, had commits land Aug 8 and Aug 10, 2026. Not RWA settlement code. Not a securities contract. Genesis and rollup plumbing — the boring, load-bearing stuff nobody screenshots.
Meanwhile DUSK's most active pair, DUSK/USDT on Binance, was doing about $117k in 24h volume when I checked, against roughly $3.07M total across 51 markets (CoinGecko). For a project whose entire thesis is "institutions will finally transact on a public chain," that's a thin signal.
Made me reconsider my own framing going in — I assumed compliant privacy meant invisible institutional flow humming in the background. What I found instead was infra still being wired, quietly, while the market cap sits under $50M.
So which comes first here — the institutions Dusk keeps promising, or the plumbing finally catching up to the pitch?
@Dusk

Reading the Phoenix circuit constraints stopped me. On Dusk $DUSK #dusk @Duskfoundation the Transfer Contract never looks at the actual note values or which Merkle leaf is spent.
It only checks a PLONK proof that the private inputs satisfy five conditions: the note hash opens against a recent Merkle root of notes, the prover knows the note secret key, the nullifier equals Poseidon(npk′ ‖ position), the output commitments open correctly, and the sum of input values equals outputs plus fee plus any deposit.
Nullifiers themselves are published so the network can reject reuse. Because each is derived from the hidden note key and position, no observer can map a nullifier back to a specific leaf. Validity lives entirely inside circuit satisfaction; the contents never appear on the ledger.
What changed for me was realizing double-spend protection and balance integrity both sit inside the proof rather than any visible state change.
Next check: whether every accepted Phoenix transaction’s published nullifiers stay unique in the on-chain nullifier set after finality.
@Dusk