Fleet Registration
How to register a fleet: where to go and which steps to follow. The path depends on your organization's plan — on the Managed Service Nodle signs and pays for every on-chain operation, while everyone else registers on-chain from their own wallet.
How it works
On the Managed Service plan, Nodle performs every on-chain operation for you — claiming the fleet identity, registering locations and swarms, and maintaining them afterwards. You fill in a short form, and your dashboard wallet never needs funding: no tokens to buy and no gas to pay.
Registering a fleet requires the admin role. Admins and editors can manage an existing fleet's locations, swarms and webhooks.
Register a fleet
- Go to Fleets in the sidebar and click Register Fleet. The registration form opens straight away.
- Details — enter the tag identifier and a fleet name. If you paste a bare UUID, pick the tag type as well. The dashboard checks on-chain that the identifier is not already claimed.
- Locations (optional) — add the countries, or the administrative divisions, where the fleet operates. The first location you add fixes the fleet at country or local level, so the rest must match it.
- Swarm membership — build the filters that match your devices' advertisements, or continue without them to register the fleet with an empty filter and add them later.
- Click Register. Everything is submitted as one request; the summary that follows lists the claim, location and swarm transactions.
What it costs you
Nothing on-chain — Nodle posts the bonds and pays the gas. Your plan includes a number of fleet registrations per billing period, and the form shows how many are left and the date the count resets. Once they are used up, new registrations are refused until that date; contact the Nodle team if you need more before then.
After registering
- The fleet appears under Fleets. Open it to add locations, promote or drop a location tier, manage swarm membership, set up webhooks, or delete it — all handled by Nodle in the same way.
- Already claimed a fleet yourself? Its Locations card shows a Set Nodle as Operator button. Confirm it once and Nodle can run registrations and maintenance for that fleet too.
Where to register
- Go to Fleets in the sidebar and click Register Fleet.
- Your organization is not on the managed service, so a dialog offers the upgrade — choose Continue on-chain to register yourself.
- Fill in your fleet identity and name, then follow the prompts. The exact token amounts are always shown before you sign anything.
Registering a fleet requires the admin role; admins and editors can manage an existing fleet's locations and swarms.
What you need
- Your dashboard wallet — created automatically with your account (no MetaMask or other external wallet). Its address is shown in the dashboard header; this is the address you must fund.
- NODL on zkSync — for the registration bond (amounts below). Tokens on Ethereum mainnet or other chains will not work.
- ETH on zkSync — for gas. Every transaction (approval, claim, location, swarm) pays a small gas fee.
Tokens required
Registering a fleet posts a bond in NODL. Bonds are deposits, not fees — removing (burning) a registration returns the bond to whoever paid it. The amounts below are read live from the production registry contract on zkSync Era.
- Fleet claim: 1,000 NODL — the one-time bond to claim your fleet identity.
- Locations (optional) — each registered location posts an extra bond that depends on the tier you choose when you add it; country-level costs 16× the subdivision level:
| Tier | Subdivision | Country |
|---|---|---|
| 0 | 1,000 NODL | 16,000 NODL |
| 1 | 2,000 NODL | 32,000 NODL |
| 2 | 4,000 NODL | 64,000 NODL |
| 3 | 8,000 NODL | 128,000 NODL |
| 4 | 16,000 NODL | 256,000 NODL |
| 5 | 32,000 NODL | 512,000 NODL |
Bond amounts grow ×2 per tier up to tier 23. Higher tiers increase your fleet's regional discoverability. Swarms (the filters that match your devices) have no bond — they only cost gas.
Registration steps
- Claim the identity — enter your fleet identity and name. The operator address is optional and defaults to your own wallet; set it only if a different address should run the fleet day to day. If prompted, approve the NODL bond first; the claim then submits automatically.
- Wait for recording — after the claim confirms, the dashboard records your fleet so detections can flow. Keep the dialog open until it finishes; use Retry recording if it fails. A fleet that is not recorded shows no data.
- Add locations (optional) — from the fleet's page, register countries or subdivisions and pick a starting tier for each.
- Register a swarm — from the fleet's page, so the network starts matching your devices' advertisements.
Fleet identity formats
ibeacon:<uuid>(or a bare UUID) — iBeacon proximity UUID.eddystone:<20 hex>— Eddystone-UID namespace (10 bytes, not a UUID).cid:<4 hex>— Bluetooth SIG company ID, e.g.cid:076c.sdata:<4|8|32 hex>— service data UUID.cid:<4 hex>/<2 hex>— a company ID narrowed to one advertising protocol byte. This is an ingest filter kept in the dashboard only: it has no on-chain identity, so it costs no bond and no gas, and locations and swarms do not apply to it.
An identity with a #<instance> suffix is a single device, not a fleet, and cannot be registered here.
Managing the fleet afterwards
From the fleet's page you sign each of these yourself, so keep some ETH on zkSync for gas:
- Locations — add one, promote it to a higher tier (posts the difference in bond), drop it to a lower one, or burn it to release the bond.
- Update operator — from the Locations card, hand operation of the fleet to another address.
- Swarms — register, accept or delete swarm membership; no bond, gas only.
- Delete fleet — burns the on-chain registration and returns the bond.
Prefer not to manage any of this? Subscribing to the Managed Service plan lets Nodle sign and pay for these operations on your behalf.