I integrated ILMRegistry contract into our FE. Now we are getting strategies dynamically from that contract and just description, name, logo and type from config. I think we should rely on config as less as possible. Moving from config to ILMRegistry will gives us a lot of flexibility in future. For example, we could configure logo, description and name of a strategy and deploy FE. UI will stay the same (strategy will not appear) until it is registered in registry contract. This means that we can finish eng tasks much earlier then marketing team so we are not late and they don't depends on us that much.
I integrated ILMRegistry contract into our FE. Now we are getting strategies dynamically from that contract and just description, name, logo and type from config. I think we should rely on config as less as possible. Moving from config to ILMRegistry will gives us a lot of flexibility in future. For example, we could configure logo, description and name of a strategy and deploy FE. UI will stay the same (strategy will not appear) until it is registered in registry contract. This means that we can finish eng tasks much earlier then marketing team so we are not late and they don't depends on us that much.