Compliance Interface
The Compliance contract interface defines the set of functions and events used to enforce regulatory compliance within the T-REX protocol. Below is a detailed breakdown of each function and event, explaining its purpose, source, and functionality.
TokenBound
Event
Description: Emitted when a token has been bound to the compliance contract.
TokenUnbound
Event
Description: Emitted when a token has been unbound from the compliance contract.
bindToken
Source: ICompliance
Description: Binds a token to the compliance contract. This function emits a TokenBound
event.
unbindToken
Source: ICompliance
Description: Unbinds a token from the compliance contract. This function emits a TokenUnbound
event.
transferred
Source: ICompliance
Description: Called whenever tokens are transferred from one wallet to another. This function can update state variables in the compliance contract, which are used by canTransfer
to decide if a transfer is compliant.
created
Source: ICompliance
Description: Called whenever tokens are created on a wallet. This function can update state variables in the compliance contract, which are used by canTransfer
to decide if a transfer is compliant.
destroyed
Source: ICompliance
Description: Called whenever tokens are destroyed. This function can update state variables in the compliance contract, which are used by canTransfer
to decide if a transfer is compliant.
isTokenAgent
Source: ICompliance
Description: Returns true if the address given corresponds to a token agent.
isTokenBound
Source: ICompliance
Description: Returns true if the address given corresponds to a token that is bound with the compliance contract.
canTransfer
Source: ICompliance
Description: Checks if a transfer is compliant. This is a read-only function that cannot be used to increment counters, emit events, or modify state variables.
Last updated