After brief discussions in the BrightId keybase chat, it seems we can configure a node's verification algorithm to weight connections higher that are close to seed members that we can specify. We should investigate if this could be a useful feature for mitigating some of the recently uncovered issues with single users controlling multiple users accounts.
We can also investigate if we can combine alternative configurations with records of other engagement within 1Hive.
After brief discussions in the BrightId keybase chat, it seems we can configure a node's verification algorithm to weight connections higher that are close to seed members that we can specify. We should investigate if this could be a useful feature for mitigating some of the recently uncovered issues with single users controlling multiple users accounts.
We can also investigate if we can combine alternative configurations with records of other engagement within 1Hive.