https://github.com/hazae41/eligos
WebAssembly port of Secp256k1 signatures and key exchange
https://github.com/hazae41/eligos
Last synced: 29 days ago
JSON representation
WebAssembly port of Secp256k1 signatures and key exchange
- Host: GitHub
- URL: https://github.com/hazae41/eligos
- Owner: hazae41
- License: unlicense
- Created: 2023-09-05T21:43:44.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2023-10-12T14:09:54.000Z (over 1 year ago)
- Last Synced: 2025-03-06T16:08:49.632Z (about 2 months ago)
- Language: TypeScript
- Size: 579 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
- Security: SECURITY.md
Awesome Lists containing this project
README
# Eligos
WebAssembly port of Secp256k1 signatures and key exchange
```bash
npm i @hazae41/eligos
```
[**Node Package 📦**](https://www.npmjs.com/package/@hazae41/eligos) • [**Deno Module 🦖**](https://deno.land/x/eligos) • [**Next.js CodeSandbox 🪣**](https://codesandbox.io/p/github/hazae41/eligos-example-next)
## Algorithms
- Secp256k1 from RustCrypto (k256)
## Features
- Reproducible building
- Pre-bundled and streamed
- Zero-copy memory slices
## Building
### Unreproducible building
You need to install [Rust](https://www.rust-lang.org/tools/install)
Then, install [wasm-pack](https://github.com/rustwasm/wasm-pack)
```bash
cargo install wasm-pack
```
Finally, do a clean install and build
```bash
npm ci && npm run build
```
### Reproducible building
You can build the exact same bytecode using Docker, just be sure you're on a `linux/amd64` host
```bash
docker compose up --build
```
Then check that all the files are the same using `git status`
```bash
git status --porcelain
```
If the output is empty then the bytecode is the same as the one I commited
### Automated checks
Each time I commit to the repository, the GitHub's CI does the following:
- Clone the repository
- Reproduce the build using `docker compose up --build`
- Throw an error if the `git status --porcelain` output is not empty
Each time I release a new version tag on GitHub, the GitHub's CI does the following:
- Clone the repository
- Do not reproduce the build, as it's already checked by the task above
- Throw an error if there is a `npm diff` between the cloned repository and the same version tag on NPM
If a version is present on NPM but not on GitHub, do not use!