--- title: "From a node on your shelf to a node in the network" url: "https://kyberfusion.com/blog/from-your-shelf-to-the-network" description: "A home node idles most of the day. Lending that capacity is a question of consent, isolation and energy, not of technology. Here is how a Node is meant to join." --- # From a node on your shelf to a node in the network October 8, 2026·4 min read·Editorial team A home compute node with four coloured lights and a sharing switch turned on, cabled to a blurred server rack behind it It is three in the morning. On a shelf in your hallway, a KyberDeck Node has finished the night’s work: the day’s notes are synced, the long memory your assistant keeps is indexed, the backups are done. Its light ring is dim. For the next five hours it will do almost nothing, and it will still be drawing power. Somewhere else, at the same moment, someone’s swarm of agents needs an hour of compute to finish a job before morning. The capacity exists. It is sitting on your shelf. Nothing connects the two. ## The real cause: lending is a trust problem, not a technical one Running someone else’s work on a spare machine is not hard. Volunteer computing projects have done it for decades. What is hard is everything around it: who may run what, on which machine, when, using whose electricity, and how anyone proves afterwards what happened. A home node makes this sharper, because it is not a spare server in a rack. It is the device that holds your assistant’s memory. Any plan to lend its capacity has to start from the assumption that the owner’s own data is the most valuable thing on it. ## Why lending spare capacity usually goes wrong **Consent hidden in a setting.** Sharing is on by default, or bundled into an update, and the owner finds out from the electricity bill. That is not lending; it is taking. **Strangers’ work next to your memory.** The borrowed job runs as just another process on the same system, with the same disk and the same network. One mistake in isolation, and a stranger’s code can reach what your assistant knows. **Energy nobody counts.** The owner pays for the power, but the accounting measures only compute. Lending turns out to cost more than it settles. **Settlement you have to trust.** The operator reports what was used and what is owed, and the owner has no way to check either figure. **No clean way out.** Leaving means losing what was settled, or waiting out a lock-in period, or discovering that the node still accepts work after it was “switched off”. ## How a Node is meant to join Here is the design the KyberFusion network is built to, step by step. None of it ships yet. **Off by default.** A KyberDeck Node lends nothing until its owner switches lending on, with something like `kyber fusion contribute --node`. The command is illustrative; the principle is not. What the Node is for in the first place is described in [the home node](https://kyberdeck.com/blog/the-home-node) on KyberDeck. **Your rules, stated up front.** Which hours, which classes of work, which jurisdictions the work may come from, and a ceiling on the energy it may draw. The network places work inside those rules and never outside them. **A cell, not a process.** Work from the network runs in its own KyberCell, sealed off from the memory store, with its own files and a network closed except for what the job needs. On a Node this is enforced by the same system that enforces it everywhere else, as explained in [the same OS in the cloud](https://kyberlinux.com/blog/kyberlinux-as-a-fusion-node). **Your own work first.** When your assistant needs the Node, borrowed work gives way. Whether a job should run at home or out in the network is a question KyberAgent takes up in [where a swarm should run](https://kyberagent.com/blog/where-a-swarm-should-run), and the answer works in both directions. **Metered, not estimated.** The compute used is measured, the energy drawn is measured, and both are settled in tokens on a ledger the owner can read without asking anyone. A token is a unit of settlement for compute: what the Node receives for capacity used can be spent on renting capacity when its owner needs more than the Node has. Tokens carry no promise of return, profit or price. This is not an offer. **One command out.** Switching lending off stops new work immediately and lets running cells finish or be cancelled. There is no exit fee and nothing to wait out. ## The honest limits A home node that lends capacity draws more power than an idle one, and depending on the hour and the tariff, that may cost more than the settlement covers; the owner’s meter, not our estimate, should decide. Heat and noise are real on a shelf in a hallway. Home connections are slower and less reliable than a data centre’s, so only some work fits. And isolation is something to test, not to promise: until KyberCell has been attacked by people who were not involved in building it, no one should lend a node that holds anything they cannot afford to lose. ## A test you can run today Find out what your own idle hardware is doing. Pick one machine you leave on: a home server, a desktop, a mini PC. For one day, check its processor load at a few different hours (Task Manager on Windows, `uptime` or `top` on Linux and macOS). If you have a plug-in energy meter, read its power draw while it sits idle. You now know two numbers: how much capacity the machine leaves unused, and what it costs you to keep that unused capacity switched on. Those are the two numbers lending is supposed to improve. The [KyberFusion homepage](https://kyberfusion.com/) shows how the network is meant to settle them. - home node - capacity - energy - tokens ## Keep reading - [One request, end to end: from a card to the cloud and back](https://kyberfusion.com/blog/one-request-end-to-end) - [What a cloud node knows about you](https://kyberfusion.com/blog/what-a-node-knows-about-you)