#dusk $DUSK @Dusk
One thing I find clever about Dusk is that it doesn’t force every user into the same transaction model.
There’s Moonlight for transparent, account-based activity.
Then there’s Phoenix, which uses notes, nullifiers and zero-knowledge proofs for obfuscated transactions.
That sounds like a small design choice, but for financial infrastructure it’s actually pretty important.
Not every transaction needs to be private.
Not every transaction should be completely public either.
Dusk basically built two lanes for two different needs.
That flexibility is more interesting to me than another chain claiming it has “privacy.”
#dusk @Dusk
$PORTAL
$ACE
Which transaction model would you prefer?
One thing I find clever about Dusk is that it doesn’t force every user into the same transaction model.
There’s Moonlight for transparent, account-based activity.
Then there’s Phoenix, which uses notes, nullifiers and zero-knowledge proofs for obfuscated transactions.
That sounds like a small design choice, but for financial infrastructure it’s actually pretty important.
Not every transaction needs to be private.
Not every transaction should be completely public either.
Dusk basically built two lanes for two different needs.
That flexibility is more interesting to me than another chain claiming it has “privacy.”
#dusk @Dusk
$PORTAL
$ACE
Which transaction model would you prefer?
A) Fully transparent
B) Privacy when needed
C) Fully private
D) Depends on the use case
1 يوم (أيام) مُتبقية