Using blockchain for electronic document signing

Abstract

The systems and methods of the present disclosure may allow for, for example, the uploading and signing of one or more electronic documents by multiple users or participants. Information about each transaction (e.g., uploading, signing, verification, etc.) performed by a user / participant related to the uploaded and signed document may further be generated and provided to one or more blocks in the blockchain. In addition, the electronic information of the uploaded and signed document may be shuffled and provided to one or more blocks in the blockchain. Thus, using embodiments of the present disclosure, an immutable transaction history may be provided for uploaded and electronically / digitally signed documents.

Description

Technical Field

[0001] The present disclosure relates to electronic document signing, and in particular to electronic document signing using blockchain technology. Background Art

[0002] Existing electronic document signing methods and platforms are often susceptible to fraud or tampering, and may not be able to provide participants with fast, efficient, and correct transaction confirmations or transaction histories. Therefore, there is a need for systems and methods for electronically or digitally signing and securely transmitting documents that provide tamper-proof document transaction histories available to all participants, increased security for better fraud prevention, and faster transmission confirmations. Summary of the invention

[0003] Briefly described, the present disclosure relates to systems and methods for digital or electronic document signing. The systems and methods of the present disclosure take into account, for example, the uploading and signing of one or more electronic documents by multiple users or participants. In addition, transaction details or information related to each transaction (e.g., uploading, signing, verification, etc.) performed by a user / participant related to the uploaded and signed documents can be further generated and provided to one or more blocks in the blockchain. The electronic information of the uploaded and signed documents can also be hashed, and the hash value can be provided to one or more blocks in the blockchain. This blockchain technology generally provides an environment that provides a high level of security, compliance, transparency and trust among participants by applying cryptography to ensure the security of transactions and making the transaction history immediately available to each participant. Therefore, using embodiments of the present disclosure, an immutable / tamper-proof transaction history for uploaded and electronically / digitally signed documents can be provided to all users / participants. In addition, embodiments of the present disclosure can provide a lightweight, fast and trusted document management platform with improved fraud prevention and security, as well as faster transmission confirmation, resulting in loss prevention and cost savings.

[0004] For example, the system or platform can facilitate electronic or digital signatures of document(s) by two or more participants. The participants can create account(s) through a website and / or application (such as a mobile application) that is part of or in communication with the system / platform (e.g., the participant can generate or select user credentials, such as a username and password, or other suitable verification information for logging into the website or application). One of the participants (e.g., the sender) can log into the website or application using their credentials and upload one or more documents (e.g., PDF, Word, etc.). ® The sender may further add or assign names or tags to the uploaded document(s) (eg, in a text field on a website or smartphone application).

[0005] In addition, the system generates a hash for the uploaded document(s). In one variation, the system may apply a cryptographic hash function (e.g., SHA256 or RIPEMD function) to the electronic information of the uploaded document(s), e.g., the system / platform may take an input as the electronic information of the document(s) and apply a hash function to convert any input length to an output of a fixed length, e.g., a hash value of a fixed length. The sender may also electronically or digitally sign or otherwise provide their digital or electronic signature information to the uploaded document(s) (e.g., electronically sign with their initials, electronically sign with a sketch, or otherwise generate digital or electronic signature information). Details of the transaction information or digital signature information may be stored in one or more blocks of the blockchain, and the transaction information / details may include document hashes, date and time, participant information (e.g., verified email IDs), or other suitable information.

[0006] The sender may also send signature requests to additional participants or recipients (e.g., via email, text message, or other appropriate notification means). Additional participants or recipients may also register with the website / application in order to sign the uploaded document (e.g., the other participants may generate or select credentials, such as a username and password, or other suitable verification information for logging into the website or application). The additional participants or recipients may then download the uploaded document and provide their digital or electronic signature information to the document(s). Details of the digital signature information of the other participants or recipients or transaction information may also be stored in one or more blocks of the blockchain (e.g., document hashes, date and time, participant information, such as verified email IDs, etc.).

[0007] Additionally, the recipient can return (one or more) signed documents to the sender. The sender can then verify the signed document and complete the transaction. The document files can be stored on file storage platforms such as InterPlanetary File System (IPFS), Amazon ® Participants can also see an immutable transaction history of uploaded and signed documents in the blockchain.

