hypermine-bc / hypersign Goto Github PK

• Enroll bootstrape identity
• Register an identity
• Enroll an identity
• Reenroll an identity
• Revoke an identity/certificate
• Getting identity info

Help doc

• Certificates are one of the most important part of Hyperledger.
• HL needs a lot more certificates to be mangaged because of its complex architecture.
• Managing these certificates is very cumbersome and timetaking.
• Our goal is to simplify the process of certificate management.
• Part of the large goal is to build a tool to to generalise this concept.

Note: This is half thought problem, more researches needs to be done in this section.

A discord channel should be created, so that people testing the app can take questions

• https://github.com/Vishwas1/fabric-ca.git
• https://readthedocs.org/projects/hyperledger-fabric-ca/downloads/pdf/latest/

There should be live playground for testing add for developers

• #12
• #11
• #10

• What algorithm?
• What key-size?
• What library?
• Just focus on cryptographic key-pair generation
• To remind you, we need not to know anything about Blockchain in general for this task.
• etc.

• https://github.com/Vishwas1/openssl.git
• https://www.openssl.org/docs/

• Help
• Help

• What algorithm?
• What key-size?
• What library?
• Just focus on cryptographic key-pair generation
• To remind you, we need not to know anything about Blockchain in general for this task.
• etc.

I've been looking at the readme file, and the problem which this project aims to solve is very important. Even I've been working on this, but not getting much time to work on this/ would like to contribute.

From the Readme, I see that purpose of AuthServer is to verify signatures. Here, phone and computer are peers and they have to depend on the AuthServer as a middleman for functioning. I think a server is not required to verify signatures since it's pure Elliptic Curve Cryptography which means the phone and computer can do themselves. A computer browser can generate a random number, this number should be relayed to the phone using something like WebRTC for it so sign it using the private key and can relay the number with the signature back to the computer browser UI and a continuous WebRTC connection can be established between the browser and the phone. Further, signature requests for every action from the dApp can be sent to the phone for signing as long as the connection is active.

Currently, there is a service called WalletConnect. My concerns are that the connection is through a centralized server. It means if their server shuts down for a few minutes, users won't be able to use their phone to sign transactions on a dApp running on their computer.

It'd be really great if we can establish a local connection using something like WebRTC, in case the user's computer and phone are on the same WiFi network and only use a centralized server if both devices are not on the same network. P2P communication between the computer and phone can remove the dependency of an authentication server.

• Prerequisite
• Install the server and client
• Initialize the server
• Start the server
• Configure database

Help-doc

• Why there is diffrences in key-pair formats among these chanins?
• What is the rational behind using different key algo and formats?

• What algorithm?
• What key-size?
• What library?
• Just focus on cryptographic key-pair generation
• To remind you, we need not to know anything about Blockchain in general for this task.
• etc.

• Irrespective of blockchain, see how does digital signature works in these chains.

Two ways of interacting with a Hyperledger Fabric CA server:

• Hyperledger Fabric CA client
• Fabric SDKs

We have already done research on CA client cmd tool. We need to research on node js SDK. Use SDK to mimmic those same steps which we did here with cmd client .

Goal: To use single cryptographic key pair to do transactions on multiple chains.
Problem:
Every day new blockchain coming up. In order to get services (by doing transactions, essentially) of these chains, a user has to manage their respective key-pairs which is becoming a hassle for them. The problem exists specially in an enterprise setting where an user (employee) has been using username and password for single sign on (SSO), and now one (or some) of the registered service provider (SPs) want to implement blockchain (same or different) in their ecosystem either for payment (on Bitcoin blockchain) or for smart contract execution, in either of the case, they require user to manage key-pair for doing transactions. Now the user has to manage set of key-pairs, since these SPs may or may not use same blockchain, apart from current username and password. User also has fear that tomorrow if another SP start using a different blockchain, then he has to manage another set of key-pair.

More

• https://hyperledger-fabric.readthedocs.io/en/master/msp.html#how-to-generate-msp-certificates-and-their-signing-keys