Composability is often celebrated in blockchain, but in regulated finance, flexibility can be a liability. DUSK takes a different approach.
Most blockchain ecosystems treat composability as a core advantage, allowing protocols to be freely combined, extended, and reused. DUSK intentionally does not follow this model. For regulated financial infrastructure, unrestricted composability introduces execution risk, audit ambiguity, and compliance uncertainty. Limiting composability is a deliberate design choice to protect outcome integrity.
In open composable environments, execution paths multiply and dependencies become unpredictable. Auditing becomes application-specific rather than systemic, and changes in one protocol can unexpectedly affect outcomes in another. While this flexibility accelerates experimentation, it makes execution behavior difficult to reproduce and verify. For regulated assets, this unpredictability is unacceptable.
Financial workflows require deterministic execution, clearly defined state transitions, and verifiable compliance. When execution logic spans multiple composable layers, accountability becomes unclear, disputes are harder to resolve, and auditability is reduced. DUSK avoids this by constraining execution paths at the protocol level.
By prioritizing protocol-defined execution behavior, limited interaction surfaces, and network-wide enforcement of rules, DUSK ensures consistent verification across validators. These constraints are intentional. They maintain predictable, reproducible, and verifiable financial outcomes under regulatory scrutiny.
DUSK is not trying to be the most composable blockchain. It is built to support financial workflows that must withstand audits, regulatory oversight, and dispute resolution. Limiting composability is not a compromise — it is a design decision aligned with the realities of regulated finance.
