Ripple has updated its core cryptographic dependency, @noble/hashes, to version 2.0.1, a major bump that may introduce breaking changes for developers.
> impact
We have updated the dependency on `@noble/hashes` from version 1.8.0 to 2.0.1 across our relevant libraries. This represents a major version upgrade for a critical component responsible for cryptographic hashing functions within the Ripple ecosystem.
This update is essential for maintaining best-in-class security and performance. The `@noble/hashes` library is independently audited and widely trusted. By moving to the latest major version, we ensure Ripple benefits from the most recent security enhancements, performance optimizations, and modern JavaScript practices, which is non-negotiable for libraries handling cryptographic operations.
The primary impact on developers is the potential for breaking changes, as is common with major version bumps. Any projects that directly or indirectly interact with hashing functions via Ripple's libraries should be reviewed for compatibility. We recommend consulting the official `@noble/hashes` changelog to understand the specific API changes between v1.x and v2.x and running a full test suite after updating your Ripple dependencies.
> Try this now
try this
# 1. Check your project's dependency tree for the old version.
# This command will show you if you are using a pre-2.0.0 version of @noble/hashes,
# likely as a transitive dependency from an older Ripple library.
npm ls @noble/hashes
# Example Output (Potentially Problematic):
# your-project@1.0.0 /path/to/your-project
# └─┬ ripple-lib@1.10.0
# └── @noble/hashes@1.8.0
# 2. Update your Ripple dependencies to the latest version.
# This will pull in the new version that correctly bundles @noble/hashes@2.0.1.
npm install ripple-lib@latest
# 3. Verify the update was successful by running the check again.
# The output should now reflect the new, updated version.
npm ls @noble/hashes
# Expected Output (After Update):
# your-project@1.0.0 /path/to/your-project
# └─┬ ripple-lib@1.11.0
# └── @noble/hashes@2.0.1
# 4. Finally, re-run your entire test suite.
# This is the most critical step to catch any regressions or breaking changes
# introduced by the major version bump in the hashing library.
npm test