Compatibility is the single most misunderstood idea in the prod.keys ecosystem, largely because it is treated as a property of a file. It is not. Compatibility is a relationship between four things at once: the firmware, the key revision, the keyset, and the content or tool environment the keyset is used in.
The relationship chain
The chain runs in one direction. Firmware establishes which generations and revisions of key material exist. A key revision identifies which of those a given keyset contains. The keyset is what a tool loads. The content or tool environment expects a particular revision, and compatibility is simply whether the four agree.
Break any link and the operation fails — but it fails in a different way each time, which is why the troubleshooting hub maps errors individually rather than offering a single “fix everything” answer.
Documented facts versus community assumptions
A great deal of what circulates about prod.keys compatibility is repetition rather than documentation. Phrases like “works on the latest firmware” or “complete keyset” are claims about a moving target, and they rarely state who verified them or when. This site separates the two: a documented statement names a source and a review date; an assumption is labelled as an assumption.
The table below sets out that contrast directly, entry by entry. No firmware number or revision is stated, because none has been recorded on this site.
Why firmware sits at the top
Because revisions follow firmware, not the other way round. A system update can introduce a new generation, so a keyset that was current before an update may not be after it. The firmware guide explains that relationship, and the versions hub records what has actually been confirmed.
Reading a compatibility statement responsibly
- A statement is only useful if it names the revision and the environment it applies to.
- “Compatible” without a version is not a compatibility statement — it is marketing.
- Community reports can be useful evidence, but they are evidence of someone’s experience, not of your system.
- When a mismatch occurs, work from the error backwards rather than replacing files at random.