BAZR token contract address, Solana mainnet-beta:

7YhmLtcwtqdTkoGZWMJ7AkQzoFdUJK4FTEk6b1gpump

Token-2022 mint, 6 decimals, fixed supply of 1,000,000,000. Mint authority and freeze authority are both revoked, so no further supply can be minted and no account can be frozen. Both facts are readable straight off the chain on solscan.io and solana.fm.

The Anchor program described further down is a different address, and it is not deployed on any cluster right now. The two are not interchangeable.

Solana meme aftermarket. One degen's exit is another's entry.

A token that stopped trending did not stop existing. It went to the attic. BAZR takes launchpad graduates that nobody watches any more, reads what is still measurably on chain, and puts a price tag on the result. The tag carries the number and the reason for the number, in that order.

The relic score is a survival-signal summary, not a forecast of recovery. It reports what five on-chain axes say about a token today. It does not estimate whether a token comes back, and no part of this organisation sells that estimate. When the signals disagree, the verdict says so instead of picking a side.

Five axes, fixed weights, published before any score is shown. The full derivation of every axis is in docs/relic-spec.md.

A missing axis is not scored as zero. It is removed from the denominator and the remaining weights are renormalised. Scoring an unreadable axis as zero would punish a token for the indexer's blind spot, and the number would quietly stop meaning what it claims to mean. So each axis carries a status of ok or unknown, the score divides only by the weight actually available, and every axis reports the contribution it made to the final number.

The middle band is where survival signals genuinely conflict. Forcing dead or dormant there would manufacture a confidence that the data does not contain, so BAZR returns unclear and shows the breakdown. A high aggregate with liquidity below 40 is also unclear, never dormant: a token you cannot exit is not sleeping.

A curator who opens a stall posts a bond and lists a token with a written reason. The outcome of that listing is written on chain either way. Losses are recorded at the same size as wins, in the same account, and are never hidden behind an aggregate. A stall page shows resolved wins and resolved losses side by side, and a slashed bond stays in the history.

This is the part after graduation, and only that part.

• No new token feed, no launch sniping, no trending board. That ground belongs to other tools and BAZR does not compete for it
• No exchange of its own. No order book, no perpetuals. Route calculation stays route calculation
• No prediction of price, no revival estimate, no signal to buy. The score is a description of the present, not a claim about the future

The Anchor program is not deployed on any cluster. It ran on devnet from 2026-08-18 and was closed there on 2026-08-20 -- the same day it was deployed to mainnet-beta and closed again six minutes later. Every closing signature, slot and recovered rent figure is listed in the main repository README. The source and the IDL are still in the repository and can be redeployed; what is gone is the deployment.

• The scoring rules were published before the scores. Axis definitions, weights, renormalisation and the exact verdict thresholds are all written down and versioned in the open.
• One full stall cycle ran on devnet. A stall was opened with a bond, listings were resolved both ways, and the resulting record carries two wins and one loss against the same keeper. Closing the program removed the executable, not those accounts -- they are still readable on devnet, and nothing can change them.
• The IDL was published on chain, not only in the repository. While the program was deployed the IDL account above was owned by the program itself and anyone could decode the instructions from it without trusting this page. That account was closed with the program on 2026-08-20, so today the checkable copy is the committed one in the repository.
• A TypeScript SDK and a terminal client cover the same scoring API the site uses, so a score can be pulled without a browser.
• The Tag browser extension source is in the open. It overlays the price tag on a token address wherever that address appears. It is source only and is not listed in any extension store.

1. A token address goes in. It has to be a launchpad graduate, not a fresh launch
2. The indexer reads the five axes and marks each one ok or unknown
3. Available weights are renormalised, the score is aggregated, and each axis reports its contribution
4. Thresholds turn the aggregate into dead, dormant or unclear, and the reason travels with it
5. The tag renders the number next to the breakdown that produced it, never the number alone
6. A curator who disagrees can open a stall, post a bond and list the token with a written reason, and the outcome is settled on chain

flowchart TD
    spec["relic spec<br/>BazrMarket/bazr, docs/relic-spec.md"]
    prog["Anchor program<br/>BazrMarket/bazr, not deployed"]
    api["Scoring service<br/>api.bazr.market"]
    web["Front end<br/>bazr.market"]
    sdk["SDK and terminal client<br/>BazrMarket/bazr-sdk"]
    ext["Tag browser extension<br/>BazrMarket/bazr"]

    spec -->|fixes axes, weights, thresholds| api
    api --> web
    api --> sdk
    api --> ext
    prog -->|bonds, resolved wins and losses| web

• Website: bazr.market
• Scoring API: api.bazr.market
• X: @bazrmarket
• Main repository: BazrMarket/bazr
• SDK and terminal client: BazrMarket/bazr-sdk
• Scoring specification: docs/relic-spec.md
• Program FSLSR2xYiR5NPWg6g8DZ1KyVRVa7xW37gDStbaDfSXLb: closed on devnet and on mainnet-beta, what happened
• Program source and committed IDL: BazrMarket/bazr/anchor-program
• License: MIT