Distributed and blockchain-based student academic ledger systems and methods

A method comprising:

• receiving, by a blockchain network from an application, a first request that is digitally signed using a private key of a student member of the blockchain network, wherein the blockchain network includes a plurality of student members and institutional members, wherein the blockchain network is permissioned to restrict access to a distributed ledger, wherein the distributed ledger includes a set of student data associated with the student member that is replicated across a plurality of peer nodes;
• responsive to the first request that is digitally signed using the private key of the student member of the blockchain network, granting, by program code deployed on the blockchain network to a blockchain program associated with an institutional member of the blockchain network, a public key that pairs with the private key;
• receiving, from the blockchain program, a second request update the set of student data on the distributed ledger in the blockchain network;
• responsive to receiving the second request, verifying, by the blockchain network, the public key granted to the blockchain program;
• responsive to verifying the public key granted to the blockchain program, executing, by the blockchain network, at least one blockchain transaction to generate an updated set of student data in the distributed ledger;
• and
• enforcing, by the blockchain network, a consensus protocol between the plurality of peer nodes that prevents editing the updated set of student data using the private key, wherein enforcing the consensus protocol includes:
• denying, by the blockchain network, attempts to modify the updated set of student data using the private key and allowing modifications to the updated set of student data using the public key granted to the blockchain program.

A system comprising:

• one or more hardware processors;
• one or more non-transitory computer-readable media storing instructions, which, when executed by one or more hardware processors cause:
• receiving, by a blockchain network from an application, a first request that is digitally signed using a private key of a student member of the blockchain network, wherein the blockchain network includes a plurality of student members and institutional members, wherein the blockchain network is permissioned to restrict access to a distributed ledger, wherein the distributed ledger includes a set of student data associated with the student member that is replicated across a plurality of peer nodes;
• responsive to the first request that is digitally signed using the private key of the student member of the blockchain network, granting, by program code deployed on the blockchain network to a blockchain program associated with an institutional member of the blockchain network, a public key that pairs with the private key;
• receiving, from the blockchain program, a second request update the set of student data on the distributed ledger in the blockchain network;
• responsive to receiving the second request, verifying, by the blockchain network, the public key granted to the blockchain program;
• responsive to verifying the public key granted to the blockchain program, executing, by the blockchain network, at least one blockchain transaction to generate an updated set of student data in the distributed ledger;
• and
• enforcing, by the blockchain network, a consensus protocol between the plurality of peer nodes that prevents editing the updated set of student data using the private key, wherein enforcing the consensus protocol includes:
• denying, by the blockchain network, attempts to modify the updated set of student data using the private key and allowing modifications to the updated set of student data using the public key granted to the blockchain program.