Prosecution Insights
Last updated: April 19, 2026
Application No. 18/863,591

COMPUTING TECHNOLOGIES FOR ENABLING BLOCKCHAIN-BASED DIGITAL TOKENS WITH ASSET-SPECIFIC ATTRIBUTES

Non-Final OA §101§DP
Filed
Nov 06, 2024
Examiner
REYNOLDS, DEBORAH J
Art Unit
2400
Tech Center
2400 — Computer Networks
Assignee
Northern Trust Corporation
OA Round
1 (Non-Final)
67%
Grant Probability
Favorable
1-2
OA Rounds
2y 5m
To Grant
80%
With Interview

Examiner Intelligence

Grants 67% — above average
67%
Career Allow Rate
111 granted / 166 resolved
+8.9% vs TC avg
Moderate +14% lift
Without
With
+13.6%
Interview Lift
resolved cases with interview
Typical timeline
2y 5m
Avg Prosecution
80 currently pending
Career history
246
Total Applications
across all art units

Statute-Specific Performance

§101
6.9%
-33.1% vs TC avg
§103
47.6%
+7.6% vs TC avg
§102
19.1%
-20.9% vs TC avg
§112
17.9%
-22.1% vs TC avg
Black line = Tech Center average estimate • Based on career data from 166 resolved cases

Office Action

