Feature Request: Revocable phone number mappings

[arthurgousset]

A friction occurs when users map their phone number to 2 different wallet addresses. In that case, a user who want to send this (double mapped) recipient CELO has to enter the last 4 digits of the recipient's wallet address.

This can be a friction when the point of phone numbers is to send funds without dealing with wallet addresses.

(AFAIK) This can be solved today, by inviting the user to re-map their phone number to the “correct” address (their choice), as the attestation service resolves to the account for which there is the highest number of attestations.

Alternatively, in the future,

• this might be solved at the smart contract level by introducing an expiry or revocation mechanism that allows users to revoke phone number mappings to wallet addresses, or
• this might be solved at the client-level by inviting apps to check whether a given phone number has an existing mapping (using a reverse lookup), prior to issuing an additional mapping.

Closed ticket for now (#9274) until we gather more feedback to prioritise.