ABIs & interfaces.

Versioned interface definitions will give integrators a stable source for functions, events, errors and compatibility expectations.

published material

Each qualified contract family should expose its ABI, interface identifier where applicable, event signatures, custom errors and notes for proxy or implementation boundaries.

compatibility

Interface references will indicate whether a change is additive, backward compatible or breaking. Applications should bind to an explicitly supported version rather than assuming all deployments expose identical behavior.

events & errors

Events and errors are part of the public integration surface. Indexers and clients should use canonical signatures and version context when decoding historical data.