About BLUZAR

Written by Ardalan Javadi, founder of BLUZAR

Introduction

BLUZAR's vision of one market, where private and public companies trade on the same verified record, has drawn people from finance, crypto, and AI. But the promise has been hidden behind technical language: ladders, attestations, Merkle roots. This page answers why BLUZAR matters, why you should care, and why it has to be built in the open rather than sold by one vendor.

Summary

Public markets work because of an invention most people never think about: the shared record. Rules for what counts as a fact about a company, who must report it, where it is filed, and how old it may be. GAAP, the audit, the filing. That record lets a stranger buy a share from another stranger without calling the CFO. The record made the market.

Private markets never got that record. They got vendors. A valuation firm prints a number, a journalist repeats it, a broker quotes it, a second vendor cites the journalist. Three sources, one fact, no key, no age. That is not a data problem. It is a missing institution.

Two supercycles now arrive at once: tokenization, which puts private assets on rails built for public ones, and agents and other new participants, who cannot take a PDF on trust. Both need the same thing: a record of what is known about an asset, by whom, from where, and how old it is.

BLUZAR is that record, built as rules rather than as a company that owns the answers. Every fact becomes a claim with a key (entity, field, unit, period, source class), a source, a state, and an age. Nothing reaches the display without those four. Claims are published daily as one file per company and their root is written to a public chain. The data is free, the way an encyclopedia is free. Where no verifiable source exists, the field is dark, and the record says what it would pay to light it.

By analogy: Bitcoin did not tell miners how to build their machines. It defined the rules that pay for computing power to show up. BLUZAR does not tell the world where private company facts come from. It defines the rules that pay for a fact to become verifiable.

Understanding BLUZAR

BLUZAR is hard to understand for the same reason it is powerful. It defines only the ladder: what each source class can earn, when two sources count as independent, when a claim replaces an older one. Who fills the record, and how, is left open. A vendor can send a few analysts to call a few brokers. A rule set that pays for verified facts can draw on every filing, every register, every fund that marks a private share, every employee who can prove a grant, and every analyst willing to be scored against the next mark. BLUZAR never has to hire them. It has to keep the rules honest.

BLUZAR versus a data vendor

A vendor is paid for scarcity: closed inputs, private method, no way to know why two vendors disagree. BLUZAR is paid, later and on top, for what only works once the record is trusted: tokenized LP interests and share verification, an analyst layer with stakes, and an API with proofs. The inputs are named, hashed, and dated. The price formula has a version and a test vector. When two claims disagree, both are on the page with their states, and the older one lives in history rather than under the rug. The record itself stays free.

The ladder

Every claim carries one of five states. The state is assigned by rule, never by hand.

  1. Proven · white #FFFFFF. zkTLS proof at the source verified by two attestors, or a signed API response from the source. Not yet shipped. No row has earned it.
  2. Corroborated · cyan #6EF2FF. Two independent sources that cannot see each other agree within tolerance. Two articles quoting one release are one source.
  3. Synced · bright blue #4A90F4. Pulled from a primary filing, register, or chain, with the document hash and reference.
  4. Declared · violet #7C10F5. One named source: self reported, press, or an estimate.
  5. Unlit · slate #4646BE. No permissionless source exists. Shown as a count and a bounty, never as a placeholder or a synthetic number.

Yellow #F8DE4F marks the active door, the one being viewed. The field is deep blue #0B0BA8.

The sphere

The doors on a company's sphere are its DNA: the rubric fields that apply to that entity given its type and facts. A young company has about 12, a late stage company about 40. Doors sit in fixed sectors by category (marks, funding, revenue, team, technology, cap table, traction) so two spheres are comparable at a glance.

Door color is the state of the latest claim on that field. Brightness is the score: the sum of state weights (Proven 1.0, Corroborated 0.8, Synced 0.6, Declared 0.2, Unlit 0) divided by the number of DNA fields, with age decay so a stale mark dims but never goes dark. The score is never printed as a number.

On chain

Base mainnet, Ethereum Attestation Service. Schema UID 0x382e9448b0a66da972e72296ea0b662039f7bb62087a2027448bae79e111163d. The attester address is shown on each attestation and on the verification layer of every page. Attestations stay valid across attester rotations. Anchoring never promotes a claim; it only proves the snapshot existed on that day.

Attestors for the Proven state: none yet. The first two attestor paths (Reclaim zkTLS provider plus a self run TLSNotary notary) are on the roadmap below.

Team

Ardalan Javadi, founder of BLUZAR, host of SecondPod.

Roadmap

Not shipped at launch, stated plainly:

  1. Proven state. zkTLS proof flows (Carta holder lines, broker confirmations, founder revenue ranges) and the second attestor.
  2. Venue quotes with proof of fetch (Hiive, Forge, EquityZen, NPM). Until then venue prices are absent, not estimated.
  3. Certificate of Incorporation pulls for price per share and preference stacks.
  4. Analyst leaderboard with stakes. The founding analysts are listed as Declared rows with zero stake until they claim a key.
  5. /ask answers cite claim UIDs before it moves off the current model.
  6. The BLUZAR X poster runs in approval mode for two weeks, then capped at 8 posts a day. Every post cites a claim UID or a page URL.
  7. Fund pages are firm level at launch. Performance rows (IRR, TVPI, DPI) are Unlit with a bounty until a public pension report lands.
  8. The subnet. Credits are paid now; conversion to alpha waits on the conditions in the whitepaper.

Parked during the September 8 to 10 build

Nothing parked as of September 8 2026. This list is copied from the build log at each integration round.