Task description
In the future, users should be able to reveal more attributes on their accounts at a later time than on account creation. To enable this, the randomness used to reveal attributes on account creation must be saved in the database so it can be accessed later.
Requirements:
The mobile wallet saves the randomness for new accounts in the database in a secure way.
The randomness can be accessed later, so people can reveal more attributes on their account. We should also have the option to access the randomness for potential future off-chain use-cases.
The new version of the mobile wallet must be able to handle “old” accounts created before the randomness could be saved in the database.
The export/import feature must support the saved randomness.
Notes:
The randomness is secret material so it must be handled in a secure way, on par with account keys and IdCredSec.
The response from createCredential from the library supplied by Concordium, has an additional field commitmentsRandomness.
Task description In the future, users should be able to reveal more attributes on their accounts at a later time than on account creation. To enable this, the randomness used to reveal attributes on account creation must be saved in the database so it can be accessed later.
Requirements:
Notes: