Dusk - Announcement Channel

🚨 Important Update 🚨 Hey everyone! Moving forward, we will no longer be using this channel for announcements. To make things easier to navigate and keep all the information in one place, all future announcements will be posted in our main Telegram group. 📢 This will be the last announcement in this channel. If you haven’t done so already, join our main group here: https://t.me/DuskNetwork How to Enable Notifications for Announcements in the main channel: 1. Right-click on the “Announcements” topic. 2. Click “Unmute” to enable notifications. If you want to only receive notifications for announcements and mute all other topics: 1. Right-click on any other topic. 2. Click “Mute notifications”. 3. Select either “Mute for x amount of time” or “Mute forever”. In addition, we’ll be hosting more community events on our Discord server going forward! Join here: https://discord.gg/dusk-official Thanks for being a part of our community, and we look forward to seeing you in the main group and on Discord! 😊

NOCTURNE UPDATE Piecrust Optimizations We have been continuing our work on Piecrust optimzations, which focus on scalability and maintaining good performance when high numbers of smart contracts are deployed so that as overall state size grows, performance does not degrade. There are two sides to this, one thing is a good performance per se, which is also being improved, and the other is minimising the dependency on the state size (number of contracts deployed is a similar thing to the state size). We have good results already but we want even better 💪 Edge Case Fixed We fixed an edge case where fixing the issue of next_slot being greater than event_loop https://github.com/dusk-network/rusk/pull/2735 Coming Up We will have an AMA early next week with Ryan and Luca from the BD team. Will share more details in a separate post so the info doesn’t get lost. We are continuing to test in an ongoing and structured manner. The testing is going well and helping us to improve the network. Overall testing and this final push are going well and we can see the finish line in sight ❤️ Reminder We received news from Binance that they are depreciating the BEP2 chain in November. We set a second deadline of Nov 1st to make your BEP2 transfers if you missed the first deadline earlier this year. We will process the transfer after mainnet, but only transfers done before Nov 1st. That’s it for now. See you tomorrow!

NOCTURNE UPDATE The reset went well, and is live and producing blocks 💪 This reset brings with it updates and optimizations which we are pleased about and are working as predicted. Additionally, stake operations (stake/unstake/withdraw) now cost 10 times less. That's all today, and see you tomorrow!

Hey guys! Friendly reminder for all node operators on Nocturne: This update requires a reset. If you're already running a node, follow the instructions here before tomorrow morning 10 AM CEST: https://docs.dusk.network/operator/nocturne/upgrade-node#nocturne-reset If you haven't set up a Nocturne node yet and want to participate, you can follow the guide here: https://docs.dusk.network/operator/nocturne/node-running-guide This reset is required due to a number of improvements we've done to Piecrust, resulting in massive performance gains. Important: The network will do a coordinated start at 10 AM CEST tomorrow Tuesday 22nd, so you have until then to upgrade!

NOCTURNE UPDATE Happy Monday everyone! We have quite a few updates for you today. Nocturne Reset We will be resetting Nocturne tomorrow morning. The timeline is as follows: 16h We will prep the installer for the update 18h We will make the installer available (around this time, not necessarily bang onthe dot) 9h tomorrow the reset will take effect and begin producing new blocks Please see the docs for instructions. https://docs.dusk.network/operator/nocturne/upgrade-node#how-to-upgrade Withdrawing support for Bitfinex We are going to cease direct support for their platform due to regulatory concerns, low liquidity, and lack of support for Mainnet. Let us know if this impacts you in any way. BEP2 Migration We are receiving ongoing questions and requests about the BEP2 migration from April. We will do one more migration, with a deadline of Nov 1st to submit your tokens to be migrated. The migration is done manually and will be completed after mainnet, and requests submitted after the deadline will not be processed. See this guide for instructions on how to do it. https://docs.dusk.network/learn/guides/bep2-migration/ Coming up We have some exciting PRs and updates that are almost ready, including: Rusk wallet overhaul will trigger a new version of the Rusk wallet. We'll release the new Piecrust with an important fix. Given the stability of the consensus, we are going to test the ValidationResult introduction as well as the introduction of the new event-based Stake logic only on some of the nodes. These changes are compatible with the current network, so we don't need to release them to all nodes, but we will stage them on a few of them first.

