I went looking for how "native issuance" actually shows up in Dusk's own products. What I found was the word "tokenized" instead.
Dusk's own materials draw a sharp line: tokenization just puts a digital skin on assets still governed by legacy systems, while native issuance creates the asset fully on-chain from day one. Dusk positions itself as the one built for the second, not the first.
Then I checked Dusk's own documentation for Dusk Trade, its flagship application layer for real-world assets. It describes Dusk Trade as "the application layer for tokenized financial assets on Dusk."
Same company, across its own materials, two different words for what it's building.
Maybe the underlying issuance is native and only the application layer speaks in tokenization terms. Maybe not. Dusk's own writing doesn't say.
When Dusk calls Trade an application layer for tokenized financial assets, where exactly does native issuance begin, and tokenization end?
@Dusk #dusk $DUSK
Dusk's own materials draw a sharp line: tokenization just puts a digital skin on assets still governed by legacy systems, while native issuance creates the asset fully on-chain from day one. Dusk positions itself as the one built for the second, not the first.
Then I checked Dusk's own documentation for Dusk Trade, its flagship application layer for real-world assets. It describes Dusk Trade as "the application layer for tokenized financial assets on Dusk."
Same company, across its own materials, two different words for what it's building.
Maybe the underlying issuance is native and only the application layer speaks in tokenization terms. Maybe not. Dusk's own writing doesn't say.
When Dusk calls Trade an application layer for tokenized financial assets, where exactly does native issuance begin, and tokenization end?
@Dusk #dusk $DUSK
