IP Library Granted Patent US 12,511,642
Granted Patent B2
US 12,511,642 · App. 18/213,762 · Granted Dec 30, 2025

Using a conversation interface to transfer digital assets

Inventors: Pavan Agarwal (Dorado, PR); Gabriel Albors Sanchez (San Juan, PR); Jonathan Ortiz Rivera (San Juan, PR); Thomas Smith (Guaynabo, PR)
Assignee: Celligence International LLC
G06Q20/36G06Q20/123G06Q20/363G06Q20/3821G06Q20/3829G06Q20/4014
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,511,642
App. No.
18/213,762
Granted
Dec 30, 2025
Kind
B2
Abstract

Systems and methods are provided for facilitating digital asset transfer via natural language commands using a conversation or chat interface associated with a digital wallet application. The digital wallet owner may exchange commands with an assistant user. The assistant user may comprise an automated software agent. The digital wallet owner may transfer digital assets to a recipient's digital wallet identified by command to the assistant user. The transfer command may comprise the recipient's name preceded with a “@” notation.

Claims (37)

1 . A method for transferring a digital asset using natural language commands, the method comprising:

establishing, by a processor, a first digital wallet in a data store connected to the processor;

receiving, by the processor, a first user name of a first user for the first digital wallet from a first user device;

identifying the first digital wallet associated with the first user by using an @map function using the first user name, wherein the @map function resolves user names to public addresses of digital wallets that correspond to the user names without requiring entry of a full cryptographic address;

upon identifying the first digital wallet, by the processor, logging the first user device into the first digital wallet without requiring session-token-based authentication;

obtaining a first user input comprising a natural language transfer command displayed within a conversation interface of the first digital wallet, the conversation interface configured to receive user input comprising unstructured natural language, and display assistant user input comprising one or more contextual responses generated by an automated assistant user based on the parsed natural language input of the first user;

parsing the natural language transfer command to extract one or more entities including a recipient name and digital asset amount;

identifying a second digital wallet associated with a second user by using the extracted recipient name and the @map function to retrieve a public address associated with the second user;

verifying a contextual identity of the second user by prompting the second user for image-based verification via the automated assistant user;

recording, by the processor, a transfer in the first digital wallet for an amount of digital asset from the first digital wallet to the second digital wallet, wherein the automated assistant user confirms the transaction using a secure contextual response protocol based on prior chat history or device context.

2 . The method of claim 1 , wherein the transfer command comprises a name of the second user preceded with an “@” notation, and wherein the conversation interface parses the @ notation to identify the recipient name without requiring manual entry of the public address associated with the second user.

3 . The method of claim 2 , wherein identifying the second digital wallet associated with the second user comprises obtaining a recipient's public key retrieved using the @map function and the name of the second user, and wherein the @map function queries a locally or cloud-stored username-to-address mapping to resolve the recipient's public key.

4 . The method of claim 3 , further comprising storing, by the processor, a public key for the first digital wallet; and

storing, by the first user device, a private key for the first digital wallet locally on the first user device, wherein the stored public key is distinct from the public key retrieved using the @map function for the second digital wallet.

5 . The method of claim 1 , further comprising obtaining, by the conversation interface, a first assistant user response from the automated assistant user, wherein the response comprises a dynamically generated request to confirm the digital asset transfer, based at least in part on the context of the first user input.

6 . The method of claim 4 , further comprising obtaining, by the conversation interface, a second user input from the first user device, wherein the second user input is provided in response to the automated assistant user generating a request to confirm the digital asset transfer.

7 . The method of claim 5 , wherein the first assistant user response is generated by the automated assistant user based on analyzing a current balance or asset type associated with the first digital wallet to determine whether confirmation of the digital asset transfer is required.

8 . The method of claim 1 , wherein the automated assistant user is an automated software agent configured to parse natural language input, generate contextual responses based on the parsed natural language input, and facilitate secure digital asset transfers by prompting for user confirmations and verifying transaction parameters.

9 . A system for transferring a digital asset using natural language commands, the system comprising:

one or more physical processors configured by machine-readable instructions to:

establish a first digital wallet in a data store connected to the one or more physical processors;

receive a first user name of a first user for the first digital wallet from a first user device;

identify the first digital wallet associated with the first user by using an @map function using the first user name wherein the @map function resolves user names to public addresses of digital wallets that correspond to the user names without requiring entry of a full cryptographic address;

