diff --git a/astro.config.js b/astro.config.js index 2509dd19..50d42fef 100644 --- a/astro.config.js +++ b/astro.config.js @@ -27,6 +27,7 @@ export default defineConfig({ '/learn/deep-dive/assets-and-regulations/mica': '/learn/deep-dive/assets-and-regulations', '/learn/deep-dive/assets-and-regulations/lifecycle': '/learn/deep-dive/assets-and-regulations', '/learn/deep-dive/assets-and-regulations/dematerialization': '/learn/deep-dive/assets-and-regulations', + '/learn/deep-dive/economic-protocol': '/learn/tokenomics', '/learn/wallet-terminology': '/learn/glossary', '/developer/integrations/hashing-algorithms': '/developer/integrations/reference', '/developer/integrations/addresses': '/developer/integrations/reference', diff --git a/src/components/ResourceLinksGrid.astro b/src/components/ResourceLinksGrid.astro index 5f9198c5..1af5d530 100644 --- a/src/components/ResourceLinksGrid.astro +++ b/src/components/ResourceLinksGrid.astro @@ -14,9 +14,9 @@ import { LinkCard, CardGrid } from "@astrojs/starlight/components"; description="Check out Dusk's privacy-preserving self-sovereign identity protocol." /> Dusk Block Explorer, along with statistics and information about the network. +You can view transactions and blocks on the Dusk Block Explorer. Dusk is a privacy-preserving blockchain. Privacy-preserving [Phoenix](/learn/deep-dive/duskds-tx-models) 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/deep-dive/duskds-tx-models) 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. +The explorer can show the transaction type and metadata such as payload, fee, and gas used (depending on the transaction model and contract). diff --git a/src/content/docs/learn/community.mdx b/src/content/docs/learn/community.mdx index 8fb82753..b41babee 100644 --- a/src/content/docs/learn/community.mdx +++ b/src/content/docs/learn/community.mdx @@ -1,37 +1,51 @@ --- title: Get involved & Community -description: An overview of Dusk socials and official channels. Here you can find information to join and get involved in Dusk. +description: Official channels for updates and support, plus ways to contribute to the ecosystem and docs. --- import { LinkCard, CardGrid } from '@astrojs/starlight/components'; -Welcome to the Dusk community section! Here, you can connect with us and join vibrant discussions about our technology and its applications. Your engagement and feedback are vital to our growth and success. +Use the channels below to get updates, ask questions, and contribute. -## Connect with Us - -Get in touch with us. We are very happy to engage directly with our community and users. Don't shy away from shooting us a message in case you have questions, or simply to say hi! +## Official channels - - - - + + + + -## Socials +## Getting help + +- For documentation fixes and requests, contribute in the docs repo: dusk-network/docs. +- For protocol/app questions, use Discord. +- Be careful with DMs and links. Official channels will never ask for your seed phrase or private keys. -Want to stay up-to-date and learn more about Dusk? Keep an eye out on the following platforms: +## Socials -- [Dusk Twitter](https://twitter.com/DuskFoundation) +- [Dusk X(Twitter)](https://twitter.com/DuskFoundation) - [Dusk LinkedIn](https://www.linkedin.com/company/dusknetwork/) - [Dusk Youtube](https://www.youtube.com/c/DuskNetwork) - [Dusk Reddit](https://www.reddit.com/r/DuskNetwork/) - [Dusk Github](https://github.com/dusk-network) -## We'd Love to Hear from You! - -Your feedback helps us improve. Feel free to suggest new ideas or report any issues through our website form [here](https://dusk.network/contact/). - -## Join Dusk as a Node operator +## Run a node -To ease you into the intricacies of Dusk, you might consider participating in node running: [run a Provisioner node](/operator/provisioner). +Interested in helping secure the network? Start here: [Run a provisioner node](/operator/provisioner). diff --git a/src/content/docs/learn/core-values.mdx b/src/content/docs/learn/core-values.mdx index bc8ee88d..05c21da4 100644 --- a/src/content/docs/learn/core-values.mdx +++ b/src/content/docs/learn/core-values.mdx @@ -1,61 +1,57 @@ --- title: Core Values -description: Learn about Dusk’s decentralized Financial Market Infrastructure and how it provides privacy and regulatory compliance. +description: "What Dusk optimizes for: regulated markets, privacy with selective disclosure, and deterministic settlement." --- -## Vision +This page summarizes the principles behind Dusk and the tradeoffs they imply. +If you’re new, start with [Overview](/learn/overview) and then read [Core Components](/learn/core-components). -Dusk's **vision** describes the desired state of our organization within a foreseeable timeframe and guides the direction of the business's efforts in a practical way. You can regard it as the objective of the organization and the lighthouse in planning and constantly reassessing the step in building a highly-effective strategic plan. +## Principles -:::tip[Dusk's vision] -We envision a future where digital assets are seamlessly integrated into the decentralized global economy. -::: +### Regulated workflows, on-chain -It is worth expanding on some of the terminology of our *vision statement* and their significance for Dusk's overall strategy in advancing our [mission](#mission). +Dusk is built for markets where rules are part of the product: -
-**More on Dusk's vision** -💡 Dusk's vision significantly extends the *decentralized finance (DeFi)* focus horizon. The latter relates almost exclusively to a class of digital assets (i.e. utility tokens) alternative to, and non-overlapping with traditional asset-backed instruments. Instead, our vision extends the *DeFi principles* to the whole panoply of assets and, as such, it encompasses the entire ensemble of digital tokens, including those being **asset-backed**, i.e. **tokens representing ownership of real world goods or financial instruments, and as such regulated by the law**. The most emblematic of these assets are [securities](https://www.investopedia.com/terms/s/security.asp), and with *security tokens* we indicate their digital representation on the digital ledger technology (DLT) such as *blockchain*. -
+- eligibility and access controls +- disclosure and reporting requirements +- constraints like limits, holds, and transfer restrictions -:::note -🔮 The term Decentralized Market Infrastructure (DeMI) refers to leveraging Distributed Ledger Technologies (DLTs) to create a protocol-based Financial Market Infrastructure, as opposed to traditional platform-based systems like Central Securities Depositories (CSDs). DeMI enhances the efficiency and reduces the costs of regulated financial markets. -::: +### Privacy with selective disclosure -## Ambition +Dusk treats privacy as a protocol feature, not an application add-on: -:::tip[Dusk's ambition] -A decentralized, privacy-preserving, and programmable financial market infrastructure. -::: +- confidential balances and transfers where needed +- the ability to reveal information to authorized parties when required -The [DLT-R regime](https://www.ey.com/en_gr/tax/tax-alerts/regulation-eu-2022-858-on-distributed-ledger-technology-market-infrastructures) came into effect in June 2023. It is Dusk ambition to comply with the DLT-R regulation and enhance a licensed security exchange to operate under such exemption. +For details, see [Cryptography](/learn/cryptography) and [Transaction Models](/learn/deep-dive/duskds-tx-models). -## Mission +### Deterministic settlement -With **mission** we define Dusk organization’s *core purpose, focus, and aims*. +Market infrastructure needs predictable finality. DuskDS is designed for fast, deterministic settlement suitable for regulated venues. -:::tip[Dusk's mission] -We empower users to fully control their assets. -::: +### Modular architecture -This mission statement is short but dense in its significance. In its essence, Dusk enroots within the DeFi movement, insofar as aiming to return to the users the prerogative to be custodians of their own assets, and dispose of them as they see fit (within the confines of what the law allows). +Dusk separates settlement from execution so you can match the right environment to each use case: -In fact, the ambition goes far beyond custodianship, as DeFi protocols provide the opportunity to augment digital assets with behaviours and characteristics that can be directly programmed within the assets themselves, and composed as the users sees fit. These behaviours are codified within the so called _smart contracts_. +- DuskDS for consensus, settlement, and privacy-capable transaction models +- DuskEVM for EVM-compatible application development -
-**More on DeFi advantages** -💡 `DeFi` protocols uniquely allow for **user-centric composability of applications**, as well as **global liquidity aggregation** across the entirety of their ecosystem. This departs radically from the incumbent **platform-brokered** landscape, where financial services are siloed, interoperability is almost non-existent, and liquidity is fragmented. -
+## Vision -## Culture +:::tip[Dusk's vision] +Digital assets integrated into the decentralized global economy. +::: + +## Mission -At Dusk, we prioritize our core values of **integrity, communication, innovation, responsibility, and collaboration** in all of our endeavors. +:::tip[Dusk's mission] +Enable people and institutions to control and use their assets on-chain, within real-world constraints. +::: -
-**More on Dusk's culture** -💡 Dusk is a flat, community-oriented organization that is focused on advancing a novel networking protocol through a combination of pervasive knowledge sharing, an evolutionary development process, frequent communication, and joint ownership of all deliverables. We strive to tame complexity through these practices and to be a trusted and respected leader in the decentralized software industry. +## Culture -We are committed to honesty, effective communication, and continuous innovation, and we take ownership of our tasks and responsibilities with a focus on excellence and the best interests of our users. We also value collaboration and teamwork, fostering a culture of mutual support and shared knowledge. +We aim to be clear and rigorous in the way we build: -These values are integral to our identity as a company and our commitment to delivering high-quality decentralized software. -
+- write things down (docs, specs, and concrete examples) +- prefer secure-by-design primitives over “bolt-on” complexity +- keep developer UX practical (EVM where it helps, native where it matters) diff --git a/src/content/docs/learn/cryptography.md b/src/content/docs/learn/cryptography.md index 4daef53a..9eb95b66 100644 --- a/src/content/docs/learn/cryptography.md +++ b/src/content/docs/learn/cryptography.md @@ -1,42 +1,41 @@ --- title: Cryptography -description: An overview of the cryptographic primitives used in Dusk. +description: The main cryptographic building blocks behind Dusk’s privacy and verification. --- -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 uses zero-knowledge proofs and elliptic curve cryptography to enable confidential transactions and selective disclosure. +This page is a high-level map of the primitives you’ll see referenced across the docs. -## Dusk primitives +For protocol-level details and formal security arguments, refer to the [Dusk whitepaper](https://dusk-cms.ams3.digitaloceanspaces.com/Dusk_Whitepaper_2024_4db72f92a1.pdf) and the papers listed in [Additional Resources](/learn/deep-dive/additional-resources). + +## Primitives used in Dusk ![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. +At the foundation of Dusk’s architecture are primitives like **BLS12-381**, **JubJub**, **Schnorr**, and **Poseidon**. Dusk also uses Merkle tree constructions and a PLONK-based proving stack. -### BLS12_381 +### 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. +BLS12-381 is a pairing-friendly elliptic curve used in many modern proof systems. In Dusk it appears as part of the zero-knowledge and signature stack. ### 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. +JubJub is an elliptic curve that’s efficient in SNARK-friendly settings and is commonly used in privacy-preserving designs. ### 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. +Schnorr signatures are a signature scheme used for authentication and integrity. In Dusk they are part of the foundation for signing and verifying protocol actions. ### 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. +Poseidon is a hash function designed to be efficient inside zero-knowledge circuits. It is commonly used for commitments and Merkle tree hashing in ZK applications. -### Dusk-Merkle +### 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 +Dusk includes a sparse Merkle tree implementation (`dusk-merkle`). Merkle trees enable efficient membership proofs over large datasets and show up throughout blockchain systems. -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. +### PLONK -With PLONK, developers can define custom and reusable circuits that can be integrated into Dusk based smart contracts. +PLONK is a proving system used to build zero-knowledge proofs. In Dusk it underpins privacy-preserving transactions and protocols that require succinct, verifiable computation. -If you want the full cryptographic details and formal security arguments, -refer to the [Dusk whitepaper](https://dusk-cms.ams3.digitaloceanspaces.com/Dusk_Whitepaper_2024_4db72f92a1.pdf) and the papers listed in -[Additional Resources](/learn/deep-dive/additional-resources). +With PLONK, developers can define reusable circuits and generate proofs that can be verified on-chain. diff --git a/src/content/docs/learn/deep-dive/economic-protocol.md b/src/content/docs/learn/deep-dive/economic-protocol.md deleted file mode 100644 index c383c302..00000000 --- a/src/content/docs/learn/deep-dive/economic-protocol.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Economic Protocol -desccription: Learn about the economic protocol that underpins Dusk’s protocol incentives. ---- - -The Dusk's **economic protocol** represents a transformative approach to the utilization and functionality of smart contracts in blockchain technology. This document provides a comprehensive overview of the protocol's features, their implications, and the opportunities they present for developers, enterprises, and users in the blockchain ecosystem. - -:::note -The formal description of the economic protocol can be found in [this link](https://dusk-network.github.io/dusk-protocol/economic-protocol.pdf). -::: - -## Key Features - -The economic protocol enriches smart contracts on the Dusk with three innovative capabilities: - -1. **The protocol (transfer contract) arbitrates smart contracts payments:** this feature enables smart contracts to function as revenue-generating tools, allowing developers to monetize their services. From a technical perspective, defining economic capabilities at protocol level has the benefit of standardizing payments across the whole Dusk ecosystem, allowing for financial composability beyond the applicative one. An immediate benefit of this is the capability in the future to perform payments in differently denominated tokens (such as stablecoin) while the gas remains denominated in `DUSK` - -2. **Smart contracts can choose to pay gas fees:** by shifting the responsibility of gas fees from users to smart contracts, the protocol facilitates a more user-friendly experience, enhancing the mainstream appeal and adoption of blockchain technology. - -3. **Developers can deploy _autocontracts_ : smart contracts that execute autonomously in response to an event:** smart contracts gain the ability to execute functions autonomously based on events emitted by other smart contracts. This is unprecedented in the blockchain world and can unlock advanced trading strategies, automated asset transfers, and optimized business processes. - -## Impact and Benefits - -The introduction of these capabilities significantly alters the landscape for blockchain development and user interaction. Key impacts include: - -- **Improved developer flexibility:** greater creative freedom in designing business models on the blockchain. -- **Enhanced user experience:** lower barriers to entry for non-blockchain-savvy users, fostering mainstream adoption. -- **Economic efficiency:** potential for cost savings and automated operations for businesses and developers. - -## Comparing Traditional vs. Dusk Smart Contracts - -| Feature | Traditional Smart Contracts | Dusk Smart Contracts | -|:---------:|:-----------------------------:|:------------------------------:| -| Fee mechanisms | Limited to transaction taxes | Can implement subscription fees | -| Gas payment | User responsibility | Smart contract responsibility | -| Autonomy | Limited function execution | Advanced autocontract capabilities | - -The economic protocol paves the way for a seamless integration of traditional finance and blockchain technology, while also unlocking a plethora of new use cases and business models. The implementation of these features is not just an advancement but a necessity for the future of blockchain technology and its mass adoption. diff --git a/src/content/docs/learn/glossary.md b/src/content/docs/learn/glossary.md index db06d387..71abfcc0 100644 --- a/src/content/docs/learn/glossary.md +++ b/src/content/docs/learn/glossary.md @@ -1,504 +1,116 @@ --- title: Glossary -description: A detailed glossary of terms specific to Dusk and general definitions. +description: Dusk-specific terms and concepts used across the docs. --- ## Dusk terminology #### Account -Accounts in Dusk manage transactions with different visibility levels. An account is linked to a profile and categorized as either a [Shielded Account](#shielded-account) for privacy-preserving transactions or a [Public Account](#public-account) for transparent transactions. Each account type has its own unique address format. +Accounts in Dusk manage transactions with different visibility levels. An account is linked to a profile and categorized as either a [Shielded Account](#shielded-account) (privacy-preserving) or a [Public Account](#public-account) (transparent). #### Archive Node -An [Archive node](/operator/archive-node) is a Dusk node that preserves a complete historical record of the Dusk blockchain, and does not participate in consensus. +An [archive node](/operator/archive-node) stores the full historical record of the Dusk blockchain and does not participate in consensus. #### Citadel -[Citadel](/developer/digital-identity/protocol) is a self-sovereign identity system that is part of the Dusk protocol. +[Citadel](/developer/digital-identity/protocol) is Dusk's identity and access layer (selective disclosure). #### Confidential Security Contract Standard (XSC) -A standardized framework for confidential smart contracts, which any company or organization can customize according to business-specific requirements (e.g., complying with data privacy and financial regulations). +A standard for confidential smart contracts that can be adapted to business requirements (for example, privacy constraints and compliance rules). #### DUSK -The native cryptocurrency of Dusk. It is used to pay for transaction fees and staking. +The native token of Dusk. It is used to pay for transaction fees (gas) and staking. -#### Dusk EVM +#### DuskDS -[Dusk EVM](/learn/deep-dive/dusk-evm) is a EVM execution environment, that uses DuskDS as settlement and data availability layer. +DuskDS is the settlement layer of the Dusk architecture: consensus, data availability, settlement, and the native transaction models. -#### Dusk VM +#### DuskEVM -[Dusk VM](/learn/deep-dive/dusk-vm) is general purpose virtual machine developed by Dusk that runs WASM smart contracts and manages their memory. +[DuskEVM](/learn/deep-dive/dusk-evm) is an EVM execution environment that uses DuskDS as its settlement and data availability layer. + +#### DuskVM + +[DuskVM](/learn/deep-dive/dusk-vm) is a WASM execution environment for Dusk-native smart contracts. #### Hedger -Hedger is the evolution of Zedger, built on DuskEVM and powered by fully homomorphic encryption for enhanced privacy. -#### Hyperstaking +Hedger is the evolution of Zedger, built on DuskEVM. -Hyperstaking is stake abstraction: a feature that lets smart contracts participate in staking and manage staking rewards with on-chain logic. +#### Stake Abstraction (Hyperstaking) -It enables use cases like staking pools, delegated staking services, and other programmable staking patterns. See: [Stake Abstraction](/learn/hyperstaking). +Stake abstraction (also called hyperstaking) lets smart contracts participate in staking and manage rewards with on-chain logic. + +See: [Stake Abstraction](/learn/hyperstaking). #### Kadcast -[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. +[Kadcast](/learn/core-components#network-layer-kadcast) is Dusk's P2P networking layer. #### LUX -The smallest denomination of DUSK. 10^9 LUX = 1 DUSK, 1 DUSK = 1,000,000,000 LUX. +The smallest denomination of DUSK. + +- `1 DUSK = 1,000,000,000 LUX` #### Moonlight -[Moonlight](/learn/deep-dive/duskds-tx-models) 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/duskds-tx-models) is Dusk's public, account-based transaction model. #### Phoenix -[Phoenix](/learn/deep-dive/duskds-tx-models) 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/duskds-tx-models) is Dusk's shielded, UTXO-based transaction model. -#### Public Account +#### Profile -A public account is based on the [Moonlight](#moonlight) account-based transaction model and is used for transparent, public transactions. It uses public addresses to provide full transparency. +A profile is a pairing of a Moonlight (public) account and a Phoenix (shielded) account derived from a single mnemonic. -#### Shielded Account +Wallets use profiles so you can manage both models side-by-side while keeping keys and addresses organized. -A shielded account is based on the [Phoenix](#phoenix) UTXO transaction model and is designed for privacy-preserving transactions. It utilizes shielded addresses for confidentiality while supporting regulatory compliance by making the sender known to the receiver. +![Wallet hierarchy](../../../assets/wallet_hierarchy.png) -#### Profile +#### Provisioner -A profile is a pairing of a [Moonlight](#moonlight) (public) account and a [Phoenix](#phoenix) (shielded) account derived from a single mnemonic. +A provisioner is a staker running a node that can be selected for consensus duties (block generation and committee slots). -Wallets use profiles so you can manage both transaction models side-by-side, while keeping keys and addresses organized. +See: [Run a provisioner node](/operator/provisioner). -![Wallet hierarchy](../../../assets/wallet_hierarchy.png) +#### Public Account + +A public account uses Moonlight and is designed for transparent transactions. It uses public addresses. #### RUES -The Rusk Universal Event System (RUES) is an integral part of the architecture of Dusk, providing an events system that allows real-time communication and event subscriptions. +RUES (Rusk Universal Event System) is the event system used to stream chain events to external consumers. #### Rusk -[Rusk](/learn/core-components#rusk) is the official Dusk platform's Rust reference implementation. +[Rusk](/learn/core-components#rusk) is the Rust node implementation of DuskDS. #### Rusk Wallet -The official CLI wallet for Dusk, enabling users to manage DUSK, interact with the blockchain and execute transactions via a command-line interface. +The [Rusk Wallet](/learn/rusk-wallet) is the official CLI wallet for Dusk. + +#### Shielded Account + +A shielded account uses Phoenix and is designed for privacy-preserving transactions. #### Succinct Attestation -Succinct Attestation is a unique Proof-of-Stake consensus algorithm developed by Dusk which allows network participants to compete for block producer rights. +Succinct Attestation is Dusk's proof-of-stake consensus protocol. #### W3sper SDK -[W3sper](/developer/integrations/w3sper) is a JavaScript library for communication within the Dusk ecosystem, enabling developers to integrate Dusk dApps into (web) applications. +[W3sper](/developer/integrations/w3sper) is a JavaScript library for integrating with the Dusk ecosystem. #### Web Wallet -The [Web Wallet](https://apps.dusk.network/wallet/) is the official web-based wallet for Dusk, providing users with an accessible way to manage DUSK and interact with the blockchain through a user-friendly interface. +The [Web Wallet](/learn/web-wallet) is the official browser-based wallet for Dusk. #### Zedger -[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 - -#### Account - -In an account-based blockchain, a combination of a private key and a public key where a user's funds are stored as a balance. - -#### Account-Based Transaction Model - -A protocol that represents assets as balances within personal accounts, similar to bank accounts. - -#### Address - -A unique blockchain identifier derived from an account’s public key. - -#### Application Program Interface (API) - -Software code that enables communication between different systems via request-response messages. It enables tasks like requesting user balances, listening to on-chain events and more. - -#### Archive node - -A type of full node in blockchain networks that stores the entire history of the blockchain, including all past states, transactions, and emitted events since the genesis block. Archive nodes enable deep historical data retrieval, supporting use cases like blockchain explorers, audits, and regulatory compliance. - -#### Asset Token - -A category of tokens that represent a “real world” asset or product — such as a commodity (e.g., gold) or currency (e.g., US dollar) — as opposed to utility tokens, which provide network-specific functions. - -#### Balance - -The assets owned by an account in an account-based transaction model, available for exchange or spending. - -#### Bandwidth - -The maximum amount of data that can be transmitted across a path in a fixed period of time. - -#### BLS Digital Signature - -A digital signature that uses elliptic curves to encrypt the public key and private key of the parties involved in order to permit people to sign transactions on the blockchain without revealing any data. - -#### Block - -Files in which data of the network is permanently recorded. A block permanently stores records of transactions which, once written, cannot be altered or removed. Every time a block is completed, a new block is formed in the blockchain. - -#### Block Explorer - -A web tool for searching blockchain information, such as block creation dates, sizes, gas fees, and transaction details. - -#### Block Header - -Metadata in each block summarizing its content, including the previous block's hash, blockheight, timestamp and nonce. - -#### Block Height - -The number of blocks preceding a given block, starting from the genesis block, which has a height of zero. - -#### Block Generator - -A provisioner elected by the network to produce a new block in exchange for a reward in DUSK. - -#### Block Reward - -An amount of tokens awarded by the network to eligible stakers for each block they create successfully or vote cast when eligible to do so. - -#### Block Time - -The duration it takes to create a new block in the blockchain. - -#### Brute Force Attack (BFA) - -A method where hackers attempt to guess a private key through repeated attempts until successful. - -#### Coinbase - -A reward mechanism that mints new tokens for validators, incentivizing them to secure the network, especially during its early stages. - -#### Confidential Smart Contract - -A smart contract which permits the creation of confidential or private transactions. - -#### Confirmation - -The process by which validators verify and accept blocks on the blockchain, adding them to the chain. - -#### Consensus - -A process where the majority of validators agree on the current state of the blockchain. - -#### Cryptographic Hash Function - -A special class of hash function that has certain properties in order to make it secure and ideal for cryptographic purposes, including the following: (i) it is deterministic, meaning it always produces the same result; (ii) it is fast, meaning it returns the hash of an input very quickly; (iii) it is pre-image resistant, meaning it is virtually impossible to determine the original input data from its hash value; and (iv) even a small change in the input data would result in a massive change to the hash value. - -#### Decentralized - -A system where functions and authority are distributed among peers rather than concentrated in a central entity. - -#### Decentralized Application - -A digital program running on a decentralized network, utilizing smart contracts to interact with the blockchain and enforce agreements. - -#### DeMI -The term Decentralized Market Infrastructure (DeMI) refers to leveraging Distributed Ledger Technologies (DLTs) to create a protocol-based Financial Market Infrastructure, as opposed to traditional platform-based systems like Central Securities Depositories (CSDs). DeMI enhances the efficiency and reduces the costs of regulated financial markets. - -#### Devnet - -An experimental network used by blockchain developers and users, where tokens have no real monetary value. - -#### Digital Signature - -A tool used to sign transactions on the blockchain that verifies the identity of the signer or sender. Each signer uses a private key to produce a unique ‘digital signature’ that can only be decrypted by the signer’s public key — which the signer shares with the receiver. - -#### Double Spend (Attack) - -An attack on the network in which a person attempts to spend the same tokens multiple times. - -#### Elliptic Curve Cryptography - -Cryptographic methods that use an elliptic curve to encrypt data. An example of elliptic curve cryptography is the BLS digital signature. - -#### Elliptic Curve - -A mathematical function whereby any point on the curve can be mirrored over the x-axis and the curve remains the same. - -#### Epoch - -A specific period of time used to mark specific events within the network, such as the creation and addition of new blocks to the blockchain. - -#### Faucet - -A reward system in the form of a website or app that distributes tokens in exchange for the completion of certain tasks. - -#### Fault Tolerance - -The capacity of the network to operate as intended even if certain components fail. - -#### Finality - -A metric to measure the amount of time (required to finalize N new blocks) a person must wait for a guarantee that the executed transaction will not be reversed or changed. - -#### Fork - -The event whereby a blockchain splits into two branches. - -#### Fork Resistance - -The impossibility of the blockchain to be forked as a consequence of same-block finality. - -#### Gas - -The fee charged to a user in order to run a smart contract on the blockchain. - -#### Genesis Block - -The first block of a blockchain, from which all subsequent blocks are built. It is unique and hardcoded into the protocol. - -#### Genesis Contract - -A smart contract that is made available on the start of the blockchain, and hardcoded into the genesis block. - -#### Hash - -The fixed-size output of a hash function used to index, retrieve or verify data more efficiently than the original input. - -#### Hash Function - -A function that can be used to reduce a string of data to a hash. - -#### Incentive Mechanism - -A method used to reward people for conducting certain activities within the network. - -#### Incentivized Testnet (ITN) - -A testnet whereby developers are rewarded to perform specific tasks that stress new code, features, or infrastructure components in order to test network performance and stability, as well as the behavior of validators. - -#### Information Propagation Protocol (IPP) - -A software protocol used to distribute information across a (P2P) network. Information propagation protocols can be (i) structured (e.g., Kadcast), meaning the network communicates transactions and new blocks according to a pre-defined mechanism, or (ii) unstructured (e.g., Gossip), meaning the network communicates transactions and new blocks in a random manner. - -#### Latency - -The time it takes for data to go from one node to another. - -#### Mainnet - -The primary blockchain network instance where transactions have real monetary value. - -#### Mempool - -A portmanteau of “memory” and “pool”. A mempool is a buffer between the creation of blocks. As a new block is created, new transactions are created, stored, and validated in the mempool before being propagated to the network. - -#### Merkle Tree - -A data structure that results from the repeated application of a hash function to blocks of data until there is a single hash representing the entire data set. - -#### Markets in Crypto-Assets Regulation (MiCA) - -A proposed regulation by the European Commission that could profoundly impact cryptocurrency activity in the EU. As drafted, it would impact any cryptocurrency not issued by a governmental entity and especially stablecoins. - -#### Markets in Financial Instruments Directive (MiFID II) - -An instituted legislative framework by the European Commission to regulate financial markets in the EU. It regulates virtually every asset and profession within the EU financial service industry. - -#### Mnemonic - -A series of words that derive all cryptographic keys for a wallet. - -#### Node - -A computer connected to the network that maintains a copy of the blockchain. - -#### Note - -In a UTXO model, a public object where assets are stored, requiring a private key to access and spend. - -#### Permissioned - -A network that uses a layer of access control to dictate the actions that may be taken by the node users of such blockchain. - -#### Permissionless - -A network where users can interact without needing permission from any central authority. - -#### Peer - -A user interacting with others within the network. - -#### Peer to Peer (P2P) - -The direct transfer of assets or data between individuals without intermediaries. - -#### Peer to Peer (P2P) Protocol - -A decentralized network model where users exchange resources directly without a centralized server. - -#### PLONK - -A widely-used zk-SNARK protocol that enables privacy-focused blockchain applications. - -#### PLOOKup - -A function combining PLONK and lookup tables to reduce costs of zk-SNARK operations. - -#### PLONKup - -An optimized implementation of PLONK that generates zero-knowledge proofs faster for certain use-cases without additional gas costs. - -#### Poseidon - -A fast, zero-knowledge friendly cryptographic hash function. - -#### Prover - -A prover is an entity that is responsible for generating zero-knowledge proofs. The proof is used to verify certain statements, without revealing the underlying data. - -#### Provisioner - -A network participant staking at least 1,000 DUSK who competes to join the provisioner committee. - -#### Provisioner Committee - -A group of provisioners tasked with selecting and proposing new blocks for the blockchain. - -#### Consensus Key - -A unique sequence of alphanumeric characters used by a node participating in consensus (such as a provisioner) to actively sign on-chain attestations and proposals of new blocks. - -#### Private Key - -A unique sequence of alphanumeric characters used to derive its associated public key. - -#### Public Key - -A unique identifier of alphanumeric characters that is used to sign data. A public key can also be used to verify digital signatures made with a private key. - -#### Reference String - -A string of data that ZK-SNARKs use to create zero-knowledge proof. - -#### Regulated Finance (RegFi) - -The centralized banking system whereby financial instruments are regulated by laws and FIAT currencies represent monetary value. Examples of regulated financial instruments are equity securities such as stocks, debt securities such as bonds, or derivative instruments such as futures and options contracts. - -#### Regulated Decentralized Finance (RegDeFi) - -A hybrid model combining RegFi and DeFi whereby people have access to regulated financial instruments in the form of security tokens on a decentralized or P2P network. - -#### Reinforced Concrete - -A zero-knowledge friendly hash function developed by Dusk designed to work with PLONKup for processing zero-knowledge operations. - -#### Remote Procedure Call (RPC) - -A communication protocol allowing a program to request services from another program on a different networked computer. - -#### Same-Block Finality - -The guarantee that a transaction, once executed, will never be reversed or altered within the same block. - -#### Security - -A financial instrument that is tradeable and holds monetary value. Examples of securities include equity stocks, bonds, and options. - -#### Security Token - -A token structured as a security, representing an underlying asset and potentially offering dividends, profit-sharing, or interest. - -#### Self-Custody - -When assets are held in custody by the owner, rather than by an intermediary such as a bank or exchange. - -#### Settlement Finality - -A feature of the succinct attestation consensus algorithm whereby completed transactions are final and irreversible immediately after being processed. With regards to regulatory compliance, settlement finality is a vital requirement for the issuance of security tokens. - -#### Slashing - -A form of punishment whereby staking funds of provisioners and block generators who aren't performing specific duties (e.g., being online) are partially or entirely removed from the stake. - -#### Smart Contract - -An immutable contract that follows pre-defined rules to self-execute agreed-upon obligations automatically and without the involvement of third parties. - -#### Spent Transaction Output (UTXO) - -Output or funds spent in a transaction that can no longer be used as input in a new transaction. - -#### Staking - -Earning rewards by locking tokens in a staking contract to help verify transactions and participate in the consensus mechanism. - -#### (Global) State - -Data representing the current condition of the blockchain, used to validate transactions (e.g., UTXOs, balances). - -#### Sybil Attack - -An attack where a single actor attempts to take over the network by using a large number of accounts, computers, or nodes. - -#### Testnet - -An environment for testing new code, features, or infrastructure, focusing on performance, stability, and validator behavior. - -#### Tokenization - -The process whereby traditional Assets (such as securities) are digitized into tradeable, blockchain-based tokens that represent whole or fractionalized ownership of the underlying asset. - -#### Trusted Setup - -The initial event where a reference string for ZK-SNARKs is created by trusted parties. - -#### Trustless - -A network where users can interact without needing to trust the counterparty. - -#### Unspent Transaction Output (UTXO) - -Output or leftover change from a transaction that can be used as input in a new transaction. - -#### Utility Token - -A token designed for consumer use on a platform, not intended as a security. - -#### UTXO Transaction Model - -An accounting system where assets are represented as spent or unspent transaction outputs stored in encrypted public notes. - -#### Verifiable Computation - -Outsourcing computational tasks to a third-party while ensuring the results are verifiable. - -#### Verifier - -The entity that checks and validates zero-knowledge proofs generated by a prover. - -#### Virtual Machine (VM) - -A simulated environment that executes smart contracts and performs computations on the blockchain. - -#### Wallet - -A software application that enables users to access and manage digital assets on the blockchain. - -#### WASM - -WebAssembly (WASM) is a binary instruction format that enables efficient and secure execution of smart contracts on the blockchain. - -#### Zero-Knowledge Friendly Hash Function - -A cryptographic hash function optimized to process the complex data types associated with zero-knowledge operations. - -#### Zero-Knowledge Proof - -A cryptographic method used to verify the validity of given data without revealing the contents of the data in question and to permit users to send confidential transactions within the network. - -#### ZK-SNARKs - -A subset of zero-knowledge proofs that (i) generate proof which is succinct or small and constant in size (kB), (ii) need a trusted setup, and (iii) use elliptic curve cryptography. An example of zk-SNARKs is Plonk. - -#### ZK-STARK - -A subset of zero-knowledge proofs that (i) generate a proof which is rather large and not-constant in size (kB), (ii) don’t require a trusted setup, and (iii) use hash functions with respect to cryptography. +[Zedger](/learn/core-components#zedger--hedger) is a protocol for private, compliant issuance and management of regulated assets. diff --git a/src/content/docs/learn/guides/bep20-bridge.md b/src/content/docs/learn/guides/bep20-bridge.md index b9f4b055..9f595a03 100644 --- a/src/content/docs/learn/guides/bep20-bridge.md +++ b/src/content/docs/learn/guides/bep20-bridge.md @@ -3,15 +3,35 @@ title: Native DUSK to BEP20 Bridge description: How to bridge your native DUSK tokens to BEP20 DUSK on Binance Smart Chain. --- -This guide explains how to bridge your **native DUSK** tokens to **BEP20 DUSK** on Binance Smart Chain (BSC). This operation is handled through the official **BEP20 bridge** and facilitated via the [Dusk Web Wallet](https://apps.dusk.network/wallet/). +This guide explains how to bridge **native DUSK** (Dusk mainnet) to **BEP20 DUSK** on Binance Smart Chain (BSC) using the [Web Wallet](https://apps.dusk.network/wallet/). When bridging, your native DUSK tokens are locked on the Dusk network. Once locked, a mint operation is initiated on Binance Smart Chain, issuing an equivalent amount of BEP20 DUSK to your specified address. The full bridging process typically completes within 15 minutes. -:::note[Note] +:::note Want to **bridge from BEP20 DUSK to native DUSK** instead? Check our [Migration Guide](/learn/guides/mainnet-migration/) for the complete walkthrough. ::: -## Bridging Steps +## Who this is for + +- You have **native DUSK** on Dusk mainnet. +- You want **BEP20 DUSK** in an EVM wallet on BSC. + +## What you need + +- Access to the [Web Wallet](https://apps.dusk.network/wallet/). +- Enough native DUSK to cover the amount you want to bridge **plus** the bridge fee. +- A **BSC EVM address** (starts with `0x...`) where you want to receive BEP20 DUSK. + +:::caution +The BSC address is provided in the **memo** field. If you omit the memo or provide an invalid address, the bridge will not know where to mint, and funds can be lost. +::: + +## Expected time and fees + +- **Time**: typically ~15 minutes. +- **Fees**: the bridge charges a flat **1 DUSK** fee per transaction (your minted amount is `sent - 1 DUSK`). + +## Steps 1. Open the [Web Wallet](https://apps.dusk.network/wallet/). 2. Open or import your native Dusk wallet. @@ -42,3 +62,9 @@ No. This bridge only supports native DUSK to **BEP20 DUSK** on Binance Smart Cha **Is there a fee?** Yes, the bridge charges a flat fee of 1 DUSK per transaction. Your bridged amount will be **original amount - 1 DUSK**. + +## Troubleshooting + +- **Nothing arrived on BSC after ~15 minutes**: confirm your Dusk transfer succeeded and double-check the memo contains the correct `0x...` address. +- **I used the wrong memo address**: the bridge can’t mint to an unknown target. This is usually not reversible. +- **I bridged to an exchange address**: only do this if the exchange explicitly supports BEP20 DUSK deposits and you’re sure the memo address is correct. diff --git a/src/content/docs/learn/guides/duskevm-bridge.md b/src/content/docs/learn/guides/duskevm-bridge.md index 44150ba9..b89b4109 100644 --- a/src/content/docs/learn/guides/duskevm-bridge.md +++ b/src/content/docs/learn/guides/duskevm-bridge.md @@ -3,11 +3,11 @@ title: Bridge DUSK from DuskDS to DuskEVM Testnet description: How to use the Dusk Web Wallet to move DUSK from the DuskDS testnet to the DuskEVM testnet and interact with the EVM network. --- -Bridge testnet DUSK from DuskDS to DuskEVM using the official Dusk Web Wallet. Once bridged, DUSK is the native gas token on DuskEVM Testnet. +Bridge testnet DUSK (nDUSK) from DuskDS to DuskEVM using the official Dusk Web Wallet. Once bridged, DUSK is the native gas token on DuskEVM Testnet. ## Fast path -1. Get testnet DUSK in the Web Wallet and **unshield** the amount you want to bridge. See: [How to get testnet tokens](/operator/networks#how-to-get-testnet-tokens). +1. Get testnet DUSK (nDUSK) in the Web Wallet and **unshield** the amount you want to bridge. See: [How to get testnet tokens](/operator/networks#how-to-get-testnet-tokens). 2. Open the Web Wallet (testnet): [apps.testnet.dusk.network/wallet](https://apps.testnet.dusk.network/wallet/) 3. Go to `Dashboard -> Bridge` and connect your Web3 wallet (approve adding/switching to DuskEVM when prompted). 4. Set **From: DuskDS** and **To: DuskEVM**, enter an amount, and send. @@ -17,7 +17,7 @@ Bridge testnet DUSK from DuskDS to DuskEVM using the official Dusk Web Wallet. O ## 1) Prerequisites -- A Dusk Web Wallet account with some **testnet DUSK** (and the amount you want to bridge **unshielded**). See: [How to get testnet tokens](/operator/networks#how-to-get-testnet-tokens). +- A Dusk Web Wallet account with some **testnet DUSK (nDUSK)** (and the amount you want to bridge **unshielded**). See: [How to get testnet tokens](/operator/networks#how-to-get-testnet-tokens). - A Web3 wallet (e.g. MetaMask) installed in your browser. - Optional: [DuskEVM deep dive](/learn/deep-dive/dusk-evm/) and [Deploy on DuskEVM](/developer/smart-contracts-dusk-evm/deploy-on-evm/). diff --git a/src/content/docs/learn/guides/legacy.md b/src/content/docs/learn/guides/legacy.md index bae1380d..3bef445c 100644 --- a/src/content/docs/learn/guides/legacy.md +++ b/src/content/docs/learn/guides/legacy.md @@ -5,7 +5,7 @@ description: Legacy programs and guides kept for transparency. These flows are n This page collects legacy programs and guides that are no longer active. -If you’re looking to move ERC20/BEP20 DUSK to native DUSK today, use: [BEP20/ERC20 Migration](/learn/guides/mainnet-migration/). +If you’re looking to move ERC20/BEP20 DUSK to native DUSK today, use: [ERC20/BEP20 Migration](/learn/guides/mainnet-migration/). ## Mainnet Genesis On-Ramp (Ended) @@ -35,4 +35,3 @@ This only applies if you staked ERC20 DUSK via the ITN2 staking portal (pre-main 3. In **Write Contract**, call `withdraw(amount)` with that exact amount. If you need help recovering funds, ask in the Dusk Discord: discord.gg/dusk-official. - diff --git a/src/content/docs/learn/guides/mainnet-migration.md b/src/content/docs/learn/guides/mainnet-migration.md index a63aea44..3723ad47 100644 --- a/src/content/docs/learn/guides/mainnet-migration.md +++ b/src/content/docs/learn/guides/mainnet-migration.md @@ -1,13 +1,33 @@ --- -title: BEP20/ERC20 Migration -description: Detailed instructions for migrating your ERC20/BEP20 DUSK tokens to Dusk mainnet. +title: ERC20/BEP20 Migration +description: Detailed instructions for migrating your ERC20/BEP20 DUSK tokens to Dusk mainnet. --- -This guide provides instructions on how to migrate your BEP20/ERC20 DUSK tokens to native DUSK on the Dusk network. The migration process is facilitated through our [Web Wallet](https://apps.dusk.network/wallet/), allowing you to convert your tokens using WalletConnect-compatible Web3 wallets. +This guide explains how to migrate **ERC20/BEP20 DUSK** (Ethereum/BSC) to **native DUSK** on Dusk mainnet. The migration flow is handled through the [Web Wallet](https://apps.dusk.network/wallet/) and uses WalletConnect to connect your EVM wallet. -The migration process locks your BEP20/ERC20 DUSK tokens in a smart contract on Ethereum or Binance Smart Chain. Once locked, an event is emitted, and native DUSK is issued to your Dusk mainnet wallet. The entire process typically takes around 15 minutes. +The migration process locks your ERC20/BEP20 DUSK in a smart contract on Ethereum or Binance Smart Chain. Once locked, an event is emitted and native DUSK is issued to your Dusk wallet. The entire process typically takes around 15 minutes. -## Migration Steps +:::note +Want to bridge **native DUSK to BEP20 DUSK** on BSC instead? See: [Native DUSK to BEP20 Bridge](/learn/guides/bep20-bridge). +::: + +## Who this is for + +- You hold DUSK on Ethereum (ERC20) or Binance Smart Chain (BEP20). +- You want to use that DUSK on Dusk mainnet (native DUSK). + +## What you need + +- A Dusk wallet (in the Web Wallet) where you want to receive native DUSK. +- An EVM wallet holding ERC20/BEP20 DUSK that supports WalletConnect. +- ETH or BNB to pay the Ethereum/BSC transaction fee for the lock transaction. + +## Expected time and fees + +- **Time**: typically ~15 minutes once your Ethereum/BSC transaction is confirmed. +- **Fees**: you pay the normal Ethereum/BSC network fee to submit the lock transaction. + +## Steps 1. Access the [Web Wallet](https://apps.dusk.network/wallet/). 2. Import an existing wallet or create a new one. @@ -34,6 +54,13 @@ Yes, the minimum migration amount is 1 LUX, which is equivalent to 1000000000 DU **What happens if I migrate smaller fractions?** If you attempt to migrate an amount of DUSK that is not a clean multiple of 1 LUX (1000000000 DUSK wei), the migration contract will round down the amount. For example: -If you migrate 1234567890 DUSK in wei (BEP20/ERC20), the contract will round it down to 1000000000 DUSK in wei, which is exactly 1 LUX in native DUSK. +If you migrate 1234567890 DUSK in wei (ERC20/BEP20), the contract will round it down to 1000000000 DUSK in wei, which is exactly 1 LUX in native DUSK. + +This rounding behavior ensures that only full LUX amounts are migrated to native DUSK, as native DUSK uses 9 decimals while ERC20/BEP20 DUSK uses 18 decimals. + +## Troubleshooting -This rounding behavior ensures that only full LUX amounts are migrated to native DUSK, as native DUSK uses 9 decimals while BEP20/ERC20 DUSK uses 18 decimals. +- **My migration transaction is pending or failed**: check it in your EVM wallet and ensure you have enough ETH/BNB for gas. +- **I don’t see native DUSK after ~15 minutes**: confirm the Ethereum/BSC lock transaction is successful and give it a bit more time during congestion. +- **My migrated amount is smaller than expected**: amounts are rounded down to full `LUX` (see above). +- **I’m trying to migrate from an exchange**: exchanges usually can’t connect via WalletConnect. Withdraw your DUSK to a self-custody wallet first. diff --git a/src/content/docs/learn/guides/staking-basics.md b/src/content/docs/learn/guides/staking-basics.md index 706b1bd5..9c070fe7 100644 --- a/src/content/docs/learn/guides/staking-basics.md +++ b/src/content/docs/learn/guides/staking-basics.md @@ -1,95 +1,84 @@ --- title: Staking on Dusk -description: Discover how to earn rewards by staking on Dusk. +description: How staking works on Dusk, what you need, and what to expect from rewards and maturity. --- -Staking is a vital component of Dusk, ensuring decentralization and security. -By staking your DUSK, you contribute to the network's integrity and consensus mechanism, enabling efficient and secure transaction validation. Staking is a way for everyone to actively support the network while earning rewards for their participation. +Staking is how Dusk selects provisioners (validator nodes) to propose and validate blocks. +Stakers earn rewards funded by token emissions and transaction fees. -## Why Stake? +## Why stake? Staking DUSK allows you to: -- Earn rewards and grow your holdings. -- Participate in consensus and increase the security of Dusk. +- Earn staking rewards. +- Help secure the network by participating in consensus. -## What do you need to start? -To begin staking, you need: +## Two ways to stake -- At least **1000 DUSK**: this is the minimum amount required to participate. -- A **running and fully-synced node**: you can learn how to run a node [here](/operator/provisioner/) -- **Time for maturity**: your stake becomes active after 2 epochs (about **4320 blocks**). +### 1) Direct staking (run a provisioner) +To earn protocol staking rewards directly, you run a provisioner node 24/7 and stake from its wallet. -:::note[Important] -After having staked your tokens, **it takes some time before you start earning rewards**. This is because your stake becomes active after the maturity period (4320 blocks). The maturity period of 4320 blocks corresponds to **approximately 12 hours** (based on an average block time of 10 seconds). Before expecting rewards, ensure to account for this waiting period. -::: +- Run a node: [Provisioner node](/operator/provisioner) +- Set up wallet + stake: [Wallet setup](/operator/guides/node-wallet-setup) -## How are Rewards determined? +### 2) Staking pools (no infrastructure) -Rewards are probabilistically allocated based on your node's participation in the network's consensus process. +Some third-party services and on-chain pools stake on behalf of users. This can let you earn staking yield without running your own node, but it adds operator and smart contract risk. -**Once** your stake is active, you start earn rewards, which come from: +- If you're building a pool as a smart contract developer, see: [Stake Abstraction](/learn/hyperstaking) +- If you're a user, follow the pool/provider's instructions and do your own due diligence. -- Your node proposing a block. -- Your node voting on a block. -- Token emissions as outlined in the [tokenomics](/learn/tokenomics#token-emission) page. +## Requirements and timing -Your **rewards depend on the size of your stake relative to the total network stake**. Larger stakes increase your likelihood of being selected to propose or validate blocks, leading to more frequent rewards. Conversely, smaller stakes may experience longer intervals between rewards. +- **Minimum stake**: 1,000 DUSK +- **Maturity**: 2 epochs (4,320 blocks), about 12 hours before rewards start +- **Unstaking**: no penalties or waiting period :::note[Important] -The more DUSK you stake, the more likely you are to earn rewards as an active participant in the network. +New stake only starts earning rewards after the maturity period. +Operators can verify the `stake active from block` value using `rusk-wallet stake-info`. ::: -## Slashing - -Dusk uses a [slashing mechanism](/learn/tokenomics#slashing) to maintain network security. If your node submits invalid blocks or goes offline, your stake may be partially reduced. This mechanism ensures the network rewards reliable participants and discourages harmful behavior. +## How are rewards determined? -:::note[Important] -To prevent slashing, ensure your node is operational and synced before staking. -::: +Once your stake is active, rewards are probabilistic and depend on consensus participation and the size of your stake relative to the total active network stake. -## Re-stake Rewards & Increase Stake -You can increase your stake at any time without needing to unstake first. When you do, **90% of the added amount becomes active immediately** and begins accruing rewards, while the remaining **10% is moved to your inactive stake**. However, if your stake is not active yet, no penalties are applied, and the full added amount will be available as soon as the original stake becomes eligible. +For reward sources and distribution details, see: -The inactive portion does not generate rewards and remains locked. It can only be accessed by **fully unstaking** your holdings. Withdrawn rewards are available immediately and can be restaked if you choose. Any new staked amount is directly eligible (without the need of waiting for the maturity period), except for the 10% inactive portion (which will never become eligible). +- [Incentives](/learn/tokenomics#incentives) +- [Token emission](/learn/tokenomics#token-emission) -:::note[Important] -When you increase your stake, keep in mind that: -- **90%** is added to your active stake and starts earning rewards. -- **10%** goes to your inactive stake, accessible only if you **fully** unstake. -- This applies only if the stake is **already** eligible. -::: - -This mechanism promotes fairness and prevents potential exploitation of compounding effects, ensuring a balanced staking system. - -### Example -As an example, suppose you initially stake 5,000 DUSK. After 2 epochs (4320 blocks), your stake becomes active. +## Slashing -Some time passes, and you decide to add 4,000 DUSK to your stake: +Dusk uses **soft slashing**: stake is not burned, but repeated faults or long downtime can suspend rewards and reduce effective stake. -- 90% of the newly added amount (3,600 DUSK) is immediately added to your active stake. -- 10% of the newly added amount (400 DUSK) is moved to your inactive stake. +See: [Slashing](/learn/tokenomics#slashing). -At this point: +## Adding to an existing stake -- Your active stake becomes 8,600 DUSK (5,000 + 3,600). -- Your inactive stake holds 400 DUSK. +You can add to your stake without fully unstaking first. -If you later withdraw 8,000 DUSK, leaving 600 DUSK staked: +- If your stake is already active, **90%** of the additional amount becomes active immediately and starts earning rewards. The remaining **10%** becomes **inactive stake**. +- Inactive stake does not earn rewards and can only be unlocked by fully unstaking. +- If you add stake before the original stake becomes active (still in the maturity period), the top-up follows normal maturity and is not subject to the 90%/10% split. -- You immediately have 8,000 DUSK, fully liquid. -- Your active stake is now 600 DUSK. -- Your inactive stake remains 400 DUSK. +
+Example -If you then fully unstake the remaining 600 DUSK, the 400 DUSK in your inactive stake is unlocked and becomes available. +Suppose you stake **5,000 DUSK**. After the maturity period, your stake becomes active. +If you later add **4,000 DUSK**: +- **3,600 DUSK (90%)** becomes active immediately. +- **400 DUSK (10%)** goes to inactive stake. -## Ready to Stake? +If you withdraw down to **600 DUSK** active stake, the **400 DUSK** inactive stake remains locked until you fully unstake the remaining active stake. -Staking is a great way to earn rewards and participate in Dusk’s ecosystem. +
-Staking not only benefits you through rewards but also strengthens the Dusk network’s security and decentralization. +## Next steps -Start staking now using the [web wallet](https://apps.dusk.network/wallet/setup/)! +- Direct staking (run your own node): [Provisioner node](/operator/provisioner), then [Wallet setup](/operator/guides/node-wallet-setup) +- Understand rewards and emissions: [Tokenomics](/learn/tokenomics) +- If you hold ERC20/BEP20 DUSK: [Mainnet migration](/learn/guides/mainnet-migration) diff --git a/src/content/docs/learn/hyperstaking.md b/src/content/docs/learn/hyperstaking.md index 651c424a..b7edbfbc 100644 --- a/src/content/docs/learn/hyperstaking.md +++ b/src/content/docs/learn/hyperstaking.md @@ -31,9 +31,9 @@ Contracts can implement arbitrary reward-splitting rules (for example: route a p - The **minimum stake** requirement applies to contracts too: **1,000 DUSK**. - Stake is considered active after a maturity period of **4320 blocks (~12 hours)**. -- Reward distribution depends on consensus participation; see [Staking basics](/learn/guides/staking-basics#how-are-rewards-determined). +- Reward distribution depends on consensus participation; see [Staking on Dusk](/learn/guides/staking-basics#how-are-rewards-determined). -## Technical guide (smart contract developers) {#technical-guide} +## Technical guide (smart contract developers) Stake abstraction requires contracts to interact with the genesis **Stake Contract** (and the **Transfer Contract** for contract-to-contract calls). diff --git a/src/content/docs/learn/overview.mdx b/src/content/docs/learn/overview.mdx index 58323947..4d72c81c 100644 --- a/src/content/docs/learn/overview.mdx +++ b/src/content/docs/learn/overview.mdx @@ -1,35 +1,29 @@ --- title: About Dusk -description: Build regulated, privacy-preserving finance on a purpose-built blockchain. +description: A blockchain for regulated markets that need privacy, compliance controls, and fast settlement. --- -import { LinkCard, Card, CardGrid } from '@astrojs/starlight/components'; +import { LinkCard, CardGrid } from '@astrojs/starlight/components'; -Dusk is the privacy blockchain for regulated finance. +Dusk is a blockchain designed for regulated finance: you can issue, trade, and settle assets on-chain without putting sensitive market data on public display. -It lets you launch and use markets where: +## At a glance -- Institutions can meet real regulatory requirements on‑chain -- Users get confidential balances and transfers instead of full public exposure -- Developers build with familiar EVM tools plus native privacy and compliance primitives +On Dusk you can build markets where: -Dusk combines: - -- Zero‑knowledge technology for confidentiality -- On‑chain compliance for MiCA / MiFID II / DLT Pilot Regime / GDPR‑style regimes -- Succinct Attestation, a PoS consensus protocol for fast, final settlement -- A modular architecture with DuskDS (data & settlement) and DuskEVM (EVM execution) +- **Institutions** can encode eligibility, disclosure, and reporting rules into on-chain workflows. +- **Users** can use confidential balances and transfers (with the ability to reveal information to authorized parties when required). +- **Developers** can ship dApps with familiar EVM tooling while relying on a settlement layer built for privacy and compliance. ## What is Dusk? -Most financial markets still run on opaque, centralized systems. -Dusk is built to move those workflows on‑chain without sacrificing: +Most financial market infrastructure is still a patchwork of closed systems. Public blockchains remove platform risk, but fully transparent execution leaks positions, counterparties, and balances. -- Regulatory compliance -- Counterparty privacy -- Execution speed and finality +Dusk is built to support regulated markets on-chain without forcing a choice between: -On Dusk, institutions can issue and manage financial instruments while enforcing disclosure, KYC/AML, and reporting rules directly in the protocol. +- **Compliance** (KYC/AML checks, eligibility, limits, reporting, disclosure) +- **Privacy** (confidential balances and transfers, selective disclosure) +- **Settlement performance** (fast, deterministic finality) In short: Dusk is a privacy-enabled, regulation-aware blockchain for institutional-grade finance. @@ -37,7 +31,7 @@ In short: Dusk is a privacy-enabled, regulation-aware blockchain for institution ### Built for regulated markets -Dusk is designed around the needs of regulated financial institutions: +Dusk is designed around the needs of regulated financial institutions and venues: - Native support for compliant issuance of securities and RWAs - Identity and permissioning primitives that let you differentiate between public and restricted flows @@ -47,11 +41,11 @@ See: [Core Values](/learn/core-values) and [Tokenization & Native Issuance](/lea ### Privacy by design, transparent when needed -Dusk uses zero‑knowledge proofs and dual transaction models (Phoenix and Moonlight) to let users choose between: +Dusk uses zero‑knowledge proofs and dual transaction models (Phoenix and Moonlight) to let you choose between: -- Public transactions for transparent flows, and -- Shielded transactions for confidential balances and transfers, - with the ability to reveal information to authorized parties when required. +- Public transactions for transparent flows +- Shielded transactions for confidential balances and transfers +- Selective disclosure to authorized parties when required See: [Cryptography](/learn/cryptography) and [Transaction Models on Dusk](/learn/deep-dive/duskds-tx-models). @@ -67,10 +61,12 @@ For the full consensus specification, see Section 3 “Consensus mechanism” of ### Modular & EVM-friendly -Dusk separates settlement from execution, making it easier to match the right environment to each use case: -- DuskDS – consensus, data availability, settlement, and the privacy‑enabled transaction model -- DuskEVM – an Ethereum‑compatible execution layer where DUSK is the native gas token -- Native bridging between layers so assets can move where they’re most useful +Dusk separates settlement from execution: + +- **DuskDS**: consensus, data availability, settlement, and the privacy-enabled transaction model +- **DuskEVM**: an Ethereum-compatible execution layer where DUSK is the native gas token + +Assets can move between layers so you can use the right environment for each job. See: [Core Components](/learn/core-components) and [DuskEVM Developer Docs](/developer/smart-contracts-dusk-evm/deploy-on-evm). @@ -107,7 +103,7 @@ Here’s how the main components fit together: | **Rusk** | Reference node implementation that runs Succinct Attestation | [Run a node](/operator/overview) | | **Citadel**| Identity & access primitives for compliant, permissioned flows | [Core Components](/learn/core-components#citadel) | -If you want a deeper technical dive, start with [Cryptography](/learn/cryptography) or the [Dusk Whitepaper](https://dusk-network-dusks3.s3.eu-central-1.amazonaws.com/Dusk_Whitepaper_2024_4db72f92a1.pdf). +If you want a deeper technical dive, start with [Cryptography](/learn/cryptography) or the [Dusk Whitepaper](https://dusk-cms.ams3.digitaloceanspaces.com/Dusk_Whitepaper_2024_4db72f92a1.pdf). ## Start building on Dusk diff --git a/src/content/docs/learn/rusk-wallet.md b/src/content/docs/learn/rusk-wallet.md index fc515c5f..71b940d1 100644 --- a/src/content/docs/learn/rusk-wallet.md +++ b/src/content/docs/learn/rusk-wallet.md @@ -1,111 +1,93 @@ --- title: Rusk Wallet -description: Using the Rusk Wallet to leverage CLI functionalities when interacting with Dusk. +description: "The official CLI wallet for Dusk: scripting, staking, and operator workflows." --- -The [**Rusk Wallet**](https://github.com/dusk-network/rusk/tree/master/rusk-wallet) is a powerful and feature-rich command-line interface (CLI) wallet designed for managing DUSK and interacting directly with the network. +`rusk-wallet` is the official command-line wallet for Dusk. Use it when you want automation, terminal-first workflows, or node/operator tasks. -Latest release is rusk-wallet-0.2.0. +If you prefer a UI for everyday transfers, use the [Web Wallet](/learn/web-wallet). -Users can choose to use either the interactive mode, which offers a menu-driven interface, or execute specific subcommands to perform tasks such as sending funds, managing balances, staking, and interacting with smart contracts. +## Install -## Commands Overview +- Download a prebuilt binary from the Rusk releases page. +- Or build from source from the rusk repo. -By default, the CLI runs in **interactive** mode when no arguments or subcommands are provided. To start it, simply run: +## Usage + +Run without arguments to start interactive mode: ```bash rusk-wallet ``` -This mode presents users with a menu-driven interface, allowing them to navigate through wallet functions interactively without typing commands manually. - -The Rusk Wallet can be also run in **headless mode**, where you specify a subcommand to execute actions directly without needing the interactive interface. - -To skip the interactive mode and run in headless mode, provide a subcommand directly: +Run a command directly (headless mode): ```bash -rusk-wallet +rusk-wallet [flags] ``` -For example: + +Discover available commands and flags with: ```bash -rusk-wallet balance +rusk-wallet --help +rusk-wallet --help ``` -The Rusk wallet provides several subcommands for wallet creation, transactions, staking, and more: - +The full CLI command reference lives in the upstream README: +rusk-wallet/src/bin/README.md. -| **Subcommand** | **Description** | -|--------------------|---------------------------------------------------------| -| `create` | Create a new wallet | -| `restore` | Restore a lost wallet using the recovery phrase | -| `balance` | Check your current DUSK balance | -| `history` | View the transaction history of a wallet address | -| `transfer` | Send DUSK through the network | -| `shield` | Convert public DUSK to shielded DUSK | -| `unshield` | Convert shielded DUSK to public DUSK | -| `stake` | Stake DUSK to earn rewards | -| `unstake` | Unstake your DUSK | -| `withdraw` | Withdraw accumulated staking rewards | -| `contract-deploy` | Deploy a smart contract | -| `contract-call` | Call a contract | -| `export` | Export your BLS provisioner key-pair | -| `settings` | View current settings | +## Common tasks - - -## Wallet Password - -By default, the wallet will prompt you for a password whenever sensitive information needs to be decrypted (e.g., accessing the wallet or exporting keys). If you're running automated scripts or in a headless environment, you can bypass this prompt using the `RUSK_WALLET_PWD` environment variable: +### Create or restore a wallet ```bash -export RUSK_WALLET_PWD= +rusk-wallet create ``` -The `RUSK_WALLET_PWD` is used for: +```bash +rusk-wallet restore +``` -- Wallet decryption (in all commands that use a wallet) -- Wallet encryption (during the wallet creation, in `create`) -- BLS key encryption (in `export`) +### Check balance -## Offline Commands +```bash +rusk-wallet balance +``` -Some commands can run without an active connection to Rusk. These commands work offline because they rely on locally stored wallet data instead of requiring real-time interaction with the Dusk. Offline commands are particularly useful for setting up or recovering wallets before connecting to the network. +### Transfer funds -- `create`: Create a new wallet -- `restore`: Restore an existing wallet -- `addresses`: Retrieve wallet addresses -- `export`: Export your BLS provisioner key-pair - -All other commands, including transactions, require an active connection to a running Rusk instance. +Use the built-in help for the exact flags: -To explore all available commands, you can run: ```bash -rusk-wallet help +rusk-wallet transfer --help ``` -## Staking with an owner key +### Stake (owner key optional) -A stake in Dusk is defined by two keys: -- **Consensus key:** used to participate in consensus. -- **Owner key:** entitled to unstake or withdraw DUSK. +A Dusk stake has two roles: -By default, the Rusk Wallet uses your wallet’s consensus key as the owner key. If you don't specify an owner, both consensus activities and stake ownership will be tied to the same consensus key. +- **Consensus key**: used to participate in consensus. +- **Owner key**: the address that can `unstake` and `withdraw`. -However, you can override this behavior by passing `--owner
`, for example: +If you don't specify `--owner`, the consensus key is also the owner. ```bash -# Stake 2000 DUSK with a custom owner -rusk-wallet stake --amt 2000 --owner ADDo5VBg8q…Kb1jZFmWr +# Stake with the default owner (consensus key) +rusk-wallet stake --amt 1000 + +# Stake with a separate owner address +rusk-wallet stake --amt 1000 --owner ``` -Alternatively, you can simply omit the `--owner
` flag: +For the node-operator flow (exporting consensus keys, staking, and monitoring with `stake-info`), follow: [Wallet setup](/operator/guides/node-wallet-setup). + +## Non-interactive use (automation) + +Most commands prompt for a wallet password when they need to decrypt secrets. For automation, you can provide it via `RUSK_WALLET_PWD`: + ```bash -# Stake 1000 DUSK with a default owner key -rusk-wallet stake --amt 1000 +export RUSK_WALLET_PWD= +rusk-wallet balance ``` -so that the owner key is the consensus key. -:::note[Important] -if you choose a non-consensus key as the owner, keep in mind that only that owner key can later unstake or withdraw those funds. -::: \ No newline at end of file +Only do this in controlled environments, and be careful not to leak passwords via shell history, logs, or CI output. diff --git a/src/content/docs/learn/tokenization-comparison.md b/src/content/docs/learn/tokenization-comparison.md index a11d5243..c9febb4d 100644 --- a/src/content/docs/learn/tokenization-comparison.md +++ b/src/content/docs/learn/tokenization-comparison.md @@ -1,42 +1,28 @@ --- -title: Digitization, Tokenization and Native Issuance -description: Understand the difference between Tokenization and Native Issuance, and how Dusk is able to provide both. +title: Native Issuance +description: What native issuance means, how it differs from tokenization, and why it matters for regulated assets. --- -## Common Misconceptions -In the rapidly changing financial markets, tokenization is often mistaken for native issuance, leading to confusion. However, these are distinct processes with different implications for how regulated financial assets are managed, traded, and settled. Understanding these differences is essential for grasping how blockchain technology applies to real-world assets (RWAs). +People often use “tokenization” to mean “putting an asset on a blockchain”. For regulated assets, it helps to be more precise because the lifecycle (issuance, custody, trading, settlement, reporting) determines what has to happen off-chain. +This page defines the terms and explains where **native issuance** fits in. -Before understanding the differences between tokenization and native issuance, let's first take a step back and quickly mention what digitization is. +## Definitions ### Digitization -Digitization is the process of transforming physical or paper-based financial assets, such as securities or certificates, into a digital format. At its core, digitization is simply about changing the medium of the asset from physical to digital, allowing for easier access, handling, and transfer through electronic systems. However, it does not inherently change the underlying nature of the asset, nor does it introduce new functionalities. A digital representation of an asset still operates within the constraints of traditional market infrastructures, such as central securities depositories (CSDs), clearinghouses, and intermediaries. -For example, a paper-based stock certificate that is digitized remains fundamentally the same stock, only stored and transacted electronically. The inefficiencies of settlement times, trade reconciliation, and reliance on intermediaries still persist, though in a more convenient digital form. +Digitization is moving an asset’s recordkeeping from paper/manual processes to digital systems (for example, dematerialized securities in a central registry). The asset lifecycle and intermediaries usually stay the same. ### Tokenization -Tokenization builds on digitization by adding specific functionalities to these digital representations, such as fractional ownership and programmability via smart contracts. +Tokenization is issuing a token that represents an asset (or a claim on an asset). The token may be programmable and easier to integrate with apps, but regulated assets often still rely on existing custody/registry/settlement processes off-chain. -While tokenization introduces exciting possibilities like the ability to fractionalize ownership or automate specific functions through smart contracts, it still faces a fundamental limitation. This limitation comes from the fact that there is the need for reconciliation between the tokenized asset and the underlying asset. Due to regulatory requirements, the underlying asset is still held by a custodial entity (such as a CSD), and this dependence introduces inefficiencies, including delays in settlement and increased costs due to the necessity of verifying that the tokenized form and the underlying asset are in sync. +### Native issuance -Tokenization deals with the front-end of financial transactions, making assets more accessible and programmable. However, it does not resolve the deeper infrastructural challenges related to clearing, settlement, and compliance. These challenges can only be resolved by innovating the infrastructure level of finance and hold the necessary licenses to do so. The vast majority of tokenization platforms still need to rely on traditional financial intermediaries, as the underlying asset needs to be reconciled with the synthetic one. Securities are highly regulated assets, and there is no way to avoid the scrutiny of regulators. The requirement of having the necessary licenses to deal with securities is often an obstacle for tech companies, as they depend on complying with applicable regulatory frameworks in order to use their solution. - - -### Native Issuance -Native issuance is the next step in the evolution of digital finance, and it represents a significant departure from both digitization and tokenization. In native issuance, the asset itself is created and exists natively on the blockchain, without the need for a corresponding underlying asset held elsewhere. Because the asset exists entirely within the digital realm, there is no need for reconciliation between a synthetic token and its physical or off-chain counterpart: everything happens on-chain. - -Native issuance eliminates the inefficiencies introduced by custodial systems and enables disintermediation, where assets can be transferred, settled, and cleared entirely on-chain. By removing intermediaries and creating an environment where the asset is fully native to the ledger, native issuance allows for faster finality, lower costs, and stronger compliance with regulatory requirements like privacy and transparency. The advantages of native issuance clearly surpass those of simple tokenization. - -## Understanding the Differences -Understanding the difference between digitization, tokenization, and native issuance is essential for anyone involved in the modernization of financial markets, as these processes have profound implications for efficiency, cost, and regulatory compliance. - -Digitized and tokenized assets still rely on outdated infrastructure (such as CSDs) for settlement, introducing inefficiencies like delayed finality and increased costs. native issuance, by contrast, enables real-time settlement, reducing the risk of settlement failures and enhancing market liquidity. - -Tokenization typically involves a custodial model where the underlying asset is held by a third party, creating reliance on intermediaries and regulatory frameworks that can slow down the system. Native issuance eliminates these middlemen, leading to faster and cheaper transactions. +Native issuance means the asset itself is created and managed **on-chain**: issuance, transfers, and (depending on the design) settlement happen on the ledger without needing to reconcile a “token” against a separate system of record. ### Digitization vs Tokenization vs Native Issuance -Below, you can find a diagram that gives an overview about the main differences: +Here’s a quick comparison: | | **Digitization** | **Tokenization** | **Native Issuance** | |---------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------|--------------------------------------------------------------------| @@ -48,20 +34,13 @@ Below, you can find a diagram that gives an overview about the main differences: | **Risk of Settlement Failure** | Yes, due to manual reconciliation and intermediary involvement | Yes, due to manual reconciliation and intermediary involvement | No, as settlement is on-chain | | **Innovation Level** | Zero. This is how things work now | Low. It only introduces fractionalization and partial programmability | High. It removes intermediaries and enables fully on-chain processes | -## Why Dusk - -### Beyond Tokenization - -While most projects limit their focus on tokenization, which addresses only the "front-end" of the financial system, Dusk innovates across the entire financial infrastructure, including essential back-end processes like clearance, settlement, and compliance. Dusk provides fast, private, and efficient on-chain settlement that meets institutional standards, delivering a decentralized market infrastructure that removes the need for intermediaries and custodial reliance. Unlike the vast majority of projects, Dusk tackles not only tokenization but also the deeper regulatory and operational challenges necessary for institutional-grade financial markets. - -Dusk isn’t just another platform layering tokenization onto outdated systems. It is building an entirely new decentralized financial market infrastructure that allows assets to be natively issued, settled, and cleared on-chain without the need for intermediaries like CSDs. By focusing on both the front-end (tokenization) and the back-end (settlement and compliance), Dusk is paving the way for a truly disintermediated financial market for trading securities. - -### Meeting Institutional Standards +## Where Dusk fits -Many other blockchains, including popular solutions like Layer 2s on Ethereum, are not well-suited for settling securities transactions due to their inability to meet the stringent requirements of institutional-grade financial markets. +Dusk is built for regulated markets where **privacy, compliance controls, and deterministic settlement** are requirements, not add-ons. -Some of the challenges are: +In practice, that means you can: -- **Fast Finality**: Securities settlement requires transactions to be finalized in under 10 seconds to meet institutional standards. Ethereum Layer 2 solutions, which batch transactions and settle them on Layer 1, usually experience delays of at least several minutes. This disqualifies them from real-time settlement use cases, making them unsuitable for securities transactions where fast finality is crucial. +- build applications and tokenization-style workflows with familiar EVM tooling (via **DuskEVM**), and +- rely on the settlement layer (**DuskDS**) for privacy-capable transaction models and finality. -- **Compliance and Privacy**: Regulatory frameworks like GDPR require privacy-preserving transaction models. Dusk’s protocol is designed to ensure compliance by offering features like selective disclosure and explicit acceptance, which are essential for adhering to legal and regulatory standards throughout the transaction lifecycle. In contrast, networks with account-based models (like EVM-based chains) do not provide the privacy needed for such compliance. This lack of privacy also increases the risk of market manipulation, further complicating their use for regulated assets like securities. \ No newline at end of file +If you want the architectural overview next, see [Core Components](/learn/core-components). For the product and market framing, see [Overview](/learn/overview). diff --git a/src/content/docs/learn/tokenomics.md b/src/content/docs/learn/tokenomics.md index 8c85e795..48d7b29e 100644 --- a/src/content/docs/learn/tokenomics.md +++ b/src/content/docs/learn/tokenomics.md @@ -1,165 +1,126 @@ --- -title: Tokenomics -description: Overview of Dusk’s tokenomics, allocation, vesting schedules, and incentives. - - +title: Tokenomics +description: DUSK token utility, supply, emissions, and staking incentives. --- -The Dusk protocol utilizes the DUSK token both as an incentive for consensus participation and as its primary native currency. DUSK is currently represented as an ERC20 or BEP20 token. Since mainnet is now live, users are able to [migrate tokens to native DUSK](/learn/guides/mainnet-migration) via a burner contract. - -This page provides an in-depth overview of the DUSK token’s metrics, utility, allocation, emission schedule, rewards, as well as insights from the Economic Protocol Design report. - -## Token Metrics - -- **Token Name**: Dusk -- **Token Symbol**: DUSK -- **Initial Supply**: 500,000,000 DUSK, comprising both ERC20, BEP20. These are migrated to native DUSK tokens using a burner contract. -- **Total Emitted Supply**: 500,000,000 DUSK will be emitted over 36 years to reward stakers on the mainnet, following the [Token Emission Schedule](#token-emission-schedule). -- **Maximum Supply**: 1,000,000,000 DUSK, combining the 500M initial supply and 500M emitted over time. -- **Circulating Supply**: Available on [this page](https://supply.dusk.network/). The circulating supply reflects the initial supply minus the DUSK held by the [Dusk deployer](https://etherscan.io/token/0x940a2db1b7008b6c776d4faaca729d6d4a4aa551?a=0x618bb3b255928ae6b2046df5c828fa1dc7e3c5f0). -* **ICO**: Raised \$8 million in November 2018, with tokens priced at $0.0404. Private sale tokens account for 50% of the total supply, split between 10% DUSK BEP20 and 40% DUSK ERC20. - -## Token Contract - -The DUSK token is available as an ERC20 on Ethereum and a BEP20 on Binance Smart Chain. - -| Chain | Standard | Contract Address | -|----------------------|----------|--------------------------------------------| -| Ethereum | ERC20 | [0x940a2db1b7008b6c776d4faaca729d6d4a4aa551](https://etherscan.io/token/0x940a2db1b7008b6c776d4faaca729d6d4a4aa551) | -| Binance Smart Chain | BEP20 | [0xb2bd0749dbe21f623d9baba856d3b0f0e1bfec9c](https://bscscan.com/token/0xb2bd0749dbe21f623d9baba856d3b0f0e1bfec9c) | - -## Token Markets & Exchanges +DUSK is the native token used for transaction fees (gas) and staking on the Dusk network. -The DUSK token is widely accessible on top-tier CEXs and DEXs. For more information on the various locations DUSK is accessible, see the markets pages for Coinmarketcap and Coingecko: -- [DUSK markets Coinmarketcap](https://coinmarketcap.com/currencies/dusk/#Markets) -- [DUSK markets Coingecko](https://www.coingecko.com/en/coins/dusk) +If you hold ERC20/BEP20 DUSK (on Ethereum/BSC), follow the [mainnet migration guide](/learn/guides/mainnet-migration) to move to native DUSK. -## Token Utility +For economic model rationale and assumptions, see the Economic Protocol Design report. -DUSK serves several key purposes within the ecosystem: -* Used for staking in consensus participation. -* Rewards to consensus participants. -* Payment of network fees (See [Transaction fees & gas](#transaction-fees--gas)). -* Paying for the deployment of dApps on the network. -* Payment of services on the network. +## Quick facts -### Transaction fees & gas +- **Symbol**: DUSK +- **Decimals (native DUSK)**: 9 (`1 DUSK = 1,000,000,000 LUX`) +- **Decimals (ERC20/BEP20 DUSK)**: 18 (see [migration guide](/learn/guides/mainnet-migration)) +- **Supply model**: 500,000,000 initial + 500,000,000 emitted over time (max 1,000,000,000) +- **Live supply**: see [supply.dusk.network](https://supply.dusk.network/) -Every transaction on Dusk consumes **gas**, a unit that measures how much work it does on-chain. +## What DUSK is used for -- You specify a **gas limit** (maximum work you’re willing to pay for) and a **gas price** in `LUX` - (`1 LUX = 10⁻⁹ DUSK). -- The actual fee paid is `gas_used × gas_price`. Unused gas is not charged. -- If a transaction runs out of gas during execution, it is reverted and the fee for the gas consumed is still charged. +- **Gas**: pay for transactions and on-chain execution. +- **Staking**: secure the network and earn rewards. -Gas price adjusts with network demand. When demand is low, prices tend to be low, resulting in very cheap transactions for users. +## Fees and gas -Collected fees are added to the block reward and redistributed as described in [Incentive structure](#incentive-structure). +Every transaction consumes **gas** (a unit of work). Fees are paid in `DUSK`. -## Token Allocation and Vesting Overview +- You set a **gas limit** and a **gas price** (in `LUX`). +- The fee paid is `gas_used * gas_price`. +- Unused gas is not charged. +- If a transaction runs out of gas, it reverts, but the gas spent is still paid. -The vesting period ran from May 2019 to April 2022. - -| Allocation Category | Percentage | DUSK Tokens | Vested | -|---------------------|------------|---------------|---------------| -| Token Sale | 50% | 250,000,000 | 250,000,000 | -| Team | 6.4% | 32,000,000 | 32,000,000 | -| Advisors | 6.4% | 32,000,000 | 32,000,000 | -| Development | 18.1% | 90,500,000 | 90,500,000 | -| Exchange | 11.8% | 59,000,000 | 59,000,000 | -| Marketing | 7.3% | 36,500,000 | 36,500,000 | -| **Total** | **100%** | **500,000,000** | **500,000,000** | - -## Staking Details - -Staking is a crucial aspect of the Dusk protocol, allowing token holders to contribute to network security. For more details on the emission schedule, see the **[Token Emission Schedule](/learn/tokenomics#token-emission-schedule)** below. Here are the primary details for staking DUSK tokens: - -* **Minimum Staking Amount**: 1000 DUSK. -* **Maximum Staking Amount**: No upper bound. -* **Stake Maturity Period**: 2 Epochs - 4320 blocks. -* **Unstaking**: No penalties or waiting period. +Collected fees are part of the **block reward** and are redistributed (see [Incentives](#incentives)). -## Token Emission Schedule +## Staking parameters -The DUSK token emission schedule plays a vital role in incentivizing network participants, particularly in the early stages of the blockchain network, where transaction fees alone may not be sufficient to reward node operators and validators. By systematically emitting tokens over time, the Dusk network ensures that participants are adequately compensated for securing and maintaining the network, fostering its growth and decentralization. +For the user-facing flow, see [Staking on Dusk](/learn/guides/staking-basics). -The token emission has been designed to align with the long-term vision of building a robust and enduring ecosystem, while controlling inflation and limiting potential attack vectors. The emission schedule follows a carefully structured geometric decay model, wherein the number of emitted tokens reduces systematically every 4 years. This approach balances the need for continuous token issuance with inflation control, ensuring long-term sustainability and stability for the DUSK token economy. +- **Minimum stake**: 1,000 DUSK +- **Maximum stake**: no upper bound +- **Maturity**: 2 epochs (4,320 blocks) +- **Unstaking**: no penalties or waiting period +- **Adding to stake (top-ups)**: see [Adding to an existing stake](/learn/guides/staking-basics#adding-to-an-existing-stake) -Key aspects of the DUSK token emission schedule include: +## Incentives -- **36-Year Emission Duration**: The token emission is distributed across 36 years, divided into 9 periods of 4 years each. -- **Emission Reduction Every 4 Years**: Token emission decreases every 4 years by a fixed reduction rate, ensuring gradual reduction in token issuance, similar to Bitcoin’s halving model. +Each block has a **block reward** consisting of: -## Token Emission +- newly emitted DUSK (see [Token emission](#token-emission)), and +- all transaction fees paid in that block. -The emission rate starts with a reduction rate `r = 0.5`, meaning the token emission halves every 4 years. This strategy is designed to rapidly build network participation by providing strong early incentives. +Reward distribution: -| Period (Years) | Period Duration (Blocks) | Total Emission (DUSK) | Total Supply (Cumulative) | Emission Per Block | Reduction Rate (r) | -|--------------------|--------------------------|-----------------------|---------------------------|--------------------|--------------------| -| 1 (0-4) | 12,614,400 | 250.48M | 250.48M | 19.8574 DUSK/block | N/A | -| 2 (4-8) | 12,614,400 | 125.24M | 375.72M | 9.9287 DUSK/block | 0.5 | -| 3 (8-12) | 12,614,400 | 62.62M | 438.34M | 4.9644 DUSK/block | 0.5 | -| 4 (12-16) | 12,614,400 | 31.31M | 469.65M | 2.4822 DUSK/block | 0.5 | -| 5 (16-20) | 12,614,400 | 15.65M | 485.30M | 1.2411 DUSK/block | 0.5 | -| 6 (20-24) | 12,614,400 | 7.83M | 493.13M | 0.6206 DUSK/block | 0.5 | -| 7 (24-28) | 12,614,400 | 3.91M | 497.04M | 0.3103 DUSK/block | 0.5 | -| 8 (28-32) | 12,614,400 | 1.95M | 498.99M | 0.1551 DUSK/block | 0.5 | -| 9 (32-36) | 12,614,400 | 0.98M | 499.97M | 0.0776 DUSK/block | 0.5 | +- **Block generator**: 70% + up to an extra 10% (based on credits included in the certificate; any undistributed portion is burned) +- **Development fund**: 10% +- **Validation committee**: 5% +- **Ratification committee**: 5% -More information regarding the model can be found in the -Economic Protocol Design report. +## Token emission -## Incentive Structure +The network emits a total of **500,000,000 DUSK** over **36 years** to fund staking rewards. +Emissions follow a geometric decay model with reduction rate `r = 0.5` (halving every 4 years). -Each block has a **block reward** that consists of: +
+Emission schedule (by period) -- Newly emitted DUSK according to the [token emission schedule](#token-emission-schedule) -- All transaction fees paid in that block +| Period (Years) | Period Duration (Blocks) | Total Emission (DUSK) | Total Supply (Cumulative) | Emission Per Block | Reduction Rate (r) | +|---|---:|---:|---:|---:|---:| +| 1 (0-4) | 12,614,400 | 250.48M | 250.48M | 19.8574 | N/A | +| 2 (4-8) | 12,614,400 | 125.24M | 375.72M | 9.9287 | 0.5 | +| 3 (8-12) | 12,614,400 | 62.62M | 438.34M | 4.9644 | 0.5 | +| 4 (12-16) | 12,614,400 | 31.31M | 469.65M | 2.4822 | 0.5 | +| 5 (16-20) | 12,614,400 | 15.65M | 485.30M | 1.2411 | 0.5 | +| 6 (20-24) | 12,614,400 | 7.83M | 493.13M | 0.6206 | 0.5 | +| 7 (24-28) | 12,614,400 | 3.91M | 497.04M | 0.3103 | 0.5 | +| 8 (28-32) | 12,614,400 | 1.95M | 498.99M | 0.1551 | 0.5 | +| 9 (32-36) | 12,614,400 | 0.98M | 499.97M | 0.0776 | 0.5 | -This total reward is distributed between network participants and the development fund. In the current design: - -- **70%** to the Block Generator (proposal step) and an extra **10%** depending on the -credits included in the certificate. Any undistributed rewards from this 10% are burned as part of the gas-burning mechanism. -- **10%** to the Dusk Development Fund -- **5%** to the Validation Committee (validation step) -- **5%** to the Ratification Committee (ratification step) - -This structure rewards all roles in Succinct Attestation, with a strong incentive for block generators to include as many votes as possible in their certificates. +
## Slashing -Dusk uses soft slashing to discourage misbehaviour and long downtime from provisioners. The protocol does not burn a provisioner’s staked DUSK; instead it temporarily reduces how that stake participates and earns rewards. +Dusk uses **soft slashing** to discourage repeated faults and long downtime. +Soft slashing does not burn stake; it reduces a provisioner's effective participation and rewards. -### When can you be slashed? +- **Suspension**: stake is suspended for one or more epochs (not eligible for selection; earns no rewards). +- **Penalization**: a portion of stake is moved to the claimable rewards pool, reducing effective stake used in sortition. -Soft slashing is only applied when a provisioner repeatedly fails to behave as expected, for example by: +In practice: run official software, keep it updated and online, and monitor missed duties. -- running outdated or modified node software; or -- frequently missing assigned duties (e.g. block generator or committee slots). +## Token versions and contracts -If you run the official, up‑to‑date node and keep it online and in sync, slashing should be rare. +Native DUSK is the mainnet token. +ERC20 and BEP20 DUSK exist on other chains for migration and bridging. -### Effects of soft slashing +| Chain | Standard | Contract address | +|---|---|---| +| Ethereum | ERC20 | [0x940a2db1b7008b6c776d4faaca729d6d4a4aa551](https://etherscan.io/token/0x940a2db1b7008b6c776d4faaca729d6d4a4aa551) | +| BSC | BEP20 | [0xb2bd0749dbe21f623d9baba856d3b0f0e1bfec9c](https://bscscan.com/token/0xb2bd0749dbe21f623d9baba856d3b0f0e1bfec9c) | -Soft slashing has two consequences: +## Markets -**Suspension** +For up-to-date markets and trading venues, see: -After enough faults, the provisioner’s stake is **suspended** for one or more epochs: +- [CoinMarketCap markets](https://coinmarketcap.com/currencies/dusk/#Markets) +- [CoinGecko markets](https://www.coingecko.com/en/coins/dusk) -- the suspended stake is not considered for committee selection; -- it earns no rewards while suspended; -- repeated faults increase the length of future suspensions. +## Historical allocation (initial supply) -Once the suspension period ends and the node behaves correctly, the stake becomes eligible again. - -**Penalization** +The vesting period ran from May 2019 to April 2022. -Alongside suspension, a portion of the stake is **penalized**: +
+Allocation and vesting table -- the penalized portion is moved to the claimable rewards pool, so no DUSK is lost from the system; -- the effective stake used in sortition is reduced, so the node is selected less often; -- the penalty grows with consecutive suspensions (starting around 10% of the stake and increasing in steps). -If the effective stake falls below the minimum (1000 DUSK), it must be un‑staked and re‑staked to participate again. +| Allocation Category | Percentage | DUSK Tokens | Vested | +|---|---:|---:|---:| +| Token Sale | 50% | 250,000,000 | 250,000,000 | +| Team | 6.4% | 32,000,000 | 32,000,000 | +| Advisors | 6.4% | 32,000,000 | 32,000,000 | +| Development | 18.1% | 90,500,000 | 90,500,000 | +| Exchange | 11.8% | 59,000,000 | 59,000,000 | +| Marketing | 7.3% | 36,500,000 | 36,500,000 | +| Total | 100% | 500,000,000 | 500,000,000 | -In practice, avoiding slashing is straightforward: run the official software, keep your node current and online, and monitor it for missed duties. +
diff --git a/src/content/docs/learn/web-wallet.md b/src/content/docs/learn/web-wallet.md index 794dfa31..5443c23a 100644 --- a/src/content/docs/learn/web-wallet.md +++ b/src/content/docs/learn/web-wallet.md @@ -1,49 +1,52 @@ --- title: Web Wallet -description: Use the Dusk Web Wallet to manage your DUSK and interact with the network. +description: Use the Dusk Web Wallet to manage DUSK in your browser. --- -The [Dusk Web Wallet](https://wallet.dusk.network) is the seamless tool to manage DUSK and interact with the network securely. Designed with an intuitive UI, the web wallet allows users to send and receive funds, manage assets, and interact with decentralized applications (dApps) built on Dusk. +The Dusk Web Wallet is the simplest way to manage DUSK and interact with the network. +It runs in your browser and supports both **public** (Moonlight) and **shielded** (Phoenix) transfers. -The Web Wallet can be accessed directly from your browser without the need to install any extensions. +## What you can do with it -With Dusk’s dual-model approach, you can choose to send funds through a **shielded** or **public** transaction, giving you full control over your transaction’s privacy. +- Create or restore a Dusk wallet from a mnemonic. +- Send and receive DUSK using public or shielded transfers. +- Migrate ERC20/BEP20 DUSK to native DUSK: [ERC20/BEP20 Migration](/learn/guides/mainnet-migration). +- Bridge native DUSK to BSC: [Native DUSK to BEP20 Bridge](/learn/guides/bep20-bridge). +- Bridge DuskDS testnet to DuskEVM testnet: [DuskDS to DuskEVM bridge](/learn/guides/duskevm-bridge). + +For node/operator staking workflows, use the CLI wallet and operator guides instead: +[Staking on Dusk](/learn/guides/staking-basics), [Rusk Wallet](/learn/rusk-wallet), and [Run a provisioner node](/operator/provisioner). -ou can easily convert your funds between public and shielded forms. This flexibility accommodates diverse needs, ensuring both user privacy and regulatory compliance ## How to use the Web Wallet -Using the Web Wallet is easy and intuitive: +### 1) Open the Web Wallet -### 1) Access the Web Wallet -Visit the official [Web Wallet](https://wallet.dusk.network) page using any modern web browser. +Visit the official Web Wallet at apps.dusk.network/wallet. :::note[Important] -Always ensure you are on the official Dusk website to prevent phishing attacks. +Always verify the URL before entering your recovery phrase. Never share your mnemonic or private keys. ::: -### 2) Create or Restore a Wallet +### 2) Create or restore a wallet + You can either create a new wallet or restore an existing one using your recovery phrase. -#### Option A) Create a New Wallet -1. Click **Create New Wallet** -2. Write down and securely store your **12-word recovery phrase**. This phrase is the only way to recover your wallet. Never share it with anyone, and keep it in a safe -1. Set a **strong password** to encrypt your wallet. If you lose the password, you can still recover your funds by creating a new wallet from the recovery phrase. +#### Option A) Create a new wallet -#### Option B) Restore an Existing Wallet -1. Click **Restore Wallet** -2. Enter your **12-word recovery phrase** and follow the instructions to access your funds. +1. Click **Create New Wallet**. +2. Write down and securely store your **12-word recovery phrase**. +3. Set a **strong password** to encrypt your wallet. -### 3) Add and Manage DUSK -Once your wallet is set up, you’ll be able to view your balance, transaction history, and manage DUSK. +#### Option B) Restore an existing wallet -- **To Receive DUSK:** - - Navigate to the **Receive** tab and copy your wallet address. Share this address with the sender to receive funds. +1. Click **Restore Wallet**. +2. Enter your **12-word recovery phrase** and follow the prompts. -- **To Send DUSK:** - - Navigate to the **Send** tab, enter the recipient’s address, amount, and choose between shielded or public transfer options. - - Confirm and sign the transaction. +### 3) Receive or send DUSK +- **Receive**: open the **Receive** tab and copy your address. +- **Send**: open the **Send** tab, enter the recipient and amount, then choose **public** or **shielded**. -:::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/deep-dive/duskds-tx-models). +:::tip +Public transfers use Moonlight. Shielded transfers use Phoenix. Learn more about both models in [Transaction Models on Dusk](/learn/deep-dive/duskds-tx-models). ::: diff --git a/src/content/docs/operator/FAQ.md b/src/content/docs/operator/FAQ.md index 716fd59a..b572f4f1 100644 --- a/src/content/docs/operator/FAQ.md +++ b/src/content/docs/operator/FAQ.md @@ -44,7 +44,7 @@ After the 4320-block maturity period (about 12 hours). See [/learn/guides/stakin #### How do I increase stake or compound rewards? -See [/learn/guides/staking-basics#re-stake-rewards--increase-stake](/learn/guides/staking-basics#re-stake-rewards--increase-stake). +See [/learn/guides/staking-basics#adding-to-an-existing-stake](/learn/guides/staking-basics#adding-to-an-existing-stake). ## Keys and Recovery diff --git a/src/content/docs/operator/guides/node-wallet-setup.md b/src/content/docs/operator/guides/node-wallet-setup.md index 4a2a1d39..9e973057 100644 --- a/src/content/docs/operator/guides/node-wallet-setup.md +++ b/src/content/docs/operator/guides/node-wallet-setup.md @@ -17,8 +17,8 @@ This guide explains setting up the wallet and the last steps needed to start run Before setting up your node wallet, you’ll need a mnemonic. You can obtain one using any of the following methods: -- **Using the CLI wallet ([rusk-wallet](https://github.com/dusk-network/rusk/blob/master/rusk-wallet/src/bin/README.md))**, either directly on your node or locally on your machine. You can download Rusk Wallet from the [Rusk releases page](https://github.com/dusk-network/rusk/releases?q=rusk+wallet&expanded=true). -- **Using the [Web Wallet](https://apps.dusk.network/wallet/setup/)** if you would rather use a web app to access your wallet on your main device. +- **Using the CLI wallet ([Rusk Wallet](/learn/rusk-wallet))**, either directly on your node or locally on your machine. You can download it from the [Rusk releases page](https://github.com/dusk-network/rusk/releases?q=rusk+wallet&expanded=true). +- **Using the [Web Wallet](/learn/web-wallet)** if you would rather use a web app to access your wallet on your main device. **Important:** Back up your mnemonic phrase securely and never share it. Anyone with access to this phrase can control your wallet and funds. diff --git a/src/content/docs/operator/guides/upgrade-node.mdx b/src/content/docs/operator/guides/upgrade-node.mdx index 9576c28c..f353dd72 100644 --- a/src/content/docs/operator/guides/upgrade-node.mdx +++ b/src/content/docs/operator/guides/upgrade-node.mdx @@ -3,9 +3,9 @@ title: Upgrade your node description: Learn how to update your Dusk node to the latest version of the Nocturne testnet. --- -A network may be occasionally upgraded with new features and performance optimizations. +A network may occasionally be upgraded with new features and performance optimizations. -To make the upgrade process as flawless as possible, the [node installer](https://github.com/dusk-network/node-installer) script may be updated from time to time. This script can be ran in a non-destructive way, meaning it changes only what is needed. It will gracefully shut down Rusk for you. +To make the upgrade process as flawless as possible, the [node installer](https://github.com/dusk-network/node-installer) script may be updated from time to time. This script can be run in a non-destructive way, meaning it changes only what is needed. It will gracefully shut down Rusk for you. ## How to Upgrade @@ -71,7 +71,7 @@ If everything else fails, check out the [manual resync](/operator/guides/manual- This only applies for testnet. ::: -Sometimes the Testnet gets reset. For that you need to reset the state of Nocturne. +Sometimes the testnet gets reset. In that case you need to reset the state of Nocturne. 1. To reset the state of Nocturne, download the latest version of our installer: ```sh @@ -95,9 +95,9 @@ rusk-wallet stake-info ``` If you already have DUSK staked, wait until the chain starts producing blocks. You can check [our explorer](https://testnet.apps.dusk.network/explorer/) to see if the chain is progressing or when it will produce the genesis block. -1. If you do not have testnet DUSK, request nDUSK from the [faucet](/operator/networks#how-to-get-testnet-tokens). +5. If you do not have testnet DUSK (nDUSK), request it from the [faucet](/operator/networks#how-to-get-testnet-tokens). -2. Stake your nDUSK: +6. Stake your nDUSK: ```sh rusk-wallet stake --amt 1000 # Or however much you want to stake ``` diff --git a/src/content/docs/operator/provisioner.mdx b/src/content/docs/operator/provisioner.mdx index 9cf12412..8928e879 100644 --- a/src/content/docs/operator/provisioner.mdx +++ b/src/content/docs/operator/provisioner.mdx @@ -7,7 +7,7 @@ import { Tabs, TabItem } from '@astrojs/starlight/components'; Provisioners are full nodes that participate in consensus. To participate, you stake a **minimum of 1000 DUSK** and run a provisioner node 24/7. -If you only want to stake (without operating infrastructure), start with: [Staking basics](/learn/guides/staking-basics/). +If you only want to stake (without operating infrastructure), start with: [Staking on Dusk](/learn/guides/staking-basics/). ## Provisioner Specifications diff --git a/src/content/i18n/.gitkeep b/src/content/i18n/.gitkeep new file mode 100644 index 00000000..e69de29b diff --git a/src/content/i18n/en.json b/src/content/i18n/en.json new file mode 100644 index 00000000..0967ef42 --- /dev/null +++ b/src/content/i18n/en.json @@ -0,0 +1 @@ +{} diff --git a/src/sidebars/siteSidebar.js b/src/sidebars/siteSidebar.js index 60cea40d..e6186148 100644 --- a/src/sidebars/siteSidebar.js +++ b/src/sidebars/siteSidebar.js @@ -8,13 +8,11 @@ const siteSidebar = [ collapsed: false, items: [ { label: "Overview", link: "/learn/overview" }, - { label: "Native Issuance", link: "/learn/tokenization-comparison" }, - { label: "Core Values", link: "/learn/core-values" }, { label: "Core Components", link: "/learn/core-components" }, + { label: "Core Values", link: "/learn/core-values" }, + { label: "Native Issuance", link: "/learn/tokenization-comparison" }, { label: "Ecosystem & Partners", link: "/learn/ecosystem" }, - { label: "Cryptography", link: "/learn/cryptography" }, { label: "Tokenomics", link: "/learn/tokenomics" }, - { label: "Stake Abstraction", link: "/learn/hyperstaking" }, { label: "Get involved & Community", link: "/learn/community" }, { label: "Glossary", link: "/learn/glossary" }, ], @@ -41,9 +39,9 @@ const siteSidebar = [ label: "Deep dive into Dusk", collapsed: true, items: [ + { label: "Cryptography", link: "/learn/cryptography" }, { label: "Transaction Models", link: "/learn/deep-dive/duskds-tx-models" }, { label: "Assets & Regulations", link: "/learn/deep-dive/assets-and-regulations" }, - { label: "Economic Protocol", link: "/learn/deep-dive/economic-protocol" }, { label: "DuskVM", link: "/learn/deep-dive/dusk-vm" }, { label: "DuskEVM", link: "/learn/deep-dive/dusk-evm" }, { label: "Additional Resources", link: "/learn/deep-dive/additional-resources" }, @@ -61,6 +59,7 @@ const siteSidebar = [ items: [ { label: "Deploy on DuskEVM", link: "/developer/smart-contracts-dusk-evm/deploy-on-evm" }, { label: "Smart Contracts on DuskDS", link: "/developer/smart-contracts-duskds" }, + { label: "Stake Abstraction", link: "/learn/hyperstaking" }, { label: "Digital Identity Protocol", link: "/developer/digital-identity/protocol" }, ], },