Skip to content

BLOCKOTUS/hyperledger-fabric-offline-transaction-signing

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

30 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation


|| BLOCKOTUS || Offline Transaction Signing

for Hyperledger Fabric







Abstract

In most use cases an application will persist the user's credentials including the private key and sign transactions for the user. However some business scenarios may require higher level of privacy. What if the user wants to keep their private key secret and does not trust another system or backend server to securely store it and use it?

The fabric-common package comes with the ability to sign a transaction outside of the application. The application may choose to include the signature when calling the send method of the service instead of the identity context that would be used to create the signature. [1]

Documentation

import { sendProposal } from 'hyperledger-fabric-offline-transaction-signing';

const proposalResponse = await sendProposal({
  client,
  user,
  privateKeyPEM,
  channel,
  chaincode,
  fcn,
  args,
});

This repository is part of the BLOCKOTUS Organism.

BLOCKOTUS Architecture

Tool compatible with || BLOCKOTUS || Organism

Build complete decentralized applications with Blockotus Open and Decentralized Standard and Hyperledger Fabric.

The kit includes a Frontend (Svelte / React), a Backend (Nodejs / Express), a Network and Chaincode Contracts (Hyperledger Fabric) as specified by Blockotus Open and Decentralized Standard.

BLOCKOTUS Organism.






References

[1] https://hyperledger.github.io/fabric-sdk-node/release-2.2/tutorial-sign-transaction-offline.html

About

Hyperledger Fabric offline transaction signing library. Sign a transaction outside of the application.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published