upon identifying the first digital wallet, log in the first user device into the firstdigital wallet without requiring session-token-based authentication;

obtain a first user input comprising a natural language transfer command displayed within a conversation interface of the first digital wallet, the conversation interface configured to receive user input comprising unstructured natural language, and display assistant user input comprising one or more contextual responses generated by an automated assistant user based on the parsed natural language input of the first user;

parsing the natural language transfer command to extract one or more entities including a recipient name and digital asset amount;

identify a second digital wallet associated with a second user by using the extracted recipient name and the @map function to retrieve a public address associated with the second user;

verifying a contextual identity of the second user by prompting the second user for image-based verification via the automated assistant user;

record a transfer in the first digital wallet for an amount of digital asset from the first digital wallet to the second digital wallet, wherein the automated assistant user confirms the transaction using a secure contextual response protocol based on prior chat history or device context.

10 . The system of claim 9 , wherein the transfer command comprises a name of the second user preceded with an “@”notation, and wherein the conversation interface parses the @ notation to identify the recipient name without requiring manual entry of the public address associated with the second user.

11 . The system of claim 10 , wherein identifying the second digital wallet associated with the second user comprises obtaining a recipient's public key retrieved using the @map function and the name of the second user, and wherein the @map function queries a locally or cloud-stored username-to-address mapping to resolve the recipient's public key.

12 . The system of claim 9 , further comprising storing, by the processor, a public key for the first digital wallet; and

storing, by the first user device, a private key for the first digital wallet locally on the first user device, wherein the stored public key is distinct from the public key retrieved using the @map function for the second digital wallet.

13 . The system of claim 9 , further comprising obtaining, by the conversation interface, a first assistant user response from the automated assistant user, wherein the response comprises a dynamically generated request to confirm the digital asset transfer, based at least in part on the context of the first user input.

14 . The system of claim 13 , further comprising obtaining, by the conversation interface, a second user input from the first user device, wherein the second user input is provided in response to the automated assistant user generating a request to confirm the digital asset transfer.

15 . The system of claim 14 , wherein the first assistant user response is generated by the automated assistant user based on analyzing a current balance or asset type associated with the first digital wallet to determine whether confirmation of the digital asset transfer is required.

