They are proposing a new protocol. However, the main concepts can be adapted for namecoin, namely a unique URI (which can be .bit) and an audit of every access (potentially namecoin spends) and since hte block-chain is transparent, audit tools which trawl the block-chain to figure out classes of people (actual owners of privatekeys would be harder) it could be implemented.
http://www.zdnet.com/transforming-the-w ... 000030534/
TechReview of privacy
TechReview of privacy
Dr. Lawrence Lau
http://www.linkedin.com/in/drllau
http://www.linkedin.com/in/drllau
-
John Kenney
- Posts: 94
- Joined: Sat Mar 29, 2014 2:20 pm
- os: linux
- Location: Sheffield, England
- Contact:
Re: TechReview of privacy
The paper gives more information... http://dig.csail.mit.edu/2014/Papers/PST-PETS/PETS.pdf seems interesting & I agree a lot of those concepts could be applied to Namecoin. It looks like they've chosen DHT instead.
I've been wanting to do some similar things with Namecoin & the id/ space. I want to add a web of trust so that people can store id information in the blockchain & the verifications of that information too. If the verifications can come from verified identities, then I think it'd be possible to use statistics to mitigate Sybil attacks & create a new improved type of web of trust system. I also want to try to standardise a format for storing verification tokens for private information in the blockchain.
A Namecoin id can already be used for authentication, but there's no verification of the data stored in id, I mean it's verified that was what was entered by that user, but I could call myself Fred Flintstone if I wanted or set up thousands of fake IDs. Also, if there's a way for third parties to verify information stored, there's no standard way to not broadcast all the id information you store under id to the world, yet & that becomes even more important when it's verified information.
I've been wanting to do some similar things with Namecoin & the id/ space. I want to add a web of trust so that people can store id information in the blockchain & the verifications of that information too. If the verifications can come from verified identities, then I think it'd be possible to use statistics to mitigate Sybil attacks & create a new improved type of web of trust system. I also want to try to standardise a format for storing verification tokens for private information in the blockchain.
A Namecoin id can already be used for authentication, but there's no verification of the data stored in id, I mean it's verified that was what was entered by that user, but I could call myself Fred Flintstone if I wanted or set up thousands of fake IDs. Also, if there's a way for third parties to verify information stored, there's no standard way to not broadcast all the id information you store under id to the world, yet & that becomes even more important when it's verified information.