contract addresses.

Canonical deployment addresses will be published by network and protocol role so integrators can distinguish current deployments from historical or test instances.

what each record should contain

A production entry should include the network, contract or proxy address, implementation relationship where applicable, protocol role, version, deployment transaction and status.

verification rules

Applications should resolve addresses from the official reference and registry rather than copying values from screenshots, chat messages or unverified third-party lists.

lifecycle

Superseded and deprecated deployments will remain visible with clear status labels so historical transactions can still be interpreted correctly.