POLARBEAR has 0 dated snapshots and 0 daily candles in this archive. Explore each available source and pool below.
The recorded sequence
What happened to POLARBEAR?
01First tracked
Entered the DexBrief catalog.
02Catalog retired
no tracked market after 3 checks
First tracked is not launch; retirement is a catalog decision, not a verified final trade or cause of death.
The evidence in this case
POLARBEAR: what happened and what the record supports
What triggered the POLARBEAR retirement
For POLARBEAR, the stored decision is "no tracked market after 3 checks". The record counts 3 checks, but does not retain 3 independent provider responses. It cannot establish the date of POLARBEAR's last trade.
The saved market footprint of POLARBEAR
Glamsterdam Polar Bear's saved token page retained price $0.0001174, 24-hour volume $33.69K, pool liquidity $21.45K, fully diluted value $117.42K, 24-hour trades 244. Those fields lack a complete set of trustworthy observation dates, so they describe the archived POLARBEAR snapshot and are excluded from dated return calculations. The saved route is 0x4ccfd41252b0e9517dda10e45da8248a2a8b5316. The $117.42K figure is fully diluted value; a circulating market cap was not retained for POLARBEAR.
POLARBEAR supply and contract controls
Glamsterdam Polar Bear's September 01, 2026 contract snapshot records contract ownership: renounced; token supply: 1,000,000,000.
The missing interval in POLARBEAR's history
The POLARBEAR archive currently contains 0 dated snapshot(s) and 0 daily candle(s). It lacks a comparable price or activity series spanning at least six hours. First tracking is July 29, 2026; catalog retirement is August 06, 2026. An observed decline between those markers cannot be reconstructed from the retained POLARBEAR values alone.
Each row is one source and one scope. Pool liquidity and activity are not token-wide totals. Missing fields are not zero. Full history is available in the downloads.
DexBrief’s compiled observations and analysis may be cited with attribution under CC BY 4.0; underlying provider data remains subject to its source terms.