Office Action 2: Notice of Allowance (2024-09-05)

CLAIMS:
AMENDMENTS TO THE CLAIMS

The following listing of claims will replace all prior versions, and listings, of claims in the application:1.(Currently Amended) An apparatus for delegating a role associated with an NET using aself-executable data structure, the apparatus comprising:at least a processor; anda memory communicatively connected to the at least a processor, the memory containinginstructions configuring the at least a processor to:receive a data collection, wherein the data collection comprises a plurality of data objects associated with at least one NET;verify at least a usage of the at least one NET as a function of the data collection;determine at least a role associated with the at least one NET, wherein determining the at least a role comprises:retrieving training data from a blockchain storage of a data store, wherein the training data comprises a plurality of usage data correlated to a plurality of role data:training, iteratively, a role designation machine-learning model as a function of the training data: and determining the at least a role as a function of the at least a usage of the at least one NFET using the trained role designation machine-learning model; andgenerate a self-executable data structure, wherein the self-executable datastructure is configured to delegate the at least a role associated with the at least one NFET.

2\. (Original) The apparatus of claim 1, wherein the data collection comprises information associated with an owner of the at least one NFT.SVG {EMBED HERE} 0.110.043

3\. (Original) The apparatus of claim 1, wherein verifying the at least a usage of the at least one NET comprises generating a verification datum as a function of the data collection.
4\. (Canceled)200 ClarendoSVG {EMBED HERE} 0.260.323596

5\. (Original) The apparatus of claim 1, wherein delegating the at least a role associated with the at least one NFT comprises delegating at least a usage right of the at least one NFT.

6\. (Original) The apparatus of claim 5, wherein the at least a usage right comprises a temporary usage right.

7\. (Original) The apparatus of claim 1, wherein the at least one NFT comprises an NFT selected from the group consisting of a utility NFT, a rental NFT, a fractional NFT, and a governance NFT.

8\. (Original) The apparatus of claim 1, wherein the self-executable data structure is configured to be executed on a decentralized platform.

9\. (Original) The apparatus of claim 1, wherein the at least a processor is further configured to analyze the data collection using a decision tree, wherein the decision tree comprises a plurality of nodes.

10\. (Original) The apparatus of claim 1, further comprising an interface communicatively connected to the at least a processor, wherein the interface is configured to display the at least one NFT.

11\. (Currently Amended) A method for delegating a role associated with an NFT using a self-executable data structure, the method comprising:receiving, by at least a processor, a data collection, wherein the data collection comprises a plurality of data objects associated with at least one NFT;
verifying, by the at least a processor, at least a usage of the at least one NFT as a function of the data collection;
determining, by the at least a processor, at least a role associated with the at least oneNFT, wherein determining the at least a role comprises:retrieving training data from a blockchain storage of a data store, wherein the training data comprises a plurality of usage data correlated to a plurality of role data;
training, iteratively, a role designation machine-learning model as a function of the training data; and
determining the at least a role as a function of the at least a usage of the at least one NFT using the trained role designation machine-learning model; and200 Clarendon St.
59' Floor

generating, by the at least a processor, a self-executable data structure, wherein the self- executable data structure is configured to delegate the at least a role associated with the at least one NFT.

12\. (Original) The method of claim 11, wherein the data collection comprises information associated with an owner of the at least one NFT.

13\. (Original) The method of claim 11, wherein verifying the at least a usage of the at least one NFT comprises generating a verification datum as a function of the data collection.

14\. (Canceled)

15\. (Original) The method of claim 11, wherein delegating the at least a role associated with the at least one NFT comprises delegating at least a usage right of the at least one NFT.

16\. (Original) The method of claim 15, wherein the at least a usage right comprises a temporary usage right.

17\. (Original) The method of claim 11, wherein the at least one NFT comprises an NFT selected from the group consisting of a utility NFT, a rental NFT, a fractional NFT, and a governance NFT.

18\. (Original) The method of claim 11, wherein the self-executable data structure is configured to be executed on a decentralized platform.

19\. (Original) The method of claim 11, further comprising analyzing, by the at least a processor, the data collection using a decision tree, wherein the decision tree comprises a plurality of nodes.

