Bridge Protocol's compliance registry is responsible of the storage of all identity information linked to an address or the storage of the history of transfers linked to an address.
Bridge Protocol is a tool to enforce and manage on-chain compliance rules that come from off-chain regulation. Therefore, someone needs to be the link between both worlds, updating on-chain what has been validated off-chain. We call that entity a KYC/AML provider.
Bridge Protocol supports compliance delegation, i.e. enabling multiple KYC/AML providers to work on the same token. For example, if your token is distributed to both US investors and European investors, you can have a US provider managing the compliance of US investors, and a European provider managing the compliance of European investors.
- A KYC/AML provider can be yourself and/or third-party entities.
- A token can have as many providers as you want.
- You can add and remove providers to a token at any time.
The Compliance Registry is responsible of the storage of all identity information linked to an address or the storage of the history of transfers linked to an address. The compliance registry is managed by trusted intermediaries, the KYC/AML providers. Each trusted intermediary has its own space within the registry to update its own address related information. Based on the token trusted intermediaries, the Compliance Registry will return the compliance information that have been updated by one of the token trusted intermediary.
The Compliance Registry is designed to store only pseudo-anonymized data (no Customer Identification Data).
To be able to maintain a single reference currency for transfers history, the Compliance Registry will use the Price Oracle.
Attributes is an array of uint256.
User validity end date (UNIX timestamp)
User KYC level
User single transfer limit in referrence currency
User monthly transfer limit in referrence currency
User yearly transfer limit in referrence currency
User freeze direction
Frozen as token receiver
Frozen as token sender
Frozen as token sender
Frozen as token sender and receiver
User freeze start date (UNIX timestamp)
User freeze end date (UNIX timestamp)
Specifies if start date and end date period has to be inverted
Freeze period not inverted
Freeze period inverted
Global whitelist flag
User not whitelisted