Golova ID

Digital device passport

Golova ID is a passport for a specific physical device: serial number, photos, ownership and repair history, “wanted” status. It is issued by the owner in the Golova CRM, can be checked by anyone via QR or serial number, and transfers to the buyer on a marketplace sale. The history root is anchored in the blockchain.

❋ Why

Theft protection

A stolen device is hard to launder: the owner flags the theft, and the “wanted” status is seen by anyone who checks the serial number or QR — here, on the marketplace, in any repair shop.

Ownership history

The chain factory → distributor → rental company → second-hand buyer. Every event is recorded with a hash and a date and cannot be rewritten after the fact.

Trust on the marketplace

A listing with a passport carries the “Golova ID” badge: provenance confirmed, the device is not reported stolen. Such equipment sells faster and for more.

Warranty and insurance

Serial number, photos of the condition and the nameplate, commissioning date — a ready-made file for a warranty or insurance claim.

❋ How to check

QR on the device, serial number or GLV number

Scan the sticker or enter the serial number on the check page. The answer: verified / wanted / sold, brand and model, issuer, passport issue year, blockchain anchor, device photos.

A red “wanted” banner — do not buy and notify the owner. “Not found” — there simply is no passport.

Honestly about what the passport proves: one issued by the owner confirms registration, ownership and history, but not the authenticity of the device — only a passport issued by the manufacturer confirms that.

Who sees what
  • Everyone: status, brand and model, issuer, year, number of events, anchor, device photos.
  • Owner and buyer: serial number, nameplate, full history, parameters.
  • Everyone, if the owner decides: the “open full passport” switch on the passport page in the CRM.

❋ How to issue

  1. 01

    In the Golova CRM open Tools → Passports → “Issue Golova ID”.

  2. 02

    Pick the item from the catalog — brand, model and photos are pulled in automatically. Warehouse units with serial numbers are listed, so you can issue passports for a whole batch at once.

  3. 03

    Add photos: the device from 3–4 angles and a close-up of the nameplate with the serial number. Custom parameters — board numbers, kit contents, notes — are optional.

  4. 04

    Print QR stickers (a sheet for the whole batch in one click) and put them on the devices. The QR leads to the public check.

Theft: on the passport page in the CRM press “Report theft” — the “wanted” status appears here and on the marketplace immediately. Found it — clear the status in the same place.

❋ Sale on the marketplace

  1. 01

    When publishing the device to the marketplace from the CRM, keep the passport in the listing — it is filled in automatically and the card gets the “Golova ID” badge.

  2. 02

    The buyer checks the passport before the deal: status, issuer, year, blockchain anchor, device photos.

  3. 03

    Once the deal is confirmed, the sale is recorded in the passport and the buyer receives a claim code in the marketplace deals cabinet.

  4. 04

    A buyer with Golova takes the passport over when importing the item into their catalog; without Golova — by the code, once they sign up. The ownership history continues under their name.

❋ Blockchain anchor

Passport data lives in the Golova registry, and a Merkle root of all histories is periodically published to a blockchain (an L2 network). Each passport keeps an inclusion proof: anyone can verify that the history existed in this form at the time of the anchor and has not changed. This proves immutability without having to trust Golova itself. New events go into the next batch.

Next: factory issuers — a passport “from the production line” is worth more than one created by the owner after the fact — and repair shops writing the service history into the passport.

❋ Questions

The device has no passport — is that bad?

No. Passports are issued by owners voluntarily; most equipment has none yet. “Not found” is not a warning sign, just missing data. The warning sign is the “wanted” status.

Who issues a passport, and can someone issue one for a device they do not own?

The issuer is a Golova client company; its name comes from its settings, not from user input. The passport is bound to the issuer account and transfers only through a deal or a claim code. Later, factories will be able to issue passports at production.

What is visible to everyone, and what is not?

To everyone via QR: status, brand and model, issuer, year, number of events, anchor, device photos. The serial number, nameplate, full history and parameters are visible to the owner, the buyer of the deal and the holder of the claim code — or to everyone if the owner has opened the passport.

Can the history be forged?

Every event stores the hash of the previous one, and the root of the whole history is periodically published to a blockchain network. Changing any record breaks the chain and diverges from the anchor — forgery is visible.

How much does it cost?

Issuing passports, checks and events are free for Golova clients, with no limits.

Is there an API?

Yes: GET /api/passport/… (serial number or GLV code) returns the public view of the passport as JSON — for marketplaces, pawnshops, repair shops and AI agents.

Buying second-hand? Check the device in ten seconds.

Check a device