The Identity Registry Storage is serving as the backbone for storing and managing identity data. It works in conjunction with the Identity Registry to ensure that identity information is securely stored, easily accessible, and efficiently managed.

Key Features of the Identity Registry Storage

1. Centralized Storage:

   • The Identity Registry Storage acts as a centralized repository for identity data. It stores mappings of wallet addresses to ONCHAINID addresses, ensuring that identity information is consistently and securely maintained.

2. Interoperability:

   • The same Identity Registry Storage can be shared by multiple Identity Registry contracts. This feature enhances interoperability and ensures that identity data can be accessed and managed across different parts of the T-REX ecosystem.

3. Efficient Data Retrieval:

   • The Identity Registry Storage is designed for efficient data retrieval, enabling quick access to identity information. This is particularly important for verifying identities during token transfers and other regulated actions.

How the Identity Registry Storage Works

1. Data Storage:

   • The Identity Registry Storage stores the ONCHAINID addresses corresponding to participant wallet addresses. This mapping ensures that each wallet address can be linked to an ONCHAINID, which contains the necessary claims and credentials for identity verification.

2. Integration with Identity Registry:

   • When the isVerified function is called on the Identity Registry, the Identity Registry fetches the ONCHAINID address corresponding to the recipient's wallet from the Identity Registry Storage. This process is critical for verifying the identity of participants during transactions.

Benefits of Identity Registry Storage

1. Security and Reliability:

   • By centralizing the storage of identity data, the Identity Registry Storage ensures that identity information is secure and reliable. The use of blockchain technology provides immutability and transparency, making it a trustworthy source of identity data.

2. Scalability:

   • The ability to share the same Identity Registry Storage across multiple Identity Registry contracts enhances the scalability of the T-REX protocol. It allows for efficient management of identity data as the ecosystem grows.

3. Flexibility:

   • The design of the Identity Registry Storage allows for flexible integration with other components of the T-REX protocol. It can easily adapt to different use cases and requirements, providing a robust solution for identity management.

The Identity Registry Storage interface defines the set of functions and events used to manage and store identity data within the T-REX protocol. Below is a detailed breakdown of each function and event, explaining its purpose, source, and functionality.

IdentityStored

Event

Description: Emitted when an identity is registered into the storage contract.

event IdentityStored(address indexed investorAddress, IIdentity indexed identity);

IdentityUnstored

Event

Description: Emitted when an identity is removed from the storage contract.

event IdentityUnstored(address indexed investorAddress, IIdentity indexed identity);

IdentityModified

Event

Description: Emitted when an identity has been updated in the storage contract.

event IdentityModified(IIdentity indexed oldIdentity, IIdentity indexed newIdentity);

CountryModified

Event

Description: Emitted when an identity's country has been updated in the storage contract.

event CountryModified(address indexed investorAddress, uint16 indexed country);

IdentityRegistryBound

Event

Description: Emitted when an Identity Registry is bound to the storage contract.

event IdentityRegistryBound(address indexed identityRegistry);

IdentityRegistryUnbound

Event

Description: Emitted when an Identity Registry is unbound from the storage contract.

event IdentityRegistryUnbound(address indexed identityRegistry);

addIdentityToStorage

Source: IIdentityRegistryStorage

Description: Adds an identity contract corresponding to a user address in the storage. Only callable by an agent of the contract.

function addIdentityToStorage(
    address _userAddress,
    IIdentity _identity,
    uint16 _country
) external;

removeIdentityFromStorage

Source: IIdentityRegistryStorage

Description: Removes a user from the storage. Only callable by an agent of the contract.

function removeIdentityFromStorage(address _userAddress) external;

modifyStoredInvestorCountry

Source: IIdentityRegistryStorage

Description: Updates the country corresponding to a user address. Only callable by an agent of the contract.

function modifyStoredInvestorCountry(address _userAddress, uint16 _country) external;

modifyStoredIdentity

Source: IIdentityRegistryStorage

Description: Updates an identity contract corresponding to a user address. Only callable by an agent of the contract.

function modifyStoredIdentity(address _userAddress, IIdentity _identity) external;

bindIdentityRegistry

Source: IIdentityRegistryStorage

Description: Adds an identity registry as an agent of the Identity Registry Storage Contract. Only callable by the owner of the contract.

function bindIdentityRegistry(address _identityRegistry) external;

unbindIdentityRegistry

Source: IIdentityRegistryStorage

Description: Removes an identity registry from being an agent of the Identity Registry Storage Contract. Only callable by the owner of the contract.

function unbindIdentityRegistry(address _identityRegistry) external;

linkedIdentityRegistries

Source: IIdentityRegistryStorage

Description: Returns the identity registries linked to the storage contract.

function linkedIdentityRegistries() external view returns (address[] memory);

storedIdentity

Source: IIdentityRegistryStorage

Description: Returns the ONCHAINID of an investor based on their wallet address.

function storedIdentity(address _userAddress) external view returns (IIdentity);

storedInvestorCountry

Source: IIdentityRegistryStorage

Description: Returns the country code of an investor based on their wallet address.

function storedInvestorCountry(address _userAddress) external view returns (uint16);