📢 Discord Revamp Announcement 📢 Hey everyone! 👋🏻 We’ve made some exciting updates to our Discord to make it more organized and engaging for the entire community. Here’s what’s new: 🎉 Community Rewards: By engaging with content, participating in events, and interacting with the community, you can now earn points and unlock exclusive rewards! Head over to #engage on Discord to get started. 🎟 New Ticketing System: Have questions or need help? We’ve implemented a new support ticket system. Just head to #submit-ticket on Discord, and our team will assist you. 🗂 Server Structure: We’ve reorganized the Discord into sections for easier navigation. Key changes include: #updates: Daily/weekly updates and minor announcements. #twitter: Interact with the latest posts and earn points! #official-links: Find all official Dusk resources in one place. #interviews: AMAs and interviews with the team and partners. #marketplace: Redeem your points for exclusive rewards. #share-content: Share your Dusk-related content and support others. #news-digest: Relevant news shared by @kyevanhoot. #suggestions: Submit ideas and feedback to help improve Dusk. 💻 Developer Section: We’ve added #node-runner and #developers-talk channels for more in-depth discussions about tech and development. 🔊 Voice Channels: New voice channels have been added for both the community and developers to hang out and chat in real time. 🚨 If you haven’t joined our Discord yet, now’s the perfect time! Join using this link: https://discord.gg/dusk-official. If you have more ideas feel free to drop them in #suggestions on Discord. Looking forward to hear them! 🙌🏻

NOCTURNE UPDATE I don't have that much to report today, just that everything is going well and we are continuing to optimize and improve the network. We expect this PR to be merged soon https://github.com/dusk-network/rusk/pull/2475 and when it is it will further reduce the probability of losing synchrony with the rest of the network, so look out for this soon! Thank you to everyone who attended and asked questions during the AMA yesterday, we will be doing more with more team members in the future. Have a great weekend!

@everyone NOCTURNE UPDATE Consensus Improvement This update makes the consensus much more robust by shortcircuiting the iteration when a Quorum other than Valid (like Invalid Quorum or No Candidate Quorum ) is reached. This is the PR https://github.com/dusk-network/rusk/pull/2633 And it solves this issue https://github.com/dusk-network/rusk/issues/2301 AMA Don’t forget to join us later today for the AMA with Fulvio and Matteo. It will be held on Discord in the #ama channel. https://discord.gg/dusk-official Coming up We will have some numbers to share soon about the improvement made to our speed and numbers, so keep an eye for those over the next few days. The consensus team are working on some security optimizations, which you can see here: https://github.com/dusk-network/rusk/issues/2483 This issue was not deemed to be compulsory but further reduces any possibility for un-syncing of Provisioners. Technical backlog is running very thin, so good progress is being made.

NOCTURNE UPDATE Welcome to another update! New node installer version You only need to follow the upgrade instructions: https://docs.dusk.network/operator/nocturne/upgrade-node#how-to-upgrade This is not a mandatory release. It fixes a configuration problem with Rusk wallet, fixes the Moonlight unstake operation and stake information provides more information. Network stability improvement Nodes now take into consideration the network before joining in and participating in the consensus activities. As a result, bootstrapping is now much smoother, also when multiple nodes start at the same time. This is the PR https://github.com/dusk-network/rusk/pull/2656 And it solves this issue https://github.com/dusk-network/rusk/issues/2386 New Community Manager! Meet George - I will tag him in a post in the main group and you can see him in the admin list there too - who is joining as our new Community Manager. He will lead our community initiatives and be your go-to contact for questions and support. From George: Hey Dusk fam! 🌟 I’m super excited to introduce myself as the new Community Manager here at Dusk! I’ve been in the Web3 space for 3+ years and gathered extensive experience as a Community Manager for other projects. Professionally, I studied International Marketing, which has helped me understand how to build strong connections with communities like ours. My goal at Dusk is twofold: to be the bridge between you and the team, and also to help amplify our vision so that the world can truly understand what we’re building. I’m committed to inspire our community and ensure that together, we don’t just grow—we become a driving force in the Web3 space. This means: 💠 Communicating all things Dusk—progress, updates, AMAs, and more—with you in an open and transparent way. 💠 Organizing fun and engaging events to bring us all together, and keeping things exciting as we build. 💠 Collaborating with partners to create co-organized events and campaigns that will strengthen our bonds and expand our reach. 💠 And of course, making sure we grow our community even more by creating a space that’s welcoming, vibrant, and focused on our shared goals. Your voice will be a key part of this journey. Whether it’s feedback, suggestions, or just a chat, I’m here to listen. Let’s work together to build something truly visionary—a decentralized, privacy-focused financial system that can redefine how the world thinks about blockchain. I’m really looking forward to what we can accomplish together. Coming up AMA Reminder Don't forget to join us tomorrow at 3 PM CEST for an AMA with Fulvio and Matteo. Please leave your questions in the #ama channel in Discord. Only tech-related questions, future AMAs will feature BD and marketing team members, so let's stick to tech for this one. Discord link: https://discord.gg/dusk-official We also expect a PR related to the consensus to go live soon. Thanks!

