[5 / 0 / ?]
Quoted By:
SCENARIO: a P2P distributed network in which users connect by a DHT. They identify themselves by a hexadecimal 76-character string.
PROBLEM: users need to choose their own ID, not have a really long and random one assigned to them. And with security in mind, the network needs to remain 100% distributed, so servers with pubkey:username aren't possible.
POSSIBLE SOLUTION: distributed databases. However, how can we guarantee the uniqueness of the username? A blockchain à la bitcoin isn't a possibility because downloading gigabytes of data also isn't user friendly and also not useful for dynamic content.
POSSIBLE SOLUTION: Distributed file systems such as Tahoe-LAFS. Extremely complicated and overkill, not easily or cleanly implemented.
So, the issue is having user-friendliness and security/distribution at the same time.
Any ideas?
PROBLEM: users need to choose their own ID, not have a really long and random one assigned to them. And with security in mind, the network needs to remain 100% distributed, so servers with pubkey:username aren't possible.
POSSIBLE SOLUTION: distributed databases. However, how can we guarantee the uniqueness of the username? A blockchain à la bitcoin isn't a possibility because downloading gigabytes of data also isn't user friendly and also not useful for dynamic content.
POSSIBLE SOLUTION: Distributed file systems such as Tahoe-LAFS. Extremely complicated and overkill, not easily or cleanly implemented.
So, the issue is having user-friendliness and security/distribution at the same time.
Any ideas?
