IP Library › Granted Patent US 12,640,934
Granted Patent B2
US 12,640,934 · App. 18/858,177 · Granted May 26, 2026

Non-native blockchain signatures

Inventor: Paul Germouty (London, GB)
Assignee: nChain Licensing AG
H04L9/3252G06Q20/38215G06Q20/3825G06Q20/3829G06Q20/401H04L9/0825H04L9/3236H04L9/3249H04L9/3268H04L9/50
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,640,934
App. No.
18/858,177
Granted
May 26, 2026
Kind
B2
Abstract

A computer-implemented method for enabling non-native blockchain signatures to be verified in-script, wherein the method is performed by a first party and comprises: obtaining a second blockchain transaction, wherein the second blockchain transaction references a first blockchain transaction; generating a first signature based on at least the second blockchain transaction, wherein a first private key used to generate the first signature is set equal to one; generating a second signature based on the first signature, wherein the first signature is a native blockchain signature and the second signature is a non-native blockchain signature; including the first signature and the second signature in an unlocking script of the second blockchain transaction for verification when the unlocking script is executed together with a locking script of the first blockchain transaction; and causing the second blockchain transaction to be submitted to a blockchain network.

Claims (39)

1 . A computer-implemented method for enabling non-native blockchain signatures to be verified in-script, wherein the method is performed by a first party and comprises:

obtaining a second blockchain transaction, wherein the second blockchain transaction references a first blockchain transaction;

generating a first signature based on at least the second blockchain transaction, wherein a first private key used to generate the first signature is set equal to one;

generating a second signature based on a message comprising the first signature, wherein the first signature is a native blockchain signature and the second signature is a non-native blockchain signature;

including the first signature and the second signature in an unlocking script of the second blockchain transaction for verification when the unlocking script is executed together with a locking script of the first blockchain transaction; and

causing the second blockchain transaction to be submitted to a blockchain network.

2 . The method of claim 1 , wherein the first signature is an Elliptic Curve Digital Signature Algorithm (ECDSA) signature.

3 . The method of claim 1 , wherein an ephemeral key used to generate the first signature is set equal to one.

4 . The method of claim 1 , wherein the second signature is one of:

a quantum resistant signature,

a Rabin signature,

a Schnorr signature.

5 . The method of claim 1 , wherein the second signature is an identity-based signature.

6 . The method of claim 5 , wherein the first party has a first identifier, a second private key, and a second public key, wherein the second private key is based on the first identifier, and wherein the second signature is based on the first signature, the first identifier, the second private key.

7 . The method of claim 6 , wherein the first identifier comprises at least part of one or more of the following: a name, an address, a date of birth, an email address, a username, a passport number, a driving license number, a national insurance number.

8 . The method of claim 6 , wherein the second public key comprises a set of parameters, the set of parameters including at least a prime number, an elliptic curve point generator of order of the prime number, a first hash function, a second hash function, and wherein the second private key is generated by:

computing a first elliptic curve point based on a first random value and the elliptic curve generator, wherein the first elliptic curve point is a first value of the second private key;

computing a second value of the second private key based on the first elliptic curve point, a master secret key, a first hash generated by hashing the first elliptic curve point and the first identifier with the first hash function.

9 . The method of claim 8 , wherein the second signature is generated by:

computing a first value of the second signature based on a second random value and the elliptic curve generator;

computing a second value of the second signature based on the second random value, the first value of the second private key, a second hash generated by hashing the first identifier, the first value of the second signature, and the first signature; and

setting a third value of the second signature as the first value of the second private key.

10 . The method of claim 1 , wherein the locking script of the first blockchain transaction represents a certificate, and wherein submitting the second blockchain transaction represents a revocation of the certificate.

11 . A computer-implemented method of generating blockchain transactions for verifying non-native blockchain signatures in-script, wherein the method is performed by a second party and comprises:

