Many contract's ABIs technically can be described as a union of multiple smart contract interfaces. As an example an OpenZeppelin ERC721 might support:
IERC165 (Introspection)
RoleAccessControl
IERC721
IERC721Metadata
It could be useful to have an additional abiInterfaces optional key-value field that splits the contracts abi into individual interfaces. Why is this useful? One might want to group all RoleAccessControl smart contracts for example to create a general management interface.
Many contract's ABIs technically can be described as a union of multiple smart contract interfaces. As an example an OpenZeppelin ERC721 might support:
abiInterfacesoptional key-value field that splits the contracts abi into individual interfaces. Why is this useful? One might want to group all RoleAccessControl smart contracts for example to create a general management interface.