[0008] In some variations, a system for electronic document signing may have one or more processors in communication with a plurality of devices, each of which is managed by a user or participant. The processor(s) further communicate with a memory storing instructions. The processor(s) accesses a document from a first device managed by a first user among a plurality of users, and also receives signature information of the first user from the first device. The processor(s) associates the signature information with the document to form a signed document. The processor(s) also generates transaction information related to the signature information received from the first device, and provides the transaction information to a current block of a blockchain. In some variations, the transaction information may include a transaction type, participant information, a status of the document, time and date information, or any other suitable information or combination thereof. The processor(s) also generates a hash of the signed document and provides the hash of the signed document to the current block in the blockchain. For example, the processor(s) are configured to apply a hash function to the electronic data or information of the signed document. The signed document may be provided to and stored in a storage device (such as a cloud-based storage device or other suitable memory or storage device).

[0009] In addition, the processor(s) provide the signed document to a second device managed by a second user of the plurality of users, and receive additional signature information of the second user from the second device (e.g., when the second user provides their digital signature information for signing the document). The additional signature information may be associated with the signed document to form an updated signed document. The processor(s) also generates additional transaction information related to the received additional signature information of the second user, and provides the additional transaction information to the current block of the blockchain. The processor(s) further generates a hash of the updated signed document (e.g., the processor(s) are configured to apply a hash function to the electronic data or information of the updated signed document), and provides the hash of the updated signed document to the current block of the blockchain.

[0010] In addition, the processor(s) are configured to provide the updated signed document to a first device managed by the first user and receive verification information from the first user that the updated signed document was received or signed. The processor(s) then provide the verification information from the first user to the current block in the blockchain.

[0011] Still further, the processor(s) may be configured to display information associated with the blockchain to provide a transaction history of documents, signed documents, and updated signed documents.

[0012] In another variation, a method may include receiving a document from a first device managed by a first user among a plurality of users, and receiving signature information, such as an electronic signature or other digital signature information, from the first user using the first device. The signature information may be associated with the document to form a signed document.

[0013] Transaction information related to the signature information received from the first user may also be generated. The transaction information may be provided to the current block of the blockchain. In one example, the transaction information may include a transaction type, user information, a status of a document, time or date information, or any other suitable information or combination thereof.

[0014] A hash of the signed document may also be generated, and the hash value may be provided to the current block of the blockchain. The hash of the signed document may be generated by applying a cryptographic hash function to the electronic data or information of the signed document (e.g., generating a hash value of a fixed length). The signed document may also be provided to and stored in a storage device (such as a cloud-based storage platform or other suitable file storage platform).

[0015] In addition, the method may include providing the signed document to a second device managed by a second user of the plurality of users (e.g., upon receiving a request from the second user to access the document and sign it). Additional signature information from the second user may further be received from the second device, and the additional signature information may be associated with the signed document to form an updated signed document.

[0016] In addition, additional transaction information related to the received additional signature information can be generated and provided to the current block of the blockchain. A hash of the updated signed document can also be generated and provided to the current block of the blockchain (e.g., by applying a cryptographic hash function to the electronic data or information of the updated signed document).

[0017] The method may also include providing the updated signed document to a first device managed by the first user and receiving verification information from the first user (e.g., when the first user verifies that the second user or (one or more) other users have properly signed the updated signed document). The verification information may also be provided to the current block in the blockchain.

[0018] Additionally, the method may include displaying information contained in or associated with the blockchain to provide a transaction history of the document, the signed document, or an updated signed document.

[0019]

[0011] Various objects, features and advantages of the present disclosure will become apparent to those skilled in the art when reviewing the following detailed description in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] It should be understood that for simplicity and clarity of illustration, the elements shown in the drawings are not necessarily drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements. Embodiments incorporating the teachings of the present disclosure are shown and described with respect to the drawings herein, in which:

[0021] Figure 1 A schematic diagram of a system or platform for electronic or digital document signing using blockchain is shown.

[0022] Figure 2 A flow chart illustrating the use of blockchain for electronic or digital document signing.

[0023] Figure 3 A block diagram illustrating a process for electronic or digital document signing using blockchain.

[0024] Figure 4 A flow chart illustrating a process for electronic or digital document signing using blockchain.

[0025] Figures 5A-5F An exemplary screenshot of a platform for electronic or digital document signing using blockchain is shown.

