Accounts, KYC and device attestation

Unetwork has two roles. You choose which role you are using when you sign in, and that choice applies to that session.

The Unetwork Node Operator role manages your Unetwork Node and the licenses associated with it. The Unetwork License Operator role operates one or more Unetwork licenses on participating devices. After the full terms have been introduced, these are abbreviated to UNO and ULO.

An account is not fixed to one role, so a single account can sign in as either. There is one limit that matters: an account cannot operate the licenses it owns. To run your own licenses you need a second account to operate them.

A single ULO account can manage multiple licenses.

You do not need:

• a separate email for every license
• a separate ULO account for every phone
• separate KYC for every device

This is the most important distinction in this guide.

KYC asks who is participating. It verifies the identity of the person behind a Unetwork account.

Device attestation asks what device is participating. It evaluates the device itself and helps Unetwork determine whether the endpoint is a genuine physical device, and what level of device trust can be established.

A user can therefore have one KYC verified ULO account, operating multiple licenses, across multiple individually attested devices.

Individual KYC is currently handled through Sumsub. You can begin onboarding without immediately completing KYC, but verification becomes required when certain platform conditions are reached.

KYC is required when:

• your account reaches the applicable incentive threshold
• you want to withdraw
• you participate in certain tasks that require verified users

The current incentive threshold is 5 UP. Some tasks may require KYC before you can participate, regardless of your incentive balance.

If you previously completed the full Unetwork individual KYC process successfully through ShuftiPro, that verification remains valid. You do not need to repeat KYC solely because Unetwork moved new individual verification to Sumsub.

If you completed ID verification through ShuftiPro but not address verification. Complete the current Sumsub flow. Sumsub will ask for your identity document again, because it is a different provider and cannot rely on a check carried out elsewhere.

If you previously used all three verification attempts. The attempt limit has been reset, so you can try again.

If you are unsure which verification you previously completed, check your account status before assuming your UNO is already verified.

You can sign in to a single account as either role. What you cannot do is operate the licenses that same account owns, so running your own licenses means a second account.

Each account completes its own KYC. You are verifying the same person, but verification belongs to the account.

Unetwork currently allows the same person to complete KYC for up to two separate accounts.

One account has one email address, so a second account needs a second address. You do not need large numbers of aliases to operate multiple licenses: a single account can operate many.

Unetwork currently treats several forms of alternative email addressing as aliases, including plus aliases and dot aliases.

A plus-addressed email can be used as an account email. Multiple aliases for the same email account should not be treated as a method for creating multiple independent accounts.

These two features solve different problems.

Changing your email does not create a new Unetwork user. Your user ID remains the same, your KYC remains with the account, and existing account data remains with the account. For UNO accounts, changing the email also leaves the wallet association untouched. There is a single wallet association and it stays with the account.

Merge Accounts currently supports ULO to ULO only. It does not merge your UNO and ULO into one account.

The account you choose to keep becomes the destination, or base, account. You should begin the merge from the ULO account you want to continue using.

When eligible ULO accounts are merged:

• licenses move to the retained ULO account
• applicable account data moves to the retained account
• existing lease and device bindings remain in place
• the source account is disabled and becomes inaccessible

The destination account becomes the account you continue using.

There are two cases, and they have different fixes.

If you already have two accounts on aliases of one inbox, for example name+123@gmail.com and name+456@gmail.com, use the Change Email procedure in Settings.

If you have been using a single account for both roles, you have two options. Create a new account with a distinct inbox, cancel your existing leases and create new ones for that account. Or contact Support, who can transfer the licenses for you.

You may be able to consolidate them through Merge Accounts. Choose the ULO account you want to keep and use that account as the destination. Multiple ULO licenses can then operate under that one ULO account.

You do not need to maintain multiple ULO emails simply because you operate multiple licenses.

A wallet and an email are different parts of your account structure.

There is a single wallet association, and it belongs to the account. Changing your email leaves it untouched.

If you have a wallet-only ULO account that needs to enter the current account merge process, you must first attach an email address to that account through the management portal. You can then use the normal ULO merge process.

Attaching an email only fails if that address already exists in the Unetwork system. The wallet association is not changed by attaching an email.

Only ULO to ULO account merges are currently supported.

Scout & Runner is currently aware of the Unetwork account merge process. A valid ULO merge should therefore continue to work with Scout & Runner.

Every participating device has its own attestation status.

All three states can currently connect to the network. The difference becomes important when specific tasks require a minimum level of device trust.

Extended Telemetry and Entropy currently require at least software attestation. CLI and Surveys do not currently have an attestation-based eligibility requirement.

For Extended Telemetry, hardware and software attestation are currently treated the same. Other normal task requirements still apply to Entropy.

At present, none of the current task requirements covered here require hardware attestation specifically rather than software attestation.

For Extended Telemetry, hardware and software attestation are currently treated identically.

Attestation should therefore be understood primarily as an eligibility and device-trust requirement, rather than as a universal incentive multiplier. Network incentives depend on the individual service, task, eligibility conditions and qualifying activity.

An unattested device cannot currently participate in Extended Telemetry or Entropy, so its incentive opportunities can be more limited, even though it can still connect to the network.

The app and management portal receive attestation information from the same underlying source. If they temporarily display different states, this is likely to be a caching or display issue rather than two different attestation results.

Refresh or reopen the relevant application or portal. If the discrepancy persists, contact Support so the account and device can be checked.