Network live · Beta

I am. You are.
We are Consensus.

Ready to power the network?

Run a node. Carry traffic. Help build the network. Serve HTTP and TCP tunnels, forward and reverse proxy requests, leased stable IPs, and metered WebSocket sessions while Consensus is in public beta.

No rewards are paid during the beta. It exists to expand the network and find viable nodes.

Run a Node → See requirements
Four ways a node serves

Four kinds of traffic, one node.

SERVE 01

Serve tunnels

Forward HTTP and TCP traffic for tunnels opened through your node, putting local services on public HTTPS URLs.

SERVE 02

Serve the proxy

Execute deduplicated HTTP as a forward or reverse proxy for the network.

SERVE 03

Lease your IP

Offer a verified, long-lived static IPv4 address into the shared pool for apps that need to route through a whitelisted IP.

SERVE 04

Serve WebSockets

Host metered WebSocket sessions, bounded by time and data, and close each one cleanly when its budget runs out.

The bar to join

Every node is vetted, to join and to stay.

Consensus enforces quality rather than assuming it. A machine passes an encrypted admission test before it can register, and the network, not the node, makes the call. The vetting never stops: a node must stay connected and healthy to keep receiving traffic.

Recommended machine
Memory8 GB Cores4 Storage50 GB SSD Bandwidth100 Mbps Public IPv41 public Open port1 inbound Uptime24 / 7 RuntimeBun
The admission test
≥ 85%
Steady throughput
Holds its rate across a sustained run of 16 KB responses, with no throttling.
≥ 90%
A real core
Gets at least 90% of a full CPU core, with no shared or stolen time.
≥ 50 req/s
Capacity
Even its slowest window serves 50 requests a second at 16 KB.
p99 ≤ 50 ms
Responsiveness
Its event loop picks up new work without stalls.
The network, not the node, decides admission, and a node must also have at least 512 MB of memory. Admission is not the finish line: a node must keep its encrypted tunnel connected to keep receiving traffic.
From install to live

Three steps to a live node.

01
Clone and install
Get the latest node software from GitHub and install its dependencies with Bun.
$ git clone https://github.com/Demali-876/consensus-node.git $ cd consensus-node $ bun install
02
Run guided setup
One command installs the approved release, runs the admission test, verifies email, collects payout addresses, registers, and starts the node. A domain is issued on pass.
Prefer a browser? bun run setup:wizard runs the same flow on a local page.
$ bun run setup
03
Keep it running
Install the boot service so the node starts at boot, without a login, and stays in the active set.
$ cd ~/.consensus/node-runtime/current $ sudo scripts/install-launchd.sh
Read the full node guide →
Operator questions

What running a node involves.

What does a Consensus node actually do?

A node carries live traffic for the network. It forwards HTTP and TCP tunnels so local services reach a public HTTPS URL, executes deduplicated proxy requests as a forward or reverse proxy, offers its static IPv4 address to apps that need a whitelisted IP, and hosts prepaid, metered WebSocket sessions.

Do nodes earn rewards during the beta?

No. No rewards are paid during the public beta, and the network is free to use. The beta exists to expand the network and find viable nodes: machines that pass admission and keep passing the heartbeat and re-tests under real traffic. Registration is complete, payout addresses included, so a node that joins now is fully set up once the reward model is decided.

What hardware do I need to run a node?

We recommend at least 8 GB of memory, 4 cores, 50 GB of SSD storage, and 100 Mbps of bandwidth, with a public IPv4 address. Node releases currently target Macs with Apple Silicon. Plan for one inbound port you can open: it is not needed to join, but nodes are expected to become directly reachable. The node runs on Bun and needs to stay online 24/7.

How does admission work?

Setup runs an encrypted admission test, and the network, not the node, decides the result. Serving 16 KB responses under sustained load, the machine must hold at least 85% of its starting throughput, get at least 90% of a full CPU core, and serve at least 50 requests a second in its slowest window. It also needs a responsive event loop and at least 512 MB of memory. Admission is not the finish line: a node must keep its encrypted tunnel connected, and only connected, healthy nodes receive traffic.

How long does setup take?

Three steps. Clone the latest node software from GitHub and install it with Bun; run the guided setup, which installs the approved release, runs the admission test, verifies your email, collects payout addresses, registers the node, and starts it; then install the boot service so the node restarts on its own after a reboot. A domain is issued once the node passes.