I’d like to continue this idea here. Besides it needs a HIP itself, I’ve been talking with juanu and I’d like to read what the community thinks about it. @juanu correct me if there is something wrong:
- Build a contract that stores “management declarations” like: 0x1 manages [0x2, 0x3, …] accounts and such. This could have a limit (max of 10 managed accounts, for example). This ‘declaration’ requires an extra on-chain tx.
- Include management in the policy, allowing 0x2 to say something like “my account will be managed by 0x1”. The challengers could check in the management contract if it’s true, or else challenge the submission as duplicates/sybil (like @green proposal). Also, Juanu suggest that it could be “declared” after the submission to avoid Removal Request of declared managements.
- This seeks transparency. People will continue managing family accounts, but integrators could use this new contract to check if it’s a managed human account or not. Also, a more strict policy with non-declared managements can lead to challenges as sybil/duplicates and keep the security of the registry.
- We can also use this contract for others segmentations of human accounts, as I mentioned with PoH Levels. I just need to think more about it.