generating a first blockchain transaction comprising a locking script, wherein the locking script comprises a first verification script and a second verification script, wherein when the locking script of the first blockchain transaction is executed together with an unlocking script of a second blockchain transaction, the first verification script is configured to verify a first signature based on a first public key corresponding to a first private key set equal to one, and the second verification script is configured to verify a second signature based on a message comprising the first signature, wherein the first signature is a native blockchain signature and the second signature is a non-native blockchain signature; and

causing the first blockchain transaction to be submitted to a blockchain network.

12 . The method of claim 11 , wherein the second verification script is configured to verify an identity-based signature.

13 . The method of claim 12 , wherein a first party has a first identifier, a second private key, and a second public key, wherein the second private key is based on the first identifier, and wherein the second signature verification script is configured to verify the second signature based on the first identifier, the second public key, and the first signature.

14 . The method of claim 13 , wherein the second public key comprises a set of parameters, the set of parameters including at least a prime number, an elliptic curve point generator of order of the prime number, a first hash function, a second hash function, and a public value corresponding to a master secret key, wherein the second signature comprises a first value, a second value, and a third value, and wherein the second verification script is configured to verify the second signature by:

computing a first verification value based on the first value, a first hash generated by hashing the third value and the first identifier with the first hash function, a second hash generated by hashing the first identifier, the first value, and the first signature with the second hash function, and the public value corresponding to the master secret key;

computing a second verification value based on the second value and the elliptic curve generator; and

verifying that the first verification value corresponds to the second verification value.

15 . The method of claim 13 , wherein the locking script of the first blockchain transaction comprises the first identifier, and wherein the second verification script is configured to verify that the unlocking script of the first blockchain transaction comprises the first identifier.

16 . The method of claim 13 , wherein the locking script of the first blockchain transaction comprises a hash of the first identifier, and wherein the second verification script is configured to verify that the unlocking script of the first blockchain transaction comprises the first identifier by hashing the first identifier and comparing the result with hash of the first identifier.

17 . The method of claim 12 , wherein the locking script comprises a plurality of instances of the second verification script, and wherein when executed, each instance of the second verification script is configured to verify a respective identify-based signature included in the unlocking script of the second blockchain transaction.

18 . The method of claim 12 , wherein the locking script is configured to verify that the unlocking script of the second blockchain transaction comprises an identifier, the identifier having one or more predetermined fields.

19 . A non-transitory computer readable media comprising a computer program and configured so as, when run on one or more processors, the one or more processors perform a method of generating blockchain transactions for verifying non-native blockchain signatures in-script, wherein the method is performed by a second party and comprises:

generating a first blockchain transaction comprising a locking script, wherein the locking script comprises a first verification script and a second verification script, wherein when the locking script of the first blockchain transaction is executed together with an unlocking script of a second blockchain transaction, the first verification script is configured to verify a first signature based on a first public key corresponding to a first private key set equal to one, and the second verification script is configured to verify a second signature based on a message comprising the first signature, wherein the first signature is a native blockchain signature and the second signature is a non-native blockchain signature; and

