SUNDARA RAJAN

GAVS Technologies Pvt. Ltd.

I CLAIM:
1. A method of managing master data in enterprise networks using blockchain, the
method comprising:
detecting, by a processor (302), an event associated with a data entity of a master data, wherein the event is initiated by an enterprise network node (106) on a blockchain database (214) or an off-chain database (204);
validating, by the processor (302), the event based on predetermined validation rules;
initiating, by the processor (302), a transaction indicative of the event using one or more cryptographic keys if the event is valid;
adding, by the processor (302), the initiated transaction to a blockchain ledger based on a predetermined entity smart contract;
updating, by the processor (302), metadata and attributes associated with the data entity on the blockchain database (214);
propagating, by the processor (302), the data entity to other participating enterprise network nodes (106); and
linking, by the processor (302), the data entities of the master data based on the propagation.
2. The method of claim 1, wherein the event associated with data entity comprises
creating a data entity, creating an instance of data entity, modifying attributes of a data
entity, transferring full ownership of data entity instance, transferring partial ownership of
attributes of a data entity, managing version of smart contracts, or switching private keys.
-28-

SUNDARA RAJAN

GAVS Technologies Pvt. Ltd.

3. The method of claim 2, wherein creating the data entity or the data entity instance comprises uploading the data entity or data entity instance associated with an enterprise on an off-chain database.
4. The method of claim 2, wherein transferring full ownership of a data entity instance comprises:
receiving, by the processor (302), selection of data entity instance stored on an off-chain database for transferring full ownership to a target enterprise;
mapping, by the processor (302), the selected data entity instance to a public key of the target enterprise; and
changing, by the processor (302), the ownership information of the data entity instance in favor of the target enterprise based on the mapping.
5. The method of claim 2, wherein transferring partial ownership of attributes of a data
entity comprises:
receiving, by the processor (302), selection of data attributes of a data entity stored on an off-chain database for transferring partial ownership to an external stake holder;
mapping, by the processor (302), the selected data attributes to a public key of the external stake holder; and
changing, by the processor (302), the ownership information of the attributes of the data entity in favor of the target external stake holder.
-29-

SUNDARA RAJAN

GAVS Technologies Pvt. Ltd.

6. The method of claim 3, wherein validating the uploaded data entity or data entity
instance further comprises:
parsing the uploaded data;
matching the uploaded data with pre-existing data on the off-chain database to identify duplicates in the uploaded data, wherein the matching is performed using natural language processing and semantic parsing methods;
checking whether the data comprises predefined number of characters; and
checking whether the uploaded data has predefined access rights.
7. The method of claim 3, wherein uploading the data entity further comprises:
identifying, by the processor (302), large documents;
transferring, by the processor (302), the large documents to interplanetary file system (IPFS) by generating a unique hash;
creating, by the processor (302), smart contract for the entity and an IPFS hash; and accessing, by the processor (302), the large documents from the IPFS using the hash.
8. The method of claim 2, wherein managing version of the smart contracts comprises:
receiving, by the processor (302), modifications to the smart contracts;
capturing, by the processor (302), mapping information between an original version
and a new version to facilitate data migration between the versions;
creating, by the processor (302), an updated version of the smart contract; and mapping, by the processor (302), the data entities based on the updated version of
smart contracts.
-30-

SUNDARA RAJAN

GAVS Technologies Pvt. Ltd.

9. The method of claim 2, wherein switching private keys comprises:
receiving, by the processor (302), request for new set of private keys;
generating, by the processor (302), new set of private keys; and
updating, by the processor (302), the smart contracts using the generated private keys.
10. The method of claim 1 further comprising: maintaining an audit trail of the data
entities on the blockchain, wherein maintaining comprises:
detecting, by a processor (302), modifications to a smart contract;
storing, by the processor (302), the historical modifications to an off-chain database (204); and
retrieving, by the processor (302), the historical modifications as audit trails for analysis.
11. The method of claim 1, wherein the validation rules comprise predetermined semantic policies, predetermined syntactic policies, predetermined access policies, predetermined duplicate matching policies, and predetermined enterprise validation policies.
12. A system for master data management in a plurality of enterprise networks using a blockchain, the system comprising:
one or more memory units (303);
one or more processors (302) coupled to the one or more memory units (303), wherein the processor (302) is configured to:
-31-

SUNDARA RAJAN

GAVS Technologies Pvt. Ltd.

detect an event associated with a data entity of a master data (402), wherein the event is initiated by an enterprise network node (106) on a blockchain database (214) or an off-chain database (204);
validate the event based on predetermined validation rules;
initiate a transaction indicative of the event using one or more cryptographic keys if the event is valid;
add the initiated transaction to a blockchain ledger (212) based on a predetermined entity smart contract;
update metadata and attributes associated with the event on the blockchain database (214);
propagate the data entity to other participating enterprise network nodes (106); and
link the data entities of the master data based on the propagation.
13. The system of claim 12, wherein the off-chain database (204) is configured to perform duplicate matching and syntactic check on the data entity instance.
-32-