20\. (Original) The method of claim 11 further comprising displaying the at least one NFT using an interface communicatively connected to the at least a processor.200 Clarendon St.
59' Floor

OFFICE ACTION:
Notice of Pre-AIA  or AIA  Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Examiner’s Amendment
An examiner’s amendment to the record appears below.  Should the changes and/or additions be unacceptable to Applicant, an amendment may be filed as provided by 37 CFR 1.312. To ensure consideration of such an amendment, it MUST be submitted no later than the payment of the issue fee.
Claims
1.(Currently Amended) An apparatus for delegating a role associated with [[an NFT]]a non-fungible token (NFT) using a self-executable data structure, the apparatus comprising:
at least a processor; and
a memory communicatively connected to the at least a processor, the memory containing instructions configuring the at least a processor to:
receive a data collection, wherein the data collection comprises a plurality of data objects associated with at least one NFT;
verify at least a usage of the at least one NFT as a function of the data collection;
determine at least a role associated with the at least one NFT, wherein determining the at least a role comprises:
retrieving training data from a blockchain storage of a data store, wherein the training data comprises a plurality of usage data correlated to a plurality ofr ole data;
training, iteratively, a role designation machine-learning model as a function of the training data; and
determining the at least a role as a function of the at least a usage of the at least one NFT using the trained role designation machine-learning model; and
generate a self-executable data structure, wherein the self-executable datastructure is configured to delegate the at least a role associated with the at least one NFET.
11. (Currently Amended) A method for delegating a role associated with [[an NFT]]a non-fungible token (NFT) using a self-executable data structure, the method comprising:
receiving, by at least a processor, a data collection, wherein the data collection comprises a plurality of data objects associated with at least one NFT;
verifying, by the at least a processor, at least a usage of the at least one NFT as a function of the data collection;
determining, by the at least a processor, at least a role associated with the at least oneNFT, wherein determining the at least a role comprises:
retrieving training data from a blockchain storage of a data store, wherein the training data comprises a plurality of usage data correlated to a plurality of role data;
training, iteratively, a role designation machine-learning model as a function of the training data; and
determining the at least a role as a function of the at least a usage of the at least one NFT using the trained role designation machine-learning model;
generating, by the at least a processor, a self-executable data structure, wherein the self-executable data structure is configured to delegate the at least a role associated with the at least one NFT.
Allowable Subject Matter
Examiner’s Statement of Reasons for Allowance
The following is an examiner’s statement for reasons for allowance:
Independent claims 1 and 11 are allowable based on the remark presented on 5/31/2024 and in view of the claim language.
None of the previously cited closest prior art(s) by Omar and Dotan-Cohen, either singularly or in combination would result in a proper rejection under 35 USC 102 or 103.
All of the cited prior art of record above, whether singularly or in combination, fails to disclose the feature limitation verify at least a usage of the at least one NFT as a function of the data collection; determine at least a role associated with the at least one NFT, wherein determining the at least a role comprises: retrieving training data from a blockchain storage of a data store, wherein the training data comprises a plurality of usage data correlated to a plurality of role data; training, iteratively, a role designation machine-learning model as a function of the training data; and determining the at least a role as a function of the at least a usage of the at least one NFT using the trained role designation machine-learning model; and generate a self-executable data structure, wherein the self-executable data structure is configured to delegate the at least a role associated with the at least one NF.
Additional search does not yield suitable references that reasonably, either singularly or in combination with previous cited references, would result in a proper rejection under 35 USC 102 or 103.
Claims dependent on independent claims are also allowed.
Any comments considered necessary by applicant must be submitted no later than the payment of the issue fee and, to avoid processing delays, should preferably accompany the issue fee. Such submissions should be clearly labeled Comments on Statement of Reasons for Allowance.
Conclusion

