SYSTEMS AND METHODS OF BLOCKCHAIN PLATFORM FOR RULE-BASED DE-CENTRALIZED ROLES AND CONTROL

1 . A method on a blockchain platform, comprising:

de-centralizing a transaction on the blockchain by communicating separately with a miner for operation and a blobber for application;

inviting one or more rule-based actions to trigger the transaction from the miner or the blobber in response to a client request;

receiving an action from the miner or the blobber;

determining whether the action is one of the rule-based actions;

rewarding the rule-based action from the miner or the blobber;

discarding any action that is not rule-based;

committing the transaction after confirming authentication of all the entities and verifying data integrity for the transaction.

2 . The method of claim 1 , wherein the transaction involves lightning mode read request with direct response from the blobber; and requesting reward from the miner at the end of the transaction.

3 . The method of claim 1 , wherein verifying data integrity includes commitment of the same Merkle root or leaf of the same Merkle root by two separate computing entities.

4 . The method of claim 1 , wherein rewarding the rule-based action is based on a counter associated with the client and the blobber from the committed transaction.

5 . The method of claim 1 , further comprising:

receiving a challenge from one or more validators;

verifying the blobber or the miner action based on the verification response of the challenge;

self-regulating the transaction and the computing entities on the blockchain platform.

6 . The method of claim 5 , wherein the validator is a client.

7 . The method of claim 1 , wherein the transaction includes metadata for an associated application.

8 . The method of claim 7 , wherein the metadata includes metadata for a file system.

9 . The method of claim 7 , further comprising browsing the metadata for the associated application to lookup the transaction data.

10 . The method of claim 1 , further comprising:

receiving a request from the client to re-assign a blobber from the committed transaction;

committing a re-assigned transaction after confirming authentication of all computing entities and verifying data integrity for the transaction.

11 . A system on a blockchain platform, comprising:

a de-centralized transaction module on the blockchain by communicating separately with a miner for operation and a blobber for application;

an invitation module to invite one or more rule-based actions to trigger the transaction from the miner or the blobber in response to a client request;

a receiving module to receive an action from the miner or the blobber;

a determining module to determine whether the action is one of the rule-based actions;

a rewarding module to reward the rule-based action from the miner or the blobber;

a discarding module to discard any action that is not rule-based;

a commitment module to commit the transaction after confirming authentication of all the entities and verifying data integrity for the transaction.

12 . The system of claim 11 , wherein the transaction involves lightning mode read request with direct response from the blobber; and requesting reward from the miner at the end of the transaction.

13 . The system of claim 11 , wherein verifying data integrity includes commitment of the same Merkle root or leaf of the same Merkle root by two separate computing entities.

14 . The system of claim 11 , wherein rewarding the rule-based action is based on a counter associated with the client and the blobber from the committed transaction.

15 . The system of claim 11 , further comprising:

a receiving module to receive a challenge from one or more validators;

a verification module to verify the blobber or the miner action based on the verification response of the challenge;

a self-regulation module to self-regulate the transaction and the computing entities on the blockchain platform.

16 . The system of claim 15 , wherein the validator is a client.

17 . The system of claim 11 , wherein the transaction includes metadata for an associated application.

18 . The system of claim 17 , wherein the metadata includes metadata for a file system.

19 . The system of claim 17 , further comprising a module to browse the metadata for the associated application to lookup the transaction data.

20 . The system of claim 11 , further comprising:

a receive module to receive a request from the client to re-assign a blobber from the committed transaction;

a commitment module to commit a re-assigned transaction after confirming authentication of all computing entities and verifying data integrity for the transaction.