docs: simplify About Dusk + staking/tokenomics

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',

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."
     />
     <LinkCard
-        title="Economic Protocol"
-        href="/learn/deep-dive/economic-protocol"
-        description="The economic protocol of Dusk encompasses the mechanisms enabling smart contract owners to create economic value through the services they offer."
+        title="Tokenomics"
+        href="/learn/tokenomics"
+        description="Learn how DUSK is used for fees and staking, and how emissions and rewards work."
     />
     <LinkCard
         title="Smart Contract Example"

src/content/docs/developer/integrations/exchanges.md

@@ -72,12 +72,12 @@ The [multisig contract](https://github.com/dusk-network/multisig-contract) conta
 ## Token Details
 
 - Token: `dusk`
-- Token decimals: `9` (18 decimals for ERC20 / BEP20 versions)
+- Token decimals: `9` (ERC20/BEP20 versions use 18 decimals)
 - Consensus mechanism: Succinct Attestation
 
 ## Token Migration (If Applicable)
 
-Users can migrate ERC20/BEP20 DUSK to native DUSK using the [migration contract](https://github.com/dusk-network/dusk-migration) and the [Web Wallet](https://wallet.dusk.network/).
+Users can migrate ERC20/BEP20 DUSK to native DUSK using the [migration contract](https://github.com/dusk-network/dusk-migration) and the [Web Wallet](https://apps.dusk.network/wallet/).
 
 More information: [/learn/guides/mainnet-migration](/learn/guides/mainnet-migration).
 

src/content/docs/developer/smart-contracts-duskds.md

@@ -173,7 +173,7 @@ For JavaScript integration, use [w3sper](https://github.com/dusk-network/rusk/tr
 
 ## Deploying
 
-To deploy a contract, use the [Rusk Wallet](https://github.com/dusk-network/rusk/tree/master/rusk-wallet/src/bin):
+To deploy a contract, use the [Rusk Wallet](/learn/rusk-wallet):
 
 ```bash
 rusk-wallet contract-deploy \

src/content/docs/learn/block-explorer.md

@@ -1,12 +1,12 @@
 ---
 title: Block Explorer
-description: Use the Dusk’s block explorer for looking at transaction details.
+description: Use the Dusk block explorer to look up transactions, blocks, and fees.
 ---
 
-Transactions can be viewed on the <a href="https://explorer.dusk.network/" target="_blank">Dusk Block Explorer</a>, along with statistics and information about the network.
+You can view transactions and blocks on the <a href="https://explorer.dusk.network/" target="_blank" rel="noreferrer">Dusk Block Explorer</a>.
 
 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).

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
 
 <CardGrid>
-        <LinkCard title="Official Dusk Website" href="https://dusk.network" description="Home of Dusk, the protocol for Regulated And Decentralized Finance. News, use cases and team information can be found here."/>
-        <LinkCard title="Discord (Duskcord)" href="https://discord.com/invite/dusk-official" description="Duskcord is where the more technical crowd hangs out. It is the best place to provide feedback, ask for help, and share your dApp ideas."/>
-        <LinkCard title="Telegram" href="https://t.me/DuskNetwork" description="The community on Telegram never sleeps. This channel is moderated by the core team."/>
-        <LinkCard title="Announcement" href="https://t.me/DuskAnnouncements" description="Annoucements and updates are posted in this read-only Telegram channel"/>
+  <LinkCard
+    title="Dusk website"
+    href="https://dusk.network"
+    description="News, use cases, and protocol information."
+  />
+  <LinkCard
+    title="Discord"
+    href="https://discord.com/invite/dusk-official"
+    description="Best place for technical support, integration questions, and feedback."
+  />
+  <LinkCard
+    title="Telegram"
+    href="https://t.me/DuskNetwork"
+    description="Read-only Telegram channel for official announcements."
+  />
+  <LinkCard
+    title="GitHub"
+    href="https://github.com/dusk-network"
+    description="Source code and issue trackers across the Dusk org."
+  />
 </CardGrid>
 
-## Socials
+## Getting help
+
+- For documentation fixes and requests, contribute in the docs repo: <a href="https://github.com/dusk-network/docs" target="_blank" rel="noreferrer">dusk-network/docs</a>.
+- 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).

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:
 
-<details class="info">
-<summary>**More on Dusk's vision**</summary>
-💡 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*.
-</details>
+- 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
 
-<details class="info">
-<summary>**More on DeFi advantages**</summary>
-💡 `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.
-</details>
+## 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.
+:::
 
-<details class="info">
-<summary>**More on Dusk's culture**</summary>
-💡 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.
-</details>
+- 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)

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.