ABOUT

The verification layer for private markets.

Public markets industrialised trust a century ago. A named third party puts a date and a signature on a specific set of documents, and a stranger can act on them. Private markets never got that layer. Thirteen trillion dollars now sits there, and the answer to how do you know is still a PDF and a handshake.

What we do

We check claims about private companies against their sources, we record exactly what we saw and when, and we anchor that record on Base so it cannot be edited afterwards. Not by the company, and not by us.

Then we do the part almost nobody does. We tell you how well each figure is actually known.

PROVENMachine-checked against a primary source, and anchored on Base.
CORROBORATEDConfirmed by more than one independent source.
SYNCEDPulled or computed from a primary source.
DECLAREDSelf-reported. One source. Recorded as a claim, not as a fact.
UNLITNo permissionless source exists. We leave it dark rather than guess.

That ladder is the product. A number without its state is not information, it is a rumour with a decimal point.

What anchoring does, and what it does not

An attestation proves that a specific piece of evidence existed on a specific date and has not been altered since. That is all it proves. It does not make a figure true, and putting something on chain never moves it up the ladder.

You can see us hold that line on our own flagship page. Anthropic’s revenue is anchored on Base, permanently, and still labelled Declared, because the only thing we can prove is that the company said it. Almost everything sold as verification quietly performs that promotion and calls the result a fact. That single refusal is the whole company.

What is live today

The permissionless layer. Anything checkable without anyone’s permission: public APIs, filings, job boards, status pages, archived snapshots. Collectors fetch it, hash exactly what they saw, and anchor the hash on Base.

SEE THE FIRST PROFILE →

What is not live yet

We would rather you read this here than discover it later. The opt-in layer is architecture, not shipped product. That is zkTLS proofs over bank, payroll and billing data, and an incentivised dispute layer for the soft claims no API can settle. It is next. It is not now.

This is the same standard we apply to the companies we report on. A roadmap described in the present tense is a Declared claim about ourselves, and we are not going to open with one.

How to check us

Every attestation we publish is signed by one address on Base. It is public, and so is the schema, because an attester nobody can identify is not an attester.

ATTESTER

0xa120EC43A349BA051a42163D9eD6adb9cF340b7B

SCHEMA

0x382e9448b0a66da972e72296ea0b662039f7bb62087a2027448bae79e111163d

Take any row, take its evidence hash, and check it against the chain yourself. You do not need our cooperation to do it, which is the point.

Corrections

If we have a row wrong, tell us. Corrections are published alongside the row they concern, with the date we were told and the date we fixed it. A verification layer that quietly edits its own history is just a database with better marketing.

BLUZAR, Inc. builds and operates the verification layer described above.

ardalan@blue-zar.comXLinkedIn