ReaperNet
OPERATING SYSTEM

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.

dcos · boot log · illustrative
[ 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 ······
40
boot-verified milestones (last 2026-09-26)
x86-64 · ARM64
every capability boot-tested on both
Own kernel
not a Linux distribution
From source
no hosted download yet
WHAT IT DOES TODAY

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.

M1–M5, M12Our own kernel

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.

M37Boots real PCs

BIOS and UEFI firmware, from a CD or a USB stick; uses only the RAM the firmware reports as free.

M38Screen console

Everything the system prints appears on the monitor (UEFI GOP / BIOS VBE graphics) as well as the serial port.

M16–M33Programs and a shell

Real ELF programs in separate, isolated address spaces (code never writable, data never executable); a shell with scripts and typed commands.

M21, M34Integrity-checked disk

DcFS: files survive power-off, every read is checked against a digest, corruption is rejected; 64 MiB disks, 8 MiB files, old disks migrated.

M35Users and permissions

Accounts with salted PBKDF2 password hashes, private files per user, lockout after repeated wrong passwords.

M36Encrypted remote login

A built-in SSH server (curve25519, Ed25519 host key, AES-GCM, strict KEX) — log in with any standard ssh client.

M6Own network stack

TCP/IP and TLS 1.3 written in the kernel, on virtio and on a real Intel e1000 network card driver.

M8–M11Verifies blockchains itself

Cosmos (CometBFT) finality, Ethereum state proofs, Bitcoin SPV and a multi-exchange price oracle — checked in the kernel, no trusted server.

M39Node pairing with BlockiD

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.

M40Owner-only SSH keys

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.

M13Post-quantum signatures

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).

SECURITY MODEL

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. 1 · Pair — the node shows a QR and fingerprint; you approve on your phone
  2. 2 · Add a key — add an ed25519 key in the BlockiD app and approve it
  3. 3 · Check the host — compare the node's host-key fingerprint (shown in My Nodes) before you connect
  4. 4 · Release — unpair the node from your BlockiD at any time
SPECIFICATIONS

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)
HOW TO GET IT

Today and next.

TODAYBuild from source

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.

NEXTFull, edge and light packages

Ready-made node packages per role, then a hosted download.

ORRun a node on your own OS

Node packages also run without DcOS — same pairing with your BlockiD.

BUILD A USB IMAGE (FROM THE REPOSITORY)
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
ROADMAP

Planned, not built yet.

The ReaperNet node on DcOS

Run the DAG-Flow node itself on the metal (today the node runs on a conventional OS; DcOS runs its verifiers).

Web 3.03 + the Odyssey (ODC) browser

A native browser and decentralised internet protocol on DcOS.

HoneyComb wallet + BlockID login on the device

Sign in with BlockID and hold keys natively on a DcOS machine.

SmartPod technology

Packaged node-and-wallet appliances running DcOS.

Signals and more drivers

Process signals, keyboard input on the screen, more network and storage hardware.

Independent security audit

An outside firm reviewing the kernel, the SSH server and the cryptography.

Keep exploring

Boot your own
piece of the network.

Run a node
Get the app