Skip to content

Fixed duplicated content #99

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
lufa23 merged 1 commit into from
Sep 9, 2025
Merged

Fixed duplicated content #99

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 0 additions & 9 deletions src/content/docs/learn/deep-dive/dusk-evm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,15 +52,6 @@ DuskEVM leverages DuskDS to store blobs, enabling developers to use EVM tooling
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)
=======
DuskEVM leverages DuskDS to store all data, such as aggregated transaction data and output roots. This enables developers to use EVM tooling while relying on DuskDS for settlement and data availability.
:::

## Architecture

The diagram below illustrates Dusk’s evolution from a monolithic design to a modular architecture, where DuskDS acts as the foundational consensus, settlement and data availability layer, and multiple execution environments operate independently at the application layer:
Expand Down