01
Software and wallet
Use the release and network that match your wallet. Control of a spending key belongs to its holder; a site account cannot replace it.
USE & RESPONSIBILITIES
Clear roles.
Clear obligations.
The network records authorised transfers. Wallet control, account access, operator participation and business contracts have separate responsibilities.
Product documentation · Edition 1 ·
SCOPE
Know which relationship you are using.
02
Operator participation
Provide accurate company and control information, protect the registration key and follow the accepted operator rules.
Operator application and rules →03
Commercial agreement
The parties agree goods, work or services, prices, delivery, refunds and payment terms. Recording a transfer does not resolve those obligations.
Business settlement guide →PARTICIPATION RULES
Make your decisions with the right information.
Wallet-holder responsibilities
Check the network, recipient, amount and fee before signing. Protect recovery material and retain payment identifiers. An accepted transfer is not reversed by an email password reset or an account deletion.
Operator responsibilities
Maintain accurate business and control disclosures, use compatible software, protect signing state and report changes in authority. Registration is not a promise of work, return or a certification of tax compliance. The application presents the operator rules and consent text accepted for that submission.
DUBYT and commercial value
DUBYT identifies the network unit. The software does not promise a market price, fixed conversion, redemption or investment return. A commercial price and a network fee are separate amounts. Coloured tariff proposals in the economic document require agreement and an authorised policy change.
Software and third-party notices
The licence and third-party notices supplied with a release govern the corresponding components. Availability of a download or source link does not itself grant a new licence, a trademark right or permission to reuse another company’s materials.
DATA & REQUESTS
Use the appropriate record.
The privacy document explains public network data, company registration records and public-source research. Keep private documents and passwords out of public reports.
For a company-record correction or application restriction, retain the application reference and follow the contact route in the operator rules. For a software issue, retain the release version and reproducible behaviour. These documents do not add a paid legal-review gate to ordinary node registration.
Find the relevant route →