diff --git a/src/content/docs/developer/integrations/introduction.md b/src/content/docs/developer/integrations/introduction.md index 677ca2fd..68363187 100644 --- a/src/content/docs/developer/integrations/introduction.md +++ b/src/content/docs/developer/integrations/introduction.md @@ -1,9 +1,9 @@ --- title: Integrations introduction -description: Integrate with Dusk. Explore integration guides, SDKs, and tools tailored for developers and institutions. +description: Integrate with DuskDS. Explore integration guides, SDKs, and tools tailored for developers and institutions. --- -This section outlines the libraries that developers can use to integrate with Dusk: +This section outlines the libraries that developers can use to: - [W3sper SDK](/developer/integrations/w3sper) - [wallet-core](/developer/integrations/wallet-core) diff --git a/src/content/docs/developer/integrations/wallet-core.md b/src/content/docs/developer/integrations/wallet-core.md index 7795b903..a06da7f9 100644 --- a/src/content/docs/developer/integrations/wallet-core.md +++ b/src/content/docs/developer/integrations/wallet-core.md @@ -1,6 +1,6 @@ --- title: Wallet Core Library -description: Integrate with Dusk Wallet-Core library to manage transactions. +description: Integrate with DuskDS Wallet-Core library to manage transactions. --- This documentation explains how to use the wallet-core library from any programming language of your preference. diff --git a/src/content/docs/developer/overview.mdx b/src/content/docs/developer/overview.mdx index 2e00f65a..7fce38c7 100644 --- a/src/content/docs/developer/overview.mdx +++ b/src/content/docs/developer/overview.mdx @@ -12,6 +12,7 @@ There are two different stacks to develop on Dusk. The first one is building on- - + + diff --git a/src/content/docs/learn/deep-dive/dusk-evm.md b/src/content/docs/learn/deep-dive/dusk-evm.md index 1458b12b..326c7e07 100644 --- a/src/content/docs/learn/deep-dive/dusk-evm.md +++ b/src/content/docs/learn/deep-dive/dusk-evm.md @@ -90,8 +90,8 @@ DuskEVM currently inherits a 7-day challenge period from the OP Stack. This is a | Opcode | Solidity Equivalent | Behavior | |-------------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| | `COINBASE` | `block.coinbase` | Returns the address of the current Sequencer's fee wallet. Effectively the same as Ethereum, but typically does not change from block to block. | -| `PREVRANDAO`| `block.prevrandao` | Returns the PREVRANDAO (the most recent RANDAO) value of L1 at the current L1 origin block. | -| `ORIGIN` | `tx.origin` | If the tx is an **L1 ⇒ L2** tx from an L1 smart contract, `tx.origin` is set to the **aliased address** of the originator. Else b +| `PREVRANDAO`| `block.prevrandao` | Returns the PREVRANDAO (the most recent RANDAO) value of DuskDS at the current DuskDS origin block. | +| `ORIGIN` | `tx.origin` | If the tx is a **DuskDS ⇒ DuskEVM** tx from a DuskDS smart contract, `tx.origin` is set to the **aliased address** of the originator. Else b :::note[Note] @@ -104,6 +104,6 @@ DuskEVM does not have a public mempool, as it is currently only visible to the S The process for a rollup transaction has two requirements: The transaction needs to be written to DuskDS, tipically by the op-batcher. -The transaction needs to be executed to modify the state (by op-geth). Afterwards, op-proposer writes a commitment to the post-transaction state to L1. Note that op-proposer does not need to write a commitment after each transaction to L1; it is OK to commit to the state after a block of transactions. +The transaction needs to be executed to modify the state (by op-geth). Afterwards, op-proposer writes a commitment to the post-transaction state to [DuskDS](/learn/core-components#duskds) . Note that op-proposer does not need to write a commitment after each transaction to DuskDS; it is OK to commit to the state after a block of transactions. More information about the batching process can be seen in the OP stack specs. diff --git a/src/content/docs/learn/glossary.md b/src/content/docs/learn/glossary.md index 6a3cb005..d1f66dd3 100644 --- a/src/content/docs/learn/glossary.md +++ b/src/content/docs/learn/glossary.md @@ -44,10 +44,6 @@ Hyperstaking is a feature that allows smart contracts to manage stakes with cust [Kadcast](/learn/core-components#network-layer-kadcast) is a structured information propagation protocol used by Dusk, characterized by a direct correlation between network performance, latency, and the number of nodes. -#### Lightspeed - -Lightspeed is the Dusk L2 solution that offers full EVM equivalence. Lightspeed allows Dusk to scale even further and maintain full interoperability with EVM-based blockchains. - #### LUX The smallest denomination of DUSK. 10^9 LUX = 1 DUSK, 1 DUSK = 1,000,000,000 LUX. diff --git a/src/content/docs/learn/overview.mdx b/src/content/docs/learn/overview.mdx index 52694e5f..2115e29d 100644 --- a/src/content/docs/learn/overview.mdx +++ b/src/content/docs/learn/overview.mdx @@ -46,8 +46,10 @@ This section provides a brief overview of Dusk’s [core components](/learn/core | **Phoenix & Moonlight** | Dusk enables both shielded and public transactions through its dual-model approach, offering unmatched flexibility to achieve both privacy and compliance. | ![Phoenix & Moonlight Image](../../../assets/get_started/Phoenix_and_Moonlight.png) | | **Citadel** | Self-sovereign identity solution for privacy-preserving KYC/AML compliance. It is a protocol designed for authenticating with third party services while protecting sensitive data | ![Citadel Image](../../../assets/get_started/Citadel.png) | + +:::tip[Tip] Find more details about Dusk’s core components [here](/learn/core-components). ---- +:::