Abstract: This disclosure enables a digital token with a set of asset-specific attributes, where the set of asset-specific attributes is modifiable or enabled to receive a new asset-specific attribute at least after the digital token with the set of asset-specific attributes is issued on a blockchain-based tokenization platform. Such functionality may be enabled via the digital token containing an attribute component with a set of key-value pairs populated with a subset of the set of asset-specific attributes, where the set of key-value pairs is programmed to be modified or have a new key-value pair being added thereto after the digital token is issued on the blockchain-based tokenization platform.

Abstract: Systems and methods described herein may generate a digital payment token associated with a payor-user indicating the status of a payment obligation of the payor-user. The systems and methods may generate a first block containing the digital payment token and append the first block to a blockchain. The systems and methods may receive a confirmation message from a third-party transaction server that the payor-user has either fully or partially fulfilled his or her payment obligation. Based upon the confirmation message, the systems and methods may retrieve the block containing the digital payment token and update the digital payment token to generate an updated digital payment token. The system and methods may generate a second block containing the updated digital payment token to supersede the first block and append the second block to the blockchain. The updated digital payment token may indicate that the digital payment token has expired.

Abstract: Systems and methods described herein may generate a digital payment token associated with a payor-user indicating the status of a payment obligation of the payor-user. The systems and methods may generate a first block containing the digital payment token and append the first block to a blockchain. The systems and methods may receive a confirmation message from a third-party transaction server that the payor-user has either fully or partially fulfilled his or her payment obligation. Based upon the confirmation message, the systems and methods may retrieve the block containing the digital payment token and update the digital payment token to generate an updated digital payment token. The system and methods may generate a second block containing the updated digital payment token to supersede the first block and append the second block to the blockchain. The updated digital payment token may indicate that the digital payment token has expired.

Abstract: Embodiments disclosed herein provide systems and methods for digital identity management and permission controls within distributed network nodes. A network node may receive a request to generate a new digital identity record for an entity. The network node may retrieve a template based on an entity type; and receive information, reference documents, and biometric information for the new digital identity record. The network node may associate and store the received information to the data fields in the new digital identity record, generate respective one directional cryptographic hashes of the reference documents and the biometric information, and store the hashes in the new digital identity record while storing the reference documents and biometric information in a non-blockchain repository. The network node may generate a digital identity record block for the new digital identity record, encrypt the digital identity record block, and append the encrypted block to the latest valid blockchain.

Abstract: Embodiments disclosed herein describe systems and methods for deploying a new code block on a blockchain. In an embodiment, an application server may provide a user with a graphical user interface (GUI) with contract components and document components. The application server may generate an assembled contract text based on the user selecting the contract and document components. The application server may determine the blockchain addresses or local addresses of smart contract components corresponding to the contract components and the documents components. The application server may generate a code block including references to the addresses of the smart contracts and the document components or containing the executable code itself and may deploy the code block to the latest valid blockchain. The application server may execute the smart contract in the code block based in response to a digital event trigger.

Abstract: Embodiments disclosed herein provide systems and methods for digital meeting management within a blockchain. Before a meeting, a computer may generate a digital meeting record containing a plurality of data fields and linked to various smart contracts to capture meeting activities. During the meeting, a first smart contract may authenticate and record attendees in the digital meeting record based on biometric information received from the attendees' devices. Furthermore, a second smart contract may capture in the digital meeting record, meeting actions of each attendee, including date, time, and location associated with the meeting actions. After the meeting, a third smart contract may autopopulate post meeting documentation. After review by the attendees, the third smart contract may store a hash of the documentation to the digital meeting record and store the documentation in a repository. Once appended to the blockchain, the digital meeting record becomes an immutable record of the meeting.

Abstract: Embodiments disclosed herein provide systems and methods for digital identity management and permission controls within distributed network nodes. A network node may receive a request to generate a new digital identity record for an entity. The network node may retrieve a template based on an entity type; and receive information, reference documents, and biometric information for the new digital identity record. The network node may associate and store the received information to the data fields in the new digital identity record, generate respective one directional cryptographic hashes of the reference documents and the biometric information, and store the hashes in the new digital identity record while storing the reference documents and biometric information in a non-blockchain repository. The network node may generate a digital identity record block for the new digital identity record, encrypt the digital identity record block, and append the encrypted block to the latest valid blockchain.

Abstract: Systems and methods described herein may generate a digital payment token associated with a payor-user indicating the status of a payment obligation of the payor-user. The systems and methods may generate a first block containing the digital payment token and append the first block to a blockchain. The systems and methods may receive a confirmation message from a third-party transaction server that the payor-user has either fully or partially fulfilled his or her payment obligation. Based upon the confirmation message, the systems and methods may retrieve the block containing the digital payment token and update the digital payment token to generate an updated digital payment token. The system and methods may generate a second block containing the updated digital payment token to supersede the first block and append the second block to the blockchain. The updated digital payment token may indicate that the digital payment token has expired.

Abstract: Embodiments disclosed herein describe systems and methods for deploying a new code block on a blockchain. In an embodiment, an application server may provide a user with a graphical user interface (GUI) with contract components and document components. The application server may generate an assembled contract text based on the user selecting the contract and document components. The application server may determine the blockchain addresses or local addresses of smart contract components corresponding to the contract components and the documents components. The application server may generate a code block including references to the addresses of the smart contracts and the document components or containing the executable code itself and may deploy the code block to the latest valid blockchain. The application server may execute the smart contract in the code block based in response to a digital event trigger.

Abstract: Systems and methods described herein may generate a digital payment token associated with a payor-user indicating the status of a payment obligation of the payor-user. The systems and methods may generate a first block containing the digital payment token and append the first block to a blockchain. The systems and methods may receive a confirmation message from a third-party transaction server that the payor-user has either fully or partially fulfilled his or her payment obligation. Based upon the confirmation message, the systems and methods may retrieve the block containing the digital payment token and update the digital payment token to generate an updated digital payment token. The system and methods may generate a second block containing the updated digital payment token to supersede the first block and append the second block to the blockchain. The updated digital payment token may indicate that the digital payment token has expired.

Abstract: Embodiments disclosed herein provide systems and methods for digital identity management and permission controls within distributed network nodes. A network node may receive a request to generate a new digital identity record for an entity. The network node may retrieve a template based on an entity type; and receive information, reference documents, and biometric information for the new digital identity record. The network node may associate and store the received information to the data fields in the new digital identity record, generate respective one directional cryptographic hashes of the reference documents and the biometric information, and store the hashes in the new digital identity record while storing the reference documents and biometric information in a non-blockchain repository. The network node may generate a digital identity record block for the new digital identity record, encrypt the digital identity record block, and append the encrypted block to the latest valid blockchain.

Abstract: Embodiments disclosed herein provide systems and methods for digital meeting management within a blockchain. Before a meeting, a computer may generate a digital meeting record containing a plurality of data fields and linked to various smart contracts to capture meeting activities. During the meeting, a first smart contract may authenticate and record attendees in the digital meeting record based on biometric information received from the attendees' devices. Furthermore, a second smart contract may capture in the digital meeting record, meeting actions of each attendee, including date, time, and location associated with the meeting actions. After the meeting, a third smart contract may autopopulate post meeting documentation. After review by the attendees, the third smart contract may store a hash of the documentation to the digital meeting record and store the documentation in a repository. Once appended to the blockchain, the digital meeting record becomes an immutable record of the meeting.