Patent Description:
In this document, the term 'blockchain' is used to include all forms of electronic, computer-based, distributed ledgers. These include consensus-based blockchain and transaction-chain technologies, permissioned and un-permissioned ledgers, shared ledgers, and variations thereof. A widely known application of blockchain technology is the Bitcoin ledger, although other blockchain implementations have been proposed and developed. While Bitcoin may, in some examples, be referred to herein for the purpose of convenience and illustration only, it should be noted that the present application is not limited to use with the Bitcoin blockchain. Alternative blockchain implementations and protocols fall within the scope of the present application. The term "Bitcoin" is used herein to include all variations and versions deriving from or based upon the Bitcoin protocol. The abbreviation "BTC" may be used for convenience of reference only.

A blockchain is a peer-to-peer, electronic ledger which is implemented as a computer-based decentralized system made up of blocks which in turn are made up of transactions. Each transaction is a data structure that encodes the transfer of control of a digital asset between addresses in the blockchain system, and includes at least one transaction input and at least one transaction output. Each block contains a hash of the previous block so that blocks become chained together to create a permanent, unalterable record of all transactions which have been written to the blockchain since its inception.

The concept of decentralization is fundamental to the blockchain system. Decentralized systems provide the advantage that, unlike distributed or centralized systems, there is no single point of failure. Therefore, decentralized systems offer an enhanced level of security and resilience. The security is further enhanced by the use of known cryptographic techniques such as Elliptic Curve Cryptography and ECDSA.

Ownership and control over a digital asset or resource in a blockchain system is controlled through public-private key pairs. The digital asset or resource can be a token. The token can be representative of any type of entity. This could include currency, hard assets, soft assets, computing resources, or any other entity or service. For ease of reference, we may use the term "asset". An unspent transaction output (UXTO) address is akin to a public key, and control over the asset allocated to that UXTO address is evinced by use of the corresponding private key. To transfer the digital asset by using the UXTO as an input to another transaction, the input must be digitally signed by the corresponding private key. Accordingly, control over the security and secrecy of private keys is fundamental to the security and reliability of the blockchain.

One type of digital asset can include, for example, electronic documents. However, the invention is not limited to use in respect of documents, and access control, security and/or integrity preservation of other types of digital resource also fall within the scope of the invention. For example, software is often distributed over computing networks. The distribution, storage and handling of that software needs to be performed in a secure manner, wherein access is controlled and unauthorised access or alteration is prevented. The state and integrity of the software needs to be ensured, and verifiable as unaltered. However for convenience only, we may refer to electronic documents as a convenient illustration.

In some situations, multiple nodes may submit documents in a situation in which the substance of the documents is to remain confidential until all documents are revealed, and in which post-submission alterations to the documents is prevented. Thus, access to the data must be appropriately controlled, as well as processing or manipulation of that data. Paper-based submission processes would have relied on enclosing the documents in a sealed envelope and opening the envelopes after submissions are received from all participants. All such systems are now implemented using computer networks and documents are provided in electronic form, making the sealing of such documents and preventing their alteration very difficult. There is a significant risk that a submitted electronic document may be revealed or accessed improperly and the integrity of the document or the submission process may be impugned. The processes require trust in the manager or principal that oversees and implements the submission system, and trust in the technical security of the computer system for receiving and storing the documents. This is not ideal, as security breaches and unauthorised access of data, and possibly its alteration as well, are numerous and well known.

For example only, and without limitation of the invention, an electronic document may be submitted as part of a tender procurement process in a competitive bidding situation. To preserve the integrity of the process, it is fundamental that no bidder is able to access another bidder's material prior to the end of the submission period and that no bid is altered after submission. Accordingly, bidders need to rely on the honesty and integrity of the party seeking the bids, and the security of any computing system used for bid submission and storage.

In another purely illustrative example, documents may be submitted as part of a real estate purchase process, such as an offer and acceptance process involving multiple offeree parties. Existing real estate offer and acceptance processes typically rely on a real estate broker to maintain integrity and security of the offer and acceptance process, ensuring that respective offerees are not privy to details of another offeree's offer. Offers may be received via facsimile or via electronic mail; however, existing devices and systems rely on the integrity of a real estate broker for maintaining the security of the offer documents and for revealing the offer documents only after all offerees have provided an offer document.

In another example, documents may be submitted as part of a testing process, like the submission of examination papers or essays for marking. The contents of the papers should not be made available to anyone until all papers are submitted to prevent copying; and no alteration of submitted papers should be possible.

Other example situations may also be enabled through providing for a method and system that ensures submitted documents remain secured and confidential until all submissions are received, and wherein each document is verifiably unaltered. It would be advantageous to provide for methods and system that ensure submitted electronic documents are secure, inaccessible to any until all document are accessible, and unaltered.

Thus, there is a need for improved solutions relating to data and digital resources for which access and storage need to be controlled in a secure manner, and wherein alteration of the state of the data/resource prevented and/or the integrity of that state can be verified.

The present application provides methods and systems having such advantages, amongst others.

<NPL>) describes a decentralized, auditable access-control framework for blockchain-based data sharing which builds upon two abstractions. First, on-chain secrets enable collective management of (verifiably shared) secrets under a Byzantine adversary where an access-control blockchain enforces user-specific access rules and a secret-management cothority administrates encrypted data. Second, skipchain-based identity and access management enables administration of dynamic, sovereign identities and access policies.

<CIT> describes one or more servers automatically, based on a set of predetermined rules, executing a mechanism allowing blockchain-asset exchange customers to place standing-limit or market orders for blockchain-based digital assets (e.g., cryptocurrencies) with a counter-party, but without counter-party risk.

<NPL>) describes an open-source system that aims to provide a means to accelerate production enterprise adoption of blockchain technology.

<CIT> describes a two-factor combined public key system and authentication method combined by identity key and random key.

The present application provides method(s) and system(s) as defined in the appended claims.

According to an aspect of the present disclosure, there is provided a computer-implemented method as defined in claim <NUM>.

According to another aspect of the present disclosure, there is provided a computing device as defined in claim <NUM>.

According to a further aspect of the present disclosure, there is provided a non-transitory processor-readable medium as defined in claim <NUM>.

In overview, the present application may provide computer-implemented methods and systems for controlling access to a digital asset or resource, maintaining the state of that asset or resource, and/or verifying that the state has not been altered.

Methods and systems of the invention may provide that participating nodes hold private key shares and collaborate in creating a public key. A digital resource or asset to be submitted by one of the participating nodes is encrypted using the node's own public key and the collaboratively-obtained public key, thereby meaning that the node's own private key and a collaborative private key are required to decrypt the digital asset or resource. (It is important to note that hereafter the digital asset/resource/data may be referred to as simply an "asset", "digital resource"or even a "document" purely for convenience, but that the invention is not thus limited).

Through forming commitment channels between each participating node and a principal node, the participating nodes may confirm submission of their respective encrypted document to a public storage. Each participating node may eventually submit a transaction on the blockchain that reveals its private key share such that any of the nodes is able to then create the collaborative private key from the shares extracted from the blockchain. If the participating node intends its own document to be revealed (since it may opt to withdraw), then it may also disclose its own private key, thereby enabling decryption of its document. The blockchain transactions may further include hashes of the submitted documents so as to enable verification of the integrity of the documents. "Verifying the integrity" may comprise verifying or proving that the state of the digital resource has not been altered. In this manner, the nodes may be assured that their document is only revealed when all other nodes have participated in revealing their respective key shares on the blockchain and all documents from participating nodes become decryptable and accessible at the same time. The present system may thus provide for coordinated and synchronized access to the encrypted documents in a manner in which the documents are verifiably unaltered.

The present invention may provide a computer-implemented method of controlling access to, and/or verifying, a digital resource (e.g. document, software etc.) by a plurality of nodes and a principal node in a blockchain network.

The plurality of nodes may have respective private key shares, where a collective private key of a collective private-public key pair is based on a set of the respective private key shares, and where a first node has a first nodal private-public key pair. The method may be performed by a node. It may include: generating, by the first node, a document crypto public key by combining a first nodal public key of the first nodal private-public key pair and a collective public key of the collective private-public key pair; encrypting the document using the document crypto public key; generating one or more blockchain transactions for a first commitment channel by: generating, by the first node, a commitment transaction having a commitment transaction output locked by a private key share of the first node such that a valid subsequent transaction having the commitment transaction output as an input is (required) to include the private key share of the first node, and receiving, by the first node, the valid subsequent transaction signed by the principal node. The method may also include the step of: in response to receiving the valid subsequent transaction signed by the principal node, broadcasting the commitment transaction to the blockchain network.

In some implementations, the method includes broadcasting, by the first node, to the blockchain network the valid subsequent transaction that is signed by the principal node prior to a first time-lock threshold to reveal the private key share of the first node on the blockchain.

In some implementations, the method includes retrieving from the blockchain the set of private key shares associated with the document; in response to determining that a quantity of private key shares is greater than a private key share threshold, regenerating the collective private key of the collective private-public key pair from the retrieved set of private key shares; and decrypting the encrypted document using a document crypto private key, the document crypto private key being a combination of the regenerated collective private key and a first nodal private key of the first nodal private-public key pair.

