Address Registry lets you verify the legal entity controlling a blockchain address before sending or receiving a transaction. It's designed for one purpose: counterparty discovery and verification for digital asset transactions.

Address Registry is free, enabled by default for all Fireblocks customers, and currently covers addresses within the Fireblocks network.

This article covers the registry itself: what it returns, how it works, and its limits. For using it as a check within your compliance policy, see Address Registry Screening in Compliance Screening.

What it returns

Querying an address that belongs to an opted-in Fireblocks customer returns:

• Verification status: whether the counterparty's legal entity information has been independently verified, or is based on Fireblocks data without independent validation.
• Legal entity information: entity name, jurisdiction, and Legal Entity Identifier (LEI) if declared, plus a Travel Rule provider and compliance contact email if the counterparty has shared those too.

If an address can't be resolved, because the counterparty isn't a Fireblocks customer, has opted out, or is in an unsupported environment, the result is simply "not found." That doesn't mean the address is unhosted, illicit, or non-compliant, just that there's no match.

How it works

Address Registry works on consent: when it's active for your workspace, other opted-in Fireblocks customers can look up your vault addresses and see your legal entity name and jurisdiction, and you can do the same for theirs. Results are deterministic, based on registered data, not inferred from transaction heuristics.

Only workspaces with Address Registry enabled can perform queries. See Acceptable use below.

Look up an address

1. Go to Security > Policies > Compliance > Address Registry.
2. Enter the blockchain address in the search bar.
3. View the result.

You can also look up addresses via the API.

Opting out

All workspaces are opted in by default, including new ones you create in the future. You can opt out at the individual vault account level, the whole-workspace level, or, by contacting your Customer Success Manager, at the account level across every current and future workspace.

Opting out means lookups against your addresses return "not found," and you lose the ability to query other addresses or use any compliance workflow that depends on the registry. Opting back in restores both.

Limitations

Address Registry isn't currently available for workspaces hosted on European or Swiss environments, due to infrastructure isolation between production instances; queries against these workspaces return "not found." It's also not available in Developer Sandbox workspaces.

Acceptable use

Address Registry exists for one purpose: verifying counterparties in connection with digital asset transactions. You must not:

• Use it for any other purpose.
• Scrape, bulk-download, or systematically extract data from it.
• Resell, redistribute, or commercialize query results or any data obtained from it.
• Attempt to identify, profile, or de-anonymize individual people using its data.
• Use it for surveillance or competitive intelligence.
• Circumvent technical controls, authentication requirements, or rate limits.

Fireblocks monitors usage for misuse and can suspend or revoke access, with or without notice, if it detects abuse. Use must comply with your agreement with Fireblocks.

FAQ

The questions below are the ones readers ask most often.

What does "verified" mean?

A result is verified when the counterparty declared an LEI, the entity data came from GLEIF, and Fireblocks' compliance team confirmed the legal entity name matches Fireblocks' own client records. Anything else is based on Fireblocks data without that independent check.

Can I look up any address, or only ones I am about to transact with?

Any address. There is no requirement to have an active or pending transaction with it.

What can someone learn about my customers or end users?

Nothing. A lookup only returns information about the legal entity controlling a vault, its name, jurisdiction, and LEI if declared, never anything about that entity's own individual account holders.

How is this different from blockchain analytics?

Blockchain analytics firms link addresses to entities using heuristics, typically without consent. Address Registry is consent-based and deterministic: every result reflects data an institution chose to register, not an inference.

What stops someone from scraping the registry?

You can only look up a specific address; you can't enumerate the registry or query in reverse. Fireblocks also enforces authentication, rate limits, daily caps, and monitoring to keep query volume proportional to transaction volume.

Does Fireblocks sell this data?

No.

What are the General Data Protection Regulation (GDPR) implications?

Address Registry is designed to return information at the legal entity level and isn't intended to contain data about individual account holders. Fireblocks doesn't maintain any link within the registry between vault addresses and identified natural persons. You should still assess your own data protection obligations around participating in it.

Developer portal

See Address Registry and Look up legal entity by blockchain address.