ERC-7303 Conformance Fixture

A redeployable fixture and test suite answering one question: does a contract actually implement ERC-7303?

The durable part of this fixture is the sources in contracts/ and the expected values asserted in test/conformance.js — everything is recomputable and redeployable on any chain. Concrete testnet addresses are listed at the end for convenience only; they are not the fixture.

Layout

Running

npm install
npx hardhat test

Expected values

Interface identifier

The IERC7303 identifier is the XOR of its three function selectors (events do not contribute):

A compliant contract answers supportsInterface(0x01ffc9a7) = true, supportsInterface(0x4ee69337) = true, and supportsInterface(0xffffffff) = false.

Canonical role structure of FixtureTarget

Deployed as FixtureTarget(ct721, ct1155):

Deployment emits exactly one ERC721ControlTokenAdded and two ERC1155ControlTokenAdded events matching the table.

Roles compose in two directions:

• OR within a role — holding either entry of MINTER_ROLE grants the role.
• AND across roles — reissue(tokenId, to) stacks the modifiers of MINTER_ROLE and BURNER_ROLE and succeeds only for a caller holding both, whether the two roles are satisfied through the same standard (ERC-1155 + ERC-1155) or across standards (ERC-721 + ERC-1155).

Role lifecycle

For each control-token path: hasRole is false before minting, true after the issuer mints, and false again after the issuer burns — with no cooperation from the holder (the kill switch). The gated functions (safeMint, burn) succeed exactly when the caller holds the role and otherwise revert with "ERC7303: not has a required token".

Negative case

LegacyTarget gates identically to FixtureTarget (same control tokens, same revert string) but pre-dates IERC7303: it exposes no hasRole/getter functions and supportsInterface(0x4ee69337) answers false. Discovery tooling encountering such a contract must classify it as not implementing this ERC, behavioral equivalence notwithstanding. This is the boundary the fixture pins down: conformance is the declared, machine-readable interface — not the gating behavior.

Convenience deployments (informational, not normative)

An instance of each case is deployed on Sepolia. Testnets are ephemeral; if these disappear, redeploy the sources above — the expected values are unchanged on any chain.