DenyList & Related Events

While primarily managed and emitted by the ART20 module, deny list-related events affect the SALE module’s functionality indirectly. For instance, if an address is placed on a deny list, it may not be able to receive NFTs purchased from the sale. Notable deny list events and their relevance to SALE:

• DenyListStatusChanged: Emitted when an address is added to or removed from a deny list. Impact on SALE: Buyers newly added to the deny list may fail to receive purchased NFTs, while those removed from it regain the ability to participate in future sales.

• DenyListAuthorityRevokedEvent: Emitted when the authority to modify a deny list is revoked from the collection owner. Impact on SALE: Ensures that the deny list remains static once authority is lost, allowing predictable and stable conditions for buyers and sellers.

Use Cases:

• Enable UIs to indicate whether a particular buyer is eligible to participate in sales.

• Keep marketplaces in sync with compliance or curation decisions by the collection owner.

• Ensure buyer expectations match actual capabilities, preventing failed transactions due to deny list conflicts.

These events, combined with the ART20 deny list mechanics, ensure that the SALE module operations are transparent, predictable, and adaptable. Buyers, sellers, indexers, and analytics tools rely on these emitted events to stay informed about sales, adjust their behavior accordingly, and maintain trust in the marketplace.