Index paymentReference in storage subgraph for unencrypted requests

[MantisClone]

Problem

We're considering a feature for REQScan to search for a request by paymentReference.

Solution

Building such a feature would be easier if the storage subgraph calculated and indexed the paymentReference whenever it indexed a new unencrypted request.

Considerations

In the past, we have tried to keep a layer of privacy by obscurity between the paymentReference and the request. But anyone can derive the paymentReference from an unencrypted request. Should we maintain privacy by obscurity?

[MantisClone]

Linking the payment to an unencrypted request is technically possible, but difficult. This issue is proposing to make it easy - via REQScan.

Linking the payment to an encrypted request remains impossible.

[MantisClone]

Delay until V2. In V1, we'll calculate the paymentReference in the frontend.

[Fpinto29]

Delay to V3