Add DuskEVM page #75
Add DuskEVM page #75
Conversation
There was a problem hiding this comment.
It's a bit of a semantics game, but let me know what you think of my comments @lufa23 @Neotamandua
| @@ -0,0 +1,76 @@ | |||
| --- | |||
| title: DuskEVM | |||
| description: DuskEVM is a fully EVM-compatible Layer 2 rollup built on the Dusk Network. Powered by the OP Stack and EIP-4844 (Proto-Danksharding), it enables developers to leverage Ethereum tooling while settling on Dusk L1’s compliant, privacy-preserving infrastructure. | |||
There was a problem hiding this comment.
I'm not a big fan of calling DuskEVM a L2 due to the way we position it in our architecture. DuskEVM sits somewhere between a L2 and being an extra execution environment within Rusk. I think we should refer it as one of potentially many execution environments. And the specific layer being the execution layer.
The 7-day challenge period is a quirk we have to live with in the very short term, until we implement our approach to get to same block finality.
Here's an architecture picture to illustrate what I mean:
| description: DuskEVM is a fully EVM-compatible Layer 2 rollup built on the Dusk Network. Powered by the OP Stack and EIP-4844 (Proto-Danksharding), it enables developers to leverage Ethereum tooling while settling on Dusk L1’s compliant, privacy-preserving infrastructure. | ||
| --- | ||
|
|
||
| DuskEVM is an EVM-equivalent L2 execution environment built on Dusk. It leverages the <a href="https://docs.optimism.io/stack/getting-started" target="_blank">OP Stack</a> and supports <a href="https://www.eip4844.com/" target="_blank">EIP-4844</a> (Proto-Danksharding) to deliver scalable and modular EVM execution while settling on the regulatory compliant and privacy-focused Dusk (L1) infrastructure. |
There was a problem hiding this comment.
| DuskEVM is an EVM-equivalent L2 execution environment built on Dusk. It leverages the <a href="https://docs.optimism.io/stack/getting-started" target="_blank">OP Stack</a> and supports <a href="https://www.eip4844.com/" target="_blank">EIP-4844</a> (Proto-Danksharding) to deliver scalable and modular EVM execution while settling on the regulatory compliant and privacy-focused Dusk (L1) infrastructure. | |
| DuskEVM is an EVM-equivalent L2 execution environment built on Dusk. It leverages the <a href="https://docs.optimism.io/stack/getting-started" target="_blank">OP Stack</a> and supports <a href="https://www.eip4844.com/" target="_blank">EIP-4844</a> (Proto-Danksharding) to deliver scalable and modular EVM execution while settling on the regulatory compliant and privacy-focused Dusk (L1) infrastructure. |
This sounds a bit like we're suggesting DuskEVM cannot be compliant and privacy enabled. We in fact can do that up to a certain extend with the current dApp we have in development.
I also wouldn't say the L1 is privacy-focused. It has privacy/ZK capabilities that can be used in a wide context, but in the end it's a means to end -> Disintermediate TradFi.
Strategically that means that Dusk with small letter d (re: L1) is the consensus and data availability layer within our architecture to provide security for, and enable the settlement of, disintermediate securities trading/management transactions.
The application layers (DuskEVM instances, Piecrust instances) are the execution environments in which the computations to do these disintermediation actions take place. ZK/FHE are part of those computations.
Co-authored-by: Hein Dauven <heindauven@gmail.com>
[ADDED]
[CHANGED]