interledger / interledger/open-payments-node
Transition to SubtleCrypto from Node's crypto module
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 4
- Avg merge
- 27m
- Merged PRs (30d)
- 3
Description
Context
Currently, using @interledger/http-signature-utils and @interledger/open-payments outside of a Node environment is impractical, primarily due to the use on Node's crypto module. The SubtleCrypto API, while accessible in both browser and Node environments, does not yet offer support for Ed25519 or is experimental:
- In Chromium-based browsers, the algorithm is accessible by activating the
Experimental Web Platform Featuresflag - In Firefox there is no support the algorithm;
- Safari has support in a stable release;
- In Node, the Ed25519 algorithm is still considered experimental;
Todos
- Transition to SubtleCrypto from Node's crypto module once the Ed25519 curve support becomes stable across all browsers
-
@interledger/http-signature-utils -
@interledger/open-payments
-
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the cryptographic entry points in @interledger/http-signature-utils and @interledger/open-payments, then check current Ed25519 support in browsers and Node's SubtleCrypto implementation. The work is done when both packages use SubtleCrypto instead of Node's crypto module and the algorithm is stable across the supported browsers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cryptography
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100