dusk-primary-sources-2026-05-12

Dusk primary sources

Collected: 2026-05-12 UTC

Primary sources reviewed

• https://dusk.network/
  • Official homepage
  • Used to anchor Dusk’s public positioning as infrastructure for regulated digital assets and finance
• https://docs.dusk.network/
  • Official docs portal
  • Used to confirm the live documentation surface and project vocabulary
• https://github.com/dusk-network/docs
  • Official docs repository
  • Used because the web docs are bot-protected on several pages; the repo provided direct access to the source markdown for the current docs
• https://raw.githubusercontent.com/dusk-network/docs/main/public/llms-full.txt
  • Docs corpus map
  • Used as the fastest overview of DuskDS, DuskEVM, DuskVM, Citadel, Dusk Connect, and Dusk Trade as distinct stack layers
• https://github.com/dusk-network/whitepaper
  • Public whitepaper repository
  • Reviewed mainly to confirm that the older whitepaper repo exists, though the current docs were more operationally useful than the repo contents in this pass
• https://docs.dusk.network/learn/market-infrastructure/
  • Market-infrastructure framing
  • Used to anchor Dusk’s thesis around participant eligibility, privacy, settlement, and disclosure coordination
• https://docs.dusk.network/learn/tokenization-comparison/
  • Native-issuance framing
  • Used to preserve Dusk’s explicit distinction between digitization, tokenization, and native issuance
• https://docs.dusk.network/developer/digital-identity/protocol/
  • Citadel identity protocol page
  • Used to inspect the license-provider / user / service-provider split and the stealth-address plus ZK-proof identity flow
• https://docs.dusk.network/learn/deep-dive/duskds-tx-models/
  • DuskDS transaction-model deep dive
  • Used to inspect the Phoenix versus Moonlight split and how Dusk frames selective disclosure at the settlement layer
• https://docs.dusk.network/operator/provisioner/
  • Provisioner operator docs
  • Used to confirm stake-gated consensus participation and current operator posture
• https://docs.dusk.network/learn/deep-dive/consensus/
  • Succinct Attestation consensus docs
  • Used to inspect deterministic sortition, committee credits, proposal/validation/ratification flow, rolling finality, and emergency modes

Key takeaways from primary sources

• Dusk is analytically strongest as a layered regulated-finance stack rather than as a generic smart-contract chain. The docs repeatedly separate settlement, execution, identity, wallet connection, and market workflows.
• The native-issuance page is especially important because it shows Dusk trying to shift the conversation from token wrappers toward making the ledger itself the lifecycle anchor for regulated assets.
• The market-infrastructure docs make the protocol’s target use case unusually explicit: participant permissions, wallet binding, transfer rules, privacy, servicing, reporting, and settlement are meant to coordinate on the same substrate.
• Phoenix and Moonlight are valuable lower-layer comparison points because Dusk treats transparency and privacy as native transaction-model choices instead of assuming one universal mode.
• Citadel adds a distinct identity-control surface based on license issuance, stealth-address delivery, and zero-knowledge proof of license possession, which is richer than a simple allowlist or KYC flag.
• Succinct Attestation matters because Dusk’s regulated-market story still depends on a specific consensus and operator design: stake-gated provisioners, deterministic sortition, committee voting, rolling finality, and emergency-mode powers.
• Dusk therefore belongs in the corpus as a useful “thick stack” comparison case against standards like ERC-3643 and middleware layers like Tokeny or Chainlink ACE.

Why this entry belongs in the corpus

• It gives the compliance/tokenization cluster a protocol-stack comparison point rather than only standards and middleware vendors.
• It helps separate native settlement, privacy/account models, identity/access controls, and product-layer market workflows.
• It is a good anchor for later comparisons among ERC-3643, Tokeny, ONCHAINID, Chainlink ACE, and other regulated-asset infrastructure projects.