diff --git a/src/assets/modular_vs_monolithic.png b/src/assets/modular_vs_monolithic.png new file mode 100644 index 00000000..ce6335ad Binary files /dev/null and b/src/assets/modular_vs_monolithic.png differ diff --git a/src/content/docs/developer/integrations/exchanges.md b/src/content/docs/developer/integrations/exchanges.md index f1fcd96f..f3a180ef 100644 --- a/src/content/docs/developer/integrations/exchanges.md +++ b/src/content/docs/developer/integrations/exchanges.md @@ -111,15 +111,15 @@ Dusk is **fully compliant** with key global regulatory frameworks, providing rob - TFR (Transfer of Funds Regulation) Dusk supports two distinct transaction models, which users can navigate between in a transparent way: -- [Phoenix](/learn/tx-models#phoenix) enables confidential transactions while maintaining regulatory compliance -- [Moonlight](/learn/tx-models#moonlight) is a completely transparent and auditable model. +- [Phoenix](/learn/deep-dive/transaction_models/tx-models#phoenix) enables confidential transactions while maintaining regulatory compliance +- [Moonlight](/learn/deep-dive/transaction_models/tx-models#moonlight) is a completely transparent and auditable model. Unlike traditional privacy coins, Dusk doesn't aim for full anonymity, but instead provides both privacy and regulatory compliance. ### Compliance in Moonlight (public) -[Moonlight](/learn/tx-models#moonlight) is designed specifically for full transaction transparency, making it ideal for integration with exchanges and ensuring that: +[Moonlight](/learn/deep-dive/transaction_models/tx-models#moonlight) is designed specifically for full transaction transparency, making it ideal for integration with exchanges and ensuring that: - **CASPs** can easily meet compliance obligations under **AMLD5**, **MiCA**, and **TFR**. - There is full support for **KYC**, transaction monitoring, and reporting requirements without any legal or technical barriers. diff --git a/src/content/docs/developer/integrations/historical_events.md b/src/content/docs/developer/integrations/historical_events.md index 35a6f867..91c68f9e 100644 --- a/src/content/docs/developer/integrations/historical_events.md +++ b/src/content/docs/developer/integrations/historical_events.md @@ -14,7 +14,7 @@ The GraphQL API provides access to finalized historical blockchain transaction-e The **moonlightHistory** endpoint allows for advanced filtering, enabling queries based on sender, receiver, block range, and pagination.**fullMoonlightHistory** retrieves all public `DUSK` value transfers for a given address, without additional filtering options. ::: -You can also checkout the [transaction models](/learn/tx-models#transaction-models-on-dusk) page, to get familiar with the terminology of `moonlight` & `phoenix`. +You can also checkout the [transaction models](/learn/deep-dive/transaction_models/tx-models#transaction-models-on-dusk) page, to get familiar with the terminology of `moonlight` & `phoenix`. Refer to [GraphQL queries](/developer/integrations/http-api/#graphql-queries) for additional information on the GraphQL endpoint. diff --git a/src/content/docs/developer/smart-contract/core-concepts.md b/src/content/docs/developer/smart-contract/core-concepts.md index d9f0c703..e01443e5 100644 --- a/src/content/docs/developer/smart-contract/core-concepts.md +++ b/src/content/docs/developer/smart-contract/core-concepts.md @@ -44,7 +44,7 @@ Because the **core** crate lacks heap memory allocations, we can explicitly also ### Usage of panic & reverting state -While you can have Result types in your smart contracts and handle them in multiple function calls, in the end you may want to abort execution. For example if a specific requirement is not satisfied you can always make use of directives that lead to panic (e.g., `.expect()` or `panic!()`). This is equivalent to `require()` in Solidity. It will abort the smart contract execution and let the transaction [fail](/learn/tx-fees#unsuccessful-transactions). This will also **revert** the state, making no changes to it. +While you can have Result types in your smart contracts and handle them in multiple function calls, in the end you may want to abort execution. For example if a specific requirement is not satisfied you can always make use of directives that lead to panic (e.g., `.expect()` or `panic!()`). This is equivalent to `require()` in Solidity. It will abort the smart contract execution and let the transaction [fail](/learn/deep-dive/tx-fees#unsuccessful-transactions). This will also **revert** the state, making no changes to it. ## UTXO & Account-model @@ -58,7 +58,7 @@ Therefore developers need to figure out how to represent users. In Dusk, an "address" is defined by the developer within the contract's logic. This approach gives developers more control over the privacy and compliance features of their applications but also increases their responsibility to securely identify and authenticate users and transactions. -The `msg.sender` is not "abstracted" away on dusk. A way to mimic that behavior is by explicitly taking the address as function argument and a signature that signed all other function arguments (including the address). Then verifying this in the function. Examples of such usage can be found in the [transparent token standard](/learn/token-standards#dusks-token-standards), the [Moonlight transaction model](/learn/deep-dive/transaction_models/moonlight) and [Zedger](/learn/deep-dive/transaction_models/zedger). +The `msg.sender` is not "abstracted" away on dusk. A way to mimic that behavior is by explicitly taking the address as function argument and a signature that signed all other function arguments (including the address). Then verifying this in the function. Examples of such usage can be found in the [transparent token standard](/learn/deep-dive/token-standards#dusks-token-standards), the [Moonlight transaction model](/learn/deep-dive/transaction_models/moonlight) and [Zedger](/learn/deep-dive/transaction_models/zedger). ## Methods diff --git a/src/content/docs/learn/block-explorer.md b/src/content/docs/learn/block-explorer.md index 29f9cf39..023d17ae 100644 --- a/src/content/docs/learn/block-explorer.md +++ b/src/content/docs/learn/block-explorer.md @@ -5,8 +5,8 @@ description: Use the Dusk’s block explorer for looking at transaction details. Transactions can be viewed on the Dusk Block Explorer, along with statistics and information about the network. -Dusk is a privacy-preserving blockchain. Privacy-preserving [Phoenix](/learn/tx-models#phoenix) transactions do not expose the sender, receiver and amount transferred to anyone other than the involved parties (sender, receiver, and users with the view key). +Dusk is a privacy-preserving blockchain. Privacy-preserving [Phoenix](/learn/deep-dive/transaction_models/tx-models#phoenix) transactions do not expose the sender, receiver and amount transferred to anyone other than the involved parties (sender, receiver, and users with the view key). -For public [Moonlight](/learn/tx-models#moonlight) transactions or other types of chain interactions, the visibility of transaction details depends on the contract implementation and whether developers use privacy technology like zero-knowledge proofs. +For public [Moonlight](/learn/deep-dive/transaction_models/tx-models#moonlight) transactions or other types of chain interactions, the visibility of transaction details depends on the contract implementation and whether developers use privacy technology like zero-knowledge proofs. The block explorer can be used to view the type of transactions submitted, as well as the payload, transaction fee and gas used. diff --git a/src/content/docs/learn/core-components.md b/src/content/docs/learn/core-components.md index 33cb7d04..dfdcbf95 100644 --- a/src/content/docs/learn/core-components.md +++ b/src/content/docs/learn/core-components.md @@ -3,17 +3,25 @@ title: Core Components description: Introduction to the core components that power Dusk. --- -Dusk is built on a foundation of custom-developed tools and components, specifically designed to meet [institutional standards](/learn/tokenization-comparison#meeting-institutional-standards) for privacy, regulatory compliance, and secure interactions with regulated assets. These components enable Dusk to support not only the tokenization of real-world assets (RWAs) but also [native issuance](/learn/tokenization-comparison#native-issuance). +Dusk is built with a modular architecture, leveraging the tools and components, specifically designed to meet [institutional standards](/learn/tokenization-comparison#meeting-institutional-standards) for privacy, regulatory compliance, and secure interactions with regulated assets. These components enable Dusk to support not only the tokenization of real-world assets (RWAs) but also [native issuance](/learn/tokenization-comparison#native-issuance). What sets Dusk apart from other blockchains is its tailor-made architecture, driven by continuous cryptographic research to ensure compliance, privacy, and robust network security, providing a reliable foundation to be a **Decentralized Market Infrastructure** (DeMI). -## Rusk +## DuskDS + +DuskDS is the settlement, consensus, and data availability layer at the foundation of the Dusk architecture. It provides finality, security, and native bridging for all execution environments built on top, including DuskEVM and DuskVM. By modularizing the protocol stack, DuskDS is built to meet institutional demands for compliance, privacy, and performance. + +DuskDS includes Rusk (the node implementation) which is powered by Succinct Attestation (PoS-based consensus), Kadcast (P2P networking layer), and the Transfer and Stake Genesis contracts. Together, these elements form a secure, compliant, and composable environment for regulated financial applications + +Through its dual transaction models (Phoenix and Moonlight), it provides a secure settlement and data availability layer for compliant execution environments (such as DuskEVM and DuskVM). For seamless, trustless transfers between execution layers, DuskDS exposes a native bridge. + +### Rusk Rusk can be thought of as the technological heart of the Dusk protocol, similar to the motherboard of a computer. It is the reference implementation of the Dusk protocol in Rust. Rusk serves multiple critical functions. It includes foundational elements like the genesis contracts, such as the transfer and stake contract. It integrates key components such as Plonk, Kadcast and Dusk VM, and supplies host functions to smart contract developers through Dusk Core. Beyond that, Rusk houses the consensus mechanism and node software, maintaining the chain state, database and network. It also provides crucial external APIs through the Rusk Universal Event System (RUES). Deep dive into Rusk implementation -## Consensus Layer: Succinct Attestation +### Succinct Attestation [Succinct Attestation](/learn/deep-dive/succinct-attestation) (SA) is the unique **proof-of-stake** (PoS) consensus algorithm at the core of Dusk. It uses a committee-based approach where stakers, called provisioners, participate in generating, validating and ratifying blocks. Provisioners are randomly selected based on their stake. @@ -26,15 +34,7 @@ Blocks are added to the blockchain if they receive enough votes. The Determinist [Deep dive into Succinct Attestation](/learn/deep-dive/succinct-attestation) -## Execution Layer: Dusk VM - -[Dusk VM](/learn/deep-dive/dusk-vm) is a highly optimized virtual machine 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 +### Network Layer: Kadcast Kadcast 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. @@ -42,10 +42,6 @@ Kadcast is highly resilient to network changes and failures. It dynamically upda Deep dive into Kadcast implementation -## Application layer - -At the application layer of our network, we’ve introduced innovative protocols and a dual transaction model designed to seamlessly meet the needs of financial institutions looking to tokenize Real-World Assets. Let’s take a closer look at the Genesis contracts, Citadel and Zedger/XSC. - ### 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. @@ -56,7 +52,7 @@ The [Transfer Contract](/learn/deep-dive/transaction_models/transactions) is res ### Phoenix & Moonlight -[Phoenix](/learn/tx-models#phoenix) & [Moonlight](/learn/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. +[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) @@ -64,62 +60,48 @@ The [Transfer Contract](/learn/deep-dive/transaction_models/transactions) is res ### Transactions on Dusk -Transactions in Dusk are managed by the Transfer Contract. The Transfer Contract oversees the handling of both transparent and obfuscated transactions within the network. +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/tx-models#utxos) and [account-based](/learn/tx-models#account-model) model through [Phoenix](/learn/tx-models#phoenix) and [Moonlight](/learn/tx-models#moonlight) to handle transfers of the native currency, gas payments, and serve as a contract execution entry point. +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. [Deep dive into the Transfer Contract](/learn/deep-dive/transaction_models/transactions) -### Citadel - -![Citadel](../../../assets/citadel.gif) - -Citadel is a Self-Sovereign Identity (SSI)/Digital Identity (DI) protocol designed for authenticating with third party services while upholding user privacy. With Citadel it’s possible to anonymously prove identity information, like meeting a certain age threshold or living in a certain jurisdiction, without revealing the exact information or revealing more information than is necessary. Given that Citadel is part of the network, it has wide ranging applications for on-chain activity and realizing compliance in regulated financial markets. - -[Deep dive into Citadel](/developer/digital-identity/protocol) +## Execution environments -### Zedger & XSC +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. -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. - -Zedger allows for the digital representation, native issuance and management of securities in a privacy-preserving manner. Issuers of securities are able to issue, manage, and let investors trade securities as XSC tokens It offers built-in support for compliant settlement, redemption of securities, preventing pre-approved users from having more than one account, supports dividend distribution and voting, and can handle capped transfers. Zedger aims to support a range of security types, like stocks, bonds and ETFs. The emphasis on regulatory compliance and privacy ensures that all operations meet the highest standards required by financial authorities and stakeholders. - -[Deep dive into Zedger](/learn/deep-dive/transaction_models/zedger) - -## Dusk primitives +### Dusk VM +[Dusk VM](/learn/deep-dive/dusk-vm) is a highly optimized virtual machine 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. -![Elliptic Curves image](../../../assets/elliptic_curves.png) +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. -At the foundation of Dusk’s architecture are the cryptographic primitives - BLS12_381, JubJub, Schnorr and Poseidon. These cryptography tools provide the robust security and privacy features of the network. Besides these, we also make use of our own Merkle tree implementation called dusk-merkle, and our own PLONK proving system. +[Deep dive into Dusk VM](/learn/deep-dive/dusk-vm) -### BLS12_381 +### Dusk EVM +[Dusk EVM](/learn/deep-dive/dusk-vm) is a fully EVM-equivalent execution environment. Built on the OP Stack with support for EIP-4844 (Proto-Danksharding), it enables developers to deploy smart contracts using standard EVM tooling—while benefiting from DuskDS's regulatory compliant infrastructure. -BLS12_381 is a pairing-friendly elliptic curve used within Dusk to enable aggregation of signatures, which significantly reduces the amount of data to be stored and transmitted over the network, improving overall efficiency of the blockchain. This curve is especially crucial in the context of zero-knowledge proofs, where it provides the backbone for secure and private transactions. +[Deep dive into Dusk EVM](/learn/deep-dive/dusk-evm) -[Deep dive into BLS](/learn/deep-dive/cryptography/bls) -### JubJub +## Applications -JubJub is an elliptic curve specifically designed to enable fast, secure zero-knowledge proofs. This curve is utilized within Dusk for the construction of efficient zk-SNARKs, allowing transactions and contracts to maintain privacy and integrity without the need to reveal underlying data. +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. -### Schnorr Signatures -Schnorr signatures are a type of digital signature scheme. They offer resistance against forgery. In Dusk, Schnorr signatures contribute significantly to securing user transactions and smart contract interactions. They ensure that only valid transactions are processed and added to the blockchain. +## Zedger / Hedger -### Poseidon +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. -Poseidon is a cryptographic hash function specifically designed for use in zero-knowledge circuits. It is optimized for performance, security and data integrity within Dusk. By producing a unique hash value for every distinct input, it forms the heart of Dusk’s data structures, making it virtually impossible to alter transaction data once it’s included in the blockchain. +Zedger allows for the digital representation, native issuance and management of securities in a privacy-preserving manner. Issuers of securities are able to issue, manage, and let investors trade securities as XSC tokens It offers built-in support for compliant settlement, redemption of securities, preventing pre-approved users from having more than one account, supports dividend distribution and voting, and can handle capped transfers. Zedger aims to support a range of security types, like stocks, bonds and ETFs. The emphasis on regulatory compliance and privacy ensures that all operations meet the highest standards required by financial authorities and stakeholders. -[Deep dive into hashing](/learn/deep-dive/cryptography/hashing) +[Deep dive into Zedger](/learn/deep-dive/transaction_models/zedger) -### Dusk-Merkle +Differently from Zedger, which operated directly on Rusk, Hedger runs on DuskEVM leveraging the EVM equivalency of Dusk’s new execution layer. ZK operations in Hedger are handled via precompiled contracts provided by DuskEVM, mirroring the functionality once exposed through host functions in Rusk. This shift enables significantly easier developer access to privacy-preserving logic, while preserving the regulatory guarantees and auditability required for compliant finance. -Dusk also includes a custom, sparse Merkle tree implementation that is agnostic to the choice of hash function. Merkle trees are a fundamental part of many blockchains, enabling efficient and secure verification of large data structures. The Dusk Merkle tree is designed for flexibility and performance, given it’s used in multiple locations like the stake and transfer contract, and Citadel. - -### PLONK +### Citadel -PLONK is a versatile proof system developed to facilitate the implementation of zero-knowledge proofs. It forms the core of Dusk’s proof system, allowing efficient and private transactions on the network that are both small in proof size and fast to verify. +![Citadel](../../../assets/citadel.gif) -With PLONK, developers can define custom and reusable circuits that can be integrated into Dusk based smart contracts. +Citadel is a Self-Sovereign Identity (SSI)/Digital Identity (DI) protocol designed for authenticating with third party services while upholding user privacy. With Citadel it’s possible to anonymously prove identity information, like meeting a certain age threshold or living in a certain jurisdiction, without revealing the exact information or revealing more information than is necessary. Given that Citadel is part of the network, it has wide ranging applications for on-chain activity and realizing compliance in regulated financial markets. -[Deep dive into PlonK](/learn/deep-dive/cryptography/plonk) \ No newline at end of file +[Deep dive into Citadel](/developer/digital-identity/protocol) \ No newline at end of file diff --git a/src/content/docs/learn/cryptography.md b/src/content/docs/learn/cryptography.md new file mode 100644 index 00000000..1511eaf0 --- /dev/null +++ b/src/content/docs/learn/cryptography.md @@ -0,0 +1,44 @@ +--- +title: Cryptography +description: An overview of the cryptographic primitives used in Dusk. +--- + +At the core of Dusk’s security model is a carefully curated suite of cryptographic primitives, many of which Dusk has helped pioneer. From the first Rust implementation of PLONK to research on PlonKup, FORT, and both the Reinforced Concrete hash and Poseidon Hash, Dusk has been pushing the state of the art to combine institutional-grade privacy with verifiable performance. Other building blocks such as BLS12-381, JubJub, Schnorr, sparse Merkle tree, and the PLONK proving system, form the low-level toolkit that powers Dusk. + +## Dusk primitives + +![Elliptic Curves image](../../../assets/elliptic_curves.png) + +At the foundation of Dusk’s architecture are the cryptographic primitives - BLS12_381, JubJub, Schnorr and Poseidon. These cryptography tools provide the robust security and privacy features of the network. Besides these, we also make use of our own Merkle tree implementation called dusk-merkle, and our own PLONK proving system. + +### BLS12_381 + +BLS12_381 is a pairing-friendly elliptic curve used within Dusk to enable aggregation of signatures, which significantly reduces the amount of data to be stored and transmitted over the network, improving overall efficiency of the blockchain. This curve is especially crucial in the context of zero-knowledge proofs, where it provides the backbone for secure and private transactions. + +[Deep dive into BLS](/learn/deep-dive/cryptography/bls) + +### JubJub + +JubJub is an elliptic curve specifically designed to enable fast, secure zero-knowledge proofs. This curve is utilized within Dusk for the construction of efficient zk-SNARKs, allowing transactions and contracts to maintain privacy and integrity without the need to reveal underlying data. + +### Schnorr Signatures + +Schnorr signatures are a type of digital signature scheme. They offer resistance against forgery. In Dusk, Schnorr signatures contribute significantly to securing user transactions and smart contract interactions. They ensure that only valid transactions are processed and added to the blockchain. + +### Poseidon + +Poseidon is a cryptographic hash function specifically designed for use in zero-knowledge circuits. It is optimized for performance, security and data integrity within Dusk. By producing a unique hash value for every distinct input, it forms the heart of Dusk’s data structures, making it virtually impossible to alter transaction data once it’s included in the blockchain. + +[Deep dive into hashing](/learn/deep-dive/cryptography/hashing) + +### Dusk-Merkle + +Dusk also includes a custom, sparse Merkle tree implementation that is agnostic to the choice of hash function. Merkle trees are a fundamental part of many blockchains, enabling efficient and secure verification of large data structures. The Dusk Merkle tree is designed for flexibility and performance, given it’s used in multiple locations like the stake and transfer contract, and Citadel. + +### PLONK + +PLONK is a versatile proof system developed to facilitate the implementation of zero-knowledge proofs. It forms the core of Dusk’s proof system, allowing efficient and private transactions on the network that are both small in proof size and fast to verify. + +With PLONK, developers can define custom and reusable circuits that can be integrated into Dusk based smart contracts. + +[Deep dive into PlonK](/learn/deep-dive/cryptography/plonk) \ No newline at end of file diff --git a/src/content/docs/learn/deep-dive/assets-and-regulations/mica.md b/src/content/docs/learn/deep-dive/assets-and-regulations/mica.md index 4e635f1d..b60423e4 100644 --- a/src/content/docs/learn/deep-dive/assets-and-regulations/mica.md +++ b/src/content/docs/learn/deep-dive/assets-and-regulations/mica.md @@ -17,7 +17,7 @@ MiCA defines and creates regulations for two things: * **Crypto Assets** - defined as ‘Distributed Ledger Technology-based cryptographic tokens that are used as a medium of exchange’. MiCA lays down specific definitions of three subclasses of crypto assets: * _Electronic Money Tokens_ - crypto assets that maintain a ‘stable’ value by referencing a single ‘real word’ fiat currency, specifically (and only for the purposes of MiCA) the Euro. Examples include Quantoz and STASIS EURO. * _Asset-Referenced Tokens_ - crypto assets that maintain a ‘stable’ value by referencing anything other than a single fiat currency (i.e. two or more fiat currencies, one or more cryptocurrencies, one or more other assets such as gold or diamonds). Examples include [PAX Gold](https://paxos.com/paxgold/) and [DIAM](https://www.diamdexx.com/). - * _Utility Tokens_ - crypto assets designed to provide access to a service offered by the issuing entity. Examples include [Dusk](/learn/tx-fees), [Filecoin](https://filecoin.io/) and [Binance Coin](https://www.binance.com/en). + * _Utility Tokens_ - crypto assets designed to provide access to a service offered by the issuing entity. Examples include [Dusk](/learn/deep-dive/tx-fees), [Filecoin](https://filecoin.io/) and [Binance Coin](https://www.binance.com/en). * **Crypto Asset Service Providers** - defined as entities that engage in any of the following activities: * custody and administration of crypto assets on behalf of third parties * crypto exchange services (running an exchange) diff --git a/src/content/docs/learn/deep-dive/dusk-evm.md b/src/content/docs/learn/deep-dive/dusk-evm.md new file mode 100644 index 00000000..7d7d5310 --- /dev/null +++ b/src/content/docs/learn/deep-dive/dusk-evm.md @@ -0,0 +1,69 @@ +--- +title: DuskEVM +description: DuskEVM is a fully EVM-compatible execution environment built on the Dusk Network. Powered by the OP Stack and EIP-4844 (Proto-Danksharding), it enables developers to leverage EVM tooling while settling on Dusk’s compliant and modular infrastructure. +--- + +DuskEVM is an EVM-equivalent execution environment within the modular Dusk stack, delivering scalable smart contract execution while inheriting security, consensus, and settlement guarantees from DuskDS. + +DuskEVM enables developers to deploy smart contracts using standard EVM tooling while benefiting from a modular architecture designed to support regulatory compliance and meet the needs of financial institutions. + +:::note[Note] +The separation of execution environments like DuskEVM from DuskDS introduces modularity into Dusk’s architecture, enabling scalability, extensibility, and protocol composability. +::: + +## Dusk's Modular Stack + +With the introduction of DuskEVM, Dusk has expanded into a modular stack, providing a clean separation between settlement and execution environments: + +| Layer | Description | +|------------------|-----------------------------------------------------------------------------| +| **DuskDS** | Settlement and data availability layer.| +| **DuskEVM** | EVM execution environment | +| **DuskVM** | Execution environment using Phoenix | + + + +DuskDS provides consensus, data availability, and settlement for the disintermediate trading of securities and other regulated assets. + +Execution environments like DuskEVM operate at the application layer, where disintermediation logic is executed. These environments can incorporate advanced cryptographic techniques, such as ZK and FHE, to enable privacy-preserving and compliant computations. + +:::note[Note] +Dusk's modular architecture makes Dusk highly extensible and composable, as new execution environments can be introduced without modifying the consensus and settlement layer. +::: + + +### How DuskEVM works + +The Ethereum Virtual Machine (EVM) is a general-purpose, stack-based, stateless execution environment that processes smart contract logic. As the EVM is independent of consensus and data availability, it can be instantiated independently. + +DuskEVM leverages the OP Stack and supports EIP-4844 (Proto-Danksharding) + +While DuskEVM uses the OP Stack architecture, it settles directly using DuskDS rather than Ethereum. This required no modification to Optimism core components and it has been implemented by adding additional services. + + +:::note[Note] +DuskEVM leverages DuskDS to store call data and blobs, enabling developers to use EVM tooling while relying on DuskDS for settlement and data availability. +::: + + +### Components + +DuskEVM relies on the following components: + +| Component | Description | +|------------------|--------------------------------------------------------------------------| +| **Sequencer** | Batches transactions | +| **Execution Node**| Executes smart contracts +| **Batcher** | Posts data and transaction batches to DuskDS | +| **Fraud Proofs** | Provides a mechanism to challenge invalid state transitions | + + +:::note[Note] +DuskEVM currently inherits a 7-day challenge period from the OP Stack. This is a temporary limitation, as future upgrades will introduce one-block finality. +::: + +### Architecture + +The diagram below illustrates Dusk’s evolution from a monolithic design to a modular architecture, where DuskDS acts as the foundational consensus and data availability layer, and multiple execution environments operate independently at the application layer: + +![Dusk's modular architecture](../../../../assets/modular_vs_monolithic.png) \ No newline at end of file diff --git a/src/content/docs/learn/deep-dive/dusk-vm.md b/src/content/docs/learn/deep-dive/dusk-vm.md index 6bad495c..de76e82b 100644 --- a/src/content/docs/learn/deep-dive/dusk-vm.md +++ b/src/content/docs/learn/deep-dive/dusk-vm.md @@ -1,5 +1,5 @@ --- -title: Dusk VM and Dusk Core +title: Dusk VM description: Learn about Dusk VM, the wasmtime VM that efficiently executes smart contracts on Dusk. --- diff --git a/src/content/docs/learn/token-standards.md b/src/content/docs/learn/deep-dive/token-standards.md similarity index 79% rename from src/content/docs/learn/token-standards.md rename to src/content/docs/learn/deep-dive/token-standards.md index fca9e053..30824d34 100644 --- a/src/content/docs/learn/token-standards.md +++ b/src/content/docs/learn/deep-dive/token-standards.md @@ -12,6 +12,6 @@ A Token Standard specifies the parameters and data types that must be used in th ## Dusk's Token Standards Dusk has several token standards to meet different use cases, providing developers the tools they need to build secure and interoperable blockchain applications: -- TC (Transparent Token Contract): The transparent token standard on Dusk functions similarly to ERC20 and [Moonlight](/learn/tx-models#moonlight), where token transfers are transparent. An example implementation can be seen here. -- XC (Confidential Token Contract): The privacy-preserving token standard on Dusk offers privacy features, ensuring that transaction details are kept confidential. This standard is similar to [Phoenix](/learn/tx-models#phoenix) transactions, where the sender, receiver and amount transferred are not exposed to anyone other than the involved parties. +- TC (Transparent Token Contract): The transparent token standard on Dusk functions similarly to ERC20 and [Moonlight](/learn/deep-dive/transaction_models/tx-models#moonlight), where token transfers are transparent. An example implementation can be seen here. +- XC (Confidential Token Contract): The privacy-preserving token standard on Dusk offers privacy features, ensuring that transaction details are kept confidential. This standard is similar to [Phoenix](/learn/deep-dive/transaction_models/tx-models#phoenix) transactions, where the sender, receiver and amount transferred are not exposed to anyone other than the involved parties. - XSC (Confidential Security Contract): The security token contract (XSC) is a set of standards on Dusk, specifically designed for the issuance and life-cycle management of different types of securities. This standard has features that ensure regulatory compliance and provides functions for whitelisting, force transfers, corporate actions (E.g. dividend or coupon payments, voting), and auditor access to private state. It uses the [Zedger](/learn/deep-dive/transaction_models/zedger) protocol. diff --git a/src/content/docs/learn/deep-dive/transaction_models/transactions.md b/src/content/docs/learn/deep-dive/transaction_models/transactions.md index 3ff859ad..c35859df 100644 --- a/src/content/docs/learn/deep-dive/transaction_models/transactions.md +++ b/src/content/docs/learn/deep-dive/transaction_models/transactions.md @@ -13,7 +13,7 @@ The Transfer Contract provides support for: - [Phoenix](/learn/deep-dive/transaction_models/phoenix): A privacy-preserving, UTXO-based model. :::note[Note] -The Transfer Contract implements Dusk's Phoenix and Moonlight [transaction models](/learn/tx-models), allowing users to effortlessly switch between shielded and public transactions. +The Transfer Contract implements Dusk's Phoenix and Moonlight [transaction models](/learn/deep-dive/transaction_models/tx-models), allowing users to effortlessly switch between shielded and public transactions. ::: These two models act as equivalent payment rails for Dusk: @@ -26,7 +26,7 @@ This dual-model approach provides the optimal flexibility for privacy and transp # Paying for gas fees -[Gas fees](/learn/tx-fees) can be paid using Phoenix notes or Moonlight balances: +[Gas fees](/learn/deep-dive/tx-fees) can be paid using Phoenix notes or Moonlight balances: - When paying fees using Moonlight, fees are deducted directly from the sender's balance. - When paying fees using Phoenix, fees are securely embedded in the zero-knowledge proof. diff --git a/src/content/docs/learn/tx-models.md b/src/content/docs/learn/deep-dive/transaction_models/tx-models.md similarity index 100% rename from src/content/docs/learn/tx-models.md rename to src/content/docs/learn/deep-dive/transaction_models/tx-models.md diff --git a/src/content/docs/learn/tx-fees.md b/src/content/docs/learn/deep-dive/tx-fees.md similarity index 100% rename from src/content/docs/learn/tx-fees.md rename to src/content/docs/learn/deep-dive/tx-fees.md diff --git a/src/content/docs/learn/glossary.md b/src/content/docs/learn/glossary.md index 330fdc48..04c603df 100644 --- a/src/content/docs/learn/glossary.md +++ b/src/content/docs/learn/glossary.md @@ -25,10 +25,17 @@ A standardized framework for confidential smart contracts, which any company or The native cryptocurrency of Dusk. It is used to pay for transaction fees and staking. +#### Dusk EVM + +[Dusk EVM](/learn/deep-dive/dusk-evm) is a EVM execution environment, that acts as a L2 that settles on Dusk (L1). + #### Dusk VM [Dusk VM](/learn/deep-dive/dusk-vm) is general purpose virtual machine developed by Dusk that runs WASM smart contracts and manages their memory. +#### Hedger +Hedger is the evolution of Zedger, built on DuskEVM and powered by fully homomorphic encryption for enhanced privacy. + #### Hyperstaking Hyperstaking is a feature that allows smart contracts to manage stakes with custom logic. Similar to "Account Abstraction," it enables use cases like privacy-preserving staking, affiliate programs, delegation, liquid staking, and yield boosting. Staking operations are initiated via a provisioner key, with signature verification only required for the initial stake, offering flexibility and innovation in staking models. @@ -47,11 +54,11 @@ The smallest denomination of DUSK. 10^9 LUX = 1 DUSK, 1 DUSK = 1,000,000,000 LUX #### Moonlight -[Moonlight](/learn/tx-models#moonlight) is an account-based transaction model on Dusk that tracks balances for accounts and contracts, offering full transparency. It is faster and cheaper than Phoenix, making it easier for developers to integrate with external protocols. +[Moonlight](/learn/deep-dive/transaction_models/tx-models#moonlight) is an account-based transaction model on Dusk that tracks balances for accounts and contracts, offering full transparency. It is faster and cheaper than Phoenix, making it easier for developers to integrate with external protocols. #### Phoenix -[Phoenix](/learn/tx-models#phoenix) is a UTXO-based, privacy-preserving transaction model on Dusk used for transferring DUSK. It enables users to spend "notes" privately using zero-knowledge proofs without linking balances to addresses. +[Phoenix](/learn/deep-dive/transaction_models/tx-models#phoenix) is a UTXO-based, privacy-preserving transaction model on Dusk used for transferring DUSK. It enables users to spend "notes" privately using zero-knowledge proofs without linking balances to addresses. #### Public Account @@ -63,7 +70,7 @@ A shielded account is based on the [Phoenix](#phoenix) UTXO transaction model an #### Profile -A [profile](/learn/wallet-terminology#profile-and-accounts) is a pairing of a Public Account ([Moonlight](#moonlight) and a Shielded Account ([Phoenix](#phoenix) derived from a single mnemonic. Profiles are created in pairs to allow for both public and privacy-preserving transactions. +A [profile](/learn/wallet-terminology#profile-and-accounts) is a pairing of a Public Account [Moonlight](#moonlight) and a Shielded Account ([Phoenix](#phoenix) derived from a single mnemonic. Profiles are created in pairs to allow for both public and privacy-preserving transactions. #### RUES @@ -91,7 +98,7 @@ The [Web Wallet](https://apps.dusk.network/wallet/) is the official web-based wa #### Zedger -[Zedger](/learn/core-components#zedger--xsc) is a Dusk-based protocol combining UTXO and account models for the private, compliant management of securities. Zedger allows issuers to digitally represent, issue, and trade securities like stocks and bonds while ensuring regulatory compliance. +[Zedger](/learn/core-components#zedger--hedger) is a Dusk-based protocol combining UTXO and account models for the private, compliant management of securities. Zedger allows issuers to digitally represent, issue, and trade securities like stocks and bonds while ensuring regulatory compliance. ## Definitions diff --git a/src/content/docs/learn/introduction.md b/src/content/docs/learn/introduction.md index 9e2f0b57..e218cb02 100644 --- a/src/content/docs/learn/introduction.md +++ b/src/content/docs/learn/introduction.md @@ -11,7 +11,7 @@ Utilizing zero-knowledge proofs (ZKPs) and other advanced cryptographic primitiv All products issued on Dusk’s platform are fully compliant with the European Union’s **MiFID** II and **MiFIR** regulations, as well as compatible with the **DLT Pilot Regime Regulation**. Dusk also provides baked-in compliance with **MiCA** and **GDPR**. Dusk employs an innovative PoS-based consensus mechanism, known as [Succinct Attestation](/learn/deep-dive/succinct-attestation). -Dusk is powered by [zero knowledge proofs](/learn/deep-dive/cryptography/zkp), and achieves flexibility through its multiple [transaction models](/learn/tx-models#transaction-models-on-dusk). +Dusk is powered by [zero knowledge proofs](/learn/deep-dive/cryptography/zkp), and achieves flexibility through its multiple [transaction models](/learn/deep-dive/transaction_models/tx-models#transaction-models-on-dusk). Simply put, **Dusk is** a privacy-enabled and regulatory-compliant decentralized ledger paves the way for **decentralized market infrastructure**. @@ -33,7 +33,7 @@ Its whole stack has been built to address all the applicable regulations that ap ### Unparalleled Privacy -Dusk implements [confidential smart contracts](/developer/smart-contract/guides/my-first-contract) by allowing anyone to build ZKP-powered contracts. Our privacy-preserving and public transaction models [Phoenix and Zedger](/learn/tx-models#transaction-models-on-dusk) give users and developers the flexibility they need, based on their use-case, to pick the visibility of transactions. +Dusk implements [confidential smart contracts](/developer/smart-contract/guides/my-first-contract) by allowing anyone to build ZKP-powered contracts. Our privacy-preserving and public transaction models [Phoenix and Zedger](/learn/deep-dive/transaction_models/tx-models#transaction-models-on-dusk) give users and developers the flexibility they need, based on their use-case, to pick the visibility of transactions. To ensure privacy, Dusk utilizes some of the most advanced and widely regarded cryptographic tools available in the realm of zero-knowledge (ZK) technology. Notably, Dusk employs the [PlonK](/learn/deep-dive/cryptography/plonk) proof system and the [Poseidon](/learn/deep-dive/cryptography/hashing#poseidon-hash) hash function, both of which are critical components in the ZK toolkit. PlonK is highly efficient in generating and verifying proofs, while Poseidon enhances security with its specially designed hashing algorithm tailored for ZK applications. diff --git a/src/content/docs/learn/overview.mdx b/src/content/docs/learn/overview.mdx index da1ffaae..52694e5f 100644 --- a/src/content/docs/learn/overview.mdx +++ b/src/content/docs/learn/overview.mdx @@ -27,7 +27,7 @@ Learn [more about Dusk](/learn/introduction), its [usecases](/learn/introduction There are several things you can do on Dusk: - [Stake and accrue rewards](/learn/guides/staking-basics/): DUSK can be staked to secure the network and receive rewards. Staking is easy, and it allows users to participate in consensus and increase the decentralization of the protocol. - [Issue Regulated Financial Assets](https://dusk.network/contact/): Dusk is designed for financial institutions to issue digital bonds, stocks, and RWAs natively on-chain—without the need for intermediaries like Central Securities Depositories (CSDs). -- [Shielded and Public Transactions](/learn/tx-models/): Dusk offers both shielded and public transactions through Phoenix & Moonlight. Institutions can comply with regulations while keeping sensitive data private. +- [Shielded and Public Transactions](/learn/deep-dive/transaction_models/tx-models): Dusk offers both shielded and public transactions through Phoenix & Moonlight. Institutions can comply with regulations while keeping sensitive data private. - [Use Self-Sovereign Identity](/developer/digital-identity/protocol/): Dusk’s Citadel SSI solution enables privacy-first identity verification (useful for KYC/AML), letting users prove their identity without disclosing personal details - [Build & Deploy Smart Contracts](/developer/smart-contract/introduction/): Dusk’s ZK-friendly virtual machine (Dusk VM) enables confidential, high-performance smart contracts. diff --git a/src/content/docs/learn/tokenomics.md b/src/content/docs/learn/tokenomics.md index b1935848..7a43b0ee 100644 --- a/src/content/docs/learn/tokenomics.md +++ b/src/content/docs/learn/tokenomics.md @@ -39,7 +39,7 @@ The DUSK token is widely accessible on top-tier CEXs and DEXs. For more informat DUSK serves several key purposes within the ecosystem: * Used for staking in consensus participation. * Rewards to consensus participants. -* Payment of network fees ([gas](/learn/tx-fees)). +* Payment of network fees ([gas](/learn/deep-dive/tx-fees)). * Paying for the deployment of dApps on the network. * Payment of services on the network. diff --git a/src/content/docs/learn/web-wallet.md b/src/content/docs/learn/web-wallet.md index 7c1ac8bf..5f679fae 100644 --- a/src/content/docs/learn/web-wallet.md +++ b/src/content/docs/learn/web-wallet.md @@ -45,5 +45,5 @@ Once your wallet is set up, you’ll be able to view your balance, transaction h :::tip[Tip] -The Dusk Web Wallet supports both **shielded** and **public** transactions, giving you the flexibility to meet privacy and compliance requirements as needed. You can use Phoenix for confidential transfers and Moonlight when full transparency is essential. [Learn more about these transaction models](/learn/tx-models). +The Dusk Web Wallet supports both **shielded** and **public** transactions, giving you the flexibility to meet privacy and compliance requirements as needed. You can use Phoenix for confidential transfers and Moonlight when full transparency is essential. [Learn more about these transaction models](/learn/deep-dive/transaction_models/tx-models). ::: diff --git a/src/sidebars/defaultSidebar.js b/src/sidebars/defaultSidebar.js index 1bb1015a..53fb0cdf 100644 --- a/src/sidebars/defaultSidebar.js +++ b/src/sidebars/defaultSidebar.js @@ -7,10 +7,8 @@ const defaultSidebar = [ { label: "Native Issuance", link: "learn/tokenization-comparison" }, { label: "Core Values", link: "learn/core-values" }, { label: "Core Components", link: "learn/core-components" }, + { label: "Cryptography", link: "learn/cryptography" }, { label: "Tokenomics", link: "learn/tokenomics" }, - { label: "Wallet Terminology", link: "learn/wallet-terminology" }, - { label: "Transaction Models", link: "learn/tx-models" }, - { label: "Transaction Fees & Gas", link: "learn/tx-fees" }, { label: "Stake Abstraction", link: "learn/hyperstaking" }, { label: "Get involved & Community", link: "learn/community" }, { label: "Glossary", link: "learn/glossary" }, @@ -100,8 +98,12 @@ 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: "Economic Protocol", link: "learn/deep-dive/economic-protocol" }, { label: "Dusk VM", link: "learn/deep-dive/dusk-vm" }, + { label: "DuskEVM", link: "learn/deep-dive/dusk-evm" }, { label: "Succinct Attestation Consensus", link: "learn/deep-dive/succinct-attestation",