I checked which Dusk products are actually live
#dusk
Status language drifts as it travels. Announcement, testnet, alpha, launch, all of it flattens into the word "live" by the time it reaches an exchange feed.
Dusk publishes its own answer, and it is more precise than what gets repeated. The homepage carries a stack panel with four rows. The L1 reads Live. DuskEVM reads Testnet. Hedger reads Testnet. Dusk Trade reads Building.
The developer docs match. The quickstart is titled deploy a Solidity contract to DuskEVM Testnet, and it publishes exactly one network: chain ID 745, on rpc.testnet.evm.dusk.network. No mainnet chain ID appears anywhere in the docs.
What makes this more than a version-number quibble is the dependency stack. Dusk's core components page states that Hedger runs on DuskEVM. Dusk Trade is a waitlist with a sign-up form. The confidential token standard and the trading venue both inherit whatever DuskEVM's status happens to be.
@Dusk announced the public testnet on December 5 2025 and described it as the final stage before mainnet. Then on January 17 2026 the bridge incident notice paused bridge services and said the team would share a confirmed plan and timeline for resuming the DuskEVM launch. I have looked through the news page and the account since. Aegis in March, Dusk Connect in April, Boreas in May. No revised mainnet date in any of them.
I want to be exact about one thing, because most of the confusion sits here. The Dusk L1 has been live since January 7 2025. That is genuine and independently checkable. The exchange posts announcing a live DuskEVM mainnet are describing the layer underneath it. $DUSK
So how much of a regulated markets story can be true while the layer carrying it is still issuing testnet DUSK?
#dusk
Status language drifts as it travels. Announcement, testnet, alpha, launch, all of it flattens into the word "live" by the time it reaches an exchange feed.
Dusk publishes its own answer, and it is more precise than what gets repeated. The homepage carries a stack panel with four rows. The L1 reads Live. DuskEVM reads Testnet. Hedger reads Testnet. Dusk Trade reads Building.
The developer docs match. The quickstart is titled deploy a Solidity contract to DuskEVM Testnet, and it publishes exactly one network: chain ID 745, on rpc.testnet.evm.dusk.network. No mainnet chain ID appears anywhere in the docs.
What makes this more than a version-number quibble is the dependency stack. Dusk's core components page states that Hedger runs on DuskEVM. Dusk Trade is a waitlist with a sign-up form. The confidential token standard and the trading venue both inherit whatever DuskEVM's status happens to be.
@Dusk announced the public testnet on December 5 2025 and described it as the final stage before mainnet. Then on January 17 2026 the bridge incident notice paused bridge services and said the team would share a confirmed plan and timeline for resuming the DuskEVM launch. I have looked through the news page and the account since. Aegis in March, Dusk Connect in April, Boreas in May. No revised mainnet date in any of them.
I want to be exact about one thing, because most of the confusion sits here. The Dusk L1 has been live since January 7 2025. That is genuine and independently checkable. The exchange posts announcing a live DuskEVM mainnet are describing the layer underneath it. $DUSK
So how much of a regulated markets story can be true while the layer carrying it is still issuing testnet DUSK?
