IP Library Granted Patent US 12,307,439
Granted Patent B2
US 12,307,439 · App. 17/285,249 · Granted May 20, 2025

Secure digital wallet processing system

Inventors: Sercan Karaoglu (Rotterdam, NL); Mohammed Chakib Bouda (Schiedam, NL)
Assignee: Bell Identification B.V.
G06Q20/3674G06Q20/363G06Q20/3823G06Q20/3827G06Q20/3829G06Q2220/00
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,307,439
App. No.
17/285,249
Granted
May 20, 2025
Kind
B2
Abstract

Systems and methods for implementing a secure digital wallet processing system. An example method comprises: receiving, by a computer system, a distributed ledger transaction and a public address; retrieving, from a key management system, a private key corresponding to the public address, wherein the key management system comprises a hardware security module (HSM) that generated the public address from the private key; signing the distributed ledger transaction by the private key; and providing the signed distributed ledger transaction to a distributed ledger.

Claims (49)

1. A computer-implemented method of a secure digital wallet processing system, the method comprising:

retrieving, by a hardware security module (HSM) of the secure digital wallet processing system from a cold storage included in the secure digital wallet processing system, a private key associated with a customer, wherein the secure digital wallet processing system further includes a warm storage;

generating, using the HSM, a public address associated for the customer from the private key, by performing by the HSM a cryptographic operation on the private key retrieved by the HSM from the cold storage, wherein the public address is not generated from a public key;

encrypting, by the HSM, the private key and the public address;

storing the encrypted public address in association with the encrypted private key in a key management system database of the secure digital wallet processing system;

receiving a distributed ledger transaction request including an authentication token and a customer identifier, the customer identifier being the public address associated with the customer;

validating the distributed ledger transaction request using the received public address by an authenticator that accesses a customer identifier public address database;

in response to the validating the distributed ledger transaction request, retrieving using the received public address, from the key management system database, the encrypted private key;

decrypting the encrypted private key;

signing, using the HSM, a distributed ledger transaction by the decrypted private key; and

providing the signed distributed ledger transaction to a distributed ledger.

2. The method of claim 1 , wherein the distributed ledger transaction is one of: a cryptocurrency buy order, a cryptocurrency sell order, a cryptocurrency transfer to another public address, or a code implementing a smart contract.

3. The method of claim 1 , further comprising:

generating the public address and providing the public address to a user prior to receiving the distributed ledger transaction.

4. The method of claim 1 , further comprising:

prior to the retrieving, storing the private key and a corresponding public key in the cold storage.

5. The method of claim 1 , further comprising:

performing by the HSM the cryptographic operation on the private key in the warm storage.

6. A computer system, comprising:

a memory; and

a processor coupled to the memory, wherein the memory comprises executable instructions which, when executed by the processor, cause the processor to perform a method including:

retrieving, by using a hardware security module (HSM) of the computer system from a cold storage included in the computer system, a private key associated with a customer, wherein the computer system further comprises a warm storage;

generating, by using the HSM, a public address associated or the customer, from the private key, by performing by the HSM a cryptographic operation on the private key retrieved by the HSM from the cold storage, wherein the public address is not generated from a public key;

encrypting, by using the HSM, the private key and the public address;

storing the encrypted public address in association with the encrypted private key in a key management system database of the computer system;

receiving a distributed ledger transaction request including an authentication token and a customer identifier, the customer identifier being the public address associated with the customer;

validating the distributed ledger transaction request using the received public address by an authenticator that accesses a customer identifier public address database;

in response to the validating the distributed ledger transaction request, retrieving using the received public address, from the key management system database, the encrypted private key;

decrypting the encrypted private key;

using the HSM to sign a distributed ledger transaction by the decrypted private key; and

providing the signed distributed ledger transaction to a distributed ledger.

7. The computer system of claim 6 , wherein the distributed ledger transaction is one of: a cryptocurrency buy order, a cryptocurrency sell order, a cryptocurrency transfer to another public address, or a code implementing a smart contract.

8. The computer system of claim 6 , wherein the method further includes:

generate the public address and providing the public address to a user prior to receiving the distributed ledger transaction.

9. The computer system of claim 6 , wherein the HSM is included in a key management system of the computer system, the key management system further including at least one of: a warm storage device or a cold storage device.

