You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If DASH is going to succeed at being Digital Cash, it needs to be easy to implement in more places with less concern for auditing and absolutely NO hard reliance on inherently insecure C/C++ code.
AES-GCM and PBKDF2 are widely adopted across many programming languages as part of the standard library. They're also supported by WebCrypto (which means Bun and Node too).
wallet.dat relies on EVP_BytesToKey (Digital EnVeloPe Encryption), which is proprietary to OpenSSL's crypto implementations.
wallet.dat also uses the "outdated" AES-CBC, but this isn't actually an issue for the use case of local storage - if you're afraid that your non-transit storage is adversarial... you have much bigger problems that what AES-GCM can solve for you.
If DASH is going to succeed at being Digital Cash, it needs to be easy to implement in more places with less concern for auditing and absolutely NO hard reliance on inherently insecure C/C++ code.
WebCrypto
(which means Bun and Node too).wallet.dat
relies onEVP_BytesToKey
(Digital EnVeloPe Encryption), which is proprietary to OpenSSL's crypto implementations.wallet.dat
also uses the "outdated" AES-CBC, but this isn't actually an issue for the use case of local storage - if you're afraid that your non-transit storage is adversarial... you have much bigger problems that what AES-GCM can solve for you.See also:
The text was updated successfully, but these errors were encountered: