CopyGrade
Changelog

Scoring rules change in public.

The CopyGrade Score model is tuned continuously against real wallet outcomes. Every material change to how a score is computed — the scoring math, the farming detectors, the realistic-return and simulator arithmetic, the validation reads, and the trade data that feeds them — is recorded here, dated, so the way a score is computed is never a moving target you can't see. Scoring changes only: pricing, notification and product changes are not logged here.

October 11, 2026

Cross-wallet farming findings no longer flap day to day

The daily cross-wallet pass had been re-checking a different sliver of wallets each day and discarding every finding it did not re-check, so a decoy or coordination flag on a wallet could lift one morning and return the next. A finding now stands until the pass re-evaluates that wallet with all of the cluster's members loaded.

  • The daily pool is the most recently trading wallets, not the most recently synced ones, so wallets that trade together are checked together.
  • Every standing cluster's members are re-checked each run, ahead of the pool; a finding is cleared only when that re-check no longer supports it.
  • A wallet the pass did not reach keeps its findings instead of losing them for want of a scan.
  • No change to what counts as a decoy cluster or a coordination ring, or to how a finding weighs into the farming flag.
September 3, 2026

A public track-record page, published either way

The forward-return table that has lived on the methodology page since June now has its own page, /track-record, led by the honest headline (three 30-day reads, no rank correlation yet) and joined by a second ledger no one else publishes: whether the wallets we graded into each band 30 and 90 days ago are still trading and still in that band, and whether our farming-risk flags held.

  • Liveness by band: of the wallets graded into each score band on a day 30 and 90 days ago, the share with a fill in the last 30 days, and the share still in that band today — over the wallets we still track, with a 30-wallet publication floor per band.
  • Farming-flag persistence both ways: the share of flagged wallets still flagged, and the share of clean wallets since flagged.
  • Both ledgers are computed live and refreshed hourly; aggregates only, no wallet is named, and a small cell is withheld rather than shown.
  • No scoring change. The page reads the grades already published; the model's weights stay frozen until the return table shows a persistent signal.
September 2, 2026

The activity gate now floors the length of the record

A wallet whose recorded trades span fewer than 30 days from first to last fill is capped at the caution band (64) — the same ceiling the gate already applies under 20 recent trades. A short record cannot read as a copy candidate however clean its numbers.

  • Why: among top-band wallets, records shorter than 30 days produced a positive 30-day forward return in about 3% of measured windows, against 19–31% for longer records. The floor sits where that step is; 14 days would not have caught it.
  • Scope, measured on 2026-09-01 as the change shipped: 18 of the 189 wallets above the cap fall under the new floor, 8 of them on the copyable shortlist, and each moves to the caution band at its next re-score. Every other wallet's score is unchanged, and the five sub-scores are untouched.
  • The confidence chip and the bottom-line recommendation both name the short record as the reason, so the cap is legible on the page rather than mysterious.
  • Volume is still not a gate. A minimum-stake floor was measured at the same time and deliberately left unbuilt — small books mostly go quiet rather than lose — and the methodology page records that as an open limitation.
July 25, 2026

Fixed: our trade tape was storing every fill twice

An ingestion defect had been writing duplicate copies of the same Polymarket fill, leaving roughly a quarter of stored trades as phantom rows. Every wallet has been re-scored on the corrected tape, and scores moved — mostly downward in farming risk.

  • What was wrong: the sync's de-duplication key was built from a timestamp that changed shape once it had been written to and read back from the database, so an already-stored fill did not match itself on the next run and was inserted again. About 24% of rows in the trades table were duplicates.
  • Why it moved scores: farming detectors read repetition in the trade history — self-trade wash, iceberg accumulation, copy-bait cadence. Duplicated fills look like repeated activity, so they pushed wallets toward a flag that their real history does not support.
  • Measured effect, holding the model constant: across the same 2,016 wallets, the farming-flagged rate fell from 61.7% to 47.8% and the severe rate from 52.6% to 37.4%. 281 wallets moved from flagged to clean; 2 moved the other way. Median CopyGrade Score rose about 3 points.
  • If you looked at a wallet before 2026-07-24 and it carried a farming flag, re-check it — there is a real chance the flag was ours, not the wallet's.
  • No weight, threshold or detector changed. This was a data-quality fix; the model is the same one described on /methodology.
July 24, 2026

The Copy Score is now the CopyGrade Score

A rename, not a model change: the 0–100 metric formerly called the Copy Score is now the CopyGrade Score. Same inputs, same weights, same numbers — only the name is new.

  • Why: “Copy Score” turned out to be a crowded, generic name in the copy-trading space; naming the metric after CopyGrade itself makes it unambiguous whose methodology produced the number.
  • Nothing about the model changed with this entry — no factor, weight, detector, or threshold moved. Scores computed before and after the rename are directly comparable.
  • Older entries on this page now use the new name for readability; where they say CopyGrade Score, the metric was called Copy Score at the time.

How the score is built is documented in full on the methodology page, and how it has performed on the track record page.