§101 §DP
DETAILED ACTION This is a non-final Office Action in response to communications received on 11/06/2024. The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . Drawings The drawings filed on 11/06/2024 are acknowledged. Priority or Provisional Priority to 06/21/2022 is recognized. Statutory Double Patenting A rejection based on double patenting of the “same invention” type finds its support in the language of 35 U.S.C. 101 which states that “whoever invents or discovers any new and useful process... may obtain a patent therefor...” (Emphasis added). Thus, the term “same invention,” in this context, means an invention drawn to identical subject matter. See Miller v. Eagle Mfg. Co., 151 U.S. 186 (1894); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Ockert, 245 F.2d 467, 114 USPQ 330 (CCPA 1957). A statutory type (35 U.S.C. 101) double patenting rejection can be overcome by canceling or amending the claims that are directed to the same invention so they are no longer coextensive in scope. The filing of a terminal disclaimer cannot overcome a double patenting rejection based upon 35 U.S.C. 101. Claims 1-24 are rejected under 35 U.S.C. 101 as claiming the same invention as that of claims 1-24 of prior U.S. Patent No. 11641280. This is a statutory double patenting rejection. A patent may not be obtained for an invention claimed in a commonly owned patent. Instant Application Patent No. 11641280 Claim 1. A method comprising: presenting, by a server, a user interface to a client, wherein the user interface is programmed to receive (a) a set of asset-specific attributes for a digital token to tokenize an asset of an asset type and (b) an identifier of a blockchain-based tokenization platform from a set of identifiers of a set of blockchain-based tokenization platforms capable of hosting the digital token having the set of asset-specific attributes; receiving, by the server, the set of asset-specific attributes and the identifier of the blockchain-based tokenization platform from the client; generating, by the server, the digital token based on the set of asset-specific attributes and the identifier of the blockchain-based tokenization platform such that the digital token contains a header component, an attribute component, and an immutable component, wherein the header component contains an identifier for the asset and a version for the asset, wherein the attribute component contains a first set of attributes for the asset type including a first set of key-value pairs populated with a first subset of the set of asset-specific attributes, wherein the first set of key-value pairs is programmed to be modified or have a new key-value pair being added thereto after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform, wherein the immutable component contains a second set of attributes for the asset type including a second set of key-value pairs populated with a second subset of the set of asset-specific attributes, wherein the second set of key-value pairs is programmed to not be modifiable or removable after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; issuing, by the server, the digital token on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; presenting, by the server, the user interface to the client after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform, wherein the user interface is programmed to receive a user input from the client, wherein the user input includes the identifier for the asset, the version of the asset, and a content; taking, by the server, an action with respect to the digital token after the user input is received based on identifying the digital token via the identifier for the asset and the version of the asset, wherein the action includes modifying the first set of key-value pairs based on the content or adding the new key-value pair to the first set of key-value pairs based on the content; and reissuing, by the server, the digital token on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform after the action is taken with respect to the digital token. Claim 1. A method comprising: presenting, by a server, a user interface to a client, wherein the user interface is programmed to receive (a) a set of asset-specific attributes for a digital token to tokenize an asset of an asset type and (b) an identifier of a blockchain-based tokenization platform from a set of identifiers of a set of blockchain-based tokenization platforms capable of hosting the digital token having the set of asset-specific attributes; receiving, by the server, the set of asset-specific attributes and the identifier of the blockchain-based tokenization platform from the client; generating, by the server, the digital token based on the set of asset-specific attributes and the identifier of the blockchain-based tokenization platform such that the digital token contains a header component, an attribute component, and an immutable component, wherein the header component contains an identifier for the asset and a version for the asset, wherein the attribute component contains a first set of attributes for the asset type including a first set of key-value pairs populated with a first subset of the set of asset-specific attributes, wherein the first set of key-value pairs is programmed to be modified or have a new key-value pair being added thereto after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform, wherein the immutable component contains a second set of attributes for the asset type including a second set of key-value pairs populated with a second subset of the set of asset-specific attributes, wherein the second set of key-value pairs is programmed to not be modifiable or removable after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; issuing, by the server, the digital token on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; presenting, by the server, the user interface to the client after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform, wherein the user interface is programmed to receive a user input from the client, wherein the user input includes the identifier for the asset, the version of the asset, and a content; taking, by the server, an action with respect to the digital token after the user input is received based on identifying the digital token via the identifier for the asset and the version of the asset, wherein the action includes modifying the first set of key-value pairs based on the content or adding the new key-value pair to the first set of key-value pairs based on the content; and reissuing, by the server, the digital token on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform after the action is taken with respect to the digital token. Claim 2. The method of claim 1, further comprising: presenting, by the server, the user interface to the client after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform, wherein the user interface is programmed to receive the identifier for the asset, the version of the asset, and a selection of a file containing a human-readable descriptive text that discloses, references, or represents a particular investment attribute of the asset; receiving, by the server, the identifier for the asset, the version of the asset, and a copy of the file based on the selection after the digital token is issued on the blockchain- based tokenization platform based on the identifier of the blockchain-based tokenization platform; encrypting, by the server, the copy such that an encrypted file is formed and the encrypted file is identified by a cryptographic hash value after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain- based tokenization platform; sending, by the server, the encrypted file to be stored on a storage external to the server and the blockchain-based tokenization platform after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain- based tokenization platform; identifying, by the server, the digital token via the identifier for the asset and the version of the asset after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; and causing, by the server, the cryptographic hash value to be written into a new key- value pair within the second set of key-value pairs without (a) modifying or removing the second subset of the set of asset-specific attributes already recited in the second set of key-value pairs and (b) creating a new digital token such that the encrypted file is linked to the digital token for retrieval from the storage and decryption thereof by the server via the cryptographic hash value after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform. Claim 2. The method of claim 1, further comprising: presenting, by the server, the user interface to the client after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform, wherein the user interface is programmed to receive the identifier for the asset, the version of the asset, and a selection of a file containing a human-readable descriptive text that discloses, references, or represents a particular investment attribute of the asset; receiving, by the server, the identifier for the asset, the version of the asset, and a copy of the file based on the selection after the digital token is issued on the blockchain- based tokenization platform based on the identifier of the blockchain-based tokenization platform; encrypting, by the server, the copy such that an encrypted file is formed and the encrypted file is identified by a cryptographic hash value after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain- based tokenization platform; sending, by the server, the encrypted file to be stored on a storage external to the server and the blockchain-based tokenization platform after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain- based tokenization platform; identifying, by the server, the digital token via the identifier for the asset and the version of the asset after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; and causing, by the server, the cryptographic hash value to be written into a new key- value pair within the second set of key-value pairs without (a) modifying or removing the second subset of the set of asset-specific attributes already recited in the second set of key-value pairs and (b) creating a new digital token such that the encrypted file is linked to the digital token for retrieval from the storage and decryption thereof by the server via the cryptographic hash value after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform. Claim 3. The method of claim 1, further comprising: receiving, by the server, an identifier virtually representing an asset-specific attribute of the digital token from a software application hosted outside of a data center containing the server after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; encrypting, by the server, the identifier virtually representing the asset-specific attribute of the digital token such that an attribute value represented as a cryptographic hash is formed; and causing, by the server, the cryptographic hash to be written into a new key-value pair within the first set of key-value pairs without modifying or removing the first subset of the set of asset-specific attributes already recited in the first set of key-value pairs such that a change in the new key-value pair is recoded on the blockchain-based tokenization platform external to the data center and the software application. Claim 3. The method of claim 1, further comprising: receiving, by the server, an identifier virtually representing an asset-specific attribute of the digital token from a software application hosted outside of a data center containing the server after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; encrypting, by the server, the identifier virtually representing the asset-specific attribute of the digital token such that an attribute value represented as a cryptographic hash is formed; and causing, by the server, the cryptographic hash to be written into a new key-value pair within the first set of key-value pairs without modifying or removing the first subset of the set of asset-specific attributes already recited in the first set of key-value pairs such that a change in the new key-value pair is recoded on the blockchain-based tokenization platform external to the data center and the software application. Claim 4. The method of claim 1, wherein the digital token is a first digital token, wherein the header component is a first header component, wherein the attribute component is a first attribute component, wherein the immutable component is a first immutable component, and further comprising: receiving, by the server, a set of identification data for the first digital token from a software application hosted outside of a data center containing the server after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; encrypting, by the server, the set of identification data such that an attribute value represented as a cryptographic hash is formed; and causing, by the server, the cryptographic hash to be added to a second digital token containing a second header component, a second attribute component containing a third set of key-value pairs, and a second immutable component such that the cryptographic hash is written into a new key-value pair within the third set of key-value pairs without modifying or removing those asset-specific attributes that are already recited in the third set of key-value pairs and such that a change in the new key-value pair is recoded on the blockchain-based tokenization platform external to the data center and the software application. Claim 4. The method of claim 1, wherein the digital token is a first digital token, wherein the header component is a first header component, wherein the attribute component is a first attribute component, wherein the immutable component is a first immutable component, and further comprising: receiving, by the server, a set of identification data for the first digital token from a software application hosted outside of a data center containing the server after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; encrypting, by the server, the set of identification data such that an attribute value represented as a cryptographic hash is formed; and causing, by the server, the cryptographic hash to be added to a second digital token containing a second header component, a second attribute component containing a third set of key-value pairs, and a second immutable component such that the cryptographic hash is written into a new key-value pair within the third set of key-value pairs without modifying or removing those asset-specific attributes that are already recited in the third set of key-value pairs and such that a change in the new key-value pair is recoded on the blockchain-based tokenization platform external to the data center and the software application. Claim 5. The method of claim 1, wherein the first subset of the set of asset-specific attributes and the second subset of the set of asset-specific attributes share at least one asset- specific attribute. Claim 5. The method of claim 1, wherein the first subset of the set of asset-specific attributes and the second subset of the set of asset-specific attributes share at least one asset- specific attribute. Claim 6. The method of claim 1, wherein the first subset of the set of asset-specific attributes and the second subset of the set of asset-specific attributes do not share any asset- specific attributes. Claim 6. The method of claim 1, wherein the first subset of the set of asset-specific attributes and the second subset of the set of asset-specific attributes do not share any asset- specific attributes. Claim 8. The method of claim 1, wherein the first set of key-value pairs is programmed to be modified after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform. Claim 8. The method of claim 1, wherein the first set of key-value pairs is programmed to be modified after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform. Claim 9. The method of claim 1, wherein the first set of key-value pairs is programmed to have the new key-value pair being added thereto after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform. Claim 9. The method of claim 1, wherein the first set of key-value pairs is programmed to have the new key-value pair being added thereto after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform. Claim 10. The method of claim 1,wherein the second set of key-value pairs is programmed to not be modifiable after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform. Claim 10. The method of claim 1,wherein the second set of key-value pairs is programmed to not be modifiable after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform. Claim 11. The method of claim 1,wherein the second set of key-value pairs is programmed to not be removable after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform. Claim 11. The method of claim 1,wherein the second set of key-value pairs is programmed to not be removable after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform. Claim 12. The method of claim 1, wherein the action includes modifying the first set of key-value pairs based on the content. Claim 12. The method of claim 1, wherein the action includes modifying the first set of key-value pairs based on the content. Claim 13. The method of claim 1, wherein the action includes adding the new key-value pair to the first set of key-value pairs based on the content. Claim 13. The method of claim 1, wherein the action includes adding the new key-value pair to the first set of key-value pairs based on the content. Claim 14. A system comprising: a hardware server programmed to: present a user interface to a client, wherein the user interface is programmed to receive (a) a set of asset-specific attributes for a digital token to tokenize an asset of an asset type and (b) an identifier of a blockchain-based tokenization platform from a set of identifiers of a set of blockchain-based tokenization platforms capable of hosting the digital token having the set of asset-specific attributes; receive the set of asset-specific attributes and the identifier of the blockchain-based tokenization platform from the client; generate the digital token based on the set of asset-specific attributes and the identifier of the blockchain-based tokenization platform such that the digital token contains a header component, an attribute component, and an immutable component, wherein the header component contains an identifier for the asset and a version for the asset, wherein the attribute component contains a first set of attributes for the asset type including a first set of key-value pairs populated with a first subset of the set of asset- specific attributes, wherein the first set of key-value pairs is programmed to be modified or have a new key-value pair being added thereto after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform, wherein the immutable component contains a second set of attributes for the asset type including a second set of key-value pairs populated with a second subset of the set of asset-specific attributes, wherein the second set of key-value pairs is programmed to not be modifiable or removable after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain- based tokenization platform; issue the digital token on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; present the user interface to the client after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform, wherein the user interface is programmed to receive a user input from the client, wherein the user input includes the identifier for the asset, the version of the asset, and a content; take an action with respect to the digital token after the user input is received based on identifying the digital token via the identifier for the asset and the version of the asset, wherein the action includes modifying the first set of key-value pairs based on the content or adding the new key-value pair to the first set of key-value pairs based on the content; and reissue the digital token on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform after the action is taken with respect to the digital token. Claim 14. A system comprising: a hardware server programmed to: present a user interface to a client, wherein the user interface is programmed to receive (a) a set of asset-specific attributes for a digital token to tokenize an asset of an asset type and (b) an identifier of a blockchain-based tokenization platform from a set of identifiers of a set of blockchain-based tokenization platforms capable of hosting the digital token having the set of asset-specific attributes; receive the set of asset-specific attributes and the identifier of the blockchain-based tokenization platform from the client; generate the digital token based on the set of asset-specific attributes and the identifier of the blockchain-based tokenization platform such that the digital token contains a header component, an attribute component, and an immutable component, wherein the header component contains an identifier for the asset and a version for the asset, wherein the attribute component contains a first set of attributes for the asset type including a first set of key-value pairs populated with a first subset of the set of asset- specific attributes, wherein the first set of key-value pairs is programmed to be modified or have a new key-value pair being added thereto after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform, wherein the immutable component contains a second set of attributes for the asset type including a second set of key-value pairs populated with a second subset of the set of asset-specific attributes, wherein the second set of key-value pairs is programmed to not be modifiable or removable after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain- based tokenization platform; issue the digital token on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; present the user interface to the client after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform, wherein the user interface is programmed to receive a user input from the client, wherein the user input includes the identifier for the asset, the version of the asset, and a content; take an action with respect to the digital token after the user input is received based on identifying the digital token via the identifier for the asset and the version of the asset, wherein the action includes modifying the first set of key-value pairs based on the content or adding the new key-value pair to the first set of key-value pairs based on the content; and reissue the digital token on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform after the action is taken with respect to the digital token. Claim 15. The system of claim 14, wherein the hardware server is further programmed to: present the user interface to the client after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform, wherein the user interface is programmed to receive the identifier for the asset, the version of the asset, and a selection of a file containing a human- 43readable descriptive text that discloses, references, or represents a particular investment attribute of the asset; receive the identifier for the asset, the version of the asset, and a copy of the file based on the selection after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; encrypt the copy such that an encrypted file is formed and the encrypted file is identified by a cryptographic hash value after the digital token is issued on the blockchain- based tokenization platform based on the identifier of the blockchain-based tokenization platform; send the encrypted file to be stored on a storage external to the hardware server and the blockchain-based tokenization platform after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; identify the digital token via the identifier for the asset and the version of the asset after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; and cause the cryptographic hash value to be written into a new key-value pair within the second set of key-value pairs without (a) modifying or removing the second subset of the set of asset-specific attributes already recited in the second set of key-value pairs and (b) creating a new digital token such that the encrypted file is linked to the digital token for retrieval from the storage and decryption thereof by the hardware server via the cryptographic hash value after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform. Claim 15. The system of claim 14, wherein the hardware server is further programmed to: present the user interface to the client after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform, wherein the user interface is programmed to receive the identifier for the asset, the version of the asset, and a selection of a file containing a human- 43readable descriptive text that discloses, references, or represents a particular investment attribute of the asset; receive the identifier for the asset, the version of the asset, and a copy of the file based on the selection after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; encrypt the copy such that an encrypted file is formed and the encrypted file is identified by a cryptographic hash value after the digital token is issued on the blockchain- based tokenization platform based on the identifier of the blockchain-based tokenization platform; send the encrypted file to be stored on a storage external to the hardware server and the blockchain-based tokenization platform after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; identify the digital token via the identifier for the asset and the version of the asset after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; and cause the cryptographic hash value to be written into a new key-value pair within the second set of key-value pairs without (a) modifying or removing the second subset of the set of asset-specific attributes already recited in the second set of key-value pairs and (b) creating a new digital token such that the encrypted file is linked to the digital token for retrieval from the storage and decryption thereof by the hardware server via the cryptographic hash value after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform. Claim 16. The system of claim 14, wherein the hardware server is further programmed to: receive an identifier virtually representing an asset-specific attribute of the digital token from a software application hosted outside of a data center containing the hardware server after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; encrypt the identifier virtually representing the asset-specific attribute of the digital token such that an attribute value represented as a cryptographic hash is formed; and cause the cryptographic hash to be written into a new key-value pair within the first set of key-value pairs without modifying or removing the first subset of the set of asset- specific attributes already recited in the first set of key-value pairs such that a change in the new key-value pair is recoded on the blockchain-based tokenization platform external to the data center and the software application. Claim 16. The system of claim 14, wherein the hardware server is further programmed to: receive an identifier virtually representing an asset-specific attribute of the digital token from a software application hosted outside of a data center containing the hardware server after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; encrypt the identifier virtually representing the asset-specific attribute of the digital token such that an attribute value represented as a cryptographic hash is formed; and cause the cryptographic hash to be written into a new key-value pair within the first set of key-value pairs without modifying or removing the first subset of the set of asset- specific attributes already recited in the first set of key-value pairs such that a change in the new key-value pair is recoded on the blockchain-based tokenization platform external to the data center and the software application. Claim 17. The system of claim 14, wherein the digital token is a first digital token, wherein the header component is a first header component, wherein the attribute component is a first attribute component, wherein the immutable component is a first immutable component, and the hardware server is further programmed to: receive a set of identification data for the first digital token from a software application hosted outside of a data center containing the hardware server after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; encrypt the set of identification data such that an attribute value represented as a cryptographic hash is formed; and cause the cryptographic hash to be added to a second digital token containing a second header component, a second attribute component containing a third set of key- value pairs, and a second immutable component such that the cryptographic hash is written into a new key-value pair within the third set of key-value pairs without modifying or removing those asset-specific attributes that are already recited in the third set of key- value pairs and such that a change in the new key-value pair is recoded on the blockchain-based tokenization platform external to the data center and the software application. Claim 17. The system of claim 14, wherein the digital token is a first digital token, wherein the header component is a first header component, wherein the attribute component is a first attribute component, wherein the immutable component is a first immutable component, and the hardware server is further programmed to: receive a set of identification data for the first digital token from a software application hosted outside of a data center containing the hardware server after the digital token is issued on the blockchain-based tokenization platform based on the identifier of the blockchain-based tokenization platform; encrypt the set of identification data such that an attribute value represented as a cryptographic hash is formed; and cause the cryptographic hash to be added to a second digital token containing a second header component, a second attribute component containing a third set of key- value pairs, and a second immutable component such that the cryptographic hash is written into a new key-value pair within the third set of key-value pairs without modifying or removing those asset-specific attributes that are already recited in the third set of key- value pairs and such that a change in the new key-value pair is recoded on the blockchain-based tokenization platform external to the data center and the software application. Claim 18. The system of claim 14, wherein the first subset of the set of asset-specific attributes and the second subset of the set of asset-specific attributes share at least one asset- specific attribute. Claim 18. The system of claim 14, wherein the first subset of the set of asset-specific attributes and the second subset of the set of asset-specific attributes share at least one asset- specific attribute. Claim 19. The system of claim 14, wherein the first subset of the set of asset-specific attributes and the second subset of the set of asset-specific attributes do not share any asset- specific attributes. Claim 19. The system of claim 14, wherein the first subset of the set of asset-specific attributes and the second subset of the set of asset-specific attributes do not share any asset- specific attributes. Claim 20. The system of claim 14, wherein the second subset of the set of asset-specific attributes is a copy of the first subset of the set of asset-specific attributes. Claim 20. The system of claim 14, wherein the second subset of the set of asset-specific attributes is a copy of the first subset of the set of asset-specific attributes. Claim 21. The method of claim 1, wherein the server is a single server. Claim 21. The method of claim 1, wherein the server is a single server. Claim 22. The method of claim 1, wherein the server is a set of servers. Claim 22. The method of claim 1, wherein the server is a set of servers. Claim 23. The system of claim 14, wherein the hardware server is a single server. Claim 23. The system of claim 14, wherein the hardware server is a single server. Claim 24. The system of claim 14, wherein the hardware server is a set of servers. Claim 24. The system of claim 14, wherein the hardware server is a set of servers. References Considered But Not Relied Upon Srivastava (US 2021/0056095) discloses creating assets on the blockchain through chain code transactions which may be issued by users. Maj (US 2022/0006642) discloses tokenized assets having key-value pairs where new key value pairs can be adds by a user as immutable value. Conclusion Accordingly, claims 1-24 are rejected. Any inquiry concerning this communication or earlier communications from the examiner should be directed to PEGAH BARZEGAR whose telephone number is (703)756-4755. The examiner can normally be reached M-F, 9:00 - 5:30. Examiner interviews are available via telephone using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Taghi T Arani can be reached on 571-272-3787. The fax phone number for the Application/Control Number: 17/470,067 Page 17 Art Unit: 2438 organization where this application or proceeding is assigned is 571-273- 8300. Application/Control Number: 17/386,076 Page 25 Art Unit: 2438 Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patentcenter for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272- 1000. /P.B./Examiner, Art Unit 2438 /TAGHI T ARANI/Supervisory Patent Examiner, Art Unit 2438
Read full office action