In some implementations, the commitment transaction has a transaction output that includes more than one unlocking options including a reveal option that requires a hash of the document, the private key share of the first node, a first nodal private key of the first nodal private-public key pair, a signature of the principal node, and a signature of the first node, such that a valid subsequent transaction includes a transaction input with said hash of the document, said private key share of the first node, said first nodal private key of the first nodal private-public key pair, said signature of the principal node, and said signature of the first node for selecting the reveal option.

In some implementations, the commitment transaction has a transaction output (UTXO) that includes more than one unlocking options including a rescind option that requires the private key share of the first node, a signature of the principal node, and a signature of the first node, such that a valid subsequent transaction includes a transaction input with said private key share of first node, said signature of the principal node, and said signature of the first node for selecting the rescind option.

In some implementations, the commitment transaction has a transaction output that includes more than one unlocking options including a timeout option that requires a signature of the principal node and a signature of the first node, such that a valid subsequent transaction includes a transaction input with said signature of the principal node and said signature of the first node for selecting the timeout option.

In some implementations, the encrypted document is stored in a public repository, and wherein the commitment transaction broadcasts to the blockchain network that a document generated by the first node is saved at the public repository.

In some implementations, an encumbrance on a first asset value is removed in response to the transaction input of the valid subsequent transaction having at least a signature of the principal node and a signature of the first node.

In some implementations, the valid subsequent transaction is a rescind transaction signed by the principal node, and wherein prior to receiving the rescind transaction signed by the principal node, and the method includes: generating the rescind transaction including a transaction input having the private key share of the first node and a signature of the first node.

In some implementations, an encumbrance on a first asset value is removed in response to the transaction input of the rescind transaction having the private key share of the first node, a signature of the principal node, and the signature of the first node, and an encumbrance on a second asset value is removed in response to a transaction input of a further transaction having the signature of the principal node, and wherein an encumbrance on a third asset value is removed in response to a transaction input of a further transaction having the signature of the first node, and the third asset value is a difference between the first asset value and the second asset value.

In some implementations, the valid subsequent transaction is a reveal transaction signed by the principal node, and prior to receiving the reveal transaction signed by the principal node, the method includes: generating the reveal transaction to include a transaction input having a hash of the document, a private key share of the first node, a first nodal private key of the first nodal private-public key pair, and a signature of the first node.

In some implementations, an encumbrance on a first asset value is removed in response to the transaction input of the reveal transaction having the hash of the document, the private key share of the first node, the first nodal private key of the first nodal private-public key pair, a signature of the principal node, and the signature of the first node, and an encumbrance on a fourth asset value is removed in response to a transaction input of a further transaction having the signature of the principal node, and wherein an encumbrance on a fifth value is removed in response to a transaction input of a further transaction having the signature of the first node, and the fifth asset value is a difference between the first asset value and the fourth asset value.

In some implementations, generating the one or more transactions for the first commitment channel includes generating a timeout transaction, and wherein the timeout transaction is eligible to be broadcast by the principal node to the blockchain network after a first time-lock threshold has passed.

The present invention also provides a computing device for carrying out a method as defined above.

The present invention also provides a non-transitory processor-readable medium storing processor-executable instructions, where the processor-executable instructions, when executed by a processor, cause the processor to carry out a method as defined above.

These and other aspects of the present application will be apparent from and elucidated with reference to, the embodiments described herein.

An embodiment of the present application will now be described, by way of example only, and with reference to the accompany drawings, in which:.

The present application provides a digital resource repository system for use on a blockchain network for verifying that digital resources (e.g. documents, software, data, other digital assets etc) submitted to the repository system have not been altered after being submitted and for ensuring that contents of submitted documents may not be revealed to other participating nodes until such time that each participating node reveals at least a private key share for decrypting an encrypted document. We will use the term "document" hereafter for convenience. However, any type of digital resource to which access needs to be controlled and/or verified falls within the scope of the invention.

The following description provides implementations, use cases, and illustrations relating to blockchain protocols, including the Bitcoin protocol. However, the present application has wider applicability and may be used in other systems and computer-based resources, and the present application is not limited in this regard.

In the present application, respective nodes submit a document to the document repository system via state-based transactions for eventual broadcast to the blockchain network. Upon submission of a document to the document repository system, respective nodes participating in verifying said document or documents submitted by other nodes may reveal a private key share via a reveal or rescind transaction. Further, when the respective nodes broadcast the reveal transaction to the blockchain network, the respective nodes provide a nodal private key for revealing contents of the document submitted by that respective node. As such, the document repository system described herein enables immutability of submitted documents and temporal integrity to a document selection process among participating nodes.

Reference is now made to <FIG>, which illustrates, in block diagram form, a document repository system <NUM>, in accordance with an example of the present application. The document repository system <NUM> may include a blockchain network, such as a peer-to-peer open membership network. Any number of nodes may join the blockchain network, without invitation or without consent from other nodes. The blockchain network includes an electronic ledger <NUM>, which in turn may be made up of transactions. Each transaction is a data structure that encodes transfer of control of a digital asset or value.

The document repository system <NUM> may include one or more nodes <NUM>. The nodes <NUM> may be electronic devices and may execute a blockchain protocol. The nodes <NUM> may be various types of electronic devices including, for example, computers (e.g., desktop computers, laptop computers, tablet computers, servers, etc.), mobile devices (e.g., smartphones, wearable computers such as smart watches), or other types of electronic devices. The nodes <NUM> may be coupled to one another using suitable communication technologies which may include wired or wireless communication technologies. In some examples, the document repository system <NUM> may be implemented at least partly over the Internet, and some of the nodes <NUM> may be located in geographically dispersed locations.

The one or more nodes <NUM> may maintain the electronic ledger <NUM> of one or more transactions. Each node <NUM> may store a complete copy or a partial copy of the global ledger. Transactions affecting the electronic ledger <NUM> may be verified by one or more nodes <NUM> so that validity of the electronic ledger <NUM> may be maintained. Details of implementing and operating a blockchain network, such as the Bitcoin protocol, may be appreciated by those of ordinary skill in the art.

In some implementations, each of the respective nodes <NUM> may have a nodal private-public key pair (qi, Qi). The respective nodes <NUM> may generate the nodal private-public key pairs, where the nodal private-public key pairs may be used as "one-time code". For example, the nodal public key (Qi) of the nodal private-public key pair may be used together with an encryption method for encrypting a document. The nodal private key (qi) may be distributed in response to satisfaction of operations of a protocol (e.g., as described herein), and may be used together with a decryption method for decrypting the encrypted document. Thus, once the nodal private key of the nodal private-public key pair is published, that node <NUM> may refrain from using said nodal private-public key pair for future encryption operations.

The document repository system <NUM> may include a principal node <NUM>. The principal node <NUM> may interface with the one or more nodes <NUM> and other components of the document repository system <NUM>. As described herein, the principal node <NUM> may perform operations described herein for forming commitment channels with respective nodes <NUM> and may perform operations described herein for the document repository system <NUM>.

The document repository system <NUM> may include a data store <NUM>. The data store <NUM> may collect and store documents. The collected and stored documents may be encrypted documents. In some examples, the data store <NUM> may include a hash of respective documents or a hash of a hashed respective document (e.g., double hash). Hashing a document may map that document having an arbitrary size to data of a fixed data size.

The data store <NUM> may be accessible by the one or more nodes <NUM> or the principal node <NUM>. A document may be any electronic digital file, such as a long detailed multipage entry, or a number. In some examples, a document can be a small finite set of characters and concatenated with a nonce (e.g., random number).

Encrypted documents stored in the data store <NUM> may be encrypted with a document crypto public key (Li). The document crypto public key (Li) may be defined as Li = P + Qi, where the collective private key (p) corresponding to the collective public key P may initially be unknown to the nodes <NUM> of the document repository system <NUM>.

For example, a first node <NUM> may generate the document crypto public key by combining a first nodal public key (Qi) of the first nodal private-public key pair (qi, Qi) and a collective public key (P) of the collective private-public key pair. The collective private key (p) of the collective private-public key pair may be based on a set of respective private key shares. The respective private key shares may be distributed, for example, according to a threshold secret sharing method. Further, the collective private key (p) may be generated when a set of private key shares are retrieved from each of the respective nodes <NUM>. As described herein, the collective private key (p) may be generated when the set (or a sufficient / threshold number) of private key shares have been revealed by the respective nodes <NUM>, such that the respective nodes <NUM> may collaboratively reveal or verify the encrypted document stored at the data store <NUM>. As described herein, the respective nodes <NUM> may reveal their private key share by broadcasting a valid subsequent transaction, such as a reveal transaction or rescind transaction.

The one or more nodes <NUM> in the document repository system <NUM> may perform one or more operations of a threshold secret sharing protocol. For example, the one or more nodes <NUM> may perform operations of a threshold secret sharing protocol for distributing or assigning private key shares to respective nodes <NUM>. Respective private key shares may be used for revealing or decrypting one or more documents stored in the data store <NUM>. The one or more nodes <NUM> collaboratively performing operations according to a threshold secret sharing protocol can be organized into a cluster of nodes <NUM>, as illustrated in <FIG>.

In some examples, the threshold secret sharing protocol may be defined by a (t ; n) threshold, where n may be the number of participating nodes <NUM> and t +<NUM> may be a minimal number of nodes required to reconstruct a secret. Secret sharing schemes can be examples of threshold crypto systems, where a secret may be divided into portions among n nodes, such that at least t + <NUM> nodes are required to participate in order to reconstruct the secret. Knowledge of any t portions may leave the secret unrevealed.

