⦃param⦄ Node
Last updated
Last updated
⦃param⦄ is a Quorum-based (Ethereum) blockchain protocol that has been developed to provide the Commerce Industry with a permissioned public implementation of Quorum that supports sharing documents such as Quotations, Purchase Orders and Invoices to zero-infrastructure enterprises without a need for consortium and with utmost data-privacy.
The full node consists of:
Modified Geth client from Quorum node - will have ledger structure changes to record commerce transaction states
Modified Tessera transaction manager with support for sending PGP encrypted documents on public network with subscribers support
Cayley Graph to construct node-level knowledge graph based on network events
Ready-made libraries & services for integration with enterprise resource planning (ERP) softwares
⦃param⦄ supports three modes of document transfer between nodes.
This mode is used for transferring the documents between two private nodes securely without leaving any trace on the public blockchain except for the signature of the transaction for future validation. The steps followed are:
The local node sends the documents to transaction manager
Transaction manager generates a random symmetric key for encrypting the document
Document is encrypted using random symmetric key
Later, symmetric key is encrypted using RSA with receiver's public address for sharing the key via the network
Private nodes will create a dedicated point-to-point secure connection
Both encrypted key and the document are shared via secure connection
The receiver acknowledges the document transfer
Signature hash including the acknowledgement and the document is created
Finally, upon successful private document transfer, the transaction is sent to P2P public network
Protected Mode of transfer mimics the private mode on the public node. Here, the encrypted documents are stored on the public nodes. This enables the small/medium enterprises and consumers to store documents such as invoices and purchase receipts securely on blockchain and claim ownership for forward use-cases, such as financing, insurance, resale, etc... The steps are:
Documents are encrypted using symmetric keys like Private mode
Encrypted keys and documents are stored as part of the public ledger
Transaction is processed and block is mined like public transaction
Nodes that are opted for storing protected transaction will sync as part of the block sync mechanism
Note that although the document is stored on public nodes, its readable only for the sender & receiver by default.
Public mode is in compliance with Ethereum like transaction, where the documents are open-format, included as part of the transaction and all nodes syncs this data.
Largely Smart contracts behaviour at a node level remains same, but as a network it would look different depending on the mode of transfer. Smart-contracts that involve Private/Protected documents, the contracts can be executed only on the sender and receiver nodes, who have access to these documents. Whereas, for public documents, multiple node can participate in execution and consensus.
⦃param⦄ provides enterprise level data-privacy, additionally it democratize the data by making it available equally for both sender and receiver, empowering them with the data ownership. Below tables gives the overview of the data access across parties and transfer types.
Transfer Type
Buyer Node
(all node-type)
Seller Node
(all node-type)
Protected Node
(third-party)
Public Node
(third-party)
Private
Visible
Visible
Not Applicable
Not Applicable
Protected
Visible
Visible
Not-Visible
Not-Visible
Public
Visible
Visible
Visible
Visible
"Subscribers" is the concept of attaching ownership of the documents that are shared on the network. In private/protected mode, the sender and receiver becomes subscribers automatically and they have equal access on the data, such as:
Add more subscribers
Execute smart-contracts on their nodes where private key is available
Independently run data-queries on their data for self consumption
The existing subscribers can add more subscribers to share the documents. For example, a buyer can share the invoice document with financial institutes for loan processing.
Raft based Consensus being used in testnet. There will IBFT
