Add crypto-utils building block using Noble crypto libraries#27
Open
Add crypto-utils building block using Noble crypto libraries#27
Conversation
|
👋 ejacquier, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
timothyF95
previously approved these changes
Feb 6, 2026
building-blocks/crypto-utils/crypto-utils-ts/workflow/package.json
Outdated
Show resolved
Hide resolved
| # In your workflow, reference the chain as evm:ChainSelector:<chain-id>@1.0.0 | ||
| # | ||
| # experimental-chains: | ||
| # - chain-id: 12345 # The numeric chain ID |
There was a problem hiding this comment.
nit: The latest version of CLI changed the naming from chain-id to chain-selector smartcontractkit/cre-cli#252
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new crypto-utils building block that demonstrates how to use cryptographic operations in CRE TypeScript workflows using the Noble crypto libraries as an alternative to the Node.js
cryptomodule.Why this is needed
The CRE TypeScript SDK runs on QuickJS, which doesn't support Node.js native modules. This means
require('crypto')doesn't work. Noble libraries are pure JavaScript and work perfectly in QuickJS.What's included
Math.random()polyfill (ChaCha8Rng)Random bytes
Noble's
randomBytes()fails because it needscrypto.getRandomValues, but CRE provides aMath.random()polyfill using ChaCha8Rng that is consensus-safe. The template shows how to build your ownrandomBytes():Documentation
Test plan