10. A non-transitory computer-readable storage medium comprising executable instructions that, when executed by a processor of a secure digital wallet processing system, cause the processor to perform a method including:

retrieving, by using a hardware security module (HSM) of the secure digital wallet processing system from a cold storage included in the secure digital wallet processing system, a private key associated with a customer, wherein the secure digital wallet processing system further includes a warm storage;

generating, by using the HSM, a public address associated or the customer, from the private key, by performing by the HSM a cryptographic operation on the private key retrieved by the HSM from the cold storage, wherein the public address is not generated from a public key;

encrypting, by using the HSM, the private key and the public address;

storing the encrypted public address in association with the encrypted private key in a key management system database of the secure digital wallet processing system;

receiving a distributed ledger transaction request including an authentication token and a customer identifier, the customer identifier being the public address associated with the customer;

validating the distributed ledger transaction request using the received public address by an authenticator that accesses a customer identifier public address database;

in response to the validating the distributed ledger transaction request, retrieving using the received public address, from the key management system database, the encrypted private key;

decrypting the encrypted private key;

using the HSM to sign a distributed ledger transaction by the decrypted private key; and

providing the signed distributed ledger transaction to a distributed ledger.

11. The non-transitory computer-readable storage medium of claim 10 , wherein the distributed ledger transaction is one of: a cryptocurrency buy order, a cryptocurrency sell order, a cryptocurrency transfer to another public address, or a code implementing a smart contract.

12. The non-transitory computer-readable storage medium of claim 10 , wherein the method further includes:

