You
Will be the ULO. RED nodes is the UNO. You never sign in as the node.
If you join us, you will be a Unetwork License Operator — not a node operator. You do not need a node account. This page is what Unetwork will ask of you: the person, the login, the license, and the phone. Read it before you claim a slot.
Taken from Unetwork’s Accounts, KYC and device attestation guide and written for people considering a RED nodes license. Unetwork can change this. If a task in the app says something different, follow the task.
You
Will be the ULO. RED nodes is the UNO. You never sign in as the node.
5 UP ($5 USD)
Where Unetwork currently requires KYC on your ULO account
1
ULO login is enough, even if you run more than one license
3
Device states: hardware attested, software attested, unattested
Most mix-ups come from treating these as the same. They are not.
People who take a license from this site are license operators. You claim a slot, we email a code, you paste it in the official app. You are not opening a node.
In the app, tap License Operator. When a slot is yours, we email a code and you paste it there. That login is your ULO account. KYC, withdrawals, and tasks all hang off this account — not off a node login.
We are the Unetwork Node Operator. We lease licenses. You do not create a UNO account to use one, and you do not manage our node.
Stay on License Operator. If the app asks you to pick a role, that is the one. You are not the UNO.
One verified ULO account can hold many licenses. Each license still runs on its own device.
KYC belongs to the ULO account. Attestation belongs to each device.
This is the line that matters most. One asks who. The other asks what device.
KYC asks
Unetwork verifies the person behind the account. It applies to the account, not the hardware. RED nodes never sees that check — we only asked for your name and email so we could send the code.
Attestation asks
Unetwork looks at the phone itself: is it a genuine physical device, and what level of device trust can it show? Each phone has its own state.
You can have one KYC-verified ULO account, several licenses, and several individually attested phones. You do not KYC every phone.
You can start without it. Unetwork currently handles individual KYC through Sumsub. It becomes required when one of these is true.
That’s Unetwork’s current incentive threshold. Verification is required once the account reaches it.
Withdrawals go through Unetwork’s rewards center, not through us. They may ask for KYC first.
Some work — including Extended Telemetry — needs a verified user even if you have not hit 5 UP ($5 USD) yet.
If you already completed the full Unetwork individual KYC through ShuftiPro, Unetwork says that still counts. You do not redo it only because new checks go through Sumsub. If you only did ID and not address, or you used all three attempts, complete the current Sumsub flow. The attempt limit has been reset.
Every participating phone has its own attestation. All three can currently connect to the network. The difference shows up when a task asks for a minimum level of device trust.
Hardware attested
The device can show hardware-backed attestation signals.
Can connect
Software attested
The device can show software-level attestation.
Can connect
Unattested
The device does not currently provide the required signals.
Can still connect
| Device state | Extended Telemetry | Entropy | Caller ID / SMS | Surveys |
|---|---|---|---|---|
| Hardware attested | Eligible | Eligible | Any state | Any state |
| Software attested | Eligible | Eligible | Any state | Any state |
| Unattested | Not eligible | Not eligible | Any state | Any state |
Extended Telemetry and Entropy currently need at least software attestation. Hardware and software are treated the same for Extended Telemetry. Attestation is an eligibility check, not a universal bonus. An unattested phone can still connect — it just cannot take those two tasks.
If the app and manage.unetwork.io disagree about attestation, refresh both. They use the same source. A flagged license is not the same as software attested — a software-attested device never shows a flag. If it lasts, write Unetwork at support@unetwork.io.
Your Unetwork login is the centre. A lease code from us attaches a license to that login. The phone that runs it has its own attestation.
KYC sits on your ULO account, once. Each license runs on one phone. Each phone carries its own attestation. RED nodes is the lessor — we are not a second login you have to keep.
One account, one email. A second account needs a second address. You do not need a pile of aliases to run more than one license.
Same ULO account, new address. Your user ID stays. Your KYC stays. This does not create a new Unetwork user, and it is the right move when you only want to change the inbox.
If you opened more than one ULO login by mistake, Unetwork can fold eligible ULO accounts into one. Licenses move to the account you keep. The other login is turned off. Start the merge from the ULO you want to keep.
A plus-address such as name+1@gmail.com can be an account email. Variants of the same inbox are not treated as separate people. Do not open more alias accounts. If you already have more than one ULO, merge into the one you want to keep, and start the merge from that account. If that destination is not KYC-verified yet, complete KYC there after the merge.
Wallet-only ULO? Attach an email in the management portal before a merge. Scout & Runner follows a valid ULO merge, but both accounts must be registered to the same country or the merge fails.
Keep these and the rest of the page is detail.
Pick the line that matches. Then do that — not three other things.
Claim a slot, then open the official app, choose License Operator, and paste the code we email you. Use one email. Complete KYC when Unetwork asks — not before you have to.
Keep one ULO account. Each extra license still needs its own device. You do not KYC each phone.
Use Merge Accounts. Keep the login you want. Start the merge from that account. Do not open more aliases.
Use Change Email on the ULO account you already have. Do not merge, and do not create a second login just to change the address.
It can still connect. It cannot currently take Extended Telemetry or Entropy.
It currently meets the attestation bar for Extended Telemetry and Entropy. Other task rules still apply — including KYC and the five-devices-per-IP cap on Extended Telemetry.
A wallet and an email are different parts of the same ULO account. If you need to merge accounts, attach an email in Unetwork’s management portal first.
For Unetwork account or device questions, write support@unetwork.io with your ULO email and the device state if it is about a phone. For a RED nodes license or a claim, write info@rednodes.ca.