Skins. Codes. Clear answers.

Guides/Market site guides

Market site guides

CSFloat database: item identity, history and coverage

Read FloatDB records with their observed history and attribute identity, without treating missing records or duplicates as a complete ownership certificate.

3 min read
Published Revised

THE QUICK ANSWER

A database observation is evidence about a catalogued item, not proof of every item that exists or a complete ownership history.

01

A Steam asset ID and an item fingerprint differ

CSFloat’s tracking explanation says an asset ID can change when an item is traded. Its documented tracking method instead combines float, paint seed, definition index and paint index. A changed asset ID therefore does not by itself establish that a different physical skin replaced the one in a history.

Save the complete attribute set with the record URL. A short rounded float alone throws away identifying information and should not be treated as a unique ownership certificate.

STRIKEPOT / EXPLAINED

Explanation: the documented item fingerprint

  1. Float and paint seed

    Detailed attributes used together.

  2. Definition and paint index

    Identify the item and finish combination.

  3. Observed location/time

    A database observation, not a full trade receipt.

Explanation diagram, not a website screenshot. Methodology diagram; it does not expose a player’s inventory.

Original explanation · not an account screenshot

02

Read history as observations of the item

The Project Vault release describes item history and broader inventory discovery, while also explaining blind spots in earlier collection methods. A gap between observations does not tell you what happened during the gap.

Keep observed dates distinct from inferred trade dates. For example, if an item was last seen on Monday and appears in another observed inventory on Friday, the record alone does not prove a trade happened at a particular hour on Wednesday.

Illustrative example; no live prices
Observed attribute matchEvidence connecting database records
Observation dateWhen that record was seen or updated
Missing intervalNo complete transaction story follows automatically
Current ownership claimCheck a current item record and actual transaction evidence

03

Use the later duplicate-data release

The July 2020 tracking article describes an early duplicate limitation. Later Project Vault work added duplicate data, and the December 2021 announcement made that and item history free. Do not cite the early article as proof the database can never show duplicates.

A duplicate label is still a data interpretation to examine, not a reason to declare a transaction fraudulent without checking the exact record and supporting documentation.

STRIKEPOT / EXPLAINED

Explanation: use the sources in order

  1. July 2020 methodology

    Explains identity and initial duplicate limits.

  2. Later July 2020 release

    Adds history and duplicate work.

  3. December 2021 update

    Makes database history and duplicate features free.

Explanation diagram, not a website screenshot. A source-history timeline prevents treating superseded limitations as current facts.

Original explanation · not an account screenshot

04

Know why some objects do not fit the method

The tracking method depends on inspect data and sufficiently distinguishing item attributes. The original explanation uses unapplied stickers and sticker capsules to show why not every inventory object can be tracked like a weapon skin.

An absent result can reflect coverage or observation limits. It does not establish that an item does not exist, is lost, is privately owned by a particular person, or is available for sale.

05

Keep a bounded provenance note

Record the exact record URL, full identifying values, observation dates and any history or duplicate information actually visible. Label conclusions that go beyond those observations as your inference.

Use the actual item’s inspect information and listing or trade record for a transaction. A historical owner nickname, rank or database entry cannot replace matching the current offer.

BEFORE YOU CONTINUE

Quick checklist

  • Save full attributes, not only a rounded float.
  • Separate observation dates from inferred trade times.
  • Use later duplicate/history updates alongside old methodology.
  • Treat missing results as a coverage question.

Official sources

Official public documentation reviewed on 26 October 2026 (America/Toronto).

Methodology and feature releases are dated 2020–2021 and identified as such. The older paid Premium fee table is excluded, and the early duplicate limitation is read alongside subsequent releases. No inventory crawl, private-owner lookup, signed-in database search or current coverage audit was performed.

KEEP READING

A useful next read.

All guides

Skins & trading · 2 min read

CS2 wear and pattern explained

Wear affects a skin’s condition; pattern placement affects its appearance. Inspect the actual item and compare matching attributes before judging a sale quote.

Read guide

Skins & trading · 2 min read

Inspect before buying

Open the actual listing’s inspect view, compare the complete variant and check wear, pattern and stickers before reviewing the final offer.

Read guide

Steam & trades · 2 min read

Review a trade offer

Check the recipient, every item and the final Steam confirmation before accepting. If an offer changes or is replaced, review it from the start.

Read guide