APPLICANT REBUTTAL: REMARKS
Claims 1-3, 5-13, and 15-20 are pending, with claims 1 and 11 being independent. Claims 1 and 11 are amended. Claims 4 and 14 are canceled.
In taking the foregoing actions, Applicant respectfully submits Applicant is not
necessarily conceding in this application that these claims, as originally presented, are not patentable over the references cited by the U.S. Patent and Trademark Office (USPTO) as pertinent ones of the present claim amendments and cancellations are only for facilitating expeditious prosecution. Applicant respectfully reserves the right to pursue any of the prior versions of the claims, any canceled claims and/or other claims in one or more continuing applications and/or at a later date.
Other than any claim amendments discussed further below, claim 1 has also been
amended, as shown above, to correct any noted typographical-type errors, and/or to establish proper antecedent and/or dependency basis, and/or for readability and/or consistency purposes. No new matter has been introduced.
App
licant-Initiated Interview Summary
A telephonic interview ("the interview") regarding the instant matter was conducted on May 28, 2024 between Primary Examiner James R. Turchen and Applicant's representative Khurram Rahman, Registration No. 70,147. Patentability under 35 U.S.C. §§ 102 and 103, andpotential claim amendments were discussed. Applicant thanks the Examiner for his time and consideration in conducting the interview.
A tentative agreement was reached that claim 1, as amended herein, is patentably distinguishable over the cited references. However, the Examiner indicated that he would conduct an updated search.
Claim Re
j
ections Under 35 U.S.C.
§
Claims 1-3, 5-8, 11-13 and 15-18 stand rejected under 35 U.S.C. § 102(a)(1) as allegedly being anticipated by non-patent literature document "Capability-Based Non-fungible Tokens Approach for a Decentralized AAA Framework in IoT," 2020, to Omar et al. (hereinafter "Omar"). (Office Action, p. 2). Applicant respectfully traverses these rejections.
In this case, in the interest of advancing prosecution and to further distinguish over the cited art, Applicant has amended claim 1, which is directed to an apparatus for delegating a role associated with an NFT using a self-executable data structure, to recite, (emphasis added):
at least a processor; and
a memory communicatively connected to the at least a processor, the memory
containing instructions configuring the at least a processor to:
receive a data collection, wherein the data collection comprises a plurality of data objects associated with at least one NFT; verify at least a usage of the at least one NFT as a function of the data collection;
determine at least a role associated with the at least one NFT,
wherein determining the at least a role comprises: retrieving training data from a blockchain storage of a data store, wherein the training data comprises a plurality of usage data correlated to a plurality of role data training, iteratively, a role designation machine-learning model as a function of the training data and
determining the at least a role as a function of the at least a usage of the at least one N
F
T using the trained role designation machine-learning model
;
and
generate a self-executable data structure, wherein the self-executable data structure is configured to delegate the at least a role associated with the at least one NFT.
Applicant submits that at least such an arrangement of "determin[ing] at least a role associated with the at least one NFT ... compris[ing] ... retrieving training data from a blockchain storage of a data store, wherein the training data comprises a plurality of usage data correlated to a plurality of role data ... training, iteratively, a role designation machine-learning model as a function of the training data ... and determining the at least a role as a function of the at least a usage of the at least one NFT using the trained role designation machine-learning model" is not disclosed, taught, or even suggested, by Omar. Support for the amendments to claim 1 can be found in the Application-as-originally-filed, for example, support may be found at, at least, at original claim 4 and paragraph numbers [0043]-[0045] and [0047] of the specification. Independent claim 11 has been amended in a manner similar to independent claim 1. In view of the amendments to claims 1 and 11, respective dependent claims 4 and 14 have been canceled, as shown above. No new matter has been introduced.
Omar is directed to distributed and decentralized applications on heterogeneous IoT networks. However, Omar fails to disclose, teach, or even suggest, at least the above claimed
arrangement of "determin[ing] at least a role associated with the at least one NFT ... compris[ing] ... retrieving training data from a blockchain storage of a data store, wherein the training data comprises a plurality of usage data correlated to a plurality of role data ... training, iteratively, a role designation machine-learning model as a function of the training data ... and determining the at least a role as a function of the at least a usage of the at least one NFT using the trained role designation machine-learning model" as recited in amended claim 1.
Applicant notes the Examiner's assertion regarding claims 4 and 14 that U.S. Patent
Appl. Publ. No. 2019/0340554 Al to Dotan-Cohen et al. (hereinafter "Dotan-Cohen") "discloses engagement levels and role assignments including determining the at least a role associated with the at least one NFT comprises utilizing a role designation machine-learning model configured to correlate the at least a usage to a role datum (Abstract, para 137, 195)." (Office Action. p. 5). Applicant respectfully traverses.
In any event, Dotan-Cohen, individually or in combination with Omar, fails to disclose, teach, or even suggest, at least the above claimed arrangement of "determin[ing] at least a role associated with the at least one NFT ... compris[ing] ... retrieving training data from a blockchain storage of a data store, wherein the training data comprises a plurality of usage data correlated to a plurality of role data ... training, iteratively, a role designation machine-learning model as a function of the training data ... and determining the at least a role as a function of the at least a usage of the at least one NFT using the trained role designation machine-learning model" as recited in amended claim 1.
As such, Applicant submits that Omar, and even Dotan-Cohen, individually or in
combination, fail to disclose, teach, or even suggest, each and every element of claim 1 and that claim 1 is thus allowable.
Independent claim 11, as amended, recites limitations analogous or similar to those of independent claim 1 and overcomes this rejection for at least the same reasons as discussed above with reference to claim 1. As such, Applicant submits that claim 11 is also allowable.
Claims 2, 3 and 5-8 depend, directly or indirectly, from claim 1 and claims 12, 13 and 15- 18 depend, directly or indirectly, from claim 11. As discussed above, claims 1 and 11 are patentably distinguishable over Omar, and even Dotan-Cohen, individually or in combination, for at least the reasons discussed above. Accordingly, Applicant respectfully submits that claims
2, 3, 5-8, 12, 13 and 15-18 are patentably distinguishable over Omar, and even Dotan-Cohen, individually or in combination, for at least the reasons discussed above, and because of the unique combinations of limitations recited therein.
Therefore, Applicant respectfully requests reconsideration and withdrawal of all 35 U.S.C. § 102 rejections of the claims.
Claim Re
j
ections Under 35 U.S.C.
Omar /Dotan-Cohen
Claims 4 and 14 stand rejected under 35 U.S.C. § 103 as allegedly being unpatentable
over Omar in view of Dotan-Cohen. (Office Action, p. 4). Applicant respectfully traverses these rej ections.
Claims 4 and 14 have been canceled, as shown and also noted above, rendering these rejections now moot.
Omar / Claybrook
Claims 9 and 19 stand rejected under 35 U.S.C. § 103 as allegedly being unpatentable over Omar in view of U.S. Patent No. 11,109,214 Bl to Claybrook et al. (hereinafter "Claybrook"). (Office Action, p. 5). Applicant respectfully traverses these rejections.
Claim 9 depends directly from claim 1 and claim 19 depends directly from claim 11. As discussed above, claims 1 and 11 are patentably distinguishable over Omar for at least the reasons discussed above. Furthermore, Claybrook fails to cure the deficiencies of Omar. Accordingly, Applicant respectfully submits that claims 1 and 11, as amended, and claims 9 and 19, are patentably distinguishable over Omar and Claybrook, individually or in combination, for at least the reasons discussed above, and because of the unique combinations of limitations recited therein.
Therefore, Applicant respectfully requests reconsideration and withdrawal of the 35 U.S.C. § 103 rejections of claims 9 and 19. Omar / "Official Notice"
Claims 10 and 20 stand rejected under 35 U.S.C. § 103 as allegedly being unpatentable over Omar in view of Examiner's Official Notice. (Office Action, p. 6). Applicant respectfully traverses these rejections.
Claim 10 depends directly from claim 1 and claim 20 depends directly from claim 11. As discussed above, claims 1 and 11 are patentably distinguishable over Omar for at least the reasons discussed above. Furthermore, the asserted Official Notice fails to cure the deficiencies of Omar. Accordingly, Applicant respectfully submits that claims 1 and 11, as amended, and claims 10 and 20, are patentably distinguishable over Omar and the asserted Official Notice for at least the reasons discussed above, and because of the unique combinations of limitations recited therein.
Therefore, Applicant respectfully requests reconsideration and withdrawal of the 35 U.S.C. § 103 rejections of claims 10 and 20.
Applicant further submits that the Examiner has taken improper Official Notice to assert the following at page 6 of the Office Action:
Omar discloses the apparatus of claim 1, but does not explicitly disclose
further comprising an interface communicatively connected to the at least a
processor, wherein the interface is configured to display the at least one NFT. The
examiner takes official notice that a display interface was well known at the time
of invention. It would have been obvious to a person of ordinary skill in the art before the effective filing date to modify the implementation of Omar with the
implementation of examiner's official notice in order to allow a user to view
content.
The MPEP states that "[o]fficial notice without documentary evidence to support an
examiner's conclusion is permissible only in some circumstances ... [further] the notice of facts beyond the record which may be taken by the examiner must be 'capable of such instant and unquestionable demonstration as to defy dispute' (citing In re Knapp Monarch Co., 296 F.2d 230, 132 USPQ 6 (CCPA 1961))." (MPEP § 2144.03 (A)). In addition, "[o]fficial notice unsupported by documentary evidence should only be taken by the examiner where the facts asserted to be well-known, or to be common knowledge in the art are capable of instance and unquestionable demonstration as being well-known. (See MPEP § 2144.03 (A)).
The MPEP also states that "[i]t is never appropriate to rely solely on "common
knowledge" in the art without evidentiary support in the record, as the principal evidence upon which a rejection was based." (citing Zurko, 258 F.3d at 1385, 59 USPQ2d at 1697.) (MPEP § 2144.03 (A)) ("[T]he Board cannot simply reach conclusions based on its own understanding or experience-or on its assessment of what would be basic knowledge or common sense. Rather, the Board must point to some concrete evidence in the record in support of these findings." (Id. at
1385-86, 59 USPQ2d at 1697.) As the court held in Zurko, an assessment of basic knowledge and common sense that is not based on any evidence in the record lacks substantial evidence support. (Id. at 1385, 59 USPQ2d at 1697. See alsoArendi v. Apple, 832 F.3d 1355, 119 USPQ2d 1822 (Fed. Cir. 2016) (finding that the Board had not provided a reasoned analysis, supported by the evidence of record, for why "common sense" taught the missing process step."))
The MPEP states that "[i]f applicant adequately traverses the examiner's assertion of
official notice, the examiner must provide documentary evidence in the next office action if the rejection is to be maintained. (See 37 CFR 1.104(c)(2).) (See also Zurko 258 F.3d at 1385, 59 USPQ2d at 1697 ("[T]he Board [or examiner] must point to some concrete evidence in the record in support of these findings" to satisfy the substantial evidence test.")) Applicant submits that it is not appropriate for the Office to simply rely on what is allegedly "known" to create an invention based on an interface communicatively connected to a processor and configured to display at least one NFT. As such, and at least for these additional reasons, Applicant respectfully request withdrawal of the obviousness rejections of claims 10 and 20.
As such, Applicant respectfully requests reconsideration and withdrawal of all 35 U.S.C. § 103 rejections of the claims.
Conclusion


CITED REFERENCE SUMMARIES: Ref US20220351165A1: Claims:
A method for creating, maintaining and tracking a cryptographic digital asset tied to physical asset, the method comprising: creating, via a first computing node within a distributed computing network, a digital asset file representative of a respective physical asset in possession of a first party; initializing a digital asset generator to create a blockchain-enabled non-fungible token (NFT) of the digital asset file, wherein the NFT is assigned a unique digital asset identification (ID) code; linking the unique digital asset ID code with a unique user ID code, wherein the unique user ID code is associated with the first party; creating a first transaction block including the unique digital asset code and the unique user ID code, via the first computing node in a distributed blockchain ledger, to record possession of the cryptographic digital asset and the respective physical asset with the first party; receiving an asset transfer request to transfer the cryptographic digital asset and respective physical asset to a second party; verifying a second unique user ID code which is associated with the second party; linking the cryptographic digital asset with the second unique user ID code; and creating a second transaction block including the unique digital asset ID code and the second unique user ID code in the distributed blockchain ledger for recordation of the transfer of possession of the cryptographic digital asset and the respective physical asset from the first party to the second party.
creating, via a first computing node within a distributed computing network, a digital asset file representative of a respective physical asset in possession of a first party;
initializing a digital asset generator to create a blockchain-enabled non-fungible token (NFT) of the digital asset file, wherein the NFT is assigned a unique digital asset identification (ID) code;
linking the unique digital asset ID code with a unique user ID code, wherein the unique user ID code is associated with the first party;
creating a first transaction block including the unique digital asset code and the unique user ID code, via the first computing node in a distributed blockchain ledger, to record possession of the cryptographic digital asset and the respective physical asset with the first party;
receiving an asset transfer request to transfer the cryptographic digital asset and respective physical asset to a second party;
verifying a second unique user ID code which is associated with the second party;
linking the cryptographic digital asset with the second unique user ID code; and
creating a second transaction block including the unique digital asset ID code and the second unique user ID code in the distributed blockchain ledger for recordation of the transfer of possession of the cryptographic digital asset and the respective physical asset from the first party to the second party.
The method of claim 1 , wherein the physical asset comprises lease records and wherein the digital asset file is stored within a digital vault accessible to only the first and second parties.
The method of claim 1 , wherein the physical asset comprises physical evidence and wherein the digital asset file is stored within a digital vault accessible to only the first and second parties.
The method of claim 1 , wherein the physical asset comprises feature film and documentary materials.
The method of claim 1 , wherein the physical asset comprises organs, body parts and pieces for transplant.
The method of claim 1 , wherein the physical asset comprises intellectual property and trade secret materials.
The method of claim 1 , wherein the physical asset comprises military contingency plans, operations plans or time phased force deployment data.
The method of claim 1 , wherein the physical asset comprises livestock and animal provenance and bloodline authenticity materials.
The method of claim 1 , wherein the physical asset comprises mineral and water rights materials.
The method of claim 1 , wherein the physical asset comprises data and materials for an electricity generating windmill.
The method of claim 10 , wherein electricity generated by the windmill is tokenized and sold on an associated tokenized commodities exchange.
The method of claim 1 , wherein the physical asset comprises data and materials associated with an oil, water or gas well.
The method of claim 12 , wherein output of the well is tokenized and sold on an associated tokenized commodities exchange
A decentralized computing system for creating, maintaining and tracking a cryptographic digital asset tied to physical asset, the decentralized computing system comprising: a cryptographic digital asset marketplace configured to store a plurality of digital assets and a plurality of unique digital asset identification (ID) codes; and a first computing node operatively connected to the cryptographic digital asset marketplace, the first computing node being programmed to: create a digital asset file representative of a respective physical asset in possession of a first party; initialize a digital asset generator to create a blockchain-enabled non fungible token (NFT) of the digital asset file, wherein the NFT is assigned a respective unique digital asset ID code; link the respective unique digital asset ID code with a unique user ID code, wherein the unique user ID code is associated with the first party; create a first transaction block including the respective unique digital asset ID code and the unique user ID code, via the first computing node in a distributed blockchain ledger, to record possession of the cryptographic digital asset and the respective physical asset with the first party; receive an asset transfer request to transfer the cryptographic digital asset and respective physical asset to a second party; verify a second unique user ID code which is associated with the second party; link the cryptographic digital asset with the second unique user ID code; create a second transaction block including the respective unique digital asset ID code and the second unique user ID code in the distributed blockchain ledger; and store the digital asset file within a digital vault wherein the digital asset fill is accessible only to a respective party identified within the first transaction block or second transaction block.
a cryptographic digital asset marketplace configured to store a plurality of digital assets and a plurality of unique digital asset identification (ID) codes; and
a first computing node operatively connected to the cryptographic digital asset marketplace, the first computing node being programmed to: create a digital asset file representative of a respective physical asset in possession of a first party; initialize a digital asset generator to create a blockchain-enabled non fungible token (NFT) of the digital asset file, wherein the NFT is assigned a respective unique digital asset ID code; link the respective unique digital asset ID code with a unique user ID code, wherein the unique user ID code is associated with the first party; create a first transaction block including the respective unique digital asset ID code and the unique user ID code, via the first computing node in a distributed blockchain ledger, to record possession of the cryptographic digital asset and the respective physical asset with the first party; receive an asset transfer request to transfer the cryptographic digital asset and respective physical asset to a second party; verify a second unique user ID code which is associated with the second party; link the cryptographic digital asset with the second unique user ID code; create a second transaction block including the respective unique digital asset ID code and the second unique user ID code in the distributed blockchain ledger; and store the digital asset file within a digital vault wherein the digital asset fill is accessible only to a respective party identified within the first transaction block or second transaction block.
create a digital asset file representative of a respective physical asset in possession of a first party;
initialize a digital asset generator to create a blockchain-enabled non fungible token (NFT) of the digital asset file, wherein the NFT is assigned a respective unique digital asset ID code;
link the respective unique digital asset ID code with a unique user ID code, wherein the unique user ID code is associated with the first party;
create a first transaction block including the respective unique digital asset ID code and the unique user ID code, via the first computing node in a distributed blockchain ledger, to record possession of the cryptographic digital asset and the respective physical asset with the first party;
receive an asset transfer request to transfer the cryptographic digital asset and respective physical asset to a second party;
verify a second unique user ID code which is associated with the second party;
link the cryptographic digital asset with the second unique user ID code;
create a second transaction block including the respective unique digital asset ID code and the second unique user ID code in the distributed blockchain ledger; and
store the digital asset file within a digital vault wherein the digital asset fill is accessible only to a respective party identified within the first transaction block or second transaction block.
Ref US20190340554A1: [content unavailable]
Ref US11109214B1: [content unavailable]
Ref US20240086384A1: Claims:
A computer-based digital certification management system; a certification database storing tokenized certification standards, wherein each tokenized certification standard comprises at least one certification criteria defined based on certification data attributes, and wherein the tokenized certification standards are indexed by at least some of the certification data attributes; at least one computer readable memory storing digital token management software instructions; and at least one processor coupled with the at least one computer readable memory and with the certification database, and that performs the following operations upon execution of the digital token management software instructions: receiving digital test token data; extracting a set of token distinguishing features from the digital test token data via execution of a set of digital feature extraction algorithm implementations; identifying at least one tokenized certification standard from the certification database having certification attributes satisfying a query defined using at least a portion of the set of token distinguishing features; deriving at least one satisfaction level based on the set of token distinguishing features with respect to the at least one certification criteria of the identified at least one tokenized certification standard; determining a smart contract interface of a first notarized ledger to invoke from a plurality of smart contract interfaces, the smart contract interface associated with the digital test token data; and invoking the smart contract interface based on the satisfaction level and the digital test token data.
a certification database storing tokenized certification standards, wherein each tokenized certification standard comprises at least one certification criteria defined based on certification data attributes, and wherein the tokenized certification standards are indexed by at least some of the certification data attributes;
at least one computer readable memory storing digital token management software instructions; and
at least one processor coupled with the at least one computer readable memory and with the certification database, and that performs the following operations upon execution of the digital token management software instructions: receiving digital test token data; extracting a set of token distinguishing features from the digital test token data via execution of a set of digital feature extraction algorithm implementations; identifying at least one tokenized certification standard from the certification database having certification attributes satisfying a query defined using at least a portion of the set of token distinguishing features; deriving at least one satisfaction level based on the set of token distinguishing features with respect to the at least one certification criteria of the identified at least one tokenized certification standard; determining a smart contract interface of a first notarized ledger to invoke from a plurality of smart contract interfaces, the smart contract interface associated with the digital test token data; and invoking the smart contract interface based on the satisfaction level and the digital test token data.
receiving digital test token data;
extracting a set of token distinguishing features from the digital test token data via execution of a set of digital feature extraction algorithm implementations;
identifying at least one tokenized certification standard from the certification database having certification attributes satisfying a query defined using at least a portion of the set of token distinguishing features;
deriving at least one satisfaction level based on the set of token distinguishing features with respect to the at least one certification criteria of the identified at least one tokenized certification standard;
determining a smart contract interface of a first notarized ledger to invoke from a plurality of smart contract interfaces, the smart contract interface associated with the digital test token data; and
invoking the smart contract interface based on the satisfaction level and the digital test token data.
The system of claim 1 , wherein the tokenized certification standards comprise digital tokens recorded on a second notarized ledger.
The system of claim 2 , wherein the tokenized certification standards comprise non-fungible tokens recorded on the second notarized ledger.
The system of claim 2 , wherein the second notarized ledger comprises the first notarized ledger.
The system of claim 1 , wherein the certification database comprises at least in part one of the following: a cloud database, a notarized ledger, a blockchain, a hash graph, a server, and a distributed file system.
The system of claim 1 , wherein the set of digital feature extraction algorithm implementations comprise implementations of one or more of the following: an image recognition algorithm, an audio recognition algorithm, a video recognition algorithm, a data recognition algorithm, or an edge detection algorithm.
The system of claim 1 , wherein invoking the smart contract interface includes minting a certified non-fungible token (c-NFT) on the first notarized ledger based on the digital test token data and the satisfaction level.
The system of claim 7 , wherein the operations further include indexing the c-NFT in a token database based on the set of token distinguishing features.
The system of claim 7 , wherein the c-NFT comprises a pointer to off ledger token information related to the digital test token data.
The system of claim 9 , wherein the token information comprises at least some of the digital test token data.
The system of claim 1 , wherein the satisfaction level comprises a similarity score derived from the at least one certification criteria of the identified at least one tokenized certification standard and the set of token distinguishing features.
The system of claim 11 , wherein the similarity score comprises multiple values.
The system of claim 1 , wherein the certification attributes and the set of token distinguishing features adhere to a common attribute space.
The system of claim 13 , wherein the common attribute space comprises an ontology or a namespace.
The system of claim 1 , wherein the identified at least one tokenized certification standard comprises at least one of the following: an educational standard, a test standard, an inspection standard, a lab standard, a health standard, a military standard, a physical therapy standard, a ratification, and an accreditation.
The system of claim 1 , wherein the digital test token data represents at least one of the following: an educational event, a test event, an inspection event, a lab event, a health event, a military event, a mechanical part, a game event, a work event, and a sporting event.
The system of claim 1 , wherein the first notarized ledger includes at least one of the following: a blockchain, a hash graph, a private ledger, a public ledger, a semi-public ledger, or a centralized ledger.
The system of claim 1 , wherein the smart contract interface invokes at least one of the following notarized ledger actions: create a new token on the first notarized ledger, delete a token, trade a token, sell a token, buy a token, publish a token, authenticate a token, validate a token, store a token, pay a royalty associated a token, copy a token, move a token, modify a token, or secure a token.
The system of claim 1 , wherein the smart contract interface invokes transferring a certified non-fungible token (c-NFT) from a first owner to a second owner, the second owner different than the first owner.
The system of claim 1 , wherein the satisfaction level indicates a failure of the digital test token data to satisfy the at least one certification criteria of the identified at least one tokenized certification standard.
Ref US20240104173A1: Claims:
A system for generating data feeds for users of cryptography-based storage applications, the system comprising: one or more processors; and a non-transitory computer-readable storage medium storing instructions, which when executed by the one or more processors cause the one or more processors to: detecting, using an application, a login request from a client device, wherein the login request comprises an on-chain address associated with a cryptography-based storage application corresponding to a user; retrieving on-chain operation data associated with the on-chain address, wherein the on-chain operation data comprises one or more program identifiers for one or more on-chain programs; extracting one or more login parameters from the login request; determining, based on the one or more login parameters associated with the on-chain address, whether to initiate a privacy-based login; in response to determining to not initiate the privacy-based login for the user: retrieving off-chain data associated with one or more interactions between the user and the application; and determining, via a machine learning model, one or more non-fungible tokens for a user based on the on-chain operation data and the off-chain data; and in response to determining to initiate the privacy-based login: generating, using the one or more program identifiers, a plurality of sets of non-fungible token attributes; inputting the plurality of sets of non-fungible token attributes into a machine learning model to determine available non-fungible tokens for the user; and providing, via a data feed, indications of the available non-fungible tokens to a user device of the user.
one or more processors; and
a non-transitory computer-readable storage medium storing instructions, which when executed by the one or more processors cause the one or more processors to: detecting, using an application, a login request from a client device, wherein the login request comprises an on-chain address associated with a cryptography-based storage application corresponding to a user; retrieving on-chain operation data associated with the on-chain address, wherein the on-chain operation data comprises one or more program identifiers for one or more on-chain programs; extracting one or more login parameters from the login request; determining, based on the one or more login parameters associated with the on-chain address, whether to initiate a privacy-based login; in response to determining to not initiate the privacy-based login for the user: r
[Truncated to input limit]