#dusk $DUSK @Dusk dev docs instead of the marketing page, and one line stopped me mid scroll: DuskEVM currently has no public mempool sequencer only. the grant fund page talks builder first, EVM compatible, familiar tooling. Fine. But then you hit that sequencer note and it's a different picture.
the contrast that actually stuck. Native L1 shows 210M+ DUSK staked, ~10s deterministic finality, genuinely decentralized consensus running today. DuskEVM the layer grants are pushing builders towardis still testnet, still sequencer controlled, no open mempool yet. So the part of Dusk that's live and permissionless isn't the part devs are being funded to build on. The part devs get funded for is the part still centralized by design, for now.
Not a red flag, just… a sequencing thing. Grants front run the infra, which is normal I guess, but it means build on Dusk today quietly means build on the part that isn't decentralized yet. Had to double check I wasn't misreading it nope, it's stated plainly in their own docs... how many builders actually read that line before applying, or if the pitch just says EVM compatible and stops there.
$ONG $EDEN
the contrast that actually stuck. Native L1 shows 210M+ DUSK staked, ~10s deterministic finality, genuinely decentralized consensus running today. DuskEVM the layer grants are pushing builders towardis still testnet, still sequencer controlled, no open mempool yet. So the part of Dusk that's live and permissionless isn't the part devs are being funded to build on. The part devs get funded for is the part still centralized by design, for now.
Not a red flag, just… a sequencing thing. Grants front run the infra, which is normal I guess, but it means build on Dusk today quietly means build on the part that isn't decentralized yet. Had to double check I wasn't misreading it nope, it's stated plainly in their own docs... how many builders actually read that line before applying, or if the pitch just says EVM compatible and stops there.
$ONG $EDEN
