A team wants to connect real-world assets to the Dusk ecosystem. Before starting work, they need to pass several checkpoints—each one aligns to a different official interpretation.
First checkpoint: confirm whether the underlying layer can run. Dusk Native L1 is marked as Live, publicly operating, with the network layer in production status. This is the foundation for integration, and the stated source is the official network page.
Second checkpoint: confirm whether the execution environment is mature. DuskEVM and Hedger are marked as Testnet and still in testing. To build applications on top of them, you must evaluate based on their test status—you cannot treat them as a production environment. The stated source is the official documentation.
Third checkpoint: confirm whether the product entry points are open. Dusk Trade defines responsibilities at the application layer for asset discovery, onboarding/access, payment, trading, and settlement. However, the product page is stuck at PRE-LAUNCH. The main entry is the waitlist, and the page numbers are only a preview—real trading has not been opened. The stated source is the product page.
Fourth checkpoint: confirm how far the partnership has progressed. Partnership announcements only prove that announcements were made; they do not prove delivery is complete. The integration status depends on subsequent progress. The stated source is each partnership announcement.
These four checkpoints each have their own definitions. Passing one stage does not imply that all later stages are also passed. Any conclusions from one layer cannot be extrapolated to the entire ecosystem. For assessing whether the team can actually use the system, the key is to anchor judgments to these official interpretations: the underlying layer uses the network page, the execution layer uses the documentation status, the product uses the entry type, and the partnership uses the announcement progress. After verifying all four locations, the conclusion has a basis.
Documentation may describe the full process, but that does not mean it can be used today. Functionality tables are a vision, entry types reflect the current reality, and when validating, you must follow the official labels. When judging maturity, you verify each of the four layers separately: network, execution layer, product, and partnerships. Only then will the conclusion be accurate—and only then can it map to the specific layer you truly need.
Fix the four checkpoints into a team verification template. It can be reused to integrate with any ecosystem that is still being built in phases: first confirm whether the underlying layer can support it, then check whether the execution environment is mature, next confirm whether the product entry point is open, and finally validate the partnership progress. When all four are passed one by one, the judgment has traceable evidence—and you won’t be misled by marketing from any single layer.
@Dusk $DUSK #dusk
First checkpoint: confirm whether the underlying layer can run. Dusk Native L1 is marked as Live, publicly operating, with the network layer in production status. This is the foundation for integration, and the stated source is the official network page.
Second checkpoint: confirm whether the execution environment is mature. DuskEVM and Hedger are marked as Testnet and still in testing. To build applications on top of them, you must evaluate based on their test status—you cannot treat them as a production environment. The stated source is the official documentation.
Third checkpoint: confirm whether the product entry points are open. Dusk Trade defines responsibilities at the application layer for asset discovery, onboarding/access, payment, trading, and settlement. However, the product page is stuck at PRE-LAUNCH. The main entry is the waitlist, and the page numbers are only a preview—real trading has not been opened. The stated source is the product page.
Fourth checkpoint: confirm how far the partnership has progressed. Partnership announcements only prove that announcements were made; they do not prove delivery is complete. The integration status depends on subsequent progress. The stated source is each partnership announcement.
These four checkpoints each have their own definitions. Passing one stage does not imply that all later stages are also passed. Any conclusions from one layer cannot be extrapolated to the entire ecosystem. For assessing whether the team can actually use the system, the key is to anchor judgments to these official interpretations: the underlying layer uses the network page, the execution layer uses the documentation status, the product uses the entry type, and the partnership uses the announcement progress. After verifying all four locations, the conclusion has a basis.
Documentation may describe the full process, but that does not mean it can be used today. Functionality tables are a vision, entry types reflect the current reality, and when validating, you must follow the official labels. When judging maturity, you verify each of the four layers separately: network, execution layer, product, and partnerships. Only then will the conclusion be accurate—and only then can it map to the specific layer you truly need.
Fix the four checkpoints into a team verification template. It can be reused to integrate with any ecosystem that is still being built in phases: first confirm whether the underlying layer can support it, then check whether the execution environment is mature, next confirm whether the product entry point is open, and finally validate the partnership progress. When all four are passed one by one, the judgment has traceable evidence—and you won’t be misled by marketing from any single layer.
@Dusk $DUSK #dusk