Transaction Requirements

Each Safe Token has its own, customizable credential requirements.

Below is a 4 step process every Safe Token transfer goes through. All actions are facilitated directly from the Safe Token contract.

Transfer is initialized by the user
Safe Token contract scans the sender's wallet for a valid KYC credential
Safe Token contract scans the receiver's wallet for a valid KYC credential
If both the sender and receiver pass the credential check, the Safe Tokens are transferred

Credential Requirements

Each Safe Token has its own Credential requirements, which means different Safe Tokens can require different Credentials. If both wallets in a Safe Token transaction do not have the required Credentials, the transaction fails. As a base requirement, all Safe Tokens require KYC Credentials and Non-U.S. Credentials with some Safe Tokens requiring additional credentials like Accredited Investor Status.

For instance, TOKE.safe can be traded by users that have:

KYC credential
U.S. Jurisdiction credential

While, FEI.safe can be traded by users that have:

KYC credential
U.S. Jurisdiction credential
Accredited Investor credential

Customized Pools

Each permissioned pool on the Blue Network can have its own specific credential requirements, regardless of the protocol it operates on. This means that the same Safe Token can be used to perform different credential checks when interacting with different pools. This provides a flexible and customizable approach to credential management, allowing for more granular control over the verification requirements for each pool.

For instance, FEI.safe may have the following requirements for a Curve Pool:

KYC Credential

Another pool with FEI.safe on Uniswap may require:

KYC Credential
Non-U.S. Jurisdiction Credential