NOCTURNE UPDATE We have three main things for you today.. 1. Public docs Our docs are are now public, allowing anyone to open issues, create PRs, and contribute to our documentation. This furthers our commitment to transparency and decentralization within the Dusk ecosystem. We're inviting the community to help keep our docs accurate, relevant, and useful. So check it out and get involved! LINK: https://github.com/dusk-network/docs-public 2. Performance Issue Regarding the performance issue found on our devnet, we're making solid progress. We're currently testing a solution on our devnet Lunare, replicating the conditions where we initially identified the bottleneck. If our testing on devnet proves successful, we'll roll out the fix to Nocturne for further testing by the community. LINK: https://github.com/dusk-network/piecrust/issues/396 3. AMA with Fulvio and Matteo on Thursday We have an AMA with Fulvio, co-founder and CIO, and Matteo, CTO, on Thursday at 3PM CEST. It will be a text AMA, held on Discord, so if you would like to submit questions in advance please use the #ama channel in our Discord server and they will be live on Thursday to answer questions. Best to focus on tech questions for this to the questions relevant and make the most of the time. LINK to the #ama channel: https://discord.gg/3j85tBx7 LINK to the Discord in general: https://discord.gg/dusk-official Coming up The team are working on some important PRs and I hope to have updates tomorrow!

We are pleased to share the Migration Contract Audit Report, performed by Zellic 💪 The report was very positive, finding 0 issues (yes, zero!) and we are pleased to continue driving forward to deliver mainnet. Check out the report below 👇 https://dusk.network/news/migration-contract-audit/

NOCTURNE UPDATE Over the weekend Nocturne has been ticking like a clock, so is looking good in that regard. We also onboarded 50+ nodes that are not ours, so this is great for decentralization and seeing how different nodes and set ups perform. Overall not too much to report, just that we are making good and constant progress and Nocturne is performing well.

Performance Regression And Our Path to Resolution Dear Community, We want to begin by expressing our deep gratitude for the ongoing support, contributions, and patience from all of you as we approach the final stages of our development. As we continue the testing phase, we are encouraged by Nocturne’s overall progress, but we encountered a gradual performance degradation tied to the integration of third-party smart contracts. After deploying over 10,000 large contracts, we noticed a subtle but consistent slowdown in the network's performance, particularly in Dusk VM’s transaction execution. Our team already envisioned a permanent solution and has already implemented an early patch, reducing the bottleneck by 80%. However, the complete solution requires further work to guarantee scalability and a performance baseline that remains unaffected by the size of the state—even with millions of smart contracts deployed on Dusk. Given this, we believe additional time is needed to thoroughly probe the network for any subtle performance degradations that might only manifest after prolonged periods of operation, ensuring the robustness necessary for Mainnet. Needless to say, we are not adding any new feature; our focus is purely on ensuring stability, assessing bugs and potential vulnerabilities, and conducting extensive testing to guarantee the network's resilience under real-world conditions. A key aspect of the testing phase is to uncover and address issues such as these, and while some can be resolved post-launch, others—such as potential impacts on the core protocol or virtual machine—must be tackled before we proceed. We understand the expectations, the sense of anticipation, and the urgency surrounding the launch, but we are committed to a thorough and deliberate approach to safeguard the network's long-term stability and success. We are confident that we are very close to achieving this goal. Although some additional time is necessary, our engineering team has estimated that the ongoing effort would impact the previously envisioned timeline only moderately, and we have already alerted and liaised with our PR partners and selected KOL group about our expectation. Once the current round of probing is complete, we will be in a position to publicly communicate the launch and execute shortly after. Our focus remains on ensuring that Nocturne performs at the level expected of Mainnet and beyond. In the meantime, we are planning regular AMAs with our leadership team, including Co-founder and CIO Fulvio and CTO Matteo, to provide more insights into the technology and development process. This will be followed by discussions with Ryan, Head of BD, and Emanuele C, CMO, who will share more about our strategic direction. Thank you once again for your unwavering support. We look forward to sharing more updates very soon. We will also be answering questions on discord if you want to come over https://discord.gg/dusk-official