Prosecution Timeline

Nov 06, 2024
Application Filed
Mar 12, 2026
Non-Final Rejection — §101, §DP (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12534225
SATELLITE DISPENSING SYSTEM
2y 5m to grant Granted Jan 27, 2026
Patent 12441265
Mechanisms for moving a pod out of a vehicle
2y 5m to grant Granted Oct 14, 2025
Patent 12434638
VEHICLE INTERIOR PANEL WITH ONE OR MORE DAMPING PADS
2y 5m to grant Granted Oct 07, 2025
Patent 12372654
Adaptive Control of Ladar Systems Using Spatial Index of Prior Ladar Return Data
2y 5m to grant Granted Jul 29, 2025
Patent 12365469
AIRCRAFT PROPULSION SYSTEM WITH INTERMITTENT COMBUSTION ENGINE(S)
2y 5m to grant Granted Jul 22, 2025
Study what changed to get past this examiner. Based on 5 most recent grants.

AI Strategy Recommendation

Get an AI-powered prosecution strategy using examiner precedents, rejection analysis, and claim mapping.
Powered by AI — typically takes 5-10 seconds

Prosecution Projections

1-2
Expected OA Rounds
67%
Grant Probability
80%
With Interview (+13.6%)
2y 5m
Median Time to Grant
Low
PTA Risk
Based on 166 resolved cases by this examiner. Grant probability derived from career allow rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month