Bluescreen (ticker: BLUESCREEN) is a meme token deployed on Base (EIP-155:8453), with its native contract at 0xffe6510baf2a479ab567d76af8ec79d9f7d0366a. The official website, bluescreenonbase.com, presents a Windows 98–styled interface featuring an integrated swap powered by Uniswap v3 and a cross-chain bridge using the LI.FI widget. According to source_2, the project explicitly positions itself as a non-financial meme referencing the Windows Blue Screen of Death, with no promised utility beyond cultural resonance in the Base ecosystem. Its token supply is fixed at 1 billion, fully circulating, with no mint or burn functions indicated in the supplied evidence. Contract explorers include BaseScan and Intel ARKM. Social presence is documented on Twitter (@bluescreenmeme) and Telegram (bluescreenerportal). Key evaluation questions remain: Is the contract verified and audited? Who holds upgrade, pause, or fee-collecting privileges—and are those controls transparently disclosed? Does the bridge or swap integration introduce unassessed dependency risks?
The project positions itself as a meme token on Base, with a functional website offering swaps via Uniswap v3 and bridging via LI.FI (source_2). Its contract address is consistently reported across sources (bluescreenonbase.com, CoinGecko, CoinPaprika), and supply metrics are uniform: 1B total/circulating supply on Base (CoinGecko). However, no evidence confirms actual liquidity depth, pool composition, or real-time market data — only static claims about routing. The API sources explicitly state they contain unverified claims and lack independent verification (CoinGecko, CoinPaprika). No onchain liquidity data (e.g., pool addresses, reserves, LP concentration) is supplied, nor is there evidence of sustained trading volume, spread tightness, or slippage behavior. The notice in CoinGecko flags liquidity-related risks generically but offers no project-specific mitigation or transparency. Social links exist (Twitter, Telegram, X), yet no adoption metrics — followers, engagement, or community activity — are provided. Documentation and repository URLs are absent (project object), limiting assessment of product sustainability or technical controls. The primary thesis — that BLUESCREEN captures cultural resonance and delivers executable liquidity — remains unsupported by verifiable, current, or independent evidence.
Liquidity is asserted but not evidenced: no pool identifiers, reserve balances, or exchange venue confirmation beyond generic Uniswap v3 routing claims. Concentration risk is unassessable without LP data. Spreads and exit constraints cannot be evaluated from metadata-only or API-projection sources.
Does the live swap widget at bluescreenonbase.com route to an active, sufficiently funded pool — and is that pool independently verifiable?
Overall score: 6/10 Confidence: Low