Protocol flow for notarizing a transaction
US-2020082362-A1 · Mar 12, 2020 · US
US11263605B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11263605-B2 |
| Application number | US-201815933283-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 22, 2018 |
| Priority date | Mar 22, 2018 |
| Publication date | Mar 1, 2022 |
| Grant date | Mar 1, 2022 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system for confirming an authorization to consume an output of a transaction based on multiple signatures with different authority weights is provided. The system confirms the authorization to consume the output when the combined authority weights of one or more authorities that provide their authorizations satisfy a threshold weight. The authority weight for each authority and the threshold weight are identified in an authorization specification that specifies the criterion for the authorization of a matter. The authorization specification also specifies authorization verification information for each authority. When the sum of the authority weights of the authorities whose authorizations have been verified is greater than or equal to the threshold weight, the system confirms the authorization to consume the output.
Opening claim text (preview).
I claim: 1. One or more computing systems for confirming an authorization of a transaction to consume an output of a prior transaction comprising an authorization specification of the prior transaction stored in a distributed ledger, wherein the authorization specification comprises a tree structure comprising a root node and a plurality of child nodes of the root node of the authorization specification, wherein each of the plurality of child nodes is either a leaf node or a non-leaf node, wherein the root node of the authorization specification comprises a threshold weight, each leaf node comprises an authority weight and a public key, wherein each non-leaf node has at least one descendant child leaf node, the one or more computing systems comprising: one or more processors; one or more memories; a check authorization component; a receive consume multi-signature transaction component configured to: receive the transaction, wherein the transaction comprises signatures; extract one or more signatures from the received transaction; extract the authorization specification from the prior transaction; store the extracted authorization specification in the one or more memories; and invoke the check authorization component for the root node of the authorization specification, wherein the invoking of the check authorization component further comprises passing an indication of the root node of the authorization specification to the check authorization component; wherein the check authorization component is configured to: initialize a first total weight variable for the root node of the authorization specification; select a first leaf node that is a child node of the root node of the authorization; perform a verification check on a signature of the first leaf node based on the extracted signatures; in response to determining that the signature of the first leaf node has been verified, increment the first total weight variable for the root node of the authorization specification by an authority weight of the first leaf node; select a non-leaf node that is a child node of the root node of the authorization specification; initialize a second total weight variable for the non-leaf node; select a second leaf node that is a child node of the non-leaf node; perform a verification check on a signature of the second leaf node based on the extracted signatures; in response to determining that authorization was passed for the second leaf node, increment the second total weight variable for the non-leaf node by an authority weight of the second leaf node; determine whether the incremented second total weight variable for the non-leaf node exceeds a threshold weight of the non-leaf node; and in response to determining that the incremented second total weight variable for the non-leaf node exceeds the threshold weight of the non-leaf node, increment the first total weight variable for the root node of the authorization specification by an authority weight of the non-leaf node; determine whether the incremented first total weight variable for the root node of the authorization specification is greater than or equal to a to the threshold weight of the root node of the authorization specification; and in response to determining that the incremented first total weight variable for the root node of the authorization specification is greater than or equal to the threshold weight of the root node of the authorization specification, send, to the receive consume multi-signature transaction component, an indication that the authorization of the transaction has been confirmed; and wherein the receive consume multi-signature transaction component is further configured to: receive, from the check authorization component, the indication that the authorization of the transaction has been confirmed; and record the transaction on the distributed ledger in response to receiving the indication that the authorization of the transaction has been confirmed. 2. The one or more computing systems of claim 1 , further comprising: a component configured to record the prior transaction with the authorization specification in the distributed ledger. 3. The one or more computing systems of claim 2 , wherein the distributed ledger is a blockchain. 4. The one or more computing systems of claim 2 , wherein the prior transaction includes a script with an instruction for confirming authorization based on multiple signatures, wherein the script includes instructions for summing authority weights associated with the multiple signatures and wherein the instruction for confirming authorization based on the multiple signatures includes comparing the summed authority weights associated with the multiple signatures to at least one threshold weight. 5. The one or more computing systems of claim 2 , wherein authority weights of at least two sibling nodes of the authorization specification are different. 6. The one or more computing systems of claim 2 , wherein at least one of the extracted signatures is a hash of the prior transaction encrypted with a private key of a private/public key pair. 7. The one or more computing systems of claim 1 , wherein the distributed ledger is a blockchain. 8. The one or more computing systems of claim 1 , wherein at least two nodes of the authorization specification have different authority weights. 9. The one or more computing systems comprising of claim 1 , further comprising a check constraints component. 10. A method, performed by one or more computing systems comprising one or more processors and one or more memories, wherein the one or more memories store a receive consume multi-signature transaction component and a check authorization component, for confirming an authorization of a transaction to consume an output of a prior transaction comprising an authorization specification of the prior transaction stored in a distributed ledger, wherein the authorization specification comprises a tree structure comprising a root node and a plurality of child nodes of the root node of the authorization specification, wherein each of the plurality of child nodes is either a leaf node or a non-leaf node, wherein the root node of the authorization specification comprises a threshold weight, each leaf node comprises an authority weight and a public key, wherein each non-leaf node has at least one descendant child leaf node, the method comprising: receiving, by the receive consume multi-signature transaction component, the transaction, wherein the transaction comprises signatures; extracting, by the receive consume multi-signature transaction component, one or more signatures from the received transaction; extracting, by the receive consume multi-signature transaction component, the authorization specification from the prior transaction; storing, by the receive consume multi-signature transaction component, the extracted authorization specification in the one or more memories; invoking, by the receive consume multi-signature transaction component, the check authorization component for the root node of the authorization specification, wherein the invoking of the check authorization component further comprises passing an indication of the root node of the authorization specification to the check authorization component; initializing, by the check authorization component, a first total weight variable for the root node of the authorization specification; selecting, by the check authorization component, a first leaf node that is a child node of the root node of the authorization specification; performing, by the check authorization component, a verification check on a signature of the first leaf node based on the e
Use of message hashing · CPC title
Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists · CPC title
involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] · CPC title
e-cash managed locally · CPC title
Use of electronic signatures · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.