Step 5: Get preregistration data

[jatitoam]

Add a new /preregistration/account/:account?signature=<signature> (GET) endpoint to get the full preregistration document in an application/json format.

Validations should be returning using 4xx error and a json document:

{
   "error": "<specific error>"
}

Validations:

• Account in invalid format (regex): 406
• Account not found in the preregistration collection AND in the account collection (it needs to be in both): 404
• Signature not sent: 406
• Signature not base64: 406
• Unencoded signature not json format: 406
• Validation fails (using concordium-sdk): 403

Important:

After signature verification (using concordium-sdk) the nonce needs to be cleared in the account document to invalidate it (if validation passes or fails).

Return:

If everything works, return the whole preregistration document in json format and a 200 http code.

Transformations:

The following are two rules for transforming the presented data (it will not affect the database):

• The referred count will be limited to 6. Anything more than 6 will be returned as 6 in this field.
• Add a derived field referredAmount which will be referred x 25. Tops is 150 (as referred top is 6)

[CongThuong]

May you please explain me more about "Add a derived field referredAmount which will be referred x 25. Tops is 150 (as referred top is 6)" @jatitoam

[jatitoam]

we only allow 6 referred per id, so if referrer > 6, return 6

in consequence, referredAmount (referred x 25) can only be 150 tops

[thaoredweb]

This issue is penidng signature from FE, will check later on