One example of a threshold secret sharing solution is described in an article entitled "<NPL>"). The Shamir method may be based on polynomial interpolation and w. the secret is assumed to be an element of a finite field F. The Shamir method may include a dealer or a dealerless method and may include a set of n nodes U<NUM>,. , Un and an access structure A. The groups of participants may be able to reconstruct the secret. With the Shamir method, an arbitrary random secret is stored as f(<NUM>) in a t degree polynomial f(x) and only participant i can calculate its share f(xi). If t + <NUM> out of n participants collaborate, they can reconstruct any point on f(x), with their shares (of the key k) k<NUM>, k<NUM>,. , kn which correspond to f(x<NUM>), f(x<NUM>),. , f(xn) using Lagrange Polynomial Interpolation. Using the Lagrange Polynomial Interpolation, a function f(x) with degree t can be reconstructed with t + <NUM> points <MAT> <MAT> where <MAT> Note that bi,p(xi) = <NUM> and bi,p(xj) = <NUM>.

In the presence of a dealer node, the dealer node may select a secret ao = k, assumed to be an element of the finite field F of size p (p prime), and may randomly pick t - <NUM> positive integers a<NUM>,. , at-<NUM>, which represent the coefficient of the polynomial f(x) = ao + a<NUM>x + a<NUM>x<NUM>+. The dealer node may then computes n points (xi, f(xi)) belonging to the polynomial and distribute them to the participants.

In the Shamir dealerless shares distribution phase:.

The above description of the Shamir method is one example of a threshold secret sharing solution; however, other methods or threshold secret sharing solutions may be contemplated. In some implementations, threshold signature calculations may be based on determination of k × G where k is the secret key and G is a point on the Elliptical Curve.

If f(x) is a t-degree polynomial, secret k can be interpolated by k = Σi∈π bi,πki where π may be a size t + <NUM> subset of shares ka, kb,. , kt, kt+<NUM> and b may be an interpolating factor. π may be a group of t + <NUM> nodes collaborating to calculate k × G without revealing its share ki. k may be the x = <NUM> point on a t-degree polynomial.

The above described process of calculating Q = kG may be referred to as Secret Share Joining.

In some implementations, the threshold secret sharing operations may result in allocation of a respective private key share (p^i) to each of the one or more nodes <NUM> of the document repository system <NUM>, such that a collective private key (p) of a collective private-public key pair (p, P) is based on a set of the respective private key shares. For example, the collective private key (p) may be generated or regenerated based on a set of the respective private key shares that may be represented as: <MAT>.

Thus, if there are n nodes <NUM> in the document repository system <NUM>, each of the n nodes <NUM> may be allocated a private key share (p^i), where n or a threshold quantity of key shares may be required to generate the collective private key of the collective public key P in the collective private-public key pair (p, P).

The principal node <NUM> and a respective node <NUM> may form a commitment channel <NUM>. The commitment channel <NUM> may be an example of a state channel implementation, which represents an off-chain alteration of state and which is secured by eventual settlement on a blockchain network / electronic ledger <NUM>. In some examples, the document commitment channel <NUM> may include a series of transactions generated by or signed by one or both of the principal node <NUM> or a node <NUM>, as the case may be, for exchange prior to broadcasting those transactions to the blockchain network. Transactions of the commitment channel <NUM> may be held off the blockchain network, functioning akin to promissory notes for eventual broadcast onto the blockchain network. Thus, as exemplified herein, when the principal node <NUM> and a respective node <NUM> forms the commitment channel <NUM>, operations may include generating or signing transactions by one or both of the principal node <NUM> or a node <NUM> and may further include broadcasting at least one of those transactions to the blockchain network to form that commitment channel <NUM>. Because transactions based on the commitment channel <NUM> can be exchanged between the principal node <NUM> and a respective node <NUM> "off" the blockchain network, the transactions may be exchanged without latency typically associated with broadcasting and validating transactions on the blockchain network.

For ease of exposition, a commitment channel <NUM> is illustrated in <FIG> as between the principal node <NUM> and a selected node <NUM> (e.g., Node i). However, in some examples, respective commitment channels <NUM> may be formed between the principal node <NUM> and each of the one or more nodes <NUM> participating in collectively verifying or in collectively revealing a document available in the data store <NUM>.

Reference is now made to <FIG>, which diagrammatically illustrates a commitment channel <NUM>, in accordance with an example of the present application. In some examples, a node <NUM> or the principal node <NUM> may form a commitment channel <NUM> by generating a commitment transaction <NUM> and at least one other valid subsequent transaction signed by the principal node <NUM>, and transmitting that commitment transaction <NUM> to the blockchain network. In some examples, the valid subsequent transaction may include a rescind transaction <NUM> or a reveal transaction <NUM>. Further, either the node <NUM> or the principal <NUM> may generate a timeout transaction <NUM>.

<FIG> further illustrates an encumbered digital asset <NUM>. The commitment transaction <NUM> may include an unspent transaction output (UTXO) including an encumbrance of the digital asset <NUM>. As described herein, the encumbered digital asset <NUM> diagrammatically illustrated in <FIG> may be allocated in response to a valid subsequent transaction, such as a rescind transaction <NUM>, a reveal transaction <NUM>, or a timeout transaction <NUM>.

The node <NUM> may generate a commitment transaction <NUM> to broadcast to the blockchain network that a document generated by that node <NUM> is saved at the data store <NUM>. The node <NUM> may generate the document that the node <NUM> may wish to store at the data store <NUM> (<FIG>) and may wish to disseminate to other nodes via the document repository system <NUM>. In some implementations, the contents of the generated document may not be stored or recorded by transactions on the blockchain network. However, a hash of the document (HoDi) may be recorded by one or more transactions. The hash of the document may correspond to an encrypted document that can be stored in the data store <NUM>. In some examples, a double hash of the generated document (e.g., H(HoDi)) may be recorded by a transaction that is broadcast to the blockchain network. A hash function may: (<NUM>) map data of an arbitrary size to data of a fixed size, such that the generated document can be represented in a blockchain transaction within a defined amount of data; or (<NUM>) prevent a node <NUM> from altering the generated document that may be stored at the data store <NUM>. Hashing an altered document will yield a different hash result and may indicate that the document stored at the data store <NUM> has been altered.

To illustrate examples of the commitment transaction <NUM>, the rescind transaction <NUM>, the reveal transaction <NUM>, and the timeout transaction <NUM>, reference is now made to <FIG>, which diagrammatically illustrate the respective transactions of the commitment channel <NUM>, in accordance with examples of the present application. In some implementations, the transactions may include a locking script (e.g., <scriptPubKey>), which can be an output of the transaction that may encumber a digital asset or value by imposing rules or criteria that an unlocking script (e.g., <scriptSig>) of a valid subsequent transaction must satisfy to unencumber the digital asset or value of the prior transaction.

<FIG> diagrammatically illustrates an example commitment transaction <NUM>. A node <NUM> (<FIG>) may generate the commitment transaction <NUM> for submitting a document to the document repository system <NUM> (<FIG>) for consideration by the principal node <NUM> (<FIG>) or by other nodes <NUM> (<FIG>). When the node <NUM> submits the document to the document repository system <NUM> for consideration, the node <NUM> may also submit a digital asset <NUM>. The document repository system <NUM> may require submission of the digital asset <NUM> of a specified value in exchange for consideration of the submitted document by the principal node <NUM>. The commitment transaction <NUM> may setup an encumbrance of the digital asset <NUM> until such time that a valid subsequent transaction allocates the digital asset <NUM>.

The commitment transaction <NUM> may include one or more options for unencumbering the digital asset <NUM>. The digital asset <NUM> may represent a first asset value. The options for unencumbering the digital asset may be specified in a locking script of the UTXO, such that the unlocking script of a valid subsequent transaction must contain required inputs prior to being able to unencumber the digital asset <NUM>. For example, a withdraw or rescind option <NUM> may require that an unlocking script of a valid subsequent transaction provide a signature of the principal node <NUM> (e.g., σ(S)), a private key share of the node <NUM> (e.g., p̂i), and a signature of the node <NUM> (e.g., σ(Ui)) for selecting the withdraw option. The valid subsequent transaction that can include these inputs may correspond to the rescind transaction <NUM> (<FIG>), as described herein. That is, in some examples, the commitment transaction has a transaction output that includes more than one unlocking options including a rescind option that requires the private key share of a first node, a signature of the principal node, and a signature of the first node, such that a valid subsequent transaction includes a transaction input with said private key share of the first node, said signature of the principal node, and said signature of the first node for selecting the rescind option.

In some implementations, the locking script of the commitment transaction <NUM> may include a reveal option <NUM>. The reveal option <NUM> may require that an unlocking script of a valid subsequent transaction provide a signature of the principal node <NUM> (e.g., σ(S)), a hash of the encrypted document (e.g., HoDi), a private key share of the node <NUM> (e.g., p̂i), a nodal private key (e.g., qi) of the node <NUM>, and a signature of the node <NUM> (e.g., σ(Ui)) for selecting the reveal option. The valid subsequent transaction that can include these inputs may be the reveal transaction <NUM> (<FIG>), as described herein. That is, in some examples, the commitment transaction has a transaction output that includes more than one unlocking options including a reveal option that requires a hash of the document, the private key share of a first node, a first nodal private key of the first nodal private-public key pair, a signature of the principal node, and a signature of the first node, such that a valid subsequent transaction includes a transaction input with said hash of the document, said private key share of the first node, said first nodal private key of the first nodal private-public key pair, said signature of the principal node, and said signature of the first node for selecting the reveal option.

