arnaucube
/
blockchainIDsystem
mirror of https://github.com/arnaucube/blockchainIDsystem.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
15 Commits
1 Branch
0 Tags
17 MiB
 
 
 
 
 
Tree: 4898cae5c0
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '4898cae5c0'
${ noResults }
blockchainIDsystem/README.md

3.7 KiB
Raw Blame History

blockchainIDsystem

A blockchain based anonymous distributed login system

Main concept

The objective is to guarantee a decentralized login system, but making sure that registered users are real ones and there are no bots generating large amounts of accounts. Only the verified (by email or phone) users can generate an anonymous ID (the Public-Key blind signed).

How it works?

Network infrastructure

network

There are different types of nodes:

  • peers
    • the peers of the p2p network that runs the blockchain
  • serverCA
    • Is a REST server that has been certified (is the Certified Authority) to validate the peers that will be able to participate of the blockchain.
    • Have the webapp (frontend) to validate peers through a GUI interface
    • The GUI frontend webapp allows also to view the current peers of the network and the blocks of the blockchain
  • server-ID-signer
    • The server where the user creates a non anonymous account
    • Also is the server that blind signs the Anonymous ID of the users
    • Have the webapp (frontend) to interact through a GUI interface

Step by step process

  1. Once all the nodes of the network are running, a new user can connect to the server-ID-signer.
  2. The user registers a non anonymous user (using email, phone, password, etc), and performs the login with that user
  3. The user, locally, generates a RSA key pair (private key & public key)
  4. The user blinds his Public-Key with the server-ID-signer Public-Key
  5. The user's Public-Key blinded, is sent to the server-ID-signer
  6. The server-ID-signer Blind Signs the Public-Key blinded from the user, and returns it to the user
  7. The user unblinds the Public-Key signed by the server-ID-signer, and now has the Public-Key Blind Signed by the server-ID-signer
  8. The user sends the Public-Key blind signed to the p2p network
  9. The peers verify that the Public-Key Blind Signed is correctly signed by the server-ID-signer, if it is, they add the Public-Key to the Blockchain, inside a new block
  10. Then, when the user wants to login into a platform, just needs to put his Public-Key
  11. The platform goes to the Blockchain, to check if this Public-Key is registered in the blockchain
  12. The platform sends a message encrypted with the user Public-Key, and the user returns the message decrypted with the Private-Key, to verify that is the owner of that Public-Key
RSA encryption system

https://en.wikipedia.org/wiki/RSA_cryptosystem

  • Public parameters: (e, n)
  • Private parameters: (d, p, q, phi, sigma)
  • Public-Key = (e, n)
  • Private-Key = (d, n)
  • Encryption: rsa
  • Decryption: rsa
Blind signature process

https://en.wikipedia.org/wiki/Blind_signature

  • m is the message (in our case, is the Public-Key of the user to be blinded) rsa

  • server-ID-signer blind signs m' rsa

  • user can unblind m, to get m signed rsa

  • This works because RSA keys satisfy this equation rsa and this rsa