“Success” in the product is not a visual effect—it’s a sentence that users, customer support, and integrators will use to make decisions. As long as it doesn’t specify which layer the success refers to, the next person will fill in the meaning with their own understanding: some take it as “the request has been received,” some as “execution is complete,” and some interpret it directly as “the business can already be booked.” The issue isn’t that there aren’t enough green checkmarks—it’s that the same word carries promises that are mutually different.
DuskEVM provides familiar EVM tools and an execution environment, while also obtaining settlement and data availability through DuskDS. Per the documentation, a single transaction may involve, in sequence: the sequencer recording it, L2 block execution, the batcher publishing data to DuskDS, and the connection between state commitments, fault proofs, and the settlement layer. This isn’t about putting every protocol term into the interface. On the contrary—the interface should translate terminology into actionable states, rather than covering up the differences with a vague “success.”
For example, the product can leave “request received” for the submission action, “executed” for the computation result, “data published” for the corresponding evidence, and “processable by settlement status” for the stage that has clear protocol backing. The exact wording can vary, but each term should be able to answer the same question: what does it prove, and what has it not yet proved. That way, when integrators receive status callbacks, they won’t mistake early feedback for the final business result, and users won’t be forced to guess the meaning of an empty-looking page.
Status copy is often seen as a minor detail, but in reality it determines who will misjudge first when a fault occurs. If “recorded” is said to mean “completed,” troubleshooting will begin at the wrong layer; if the execution result is called “final,” subsequent processing will lose its boundaries. Making status names more specific isn’t about adding steps—it’s about clearly separating what the system has already confirmed from what still needs verification. For products involving DuskEVM, an accurate notice reduces misunderstanding more than a lively but vague “transaction successful.”
@Dusk $DUSK #dusk
DuskEVM provides familiar EVM tools and an execution environment, while also obtaining settlement and data availability through DuskDS. Per the documentation, a single transaction may involve, in sequence: the sequencer recording it, L2 block execution, the batcher publishing data to DuskDS, and the connection between state commitments, fault proofs, and the settlement layer. This isn’t about putting every protocol term into the interface. On the contrary—the interface should translate terminology into actionable states, rather than covering up the differences with a vague “success.”
For example, the product can leave “request received” for the submission action, “executed” for the computation result, “data published” for the corresponding evidence, and “processable by settlement status” for the stage that has clear protocol backing. The exact wording can vary, but each term should be able to answer the same question: what does it prove, and what has it not yet proved. That way, when integrators receive status callbacks, they won’t mistake early feedback for the final business result, and users won’t be forced to guess the meaning of an empty-looking page.
Status copy is often seen as a minor detail, but in reality it determines who will misjudge first when a fault occurs. If “recorded” is said to mean “completed,” troubleshooting will begin at the wrong layer; if the execution result is called “final,” subsequent processing will lose its boundaries. Making status names more specific isn’t about adding steps—it’s about clearly separating what the system has already confirmed from what still needs verification. For products involving DuskEVM, an accurate notice reduces misunderstanding more than a lively but vague “transaction successful.”
@Dusk $DUSK #dusk