Skip to content

doc: why isn't this compatible with wallet.dat encryption? #1

@coolaj86

Description

@coolaj86

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.

  1. 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).
  2. wallet.dat relies on EVP_BytesToKey (Digital EnVeloPe Encryption), which is proprietary to OpenSSL's crypto implementations.
  3. 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:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions