I am not blaming uniswap. But I think there are things uniswap could have done.

The only reason why I use uniswap wallet is because I am using uniswap.

Many phisher use google sponsored link to promote drainer.

Most of the time I figured that out. Sometimes I miss.

Now. The wallet ask for unlimited approval.

However, it's from unknown source.

It seems that uniswap, by default, HIDE the notification of from unknown source.

Also the smart contract interacted is NOT from uniswap.

Otherwise no warning.

I should have seen the domain names.

Since then I use ublock lite to remove google sponsor link. Use book mark. Also most phishing sites don't bother using similar domains. So checking domain in gemini is a good way to see if a site is phising.

Is there a place we can go look and see how much buyback and burn uniswap is do for UNI? Is this still a thing or was it only temporary?

I’ve been building an open-source monitor for Capped Continuous Auctions (CCAs).

What’s new:

6 chains monitored
Ethereum, Base, Arbitrum, Unichain, Optimism, and Polygon. The monitor auto-detects new auctions across all factory contracts.

Multi-channel alerts
Telegram, Discord, Slack webhooks, and email via SendGrid. Whale bids, auction endings, daily digests.

Auction comparison
Compare up to 4 auctions side-by-side: clearing ratios, bidder overlap, concentration, and more.

Post-graduation tracking
Graduated tokens now get sparkline charts with -10%, -20%, and -30% alert bands.

REST API
Cloudflare Workers API with a free tier for basic data and a pro tier for concentration/overlap analytics.

4 of 5 real CCAs graduated.

AKITA on Base was the first to fail.

And honestly, that's a good thing.

If every auction graduated, the mechanism wouldn't be doing much filtering. A failed auction is evidence that the graduation threshold actually matters.

The more interesting signal is bidder overlap.

Some wallets are showing up in almost every CCA.

As more auctions launch, that cross-auction behavior could become one of the most valuable datasets from the monitor.

And then things broke.

polygon-rpc.com started returning 401s.

They silently introduced API key requirements.

Lesson: never depend on a single RPC provider.

The monitor now has 2–3 fallback RPCs per chain and automatically fails over between Blockscout, dRPC, PublicNode, and others.

Windows + PM2 started spawning console windows.

The watchdog uses execSync to check PM2 status every 5 minutes. On Windows, that meant a console window popping up every time.

One little windowsHide: true fixed it.

Small problem. Surprisingly annoying.

Viem's default RPCs went stale.

If you don't explicitly configure an RPC, viem uses the chain's built-in default. Those endpoints can eventually stop working without much warning.

The client factory now falls back to the monitor's public RPC list instead.

Current state

The whole thing is running on a Windows box:

• 4 PM2 processes
• ~250 MB RAM
• ~$0/month infrastructure
• 30-second polling
• Automatic auction detection
• Automatic analysis
• Automatic dashboard updates

Waiting for the next wave of CCA launches.

Dashboard: cca-monitor dashboard
Repo: GitHub repository

Dashboard and API are free. PRs welcome.