惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

A
About on SuperTechFans
Y
Y Combinator Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Microsoft Security Blog
Microsoft Security Blog
aimingoo的专栏
aimingoo的专栏
I
InfoQ
C
Check Point Blog
IT之家
IT之家
MyScale Blog
MyScale Blog
Apple Machine Learning Research
Apple Machine Learning Research
Vercel News
Vercel News
Last Week in AI
Last Week in AI
GbyAI
GbyAI
P
Proofpoint News Feed
量子位
Stack Overflow Blog
Stack Overflow Blog
Microsoft Azure Blog
Microsoft Azure Blog
月光博客
月光博客
阮一峰的网络日志
阮一峰的网络日志
人人都是产品经理
人人都是产品经理
B
Blog
T
The Blog of Author Tim Ferriss
H
Help Net Security
云风的 BLOG
云风的 BLOG

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
When three sharp wallets agree: what consensus signals on...
Слава Жулано · 2026-05-25 · via DEV Community

A few weeks into watching specific wallets on Polymarket, I noticed a pattern. Most of the time, a sharp wallet making a trade is one signal — interesting if you already trust that wallet's read, otherwise just data. Occasionally something else happens: three or four of the wallets I'd identified as sharp would all take the same side of the same market within a day. Different wallets. Different sizes. Same direction.

That coincidence is harder to explain away than any single trade. So I built it into PolySignal as its own alert type. This piece is about what consensus signals are — and what they aren't.

The premise

Polymarket is fully on-chain. Every position is public. The wallets that consistently top the leaderboard are observable: which markets they trade, when, in what size, with what eventual outcome. None of this is secret; it's just labour-intensive to track manually.

When you watch a handful of sharp wallets, each individual trade carries some information about that wallet's view. One trader's view is one data point. The question worth asking is: what changes when independent traders converge?

Three wallets is the threshold I picked

The PolySignal consensus alert fires when at least three of a user's followed wallets have taken the same side, in the same outcome, of the same market, within a 24-hour window.

Why three?

  • Two is the modal coincidence. Sharp wallets watch overlapping markets; on any active day, half the leaderboard has positions in the two or three most-trafficked questions. Two wallets agreeing is barely above baseline.
  • Three is structurally hard to coordinate accidentally. It requires three independent reads to land on the same side, in the same window, on the same market. Sharp Polymarket wallets are also specialised — some focus on politics, others on crypto, others on sports — so three converging across specialties is rarer still.
  • Four was tempting, but it filtered too aggressively. I'd rather over-alert lightly than miss the event entirely.

That threshold is configurable. Three is the launch default and it has produced sensible patterns in the few weeks of observation I have.

What it isn't

A consensus signal is not a prediction. It's not a recommendation. It's a description: three wallets with strong closed-market track records have just taken the same side of one market. Past coincidence does not guarantee future correlation. The signal is information about who's positioned where; what you do with it is your own decision.

This matters because the temptation when you see "three of your wallets agree" is to read it as evidence the side will resolve correctly. Sometimes it does. Sometimes it doesn't. The pattern's value is statistical, not deterministic.

Two failure modes I've watched in real time:

Consensus on the obvious side. When a market gets a news catalyst that pushes prices to 90¢, a lot of wallets will pile in at 91¢ expecting the gap to close. Three "sharp" wallets converging on the obvious side after the news isn't a signal — it's the same news everyone else read, expressed by people who happen to be on your watchlist.

Late-arriving consensus. Three wallets converging on a market that's already moved 30 points is information about where the consensus was, not where it's going next. The signal value of consensus drops sharply when it arrives after the move.

The mitigations are obvious in hindsight: the alert is more interesting when the market is quiet, and less interesting when it's noisy. I've thought about adding a "market is currently moving > X over the window" suppressor; for now I'd rather show all consensus events and let readers exercise their own judgement.

What it actually catches

The patterns the consensus alert catches well:

  1. Early entries into not-yet-popular markets. A new market launches; three of your watched wallets each independently decide it's worth a position. The market is still 50/50 in price terms. This is the signal class with the most consistent information value.
  2. Coordinated direction shifts. A market has been trading in a band; one day, three of your wallets all open positions on the same side at the same time. Something changed that they all noticed.
  3. Sharp-wallet positions on long-resolution questions. Markets that resolve in months sometimes show consensus from sharp wallets weeks before the rest of the market catches on.

The patterns it doesn't catch:

  • Wallets exiting a market. Exits are as informative as entries, often more so, but consensus on the entry side doesn't surface "everyone unwinding." I'll probably add a separate exit-consensus alert eventually.
  • Single-wallet conviction trades. A single sharp wallet putting on its largest position in months — the signal of behavioural conviction — is its own thing; PolySignal handles it as a per-trade tag, not as consensus.

The mechanics

For the technically curious: detection is one DB query per delivered trade alert. For each new trade I check the user's followed wallets and look for other recent trades that share (market, side, outcome) within the window. If the distinct-wallet count crosses the threshold, the consensus alert fires; a SentConsensus row is committed before the message is sent so a failed delivery never produces a duplicate.

It's a small piece of code — most of the cleverness is in the choice of threshold and window, not in the implementation.

The frame I actually use

When a consensus alert lands in my Telegram, I treat it as a flag, not an instruction. The question I ask is what do these three wallets see that I don't yet? Maybe they read a story I missed. Maybe they have domain expertise the market hasn't priced in. Maybe they're all reading the same incomplete picture — in which case the question becomes whether I have a stronger read of my own.

The signal is the start of a question. The answer is your own.

Where this runs

If you've read this far and want to see consensus signals in your own Telegram: I built PolySignal precisely so I'd stop manually correlating trades in a spreadsheet. The consensus alert is a Pro-tier feature; the rest of the bot is free.

Honest disclosure: PolySignal reports on public on-chain activity. It is an information service, not financial advice. Polymarket isn't available in every region — check yours.