@adecaro this PR depends on hyperledger-labs/fabric-smart-client#1033, right?
If that is the case, better mark is as draft :)

We usually bind an alias in the form of view.Identity("my_account") to an actual identity, and it has always felt a bit hacky and hard to understand. It also leads to more database calls and duplication (only one "alias" per key). Aliases can be the local name or reference id to retrieve it in the node itself, a public identifier like an IBAN or Ethereum or other address, or something else. Maybe we can take a look at the data model, and whether it may be worthwhile doing something like adding a table for string aliases that can be joined to the identities table? Maybe it's even feasible with backwards compatibility.

@adecaro @arner
Can you please explain you comment? is there any changes I should make?

@arner , good point. Yesterday, I was discussing with @ale-linux about reworking the FSC's identity provider and endpoint service. Your comments will be used during that rework.

not needed anymore