Documentation

Unova Nodes is the self-service deployment interface for the Unova network. It lets you spin up a node — validator, data node, or Open Innovation Node — in a few clicks, with no DevOps required. You connect your wallet, pick a node type and a deployment target, and the launchpad handles the install and registration. You always retain custody of both your wallet and your hosting account.

1. Connect your wallet from any page using the Connect Wallet button. We support MetaMask, WalletConnect, Coinbase Wallet, social login, and most other EIP-1193 wallets via Reown AppKit. You'll be prompted to switch to Unova Testnet — accept it, then sign once to complete Sign-in with Ethereum.
2. Type-2 only: create your company at /data/companyfirst. Companies own Type-2 nodes; you can't deploy one without one.
3. Go to Deploy a node and pick a type (see Node types below).
4. Pick a deployment target:DigitalOcean — paste a personal API token and we auto-provision a droplet (cost varies by node type, billed by DO directly). We also generate a per-droplet SSH key so you can manage runtime config from the launchpad later.On-premise — bring your own Ubuntu 22.04+ server and we hand you a one-line install command. Runtime config edits via the launchpad require an SSH key, so on-prem nodes are install-once for now.
5. For Type-1 / Type-2 you'll provide an operator private key — the key that signs blocks (Type-1) or data bundles (Type-2). Use a fresh wallet for this, never your main one (see The 3-key model below).
6. Type-1 and Type-2 both need owner approval before they go live. You'll see the status on My nodes.

Three different wallets are involved in running a node. Keeping them separate is what stops a single compromise from emptying your treasury.

Type-1 (validator) and Type-2 (data node) deploys both go through a one-time on-chain registration before they're fully active. Type-3 (OIN) needs no approval — it runs immediately.

Type-1 (validator)

1. You submit the deploy form. KYC fields are optional but speed up review.
2. Your node installs and starts running but doesn't mint blocks until it's registered to the validator set on chain.
3. Registration is a single on-chain transaction by the network admin. Typical SLA: 48 business hours.
4. Once registered, your node enters the validator set within a few blocks and starts producing. You can watch the transition on My nodes.

Type-2 (data node)

1. Create your company at /data/company.
2. Deploy the Type-2 node. The node's operator address automatically goes into the pending whitelist queue.
3. Once whitelisted by the network admin, your node accepts facility writes and starts participating as a data node. Same 48-hour review window.

Both flows are enforced by smart contracts on Unova Testnet — no off-chain trust. We'll move to a Safe multisig with a security co-signer in Phase 2 of the network.

Type-2 nodes are built around a company. One company can own multiple Type-2 nodes and multiple physical facilities (warehouses, factories, stores).

1. Create a company at /data/company — name, VAT, address, type. The wallet that creates it is the primary admin.
2. Invite teammates by wallet address with roles: admin (full control), operator (deploy + manage nodes), viewer (read-only). They claim the invite when they sign in.
3. Add facilities. Each facility gets its own auto-generated wallet (operator key, encrypted at rest). This is the data-attribution identity for that site — separate from any user wallet.
4. Generate an API tokenfor a facility. The launchpad picks up the Hermes URL from your Type-2 node automatically, exchanges the facility's private key for a bearer token at /auth/getApiToken, and shows it once.
5. Paste the bearer into your warehouse / IoT / ERP system as the Authorization header. Tokens are derived on demand — never persisted by us — so re-generate any time.

Atlas — the worker that batches your assets and events into on-chain bundles — has two knobs you can tune per-node from the node detail page:

• Bundling interval (default 300s) — how often the worker checks for unbundled data. Lower = fresher data, more gas. Range: 30s – 86,400s.
• Minimum items per bundle (default 3) — wait until this many assets+events accumulate before bundling. Higher = cheaper, slower indexing. Range: 1 – 10,000.

Three presets are wired in for typical use cases: Realtime (60s / 1 item), Balanced (300s / 3 items, default), and Cost-saving (1800s / 25 items).

Changes are saved to the launchpad DB and applied to the running node via SSH (we generate a per-droplet ed25519 keypair during provisioning, store the privkey AES-encrypted, and use it to sed-patch the running docker-compose.yml + restart the worker container). Older nodes deployed before this feature shipped need a redeploy to enable live apply.

If you picked the on-prem target — or you want to install manually — paste this into a fresh Ubuntu 22.04+ server with at least 4 vCPU, 8 GB RAM and 80 GB disk:

curl -sSL https://nodes.unova.io/install/setup.sh | sudo bash

The script installs Docker, pulls the official Unova node image, generates an operator key locally on your VM (the launchpad never sees it), and starts the container with auto-restart enabled. You can override defaults with environment variables — see the script source at /install/setup.sh.

Network

Unova Testnet

Chain ID

3001

Native token

UON

Block time

~5 seconds

RPC

https://uvmtest.unova.io

Explorer

https://explorertest.unova.io

Mainnet is on the roadmap but RPC and contracts are not deployed yet. Switching your wallet to Unova Mainnet inside the app will trigger a "coming soon" toast and switch you back to testnet.

• API reference — endpoints exposed by your Type-2 node (assets, events, bundles, auth)
• Block explorer
• Monitor (live network stats)
• unova.io — main site, whitepaper, contact