US 11,893,582 B2
Forcing the injection of a previous transaction's bytecode into a blockchain transaction
Ying Chan, Cambridge (GB); and Dean Kramer, London (GB)
Assigned to nChain Licensing AG, Zug (CH)
Appl. No. 16/615,806
Filed by nChain Licensing AG, Zug (CH)
PCT Filed May 14, 2018, PCT No. PCT/IB2018/053337
§ 371(c)(1), (2) Date Nov. 21, 2019,
PCT Pub. No. WO2018/215873, PCT Pub. Date Nov. 29, 2018.
Claims priority of application No. 1708185 (GB), filed on May 22, 2017; application No. 1708190 (GB), filed on May 22, 2017; application No. 1708192 (GB), filed on May 22, 2017; application No. 1708196 (GB), filed on May 22, 2017; application No. 1708198 (GB), filed on May 22, 2017; and application No. 1708200 (GB), filed on May 22, 2017.
Prior Publication US 2020/0099529 A1, Mar. 26, 2020
Int. Cl. H04L 9/32 (2006.01); G06Q 20/38 (2012.01); G06Q 20/06 (2012.01); G06Q 20/36 (2012.01); H04L 9/06 (2006.01); G06F 16/23 (2019.01); H04L 9/30 (2006.01); G06F 21/64 (2013.01); G06F 21/62 (2013.01); G06Q 10/10 (2023.01); H04L 9/00 (2022.01)
CPC G06Q 20/389 (2013.01) [G06F 16/2379 (2019.01); G06F 21/6209 (2013.01); G06F 21/645 (2013.01); G06Q 20/065 (2013.01); G06Q 20/0658 (2013.01); G06Q 20/36 (2013.01); G06Q 20/3674 (2013.01); G06Q 20/3825 (2013.01); G06Q 20/3829 (2013.01); H04L 9/0637 (2013.01); H04L 9/0643 (2013.01); H04L 9/30 (2013.01); H04L 9/3236 (2013.01); H04L 9/3239 (2013.01); H04L 9/3247 (2013.01); G06Q 10/10 (2013.01); G06Q 2220/00 (2013.01); H04L 9/3066 (2013.01); H04L 9/3252 (2013.01); H04L 9/50 (2022.05); H04L 2209/56 (2013.01)] 15 Claims
OG exemplary drawing
 
1. A method comprising:
receiving, at a node in a blockchain network, a first transaction to validate, the first transaction including a first script that, as a result of being executed, causes the node to at least:
obtain a first set of field values corresponding to the first transaction; and
obtain a second set of field values corresponding to a particular transaction;
obtaining a second transaction, the second transaction having been validated and including a second script that, as a result of being executed, causes the node to at least:
obtain the first set of field values and the second set of field values of the particular transaction supplied as a result of execution of the first script;
extract a transaction identifier from the first set of field values; and
determine, based at least in part on the second set of field values, that the particular transaction corresponds to the transaction identifier;
validating the first transaction by executing the first script and the second script and wherein the second script constrains an identity of a source of the first transaction.