Sending asset-level commands to the wallet (query, transfer, claim)

[michaelpiron]

Based on our interaction with pilot users in the Elia Group ETT implementation, we detected the clear need to be able to send asset-level commands to the wallet/service.
So instead of requesting transfers or claims based on certificate IDs, they need to be able to request transfers/claims based on the asset IDs (the asset that generated the certificates) + walletsection + timeperiod.
It is about adding a layer of higher-level commands:

Example API endpoints to illustrate this

For illustration, here are our current API endpoints, which accommodate this asset-level command need:

1. Querying certificates by asset:
   

2. Transfers by asset:
   

3. Claims by asset:
   

How can we accommodate this in the Project Origin wallet implementation?

@wisbech @MartinSchmidt @WouterMarien @torfiriand @Kingaday @Mike4Elia

[MartinSchmidt]

My immediate thought is wether or not this belongs in the wallet itself, or in another microservice that interacts with the wallet.

My worry could be that the wallet quickly becomes the new center of everything, and that is definably not what we would want in the long run, how would continually claiming work, I would rather not implement a rule engine in the wallet itself.

But the asset id could be an attribute of the certificate, and we could possible allow claims between different certs based on an filter, where attribute or ids could be used. That way it would not be a specific thing in the wallet that it only allow it on asset-id but any combination of attributes.

If you want to continue to support your current API that could then be translated in an intermediate service.