Let user re-link and re-order their contextids

[adamstallard]

If a user re-links a contexid that was used before, but only by them, it should be allowed. It should update the timestamp on that contextid and bring it to the front of the array returned by /verifications; unique should be true for that contextid.

[abramsymons]

We are allowing to link the last contextId again now.
But allowing to use old ones will cause loops in history for the contract implement to publish verifications onchain, so apps can not traverse history to find all the ids used by the user.

[adamstallard]

We are allowing to link the last contextId again now.
But allowing to use old ones will cause loops in history for the contract implement to publish verifications onchain, so apps can not traverse history to find all the ids used by the user.

At first I thought this should be fixed in the smart contract, but really the smart contract is rebuilding the whole history each time from the array that is passed in--see https://github.com/BrightID/BrightID-SmartContract/blob/d3254dc32851b0e91722b79e4a602efd05de562a/v4/BrightID.sol#L37-L42 , so if a node can insure that the address array doesn't have duplicates, there will be no cycles.

It sounds like you found a good solution by just updating the timestamp to be the newest so it will be the first in the array.

[abramsymons]

resolved by:
b80ec55