Disposable Node

Disposable Node lets you AGGREGATE latent resources worldwide (unused disk spaces, stray wifi signals, idle night bandwidth, bored retiree labour etc.). Mix and match resources as nodes EASILY (like assembling toy bricks) without technical knowledge and deploy them rapidly with just ONE COMMAND.

Most people don't know HOW to cook well, but they certainly know WHAT taste good. Disposable Node enables people without non-technical skill to improve their Private Cyberspace by simply mixing and matching predefined computing blocks (like toy bricks).


Disposable Node empowers you to import compute to process your data instead of having to export your data to cloud platforms for processing, by enabling you to leverage the latent processing power of thousands of community computers worldwide from the comfort of your personal phone.

Disposable Node gives you unprecedented income and impact by aggregating resources from millions of community computers e.g. ultra reliable storage, get insights from private data, manage trust in every transaction, set prices for your contributions.

1. Introduction

Applications in the Home Digital Hub are deployed inside Data Containers so they can be isolated from each other, run efficiently and can be managed easily.

This is very different to the traditional processing containers based on isolation of PROCESSING resources (processor, ram etc.):

  1. Application Containers (e.g. Docker) isolate applications to make them easier to deploy and maintain.
  2. Machine Containers (e.g. KVM) isolate computation ti make sharing of hardware resources easier.

With Data Containers we use standard System Containers (e.g. LXD) but with a special value added layer so we isolate based on the data type e.g. private data, shared data, public data etc.

Flexible Virtualisation

Compute Modules can run applications inside be Machine Containers (e.g. KVM) or System Containers (e.g. LXD).

Machine Container has more flexibility but is also more resource hungry, in general Compute Modules should only use Machine Containers if System Container is not suitable.

System Container provides isolation at the operation system level, allowing both traditional applications as well as newer Application Container (e.g. Docker) applications to be run inside them.

Resource Sharing

To promote resource sharing (resulting in lower costs) Compute Module tries to put as many applications as reasonable into one Module (one container), this goes the OPPOSITE direction of application containers (e.g. like Docker) which separates application out.

Compute Module isolates the technical support instead of isolating related applications that does not need to be isolated, so extra layers of protection between applications can be removed.

Compute Module lowers management costs with advanced monitoring and automation technologies instead of isolating applications by giving them their own system resources.

Operation Framework

All Compute Modules share a common Operation Framework (e.g. Infinite Disk for storage and Campus Network for communication) so they can be deployed easily around the world.

Network Isolation

Disposable Node and Personal Console form the two halves of a Private Cyberspace.

Disposable Node provides the backend computing power (e.g. when the required processing resources exceed what's available on a mobile phone or when the information is more securely processed away from the mobile phone), while the Personal Console provides the frontend user interface.


The complete Private Cyberspace can be deployed rapidly with ONE CLICK install of Console and ONE COMMAND install of Node on numerous commodity devices.

1.1. One Command

A Disposable Node can be created with just ONE COMMAND on most computers.

It can share existing computers (from home computers to remote virtual machines) with other applications as well as run on dedicated computers (from tiny Raspberry Pis to massive IBM Mainframes) by themselves.


Most old computers manufactured within the past 10 years (even laptops with damaged screens and keyboards) can be used.

1.2. Node Types

Disposable Nodes are basic building blocks of the Private Cyberspace that can be used to deploy an unlimited range of processing, networking and storage systems. Disposable Nodes cover the whole digital environment, from the version of the software being used to the size of the storage on a computer, from the room the computer is in to the name of the person walking in to do repairs.


1.3. Scalable Design

Each Disposable Node provides a set of application specific computing functions by wrapping relevant software and hardware into independently deployable computing bundles that work synergistically together with each other.


It hides the complexity of operating large scale computing resources behind a simple computing abstraction, allowing those resources to collaborate and be shared quickly and safely between members of a community.

Ironically they create highly reliable systems by being easily disposable themselves.

Node Sizes

Disposable Nodes are classified based on the size of their memory. Higher memory nodes support all features of lower memory nodes.

Listed below are some suggest minimum node sizes for some applications:

0.5G memory

  • CPU: 1
  • RAM: 0.5 GB
  • SWAP: 1 GB
  • DISK: 16 GB

Virtual Private Mesh

  1. Network Relay Node

1G memory

  • CPU: 1
  • RAM: 1 GB
  • SWAP: 4 GB
  • DISK: 64 GB

Infinite Disk

  1. SMB Server
  2. File Access Node

2G memory

  • CPU: 2
  • RAM: 2 GB
  • SWAP: 2 GB
  • DISK: 64 GB

Fuzzy Blockchain

  1. Chain Audit Node

Infinite Disk

  1. File Storage Node

Home Zone

  1. Home Clients

4G memory

  • CPU: 4
  • RAM: 4 GB
  • SWAP: 4 GB
  • DISK: 256 GB

Home Zone

  1. Home Servers

Shared Computer

Shared Computers are NOT dedicated to running Disposable Nodes, they perform other tasks e.g. running Personal Console in web browsers, editing office documents on Infinite Disk etc. along with running one or more Disposable Nodes.

Shared Computers (Windows, macOS) need at least 4G RAM to run Disposable Nodes as Virtual Machines. The lack of RAM mean running a second VM to protect the main VM might not be possible.

A shared computer with 8GB RAM is recommended and 16 GB RAM is preferred.

Suggested Configurations

4G RAM Computer

  • 1 x 1GB Disposable Node
  • 1 x 0.5GB Disposable Node

8G RAM Computer

  • 1 x 4GB Disposable Node
  • 1 x 0.5GB Disposable Node

16G RAM Computer

  • 1 x 8GB Disposable Node
  • 1 x 0.5GB Disposable Node

Node Types

Base Nodes are Virtual Machines (e.g. KVM) or System Containers (e.g. LXC) that provide basic compute resources for other Disposable Node to built on.

Base Nodes Operating Systems
Process Node Ubuntu, Debian, Red Hat
Mesh Node OpenWrt

Application Servers are created to take advantage of the services offered by the Base Nodes

Campus Network Application Core Software External Software Internal Software
Broadcast Server Mastodon BigBueButton, Peertube, coturn Gallery, Relation
Operate Server GLPI Openwisp, Zabbix Database Partition
Storage Server nbdkit Minio Infinite Disk
Blockchain Server Bitcoin Core PKI Fuzzy Blockchain
Home Network Application Core Software External Software Internal Software
File Application Nextcloud Samba
Home Application Home Assistant
Network Application mitmproxy tinc, nmap IP Rank
Search Application elasticsearch carrot2