[0026] The use of the same reference symbols in different drawings indicates similar or identical items. DETAILED DESCRIPTION

[0027] The following description in conjunction with the accompanying drawings is provided to assist in understanding the teachings disclosed herein. Although the description discloses various embodiments and examples of the present teachings, and the description is provided to assist in describing the present teachings, the embodiments, features, and embodiments discussed herein should not be interpreted as limiting the scope or applicability of the present teachings.

[0028] Figure 1 A schematic diagram of a system 10 for electronic or digital document signing using blockchain is shown. The system 10 may include one or more computer-implemented products or platforms, such as a document management provider 12 (e.g., including a software product, a mobile application, a web-based application, etc.) to facilitate uploading documents (e.g., portable document files (PDF), Microsoft ®The document management provider 12 further facilitates the generation of transaction information (e.g., when a user / participant uploads a document, signs a document, or verifies a document) and the generation of a hash of the document to be provided in a block of the blockchain 18, for example, so that an immutable transaction history of the uploaded and signed document can be made available to the users / participants of the system. The document can further be stored using a cloud-based storage / computing platform 20 (such as using the InterPlanetary File System (IPFS), Amazon Web Services (AWS), or other cloud-based storage / computing platforms). ® Web Services (AWS) or other suitable web- or cloud-based systems or platforms) to store, share or access.

