The identity registry implementation that relies on a smart contract requires the ability to submit transactions to the blockchain and listen to events. This was successfully implemented using the componentTest in Paladin as a guidance. After further conversations, because this portion of the registry would be part of the plug-in structure, it would not have access to the same features as the componentTest. Instead it would need to rely on API calls to Paladin which are not yet available. The plug-in plumbing was recently built and a config based static registry was added. The purpose of this issue is to track the work to move the flexible hierarchical logic created in the registry implementation to the manager.
The identity registry implementation that relies on a smart contract requires the ability to submit transactions to the blockchain and listen to events. This was successfully implemented using the componentTest in Paladin as a guidance. After further conversations, because this portion of the registry would be part of the plug-in structure, it would not have access to the same features as the componentTest. Instead it would need to rely on API calls to Paladin which are not yet available. The plug-in plumbing was recently built and a config based static registry was added. The purpose of this issue is to track the work to move the flexible hierarchical logic created in the registry implementation to the manager.