BAZR - Solana meme aftermarket
One degen’s exit
is another’s entry.
Launchpad graduates get forgotten, not deleted. BAZR lays them back out on the stall, prices what actually survived on chain, and prints the working on the tag.
Price it now
no wallet neededNobody threw them out.
They just stopped looking.
A launchpad graduate does not disappear. The pool, the holders and the deployer wallet are all still there, on chain, readable by anyone. What disappears is attention, and attention is the only thing every other tool measures.
Tooling coverage after a token graduates
Opened so far
Reading the index
Minute 0 to hour 1
Covered, heavily
New pairs, sniper flow, trending boards. Half a dozen products fight over this window and they are good at it.
Hour 1 to day 30
Covered, thinly
Charts still load. The wallets that mattered have already moved and nobody is writing the post-mortem.
Day 30 onward
Not covered
Pooled liquidity, deployer behaviour, holders who never left -- still on chain, still readable, and not priced by anything.
Five things that
are still measurable.
Relic is a survival-signal summary, not a forecast. Five axes are read off chain, weighted, and added. Anything that cannot be observed is marked unknown and struck out of both the sum and the divisor, so a token with a deleted account is not filed under dead by accident.
How spread out the remaining holders are, once exchange and liquidity wallets are taken out.
- -Top 10 non-custodial wallets hold 21.4 percent
- -418 wallets still hold a non-dust balance
- -Largest single holder has not moved in 96 days
total = sum of contributions / sum of observed weights = 47.29 / 0.88 = 54
Unclear. Not enough signal to call it.
So11111111111111111111111111111111111111112
worked example - drag the axes to change it
Survival-signal summary, not a prediction of price or revival.
Mark an axis unknown and the total can rise. That is the renormalisation working: a missing reading is removed from the divisor rather than counted as a zero.
The working
goes on the tag.
Weights, renormalisation and the exact figure that produced the total. If a term looks wrong to you, it is right there to argue with.
observed = axes where status == "ok"
raw = sum(axis.score * axis.weight for axis in observed)
divisor = sum(axis.weight for axis in observed)
relic = round(raw / divisor)
# unknown axes leave the sum AND the divisor.
# folding them to 0 would file every token with a
# deleted account under "dead", which is a broken
# measurement rather than a finding.
holder_dispersion 62 w 0.25 -> 15.50
lp_residual 41 w 0.25 -> 10.25
dev_wallet_state 78 w 0.20 -> 15.60
floor_shape 33 w 0.18 -> 5.94
social_afterglow unknown w 0.12 excluded
raw = 47.29
divisor = 0.88 (of 1.00 declared)
relic = 47.29 / 0.88 = 54
verdict = "unclear"Survival-signal summary, not a prediction of price or revival.
What the number is not
- notA forecast. It says what survived, not what happens next.
- notA recommendation to buy anything. It is a reading, and readings go stale.
- notA ranking. Two tokens on 61 are not interchangeable; open both and read the axes.
- notComplete. Five axes are five axes. Anything they do not observe is not in the number.
Post a bond.
Keep the receipts.
A stall costs a bond in BAZR. Every listing carries a written thesis and resolves to a hit or a miss on chain. Both are counted. Neither is hidden.
shelfrat
bond 1,000 BAZR - 24 listings
Calls the thin-liquidity ones. Right less than half the time, says so.
boxcutter
bond 2,500 BAZR - 41 listings
Bond slashed twice for listing a token with a live mint authority.
lot19
bond 500 BAZR - 8 listings
Eight listings is not a record yet. Shown with the sample size attached.
tarpline
bond 5,000 BAZR - 63 listings
Highest bond on the row. Also the longest list of misses on the row.
There is no win-rate badge anywhere on this site. The index will not even serve one as a single field: hits and misses come back separately so that dropping the denominator has to be a deliberate act somebody can be asked about.
Stalls open with the on-chain releaseRecords above are worked examples of the stall format, not live curators.
What is out on the table
Three things get built. One of them works today. The other two are described here in the present tense because that is what they will do, not because they do it yet -- each card says which is which.
On the table
Rummage board
Paste a mint, get the relic score, every axis, every label, and the arithmetic that produced the total.
Loading the van
Stalls and crates
Curators post a bond and a thesis. Crates hold a basket of survivors and rebalance on a published rule. Both settle on chain.
Still in the crate
Tag overlay and CLI
The price tag follows you: a browser overlay that puts the score on any mint address you meet, plus the same data from a terminal.
No dates. A date on this list would be a guess dressed as a commitment, and the two unfinished items depend on an audit and a mainnet deploy that are not scheduled yet.
Pack a crate.
Publish the rule.
A crate holds several post-graduation tokens at published weights, with a published rebalance rule. Issuing one burns a fee in BAZR. Components and every rebalance are readable on chain, including the ones that went the wrong way.
crate-03 - rebalanced 2x
10,000 / 10,000 bps
Every component above 50 at the time it went in. Two have fallen since.
blended relic
63
weighted mean of component relic scores, divided by the weights actually set. Same renormalisation rule as a single reading.
Rebalance rule
- - Published before the crate opens, not after a component falls.
- - Every rebalance is a transaction with the old and new weights in it.
- - A component that drops below the crate floor is removed and named.
- - The issue fee burns. The burn is a signature you can look up.
Both crates above are worked examples of the format.
Say the flaw first,
then quote the price.
Rug traces, bundled launches and live mint authorities go on the tag. They are not buried in an expandable, greyed out, or dropped from the summary. A market where the seller picks which labels to print is not a market, it is a listing.
The usual listing
Curated for the seller
Four labels withheld. Nothing here is false. The omissions are doing the work.
The tag
Everything found
Same token, same chain, same afternoon. The three alerts are the reason anyone would want the reading at all.
The label sheet
LP burned
Burn instruction on the LP mint, one signature, verifiable on chain.
Bundled launch
14 buys in the deploy block, all funded from one wallet 6 minutes earlier.
LP pulled
Pool drained 14 days after graduation. Priced in, not hidden.
Deployer still holding
Deployer wallet has not sent out since day 9. Could change tomorrow.
Serial deployer
Funding path shared with 6 other launches. Shared paths get false hits.
Mint authority live
Mint authority never revoked. Supply can still be changed.
Wash-shaped volume
Round-trip pattern across 3 wallets. Low confidence, shown anyway.
Exchange wallet seen
Known exchange deposit wallet holds 4.1 percent. Excluded from dispersion.
The tag follows
the address.
The reading is not locked in this page. It is an open read endpoint, a package, a terminal command, and a browser overlay that puts the score next to any mint address you meet somewhere else.
curl https://api.bazr.market/relic/So11111111111111111111111111111111111111112
{
"mint": "So11111111111111111111111111111111111111112",
"score": 54,
"verdict": "unclear",
"axes": [ /* all five, unknown ones included */ ],
"tags": [ /* every label found, alerts too */ ],
"disclaimer": "Survival-signal summary, not a prediction of price or revival."
}rate limit
30 reads per minute with no key. Forced refresh is 5 per minute. Over the line you get a 429 and a Retry-After header, not an empty body.
sources
Every response lists what it read and when. If a number came from somewhere else, that is in the payload rather than in a blog post.
browser overlay
A tag on every address
The overlay watches for mint addresses on whatever page you are already on and hangs the price tag next to them: score, verdict, and the alert labels. Click it and the axis breakdown opens in place.
...anyone still holding So1111...1112 after that pull?
Overlay and terminal ship after the on-chain release.
What the ticker
is holding up.
$BAZR sits under four things that settle on chain. Each one either locks the token, burns it, or moves it between people who did something checkable.
Stall bonds
Opening a stall locks BAZR. List something with a live mint authority or a pulled pool and the bond is slashed. The record stays on chain either way.
Crate issue fee
Packing a crate burns a fee in BAZR. The burn is a transaction you can look up, not a line in a chart.
Scoring API
Relic scores and labels are served to anyone. Volume above the free tier is paid in BAZR by the teams pulling it.
Slash pool
Slashed bonds do not go to a treasury wallet. They go to the holders who flagged the listing, and the split is published with the transaction.
What it is not for
- It does not gate the readings. The score API is open to anyone under the rate limit, key or no key.
- It does not buy a better score. Weights are fixed in the spec and identical for every mint.
- It does not pay a yield. Slashed bonds move to the people who flagged the listing, and that is the only distribution there is.
contract address
Not deployed. This space stays empty until there is a real address to print, and it will print in full, never shortened.
Ask before you buy
Everything below is answered the way it would be answered across a table, including where the answer is no.
No, and nothing on this site claims it does. The score summarises what survived: holders, pooled liquidity, deployer behaviour, the shape of the floor, and whether anyone is still talking. A token can score 80 and never trade again.
A score you cannot check is a rumour with a number attached. Every axis, weight and contribution is in the response body and on the page, so you can disagree with a specific term rather than with a black box.
It is marked unknown and dropped from the total, then the remaining weights are renormalised. Scoring a missing axis as zero would mark every token with a deleted account as dead, which is a measurement failure, not a finding.
No. The time axis starts after graduation. Live feeds, trending boards and sniping are somebody else's product and BAZR is not going to be a worse copy of them.
A stall costs a bond. Listings resolve to a win or a loss and both are counted on chain. A stall page shows the misses at the same size as the hits, because a record with the losses removed is an advertisement.
A basket of post-graduation tokens with published weights and a published rebalance rule. Packing one burns a fee in BAZR. The components and every rebalance are readable on chain.
No. Haggle prices a route through existing liquidity and applies a slippage cap. When a route comes from an external aggregator, the response says so in the source field.
Yes. Every label carries a confidence value and the evidence that produced it. Serial-deployer detection follows funding paths, and funding paths are shared for innocent reasons, so that one is published at medium confidence.
The scoring package, the labeller and the on-chain program IDL are published. The read API is open to anyone below the rate limit without a key.
Says so. Dead is a valid verdict and it gets printed on the tag in the same size as any other. A market that can only describe things as early is not a market.
No exchange.
Just an honest route.
There is no order book here, no perpetual, and no in-house automated market maker. Haggle finds a path through the liquidity that is already out there, holds it to a slippage cap, and writes the aggregator it used into the response.
Quote shape
computed in this page- price impact
- 7.79%
- expected out
- 1,106 USD
- minimum out
- 1,095 USD
- pool depth assumed
- 14,200 USD
- source
- jupiter
Thin liquidity: price impact above 3 percent. The warning field is populated and travels with the quote instead of being left to the interface.
Illustration of the response shape against a stated depth. Not a live quote and not routable.
What it does
Reads the pools that exist, prices a path, applies your cap, and returns the hops so you can see what you are trading through.
What it will not do
Route into a pool it cannot price, hide a thin-liquidity warning, or present an aggregator's result as its own work.
Why it says the source
An aftermarket for forgotten tokens is thin by definition. Anyone routing size through it deserves to know whose liquidity map produced the number.
boundary
New pair feeds, trending boards and sniping are somebody else’s product, and they are good at it. BAZR starts where they stop: after graduation, on the stock nobody is watching.
13 - Haggle
Bring the thing
you gave up on.
Paste the mint you have been holding since it went quiet. You will get five axes, a verdict in plain words, every label found, and the arithmetic that produced the total. If the answer is that it is dead, it will say that.
Relic is a survival-signal summary, not a prediction of price or revival. It describes what is still on chain today and nothing about tomorrow.
One last look
no wallet, no key, no account