In some implementations, the locking script of the commitment transaction <NUM> may include a timeout option <NUM>. The timeout option <NUM> may require that an unlocking script of a valid subsequent transaction provide a signature of the principal node <NUM> (e.g., σ(S)) and a signature of the node (e.g., σ(Ui)) for selecting the timeout option. The valid subsequent transaction that can include these inputs may correspond to the timeout transaction <NUM> (<FIG>). As described herein, when the node <NUM> submits neither the rescind transaction <NUM> nor the reveal transaction <NUM> within a first time-lock threshold period, the principal node <NUM> may broadcast the timeout transaction <NUM> to the blockchain network after that first time-lock threshold has passed. The timeout transaction <NUM> can include an unlocking script for providing the signature of the principal node <NUM> and the signature of the node for the timeout option <NUM>. That is, in some examples, the commitment transaction has a transaction output that includes more than one unlocking options including a time out option that requires a signature of the principal node and a signature of the first node, such that a valid subsequent transaction includes a transaction input with said signature of the principal node and said signature of the first node for selecting the timeout option. In some implementations, the signature (e.g., σ(Ui)) of the node (Ui) contained in the transaction input of the commitment transaction <NUM> and a signature of the node (Ui) contained in the transaction output of the commitment transaction <NUM> may be based on different public-private key pairs of that node. For example, that node (Ui) may have more than one public-private key pair and may generate signatures for different aspects of the commitment transaction <NUM> or other transactions for the commitment channel <NUM>.

In some implementations, the commitment transaction <NUM> may also include a double-hash of the document (H(HoDi)) (not illustrated in <FIG>) generated by the node <NUM>. The node <NUM> may generate the double-hash of the document when the node <NUM> may submit that document to the document repository system <NUM>. A hash function H(θ) may: (<NUM>) map data of an arbitrary size to data of a fixed size, such that the generated document can be represented in a blockchain transaction within a defined amount of data; or (<NUM>) prevent any node <NUM> from altering the generated document that may be stored at the data store <NUM>.

Hashing an altered document may yield a different hash result and may indicate that the document stored at the data store <NUM> has been altered.

<FIG> diagrammatically illustrates an example rescind transaction <NUM>. When forming the commitment channel <NUM>, the node <NUM> may generate the rescind transaction <NUM>. The node <NUM> may broadcast the rescind transaction <NUM> to the blockchain network in the circumstance that the node <NUM> has submitted a document to the document repository system <NUM> but subsequently does not intend to have that document considered for selection by the principal node <NUM> or any other nodes <NUM>. In particular, the node <NUM> may generate the rescind transaction <NUM> that includes a transaction input <NUM> having a private key share (e.g., p̂i) of the node <NUM>, a signature of the node <NUM> (e.g., σ(Ui)), and a signature of the principal node <NUM> (e.g., σ(S)). As will be described, the principal node <NUM> may sign the rescind transaction <NUM> when the principal node <NUM> verifies that the rescind transaction <NUM> includes mandated transaction inputs and transaction outputs for the commitment channel <NUM> for the principal node <NUM> and that respective node <NUM>. Because the rescind transaction <NUM> includes the private key share of the node <NUM>, the rescind transaction <NUM> may provide sufficient information that may contribute to decryption of documents submitted by other nodes <NUM>.

The rescind transaction <NUM> may include a transaction output having two outputs for encumbering at least two asset values. For example, the rescind transaction <NUM> may include an output for encumbering a second asset value <NUM> and a third asset value <NUM>. Thus, an encumbrance on the second asset value <NUM> may be removed in response to a transaction input of a further transaction having the signature of the principal node (e.g., σ(S)). An encumbrance on the third asset value <NUM> may be removed in response to a transaction input of a further transaction having the signature of the node <NUM> (e.g., σ(Ui)). The second asset value <NUM> may be less than the first asset value <NUM>. Further, the third asset value <NUM> may be a difference between the first asset value <NUM> and the second asset value <NUM>. Thus, in some examples, the second asset value <NUM> may be a fee when the node <NUM>: (<NUM>) submits a generated document to the data store <NUM>; but (<NUM>) withdraws the document from consideration by the principal node <NUM>. The third asset value <NUM> may represent an unencumbered asset value that may be returned to the node <NUM> that broadcasted said rescind transaction <NUM>.

Note that when the node <NUM> broadcasts the rescind transaction <NUM> to the blockchain network, the rescind transaction <NUM> includes the signature of the principal node <NUM>, the signature of that node <NUM>, and the private key share (p̂i) of that node <NUM>; however, the nodal private key (e.g., qi) of that node <NUM> is not included. Without the nodal private key (qi) of that node <NUM>, any encrypted document (EncL(Doci)) that was: (<NUM>) previously generated by that node <NUM>; and (<NUM>) encrypted using the document crypto public key (e.g., Li = P + Qi) may not be decrypted by any of the other nodes <NUM> because none of the other nodes <NUM> may determine a document crypto private key li = p + qi. When the node <NUM> fails to provide the nodal private key (qi), the document crypto private key may not be generated.

Note also that when the node <NUM> broadcasts the rescind transaction <NUM> to the blockchain network, the private key share (p̂i) of that node <NUM> may be included in the transaction input. Thus, the collective private key (p) may be generated, allowing for other nodes <NUM> to decrypt encrypted documents using a private document crypto key p + qi, where qi is the nodal private key of the nodal private-public key pair (qi, Qi) for respective nodes <NUM> and when qi is available on the blockchain network.

<FIG> diagrammatically illustrates an example reveal transaction <NUM>. When forming the commitment channel <NUM>, the node <NUM> may generate the reveal transaction <NUM>. The node <NUM> may broadcast the reveal transaction <NUM> to the blockchain network in the circumstance that the node <NUM> has submitted a document to the document repository system <NUM> and intends to have that document considered for selection by the principal node <NUM> or any other node <NUM>. By intending that document to be considered for selection, the encrypted version of that document may be decrypted using a document crypto private key li = p + qi. As the transaction input of the reveal transaction <NUM> may include both the private key share (p̂i) of that node <NUM> and the nodal private key (qi) of the nodal private-public key pair (qi, Qi), any of the principal node <NUM> or the other nodes <NUM> may decrypt that document stored at the data store <NUM>, provided that a threshold number of other nodes reveal a respective private key share.

In particular, the reveal transaction <NUM> may include a transaction input <NUM> that may include a signature of the principal node (σ(S)), a hash of the encrypted document (HoDi), a key share of the node <NUM> (p̂i), a nodal private key of the node <NUM> (qj), and a signature of the node <NUM> (σ(Ui)). As will be described, the principal node <NUM> may sign the reveal transaction <NUM> (e.g., ascribe σ(S) to the reveal transaction <NUM>) when the principal node <NUM> verifies that the reveal transaction <NUM> includes mandated transaction inputs and transaction outputs for the commitment channel <NUM> for the principal node <NUM> and that respective node <NUM>. Because the reveal transaction <NUM> includes the private key share of the node <NUM> as well as the nodal private key of the nodal private-public key pair (qi, Qi) for that respective node <NUM>, the reveal transaction <NUM> may provide sufficient information that may allow decryption of documents. That is, the reveal transaction <NUM> may provide sufficient information for determining a document crypto private key li = p + qi.

The reveal transaction <NUM> may include a transaction output having two outputs for encumbering at least two asset values. For example, the reveal transaction <NUM> may include an output for encumbering a fourth asset value <NUM> and a fifth asset value <NUM>. An encumbrance on the fourth asset value <NUM> may be removed in response to a transaction input of a further transaction having the signature of the principal node (e.g., σ(S)). An encumbrance on the fifth asset value <NUM> may be removed in response to a transaction input of a further transaction having the signature of the node <NUM> (e.g., σ(Ui)). The fourth asset value <NUM> may be less than the first asset value <NUM> (<FIG> and <FIG>). Further, the fifth asset value <NUM> may be a difference between the first asset value <NUM> and the fourth asset value <NUM>. Thus, in some examples, the fourth asset value <NUM> may be a fee for submitting a generated document to the data store <NUM> for consideration and subsequent verification by the principal node <NUM> or any other node <NUM> participating in the document repository system <NUM>. The fifth asset value <NUM> may represent an unencumbered asset value that may be returned to the node <NUM> that broadcasted said reveal transaction2 <NUM>.

In some examples, the document repository system <NUM> may be structured to encourage the respective nodes <NUM> to broadcast a reveal transaction <NUM>, rather than to broadcast a rescind transaction <NUM>. Thus, the fourth asset value <NUM> may be less than the second asset value <NUM> (<FIG>) of the rescind transaction <NUM> (<FIG> and <FIG>). Note that for ease of exposition, any transaction fees that may be attributed to mining / validating nodes of the blockchain network in accordance with a blockchain protocol (e.g., bitcoin protocol) have not been included in the description of encumbering and unencumbering of the digital assets.

