Global Corporate Reference
中文

Global Corporate Reference

The Global Registry Pass

A company record anyone can check.

The Global Registry Pass (GRP) is a signed digital credential for a company. It states registration, active status and corporate ownership as the official registries record them, so a buyer can check in seconds what would otherwise take weeks.

  • Free to issue and free to check, for every company.
  • A W3C verifiable credential with a digital signature and an independent timestamp, checkable offline.
  • A public verify page, a web badge and an evidence pack with a QR code.
  • Registry facts only: no scores, no ratings, no data about people.

See a Global Registry Pass.

Illustrative preview with synthetic data. Public beta is in preparation.

A badge for a website footer or profile. It links to the public verify page and says whether the website itself was verified.

Global Registry Pass
Current
Company
Sample Company Ltd
Registry
Registry A · EX-0001
Jurisdiction
Illustrative jurisdiction
GCR ID
GCR 000123 4

Scan or verify
registry.example/verify/GCR000123-4

What happens after a GRP is issued.

How anyone checks a GRP, how it stays current, and how a mistake is corrected.

How anyone checks a GRP

Four checks in order: timestamp, signature, revocation and expiry. The result codes are the ones the public verify API returns.

How a verifier checks a GRP A credential with an optional token enters four checks in order. First the token, if given: its chain, its hash and its time; a failure returns TSA_TOKEN_INVALID, HASH_MISMATCH or TIMESTAMP_MISMATCH. Second the signature under the node's did:web key; a failure returns SIGNATURE_INVALID. Third whether the status list or revocation record marks it revoked; yes returns REVOKED. Fourth whether the time is past validUntil; yes returns EXPIRED. A credential that passes all four is accepted: VALID with a token, VALID_TIMESTAMP_PENDING without one. chain · hash · time skipped if no token key in did:web document eddsa-jcs-2022 proof status-list bit or revocation record now past validUntil yes yes no no no no yes yes Credential + optional token Token sound? Signature holds? Revoked? Expired? Accepted VALID with a token VALID_TIMESTAMP_PENDING pending = no token given Token rejected TSA_TOKEN_INVALID HASH_MISMATCH TIMESTAMP_MISMATCH Signature invalid SIGNATURE_INVALID Revoked or expired REVOKED EXPIRED Unreadable input gets no code. The form shows: “This node cannot read that credential or token.” Status check: with no signed status list for the credential there is no code. The API answers 503 and the form shows “Checking is not available right now.” Start or rejected result Check, yes or no Accepted result Success path Failure exit

Scroll sideways to see all of it.

How a GRP stays current

A GRP is valid for 30 days and is rechecked against its source daily or at each registry release. If the source changes, the GRP is revoked and a new one is issued.

GRP credential lifecycle A lifecycle phase map. A credential is requested, then issued and stamped, then re-validated daily and at each bulk source run. A request with no timestamp answer waits in timestamp pending for up to 72 hours. A live credential is revoked on drift of the source facts, on key compromise or on a challenge outcome, and a revoked credential is reissued as a new request. A credential that reaches its validUntil date expires. WAIT PRIMARY PHASES TERMINAL OUTCOMES REQUEST STAMPED NO TSA ANSWER WITHIN 72 H DAILY · BULK 30 DAYS KEY COMPROMISE CHALLENGE DRIFT REISSUE Requested build, stamp, sign Issued and stamped valid for 30 days Re-validated mapped facts compared Timestamp pending 72 h: revoke, reissue Revoked status bit set, list re-signed reissued, except upheld challenge Expired validUntil passed Phase Wait state Terminal outcome Drift revocation (focus) Transition Wait path 6 states · 10 transitions

Scroll sideways to see all of it.

How a mistake is corrected

Anyone can challenge a GRP without an account. GCRef rechecks the source, and the source decides the outcome. A person decides only when the source cannot.

Public challenge flow A member of the public files a challenge against a credential. The node applies a limit of 5 per address and 2 per credential per hour, then re-checks the source. If the source supports the credential the challenge closes and the credential stays valid. If it differs the credential is revoked and a new one issued. If the source cannot decide, the node escalates to the officer, who upholds the challenge and revokes the credential or dismisses it. Separately, a verified rep can dispute a fact, which closes automatically when a newer source fact supersedes it or goes to the officer after 14 days. CHALLENGER member of the public, no account NODE automatic checks, automatic close COMPANY'S REP verified rep OFFICER reviews escalations A dispute is a separate path: it concerns a fact, not a credential. Unresolved after 14 days it goes to the officer's disputes queue. FILE UNDER LIMIT SUPPORTS DIFFERS NO ANSWER ESCALATE DISPUTE Files a challenge verify page, no account Applies rate limits 5 per address per hour 2 per credential per hour Re-checks source GB: Companies House fetch BR: latest CNPJ release Closes: supported credential stays valid Closes: revoked new credential issued Escalates cannot be resolved Dispute auto-close newer fact closes it 14 d: officer's queue Disputes a fact verified rep, max 5 open Officer decides upheld: revoked dismissed: unchanged Step in its owner's lane Officer decision (focus) Flow Escalation handoff Separate path 4 lanes · 9 steps · 7 flows

Scroll sideways to see all of it.