@hisoka-io/anon-rpc-worker 0.0.0-stage → 0.2.0

package/CHANGELOG.md

@@ -0,0 +1,62 @@
+# Changelog
+
+All notable changes to `@hisoka-io/anon-rpc-worker`.
+
+## 0.2.0 (2026-10-06)
+
+Built on `@hisoka-io/nox-client` 0.6.0 (`kps.discovery`). Every 0.1.0 config stays valid.
+
+### Added
+
+- Discovery (S1): identity from the snapshot and NoxRegistry, location looked up at run time. The bundle pins a
+  `nox-anon-rpc-bootstrap/1` file next to the snapshot: default anchors nox-1, nox-2 and nox-8 on their Elastic IPs,
+  the registry implementation, two keyless Arbitrum Sepolia RPC providers of different organisations and the
+  discovery policy. An empty config boots on those anchors.
+- Chain checks through the mixnet after ready: two exits to two providers at one finalized block, used on
+  byte-identical agreement only; location updates, removals, new members on probation (1 per route, 14 days).
+- Config: `bridges` (only addresses ever dialled), `registryRpcUrls`, `chainQuorum`, `discovery`
+  (`"chain"` / `"snapshot"`), reserved `trust` and `checkpoint`.
+- Learned-anchor cache `nox/v1/anchors` (public chain data, at most 32 entries, 30 days), validated whole and
+  confirmed through `/metadata.json` before use.
+- Build: `--bootstrap`, bootstrap digest in the build record and provenance; the test-bed build writes a bed
+  bootstrap (local providers, anchors, short check interval).
+
+- Release snapshot of NoxRegistry at Arbitrum Sepolia block 316207920 (10 members; nox-1, nox-2 and nox-8 publish
+  their KPS addresses), read and re-verified byte for byte through two RPC providers.
+- `verify-reproducible.sh --native` (a third build with host tools next to the two container builds) and `--bwrap`
+  (host builds at the container paths for hosts without a container runtime).
+
+### Changed
+
+- `gateways` no longer has to be a pinned member's published address; gateways are tried first in place of the
+  default anchors instead of restricting entries. After the gateways, the worker may dial the default anchors and
+  other published entries. Wallets that used `gateways` to keep traffic on chosen addresses switch to `bridges`,
+  which the worker treats as the only addresses it ever dials.
+- A gateway or bridge must answer `/metadata.json` with the node it serves (nox-kps `node_address`), and that node
+  must be a member in the bundle's snapshot.
+
+### Fixed
+
+- Reproducible WASM across checkout paths: `reproducible-rustc.sh` strips the cargo home, sysroot and workspace
+  prefixes only at the start of a source path. A checkout at a path such as `/src` used to rewrite the
+  `registry/src/` part of every dependency path, which changed each crate's `-C metadata` and the module bytes.
+
+## 0.1.0
+
+First version of the Nox mixnet worker for the anon-rpc standard (SPEC 0.3.2), built on
+`@hisoka-io/nox-client` 0.5.0 in KPS mode.
+
+### Added
+
+- The worker: boots from the NoxRegistry snapshot pinned in the bundle, dials Nox entry nodes through
+  `anonRpcWorker.kps`, and serves `fetch` calls as Nox HTTP requests through an exit, with JSON-RPC aware reply
+  sizing and retries for reads, per-call deadlines and abort, `fetch`-style redirects and stable `signalFailed` and
+  per-call error codes. The config is optional and validated before ready.
+- A reproducible single-file bundle: the nox-wasm module and the snapshot are embedded, the snapshot byte for byte;
+  the SDK's ambient `fetch` and `WebSocket` defaults are replaced by a stand-in that fails closed, and the build
+  checks the output for other network APIs. Provenance records the toolchain and every input digest.
+- Snapshot tools: generation from the chain, offline and on-chain verification, and a release gate that requires
+  every member's KPS address and two RPC providers.
+- Worker specifier contracts (the reference `WorkerSpecifier` and an `ImmutableWorkerSpecifier`) with a read-only
+  deploy planner and inspector.
+- An end-to-end test bed: a local Nox mesh with `nox-kps` sidecars and the reference harness in headless Chromium.

package/LICENSE

