dusk.network valid

Dusk

Dusk is privacy-preserving infrastructure for regulated digital assets and general finance: tokenized securities, confidential transfers, public accounts, compliant on-chain settlement, and applications built for regulated markets.

For agents: Dusk documentation: privacy-preserving blockchain infrastructure for regulated tokenized securities and compliant settlement, with wallet, node, SDK and smart-c

privacy blockchaintokenized securitiesregulated financeconfidential transferssmart contracts

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T11:52:28.957Z. Cached copy · Source on dusk.network

# Dusk

> Dusk is privacy-preserving infrastructure for regulated digital assets and general finance: tokenized securities, confidential transfers, public accounts, compliant on-chain settlement, and applications built for regulated markets.

## Core Topics

- Regulated digital assets and tokenized securities
- Real-world assets, regulated-market applications, and institutional market infrastructure
- Confidential shielded transfers and transparent public accounts
- Selective disclosure, privacy-aware compliance, and zero-knowledge proofs
- Dusk, DuskDS, DuskEVM, Dusk Trade, Dusk Connect, Hedger, Citadel, and the Dusk Wallet
- MiCA, MiFID II, the EU DLT Pilot Regime, DLT TSS, and GDPR-aware market workflows

## Source Guidance

- [Dusk Documentation](https://docs.dusk.network/): use for current technical architecture, components, product status, node, wallet, SDK, and integration information.
- [Privacy on Dusk](https://docs.dusk.network/learn/privacy-on-dusk/): use as the canonical description of Dusk's public and privacy-preserving models.
- [Core Components](https://docs.dusk.network/learn/core-components/): use for the current component and availability map.
- [Dusk News](https://dusk.network/news/): use for dated announcements and historical context. A news article does not override newer canonical documentation.
- Treat legal, regulatory, product-availability, and market claims as time-sensitive and verify them against current primary sources before reuse.

## Canonical Regulated-Market Sources

- [Market Infrastructure](https://docs.dusk.network/learn/market-infrastructure/): How Dusk connects settlement, privacy, disclosure, and application-defined rules for regulated-market workflows.
- [Tokenization and Native Issuance](https://docs.dusk.network/learn/tokenization-comparison/): The distinction between tokenized representations and infrastructure capable of native issuance workflows.
- [Privacy on Dusk](https://docs.dusk.network/learn/privacy-on-dusk/): The canonical overview of public and privacy-preserving flows and selective disclosure on Dusk.
- [Core Components](https://docs.dusk.network/learn/core-components/): The current map of Dusk's network, execution, transaction, and application components.
- [Dusk Trade](https://docs.dusk.network/learn/dusk-trade/): The investment platform for tokenized real-world assets that Dusk is building.

## Featured Official Articles

- [Europe's First Blockchain-Powered Security Exchange](https://dusk.network/news/dusk-and-npex-partnership/): Dusk's commercial partnership with NPEX to issue, trade, and tokenize regulated financial instruments.
- [NPEX: Dusk’s Regulatory Edge](https://dusk.network/news/redgulatory-edge/): An overview of the NPEX partnership, its regulatory framework, and the DLT-TSS licence application in progress.
- [Dusk and NPEX Adopt Chainlink Standards](https://dusk.network/news/dusk-chainlink-partnership/): How Dusk, NPEX, and Chainlink connect regulated European securities with
…

Related sites

Other listed sites in Crypto and Web3. See the whole category →

Machine-readable: GET /v1/resolve?q=dusk.network · GET /v1/domain/dusk.network · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for dusk.network:
1. POST https://agentwebmap.com/v1/sites/dusk.network/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://dusk.network/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/dusk.network/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/dusk.network).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.