<FIG> diagrammatically illustrates an example timeout transaction <NUM>. When forming the commitment channel <NUM>, the principal node <NUM> or the respective node <NUM> may generate the timeout transaction <NUM>. The principal node <NUM> may broadcast the timeout transaction <NUM> to the blockchain network in the circumstance that the node <NUM> has broadcast the commitment transaction <NUM> to the blockchain network, but the node <NUM> has not broadcast any valid subsequent transaction following the broadcasted commitment transaction <NUM>. In some examples, the node <NUM> may not have broadcast a rescind transaction <NUM> or a reveal transaction <NUM> if the node <NUM> may have lost network communication with the blockchain network or may have gone offline.

The timeout transaction <NUM> may be an nLockTime-based transaction, such that the principal node <NUM> may not successfully broadcast the timeout transaction <NUM> to the blockchain network until a time-lock threshold has been passed. The time-lock threshold may be defined in terms of transaction block height of the electronic ledger <NUM> (<FIG>) or UNIX time. As an example, the time-lock threshold may be a deadline for each of the nodes <NUM> to either broadcast a rescind transaction <NUM> or a reveal transaction <NUM> subsequent to the respective broadcast of the commitment transaction <NUM>. Recall that the commitment transaction <NUM> may be representative of or an indication of an encrypted document being stored at the data store <NUM> (<FIG>). That is, when a node <NUM> broadcasts a commitment transaction <NUM> to the block chain network, the node <NUM> may be broadcasting existence of that document in the document repository system <NUM>.

When the node <NUM> fails to broadcast a withdraw transaction <NUM> or a reveal transaction <NUM> before the first time-lock threshold, the node <NUM> fails to provide the private key share (p̂i) and the nodal private key (qi) of that node <NUM>. Failure to reveal the private key share of that node <NUM> may prevent other nodes participating in the document repository system <NUM> from regenerating the collective private key (p) of the collective private-public key pair (p, P), thus preventing other nodes from decrypting encrypted documents stored at the data store <NUM>. Further, failure to reveal the nodal private key (qi) of that node <NUM> may prevent other nodes participating in the document repository system <NUM> from decrypting the encrypted document of that particular node <NUM>. Recall that to decrypt the encrypted document, a document crypto private key (li = p + qi) may be required.

The timeout transaction <NUM> may include a transaction output having an output for further encumbering the first asset value <NUM> by the principal node <NUM>. That is, an encumbrance on the first asset value <NUM> may be removed in response to a transaction input of a further transaction having the signature of the principal node (e.g., σ(S)). In some examples, the document repository system <NUM> may require that the structure of the transaction output of the timeout transaction <NUM> encumber the first asset value <NUM> as a penalty to the node <NUM> who did not broadcast at least one of a withdraw transaction <NUM> or a reveal transaction <NUM> to the blockchain network prior to the first time-lock threshold (s1).

In some examples, said further transaction having the signature of the principal node (σ(S)) may include transaction outputs to distribute a portion of the first asset value to each of the other nodes <NUM> in lieu of each of the other nodes <NUM> being unable to decrypt encrypted documents that may be stored at the data store <NUM>. Recall that each of the other nodes <NUM> may be unable to regenerate the collective private key (p) without private key shares from the set or at least some nodes <NUM>.

In some examples, the nodes <NUM> may not broadcast the timeout transaction <NUM> to the blockchain network. Rather, the timeout transaction <NUM> may be broadcast by the principal node <NUM> to the blockchain network in the event that a respective node <NUM> fails to broadcast a reveal or rescind transaction prior to the first time-lock threshold. Because the timeout transaction <NUM> encumbers the first asset value <NUM> for the benefit of the principal node <NUM>, each respective node <NUM> may not operate to broadcast the timeout transaction <NUM> to the blockchain network.

Reference is now made to <FIG>, which diagrammatically illustrates commitment channels between the principal node <NUM> and each of several nodes, in accordance with examples of the present application. For example, a first commitment channel <NUM> may be formed for a "Node <NUM>" and the principal node <NUM>. A second commitment channel <NUM> may be formed for a "Node <NUM>" and the principal node <NUM>. A nth commitment channel <NUM> may be formed for a "Node n" and the principle node <NUM>. Each of the respective commitment channels may be associated with encrypted documents that may be associated with a respective node and that may be stored in a data store. In some examples, the number of commitment channels in a document repository system may correspond to the number of nodes participating in verifying or revealing encrypted documents stored at a data store <NUM> (<FIG>). Each of the first commitment channel <NUM>, the second commitment channel <NUM>, or the nth commitment channel <NUM> may be associated with a commitment transaction, a rescind transaction, a reveal transaction, or a timeout transaction having the similar features as those described in <FIG> and <FIG> herein.

As described, nodes <NUM> (<FIG>) may wish to submit one or more documents to the document repository system <NUM> (<FIG>) for consideration by the principal node <NUM> (<FIG>) or by other nodes <NUM>. Submitting a document to the document repository system <NUM> may include transmitting an encrypted document to the data store <NUM> (<FIG>) for storage and may include generating and broadcasting a commitment transaction to the blockchain network. In some examples, the encrypted document may not be specified or stored in a transaction that is broadcast to the blockchain network. Rather, a hash of the encrypted document (e.g., HoDi) may be specified in a transaction that is broadcast to the blockchain network. The hash of the encrypted document may be used to broadcast to the blockchain network that the encrypted document is saved in the data store <NUM>.

In some implementations, the principal node <NUM> may generate a request transaction requesting for document submissions from nodes <NUM>. The request transaction may include locking scripts specifying, among other specifications, a quantity of document submissions that may be received, a quantity of nodes <NUM> that may make document submissions, or time-lock thresholds for (a) when submission of commitment transactions to the blockchain network may occur (e.g., up until a time-lock threshold), such as a submission threshold time period (s0); and (b) when submission of a subsequent valid transaction (e.g., rescind transaction <NUM> or reveal transaction <NUM>) must be broadcast, such as a first threshold time period (s1). In some examples, the submission threshold time period (s0) may be implemented such that the document repository system <NUM> may receive encrypted documents from participating nodes for storage before proceeding with operations for decrypting said encrypted documents. In some examples, the request transaction may include specifications detailing use of Elliptic Curve Cryptography (ECC). For example, if the document repository system <NUM> is based on the Bitcoin protocol, the elliptic curve (secp256k1 ECDSA) having the following set of parameters may be used:.

In some implementations, a secret sharing protocol may be implemented to distribute n key shares to n nodes, where the n nodes may submit one or more documents to the document repository system <NUM>. As described herein, the n key shares may be used to generate a collective private key (p) associated with a collective public key (P) of a collective private-public key pair (p, P). In some implementations, the collective private key shares may be distributed by a trusted dealer node. When a trusted dealer node distributes collective private key shares, the trusted dealer node may be the principal node <NUM> and may have knowledge of the collective private key for generating the collective private key shares for the participating nodes.

In some other implementations, the collective private key shares may be distributed based on a dealerless protocol. With a dealerless protocol, no particular node has prior knowledge of the collective private key share, and the protocol may require at least t + <NUM> of n keyshares for generating the collective private key (p). When a polynomial-based secret share protocol is used, "t" may be the degree of that polynomial. The dealerless protocol may require that the n nodes collaborate to generate and validate the respective collective private key shares.

In some example implementations, the threshold t + <NUM> may be t ∈ Z: <NUM> < t ≤ n - <NUM>, where t may be a quantity such that t + <NUM> ≠ n. The example implementation where a threshold t + <NUM> ≠ n is used may be useful for scenarios where one or more nodes <NUM> may have broadcast a commitment transaction <NUM>, but may have subsequently severed a network communication channel with the blockchain network, such that that particular node <NUM> would not broadcast a subsequent valid transaction from the respective commitment channel <NUM>. Note that setting the threshold t + <NUM> ≠ n may ameliorate scenarios for the participating nodes <NUM> to regenerate the collective private key (p), even when one or more nodes may have severed a network communication channel with the blockchain network. Note that in the example implementation where the threshold may be t + <NUM> ≠ n, an encrypted document in the data store <NUM> may be decrypted prior to the entire set of nodes <NUM> broadcasting one of a rescind transaction <NUM> or a reveal transaction <NUM> to the blockchain network. Thus, when an encrypted document in the data store <NUM> may be decrypted prior to the entire set of nodes <NUM> broadcasting one of a rescind transaction <NUM> or a reveal transaction <NUM> to the blockchain network, nodes <NUM> that may not yet have broadcast one of a rescind transaction <NUM> or a reveal transaction <NUM> may reveal contents of other encrypted documents at the data store <NUM> and may broadcast one of a rescind transaction <NUM> or a reveal transaction <NUM> prior to passing of the first time-lock threshold based on such revelation.

In some example implementations, the document repository system <NUM> may utilize a secret sharing protocol utilizing an n + r threshold, such that n + r key shares may be required for generating the collective private key (p) of the collective private-public key pair (p, P). The additional r private key shares may be distributed to the principal node <NUM> or other trusted third parties. However, when using the secret sharing protocol with an n + r threshold, retrieving from the blockchain n private key shares would not be sufficient for generating the collective private key (p) for verifying integrity of or revealing an encrypted document at the data store <NUM>.

In some example implementations, the nodes <NUM> of the document repository system <NUM> may perform operations of a Publicly Verifiable Secret Sharing (PVSS) protocol. It may be desirable that respective nodes be able to verify that the respective nodes are allocated correct secret key shares. Key share verification may be employed for allowing nodes to verify respective key share(s), as well as key share(s) of other nodes.

An example PVSS protocol is described in "<NPL> [Stadler].