@@ -0,0 +1,190 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by the Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding any notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2026 hisoka-io
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,3 +1,197 @@
-# Temporary Holding Version
+# @hisoka-io/anon-rpc-worker
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+The Nox mixnet worker for the [anon-rpc](https://github.com/ethereum/anon-rpc) standard: one classic-script
+bundle that a wallet's anon-rpc harness loads and pins by its keccak-256 hash.
+
+The worker dials Nox entry nodes over KPS (`anonRpcWorker.kps`), sends each `fetch` call as a Sphinx packet
+through the mixnet, and an exit node performs the HTTP request; the reply returns over single-use reply blocks
+(SURBs). Who the nodes are comes from NoxRegistry: a snapshot pinned inside the bundle is the floor, and after
+ready the worker reads the registry through the mixnet itself. Where the nodes are (IP, port, KPS certhash) is
+looked up at run time, so operators change IPs whenever they like and new nodes join without a new bundle. A cold
+boot needs no seed server and no public RPC; the bundle reaches the network only through the harness's KPS dialer.
+
+What each party sees: the entry node sees the wallet's IP address and encrypted packets; the exit node sees the
+HTTP request (RPC URL, headers it forwards, body) and never who sent it. End-to-end TLS inside the worker,
+which also hides the request from the exit, is the next milestone.
+
+## Layout
+
+| Path | Contents |
+|---|---|
+| `src/` | The worker: `worker.ts` (bundle entry), `core.ts` (boot, readiness, accept loop, deadlines), `config.ts`, `fetch-map.ts` (`fetch` to Nox `HttpRequest`), `jsonrpc.ts`, `errors.ts`, `log.ts`, `storage.ts`, `spec-types.ts` (anon-rpc SPEC 0.3.2 worker types) |
+| `snapshot/` | The pinned registry snapshot, its keccak-256, JSON Schema and reviewed capability hints, and the discovery bootstrap (`nox-bootstrap.json`) |
+| `scripts/` | Snapshot generator and verifier, reproducible WASM and bundle build, hashing, provenance |
+| `specifier/` | Worker specifier contracts (Foundry) and a read-only deploy planner and inspector |
+| `e2e/` | End-to-end test bed: a local Nox mesh with `nox-kps` sidecars, the reference harness in headless Chromium |
+
+## Configuration
+
+`anonRpcWorker.config` is optional; `undefined` and `{}` boot on the anchors pinned in the bundle. Every field is
+optional, and every config valid for 0.1.0 stays valid:
+
+| Field | Type | Default | Range and meaning |
+|---|---|---|---|
+| `v` | number | 1 | must be 1 |
+| `gateways` | string[] | the bundle's default anchors | 1-16 unique KPS addresses (`<ip>:<port>:<certhash>`, no DNS names), tried first in place of the default anchors. Any address is accepted: the node behind it must name an eligible member in its `/metadata.json` before the worker routes through it |
+| `bridges` | string[] | none | 1-16 KPS addresses. When set, the worker dials **only** bridges and never a published Nox address (Tor bridge semantics). Each bridge's `/metadata.json` names the member it serves (nox-kps `node_address`), which must be in the bundle's snapshot. Excludes `gateways` |
+| `registryRpcUrls` | string[] | the bundle's list | 2-8 `https:` URLs, replacing the bundle's registry RPC providers (for example a wallet's own Arbitrum node) |
+| `chainQuorum` | integer | 2 (bundle policy) | 2-4 (exit, provider) pairs that must answer byte for byte the same; a check waits when fewer distinct exits or providers are available |
+| `discovery` | `"chain"`, `"snapshot"` | `"chain"` | `"snapshot"`: no registry reads, the pinned snapshot is the only membership source (0.1.0 behaviour, no RPC provider involved) |
+| `trust` | `"auto"` | `"auto"` | reserved for proof-backed discovery; any other value fails with `bad-config` |
+| `checkpoint` | | | reserved; any value fails with `bad-config` |
+| `logLevel` | `"debug"`, `"info"`, `"warn"`, `"error"` | `"info"` | |
+| `attemptTimeoutMs` | integer | 12,000 | 3,000-60,000 |
+| `callDeadlineMs` | integer | 25,000 | at least `attemptTimeoutMs`, at most 120,000 |
+| `maxConcurrentCalls` | integer | 16 | 1-64 |
+| `maxRequestBytes` | integer | 1,048,576 | 1,024-4,194,304 |
+| `maxResponseBytes` | integer | 8,388,608 | 65,536-67,108,864 |
+| `surbFormat` | `"auto"`, `"v1"`, `"v2"` | `"auto"` | |
+| `claimIntervalMs` | integer | 200 | 50-2,000 |
+| `bootRetryMaxMs` | integer | 60,000 | 5,000-300,000 |
+| `topologySources` | integer | 2 | 1-4 |
+| `warmup` | boolean | false | one echo through a full route before ready |
+
+An unknown key, a wrong type or an out-of-range value fails the boot with `bad-config`, naming the field.
+
+Examples:
+
+- default wallet: no config, or `{}`;
+- censored user: `{ "bridges": ["203.0.113.9:15005:uEiB..."] }`;
+- adopters listing `exampleConfig`:
+
+```json5
+{ gateways: ["100.56.0.72:15005:uEiBVDwIs40bsslDkM-BYb2AOHw3PHe70_bj5U_09r7vdIQ"] }
+```
+
+## Discovery (identity from chain, location at run time)
+
+The bundle pins `snapshot/nox-bootstrap.json` (`nox-anon-rpc-bootstrap/1`) next to the snapshot, both covered by
+the worker hash:
+
+| Field | Value |
+|---|---|
+| `anchors` | nox-1 `100.56.0.72:15005`, nox-2 `3.232.137.146:15005`, nox-8 `18.215.18.61:15005` (Elastic IPs) with their KPS certhashes |
+| `registry`, `registryImpl` | NoxRegistry `0xf7bf...6cb6` on Arbitrum Sepolia (421614), implementation `0x7285...e2a2` behind the EIP-1967 proxy |
+| `registryRpcUrls` | `https://sepolia-rollup.arbitrum.io/rpc` (Offchain Labs) and `https://arbitrum-sepolia-testnet.api.pocket.network` (Pocket Network): keyless, and checked through the live exits for `finalized`, EIP-1898 block-hash reads at the finalized block and 20-call batches. Tenderly's and Tatum's public gateways rate-limit or charge for those batches, PublicNode prunes the state of the finalized block, dRPC's free tier caps batches at 3 calls; a wallet can add its own providers with `registryRpcUrls` |
+| `policy` | quorum 2, state at most 3,600 s old, check every 600 s, at most 1 member on probation per route, probation 14 days, removals need 2 anchors, 2 members per layer |
+
+Boot: the worker dials, in priority classes and shuffled within each, bridges only (when set); otherwise the
+wallet's gateways or the bundle's anchors, then learned anchors, then the snapshot's KPS addresses, three at a time.
+As soon as one anchor serves an acceptable topology it signals ready (boot time unchanged). Served topologies are
+judged on identity (address, Sphinx key, role): a changed IP is a move, never a removal.
+
+After ready, the SDK reads NoxRegistry at one finalized block through the mixnet: two different exits to two
+different providers, every call pinned to the block hash. It uses the answer only when both pairs agree byte for
+byte, the registered members close the set (`relayerCount()` and the XOR `topologyFingerprint()`), and the proxy
+still points at the implementation the bundle knows. The answer updates locations and removes members (each route
+layer keeps at least two snapshot members); a member outside the snapshot is on probation for 14 days after the
+worker first saw it, and a route holds at most one such member. Checks repeat every 10 minutes, and early when a
+served fingerprint differs or every entry failed. Log events: `discovery.verified`, `discovery.disagreement`,
+`discovery.incomplete`, `discovery.rejected`, `discovery.probation`, `discovery.floor`, `discovery.failed`.
+
+What each party learns: RPC providers see exit IPs and public registry reads, never the wallet's address. Until
+TLS runs inside the worker, the exits terminate HTTPS, so the two-exit quorum is attested by the exits; probation
+and the snapshot floor bound what a forged answer can change. If every chain path fails, the worker keeps working
+on the snapshot floor.
+
+Operators move by sending `updateUrl` / `updateMetadataUrl` from the node key (self-service, about 0.00002 ETH);
+running workers pick the new address up within about 10 minutes.
+
+## Readiness and failure codes
+
+The worker signals ready once the config is valid, the embedded WebAssembly is initialised, the pinned snapshot
+verifies, a KPS entry has answered and a served topology was accepted. Transient faults (no entry reachable,
+a topology fetch failing) are retried with back-off while `ready` stays pending.
+
+`signalFailed` codes: `bad-config`, `unsupported-platform` (no KPS dialer, `crypto.getRandomValues` or
+WebAssembly), `wasm-blocked` (the embedder's CSP must allow `'wasm-unsafe-eval'`), `snapshot-invalid`,
+`snapshot-invalid` also covers an invalid discovery bootstrap. `snapshot-stale` (two or more nodes agree the registry no
+longer lists any known member of a route layer with its identity, and a chain check does not resolve it: a newer
+bundle is due) and `internal-error`. Members that are listed but reported offline, as while
+nodes reconnect after a restart, keep the worker running: calls through them fail one by one (`timeout` or
+`network-error`) until a topology refresh sees them online.
+
+A rejected call carries a string `code`: `cancelled` (`AbortError`), `timeout`, `network-error`, `too-large`,
+`unsupported`, `protocol-error` or `internal-error`. Redirects follow `fetch` rules inside the call deadline (at
+most 5 hops). `eth_sendRawTransaction` is sent once and never resent; after a `timeout`, check the receipt by
+transaction hash.
+
+## Storage
+
+The worker stores public network state only, under `nox/v1/`: members recent topologies removed (reorders anchors)
+and the learned-anchor cache (`nox/v1/anchors`): KPS addresses verified chain checks confirmed, with the block they
+were read at, and when each member outside the snapshot was first seen. At most 32 anchors, each dropped after 30
+days. A cache that fails any check (another registry, too many records, one malformed record) is ignored whole, and
+a learned address is used only after the node's `/metadata.json` names the same member.
+
+## What the bundle contains
+
+- `dist/anon-rpc-worker.js`: a single IIFE built by esbuild (target es2022, not minified, so it can be read
+  and audited). Every module is inlined: the worker source, the `@hisoka-io/nox-client` sources, the
+  `nox-wasm` WebAssembly module (base64), the pinned registry snapshot and the discovery bootstrap, each embedded
+  byte for byte as one string.
+  The bundle has no imports and never loads code or WebAssembly by URL. The SDK's ambient `fetch` and
+  `WebSocket` defaults are replaced at build time by a stand-in that fails closed, and the build checks the
+  output for any other network API.
+- `dist/anon-rpc-worker.js.keccak256`: the Ethereum keccak-256 of those exact bytes, the value a worker
+  specifier pins as `workerHash()`.
+- `dist/anon-rpc-worker.provenance.json`: source commit, toolchain versions, input digests (snapshot, bootstrap,
+  WASM, lockfile) and output digests.
+
+## Pinned registry snapshot
+
+`snapshot/nox-snapshot.json` (format `nox-anon-rpc-snapshot/1`, schema in `snapshot/nox-snapshot.schema.json`)
+records every NoxRegistry member on Arbitrum Sepolia at one block: address, Sphinx key, routing and ingress
+URLs, `metadataUrl` (where each node publishes its KPS address as `kps:<ip>:<port>:<certhash>/metadata.json`),
+stake, role, layer, status, and reviewed capability hints from `snapshot/capabilities.json`. Its topology
+fingerprint is computed with the SDK's own `computeTopologyFingerprint` and equals the registry's on-chain
+`topologyFingerprint()` at that block.
+
+Nodes may serve fresher topology over KPS. The worker uses it for liveness and removals (only when two different
+nodes agree, keeping at least two members per route layer) and for moved routing addresses two nodes agree on;
+additions and confirmed locations come from the chain check.
+
+The committed release snapshot is of block 316207920 (finalized, read and re-verified byte for byte through two RPC
+providers of different organisations). It carries the KPS addresses nox-1, nox-2 and nox-8 publish, so the worker
+finds its entries from the snapshot alone, and the default anchors and the chain check add any later moves.
+The release gate names the seven mix and exit nodes, which serve the mixnet without a KPS listener, with
+`--allow-missing-kps`.
+
+```bash
+pnpm --filter @hisoka-io/nox-client build
+node scripts/make-snapshot.mjs --rpc <arbitrum-sepolia-rpc> --rpc <second-rpc> [--block <n>]
+node scripts/verify-snapshot.mjs --offline                           # schema, hashes, SDK-derived fields
+node scripts/verify-snapshot.mjs --rpc <rpc> --rpc <rpc> --release   # chain re-read + every member publishes a KPS address
+```
+
+## Building and checking the hash
+
+```bash
+corepack enable && pnpm install --frozen-lockfile
+bash packages/anon-rpc-worker/scripts/build-worker.sh --release   # pinned toolchain, clean tree
+node packages/anon-rpc-worker/scripts/hash.mjs packages/anon-rpc-worker/dist/anon-rpc-worker.js
+```
+
+`scripts/toolchain.env` pins every tool that shapes the bytes: the Node and Rust container images by digest,
+rustc, wasm-pack, wasm-bindgen and binaryen (with sha256 digests of their release archives); pnpm comes from the
+repository's `packageManager` field and esbuild from the lockfile. `scripts/build-wasm.sh` follows the
+tor-js recipe: path remapping, a `RUSTC_WRAPPER` that makes cargo's metadata host-independent, `--locked`, and
+a pinned `wasm-opt` on `PATH`.
+
+`scripts/verify-reproducible.sh` builds a commit twice from clean `git archive` exports in fresh containers
+of the pinned images, at two different paths, and compares the WASM, bundle and provenance digests
+(`--local` does the same with the host's tools). `--native` adds a third build with the host's tools to the two
+container builds and requires all three to match; `--local --bwrap` runs the two host builds in bubblewrap mount
+namespaces at the container paths, for hosts without a container runtime.
+
+For a test bed, `node scripts/build.mjs --snapshot <file>` embeds another canonical snapshot (for example a
+local mesh); the provenance records which snapshot a bundle carries.
+
+## Tests
+
+```bash
+pnpm --filter @hisoka-io/anon-rpc-worker test     # worker, SDK integration over an in-memory KPS network, build
+pnpm --filter @hisoka-io/anon-rpc-specifier test        # Foundry and harness-path tests (forge, anvil)
+```
+
+The end-to-end bed has its own lockfile: see `e2e/README.md`.