Yesterday we shared the audit, and today we are sharing the specifications.
Phoenix 2.0 enables privacy without sacrificing the ability to provably identify the sender of a transaction to the receiver. This is a critical feature for regulatory compliance and institutional use cases.
"After careful evaluation, we’ve made the decision to extend the public testing phase to ensure a smooth and secure Mainnet launch. While internal testing has been successful, we believe that additional time for Lunare and Nocturne testing will allow the community to provide critical feedback and ensure the network’s resilience.
🗓 Revised Mainnet Launch Date: October 15th
We recognise that some may be disappointed by this delay, but we are confident this extension will result in a more stable and reliable network. For the full update and details on how to participate in the testing, please join our Telegram community."
🔗 [Link to Telegram Discussion](https://t.co/3U6fxeZ7VP) 🔗 [Read More: https://t.co/MWUMZhjmUs]
We are pleased to share @PolFinance_'s thorough and detailed economic report on Dusk, covering: - The $DUSK Emissions Design - The Distribution Design - The Gas Calculation Design
Understand the Duskenomics before mainnet 💪
Read the full report 👇 https://dusk.network/news/economics-report/
We are pleased to share some of our growth this year on Discord, Telegram, and X.
Our community channels have seen significant growth, including 7.4x growth on Discord and a huge 1240x increase in engagements of X according to @LunarCrush.
People often ask if there are KYC requirements to use Dusk.
To quote @HeinDauven from our AMA: "There is no KYC requirement for transferring DUSK on mainnet. You can freely transfer DUSK or use it to deploy smart contracts. The only place where you'll see KYC is on the edges (on-off ramps) or for RegDeFi"