Blockchain infrastructure priced on capacity, not capital

We measure what your machine can do, then give it real work.

Fenryx is a network built from everyday machines — laptops, home servers, whatever you've got running — organized by what they can actually contribute, not by how much money is behind them. Omnia measures the real capacity, four pools split up the work, and nobody gets a bigger cut just by claiming a bigger number.

0
devices already contributing to DePIN
0
countries running DePIN nodes
0
personal computers in use today
FENRYX NODE MESH
Why now

Most of the world's computing power just sits there, unused.

Global spend on data-center systems is climbing 62% a year toward $822B. Meanwhile the entire DePIN category — thousands of projects, millions of devices — pulled in barely seventy million dollars in 2025. The hardware was never the problem. Getting people to pay for raw capacity, with nothing else attached, is.

0
global IaaS spend in 2026, +29.3% year over year
0
active DePIN projects splitting capacity
0
total revenue across the whole DePIN category in 2025
0
enterprise blockchain market in 2025
Sources: Gartner (Jul 2026) · Grand View Research (Jun 2026) · DePIN sector report (Mar 2026) · Canalys / IDC (2025)
We're not selling spare capacity. We're building something people actually want to use — the capacity is just how it gets delivered.
How it works

How a machine earns its place in the network.

Nobody gets to declare what their hardware can do. Omnia checks it against what the network has actually seen that machine do, then assigns it to the pool that fits. Tap a pool to see how it works.

OMNIA · corroborated classification
The product

Twelve things Fenryx does that most chains don't.

Most chains manage two or three of these well. Rarely the same two or three. Tap any card for the full explanation.

Competition

Ask any chain these six questions.

Most chains answer two or three of them well. This is what we designed around answering for all six.

Can anyone become a validator?
No minimum capital, no allowlist. If your machine measures well, it's eligible.
Does it update without a hard fork?
Capability changes land through on-chain governance and an agreed block height, not a silent server push or a chain split.
Is joining actually simple?
No specialized ops knowledge required to run a node from a machine you already own.
Does it demand a big upfront investment?
Ordinary hardware — not a warehouse of rigs — earns a real, working role.
Is the reward system fair?
Pay follows measured contribution, not who arrived first or staked the most.
Does it discourage pools from forming?
Capacity subclasses and forced rotation exist specifically so capital can't out-organize small operators into irrelevance.
How we build

The four rules we don't bend on.

01

The code rules

If it isn't in the code that runs, it doesn't exist. A roadmap slide doesn't count, and neither does a comment claiming a module is finished.

02

Three labels, never a fourth

Every machine gets sorted into one of three clear performance grades. There's no vague "good enough, probably" bucket invented to dodge a real call.

03

Attack it before you extend it

Every piece goes through an attempted break first, on an isolated copy of the chain — never the live network — before the next piece gets built on top.

04

No power without a threshold

No sensitive action depends on a single key. The same rule that closes a block — agreement from more than two-thirds of the network, not one — is what any real power needs behind it too.

The ecosystem

One account. Six products built on top of it.

Chain is the reference network. Everything else runs on it, sharing the same account, the same wallet and the same token — not six separate logins pretending to be one ecosystem. Tap a product for more.

Vision

We're building a computer as big as the internet — out of machines that already exist.

There's nothing new to manufacture. It's already sitting there, in more than two billion powered-on, underused machines — a gaming rig idling overnight, a laptop closed in a drawer. We're not asking anyone to buy new hardware. We're asking them to put what they already own to work. And we hold ourselves to one bar for anything we ship: if it could carry any other project's logo and nobody would notice the difference, we didn't do it right.

Building something serious? Let's talk.

Fenryx is under active, open construction — we'd rather say that plainly than pretend otherwise. If you want the whitepaper, a seat on the private testnet, or just want to ask the hard questions first, write to us.