NOCTURNE Update We're happy to share that the Nocturne reset went smoothly today, with the network successfully restarting and producing blocks. Thanks to everyone who participated. We will be monitoring the network over the weekend to see how it performs. As mentioned before, this version of Nocturne includes a number of bug fixes to the mempool, optimizations for Kadcast, and improvements in speed when the state of the network grows. There were also updates made to the Rusk wallet and faucet to go along with the reset and bring them in line with the upgrade. If you haven’t already reset your node, here are some guidelines and instructions: If you already have a node setup with version 0.3.2, just run: curl --proto '=https' --tlsv1.2 -sSfL https://github.com/dusk-network/node-installer/releases/download/v0.3.3/node-installer.sh service rusk start This upgrading process is documented here: https://docs.dusk.network/operator/nocturne/upgrade-node#how-to-upgrade If you're about to start running a node on Nocturne, see: https://docs.dusk.network/operator/nocturne/node-running-guide If you ran an earlier version of Nocturne, see: https://docs.dusk.network/operator/nocturne/upgrade-node#nocturne-reset A bit of a lighter Nocturne update today as we are moving over the times and did a bigger one yesterday. I will update you as much as possible over the weekend depending on what info is available, and will resume normal updates on Monday (if there are less over the weekend)

NOCTURNE UPDATES Another update for you today, this time more interactive and requiring action from you. It's time to reset Nocturne. Nocturne Reset We are resetting Nocturne and this means you need to upgrade your nodes. Please find the instructions to upgrade here: https://docs.dusk.network/operator/nocturne/upgrade-node#nocturne-reset And if you don't have a node yet, here are the instructions to get started: https://docs.dusk.network/operator/nocturne/node-running-guide Why the reset? This new version of our network fixes the issues we've seen with the mempool and it makes the network a lot faster when running with a large number of smart contracts (still not as fast as we want though, so we're continuing to improve). We will also give the community a larger portion of the stake (which will continue to grow) and we increase the amount of funds people get from the faucet. This update also comes with a version of Rusk Wallet that fixes a number of issues that the community reported. Important: The network will do a coordinated start at 8AM UTC tomorrow Friday 11th, so you have until then to upgrade. If you miss the deadline: If you're a dry runner, you'll start getting slashed. For everyone else you cannot create transactions until that time has passed. That time is when the consensus will start and will try to make the first block. So, the main highlights of this upgrade are: Fixing mempool issues and making the network faster Higher stake for the community Increased funds from the faucet Rusk wallet fixes Coming up We will closely monitor the reset and continue to work on optimizing Nocturne. I will also start posting these updates in the morning (so from tomorrow morning) as posting them at the end of the day means your questions come up when the team are logging off. By posting earlier in the day it gives more time for the team to reply. Thanks!

Missed the AMA our CEO and co-founder Emanuele Francioni did with Cointelegraph? Check out the article for the highlights, including: - Blockchain and finance - Our NPEX collaboration - Anonymity and compliance - The DLT-TSS license https://cointelegraph.com/news/dusk-ceo-on-regulatory-compliance-and-upcoming-mainnet-launch-ama-recap

We have another update on Nocturne for the community. Node Installer The main issue that was resolved today pertains to the node installer. Activity: Update of the node-installer Highlight: The new version of the installer comes with a new version of Rusk wallet, fixing some known bugs. It also fixes a bug that led to your nodes block height not being retrieved properly through ruskquery block-height. For now, you do not have to do anything, but if you want to you can run the update. Links: https://github.com/dusk-network/node-installer/releases/tag/v0.3.1 Coming up An important issue regarding quorums is currently being worked on but didn't quite make it in time for this update! We are continuing to run tests and find optimizations that will make mainnet even stronger, more scalable, and robust. The testnet is still running, blocks are being created, but transactions are currently not being accepted due to a known bug, which has already been fixed but not deployed. We will run a reset soon through a new version of the node installer to apply it to testnet. PS. We also released a comprehensive update on the work done in August and September so if you'd like to check that out here it is https://dusk.network/news/aug-sept-engineering-update/

