01
Verifying node
Follows authenticated history and supports local wallet use. Connecting an ordinary node requires no company approval.
Install a node →NODE OPERATORS
Useful work.
Visible responsibility.
Operate a node for a defined purpose. Make the organisation behind it visible and understand the work, costs and permissions attached to its role.
Product documentation · Edition 1 ·
CHOOSE A ROLE
Connection, service and authority.
02
Registered operator
Links node identities to a declared company or sole trader. The public register provides attribution and the level of supporting evidence.
Operator register →03
Assigned network role
Paid work and voting authority each require their own admission and rules. Registration alone grants neither a reward allocation nor a consensus vote.
Income model →REGISTRATION
Make your operator identity clear.
- 01
Create your DueByte account
Confirm your email and keep the registration backup. Wallet access and operator access remain separate.
- 02
Identify the business
Use the legal name, jurisdiction and registration identifier from the business records. Identify the representative and disclose common ownership or control.
- 03
Submit and read the evidence
Sign the application. Company research compares public sources and explains any missing information. An ordinary non-voting node can be registered while company evidence is incomplete, provided the application is not rejected or revoked.
- 04
Prove control of the node
Follow the request → local proof → upload sequence in My application. Upload the signed public JSON proof, not a node private key or wallet backup. The request binds the proof to the network and application.
COMPANY EVIDENCE
A useful identity, with traceable sources.
When an official register cannot supply a record, research can compare business directories, registry mirrors and other public sources. Matching legal name, jurisdiction and registration number across several publishers can support company identification.
What an assessment must explain
Show the source links, record dates, matching identifiers, conflicts and the next action. Copies of one registry entry are labelled as a shared underlying record. Company identity, current legal status, representative authority and independent ownership are separate conclusions.
What other users can see
The register shows the declared company, country, evidence level and node count. Private contacts and control disclosures are not published as profile fields. A company label is not a certificate of beneficial ownership.
OPERATOR DUTIES
Plan the full operating cost.
01
Keep the service reliable
Maintain compatible software, monitor availability, protect signing state and plan upgrades without copying active signing identities.
02
Keep the identity accurate
Maintain company and representative information and disclose related operators. More processes do not mean more independent organisations.
03
Measure the economics
Compare accepted paid work with hosting, traffic, storage, maintenance and capital costs. Use real demand and realisable DUBYT value.
Calculate the result →CHANGE OR EXIT
Close responsibilities deliberately.
An ordinary node can be disconnected. An operator with assigned duties must complete or transfer outstanding obligations through the applicable role rules. Removing a public registration and changing consensus membership are separate actions.
Protect recovery material during device replacement. Do not roll back validator signing state or start the same active identity on two machines. Keep payment receipts and records of accepted work.
Membership and authority →