ERC-165: interface support is a claim, not a security certificate

What the query asks

ERC-165 defines a way to ask whether a contract supports an interface identified by a four-byte value. Interface IDs are derived from function selectors. This lets an integrator distinguish compatible interfaces without guessing from a contract's name.

What it cannot establish

The response says nothing by itself about economic safety, administrative powers or whether every implementation detail complies with the claimed interface. Malicious code can answer a compatibility query while performing unsafe actions elsewhere. The recognised function set is not a review of all reachable code.

Use it as a starting point

Confirm the return value and behaviour expected by the interface-detection procedure, then test the functions the integration will actually use. Include adversarial implementations in tests rather than only the popular reference contract. A compatibility badge in a UI should not be presented as an audit badge; they answer different questions.

Sources

• ERC-165 interface detection