An OS built for the network.
DcOS is ReaperNet's own operating system for nodes: its own kernel, file system, processes, shell and SSH. Every capability is proven by a boot test on x86-64 and ARM64 (QEMU) before it counts.
[ ok ] UEFI boot (x86-64)[ ok ] kernel up[ ok ] file system mounted[ ok ] process manager[ ok ] shell ready[ ok ] ssh: owner keys only[pair] scan QR to pair this node code ······ · fingerprint ······
Each piece, proven at boot.
DcOS is our own kernel — not Linux, not a fork. It boots on x86-64 PCs (BIOS or UEFI, from a USB stick) and on ARM64, runs its own programs with user accounts and file permissions, keeps an integrity-checked disk, accepts encrypted SSH logins, and verifies other blockchains itself — Cosmos finality, Ethereum state, Bitcoin blocks and ReaperNet’s post-quantum signatures — without trusting any server.
64-bit kernel written from scratch for x86-64 and ARM64: paging, memory allocator, preemptive scheduler; on ARM64 it runs work across all 4 CPU cores.
BIOS and UEFI firmware, from a CD or a USB stick; uses only the RAM the firmware reports as free.
Everything the system prints appears on the monitor (UEFI GOP / BIOS VBE graphics) as well as the serial port.
Real ELF programs in separate, isolated address spaces (code never writable, data never executable); a shell with scripts and typed commands.
DcFS: files survive power-off, every read is checked against a digest, corruption is rejected; 64 MiB disks, 8 MiB files, old disks migrated.
Accounts with salted PBKDF2 password hashes, private files per user, lockout after repeated wrong passwords.
A built-in SSH server (curve25519, Ed25519 host key, AES-GCM, strict KEX) — log in with any standard ssh client.
TCP/IP and TLS 1.3 written in the kernel, on virtio and on a real Intel e1000 network card driver.
Cosmos (CometBFT) finality, Ethereum state proofs, Bitcoin SPV and a multi-exchange price oracle — checked in the kernel, no trusted server.
In production mode the node shows a QR and a fingerprint on its screen; the owner approves it in the BlockiD app, and the node trusts only that owner from then on.
Remote login only with ed25519 keys the owner added and approved in the BlockiD app — no shared passwords; keys can be revoked and the host-key fingerprint is shown in My Nodes.
Verifies and creates ML-DSA-65 (FIPS 204) signatures — ReaperNet’s own transaction scheme — inside the kernel.
Each milestone is a test the kernel runs on every boot; a milestone counts only when its test passes in a real boot (QEMU, x86-64 and ARM64).
Owned by your BlockiD.
A DcOS node has exactly one owner: the BlockiD that approved its pairing. Remote access is limited to SSH keys that owner added and approved in the BlockiD app — there is no shared password.
- 1 · Pair — the node shows a QR and fingerprint; you approve on your phone
- 2 · Add a key — add an ed25519 key in the BlockiD app and approve it
- 3 · Check the host — compare the node's host-key fingerprint (shown in My Nodes) before you connect
- 4 · Release — unpair the node from your BlockiD at any time
At a glance.
- Kernel
- Own kernel, written from scratch (not Linux)
- Architectures
- x86-64, ARM64
- Boot
- BIOS + UEFI · CD or USB stick
- File system
- DcFS — digest-checked, 8 MiB files
- Network
- Own TCP/IP + TLS 1.3 · SSH server
- Cryptography
- ML-DSA-65, Ed25519, X25519, AES-GCM
- Verified milestones
- 40 (boot-tested)
Today and next.
There is no hosted download yet. DcOS is built from source; the image boots BIOS and UEFI PCs from a USB stick.
Tested in QEMU on BIOS, UEFI and USB boot paths; not yet run on a physical PC.
Ready-made node packages per role, then a hosted download.
Node packages also run without DcOS — same pairing with your BlockiD.
make kernel usb-image # builds dcos-usb.img (one image: BIOS + UEFI, CD or USB) sudo dd if=dcos-usb.img of=/dev/sdX bs=4M conv=fsync # ERASES the stick — check sdX with lsblk
Planned, not built yet.
Run the DAG-Flow node itself on the metal (today the node runs on a conventional OS; DcOS runs its verifiers).
A native browser and decentralised internet protocol on DcOS.
Sign in with BlockID and hold keys natively on a DcOS machine.
Packaged node-and-wallet appliances running DcOS.
Process signals, keyboard input on the screen, more network and storage hardware.
An outside firm reviewing the kernel, the SSH server and the cryptography.