cybernode — the node of the soft3 ladder
rung 7 of soft3: one binary that runs any compatible network instance as data, and owns everything networked — the phase-1 root chain kernel, the wire and sync, routing, mining, the genesis pipeline, the wallet, the HTTP surface. its planes stay where network-planes put them: radio reaches, sync reconciles, foculus agrees, solong rewards. cybernode.ai is the reference instance, operated by cyberia; an instance is cybernode plus a manifest.
decided and executed from the cybernode proposal (the owner, 2026-10-17 and 2026-10-27). the code moved here from the soft3 crate with its history on 2026-10-27, unchanged: the wire identifiers (soft3/chain/…/v1), the genesis files and the home directories keep their names, so every running node and every genesis hash stays valid. what changed is the crate, the binary and the unit names.
| here | holds |
|---|---|
rs/ |
the crate and binary cybernode: chain/ the kernel, genesis/, node/, wallet/, network.rs; the verbs run (node) · mine · sync (status) · genesis · chain · conformance · network |
specs/ |
chain · chain-wire · chain-conformance · chain-economy · genesis · native-node · routing |
deploy/ |
cybernode@<network>.service, cybernode-check, journald, logrotate, nginx and ufw templates of an instance |
audit/ |
the receipts: conformance, economy, mining, the net, the requirement map of the chain |
cargo install --path rs # or: cargo install cybernode, once published
cybernode run --chain pussy --home ~/.soft3/pussy --bind 127.0.0.1:8545 --radio 0.0.0.0:7791 --peers peers.toml
cybernode mine --address NEURON --node http://127.0.0.1:8545
cybernode conformance check chain
the soft3 crate remains the stack facade: it depends on cybernode, re-exports its modules for one release and forwards the operational verbs, so nothing that built against soft3::chain breaks today. the soft3 repository keeps the ladder, the contracts of the stack, the release train and the SDKs; the private repository apparatus keeps cyberia's own hosts, secrets and runbooks.
what the node must still grow, so that cyberia runs all of its execution on it, is the capability table of the proposal § 4: proving workers and block aggregation, the index over bbg, snapshots and tip proofs, particles over radio blobs, operator keys through vault. each lands here as a spec, code and a receipt.