feat: add non-SHA256 proof of work challenge method by Xe · Pull Request #1151 · TecharoHQ/anubis

Xe · 2025-09-23T03:37:55Z

Closes #283
Closes #1116
Closes #1159

Base implementation in Rust
Base implementation in the client
Add Rust to the build closure in CI
Fix package builds in CI
Fix smoke tests
Documentation
Add wasm feature detection to choose between baseline and simd128
Find a better algorithm than argon2id

This adds Rust to the build closure of Anubis. Any complaints about this will be deleted.

Checklist:

Added a description of the changes to the [Unreleased] section of docs/docs/CHANGELOG.md
Added test cases to the relevant parts of the codebase
Ran integration tests npm run test:integration (unsupported on Windows, please use WSL)
All of my commits have verified signatures

github-advanced-security

check-spelling found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

awilfox · 2025-09-23T03:44:11Z

This adds Rust to the build closure of Anubis. Any complaints about this will be deleted.

Yes hello I would like to complain about the fact it still uses Go. Can't the rest of it be rewritten in Rust, so it can be more portable?

Xe · 2025-09-23T03:44:51Z

This adds Rust to the build closure of Anubis. Any complaints about this will be deleted.

Yes hello I would like to complain about the fact it still uses Go. Can't the rest of it be rewritten in Rust, so it can be more portable?

With enough money, anything is possible :)

Signed-off-by: Xe Iaso <me@xeiaso.net>

…ng to go to bed Signed-off-by: Xe Iaso <me@xeiaso.net>

Xe · 2025-09-28T04:26:39Z

Update: wasm2js has a weird bug involving parsing the output of the Rust compiler. Gonna debug tomorrow when I'm not dog tired. I may need help from a WebAssembly expert on this.

Xe · 2025-09-28T13:50:06Z

Trying this instead: https://www.npmjs.com/package/webassemblyjs

Xe · 2025-09-28T14:47:19Z

This both requires a nightly compiler (to build this with the "MVP" CPU target, or without bulk memory instructions), and doesn't work.

Signed-off-by: Xe Iaso <me@xeiaso.net>

Xe · 2025-09-28T15:04:56Z

I broke the pure JS flow out into #1159.

Closes #1159 This uses the binaryen tool wasm2js to compile the Anubis WASM blobs to JavaScript. This produces biblically large (520Ki) outputs when you inline both hashx and sha256 solvers, but this is a tradeoff that I'm willing to accept. The performance is good enough in my testing with JIT enabled. I fear that this may end up being terrible with JIT disabled. I have no idea if this will work on big endian or not. Signed-off-by: Xe Iaso <me@xeiaso.net>

Xe · 2025-09-30T14:25:33Z

Aha! I figured it out! I have to use wasm2js on the "baseline" build. This causes everything to work correctly.

Signed-off-by: Xe Iaso <me@xeiaso.net>

check-spelling run (pull_request) for Xe/wasm3 Signed-off-by: check-spelling-bot <check-spelling-bot@users.noreply.github.com> on-behalf-of: @check-spelling <check-spelling-bot@check-spelling.dev>

Signed-off-by: Xe Iaso <me@xeiaso.net>

+}
+
+// Example usage:
+const data = hexToUint8Array("98ea6e4f216f2fb4b69fff9b3a44842c38686ca685f3f55dc48c5d3fb1107be4");


+}
+
+// Example usage:
+const data = hexToUint8Array("98ea6e4f216f2fb4b69fff9b3a44842c38686ca685f3f55dc48c5d3fb1107be4");


Signed-off-by: Xe Iaso <me@xeiaso.net>

+
+:::note
+
+The difficulty values for the WebAssembly based checks are going to be much higher than the equivalent difficulty values for the [JavaScript based checks](./proof-of-work.mdx). Generally these count the number of leading _bits_ that much match instead of the number of leading _nibbles_ that must match. Here's a rough translation table:


+
+:::note
+
+This is included mostly as a fallback for usecases that specifically require this hashing function. There are known tools that solve this particular challenge. Prefer [hashx](#hashx) unless you know what you are doing.


Signed-off-by: Xe Iaso <me@xeiaso.net>

s5bug · 2026-06-15T16:31:42Z

What's left to do here (or new now that there's conflicts)?

Xe · 2026-06-15T19:33:03Z

There are a bunch of things I need to do in order to better rethink how this should work. I'm going to start from a fresh fork and publish it as Xe/wasm4. There's been private/offline experimentation and load testing that has informed the designs at play.

Xe · 2026-06-15T21:33:06Z

moved to #1684

s5bug · 2026-06-15T23:51:22Z

Awesome, thx!

Xe self-assigned this Sep 23, 2025

github-advanced-security AI found potential problems Sep 23, 2025

View reviewed changes

feat: add wasm rigging

908f85d

Signed-off-by: Xe Iaso <me@xeiaso.net>

Xe force-pushed the Xe/wasm3 branch from 1254848 to 908f85d Compare September 27, 2025 17:50

Xe added 4 commits September 27, 2025 18:33

chore: add rust-toolchain.toml

03a6c07

Signed-off-by: Xe Iaso <me@xeiaso.net>

feat(web/js): add wasm client side runner

a63cbc7

Signed-off-by: Xe Iaso <me@xeiaso.net>

feat(lib/challenge/wasm): server side validation logic

8999303

Signed-off-by: Xe Iaso <me@xeiaso.net>

