System and techniques for utilizing a smart contracts library

A non-transitory computer readable medium embodied with programming code that when executed by a processor causes the processor to perform functions, including functions to:

• access a smart contract library comprising a plurality of templates of different legal contracts implementable as a smart contract between respective parties in the smart contract, wherein:
• each template of the plurality of templates includes a plurality of sections having different contractual terms and conditions and fillable fields for specific contract terms, and
• each respective section of the plurality of sections includes programming code operable to enforce conformance with specific section-related contractual terms and conditions of the respective section and with any specific contract terms input to a fillable field of the respective section;
• receive a selection of a template of a smart contract from the plurality of templates for implementation as a finalized smart contract;
• generate the finalized smart contract having sections with specific contract terms and conditions and programming code operable to enforce conformance with the specific contract terms;
• obtain a private cryptographic key assigned to a first user of the contract-creating computing device, wherein the private cryptographic key is associated with a public cryptographic key;
• generate a first user address associated with the contract-creating computing device in a private blockchain, wherein the first user address is based on the private cryptographic key and is associated with the first user in the private blockchain;
• generate a smart contract address for the finalized smart contract using the first user address and a nonce value;
• generate a smart contract hash value using a value related to the programming code of the finalized smart contract as an input into a hash function;
• and
• store the smart contract hash value as a transaction in the private blockchain, wherein the transaction is associated with the smart contract hash value and the first user address in the private blockchain;
• receive a revision to the finalized smart contract made by a second party contract participating device;
• modify programming code of the finalized smart contract based on the received revision to the finalized smart contract;
• track revisions to the finalized smart contract;
• upon completion of the revisions to the finalized smart contract, generate a programming code hash using the modified programming code as an input to a programming code hash function;
• and
• store the programming code hash as part of a revision-related transaction to the private blockchain, wherein the revision-related transaction is associated with the smart contract address for the finalized smart contract, a second party contract participating device address, and the first user address in the private blockchain.