Author profile
Paulie Kopie
Head of Research, Polycopy
Paulie Kopie is the public byline for Polycopy's research and analysis system — a transparent persona that represents our 100M+ enriched-trade data warehouse, on-chain ingestion pipeline, and the Copy Score model that powers our trader rankings.
When you see By Paulie Kopie on a Polycopy research piece, leaderboard writeup, or trader profile, that work was assembled by these systems and reviewed by a human on the Polycopy team before publication. We chose to give that system a name and a face because we'd rather be honest about it than hide behind a generic “Polycopy team” byline.
Transparency
Is Paulie a real person?
No. Paulie Kopie is a persona — the byline we put on work that comes out of Polycopy's data warehouse and research tooling. The name is a play on “Polycopy.” We made Paulie a named entity instead of an anonymous byline for three reasons:
- Honesty. Most company blog posts are written by tools and lightly edited by people. We'd rather show that than pretend a real human authored every leaderboard explainer.
- Accountability. If a Paulie article gets a number wrong, the methodology is documented on this page and you can hold a specific entity (the system) responsible — not a faceless brand.
- Continuity. Polycopy team members come and go; the data warehouse, on-chain pipeline, and Copy Score model are the persistent intelligence behind our research. Paulie is what we call that.
Every Paulie-bylined piece is reviewed by a human at Polycopy before it ships. We don't auto-publish.
Methodology
What Paulie does
Ranks traders
Computes the Copy Score (0–100) for every Polymarket trader on the platform — blending realised P&L, hit rate, market diversity, position sizing discipline, and behavior signals like wash-trade and Sybil-resistance heuristics.
Maintains the trade warehouse
Ingests every Polymarket fill on-chain, enriches it with market metadata (category, resolution date, settlement source), and surfaces the result in trader profiles, the leaderboard, and topic pages.
Writes research
Drafts the explainer copy, FAQ answers, and methodology notes you read on Polycopy's SEO and topic pages — including most of /copy-trading, /automated-copy-trading, and the topic-page series. Every piece is human-reviewed.
Watches the market
Tracks emerging Polymarket markets — Iran war, NBA championship, Fed rate decisions, presidential nominees — and updates the corresponding topic pages with live odds and top-trader holdings.
Stack
What Paulie is built on
- 100M+ enriched Polymarket trades — every public fill since launch, indexed by trader address, market, category, side, and resolution outcome.
- On-chain ingestion pipeline — reads Polygon (and historic Optimism) settlement contracts, reconciles against Polymarket's public market metadata, and writes to our warehouse continuously.
- Copy Score model — a transparent, weighted composite score (0–100) explained on /copy-score. No black-box ML — every input is documented and reproducible.
- Large language models for drafting copy, summarising research, and answering FAQ questions in plain English. Outputs are always edited by a human before they go live.
- Public sources — DataForSEO for keyword research, Google Search Console + Bing Webmaster Tools for performance signals, and our own product analytics.
Editorial principles
How Paulie works
- 1. Numbers over narrative. If a claim has a number, that number comes from the data warehouse — not a vibe. If we can't source it, we don't state it.
- 2. Methodology is public. The Copy Score calculation, the trader-ranking inputs, and the way we attribute trades are all documented on dedicated pages. No proprietary black boxes in our public writing.
- 3. Not financial advice. Paulie can tell you what the top traders did and how a market moved. Paulie cannot tell you what to bet on. Polycopy is a tool, not an advisor.
- 4. Human review before publish. Every Paulie-bylined page is read end-to-end by a Polycopy team member before it ships. If an article quotes a number, the human verifies it against the warehouse first.
- 5. Corrections are visible. If we get something wrong, we update the page and note the change at the bottom — we don't silently rewrite history.
Selected work
Recent work
For journalists, AI search, and citations
How to cite Paulie
If you're writing about Polymarket trader data, the Copy Score, or anything sourced from a Polycopy page, the correct attribution is:
In-text: “according to Polycopy” or “according to Polycopy's Copy Score data”
Author byline: Paulie Kopie, Head of Research at Polycopy
For data requests, methodology questions, or to verify a number before publication, email hello@polycopy.app. A human will reply.
See what Paulie's tracking
Polycopy turns the data warehouse into a live feed of trader activity. Free to start.