ci: fix rust dependencies

f150e4b

Signed-off-by: Xe Iaso <me@xeiaso.net>

github-advanced-security AI found potential problems Sep 28, 2025

View reviewed changes

Comment thread .github/workflows/docker.yml Fixed

Comment thread .github/workflows/rust.yml Dismissed

Comment thread .github/workflows/rust.yml Fixed

Comment thread .github/workflows/rust.yml Fixed

Xe added 9 commits September 28, 2025 02:45

ci: fix rust wasm32 target

9959cb0

Signed-off-by: Xe Iaso <me@xeiaso.net>

ci(packages): fix builds

bed126e

Signed-off-by: Xe Iaso <me@xeiaso.net>

ci: test ssh ci for the wasm stack

1c5ce19

Signed-off-by: Xe Iaso <me@xeiaso.net>

test(ssh-ci): use TecharoHQ/ci-images SSH runner image

41bfbf7

Signed-off-by: Xe Iaso <me@xeiaso.net>

chore(wasm): argon2id -> hashx

8b60b43

Signed-off-by: Xe Iaso <me@xeiaso.net>

fix(lib): detect failures on challenge method initialization

cf931cc

Signed-off-by: Xe Iaso <me@xeiaso.net>

feat(web/wasm): use simd128 if available

097c9e9

Signed-off-by: Xe Iaso <me@xeiaso.net>

chore: cleanups

a0df3d4

Signed-off-by: Xe Iaso <me@xeiaso.net>

feat(web/wasm): start work on wasm2js, found bugs in the code, stoppi…

bd5613c

…ng to go to bed Signed-off-by: Xe Iaso <me@xeiaso.net>

fix: disable broken wasm interpreter flow for now

705da2f

Signed-off-by: Xe Iaso <me@xeiaso.net>

Xe mentioned this pull request Sep 28, 2025

feature: pure JS fallback / WebAssembly interpreter flow #1159

Open

Xe added 2 commits September 30, 2025 14:27

chore: clean up places I forced things in testing

bba000e

Signed-off-by: Xe Iaso <me@xeiaso.net>

ci: fix invocations of setup-binaryen

a29025c

Signed-off-by: Xe Iaso <me@xeiaso.net>

Xe added 2 commits September 30, 2025 14:30

Update metadata

45c9cb6

check-spelling run (pull_request) for Xe/wasm3 Signed-off-by: check-spelling-bot <check-spelling-bot@users.noreply.github.com> on-behalf-of: @check-spelling <check-spelling-bot@check-spelling.dev>

ci: use binaryen 108

2ad7be2

Signed-off-by: Xe Iaso <me@xeiaso.net>

github-advanced-security AI found potential problems Sep 30, 2025

View reviewed changes

Xe added 4 commits September 30, 2025 14:39

fix(wasm): use interpreter on aarch64 for now

7f1a719

Signed-off-by: Xe Iaso <me@xeiaso.net>

docs: add wasm documentation

0699f33

Signed-off-by: Xe Iaso <me@xeiaso.net>

fix(wasm): support loading webassembly again

c04bd48

Signed-off-by: Xe Iaso <me@xeiaso.net>

chore(wasm): spelling fixes

accffa6

Signed-off-by: Xe Iaso <me@xeiaso.net>

github-advanced-security AI found potential problems Sep 30, 2025

View reviewed changes

docs: update CHANGELOG

1530eab

Signed-off-by: Xe Iaso <me@xeiaso.net>

Xe marked this pull request as ready for review September 30, 2025 21:03

docs: update CHANGELOG with binaryen dependency

158a3b8

Signed-off-by: Xe Iaso <me@xeiaso.net>

Xe changed the title ~~feat: add wasm rigging~~ feat: add non-SHA256 proof of work challenge method Sep 30, 2025

ci: fix smoke tests

8cc2c4d

Signed-off-by: Xe Iaso <me@xeiaso.net>

Xe mentioned this pull request Jun 15, 2026

feat: WASM based checks #1684

Open

9 tasks

Xe closed this Jun 15, 2026


		:::note

		The difficulty values for the WebAssembly based checks are going to be much higher than the equivalent difficulty values for the [JavaScript based checks](./proof-of-work.mdx). Generally these count the number of leading _bits_ that much match instead of the number of leading _nibbles_ that must match. Here's a rough translation table:


		:::note

		This is included mostly as a fallback for usecases that specifically require this hashing function. There are known tools that solve this particular challenge. Prefer [hashx](#hashx) unless you know what you are doing.

Uh oh!

Conversation

Xe commented Sep 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-advanced-security AI left a comment

Choose a reason for hiding this comment

Uh oh!

awilfox commented Sep 23, 2025

Uh oh!

Xe commented Sep 23, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Xe commented Sep 28, 2025

Uh oh!

Xe commented Sep 28, 2025

Uh oh!

Xe commented Sep 28, 2025

Uh oh!

Xe commented Sep 28, 2025

Uh oh!

Xe commented Sep 30, 2025

Uh oh!

Uh oh!

Check warning

Check warning

Uh oh!

Uh oh!

Check failure

Check failure

s5bug commented Jun 15, 2026

Uh oh!

Xe commented Jun 15, 2026

Uh oh!

Xe commented Jun 15, 2026

Uh oh!

s5bug commented Jun 15, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Xe commented Sep 23, 2025 •

edited

Loading