Declared company
The applicant names the company operating the node. Self-declared ownership is not verified beneficial ownership.
DueByte network
Node operators
Register your company and link the nodes you operate. Applications are open to every country.
Public register
Who operates the nodes.
Company names, node counts and the evidence behind each registration.
Loading the register…
How to read the verification labels
Company checks
Public sources can support company identity. Official record confirmation is shown separately.
Ordinary nodes
These nodes do not vote. Several companies or servers may share one owner.
Network policy and current authority
The current network is operated on two servers by one owner. Logical node and signing-key counts do not represent independent owners.
Loading verified policy information…
DueByte account
Checking your session…
Your account will appear when the check is complete.
Log in to DueByte
Use your separate DueByte account to manage your operator application.
Your DueByte account
Registration backup
This encrypted registration key signs your company application. It is separate from your wallet. Keep a downloaded copy and its password safe.
Restore an existing registration backup
No file selected
Encrypted DueByte registration backup · .json · under 5 KB. You will need its password. Do not select a wallet backup.Your company
Tell the network who operates your node.
Complete three short sections. After submission, you can connect an ordinary node while company checks run separately.
Your progress
From application to connected node.
See what is complete and the one action to take next.
Connect an ordinary node
Link the node on your computer to your company. Download two files, create a public proof on that computer, then upload the proof here.
01
Get the two files
On the computer running your node.
Save both files in the same folder, for example a new DueByte registration folder on your Desktop.
challenge.json — links the proof to your application.
Download proof toolduebyte-node-proof.mjs — creates the proof locally.
My node is not installed yet
Download DueByte, open it and select Connect. Return here on that computer once the node has connected.
02
Create the proof
In PowerShell on the node computer.
- Open the folder where you saved the two files.
- Click the File Explorer address bar, type powershell and press Enter.
- Copy the command below, paste it into PowerShell and press Enter.
This command uses the standard Windows DueByte node folder. Node.js 22 or newer must be available.
Node.js or a different node folder
DueByte includes Node.js. If PowerShell says “node is not recognized”, enter the full path to runtime\node.exe inside your extracted DueByte package below. You can also use an existing Node.js 22+ installation.
The node folder contains config\node_key.json. For the standard Windows app it is %APPDATA%\SunPhi Native Trial\node\trial\follower. If it does not exist, open DueByte and connect first. These paths stay in your browser.Result: a new proof.json file in the same folder. Your private keys remain on this computer.
The command reports an error
- Cannot find module: open PowerShell in the folder containing both downloaded files.
- node_key.json not found: connect your DueByte node first or enter its correct data folder above.
- proof.json already exists: rename the old public proof file, then run the command again.
03
Upload and register
Back on this page.
Select the proof.json created in step 2, then register the node.
Public node proof
proof.json · under 12 KB · created within the last 24 hours. This is not your wallet or registration backup.No file selected
After registration, the public list shows your declared company and its node count. Voting rights are separate.
Company checks and sources
Application details and permissions
How it works
Four steps. One clear path.
Register your company, connect your node and see what has been verified. Ordinary node registration is free.
Create your account
Enter your name, email and password. Confirm your email and save the encrypted registration backup.
Tell us about the company
Provide its registration details, your role and any shared ownership. Submit the signed application.
Connect your node
Download the request, create a public proof on the node computer and upload it. This links the node to your declared company.
See the evidence
Company checks run separately. Your status shows sources and any gaps. Incomplete company evidence does not block an ordinary node.
What company checks establish
Sources and comparisons
Official adapters are available for Norway and France. The UK adapter requires registry credentials. Elsewhere, or when an official source is unavailable, AI searches public business sources and registry directories.
Results show source links, record dates where available, discrepancies and missing evidence. Several publishers may reproduce the same registry.
What remains separate
Matching identifiers support company identity. They do not certify current legal status, document authenticity, representative authority or independent ownership.
Company-document uploads and automatic document-signature checks are not currently supported. A paid legal review is not required for an ordinary node.
Voting rights and network authority
Ordinary node registration does not grant voting or checkpoint-signing authority. Those rights require a separate certified network membership decision.
During launch, registry decisions require three of four designated signing roles, currently controlled by one owner. They are not four independent organizations. The current authority term ends on 1 December 2026 at 00:00 UTC; renewal requires a separate signed decision.
Your responsibilities and public information
Keep company and control disclosures accurate, protect keys and backups, run compatible software, and report ownership or authorization changes. Registration does not promise income or certify tax compliance.
After a node is registered, public pages show its declared company name, country, evidence level and node count. Private contacts, representative details and control disclosures remain private. Application records and decision history stay in the existing SUN PHI Supabase project.
Corrections and restricted applications
Decisions include a reason. If your application needs correction or is restricted, give your application reference when contacting SUN PHI. Do not send passwords or private keys. Revocation removes registry eligibility; consensus membership follows its own signed procedure.
Rules version: duebyte-operator-rules-2026-11-03