Revisit GetDataForEncryption endpoint #83
Description
See my comments from here:
I am actually quite unhappy with this design, as it spills internals into the need-to-know-domain of the users. It doesn't help either, that we have the need to document deployment differences for different chains in the same documentation.
Also the endpoint is overloaded with event based and time based registrations which leads to parameter selection based domain switching (i.e. IF triggerDefinition provided THEN query event based).
With the current wording, one might believe that the deployment on one chain allows retrieval of identities from the other.
I'd love to change this to a design where at least address is an optional parameter, and, if omitted, we would internally resolve the signer key's address.
It is a somewhat obscure/redundant endpoint anyway in my view. All necessary data is already returned during registration, where we have domain specific (time vs. event based) endpoints.