01
Who operates a node?
Use the public company register and its evidence labels. Node count is not a count of independent beneficial owners.
Public register →TRANSPARENCY
Trace the operator.
Trace the rules.
Trace the release.
Keep identity, authority, software provenance and economic records visible as distinct evidence.
Product documentation · Edition 1 ·
PUBLIC RECORDS
Go to the record that answers the question.
02
Who can authorise changes?
Read the network policy and authority observations in the operator section, together with the renewal rules.
Authority rules →03
How are rewards accounted for?
Separate ordinary fees, bootstrap activity, issuance and reserve support. Review the coloured parameters before agreement.
Economic model →RELEASE RECORD
Match the software to its network.
Release records identify packages, checksums and changes. Downloads is the single place to select a Windows or Linux archive. Keep backups associated with their network; earlier browser-service and 0.18 client balances belong to separate networks.
01
DueByte 0.3.6
Payment recovery from encrypted backup, recovery of accepted unfinished reservations and clearer history-loading feedback.
Versioned release →02
Packages and checksums
Choose the operating system and compare the downloaded archive with its release checksum.
Downloads →ACCOUNTABILITY
Publish the right measures.
The reporting model separates active wallets from unique people, logical nodes from independent owners, accepted work from submitted requests and organic payments from funded bootstrap traffic. Availability and verified outcomes matter alongside volume.
A documented rule, a signed policy and a software release are distinct records. Changes to fees, issuance or authority require the corresponding activation procedure; editing a website cannot activate them.
HELP & CORRECTIONS
Keep the context with the request.
- 01
Installation or wallet recovery
Start with the recovery guide. Record the release, operating system and public error. Do not send a backup or its password.
- 02
Company application
Use My application for the reason and evidence. Follow the operator rules for a correction request and include the application reference.
- 03
Software issue
Use the project repository to locate the release and its issue route. Keep reports reproducible and free of secrets; do not publish exploit details or private data in an ordinary public report.