Want to see our progress? Our Engineering Update for August and September is live, and it's a long one! Check out the engineering developments at $DUSK, with user-friendly explanations from DevRel Leader, Luca. https://dusk.network/news/aug-sept-engineering-update/

NOCTURNE UPDATES As part of our ongoing commitment to informing the community about our ongoing efforts, here is another update for you. Gas Limit Today a PR was merged regarding gas limits being too low, and in doing so helps to strengthen the resiliance of the network and transactions. Activity: catching too-low-gas-limit at pre-verify stage Highlight: improved network resilience as transactions with too low gas limit won't be propagated at all Links: PR: https://github.com/dusk-network/rusk/pull/2626, issue: https://github.com/dusk-network/rusk/issues/2597 Improvements to the Rusk wallet We made some pretty big improvements to the Rusk wallet Activity: Improve wallet handling in Rusk wallet, fixing the following two bugs: Moonlight addresses are not always accepted as valid BLS keys & Inconsistent address handling Highlight: This is an issue that pops up a lot. Luckily, it's not a breaking change but an issue where the wallet is giving a false-positive on what is a valid Moonlight address or not. The fix will land when we introduce a new version of the node-installer. For people who are really curious, they can either compile the wallet themselves or download a new version here. Links: We tested this with addresses that were reported to not work before. Here's an example transaction that ended up succeeding with the new version where it didn't with the old one: https://testnet.apps.dusk.network/explorer/transactions/transaction/?id=e825ce46d043b72415ec142c98b65f9eb3d2fe12de8bb29b57d3977eb0a5420a This PR makes two crucial changes: first off, it makes Moonlight addresses a first class citizen next to Phoenix. Second, it fixes a common problem. Improved Mempool Management Introduced a parameter to configure the minimum gasLimit required to accept transactions. This allows for early discarding of transactions with a gasLimit that is too low and might otherwise be discarded during the CandidateBlock generation. From now on, when the mempool reaches its transaction limit (which is configurable), instead of discarding every incoming transaction, it will try to prune transactions with the lowest gasPrice to maximize its profit. Transactions with future nonces will no longer be accepted unless the mempool contains the missing nonce chain. This ensures that a transaction will no longer remain pending. It is still possible to submit multiple transactions from the same account as long as they are consecutive. Fixed some bugs related to mempool indexing. Network Fixed a bug that prevented the refresh of the kadcast routing table during the periodic maintenance of peers. Improved error handling when sending UDP packets under stress. Added a ray-id for packet tracking in log=debug mode. Node Improved the node startup at genesis, avoiding stalling and the propagation of unnecessary block request messages. Fixed an edge case where gas_spent resulted higher than gas_limit. API Added nonce information during mempool queries. Added details regarding provisioners (locked amount, fault, and hard_faults). Coming up We are working on sharing more documentation and making it easier to contribute to the documentation yourselves. As a reminder, we'd like to let you know there will be a network upgrade soon and provisioners will need to update their nodes. We will share more info closer to the time but want to put it on your agenda. Until the next update :saluting_face:

NOCTURNE UPDATES After the initial phase of our Test plan, we are now getting into a more involved phase of our journey toward our launch. Moving forward, we are going to provide frequent updates to let the overall community assess the ongoing efforts, participate in the testing activities, and gather greater insights into the improvements we are making. The team has been hard at work and we want to share some of the things the team has been working on. The Faucet The faucet has been upgraded and you can try it out! The faucet is the gateway to testnet, and it is now working better than before. Improvement: Update the faucet to now handle all Moonlight addresses and only rate limit a user when they actually received funds This means that if you make a request from the faucet but it doesn’t go through you will be able to request again and won’t have to wait. Here are instructions to get started 👇 https://docs.dusk.network/operator/nocturne/testnet-faucet Coming up Tomorrow one of the team’s focuses will be on the Rusk wallet and some improvements related to addresses. We are also working on documentation and making it easier to contribute. In the coming days we will also reset Nocturne in order to upgrade the network. This will require action from node runners. We'll provide detailed instructions so this is a heads up for node runners. The team is working flat out to respond to community issues, run tests, and continually upgrade the tech stack. We will continue to update you and share information about the status of testnet and what it means for mainnet.