16 . The system of claim 9 , wherein the automated assistant user is an automated software agent configured to parse natural language input, generate contextual responses based on the parsed natural language input, and facilitate secure digital asset transfers by prompting for user confirmations and verifying transaction parameters.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 23, 2023
From: AGARWAL, PAVAN; SANCHEZ, GABRIEL ALBORS; RIVERA, JONATHAN ORTIZ; SMITH, THOMAS
To: CELLIGENCE INTERNATIONAL LLC
Reel/Frame 064048/0447 →
Continuity (2)
Provisional Application 63355569 · Jun 24, 2022
Related Publication 20230419301A1 · Dec 28, 2023
References Cited (68)
US 5220603A · Parker · 1993 [cited by applicant]
US 5566302A · Khalidi et al. · 1996 [cited by applicant]
US 6006194A · Merel · 1999 [cited by applicant]
US 7085735B1 · Hall et al. · 2006 [cited by applicant]
US 10043174B1 · Chikkanna · 2018 [cited by examiner]
US 10853791B1 · Ellis · 2020 [cited by applicant]
US 10992605B2 · Agarwal et al. · 2021 [cited by applicant]
US 11037154B1 · Costilla · 2021 [cited by applicant]
US 11080677B2 · Tripathi et al. · 2021 [cited by applicant]
US 11244304B2 · Kohli et al. · 2022 [cited by applicant]
US 11456869B2 · Shpurov et al. · 2022 [cited by applicant]
US 11468436B2 · Mayblum et al. · 2022 [cited by applicant]
US 11481559B1 · Asefi · 2022 [cited by applicant]
US 11501297B1 · Tai et al. · 2022 [cited by applicant]
US 11663565B2 · Grassadonia · 2023 [cited by applicant]
US 11790334B1 · Corcillo · 2023 [cited by applicant]
US 11861590B1 · Quigley · 2024 [cited by applicant]
US 12169868B2 · Navarro et al. · 2024 [cited by applicant]
US 12271895B2 · DePopas et al. · 2025 [cited by applicant]
US 20030087633A1 · Yoon · 2003 [cited by applicant]
US 20090323677A1 · Mehmood et al. · 2009 [cited by applicant]
US 20100217603A1 · Hammond et al. · 2010 [cited by applicant]
US 20120290427A1 · Reed et al. · 2012 [cited by applicant]
US 20130065669A1 · Michaelson et al. · 2013 [cited by applicant]
US 20130204787A1 · Dubois · 2013 [cited by examiner]
US 20140372301A1 · Anamanamuri · 2014 [cited by examiner]
US 20150178853A1 · Byron et al. · 2015 [cited by applicant]
US 20150220914A1 · Purves · 2015 [cited by applicant]
US 20160012465A1 · Sharp · 2016 [cited by examiner]
US 20170278096A1 · Chitalia · 2017 [cited by applicant]
US 20180137094A1 · Zhou et al. · 2018 [cited by applicant]
US 20190197530A1 · Gosalia et al. · 2019 [cited by applicant]
US 20190303921A1 · Mutter · 2019 [cited by applicant]
US 20190356641A1 · Isaacson · 2019 [cited by applicant]
US 20190362339A1 · Gurunathan · 2019 [cited by examiner]
US 20200042773A1 · Benkreira · 2020 [cited by applicant]
US 20200073999A1 · Zucker · 2020 [cited by examiner]
US 20200076798A1 · Lidsky · 2020 [cited by examiner]
US 20200322320A1 · Moon · 2020 [cited by applicant]
US 20210073804A1 · Kikinis · 2021 [cited by applicant]
US 20210119785A1 · Ben-Reuven et al. · 2021 [cited by applicant]
US 20210209584A1 · Donald et al. · 2021 [cited by applicant]
US 20210247959A1 · Agarwal et al. · 2021 [cited by applicant]
US 20210256215A1 · Oddy · 2021 [cited by applicant]
US 20210383351A1 · Chauhan · 2021 [cited by applicant]
US 20210398091A1 · Yan · 2021 [cited by applicant]
US 20220058347A1 · Singaraju · 2022 [cited by applicant]
US 20220092583A1 · Ur · 2022 [cited by applicant]
US 20220180364A1 · Peled · 2022 [cited by examiner]
US 20220207525A1 · Polania · 2022 [cited by applicant]
US 20220253852A1 · Wu et al. · 2022 [cited by applicant]
US 20220261801A1 · Davis · 2022 [cited by applicant]
US 20220270085A1 · Mee · 2022 [cited by examiner]
US 20220318424A1 · D'Agostino · 2022 [cited by applicant]
US 20220318775A1 · Tomkins et al. · 2022 [cited by applicant]
US 20230103796A1 · Purandare · 2023 [cited by applicant]
US 20230336340A1 · Polleri · 2023 [cited by applicant]
US 20230336523A1 · DeLuca · 2023 [cited by applicant]
US 20230360031A1 · DeLuca · 2023 [cited by applicant]
US 20240135364A1 · Agudelo · 2024 [cited by applicant]
Brian Quarmby, “Etherescan adds new messaging feature for anons: ‘Blockscan Chat’”, Jan. 25, 2022 (Year: 2022). [cited by examiner]
PCT International Search Report and the Written Opinion mailed Oct. 18, 2023, issued in related International Application No. PCT/US2023/026166 (8 pages). [cited by applicant]
Non-Final Office Action dated Oct. 15, 2024, issued in related U.S. Appl. No. 18/219,353 (15 pages). [cited by applicant]
“Build a Cryptocurrency Chatbot with Python: Meet Sato, the Cryptobot”, Chatbots Magazine, Nov. 23, 2017. Available at: https://chatbotsmagazine.com/build-a-cryptocurrency-chatbot-with-python-meet-sato-the-cryptobot-c8d… [cited by applicant]
PCT International Preliminary Report on Patentability mailed Jan. 2, 2025, issued in related International Application No. PCT/US2023/026166 (7 pages). [cited by applicant]
Final Office Action dated Feb. 14, 2025, issued in related U.S. Appl. No. 18/219,353 (19 pages). [cited by applicant]
Final Office Action dated Sep. 18, 2025, issued in U.S. Appl. No. 18/219,353 (15 pages). [cited by applicant]
Non-Final Office Action dated Jun. 12, 2025, issued in U.S. Appl. No. 18/219,353 (16 pages). [cited by applicant]