In an example PVSS protocol, each node Ui may have a decryption function Di, which is able to access the information encrypted with the corresponding public encryption function Ei. In this way, a dealer node may use the public encryption function to distribute key shares and publish them in the following form: <MAT>.

The encrypted shares can be publicly verified by an interested node. The nodes can verify its own key share(s) and can verify that the other nodes received correct key shares, i.e. whether the dealer node was honest or not.

The main (high level) components of the PVSS protocol include:.

In some implementations, the PVSS scheme can be interactive or non-interactive depending on necessity in the recovery phase.

Various implementations of the PVSS protocol based on several cryptosystems may be contemplated. For illustration, the following highlights a protocol described in the publication "<NPL>.

In an initialisation phase, using a public procedure, a group Gq and two independently selected generators G and g may be chosen. Each node, given its private key <MAT>, may set yi = Gxi as public key.

The dealer node may then select a random polynomial <MAT> of degree at most t - <NUM> with coefficients in Zq and sets a<NUM> = k. The commitments Cj = gaj,j = <NUM>,. , t and the encrypted shares f(i) (using the participants' public key) Yi = yif(xi) , i = <NUM>,. , n may be published.

By computing <MAT> the dealer node can show that the encrypted shares are consistent. In particular, the dealer node can produce a proof of knowledge of the f(i) by showing that Xi = gf(xi), Yi = yif(xi).

The verification of key shares can be performed using the Fiat-Shamir cryptographic technique in Stadler, cited above. The main steps of the non-interactive protocol include the following:.

and may prove that the hash of Xi, Yi, a<NUM>i, a<NUM>i, <NUM> ≤ i ≤ n, matches c.

When needed, the participant nodes can reconstruct the secret s, without having to learn anything about other nodes' shares f(xi). The information required may include Si = Gf(xi), i = <NUM>,. The secret is computed via Lagrange interpolation <MAT> where <MAT> is a Lagrange coefficient.

The above example utilizes a dealer node for computing and distributing key shares. However, it may be contemplated that a dealerless implementation of the secret sharing protocol may be implemented as described by Fiat-Shamir heuristics techniques (see e.g., "<NPL>).

As described, in some implementations, the nodes <NUM> may execute operations of a secret sharing joining protocol. The set of nodes may collaborate to generate the collective public key (P), where P = pG, where G may be the selected basepoint of the elliptic curve, and where p may be the collective private key (p).

As described, the nodes and the principal node may form a respective commitment channel based on generation of one or more transactions and broadcasting a commitment transaction to the blockchain network. To illustrate formation of an example commitment channel, reference is now made to <FIG>, which illustrates a sequence diagram <NUM> of transactions exchanged between a node <NUM> (<FIG>), a principal node <NUM> (<FIG>), and an electronic ledger <NUM>, in accordance with an example of the present application. The electronic ledger <NUM> may be a component of the blockchain network. For ease of exposition, in some examples, the blockchain network may be used to refer to the electronic ledger <NUM>. The sequence diagram <NUM> may illustrate an example formation of the commitment channel <NUM> illustrated in <FIG>.

At operation <NUM>, the node <NUM> may generate a commitment transaction <NUM> (<FIG>) having a commitment transaction output locked by a private key share of the node <NUM> such that a valid subsequent transaction having the commitment transaction output as an input is to include the private key share of the node <NUM>. In some examples, the commitment transaction <NUM> may be similar to the commitment transaction <NUM> of <FIG>.

At operation <NUM>, the node <NUM> may also transmit the commitment transaction <NUM> to the principal node <NUM>. By generating and transmitting the commitment transaction <NUM> to the principal node <NUM>, the node <NUM> may indicate to the principal node <NUM> that the node <NUM> is submitting a document to the document repository system <NUM>. Further, at operation <NUM>, the node <NUM> may transmit an encrypted document to the data store <NUM> (<FIG>) for storage. The data store <NUM> may be publically accessible, such that the nodes <NUM> and the principal node <NUM> of the document repository system <NUM> may access encrypted documents stored therein; however, the nodes <NUM> or the principal node <NUM> may need to decrypt the encrypted documents using a document crypto private key (li = p + qi), where p is the collective private key based on a set of collective private key shares distributed to the nodes <NUM> and qi is a nodal private key associated with the encrypted document.

In some examples, the commitment transaction <NUM> may be hashed and the node <NUM> may transmit a hash of the commitment transaction <NUM> to the principal node <NUM>. In some implementations, the hash of the commitment transaction <NUM> may be an identifier ("ID") for referencing that commitment transaction <NUM>. For example, the ID may be included a rescind transaction <NUM>, a reveal transaction <NUM>, or a timeout transaction <NUM> for identifying the corresponding commitment transaction <NUM>. In some examples, a hash of the commitment transaction <NUM> may: (<NUM>) map the commitment transaction <NUM> to a fixed data size; and/or (<NUM>) assist with detecting subsequent alteration of the commitment transaction <NUM>, as hashing an altered document may yield a different hash result. The principal node <NUM> or any of the nodes <NUM> may utilize expected hash results for determining whether the commitment transaction <NUM> may have been altered.

At <NUM>, the node <NUM> may generate a valid subsequent transaction. The valid subsequent transaction may be a rescind transaction <NUM> similar to that illustrated in <FIG>. The rescind transaction <NUM> may include a transaction input having a private key share of the node <NUM> and a signature of the node <NUM>. At <NUM>, the node may also transmit the rescind transaction <NUM> to the principal node <NUM>.

At <NUM>, the principal node <NUM> may verify that the rescind transaction <NUM> includes the mandated transaction inputs and transaction outputs for the commitment channel <NUM>. For example, the principal node <NUM> may verify that the rescind transaction <NUM> includes at least a signature of the node <NUM> or desired input or output asset values. In some examples, the node <NUM> may not yet provide the respective private key share (p̂i) of that node <NUM>. Once the principal node <NUM> verifies that the rescind transaction <NUM> includes the mandated transaction inputs and transaction outputs, the principal node <NUM> may append or concatenate a signature of the principal node (σ(S)) to rescind transaction <NUM> and transmit the signed rescind transaction to the node <NUM>. In some examples, the principal node <NUM> may append or concatenate a signature of the principal node without having knowledge of the private keyshare of the node <NUM>. That is, at <NUM>, the principal node <NUM> may be setting up the rescind transaction <NUM>, such that the rescind transaction <NUM> may be subsequently broadcast to the blockchain network.

Note that exchange of the "unsigned" and the principal-signed rescind transaction occurs "off" the blockchain. The node <NUM> may broadcast the principal-signed rescind transaction <NUM> to the blockchain network at a later time if the node <NUM> wishes to withdraw the document associated with the node <NUM> from consideration by the principal node <NUM> or other nodes of the document repository system <NUM>. Note that because the rescind transaction <NUM> includes the private key share (p̂i) of the node <NUM>, if the rescind transaction <NUM> is broadcast to the blockchain network, the rescind transaction <NUM> may reveal the private key share of that node <NUM> on the blockchain, such that respective nodes may retrieve from the blockchain the set of private key shares for generating the collective private key (p) that may be used in combination with a nodal private key (qi) for decrypting an encrypted document EncL(Doci).

At <NUM>, the node <NUM> may generate a reveal transaction <NUM> similar to that illustrated in <FIG>. For example, the reveal transaction <NUM> may be another example of a valid subsequent transaction described above. The reveal transaction <NUM> may include a transaction input having a hash of the document (HoDi) associated with the node <NUM>, a private key share (p̂i) of the node <NUM>, a nodal private key (qi) of the nodal private-public key pair associated with the node <NUM>, and a signature of the node <NUM>.

At <NUM>, the principal node <NUM> may verify that the reveal transaction <NUM> includes the mandated transaction inputs and transaction outputs for the commitment channel <NUM>. For example, the principal node <NUM> may verify that the reveal transaction <NUM> includes at least a signature of the node <NUM> or desired input output asset values. In some examples, the node <NUM> may not yet provide the hash of the document (HoDi) associated with the node <NUM>, the private key share (p̂i) of the node <NUM>, or the nodal private key (qi) of the nodal private-public key pair associated with the node <NUM>. Once the principal node <NUM> verifies that the reveal transaction <NUM> includes the mandated transaction inputs and transaction outputs, the principal node <NUM> may append or concatenate a signature of the principal node (σ(S)) to the reveal transaction <NUM> and transmit the signed reveal transaction to the node <NUM>. In some examples, the principal node <NUM> may append or concatenate a signature of the principal node without having knowledge of the hash of the document (HoDi) associated with the node <NUM>, the private key share (p̂i) of the node <NUM>, or the nodal private key (qi) of the nodal private-public key pair associated with the node <NUM>. That is, at <NUM>, the principal node <NUM> may be setting up the reveal transaction <NUM>, such that the reveal transaction <NUM> may be subsequently broadcast to the blockchain network.

Note that exchange of the "unsigned" and the principal-signed reveal transaction occurs "off" the blockchain. The node <NUM> may broadcast the signed reveal transaction <NUM> to the blockchain network at a later time if the node <NUM> wishes to reveal the encrypted document at the data store <NUM> for consideration by the principal node <NUM> or other nodes participating in the document repository system <NUM>. When the node <NUM> broadcasts the reveal transaction <NUM> to the blockchain network, the node <NUM> reveals the private key share (p̂i) of the node <NUM> on the blockchain and the nodal private key (qi) for contributing to generation of the document crypto private key for decrypting the encrypted document of the node <NUM>.

In some implementations, the node <NUM> may require that at least one valid subsequent transaction (e.g., at least one of the rescind transaction <NUM> or the reveal transaction <NUM>) be signed by the principal node <NUM> prior to broadcasting the commitment transaction <NUM> to the blockchain network. By refraining from broadcasting the commitment transaction <NUM> of the node <NUM> to the blockchain network until at least one of a principal-signed rescind transaction <NUM> or a principal-signed reveal transaction <NUM> is received, the node <NUM> may be assured that a portion of the first asset value <NUM> (<FIG>) may be returned if at least one of the principal-signed rescind transaction <NUM> or the principal-signed reveal transaction <NUM> is broadcasted to the blockchain network prior to the first time-lock threshold (s1).

Because in the examples described herein, the at least one valid subsequent transaction may need to be principal-signed prior to encumbrances being removed on the third asset value <NUM> (<FIG>) or the fifth asset value <NUM> (<FIG>), the node <NUM> may refrain from broadcasting the commitment transaction <NUM> of that node <NUM> until the principal-signed valid subsequent transaction is received. Once a commitment transaction <NUM> is broadcast to the blockchain network, the node <NUM> may broadcast either the rescind transaction <NUM> or the reveal transaction <NUM> to the blockchain network for contributing the private key share (p̂i) of that node <NUM> to the set of respective private key shares in exchange for either said third asset value <NUM> or said fifth asset value <NUM>. In some implementations, the rescind transaction <NUM> may be signed by the principal node <NUM> before the reveal transaction <NUM>, or vice versa. In some examples, the node <NUM> may prefer that the reveal transaction <NUM> be signed by the principal node <NUM> before any other valid subsequent transaction, at least because said fifth asset value <NUM> may be greater than said third asset value <NUM>. In some implementations, the rescind transaction <NUM> may be signed by the principal node <NUM> at substantially the same time as the reveal transaction <NUM>.

When the node <NUM> submits neither the rescind transaction <NUM> nor the signed reveal transaction <NUM>, as described herein, the principal node <NUM> may broadcast the timeout transaction <NUM> <FIG> to the blockchain network. The timeout transaction <NUM> may include a transaction output having an output for encumbering the first asset value <NUM> for the benefit of the principal node <NUM>. In the circumstance that the node <NUM> may broadcast the commitment transaction <NUM> to the blockchain network for indicating that the node <NUM> may wish to submit a document to the document repository system <NUM>, but in the circumstance that the node <NUM> fails to follow up with broadcasting either a signed rescind transaction <NUM> or a signed reveal transaction <NUM> before the first threshold time period (s1), the principal node <NUM> may remove the encumbrance on the first asset value <NUM>. In this case, the first asset value <NUM> may be a penalty to the node <NUM> for failing to reveal the private key share (p̂i) of that node <NUM> on the blockchain.

In some implementations, either the node <NUM> or the principal node <NUM> may generate the timeout transaction <NUM>. However, the principal node <NUM> may utilize the timeout transaction <NUM> for levying a penalty to the node <NUM> for failing to reveal the private key share on the blockchain. Thus, at operation <NUM>, the principal node <NUM> may generate the timeout transaction <NUM>. The timeout transaction <NUM> may be similar to that illustrated in <FIG> and may include a transaction input having a signature of the principal node <NUM>.

At <NUM>, the node <NUM> may verify that the timeout transaction <NUM> includes the mandated nLockTime-based transaction and, once verified, the node <NUM> may append or concatenate a signature of the node <NUM> (σ(Ui)) to the timeout transaction and transmit the signed timeout transaction to the principal node <NUM>.

Further, the timeout transaction <NUM> may include a transaction output including an encumbrance on the first asset value <NUM> for the benefit of the principal node <NUM>. Once the timeout transaction <NUM> is broadcast to the blockchain network, an encumbrance on the first asset value may be removed in response to a transaction input of a further transaction having the signature of the principal node (σ(S)). Note that the timeout transaction <NUM> is held in abeyance from being successfully broadcast and validated on the blockchain network until the first time-lock threshold (s1) has passed. In some implementations, operations for forming the commitment channel <NUM> may prevent the node <NUM> from broadcasting the commitment transaction <NUM> to the blockchain network until the node <NUM> appends or concatenates the signature of the node (σ(Ui)) to timeout transaction <NUM>.

In some implementations, once the timeout transaction <NUM> is successfully broadcast and validated on the blockchain network, the unencumbered first asset value <NUM> may be distributed to the other nodes as compensation or as a remedy for the lost opportunity to generate the collective private key based on a set of private key shares. Recall that each of the other nodes <NUM> depend on every other node <NUM> to reveal a respective private key share on the blockchain, such that the collective private key (p) may be generated for assembling a document crypto private key li = p + qi. The document crypto private key may be utilized for unencrypting encrypted documents originating from respective nodes Ui.

In some implementations, the timeout transaction <NUM> that has been signed by both the node <NUM> and the principal node <NUM> may be stored in the data store <NUM>, such that a plurality of nodes <NUM> (<FIG>) to the document repository system <NUM> may take note that each of the nodes <NUM> in the plurality of nodes may be subject to a penalty if the respective node <NUM>: (<NUM>) broadcasts a commitment transaction <NUM> to the blockchain network; and (<NUM>) fails to broadcast at least a rescind transaction <NUM> or a reveal transaction <NUM> that is signed by the principal node <NUM> prior to the first time-lock threshold (s1).

At <NUM>, the node <NUM> may broadcast the commitment transaction <NUM> associated with that node <NUM> to the blockchain network. The commitment channel <NUM> can be formed when the commitment transaction <NUM> is broadcast to the blockchain network. Based at least on the above examples, said node <NUM> and the principal node <NUM> may conduct operations <NUM> to <NUM>, described herein, for forming the commitment channel <NUM>.

Further, to ensure that the node <NUM> is not penalized with a value equivalent to the first asset value <NUM> (<FIG>), at <NUM>, the node <NUM> may broadcast to the blockchain network either a rescind transaction <NUM> or a reveal transaction <NUM> prior to the first time-lock threshold (s1).

Reference is now made to <FIG>, which illustrates, in flowchart form, a method <NUM> implemented at a node <NUM> (e.g., a first node = node i) of <FIG> for submitting a document to the document repository system <NUM> (<FIG>), in accordance with an example of the present application. The method <NUM> may include operations that may be carried out by one or more processors of the node <NUM> of the blockchain network. The method <NUM> may be carried out by the node <NUM> for submitting a document to the document repository system <NUM> for consideration by the principal node <NUM> (<FIG>) or by any other node participating in the document repository system <NUM>.

At operation <NUM>, the processor may retrieve a private key share (p^i) based on operations of a threshold secret sharing protocol for distributing or assigning private key shares to respective nodes in the document repository system <NUM>. Examples of the threshold secret sharing protocol include the Shamir method, described above; however, other methods similar to the threshold secret sharing protocol can be contemplated. As described, a collective private key (p) of a collective private-public key pair (p, P) may be used for generating a document crypto private key (li = p + qi) for decrypting an encrypted document EncL(Doci) stored at an accessible data store <NUM> (<FIG>).

At operation <NUM>, the processor may compute a nodal private-public key pair (qi, Qi). The computed nodal private-public key pair may be used as a "one-time code". For example, the nodal public key (Qi) of the nodal private-public key pair may be used for generating a document crypto public key (Li = P + Qi). The nodal private key (qi) may be broadcast via a reveal transaction <NUM> (<FIG>). Thus, once the nodal private key is made public to the blockchain network, the node <NUM> may refrain from using said nodal private-public key pair for future encryption operations within the document repository system <NUM>.

At operation <NUM>, the processor may generate the document crypto public key (Li = P + Qi). In some examples, the processor may generate the document crypto public key by combining a collective public key (retrieved via operations of a threshold secret sharing protocol) and a nodal public key of the node <NUM>.

At operation <NUM>, the processor may encrypt the document that the node <NUM> is tasked with submitting to the document repository system <NUM>. The encrypted document may be stored at the data store <NUM>. Any of the nodes in the document repository system <NUM> may access the data store <NUM> for retrieving encrypted documents stored therein. However, a node may not discern contents of any one of the encrypted documents until the document of interest is decrypted with a document crypto private key. The document crypto private key includes a combination of the collective private key and a nodal private key associated with the document of interest. The node <NUM> may generate the collective private key (p) once a threshold number of nodes participating in the document repository system <NUM> reveal a respective private key share on the blockchain via a rescind transaction <NUM> or a reveal transaction <NUM>. In some examples, the encrypted document may not be recorded via transactions broadcasted to the blockchain network. Rather, a hash of the document or the encrypted document may be recorded on one or more transactions described herein that may be broadcast to the blockchain network.

At operation <NUM>, the processor may generate one or more transactions for a first commitment channel <NUM> (<FIG>). In an example implementation, the processor may generate the one or more transactions for the first commitment channel <NUM> for the node <NUM> based on the operations described by the sequence diagram <NUM> in <FIG>. The first commitment channel <NUM> can be determined to be formed in a subsequent operation when a commitment transaction <NUM> (<FIG>) has been generated, when at least one of a rescind transaction <NUM> or a reveal transaction <NUM> has been signed by the principal node <NUM> (<FIG>), and when that commitment transaction <NUM> has been broadcast to the blockchain network. In some example implementations, a commitment channel <NUM> may be formed when each of the described transactions by <FIG> have been generated and signed by the node <NUM> and by the principal node <NUM> and when the commitment transaction <NUM> is broadcast to the blockchain network.

At operation <NUM>, in response to receiving a valid rescind transaction or a reveal transaction signed by the principal node, the processor may broadcast the commitment transaction <NUM> to the blockchain network, such that the commitment transaction <NUM> may be validated by mining nodes of the blockchain network. In some examples, once the processor broadcasts the commitment transaction <NUM> to the blockchain network, the processor forms the commitment channel <NUM>. In some implementations, broadcasting the commitment transaction <NUM> to the blockchain network may be akin to submitting the document of the node <NUM> to the document repository system <NUM> for consideration by the principal node or the other nodes participating in the document repository system <NUM>.

The processor may refrain from broadcasting the commitment transaction <NUM> to the blockchain network until such time that a valid rescind transaction or a reveal transaction is signed by the principal node <NUM>. As described herein, a rescind transaction or a reveal transaction may include transaction outputs for removing a encumbrance on at least a portion of a first asset value <NUM> (<FIG>, <FIG>), such that a portion of the first asset value <NUM> may be returned to the node <NUM> as an UTXO in exchange for contribution of at least the private key share of the node <NUM> to the set of private key shares.

In some examples, if the processor does not receive a valid rescind transaction or a reveal transaction signed by the principal node, the processor may halt formation of the commitment channel and the processor may avoid broadcasting a commitment transaction to the blockchain network.

Once an indication has been made by the node <NUM>, via broadcast of the commitment transaction, that the processor may be submitting a document for consideration in the document repository system <NUM>, at operation <NUM>, the processor may broadcast a rescind transaction or a reveal transaction to the blockchain network prior to a first time-lock threshold (s1). The first time-lock threshold (s1) may be established by the principal node or any other node of the document repository system <NUM>. The first time-lock threshold may be setup to govern a period of time for document submission and private key share submission by respective nodes to the document repository system <NUM>.

The processor may broadcast the reveal transaction to the blockchain network if that node intends to have that document considered. The document may be considered by the principal node or any other nodes of the system for selection. For example, the document may be a submission to a contest that is managed by the document management system <NUM>. In some other examples, the document may be a legal document submission to a court that is managed by the document management system <NUM>, where legal document submission deadlines may be prescribed by statute. In other examples, the document may be a tender submission to a government agency for award of an infrastructure project and that is managed by the document management system <NUM>. By limiting revelation of document contents to when a temporal time threshold has been passed, a tendering process may promote tender submissions that may yield a competitive process (e.g., best cost, etc.).

In some examples, the processor may broadcast the rescind transaction to the blockchain network if that node intends to have that document removed from consideration, but intends to reveal the private key share of that node such that a requisite set of private key shares may be collected for generating a collective private key (p) for document decryption. Note that a node may be incentivized to broadcast the rescind transaction to the blockchain network, rather than simply not broadcast any valid subsequent transaction, at least because broadcasting the rescind transaction: (<NUM>) reveals the private key share of that node on the blockchain; and (<NUM>) encumbers a portion of the first asset value for the benefit of that node.

If that node were to simply not broadcast any valid subsequent transaction, the first asset value would be encumbered (via a timeout transaction broadcast by the principal node) for the benefit of the principal node or for the benefit for each of the other nodes participating in the document repository system <NUM>.

Reference is now made to <FIG>, which illustrates, in flowchart form, a method <NUM> implemented at a node <NUM> (e.g., a first node = node i) of <FIG> of verifying a document submitted to the document repository system <NUM> (<FIG>), in accordance with an example of the present application. The method <NUM> may include operations that may be carried out by one or more processors of the node <NUM> of the blockchain network. The method <NUM> may be carried out by the node <NUM> for verifying previously submitted documents to the document repository system <NUM>.

At operation <NUM>, the processor may retrieve from the blockchain a set of private key shares associated with a document (Doci) or an encrypted document EncL(Doci). The set of private key shares may include private key shares (e.g., (p̂<NUM>, p̂<NUM>,. , p̂n-<NUM>, p̂n)), where each private key share in the set may be retrieved based on reveal transactions or rescind transactions broadcasted on the blockchain network by respective nodes that are participating in verifying that respective document (Doci).

At operation <NUM>, in response to determining that the quantity of private key shares is greater than a private key share threshold, the processor may generate the collective private key (p) of the collective private-public key pair (p, P) from the retrieved set of private key shares (e.g., (p̂<NUM>, p̂<NUM>,. , p̂n-<NUM>, p̂n)). In some examples, where n nodes may be participating in verifying the document submitted to the document repository system <NUM>, the private key share threshold may be n private key shares. That is, to enable any of the nodes <NUM> or the principal node <NUM> to verify a document in the data store <NUM> (<FIG>), each of the n participating nodes must reveal their respective private key share p̂n on the blockchain. If one or more of the n nodes fails to reveal their respective private key share (e.g., via broadcasting a rescind transaction or a reveal transaction), the processor may be unable to generate the collective private key (p) for generating a document crypto private key (li = p + qi). If one or more of the n nodes fails to reveal their respective private key, none of the nodes <NUM> participating in the document repository system <NUM> may be able to unencrypt the encrypted document stored at the data store <NUM>. That is, without the collaboration / contribution of private key shares from each of the n nodes, none of the nodes may decrypt and verify encrypted documents.

In some examples, where n nodes may be participating in verifying the document submitted to the document repository system <NUM>, the private key share threshold may be less than the number of nodes participating in the document repository system <NUM>. Thus, if one or more of the n nodes fails to reveal their respective private key, but if the quantity of private key shares is greater than the private key share threshold, the processor may be able to generate the collective private key (p) for generating the document crypto private key (li = p + qi). In some implementations, it may be desirable to provide the private key share threshold as less than the number of nodes participating in the document repository system <NUM> to account for nodes that may lose a connection to the blockchain network or to account for a limited number of nodes that may fail to broadcast a reveal transaction or a rescind transaction prior a first time-lock threshold (s1).

In some examples, if the processor fails to retrieve from the blockchain a requisite quantity of private key shares that is greater than the private key share threshold prior to the first time-lock threshold (s1), the processor may be unable to unencrypt the encrypted document stored at the data store <NUM> at least because the collective private key may not be generated. In such a circumstance, in some implementations, the principal node <NUM> (<FIG>) may broadcast the timeout transaction <NUM> (<FIG>) to the blockchain network and an encumbrance on the first asset value <NUM> (<FIG>) may be removed and, subsequently, included in a locking script in favour of the principal node <NUM> or other nodes in the document repository system <NUM>.

If the processor is able to generate the collective private key from the retrieved set of private key shares, at operation <NUM>, the processor may decrypt the encrypted document (EncL(Doci)) by: (<NUM>) generating the document crypto private key (li = p + qi); and (<NUM>) unencrypting the encrypted document using the document crypto private key.

In some implementations, the processor may conduct operations for hashing (e.g., H(Θ)) the unencrypted document and verifying the hash of the document (H(Doci)) with a hash of the document retrieved from the broadcasted commitment transaction associated with the node that originated the document. Note that once the requisite quantity of private key shares have been revealed on the blockchain, any of the nodes <NUM> in the document repository system <NUM> may unencrypt encrypted documents (EncL(Doci)) based on the combination of: (<NUM>) generated collective private key from the set of private key shares; and (<NUM>) a nodal private key (qi) provided by the respective nodei associated with the document (Doci). In some implementations, each node participating in the document repository system <NUM> may perform operations for: (<NUM>) decrypting the encrypted document; (<NUM>) hashing the decrypted document; and (<NUM>) verifying that a hash of the decrypted document corresponds to a hash of the document retrieved from a broadcasted commitment transaction associated with the node that originated that document.

Reference is now made to <FIG>, which illustrates, in block diagram form, a simplified node <NUM>, in accordance with an example of the present application. The node <NUM> includes a processor <NUM>, which may include one or more microprocessors, application specific integrated circuits (ASICs), microcontrollers, or similar computer processing devices. The node <NUM> may further include memory <NUM>, which may include persistent and non-persistent memory, to store values, variables, and in some instances processor-executable program instructions, and a network interface <NUM>.

The node <NUM> may include a processor-executable blockchain application <NUM> containing processor-executable instructions that, when executed, cause the processor <NUM> to carry out one or more of the functions or operations described herein.

Claim 1:
A computer-implemented method of verifying a digital resource by a plurality of nodes (<NUM>) and a principal node (<NUM>) in a blockchain network, the plurality of nodes (<NUM>) having respective private key shares, where a collective private key of a collective private-public key pair is based on a set of the respective private key shares, and where a first node of the plurality of nodes has a first nodal private-public key pair, the method comprising, at the first node:
generating a digital resource crypto public key by combining a first nodal public key of the first nodal private-public key pair and a collective public key of the collective private-public key pair;
encrypting the digital resource using the digital resource crypto public key;
generating one or more blockchain transactions for a first commitment channel (<NUM>) by:
generating a commitment transaction having a commitment transaction output locked by a private key share of the first node,
generating a valid subsequent transaction having the commitment transaction output as an input and including the private key share of the first node, and
receiving the valid subsequent transaction signed by the principal node; and
broadcasting the commitment transaction (<NUM>) to the blockchain network.