// the find
fluencelabs/nox
Rust implementation of the Fluence network peer
Nox is the Rust node implementation for the Fluence decentralized compute network — it acts as both a relay for clients and a host for WASM-based worker services. It's for developers building on or operating within the Fluence network, not for general-purpose P2P experimentation.
The workspace is well-decomposed: 30+ crates with tight boundaries (chain-connector, chain-listener, spell-event-bus, core-distributor) rather than one monolithic node binary. The chain integration is first-class — separate crates for ABI decoding, event listening, and proof tracking suggest real production use, not a prototype. Test infrastructure is solid: nextest config, dedicated nox-tests crate with pre-compiled WASM fixtures for integration testing, and a chain_listener test that spins up mock servers rather than hitting a live chain. The aquamarine VM pool design (actor.rs, vm_pool.rs, plumber.rs) handles the concurrency story for running AIR scripts across multiple VMs without a global lock.
The README is nearly useless — it's four sentences and a docker run command. There's no architecture overview, no explanation of what Aquamarine/AIR/particles are, and no guide for running a development cluster. The entire project is load-bearing infrastructure for the Fluence network specifically; if Fluence as an organization pivots or folds, this code has no standalone use case. The AGPL v3 license plus a separate CLA is a friction combination that will deter most casual contributors. The vm-utils crate ships a test QCOW2 image in the repo (tests/alpine-virt-3.20.1-x86_64.qcow2) — binary blobs in git history are a long-term maintenance problem.