UNIT BUREAU

Desk operations

Registry research checklist

This is the repeatable pass Unit Bureau uses when a profile should feel materially more authoritative: dated claims, primary URLs, and honest limits. It is not legal advice and does not replace a counterparty confirming live behavior for your account.

Tier 1 priority slugs (current)

These twenty entries are maintained first for depth and freshness. Each should meet the checklist below on every full desk cycle.

Before you open sources

  1. Confirm which legal entity and brand name the counterparty uses in contracts for the same product.
  2. Decide whether you are documenting consumer, SMB merchant, or enterprise treasury behavior separately.
  3. Note the country or corridor the requester cares about; global marketing pages often overstate coverage.

Source rules

  • Minimum three primary URLs for Tier 1 after a full pass: docs, support or developer reference, and product or coverage overview.
  • Prefer dated changelogs, API reference, or help-center articles over social screenshots.
  • If only a press release exists for a claim, label the claim as press-sourced and keep status conservative.
  • When two official pages conflict, record both links and explain the conflict in uncertainty notes.

Evidence summary format

Use plain sentences. Recommended pattern:

Desk review as of YYYY-MM-DD (public sources only). (1) Claim and URL. (2) Claim and URL. (3) Claim and URL. Not verified: account types, live fee quotes, or private beta programs.

Settlement notes format

Describe how funds are intended to move (custodial versus self-custody, batch versus instant, fiat off-ramp, chain selection, memo rules). If the vendor is silent, say so explicitly.

Status transitions

  • Listed when relevance is clear but you lack multi-source confirmation.
  • Reviewed when multiple primary sources align on the same product path, or one authoritative doc is comprehensive and recent.
  • Verified only per methodology (operator confirmation, repeatable checks, or observed flows where permitted).

After the pass

  • Update last reviewed to the pass completion date.
  • Re-read the public profile for tone: no hype, no regulatory overclaiming.
  • If the business wrote in, consider owner-confirmed per claim workflow.

Full methodology · Registry