generate the public address and providing the public address to a user prior to receiving the distributed ledger transaction.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 14, 2021
From: KARAOGLU, SERCAN; BOUDA, MOHAMMED CHAKIB
To: BELL IDENTIFICATION B.V.
Reel/Frame 055916/0369 →
Continuity (2)
Provisional Application 62748340 · Oct 19, 2018
Related Publication 20210374724A1 · Dec 2, 2021
References Cited (66)
US 10068228B1 · Winklevoss · 2018 [cited by examiner]
US 11139955B1 · So · 2021 [cited by examiner]
US 11308487B1 · Foster · 2022 [cited by examiner]
US 11323274B1 · Bowen · 2022 [cited by examiner]
US 11698979B2 · Hamel · 2023 [cited by examiner]
US 11783323B1 · Winklevoss · 2023 [cited by examiner]
US 20150262176A1 · Langschaedel · 2015 [cited by examiner]
US 20150287026A1 · Yang · 2015 [cited by examiner]
US 20150324789A1 · Dvorak · 2015 [cited by examiner]
US 20150363772A1 · Ronca · 2015 [cited by examiner]
US 20160092988A1 · Letourneau · 2016 [cited by examiner]
US 20160292672A1 · Fay · 2016 [cited by examiner]
US 20160344543A1 · Alness · 2016 [cited by examiner]
US 20160350728A1 · Melika et al. · 2016 [cited by applicant]
US 20170316410A1 · Smith · 2017 [cited by examiner]
US 20170372417A1 · Gaddam et al. · 2017 [cited by applicant]
US 20180131517A1 · Block et al. · 2018 [cited by applicant]
US 20180367316A1 · Cheng · 2018 [cited by examiner]
US 20190268165A1 · Monica · 2019 [cited by examiner]
US 20190280864A1 · Cheng · 2019 [cited by examiner]
US 20190318356A1 · Martin · 2019 [cited by examiner]
US 20190325408A1 · Goroff · 2019 [cited by examiner]
US 20190356481A1 · Spector · 2019 [cited by examiner]
US 20200013052A1 · Fok · 2020 [cited by examiner]
US 20200028675A1 · Gancarz · 2020 [cited by examiner]
US 20200067907A1 · Avetisov · 2020 [cited by examiner]
US 20200076606A1 · Burke · 2020 [cited by examiner]
US 20200111080A1 · Metcalfe · 2020 [cited by examiner]
US 20200118095A1 · Fan · 2020 [cited by examiner]
US 20200119917A1 · Christensen · 2020 [cited by examiner]
US 20200162246A1 · Schouppe · 2020 [cited by examiner]
US 20200193420A1 · Vogel · 2020 [cited by examiner]
US 20200344075A1 · Gremaud · 2020 [cited by examiner]
US 20210049591A1 · Lamesh · 2021 [cited by examiner]
US 20210083872A1 · Desmarais · 2021 [cited by examiner]
US 20210110390A1 · Janaudy · 2021 [cited by examiner]
US 20210273814A1 · Lee · 2021 [cited by examiner]
US 20220327525A1 · Tsitrin · 2022 [cited by examiner]
CN 103679444 · 2014 [cited by applicant]
CN 107409123A · 2017 [cited by applicant]
CN 108369703A · 2018 [cited by applicant]
CN 108370318A · 2018 [cited by applicant]
CN 109146481 · 2018 [cited by examiner]
CN 108615154A · 2018 [cited by examiner]
FR 3100678A1 · 2021 [cited by examiner]
KR 20190116838A · 2018 [cited by examiner]
WO 2015094326A1 · 2015 [cited by applicant]
WO WO2021073953A1 · 2021 [cited by examiner]
S. Alapati, “Expert Hadoop Administration: Managing, Tuning, and Securing Spark, YARN, and HDFS,” United Kingdom, 2016, Pearson Education, chapter 8, excerpt (Year: 2016). [cited by examiner]
W. Kinastowski, “Signing Cloud: Towards Qualified Electronic Signature Service in Cloud,” 2013 IEEE 5th International Conference on Cloud Computing Technology and Science, Bristol, UK, 2013, pp. 224-227, doi: 10.1109/Cl… [cited by examiner]
L. Zheng and Y. Zhao, “Research on managing private key of PKI users,” 2011 International Conference on Mechatronic Science, Electric Engineering and Computer (MEC), Jilin, China, 2011, pp. 2411-2414, doi: 10.1109/MEC.2… [cited by examiner]
NIST—Hardware Security Module (HSM), retrieved from https://web.archive.org/web/20201019084610/https://csrc.nist.gov/glossary/term/Hardware_Security_Module_HSM (Year: 2020). [cited by examiner]
Eskandari, Shayan, et al. “A First Look at the Usability of Bitcoin Key Management'. Proceedings 2015 Workshop on Usable Security, Internet Society,”, 2015, https://doi.org10.14722/usec.2015.23015. USEC 2015. (Year: 201… [cited by examiner]
Pal et al. “Key Management for Blockchain Technology,” ICT Express, vol. 7, No. 1, 2021, pp. 76-80, https://doi.org10.1016/j.icte.2019.08.002. Available online Aug. 21, 2019 (Year: 2019). [cited by examiner]
Translation of Foreign reference FR3100678A1 (Espacenet) (Year: 2019). [cited by examiner]
Voegtlin, “Electrum documentation Release 2.5,” retrieved from https://web.archive.org/web/20161206224326/https://media.readthedocs.org/pdf/electrum/latest/electrum.pdf on Dec. 6, 2016 (Year: 2016). [cited by examiner]
EPO Machine translation of Foreign Application CN109146481 (Year: 2018). [cited by examiner]
Application No. SG11202103833X , Written Opinion, Mailed On Nov. 1, 2022, 9 pages. [cited by applicant]
Application No. PCT/US2019/057062 , International Search Report and Written Opinion, Mailed On Jan. 10, 2020, 7 pages. [cited by applicant]
Application No. EP19872361.1 , Extended European Search Report, Mailed On Nov. 17, 2021, 8 pages. [cited by applicant]
EP19872361.1 , “Intention to Grant”, May 9, 2023, 9 pages. [cited by applicant]
Application No. CN201980068910.4 , Office Action, Mailed On Dec. 6, 2023, with English Translation, 23 pages. [cited by applicant]
Application No. CN201980068910.4 , Office Action, Mailed On Jul. 3, 2023, with English Translation, 20 pages. [cited by applicant]
Application No. CN201980068910.4 , Office Action, Mailed On Feb. 28, 2024, 18 pages with English Translation. [cited by applicant]
Application No. CN201980068910.4 , Office Action, Mailed On Dec. 6, 2023, 23 pages with English Translation. [cited by applicant]
Wang , “E-Government Planning and Design”, National School of Administration Press, Jun. 30, 2013, pp. 218-219. [cited by applicant]