Yesterday we talked about how Dusk@Dusk wants to solve the problems traditional finance encounters when moving into blockchain.
So where exactly is the problem?
Let’s imagine the simplest scenario: a financial institution trading securities on a blockchain.
If all transaction information is public, that means everyone can see in real time what this institution is buying, selling, and trading how much. That might be fine for individual accounts, but for securities, asset management, and institutional trading, it’s not realistic to disclose all information to the public.
But if we hide all information, entirely new problems arise: how can regulators audit? Are the trades legally and compliantly executed? Has the asset been reused or duplicated?
Finance needs privacy, but it cannot lose verifiability.
What Dusk truly wants to build is a blockchain that has both privacy and compliance at the same time—unlike other blockchains that exist in today’s world—not a “more anonymous blockchain.”
Tomorrow I will introduce Dusk’s first-layer technical architecture
#dusk
$DUSK
So where exactly is the problem?
Let’s imagine the simplest scenario: a financial institution trading securities on a blockchain.
If all transaction information is public, that means everyone can see in real time what this institution is buying, selling, and trading how much. That might be fine for individual accounts, but for securities, asset management, and institutional trading, it’s not realistic to disclose all information to the public.
But if we hide all information, entirely new problems arise: how can regulators audit? Are the trades legally and compliantly executed? Has the asset been reused or duplicated?
Finance needs privacy, but it cannot lose verifiability.
What Dusk truly wants to build is a blockchain that has both privacy and compliance at the same time—unlike other blockchains that exist in today’s world—not a “more anonymous blockchain.”
Tomorrow I will introduce Dusk’s first-layer technical architecture
#dusk
$DUSK