README

High level overview

Basic Identity Token attempts to create a protocol for self-sovereign distributed identities with the ability to retain information about social graphs and connections.

The hope is to decentralize social media personas, thereby improve UX on next-gen social media sites by allowing an identity with its social graph to exist in an open decentralized manner and allow any new sites the user signs up for to use them. This saves the user wasted time re-generating their social graph on every new site manually due to the walled garden problem created by closed segregated social media databases.

The current PoC code implement a login with FB button for Ethereum/Hyperledger Dapps allowing easier migration of classical social media users and persona information to the web3 decentralized world.

Licensing todos

This project is licensed under the MIT license and therefore will not use any GPL (copyleft) licensed libraries.

Currently the project has code requiring web3js and storj which are released under the GPL license. These have been removed from package.json and are no longer dependencies and will need to be refactored from the code.

Moving forward this project will use ethers-io/ethersjs instead of web3js, ethersjs is MIT licensed. Current code will be wrapped to populate the web3 namespace with a shim for ethersjs.
E.g. ethers-io/ethers.js#59

From our experimentations the storj api was found to be unuseable and unnecessary and therefore that dependency will be dropped entirely.
We will instead move to simply using the IPFS API. IPFS is licensed under MIT.

README - Basic Identity Token

Welcome to the PoC of BIT. This PoC attempts to be an implementation of a "login w/ facebook" button for web3.0 dapps. Offering a bridge of sorts for transitioning to web3.0 services while maintaining the users social profile information and allowing them to identify strongly with the services vs weakly when they're being represented by an anonymous SHA3 hash, i.e. wallet address.

SETUP

There's 2 projects here.
IdentityStore provides the identity retrieval, storage abilities GooseHunter is an implementation of using the IdentityStore dapp and frontend for authentication. You'll need 3 open terminal windows.

• First get testrpc running and give yourself some cash money. Replace the account id with your testrpc private key.

 testrpc --account="0x+PrivKey,1000000000000000000"

• Get the identity provider running:

cd IdentityStore
npm i
npm run run

• Run the GooseHunter auth user app

cd GooseHunter
npm i
truffle compile && truffle migrate
npm start

Walkthrough

Authentication flows can be one of 2:

• User starts at GooseHunter app, which attempts to personalize its frontend based on social info. If the user does not have an acc they will be re-routed to the IdentityStore app.
  In the IdentityStore app they can "login w/ facebook". Profile information from FB is written to the blockchain for a nominal fee.
  IdentityStore then reroutes back to GooseHunter which now has profile information and can render it. All future profile use is effectively free as its free to read from the blockchain.
  This also provides a proof of identity and proof of login for the user in case its needed.

• Alternatively, the user can first login @ IdentityStore, and any future use of GooseHunter will be autopopulated as the profile data is looked up by the users SHA3 wallet address hash.

Experimental featurettes:

• taxation & identity pruning
• identity pruning
• Staking associated with id's to prevent abusive behaviour

PICTURES!!

Secondary Dapp/user Authenticated BIT using app BIT PoC introscreen BIT data display BIT data display 2