[0029] In some variations, the system or platform 10 can facilitate two or more participants or users to sign one or more documents. Participants can access a document management provider user two-factor authentication or other multi-factor authentication. For example, a participant can create (one or more) accounts for accessing the document management provider 12 (e.g., the participant can generate or select user credentials, such as a username and password, or other suitable verification information for logging into a website or application associated with the document management provider 12 using a managed device 16). One of the participants (e.g., the sender) can access the document management provider 12 using its credentials (e.g., by logging in), and then the sender can upload one or more documents (e.g., PDF, Word ® The sender may also add or assign names or labels to the uploaded document(s) (e.g., in a text field on a website or application).

[0030] The system 10 or document management provider 12 may generate a hash for the uploaded document(s). In one variation, the system 10 or document management provider 12 may apply a cryptographic hash function (e.g., SHA256 or RIPEMD function) to the electronic information of the uploaded document(s), e.g., the system / platform may take as input the electronic information of the document(s) and apply a hash function to convert any input length into a fixed-length output, e.g., a fixed-length hash value.

[0031] In addition, the sender may electronically sign, digitally sign, or otherwise provide their digital or electronic signature information to the uploaded document(s) (e.g., electronically sign with initials, electronically sign with a sketch, or otherwise generate digital or electronic signature information). Details of the transaction information or digital signature information are generated and stored in one or more blocks of the blockchain 18. The transaction information / details may include document hashes, date and time, participant information such as verified email IDs, or any other suitable transaction details or information, or combinations thereof.

[0032] The sender may then send a signature request to the additional participants or recipients (e.g., via email, text message, or another suitable messaging mechanism or notification means). To sign the uploaded document, the additional participants or recipients may also register with the website / application (e.g., the other participants may generate or select credentials, such as a username and password, or other suitable verification information for logging into the website or application using managed device 16) to be able to sign or log in.

[0033] When signing / logging in, the additional participants or recipients can download the uploaded and signed documents, and then, can provide their digital or electronic signature information to the (one or more) documents. Details of the transaction information or the digital signature information of the additional participants or recipients can also be stored in one or more blocks of the blockchain 18 (e.g., document hashes, date and time, participant information, such as verified email IDs, etc.). The recipient can further send the (one or more) signed documents back to the sender, and the sender can verify and complete the transaction. Participants (e.g., senders, recipients, or other participants) will therefore be able to see the immutable transaction history of the uploaded and signed documents in the blockchain.

[0034] Figure 1It is further shown that the document management provider 12 or other computer-implemented product can reside on or otherwise be accessed by a device 16 managed by a user or participant. The user-managed device 16 may include a handheld mobile device, such as a mobile phone, smart phone, tablet computer, PDA, or other suitable mobile computing device. Additionally or in the alternative, the user-managed device 16 may include a personal computing device, such as a laptop computer, desktop computer, workstation, etc., but any suitable computing device may be used without departing from the present disclosure. The device 16 accessing or running the document management provider 12 may also be configured to access one or more networks 22, such as the Internet, a peer-to-peer network, or any other suitable private or public network or combination thereof, to enable users / participants to upload, access documents and provide their signature information to the documents. The device 16 can be connected via a wired connection (e.g., an Ethernet cable) or a wireless connection (e.g., WiFi, Bluetooth ® , cellular connection (e.g., 3G, 4G, LTE, 5G, etc.), or a combination thereof to access the network.

[0035] Each managed device 16 may further include at least one processor, such as a central processing unit (CPU) or hardware or software control logic, ROM and / or other types of non-volatile memory, and at least one storage device or memory, such as random access memory (RAM) or (ROM). The managed device 16 may further include one or more ports for communicating with external devices and various input and output (I / O) devices (such as a keyboard, mouse, touch screen and / or video display). However, the managed device 16 may include any suitable computing component that is operable to estimate, calculate, determine, classify, process, transmit, receive, retrieve, initiate, switch, store, display, communicate, indicate, detect, record, reproduce, process or utilize any form of information or data for any suitable purpose.

[0036] One or more components of the document management provider 12 may be stored in memory and executed or otherwise accessed by the processor(s) of the managed device 16. Additionally or alternatively, however, one or more components of the document management provider 12 may be stored and / or accessed from other computing devices (e.g., having a processor and memory and / or storage) in communication with the device 16. For example, one or more components of the document management provider 12 may be web-based or cloud-based and accessed and stored from one or more memories or storage of a computing device (such as a server) that is part of a data management center managed by a web or cloud service provider or other suitable entity.

[0037] Figure 2A flow chart 100 is shown for electronic document signing using a blockchain by multiple participants or users. Figure 2 As shown in , at 102, a participant (e.g., a sender) can access a document management provider 12 by logging into a website or mobile application (e.g., by entering or otherwise providing credentials or other suitable authorization information). After the sender has accessed the website / mobile application, the sender can upload one or more documents for receiving digital or electronic signature information (at 104). At 104, the sender can also (if necessary) sign the uploaded document(s) (e.g., by providing their digital signature or electronic signature information thereto).

[0038] Thereafter, at 106, the document(s) are sent or otherwise provided to other additional participants (or recipients) for receiving their verification or signature information. At 108, it may be determined whether the sender successfully uploaded, signed, or verified the document(s) (e.g., it may be determined whether the document or signature information is correctly formatted or whether the participant or sender 101 properly verified the document). If a success is determined at 108, transaction details or information related to the uploading, signing, or verification of the document(s) are generated and provided to one or more blocks in the blockchain 18 (at 110). Additionally, if a success is determined at 108, the document(s) are provided to a cloud-based file storage platform 20 (e.g., IPFS or AWS S3).

[0039] If it is determined at 108 that the document(s) were not successfully uploaded, signed, or verified, the sender may be prompted to correctly upload the document(s), sign the document(s), or verify the document(s), and steps / actions 104 to 110 may be repeated.

[0040] Figure 2 As further shown, at 114, additional participants or recipients may log into the website or mobile application (e.g., using their user credentials or other suitable verification information) to access and sign the uploaded documents. When the recipient has logged in, the recipient may, for example, access the uploaded document(s) at 116 (e.g., the document(s) may be accessed or received from the cloud-based storage device 20), and further, at 116, the recipient may provide their electronic or digital signature information to the document(s).

[0041] Subsequently, at 118, a determination may be made as to whether the recipient successfully accessed or signed the document(s). If not, the recipient is prompted to correctly sign or verify the document(s). However, if it is determined that the document(s) have been successfully accessed and signed, transaction details or information related to the signing of the document(s) are generated and provided to one or more blocks in the blockchain 18 (e.g., at 120).

[0042] It will be further understood that the following may be omitted or rearranged without departing from the scope of the present disclosure. Figure 2 Any of the steps or actions 102 to 120 shown in . Additional actions or steps may also be included, and for example, when all required participants have accessed the document(s) and signed the document(s), the document(s) may be provided to the sender for verification, and transaction details or information related to the verification may be provided to one or more blocks in the blockchain 18.

[0043] Figure 3 A block diagram of a method or process 200 for electronic or digital document signing using blockchain is shown. Figure 3 As shown in , a participant or sender may provide a request to launch or initiate a document management provider, e.g., a user may launch and access (e.g., using two-factor authentication) a website or mobile application associated with a document management provider at 202. At 204, the document management provider is launched or initiated, and at 206, the sender may log into the document management provider's website or mobile application, e.g., by entering user credentials or other suitable authentication information.

[0044] Then, at 208 , the document management provider generates and sends a request for the sender to upload and sign the document(s), and at 210 , the sender may upload and sign the document(s).

[0045] When the document has been uploaded and signed, the document management provider takes one or more actions (at 212). For example, at 214, each time the sender uploads a document and / or signs a document, the document management provider creates a transaction, e.g., including creation transaction information. In addition, when the transaction is created, the uploaded and signed document(s) are provided to and stored in a cloud-based file storage platform 20 (e.g., AWS S3 or IPFS) (at 216). The document management provider also notifies the sender (or other participants) that the transaction(s) have occurred / have been created (at 218). In one variation, the document management provider provides a notification that the document(s) have been uploaded or signed by the sender. In addition, at 220, the document management provider provides the transaction information to a block 32 in the blockchain.

[0046] like Figure 3 As shown in block 32 of , the transaction information may include a transaction ID, a transaction type, a participant identifier, status information (e.g., an indication of whether an additional participant has accessed and signed the uploaded document), and a timestamp (e.g., including the time and date when the transaction was created). In one variation, the transaction ID may include a hash of the uploaded and signed document(s) (e.g., by applying a cryptographic hash function to the electronic data or information of the provided document(s)).

[0047] An additional participant or recipient may provide a request to access a website or mobile application at 222 (eg, the recipient may launch or initiate and log into the document management provider's website or mobile application).

[0048] When logged into the website / mobile application, the participant or recipient may access and sign the uploaded document(s) at 226 , retrieve or otherwise access the uploaded document(s) from cloud-based storage 20 (at 224 ).

[0049] When the recipient has accessed and signed the uploaded document(s) at 226, the document management provider takes one or more actions at 228. For example, the document management provider creates a transaction at 230, e.g., the document management provider may create transaction information. Upon creating the transaction, the document management provider may notify the recipient or sender at 232.

[0050] Additionally, at 234, the document management provider stores the transaction information in block 34 of the blockchain 18. In one variation, the transaction information may include a transaction ID, a transaction type, a participant identifier, status information (e.g., indicating whether all attached participants have accessed and signed the uploaded document), and a timestamp (e.g., including the time and date when the transaction was created). The transaction ID may include a hash of the uploaded and signed document(s) (e.g., generated by applying a cryptographic hash function to the electronic data or information of the document(s) including the recipient's digital signature information).

[0051] It will be further understood that without departing from the scope of the present disclosure, Figure 3 Any of the actions / steps 202 to 234 shown in FIG. 2 may be rearranged or omitted, and additional steps / actions may be added.

[0052] Figure 4 A block diagram of a method or process 300 for electronic document signing using blockchain is shown. Figure 4 As shown in , at 302, the method or process 300 includes receiving (one or more) documents from a first device managed by a first user among multiple users. The method or process 300 also includes receiving electronic signature information of the first user from the first device, and associating the signature information with the document to form a signed document (at 304).

[0053] Thereafter, at 306, transaction information related to the signature information received from the first user is generated and provided to the block of the current blockchain. At 308, a hash of the signed document is generated and the hash value is provided to the current block in the blockchain. Additionally, at 308, the signed document is provided or otherwise received at a document storage device such as a cloud-based storage platform or other suitable storage device.

[0054] like Figure 4 As further shown in , at 310, the signed document is provided to a second device managed by a second user of the plurality of users. At 312, additional signature information of the second user is received from the second device, and the additional signature information is associated with the signed document to form an updated signed document.

[0055] Subsequently, the method 300 includes generating additional transaction information related to the received additional signature information of the second user and providing the additional transaction information to the block of the blockchain (at 314). In addition, at 316, a hash of the updated signed document is generated and the hash value is provided to the block of the blockchain.

[0056] At 318, the updated signed document is provided to a first device managed by the first user, and verification information is received from the first user (e.g., the first user can verify that the updated and signed document has been properly signed by all required users of the plurality of users). The verification information from the first user is further provided to a block in the blockchain.

[0057] Without departing from the scope of this disclosure, Figure 4 Any of the steps or actions 302 to 318 shown in FIG. 3 may be omitted or rearranged.

[0058] Additional steps or actions may be included. For example, the method may further include displaying information related to or in the blockchain to provide a transaction history of the document. In addition, the method may include providing the updated signed document to a first device managed by the first user, and receiving verification information from the first user. The verification information from the first user may also be further provided to the current block in the blockchain.

[0059] Figures 5A-5F Example screens are shown of a document management provider 12 facilitating electronic or digital document signing using blockchain, which may be displayed on a display 40 of a device 16 managed by a user. Figure 5A A login screen 400 of the document management provider 12 is shown (eg, which may be displayed or provided when a participant launches or otherwise accesses the document management provider).

[0060] like Figure 5A As shown in , the login screen 400 may require multi-factor authentication and has one or more text fields or input areas 402, 404 for the user / participant to enter or otherwise provide login credentials or other authentication information. For example, the login screen 400 may have: at least two input items 402 and 404 for the participant to enter an email address and a password, respectively; and at least one selectable icon or area 406, which can be selected / activated by the participant / user (e.g., using their login credentials) to log in or register with the document management provider 12.

[0061] Figure 5B An example document upload and signature screen 408 is shown for a participant (eg, sender) to upload and sign a document. When a participant logs in or registers to the login screen 400, the document upload and signature screen 408 may be shown. Figure 5BAs shown in , screen 408 provides an optional icon or area 410 that can be selected or activated to allow the sender to browse and select document files (e.g., ".pdf" documents, ".doc" documents, ".docx" documents, ".tiff" documents, ".rtf" documents, ".odt" documents, etc.) to be uploaded to the document management provider. However, any suitable means for accessing, selecting, or uploading documents may be used without departing from the scope of the present disclosure. For example, in some variations, screen 408 may include a field or area in which a document icon may be selected and dragged for its upload.

[0062] Figure 5B Screen 408 is further shown to further provide an optional field or area 414 that allows the participant to enter or otherwise provide electronic or digital signature information to the uploaded document. For example, in some variations, the participant can use an input terminal (e.g., a mouse, touch screen, etc.) of their managed device 16 to write, type, or otherwise create their digital signature or electronic signature information. Additionally or in the alternative, the participant can also upload or otherwise provide their electronic signature information (e.g., a digital image of their initials or signature or other suitable electronic or digital signature information), such as by selecting or activating one or more icons or areas 414.

[0063] In addition, the document upload and signature screen 408 may also include additional icons / selectable areas 416, 417, 418, and 419 corresponding to different functions of the document management provider. For example, a participant may select or activate one or more icons / areas 416 to switch to or move through various areas of a document requiring signature information, or to switch to or select various uploaded documents to provide signature information therefor. A participant may also select or activate icon / area 417 to save signature information entered, typed in, or otherwise provided.

[0064] Additionally, the participant may select or activate one or more icons 418 to confirm the placement of their signature, and may also select icon / area 419 to cancel the document upload and signature screen. Upon receiving the document or signature information in the document upload and signature screen 408, the platform may generate a hash of the uploaded document, create a transaction and transaction information, and provide the hash and transaction information to one or more blocks in the blockchain.

[0065] Figure 5C An exemplary status screen 420 is shown that provides details of participant information or the status of the current transaction, which may represent information retrieved from the blockchain, for example. When a participant (e.g., a sender) confirms the upload and signature of the document in screen 410 (e.g., by selecting Figure 5B 418 in the transaction), a status screen 420 may be shown. In one variation, the status screen 420 may include a list, table, or other grouping 422 of transaction information / details, including, for example, a transaction ID or other identifier for the transaction, a document hash, the name of the document, any comments on the document (e.g., which may be entered / typed by the sender), the status of the document, the owner ID of the document, the moderator ID of the document, any pending actions on the document (e.g., indicating whether the transaction is "completed" and all required participants have accessed and signed the uploaded document(s), or whether the document management provider is still "waiting" for all participants to access and sign the document). The status screen 420 may also include: one or more selectable icons or areas 424, which may be selected to perform the actions of the listed transactions (e.g., to sign or verify the uploaded documents); and one or more selectable icons / areas 426, which allow participants to download the transaction details / information. Additionally, the status screen 420 may include one or more selectable icons / areas 428 that may be selected / activated to create additional transactions (eg, upload a document, sign a document, or verify a document).

[0066] Figure 5D A screenshot of a signature screen 430 is shown that allows other or additional participants (e.g., recipients) to access and sign an uploaded document. Participants may access the signature screen 430 after providing two-factor authentication, such as by entering login credentials or other authentication information in the login screen 400 displayed on their device. Figure 5D As shown in , the signature screen 430 includes an optional field or area 432 for the participant to provide their electronic or digital signature information (eg, the participant may use an input of their managed device 16 to generate a digital signature, or may otherwise provide signature information to the uploaded document).

[0067] Additionally or in the alternative, a participant may select or activate an area or icon 434 to upload or otherwise provide their electronic signature information (e.g., a digital image of their initials or signature or other suitable electronic or digital signature information). Each time an additional participant accesses the provided signature information or uploaded document in the signature screen 430, a transaction and transaction information may be generated by the platform and provided to one or more blocks in the blockchain.

[0068] The signature screen 430 may also include additional icons / selectable areas 436, 438 corresponding to different functions of the document management provider. For example, the signature screen 430 may have one or more selectable areas or icons 436 that allow the participant to select, switch, or move between different parts of the document or between different documents that require signature information. The signature screen 430 may further include selectable areas or icons that the recipient may select / activate to save the entered, entered, or otherwise provided signature information.

[0069] The signature screen 430 may also provide a list or grouping 439 of document or transaction information or details, such as a keyword or hash value of the document, the name of the document, comments on the document, the status of the document, the owner of the document, the document arbitrators, etc. In one variation, the list or grouping of document or transaction information / details may include an optional text field that allows the recipient or other participant to edit or enter the document or transaction information or details.

[0070] Figure 5E A status screen 440 is shown (e.g., which may be displayed while participants / recipients provide their signature information to the uploaded document(s). Figure 5E As shown in , the status screen 420 may include a list, table, or other grouping 442 of transaction information / details that may be retrieved from the blockchain, including, for example, a transaction ID or other identifier of the transaction, a document hash, a document name, comments on the document (e.g., which may be entered / entered by a recipient or other participant), the status of the document, the owner ID of the document, the arbitrator ID of the document, any pending actions on the document (e.g., indicating whether the recipient's signature information has been "accepted"). The status screen 440 may also include: one or more selectable icons or areas 444, which may be selected or activated to perform the actions of the listed transactions (e.g., to sign an uploaded document or verify an uploaded document); and one or more selectable icons / areas 446, which allow for a participant to download transaction details / information.

[0071] Fig. 5FA document / transaction details screen 450 is shown that provides document or transaction details, statistics, etc. In one variation, screen 450 provides a graphic or image 452 showing ledger stats, information about signed documents, information about transactions, which may be generated based at least in part on information retrieved from the blockchain. Screen 450 may further include additional information / details about the transaction included in the blockchain, such as a document ID, a name of the document, a current status of the document, a sender of the document, a recipient of the document, and a timestamp. The document details may also provide an optional area or icon 454 that may be selected / activated to show specific details of the document. The transaction information / details may be related to or include information in the blockchain.

[0072] The foregoing description generally illustrates and describes various embodiments of the present disclosure. However, it will be understood by those skilled in the art that, without departing from the spirit and scope of the present disclosure as disclosed herein, various changes and modifications may be made to the structures discussed above of the present disclosure, and it is intended that all contents contained in the above description or shown in the accompanying drawings be interpreted as illustrative and should not be considered in a limiting sense. In addition, the scope of the present disclosure should be interpreted as covering the above-described embodiments and various modifications, combinations, additions, changes, etc., which should be considered within the scope of the present disclosure. Therefore, the various features and characteristics of the present disclosure as discussed herein may be selectively interchanged and applied to other illustrated and unillustrated embodiments of the present disclosure, and many variations, modifications and additions may be further made thereto without departing from the spirit and scope of the present invention as set forth in the appended claims.

Claims

1. A method for signing an electronic document, comprising: receiving a document from a first device managed by a first user among a plurality of users; generating a first hash of the document, and providing the first hash of the document in a block of the blockchain; receiving first signature information of the first user from the first device; forming a signed document by associating the first signature information with the document; generating first transaction information related to the first signature information received from the first device managed by the first user, and providing the first transaction information to a block of the blockchain; generating a second hash of the signed document, providing the second hash of the signed document in a block of the blockchain, and storing the signed document in a storage device; providing the signed document to a second device managed by a second user of the plurality of users; And then receiving additional signature information of the second user from the second device; forming an updated signed document by associating the additional signature information with the signed document; generating additional transaction information related to the received additional signature information of the second user, and providing the additional transaction information to a block of the blockchain; generating a third hash of the updated signed document, and providing the third hash of the updated signed document to a block of the blockchain; providing the updated signed document to the first device managed by the first user; receiving, by a document management provider, verification information from the first user via a selectable icon presented to the first user, the verification information verifying that the updated signed document has been correctly signed; and The verification information from the first user is provided to a block in the blockchain.

2. The method of claim 1 , further comprising displaying the blockchain to provide a transaction history of the document, the signed document, and the updated signed document.

3. The method according to claim 1, wherein the first transaction information or the additional transaction information comprises a transaction type, user information, a status of the document, and time or date information. The method of claim 1 , wherein the storage device comprises a cloud-based storage platform.

5. The method according to claim 1, wherein the first signature information or the additional signature information comprises electronic or digital signature information.

6. A method according to claim 1, wherein generating a first hash of the document, or generating a second hash of the signed document, or generating a third hash of the updated signed document includes applying a hash function to electronic data of the document, the signed document, or the updated signed document.

7. The method of claim 6, wherein the hash function comprises a SHA256 or RIPEMD function.

8. A system for electronic document signing, comprising: a processor in communication with a plurality of devices each managed by a user and in communication with a memory storing instructions causing the processor to: accessing a document from a first device managed by a first user of the plurality of users; generating a first hash of the document, and providing the first hash of the document in a block of the blockchain; receiving first signature information of the first user from the first device, and associating the first signature information with the document to form a signed document; generating first transaction information related to the first signature information received from the first device managed by the first user, and providing the first transaction information to a block of the blockchain; generating a second hash of the signed document, providing the second hash of the signed document in a second block, and storing the signed document in a storage device; providing the signed document to a second device managed by a second user of the plurality of users; receiving additional signature information of the second user from the second device, and associating the additional signature information with the signed document to form an updated signed document; generating additional transaction information related to the received additional signature information of the second user, and providing the additional transaction information to a block of the blockchain; generating a third hash of the updated signed document, and providing the third hash of the updated signed document to a block of the blockchain; providing the updated signed document to the first device managed by the first user; receiving, by a document management provider, verification information from the first user via a selectable icon presented to the first user, the verification information verifying that the updated signed document has been correctly signed; as well as The verification information from the first user is provided to a block in the blockchain.

9. The system of claim 8, wherein the processor is further configured to display the blockchain to provide a transaction history of the document, the signed document, and the updated signed document.

10. The system of claim 8, wherein the first transaction information and the additional transaction information include transaction type, participant information, status of the document, and time and date information.

11. The system of claim 8, wherein the storage device comprises a cloud-based storage device.

12. The system of claim 8, wherein the first signature information from the first user or the signature information from the second user comprises an electronic signature or a digital signature.

13. The system of claim 8, wherein the processor is further configured to apply a hash function to the electronic data of the document, the signed document, or the updated signed document.

14. The system of claim 13, wherein the hash function comprises a SHA256 or RIPEMD function.

15. The system of claim 8, wherein a website or mobile application accessed by the plurality of users using two-factor authentication is included in the system.

16. A method for signing an electronic document, comprising: displaying a login screen on a display of a first device managed by a first user among the plurality of users; upon receiving authentication information from the first user in one or more input items in the login screen displayed on the display of the first device, displaying a document upload and signature screen on the display of the first device; receiving a document from the first user via the document upload and signature screen; generating transaction details associated with said receipt of said document, generating a hash of said document, and providing said transaction details and said hash of said document to a block of a blockchain; displaying a login screen on a display of a second device managed by a second user of the plurality of users; upon receiving authentication information from the second user in one or more input items in the login screen displayed on the display of the second device, displaying a signature screen on the display of the second device, the signature screen including one or more input items for receiving signature information from the second user; as well as Upon receiving the signature information from the second user, additional transaction information related to the received signature information of the second user is generated, and the additional transaction information is provided to a block of the blockchain.

Images