AFTER WE integrate the Identity SubSystem into the Data DEX and can verify it meets our requirements, we then need to optimize our architecture:.
Our identityFactory deploys identity contracts for everyone; there is a lot of code duplication here. Let's aim to assess feasibility of using the EIP 1167 minimal proxy pattern. This will result in less code fragmentation and duplication, lower gas costs for user who's deploying and also allow Itheum to upgrade the core identity contract to newer and better version in future.
AFTER WE integrate the Identity SubSystem into the Data DEX and can verify it meets our requirements, we then need to optimize our architecture:.
Learn more about this standard here - https://blog.openzeppelin.com/deep-dive-into-the-minimal-proxy-contract/
Note: This should ONLY be done AFTER WE complete testnet integration of existing version with the Data DEX