We are developing a pilot for the use of sovrin in the setting of humanitarian aid in disaster areas. One of the processes we want improve is cooperation between humanitarian organizations with regards to registration and identification of people that need help. So for example:
- Humanitarian organization named Y would give out claims for people that needs help with the attributes name, age, coordinates of his/her house. They do this by having a physical meeting with these people and checking the passport for example.
- Humanitarian organization X runs a program in which cash is distributed to people over a certain age living in a certain area and people can sign up digitally. X and Y trust each other and therefore X would accept zero knowledge proofs of claims given out by Y and can therefore help people without knowing their full identity.
This seems like a workable scenario. We are however wondering to what extend we can prevent double registration.
So for example if there is a third humanitarian organization Z also giving out claims following the same schema as Y. Z is also trusted by X and claims from Z can therefore also be used to participate in the the program.
How could we prevent a person from creating a 2 wallets or/ using two phones to both register with Y and Z (or even register twice at Y). And then using both claims stored in different wallets to participate twice with the program of X and therefore receive cash twice.
Is there a method in Sovrin system to prevent double registration or does anyone have a suggestion outside of Sovrin to prevent this?