Should i Buy $AKE and $TUT ?
i keep thinking the weird part of Dusk Hedger is not even that it keeps DuskEVM financial state confidential. it’s that an encrypted Hedger balance can apparently stay encrypted and still participate in the transaction.
because normally if a balance changes, somewhere the actual number had to become readable first, right?
read the balance. calculate against it. write the new value back. that whole familiar accounting shape. except Hedger is sitting inside DuskEVM with encrypted balances and homomorphic encryption basically refusing that shape. the DuskEVM privacy engine doesn’t need the underlying amount to step into public state just because the encrypted financial state has to change.
and that is where my brain starts fighting it.
Dusk, ElGamal over ECC keeps the Hedger value encrypted, homomorphic computation works against that encrypted value, then the zero-knowledge correctness proof has to show the confidential transfer wasn’t mathematically lying.
so what actually became public enough to trust?
the Hedger balance?
no.
the hidden transaction amount?
still no.
just proof that the encrypted move checked out?
okay... so the value is usable. it just never had to become readable first and idk that feels sharper than saying Hedger gives DuskEVM privacy, because Hedger isn’t hiding the number after DuskEVM finishes with it. the number was already encrypted while the financial operation was happening.
and then i hit the next weird part of Dsuk... DuskDS still has to settle what DuskEVM just did, so does the hidden amount suddenly need to become readable there?
apparently not.
the Dusk Hedger proof can still show the encrypted move checked out while DuskEVM moves toward DuskDS settlement without turning that amount public.
maybe seeing the number was never actually the requirement, maybe proving the hidden number behaved was.
#dusk $DUSK @Dusk
i keep thinking the weird part of Dusk Hedger is not even that it keeps DuskEVM financial state confidential. it’s that an encrypted Hedger balance can apparently stay encrypted and still participate in the transaction.
because normally if a balance changes, somewhere the actual number had to become readable first, right?
read the balance. calculate against it. write the new value back. that whole familiar accounting shape. except Hedger is sitting inside DuskEVM with encrypted balances and homomorphic encryption basically refusing that shape. the DuskEVM privacy engine doesn’t need the underlying amount to step into public state just because the encrypted financial state has to change.
and that is where my brain starts fighting it.
Dusk, ElGamal over ECC keeps the Hedger value encrypted, homomorphic computation works against that encrypted value, then the zero-knowledge correctness proof has to show the confidential transfer wasn’t mathematically lying.
so what actually became public enough to trust?
the Hedger balance?
no.
the hidden transaction amount?
still no.
just proof that the encrypted move checked out?
okay... so the value is usable. it just never had to become readable first and idk that feels sharper than saying Hedger gives DuskEVM privacy, because Hedger isn’t hiding the number after DuskEVM finishes with it. the number was already encrypted while the financial operation was happening.
and then i hit the next weird part of Dsuk... DuskDS still has to settle what DuskEVM just did, so does the hidden amount suddenly need to become readable there?
apparently not.
the Dusk Hedger proof can still show the encrypted move checked out while DuskEVM moves toward DuskDS settlement without turning that amount public.
maybe seeing the number was never actually the requirement, maybe proving the hidden number behaved was.
#dusk $DUSK @Dusk