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/developer/overview.mdx
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,13 @@ This documentation provides an insight into everything related to development on
8
8
9
9
## Developing on Dusk
10
10
11
-
There are two different stacks to develop on Dusk. The first one is building on-chain the second one is building off-chain applications that integrate with Dusk.
11
+
The Dusk architecture offers a data availability layer ([DuskDS](/developer/integrations/introduction)) and an execution layer ([DuskEVM](/developer/smart-contracts-dusk-evm/deploy-on-evm)).
12
+
Depending on the use case, developers may want to integrate with one or another.
13
+
14
+
For a smoother integration, it is generally recomended to integrate with [DuskEVM](/developer/smart-contracts-dusk-evm/deploy-on-evm).
15
+
16
+
It needs to be noted that Dusk is transitioning from a monolithic architecture towards a modular one. The difference between the two is represented in the picture below:
0 commit comments