Topic: Identifi.org - Address book with ratings - page 3. (Read 27948 times)

I've started coding this based on Freenet's Library plugin. I'll let you know when I have something that works.

Slides from my presentation at Bitcoin Cafe Helsinki: http://www.rvl.io/mmalmi/identifi

My friend and I were actully working on something simialr to this until he kinda gave up and then it ended. If someone is interested in doing this I would love to help you with it.

@sirius
Maybe you can use this software for part 2)
 of your proposal :
http://code.google.com/p/phantom/

They even have anti-government licensing )
If your project will take off and will
 generate huge traffic phantom maybe better,
than Freenet.
Freenet can even collapse under
 your project's additional weight (
-------
Although, phantom can only give you networking capabilities, but not DHT or
 indexing.

I'm working on a Real P2P messaging system (encrypted channels only) which requires public/private keys. Perhaps this could be the database, You build trust by communication over public key identity, then attach your contract to your P2P identity public, Although my app isn't near complete yet, but I posted here to notify those who would like to help contribute to the project: https://github.com/Xenland/P2P-Crypt

Alternatively,

 would it be possible to make a website interface to #bitcoin-otc with the database distributed? Just something to point and click to generate your keys and identity for a start.

 Such as thing could be easily moved to a tor hidden service. I say tor because that would go nicely for Silkroad users.

Thanks for the links and ideas.

Looks like there actually is an indexing tool for Freenet: https://wiki.freenetproject.org/B-tree_index. Would be cool if Freenet could be used for all the networking stuff. I'll be looking into it.


Namecoin is a name/value system and it's not the best option for storing tons of data, like relations in this case.

This project definitely needs to get going. I started something very similar called "Bitcoin's Distributed PKI".
It was put on hold for the BitSafe Hardware Wallet.

I would argue that block chain technology is ideal for this system.
Bitcoin's block chain should be used for managing and establishing the identity and the public keys that go with it.
a separate database or block chain for reputation portion.

Interestingly, I had similar thoughts.  I spent the weekend trying to work this out and posted this thread, yesterday as well.

https://bitcointalksearch.org/topic/rfc-trust-transaction-130101

http://privwiki.dreamhosters.com/wiki/Distributed_Web_of_Trust_Proposal_2

From the people who brought you #bitcoin-otc's WoT

EDIT: also #bitcoin-wot for discussion

Distributed identity and reputation database  -- good idea.

Hey sirius ... good to see that ginger kitten back around.

Just gonna keep a watch for now .... except to say, isn't namecoin able to do a lot of this already?

All of the heavy lifting can already be provided through various means.

The things is that nothing decentralised is easy to use. I gave up on Bitcoin-OTC

Social networking based WoT is the only good option I can think of. Users could evaluate relations' trustworthiness based on their creator's location in the social network. Off to crawl Facebook ->

Not one to pick an easy task, are you?

I can't really help you here, but I can locate potential problems pretty fast.  Assuming that you can develop such a distributed reputation database, that can't be undermined or hacked, what prevents people from developing multiple online identities to game the rep systems?

Here's my idea in a nutshell: A distributed network that models identity and reputation as a graph, where different kinds of user identifiers are nodes and user-created relations are links between them. The relations can be evaluated with various algorithms and criteria, such as social network based web of trust to make it sybil-proof.

The network allows users to check the reputation and other connections of a previously unknown identity. For example, you could decide to borrow 20 bucks to a stranger in a pub after finding out he's your 3rd degree connection on FB and has mostly positive ratings. Or you could write reviews of policemen, teachers, judges or other public servants with whom you can't choose not to interact.

Reputation that is instantly visible to everyone is a big incentive to not be a butthead. Maybe even bigger than threat of imprisonment, and definitely more cost-efficient and p2p.



1. Data model
1.1 Identifier
Unique or non-unique identifier of a user. Examples:

• Name
• Phone number
• Email address
• GPG key
• Facebook username
• Date of birth
• Photograph

Fields: type, value.

1.2 Relation
A link between two or more identifiers. Relations are GPG-signed by their creator. Examples:

• ID1 says: "I traded with ID2 and it went smoothly"
• ID1 says: ID2, ID3 and ID4 belong to the same owner
• ID1 says: ID2 and ID3 are Friends on Facebook
• ID1 borrowed $100 to ID2 (signed by both parties)

Fields: Type, value, timestamp, target IDs, signatures.

2. Distributed data storage and index
This is more of an open question and I'm asking for your ideas on it. The network must be resistant to censorship and political pressure. In addition to storing the static identifiers and relations, for searching we need a dynamic inverted index that links identifiers to the relations they're involved in.

Freenet would be a solution for the static part but it doesn't solve the indexing problem. Distributed indexing could be done with a distributed hash table structure, for which there are existing libraries like Kademlia. Bootstrapping would be easier if we could use an existing indexing network like YaCy, but it doesn't support Freenet atm.

3. Use case
Web site where users can rate their experience with public servants.

1. Alice logs on to the site with her FB account
2. The site creates an ID with type "[email protected]" and Alice's username as value.
3. Alice writes a review of Bob the policeman.
4. Alice adds Bob's full name, phone number, email and FB username to the review.
5. The site creates a relation that connects Alice's ID with all the Bob's IDs she entered. The relation content is Alice's review and it's signed with the site's GPG key (because the site verifed Alice's FB identity).
6. The newly created relation is published to the network.

Now the review can be found by any of the Bob's IDs entered by Alice. Changes or additions to Bob's details can be added later with new relations. Bob could write a reply to the review and sign it with his WoT-verified GPG key, for instance.



Ideas and suggestions welcome!