causing the first blockchain transaction to be submitted to a blockchain network.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 23, 2024
From: GERMOUTY, PAUL
To: NCHAIN LICENSING AG
Reel/Frame 068988/0475 →
Priority Claims (1)
GB 2206039 · Apr 26, 2022 · national
Continuity (1)
Related Publication 20250274292A1 · Aug 28, 2025
References Cited (24)
US 10901983B2 · Zhang · 2021 [cited by examiner]
US 20190305966A1 · Qiu · 2019 [cited by examiner]
US 20220012731A1 · DeRosa-Grund · 2022 [cited by examiner]
US 20220385477A1 · Kravitz · 2022 [cited by examiner]
WO 2023143882A1 · 2023 [cited by applicant]
Ansi, “X9.62-1998, Public Key Cryptography for the Financial Services Industry: The Elliptic Curve Digital Signature Algorithm (ECDSA),” American National Standards Institute , 1998, 128 pages. [cited by applicant]
Boneh D., et al., “Hierarchical Identity Based Encryption with Constant Size Ciphertext,” Advances in Cryptology—EUROCRYPT, Annual International Conference on the Theory and Applications of Cryptographic Techniques, 200… [cited by applicant]
Boneh D., et al., “Identity-Based Encryption from the Weil Pairing,” Advances in Cryptology—CRYPTO, Lecture Notes in Computer Science, 2001, vol. 2139, pp. 213-229. [cited by applicant]
Chatterjee S., et al., “Galindo-Garcia Identity-Based Signature, Revisited,” Information Security and Cryptology—ICISC 2012, vol. 7839, 27 pages. [cited by applicant]
Cooper D., et al., “Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile,” RFC 5280, [Online], May 2008, 151 pages, Available: https://datatracker.ietf.org/doc/html/rfc5280. [cited by applicant]
Ding J., et al., “Rainbow, a New Multivariable Polynomial Signature Scheme,” Applied Cryptography and Network Security (ACNS 2005), LNCS 3531, 2005, pp. 164-175. [cited by applicant]
Ducas L., et al., “CRYSTALS-Dilithium: A Lattice-Based Digital Signature Scheme,” IACR Transactions on Cryptographic Hardware and Embedded Systems, 2018, pp. 1-31. [cited by applicant]
Fouque P-A., et al., “Falcon: Fast-Fourier Lattice-based Compact Signatures over NTRU,” Submission to the NIST's Post-Quantum Cryptography Standardization Process, 2018, 75 pages. [cited by applicant]
Fuchsbauer G., et al., “Blind Schnorr Signatures and Signed ElGamal Encryption in the Algebraic Group Model,” Advances in Cryptology-EUROCRYPT 2020: 39th Annual International Conference on the Theory and Applications of… [cited by applicant]
Galindo D., et al., “A Schnorr-Like Lightweight Identity-Based Signature Scheme,” Progress in Cryptology—AFRICACRYPT 2009, vol. 5580, pp. 135-148. [cited by applicant]
Gentry C., et al., “Hierarchical ID-Based Cryptography,” Advances in Cryptology—ASIACRYPT 2002: 8th International Conference on the Theory and Application of Cryptology and Information Security, 2002, pp. 548-566. [cited by applicant]
Joux A., “A One Round Protocol for Tripartite Diffie-Hellman,” Algorithmic No. Theory (ANTS 2000), LNCS 1838, 2000, pp. 385-393. [cited by applicant]
Kiltz E., et al., “Identity-Based Signatures,” In Identity-based Cryptography, 2009, vol. 2, 17 pages. [cited by applicant]
Koblitz N., et al., “Critical Perspectives on Provable Security: Fifteen Years of Another Look Papers,” Cryptology ePrint Archive, 2019, 47 pages. [cited by applicant]
McCurley K.S., “The Discrete Logarithm Problem,” In Proceedings of Symposia in Applied Mathematics, 1990, vol. 42, pp. 49-74. [cited by applicant]
Nick J., et al., “MuSig2: Simple Two-Round Schnorr Multi-Signatures,” Annual International Cryptology Conference. Cham: Springer International Publishing, 2021, 50 pages. [cited by applicant]
Ong H., et al., “Efficient Signature Schemes Based on Polynomial Equations,” Advances in Cryptology—CRYPT0 '84, LNCS 196, 1985, pp. 37-46. [cited by applicant]
Shamir A., “Identity-based Cryptosystems and Signature Schemes,” Advances in Cryptology—CRYPT0 '84, LNCS 196, 1985, pp. 47-53. [cited by applicant]
Tartan C., et al., “A Scalable Bitcoin-based Public Key Certificate Management System,” In Proceedings of the 18th International Conference on Security and Cryptography (SECRYPT) 2021, pp. 548-559. [cited by applicant]