Starting a new topic to discuss the implementation of a pseudo anonymous membership proof in a Social Recovery Process. see: ERC2429
Problem: In a recovery the peers will have theirs addresses link to the user in recovery. Privacy and accounts correlations is something all users should be aware and as possible the system should have mechanism to help in privacy matters.
To mitigate this problem in the context of ERC2429, I think will be beneficiary to include a extension as how the Merkle tree is build.
One solution is to generate new Accounts for each recovery contract, mitigating the potencial link between accounts. But this solution put more pressure on the peer, that will have to manage more keys. As the recovery process is something unusually done, there is a probability of keys getting lost.
The proposed solution is something like a barebone HD Wallet strategy.
- The user setting a Recovery contract has to generate a peer_Hash (ERC2429).
- The peer uses this peer_hash with their private key.
- Following something like
NewPublicKey = PrivateKey * Secret * G
- When is needed a recovery process, the user will give the
Secretagain to the peer that have a capacity of regenerate the member account.
There is no way to enforce this solution in the context of ERC2429.
p.s - gist