Inveniam Capital Partners, Inc., AKA Inveniam.io

United States of America

Back to Profile

1-74 of 74 for Inveniam Capital Partners, Inc., AKA Inveniam.io Sort by
Query
Aggregations
IP Type
        Patent 65
        Trademark 9
Jurisdiction
        United States 72
        Europe 1
        World 1
Date
2025 September 1
2025 (YTD) 3
2024 7
2023 4
2022 14
See more
IPC Class
H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system 46
H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems 44
H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols 36
G06Q 20/38 - Payment protocolsDetails thereof 24
G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme 22
See more
NICE Class
09 - Scientific and electric apparatus and instruments 7
42 - Scientific, technological and industrial services, research and design 3
Status
Pending 13
Registered / In Force 61

1.

Validating Authenticity of Electronic Documents Shared via Computer Networks

      
Application Number 19219747
Status Pending
Filing Date 2025-05-27
First Publication Date 2025-09-11
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • Deery, Brian
  • Snow, Paul
  • Paolini-Subramanya, Mahesh

Abstract

Authentication of electronic document is based on multiple digital signatures incorporated into a blockchain. Structured data, metadata, and instructions may be hashed to generate the multiple digital signatures for distribution via the blockchain. Any peer receiving the blockchain may then verify an authenticity of an electronic document based on any one or more of the multiple digital signatures incorporated into the blockchain.

IPC Classes  ?

  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • H04L 9/40 - Network security protocols

2.

SEPARATING HASHING FROM PROOF-OF-WORK IN BLOCKCHAIN ENVIRONMENTS

      
Application Number 19049930
Status Pending
Filing Date 2025-02-10
First Publication Date 2025-06-05
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Blockchain environments may mix-and-match different encryption, difficulty, and/or proof-of-work schemes when mining blockchain transactions. Each encryption, difficulty, and/or proof-of-work scheme may be separate, stand-alone programs, files, or third-party services. Blockchain miners may be agnostic to a particular coin's or network's encryption, difficulty, and/or proof-of-work schemes, thus allowing any blockchain miner to process or mine data in multiple blockchains. GPUs, ASICs, and other specialized processing hardware components may be deterred by forcing cache misses, cache latencies, and processor stalls. Hashing, difficulty, and/or proof-of-work schemes require less programming code, consume less storage space/usage in bytes, and execute faster. Blockchain mining schemes may further randomize byte or memory block access, further improve cryptographic security.

IPC Classes  ?

  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • A61B 1/018 - Instruments for performing medical examinations of the interior of cavities or tubes of the body by visual or photographical inspection, e.g. endoscopesIlluminating arrangements therefor characterised by internal passages or accessories therefor for receiving instruments
  • A61B 1/273 - Instruments for performing medical examinations of the interior of cavities or tubes of the body by visual or photographical inspection, e.g. endoscopesIlluminating arrangements therefor for the upper alimentary canal, e.g. oesophagoscopes, gastroscopes
  • A61J 1/05 - Containers specially adapted for medical or pharmaceutical purposes for collecting, storing or administering blood, plasma or medical fluids
  • A61J 1/06 - Ampoules or cartridges
  • A61K 49/00 - Preparations for testing in vivo
  • A61L 24/00 - Surgical adhesives or cementsAdhesives for colostomy devices
  • A61L 24/04 - Surgical adhesives or cementsAdhesives for colostomy devices containing macromolecular materials
  • A61L 31/06 - Macromolecular materials obtained otherwise than by reactions only involving carbon-to-carbon unsaturated bonds
  • A61M 5/00 - Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular wayAccessories therefor, e.g. filling or cleaning devices, arm rests
  • A61M 5/178 - Syringes
  • A61M 5/32 - NeedlesDetails of needles pertaining to their connection with syringe or hubAccessories for bringing the needle into, or holding the needle on, the bodyDevices for protection of needles
  • A61M 39/10 - Tube connectors or tube couplings
  • G06F 12/0815 - Cache consistency protocols
  • G06F 16/23 - Updating
  • G06F 16/2458 - Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
  • G06F 21/60 - Protecting data
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • H04L 9/08 - Key distribution
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system

3.

SYSTEMS AND METHODS FOR PROCESSING BLOCKCHAIN TRANSACTIONS

      
Application Number 18928136
Status Pending
Filing Date 2024-10-27
First Publication Date 2025-02-13
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

A blockchain system has an identity-based blockchain account including a primary chain, a secondary chain, and at least one key book applying to the account, the at least one key book having a key page. The system includes: a hardware processor; and a memory device storing instructions. When the instructions are executed by the processor, they cause the processor to: record a multi-signature transaction originating from the account in the secondary chain; associate the transaction with the key page of the at least one key book, the key page including (i) a signature-authorization rule, and (ii) a plurality of keys corresponding to a plurality of transaction authorizers; record, in the secondary chain, an authorization of the transaction from a transaction authorizer of the plurality of transaction authorizers; and once a number of authorizations recorded on the secondary chain satisfies the signature-authorization rule, record the transaction on the primary chain for execution.

IPC Classes  ?

  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • H04L 9/08 - Key distribution
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system

4.

LOAD BALANCING IN BLOCKCHAIN ENVIRONMENTS

      
Application Number 18430371
Status Pending
Filing Date 2024-02-01
First Publication Date 2024-11-21
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Hardware and software resources are load balanced when processing multiple blockchains. As more and more entities (whether public or private) are expected to generate their own blockchains for verification, a server or other resource in a blockchain environment may be over utilized. For example, as banks, websites, and retailers issue their own private cryptocoinage, the number of financial transactions may clog or hog networking and/or hardware resources. A blockchain load balancing mechanism thus allocates resources among the multiple blockchains.

IPC Classes  ?

  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • G06F 9/455 - EmulationInterpretationSoftware simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 16/18 - File system types
  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems

5.

Import and Export in Blockchain Environments

      
Application Number 18737643
Status Pending
Filing Date 2024-06-07
First Publication Date 2024-10-03
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Importation and exportation allows software services in blockchain environments. Blockchains may import data and export data, thus allowing blockchains to offer software services to clients (such as other blockchains). Individual users, businesses, and governments may create their own blockchains and subcontract or outsource operations to other blockchains. Moreover, the software services provided by blockchains may be publically ledgered by still other blockchains, thus providing two-way blockchain interactions and two-way ledgering for improved record keeping.

IPC Classes  ?

  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • G06F 9/455 - EmulationInterpretationSoftware simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 16/18 - File system types
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems

6.

TRANSACTIONAL SHARDING OF BLOCKCHAIN TRANSACTIONS

      
Application Number 18660962
Status Pending
Filing Date 2024-05-10
First Publication Date 2024-09-05
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • Douglass, Clay
  • Snow, Paul

Abstract

A complex cryptographic coinage transaction is transactionally sharded into multiple simple cryptographic coinage transactions. The complex cryptographic coinage transaction specifies cryptographic debits and/or deposits to/from multiple input accounts and/or multiple output accounts. The simple cryptographic coinage transactions, however, only specify a single one of the input accounts and/or a single one of the output accounts. A single server within a blockchain environment may thus process one of the simple cryptographic coinage transactions without requiring calls for data from other servers responsible for other accounts.

IPC Classes  ?

  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • G06F 16/182 - Distributed file systems
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems

7.

Data Backups Using Multiple Blockchains

      
Application Number 18438819
Status Pending
Filing Date 2024-02-12
First Publication Date 2024-08-15
Owner Invenian Capital Partners, Inc. (USA)
Inventor
  • O'Meara, Patrick D.
  • Cuddeback, Kevin M.
  • Bunker, Jr., Richard Gates
  • Yablunsky, Robert
  • Vidal, Quentin

Abstract

Data backups are performed in multiple blockchain environments. Digital pictures, movies, computer files, apps, and any other electronic data may be automatically backed-up, or duplicated, to multiple blockchain networks. First, an electronic data is written to a first blockchain network. A second, different, blockchain network is automatically selected based on many factors and/or parameters. Then, the electronic data is written to the second blockchain network. Still more duplicate copies of the electronic data may be redundantly written to third, fourth, and more blockchain networks. Any of the blockchain networks may send a confirmation that confirms the duplicate copy was written. One or more cryptographic proofs may be generated to prove the duplicate copies were stored to the multiple blockchain networks.

IPC Classes  ?

  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

8.

Separating hashing from proof-of-work in blockchain environments

      
Application Number 18613550
Grant Number 12225107
Status In Force
Filing Date 2024-03-22
First Publication Date 2024-08-15
Grant Date 2025-02-11
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Blockchain environments may mix-and-match different encryption, difficulty, and/or proof-of-work schemes when mining blockchain transactions. Each encryption, difficulty, and/or proof-of-work scheme may be separate, stand-alone programs, files, or third-party services. Blockchain miners may be agnostic to a particular coin's or network's encryption, difficulty, and/or proof-of-work schemes, thus allowing any blockchain miner to process or mine data in multiple blockchains. GPUs, ASICs, and other specialized processing hardware components may be deterred by forcing cache misses, cache latencies, and processor stalls. Hashing, difficulty, and/or proof-of-work schemes require less programming code, consume less storage space/usage in bytes, and execute faster. Blockchain mining schemes may further randomize byte or memory block access, further improve cryptographic security.

IPC Classes  ?

  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • A61B 1/018 - Instruments for performing medical examinations of the interior of cavities or tubes of the body by visual or photographical inspection, e.g. endoscopesIlluminating arrangements therefor characterised by internal passages or accessories therefor for receiving instruments
  • A61B 1/273 - Instruments for performing medical examinations of the interior of cavities or tubes of the body by visual or photographical inspection, e.g. endoscopesIlluminating arrangements therefor for the upper alimentary canal, e.g. oesophagoscopes, gastroscopes
  • A61J 1/05 - Containers specially adapted for medical or pharmaceutical purposes for collecting, storing or administering blood, plasma or medical fluids
  • A61J 1/06 - Ampoules or cartridges
  • A61K 49/00 - Preparations for testing in vivo
  • A61L 24/00 - Surgical adhesives or cementsAdhesives for colostomy devices
  • A61L 24/04 - Surgical adhesives or cementsAdhesives for colostomy devices containing macromolecular materials
  • A61L 31/06 - Macromolecular materials obtained otherwise than by reactions only involving carbon-to-carbon unsaturated bonds
  • A61M 5/00 - Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular wayAccessories therefor, e.g. filling or cleaning devices, arm rests
  • A61M 5/178 - Syringes
  • A61M 5/32 - NeedlesDetails of needles pertaining to their connection with syringe or hubAccessories for bringing the needle into, or holding the needle on, the bodyDevices for protection of needles
  • A61M 39/10 - Tube connectors or tube couplings
  • G06F 12/0815 - Cache consistency protocols
  • G06F 16/23 - Updating
  • G06F 16/2458 - Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
  • G06F 21/60 - Protecting data
  • H04L 9/08 - Key distribution
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

9.

Validating authenticity of electronic documents shared via computer networks

      
Application Number 18540677
Grant Number 12341906
Status In Force
Filing Date 2023-12-14
First Publication Date 2024-06-06
Grant Date 2025-06-24
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • Deery, Brian
  • Snow, Paul
  • Paolini-Subramanya, Mahesh

Abstract

Authentication of electronic document is based on multiple digital signatures incorporated into a blockchain. Structured data, metadata, and instructions may be hashed to generate the multiple digital signatures for distribution via the blockchain. Any peer receiving the blockchain may then verify an authenticity of an electronic document based on any one or more of the multiple digital signatures incorporated into the blockchain.

IPC Classes  ?

  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/40 - Network security protocols
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

10.

RAM hashing in blockchain environments

      
Application Number 18540067
Grant Number 12231535
Status In Force
Filing Date 2023-12-14
First Publication Date 2024-04-04
Grant Date 2025-02-18
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Blockchain environments may mix-and-match different encryption, difficulty, and/or proof-of-work schemes when mining blockchain transactions. Each encryption, difficulty, and/or proof-of-work scheme may be separate, stand-alone programs, files, or third-party services. Blockchain miners may be agnostic to a particular coin's or network's encryption, difficulty, and/or proof-of-work schemes, thus allowing any blockchain miner to process or mine data in multiple blockchains. GPUs, ASICs, and other specialized processing hardware components may be deterred by forcing cache misses, cache latencies, and processor stalls. Hashing, difficulty, and/or proof-of-work schemes require less programming code, consume less storage space/usage in bytes, and execute faster. Blockchain mining schemes may further randomize byte or memory block access, further improve cryptographic security.

IPC Classes  ?

  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • A61B 1/018 - Instruments for performing medical examinations of the interior of cavities or tubes of the body by visual or photographical inspection, e.g. endoscopesIlluminating arrangements therefor characterised by internal passages or accessories therefor for receiving instruments
  • A61B 1/273 - Instruments for performing medical examinations of the interior of cavities or tubes of the body by visual or photographical inspection, e.g. endoscopesIlluminating arrangements therefor for the upper alimentary canal, e.g. oesophagoscopes, gastroscopes
  • A61J 1/05 - Containers specially adapted for medical or pharmaceutical purposes for collecting, storing or administering blood, plasma or medical fluids
  • A61J 1/06 - Ampoules or cartridges
  • A61K 49/00 - Preparations for testing in vivo
  • A61L 24/00 - Surgical adhesives or cementsAdhesives for colostomy devices
  • A61L 24/04 - Surgical adhesives or cementsAdhesives for colostomy devices containing macromolecular materials
  • A61L 31/06 - Macromolecular materials obtained otherwise than by reactions only involving carbon-to-carbon unsaturated bonds
  • A61M 5/00 - Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular wayAccessories therefor, e.g. filling or cleaning devices, arm rests
  • A61M 5/178 - Syringes
  • A61M 5/32 - NeedlesDetails of needles pertaining to their connection with syringe or hubAccessories for bringing the needle into, or holding the needle on, the bodyDevices for protection of needles
  • A61M 39/10 - Tube connectors or tube couplings
  • G06F 12/0815 - Cache consistency protocols
  • G06F 16/23 - Updating
  • G06F 16/2458 - Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
  • G06F 21/60 - Protecting data
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • H04L 9/08 - Key distribution
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system

11.

Separating hashing from proof-of-work in blockchain environments

      
Application Number 17942270
Grant Number 11943334
Status In Force
Filing Date 2022-09-12
First Publication Date 2023-05-11
Grant Date 2024-03-26
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Blockchain environments may mix-and-match different encryption, difficulty, and/or proof-of-work schemes when mining blockchain transactions. Each encryption, difficulty, and/or proof-of-work scheme may be separate, stand-alone programs, files, or third-party services. Blockchain miners may be agnostic to a particular coin's or network's encryption, difficulty, and/or proof-of-work schemes, thus allowing any blockchain miner to process or mine data in multiple blockchains. GPUs, ASICs, and other specialized processing hardware components may be deterred by forcing cache misses, cache latencies, and processor stalls. Hashing, difficulty, and/or proof-of-work schemes require less programming code, consume less storage space/usage in bytes, and execute faster. Blockchain mining schemes may further randomize byte or memory block access, further improve cryptographic security.

IPC Classes  ?

  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • A61B 1/018 - Instruments for performing medical examinations of the interior of cavities or tubes of the body by visual or photographical inspection, e.g. endoscopesIlluminating arrangements therefor characterised by internal passages or accessories therefor for receiving instruments
  • A61B 1/273 - Instruments for performing medical examinations of the interior of cavities or tubes of the body by visual or photographical inspection, e.g. endoscopesIlluminating arrangements therefor for the upper alimentary canal, e.g. oesophagoscopes, gastroscopes
  • A61J 1/05 - Containers specially adapted for medical or pharmaceutical purposes for collecting, storing or administering blood, plasma or medical fluids
  • A61J 1/06 - Ampoules or cartridges
  • A61K 49/00 - Preparations for testing in vivo
  • A61L 24/00 - Surgical adhesives or cementsAdhesives for colostomy devices
  • A61L 24/04 - Surgical adhesives or cementsAdhesives for colostomy devices containing macromolecular materials
  • A61L 31/06 - Macromolecular materials obtained otherwise than by reactions only involving carbon-to-carbon unsaturated bonds
  • A61M 5/00 - Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular wayAccessories therefor, e.g. filling or cleaning devices, arm rests
  • A61M 5/178 - Syringes
  • A61M 5/32 - NeedlesDetails of needles pertaining to their connection with syringe or hubAccessories for bringing the needle into, or holding the needle on, the bodyDevices for protection of needles
  • A61M 39/10 - Tube connectors or tube couplings
  • G06F 12/0815 - Cache consistency protocols
  • G06F 16/23 - Updating
  • G06F 16/2458 - Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
  • G06F 21/60 - Protecting data
  • H04L 9/08 - Key distribution
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

12.

Apparatus and methods for producing data structures having internal self-references suitable for immutably representing and verifying data

      
Application Number 17981435
Grant Number 12231566
Status In Force
Filing Date 2022-11-06
First Publication Date 2023-02-23
Grant Date 2025-02-18
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • Beaudoin, Valérie
  • Grano, Evin T.
  • O'Meara, Patrick D.
  • Shotton, Jr., Charles T.

Abstract

Some embodiments described herein relate to a computer implemented method that includes performing a first work step associated with a first activity and with a first data product and performing a second work step associated with a second activity and associated with a second data product. A first chain of trust between the first work step and the second work step can be defined by defining a second manifest document that is associated with the second data product and that references a first manifest document associated with the first data product. An immutable data structure representing a second chain of trust independent of the first chain of trust can be defined by submitting the first manifest document and the second manifest document to a distributed ledger for validation.

IPC Classes  ?

  • G06F 21/60 - Protecting data
  • G06F 16/182 - Distributed file systems
  • G06F 16/23 - Updating
  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • G06F 16/93 - Document management systems
  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
  • G06Q 40/06 - Asset managementFinancial planning or analysis
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

13.

FEDERATED DATA ROOM SERVER AND METHOD FOR USE IN BLOCKCHAIN ENVIRONMENTS

      
Application Number 17979097
Status Pending
Filing Date 2022-11-02
First Publication Date 2023-02-16
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • Bunker, Jr., Richard Gates
  • O'Meara, Patrick D.
  • Polyzois, Christos Alkiviadis
  • Snow, Paul

Abstract

A federated-data-room server manages information about a collection of electronic documents residing elsewhere (under different organizational/customer control). The server can anchor documents to a blockchain, record usage history of each document, and provide access to the documents for authorized users. As a result, the federated-data-room server operates on customers' data, while leaving the data in control of the customers. At the same time, the federated-data-room server provides data access and enables traceability via blockchain recordation of document identifiers and document hash values.

IPC Classes  ?

  • G06Q 40/02 - Banking, e.g. interest calculation or account maintenance
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

14.

Load balancing in blockchain environments

      
Application Number 17967100
Grant Number 11930072
Status In Force
Filing Date 2022-10-17
First Publication Date 2023-02-02
Grant Date 2024-03-12
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Hardware and software resources are load balanced when processing multiple blockchains. As more and more entities (whether public or private) are expected to generate their own blockchains for verification, a server or other resource in a blockchain environment may be over utilized. For example, as banks, websites, and retailers issue their own private cryptocoinage, the number of financial transactions may clog or hog networking and/or hardware resources. A blockchain load balancing mechanism thus allocates resources among the multiple blockchains.

IPC Classes  ?

  • G06F 15/173 - Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star or snowflake
  • G06F 9/455 - EmulationInterpretationSoftware simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 16/18 - File system types
  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

15.

Systems and methods for processing blockchain transactions

      
Application Number 17844012
Grant Number 12007972
Status In Force
Filing Date 2022-06-19
First Publication Date 2022-12-22
Grant Date 2024-06-11
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

A blockchain system organized around digital identities and their accounts. Each account is treated as an independent blockchain and managed as a continuously growing Stateful Merkle Tree, while the blocks are treated as temporal synchronization points for all the chains in the system. Indexing of transactions in each block allows the system to operate at more than one synchronization level (frequency).

IPC Classes  ?

  • G06F 16/00 - Information retrievalDatabase structures thereforFile system structures therefor
  • G06F 16/22 - IndexingData structures thereforStorage structures
  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor

16.

Systems and methods for processing blockchain transactions

      
Application Number 17872229
Grant Number 12137179
Status In Force
Filing Date 2022-07-25
First Publication Date 2022-12-22
Grant Date 2024-11-05
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

A blockchain system has an identity-based blockchain account including a primary chain, a secondary chain, and at least one key book applying to the account, the at least one key book having a key page. The system includes: a hardware processor; and a memory device storing instructions. When the instructions are executed by the processor, they cause the processor to: record a multi-signature transaction originating from the account in the secondary chain; associate the transaction with the key page of the at least one key book, the key page including (i) a signature-authorization rule, and (ii) a plurality of keys corresponding to a plurality of transaction authorizers; record, in the secondary chain, an authorization of the transaction from a transaction authorizer of the plurality of transaction authorizers; and once a number of authorizations recorded on the secondary chain satisfies the signature-authorization rule, record the transaction on the primary chain for execution.

IPC Classes  ?

  • G06F 16/00 - Information retrievalDatabase structures thereforFile system structures therefor
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • H04L 9/08 - Key distribution
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system

17.

Digital contracts in blockchain environments

      
Application Number 17449291
Grant Number 11615398
Status In Force
Filing Date 2021-09-29
First Publication Date 2022-11-24
Grant Date 2023-03-28
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a contract identifier in a blockchain. Because there may be many digital contracts offered as virtual services, the contract identifier uniquely identifies a particular digital contract offered by a virtual machine, vendor or supplier. The blockchain is thus not burdened with the programming code that is required to execute the digital contract. The blockchain need only include or specify the contract identifier (and perhaps one or more contractual parameters), thus greatly simplifying the blockchain and reducing its size (in bytes) and processing requirements.

IPC Classes  ?

  • G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 20/12 - Payment architectures specially adapted for electronic shopping systems
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
  • H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
  • G06F 21/53 - Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity, buffer overflow or preventing unwanted data erasure by executing in a restricted environment, e.g. sandbox or secure virtual machine
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • H04L 67/10 - Protocols in which an application is distributed across nodes in the network

18.

Apparatus and methods for producing data structures having internal self-references suitable for immutably representing and verifying data

      
Application Number 16130628
Grant Number 11494402
Status In Force
Filing Date 2018-09-13
First Publication Date 2022-11-08
Grant Date 2022-11-08
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • Beaudoin, Valérie
  • Grano, Evin T.
  • O'Meara, Patrick D.
  • Shotton, Jr., Charles T.

Abstract

Some embodiments described herein relate to a computer implemented method that includes performing a first work step associated with a first activity and with a first data product and performing a second work step associated with a second activity and associated with a second data product. A first chain of trust between the first work step and the second work step can be defined by defining a second manifest document that is associated with the second data product and that references a first manifest document associated with the first data product. An immutable data structure representing a second chain of trust independent of the first chain of trust can be defined by submitting the first manifest document and the second manifest document to a distributed ledger for validation.

IPC Classes  ?

  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
  • G06F 21/60 - Protecting data
  • G06F 16/23 - Updating
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

19.

Computer system and method for programmatic collateralization services

      
Application Number 17705289
Grant Number 12008526
Status In Force
Filing Date 2022-03-26
First Publication Date 2022-09-29
Grant Date 2024-06-11
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • O'Meara, Patrick D.
  • Bunker, Jr., Richard Gates
  • Vidal, Quentin
  • Landers, Scott Jason
  • Spaulding, Jeannette L.
  • Cuddeback, Kevin M.
  • Vatsa, Sanjay
  • Stevens, David Todd
  • Creadon, Michael Carlo
  • Polyzois, Christos Alkiviadis

Abstract

A computer system processes a digital representation of an illiquid asset, to confirm accuracy of the digital representation and value of the asset, and generates an asset-information table indicating where the various sections of the digital representation are stored. The system also generates an asset-value token, financial-return tokens, and a data structure that includes a self-executing program. The program associates the asset-value token with the financial-return tokens, so that the illiquid asset becomes a collateral for a decentralized loan transaction implemented using blockchain technology. The use of blockchain technology for decentralized loan transactions enables immutable data traceability.

IPC Classes  ?

  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • G06Q 40/03 - CreditLoansProcessing thereof

20.

RAM hashing in blockchain environments

      
Application Number 17751864
Grant Number 11863305
Status In Force
Filing Date 2022-05-24
First Publication Date 2022-09-08
Grant Date 2024-01-02
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Blockchain environments may mix-and-match different encryption, difficulty, and/or proof-of-work schemes when mining blockchain transactions. Each encryption, difficulty, and/or proof-of-work scheme may be separate, stand-alone programs, files, or third-party services. Blockchain miners may be agnostic to a particular coin's or network's encryption, difficulty, and/or proof-of-work schemes, thus allowing any blockchain miner to process or mine data in multiple blockchains. GPUs, ASICs, and other specialized processing hardware components may be deterred by forcing cache misses, cache latencies, and processor stalls. Hashing, difficulty, and/or proof-of-work schemes require less programming code, consume less storage space/usage in bytes, and execute faster. Blockchain mining schemes may further randomize byte or memory block access, further improve cryptographic security.

IPC Classes  ?

  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06F 21/60 - Protecting data
  • G06F 16/23 - Updating
  • H04L 9/08 - Key distribution
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • G06F 16/2458 - Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
  • A61B 1/018 - Instruments for performing medical examinations of the interior of cavities or tubes of the body by visual or photographical inspection, e.g. endoscopesIlluminating arrangements therefor characterised by internal passages or accessories therefor for receiving instruments
  • A61B 1/273 - Instruments for performing medical examinations of the interior of cavities or tubes of the body by visual or photographical inspection, e.g. endoscopesIlluminating arrangements therefor for the upper alimentary canal, e.g. oesophagoscopes, gastroscopes
  • A61J 1/05 - Containers specially adapted for medical or pharmaceutical purposes for collecting, storing or administering blood, plasma or medical fluids
  • A61J 1/06 - Ampoules or cartridges
  • A61K 49/00 - Preparations for testing in vivo
  • A61L 24/00 - Surgical adhesives or cementsAdhesives for colostomy devices
  • A61L 24/04 - Surgical adhesives or cementsAdhesives for colostomy devices containing macromolecular materials
  • A61L 31/06 - Macromolecular materials obtained otherwise than by reactions only involving carbon-to-carbon unsaturated bonds
  • A61M 5/00 - Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular wayAccessories therefor, e.g. filling or cleaning devices, arm rests
  • A61M 5/178 - Syringes
  • A61M 5/32 - NeedlesDetails of needles pertaining to their connection with syringe or hubAccessories for bringing the needle into, or holding the needle on, the bodyDevices for protection of needles
  • A61M 39/10 - Tube connectors or tube couplings
  • G06F 12/0815 - Cache consistency protocols

21.

Import and export in blockchain environments

      
Application Number 17752668
Grant Number 12008015
Status In Force
Filing Date 2022-05-24
First Publication Date 2022-09-08
Grant Date 2024-06-11
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Importation and exportation allows software services in blockchain environments. Blockchains may import data and export data, thus allowing blockchains to offer software services to clients (such as other blockchains). Individual users, businesses, and governments may create their own blockchains and subcontract or outsource operations to other blockchains. Moreover, the software services provided by blockchains may be publically ledgered by still other blockchains, thus providing two-way blockchain interactions and two-way ledgering for improved record keeping.

IPC Classes  ?

  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • G06F 9/455 - EmulationInterpretationSoftware simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 16/18 - File system types
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems

22.

Inveniam Data 3.0 for Web 3.0

      
Application Number 018660831
Status Registered
Filing Date 2022-02-24
Registration Date 2022-06-30
Owner Inveniam Capital Partners, Inc. (USA)
NICE Classes  ? 09 - Scientific and electric apparatus and instruments

Goods & Services

Downloadable computer software for accessing, reading, and tracking information in the field of networked computers on a blockchain; Downloadable computer software for managing and validating cryptocurrency transactions using blockchain-based smart contracts; Downloadable computer software for managing and verifying cryptocurrency transactions on a blockchain; Downloadable computer software for managing cryptocurrency transactions using blockchain technology; Downloadable software for blockchain-based inventory management.

23.

Load balancing in blockchain environments

      
Application Number 17448942
Grant Number 11477271
Status In Force
Filing Date 2021-09-27
First Publication Date 2022-01-27
Grant Date 2022-10-18
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Hardware and software resources are load balanced when processing multiple blockchains. As more and more entities (whether public or private) are expected to generate their own blockchains for verification, a server or other resource in a blockchain environment may be over utilized. For example, as banks, websites, and retailers issue their own private cryptocoinage, the number of financial transactions may clog or hog networking and/or hardware resources. A blockchain load balancing mechanism thus allocates resources among the multiple blockchains.

IPC Classes  ?

  • G06F 15/173 - Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star or snowflake
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06F 9/455 - EmulationInterpretationSoftware simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • G06F 16/18 - File system types
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

24.

Digital contracts in blockchain environments

      
Application Number 17448954
Grant Number 11587069
Status In Force
Filing Date 2021-09-27
First Publication Date 2022-01-27
Grant Date 2023-02-21
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a contract identifier in a blockchain. Because there may be many digital contracts offered as virtual services, the contract identifier uniquely identifies a particular digital contract offered by a virtual machine, vendor or supplier. The blockchain is thus not burdened with the programming code that is required to execute the digital contract. The blockchain need only include or specify the contract identifier (and perhaps one or more contractual parameters), thus greatly simplifying the blockchain and reducing its size (in bytes) and processing requirements.

IPC Classes  ?

  • G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 20/12 - Payment architectures specially adapted for electronic shopping systems
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
  • G06F 21/53 - Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity, buffer overflow or preventing unwanted data erasure by executing in a restricted environment, e.g. sandbox or secure virtual machine
  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures

25.

Recordation of device usage to blockchains

      
Application Number 17450696
Grant Number 12118541
Status In Force
Filing Date 2021-10-13
First Publication Date 2022-01-27
Grant Date 2024-10-15
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

A personal blockchain is generated as a cloud-based software service in a blockchain environment. The personal blockchain immutably archives usage of any device, perhaps as requested by a user. However, some of the usage may be authorized for public disclosure, while other usage may be designated as private and restricted from public disclosure. The public disclosure may permit public ledgering by still other blockchains, thus providing two-way public/private ledgering for improved record keeping. Private usage, though, may only be documented by the personal blockchain.

IPC Classes  ?

  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06F 16/18 - File system types
  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • G06F 16/907 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/40 - Network security protocols
  • H04L 51/52 - User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail for supporting social networking services
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

26.

Decisional architectures in blockchain environments

      
Application Number 17449292
Grant Number 11687916
Status In Force
Filing Date 2021-09-29
First Publication Date 2022-01-20
Grant Date 2023-06-27
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a table identifier in a blockchain. Because there may be many digital contracts offered as virtual services, the table identifier uniquely identifies a particular decision table and/or the digital contract offered by a virtual machine, vendor or supplier. The blockchain is thus not burdened with the programming code that is required to execute the decision table and/or the digital contract. The blockchain need only include or specify the table identifier (and perhaps one or more contractual parameters), thus greatly simplifying the blockchain and reducing its size (in bytes) and processing requirements.

IPC Classes  ?

  • G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 20/12 - Payment architectures specially adapted for electronic shopping systems
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • G06F 21/53 - Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity, buffer overflow or preventing unwanted data erasure by executing in a restricted environment, e.g. sandbox or secure virtual machine
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
  • H04L 67/10 - Protocols in which an application is distributed across nodes in the network

27.

DISTRIBUTION OF BLOCKCHAIN VALIDATION

      
Application Number US2021040207
Publication Number 2022/006473
Status In Force
Filing Date 2021-07-01
Publication Date 2022-01-06
Owner INVENIAM CAPITAL PARTNERS, INC. (USA)
Inventor Snow, Paul

Abstract

A blockchain environment accumulates Merkle values calculated by individual nodal machines processing blockchain transactions conducted via a computer network. Any nodal machine (such as a miner) need only be sent Merkle child values as inputs. The nodal machine may then determine a hierarchical Merkle value based only on the Merkle child values provided as the inputs. Because the nodal machine only requires the Merkle child values, the nodal machine is relieved from downloading/ storing an entire blockchain. The nodal machine need only download the piece, segment, or portion of interest, which consumes far less memory byte space and requires far less processor time/tasks/cycles/operations. Moreover, because each nodal machine only needs to download a small block/byte portion of the blockchain, network packet traffic is greatly reduced.

IPC Classes  ?

  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system

28.

Distribution of Blockchain Validation

      
Application Number 17365951
Status Pending
Filing Date 2021-07-01
First Publication Date 2022-01-06
Owner INVENIAM CAPITAL PARTNERS, INC. (USA)
Inventor Snow, Paul

Abstract

A blockchain environment may accumulate Merkle values calculated by individual nodal machines. Any nodal machine (such as a miner system) need only be sent Merkle child values as inputs. The nodal machine may then determine a hierarchical Merkle value based only on the Merkle child values provided as the inputs. Because the nodal machine only requires the Merkle child values, the nodal machine is relieved from downloading/storing an entire blockchain. The nodal machine need only download the piece, segment, or portion of interest, which consumes far less memory byte space and requires far less processor time/tasks/cycles/operations. Moreover, because each nodal machine only needs to download a small block/byte portion of the blockchain, network packet traffic is greatly reduced.

IPC Classes  ?

  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/08 - Key distribution

29.

Artificial intelligence modifying federated learning models

      
Application Number 17323067
Grant Number 12192371
Status In Force
Filing Date 2021-05-18
First Publication Date 2021-10-21
Grant Date 2025-01-07
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • Snow, Paul
  • Deery, Brian
  • Paolini-Subramanya, Mahesh
  • Nadeau, Jason

Abstract

Data verification in federate learning is faster and simpler. As artificial intelligence grows in usage, data verification is needed to prove custody and/or control. Electronic data representing an original version of training data may be hashed to generate one or more digital signatures. The digital signatures may then be incorporated into one or more blockchains for historical documentation. Any auditor may then quickly verify and/or reproduce the training data using the digital signatures. For example, a current version of the training data may be hashed and compared to the digital signatures generated from the current version of the training data. If the digital signatures match, then the training data has not changed since its creation. However, if the digital signatures do not match, then the training data has changed since its creation. The auditor may thus flag the training data for additional investigation and scrutiny.

IPC Classes  ?

  • G06F 21/00 - Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06N 20/00 - Machine learning
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • H04L 9/08 - Key distribution
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

30.

Validating authenticity of electronic documents shared via computer networks

      
Application Number 17322994
Grant Number 11863686
Status In Force
Filing Date 2021-05-18
First Publication Date 2021-09-02
Grant Date 2024-01-02
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • Deery, Brian
  • Snow, Paul
  • Paolini-Subramanya, Mahesh

Abstract

Authentication of electronic document is based on multiple digital signatures incorporated into a blockchain. Structured data, metadata, and instructions may be hashed to generate the multiple digital signatures for distribution via the blockchain. Any peer receiving the blockchain may then verify an authenticity of an electronic document based on any one or more of the multiple digital signatures incorporated into the blockchain.

IPC Classes  ?

  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/40 - Network security protocols
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

31.

Smart contracts in blockchain environments

      
Application Number 17323036
Grant Number 11676132
Status In Force
Filing Date 2021-05-18
First Publication Date 2021-09-02
Grant Date 2023-06-13
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a blockchain. Because there may be many digital contracts offered as virtual services, the contract identifier uniquely identifies a particular decision table and/or the digital contract offered by a virtual machine, vendor or supplier. The blockchain is thus not burdened with the programming code that is required to execute the decision table and/or the digital contract. The blockchain need only include or specify the contract identifier (and perhaps one or more contractual parameters), thus greatly simplifying the blockchain and reducing its size (in bytes) and processing requirements.

IPC Classes  ?

  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 20/12 - Payment architectures specially adapted for electronic shopping systems
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
  • G06F 21/53 - Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity, buffer overflow or preventing unwanted data erasure by executing in a restricted environment, e.g. sandbox or secure virtual machine
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
  • H04L 67/10 - Protocols in which an application is distributed across nodes in the network

32.

ACCUMULATE

      
Serial Number 97005792
Status Pending
Filing Date 2021-09-01
Owner Inveniam Capital Partners, Inc. ()
NICE Classes  ? 09 - Scientific and electric apparatus and instruments

Goods & Services

Downloadable computer software for accessing, reading, and tracking information in the field of networked computers on a blockchain; Downloadable computer software for managing and validating cryptocurrency transactions using blockchain-based smart contracts; Downloadable computer software for managing and verifying cryptocurrency transactions on a blockchain; Downloadable computer software for managing cryptocurrency transactions using blockchain technology; Downloadable software for blockchain-based inventory management

33.

ACCUMULATEPROTOCOL

      
Serial Number 97005796
Status Pending
Filing Date 2021-09-01
Owner Inveniam Capital Partners, Inc. ()
NICE Classes  ? 09 - Scientific and electric apparatus and instruments

Goods & Services

Downloadable computer software for accessing, reading, and tracking information in the field of networked computers on a blockchain; Downloadable computer software for managing and validating cryptocurrency transactions using blockchain-based smart contracts; Downloadable computer software for managing and verifying cryptocurrency transactions on a blockchain; Downloadable computer software for managing cryptocurrency transactions using blockchain technology; Downloadable software for blockchain-based inventory management

34.

INVENIAM DATA 3.0 FOR WEB 3.0

      
Serial Number 97005803
Status Pending
Filing Date 2021-09-01
Owner Inveniam Capital Partners, Inc. ()
NICE Classes  ? 09 - Scientific and electric apparatus and instruments

Goods & Services

Downloadable computer software for accessing, reading, and tracking information in the field of networked computers on a blockchain; Downloadable computer software for managing and validating cryptocurrency transactions using blockchain-based smart contracts; Downloadable computer software for managing and verifying cryptocurrency transactions on a blockchain; Downloadable computer software for managing cryptocurrency transactions using blockchain technology; Downloadable software for blockchain-based inventory management

35.

ACCUMULATENETWORK

      
Serial Number 97005801
Status Pending
Filing Date 2021-09-01
Owner Inveniam Capital Partners, Inc. ()
NICE Classes  ? 09 - Scientific and electric apparatus and instruments

Goods & Services

Downloadable computer software for accessing, reading, and tracking information in the field of networked computers on a blockchain; Downloadable computer software for managing and validating cryptocurrency transactions using blockchain-based smart contracts; Downloadable computer software for managing and verifying cryptocurrency transactions on a blockchain; Downloadable computer software for managing cryptocurrency transactions using blockchain technology; Downloadable software for blockchain-based inventory management

36.

Separating hashing from proof-of-work in blockchain environments

      
Application Number 17037980
Grant Number 11444749
Status In Force
Filing Date 2020-09-30
First Publication Date 2021-07-22
Grant Date 2022-09-13
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Blockchain environments may mix-and-match different encryption, difficulty, and/or proof-of-work schemes when mining blockchain transactions. Each encryption, difficulty, and/or proof-of-work scheme may be separate, stand-alone programs, files, or third-party services. Blockchain miners may be agnostic to a particular coin's or network's encryption, difficulty, and/or proof-of-work schemes, thus allowing any blockchain miner to process or mine data in multiple blockchains. GPUs, ASICs, and other specialized processing hardware components may be deterred by forcing cache misses, cache latencies, and processor stalls. Hashing, difficulty, and/or proof-of-work schemes require less programming code, consume less storage space/usage in bytes, and execute faster. Blockchain mining schemes may further randomize byte or memory block access, further improve cryptographic security.

IPC Classes  ?

  • G06F 11/30 - Monitoring
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06F 16/2458 - Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06F 21/60 - Protecting data
  • G06F 16/23 - Updating
  • A61B 1/018 - Instruments for performing medical examinations of the interior of cavities or tubes of the body by visual or photographical inspection, e.g. endoscopesIlluminating arrangements therefor characterised by internal passages or accessories therefor for receiving instruments
  • A61B 1/273 - Instruments for performing medical examinations of the interior of cavities or tubes of the body by visual or photographical inspection, e.g. endoscopesIlluminating arrangements therefor for the upper alimentary canal, e.g. oesophagoscopes, gastroscopes
  • A61J 1/05 - Containers specially adapted for medical or pharmaceutical purposes for collecting, storing or administering blood, plasma or medical fluids
  • A61J 1/06 - Ampoules or cartridges
  • A61K 49/00 - Preparations for testing in vivo
  • A61L 24/00 - Surgical adhesives or cementsAdhesives for colostomy devices
  • A61L 24/04 - Surgical adhesives or cementsAdhesives for colostomy devices containing macromolecular materials
  • A61L 31/06 - Macromolecular materials obtained otherwise than by reactions only involving carbon-to-carbon unsaturated bonds
  • A61M 5/00 - Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular wayAccessories therefor, e.g. filling or cleaning devices, arm rests
  • A61M 5/178 - Syringes
  • A61M 5/32 - NeedlesDetails of needles pertaining to their connection with syringe or hubAccessories for bringing the needle into, or holding the needle on, the bodyDevices for protection of needles
  • A61M 39/10 - Tube connectors or tube couplings
  • G06F 12/0815 - Cache consistency protocols
  • H04L 9/08 - Key distribution
  • G06F 12/14 - Protection against unauthorised use of memory
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

37.

RAM hashing in blockchain environments

      
Application Number 17037995
Grant Number 11343075
Status In Force
Filing Date 2020-09-30
First Publication Date 2021-07-22
Grant Date 2022-05-24
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Blockchain environments may mix-and-match different encryption, difficulty, and/or proof-of-work schemes when mining blockchain transactions. Each encryption, difficulty, and/or proof-of-work scheme may be separate, stand-alone programs, files, or third-party services. Blockchain miners may be agnostic to a particular coin's or network's encryption, difficulty, and/or proof-of-work schemes, thus allowing any blockchain miner to process or mine data in multiple blockchains. GPUs, ASICs, and other specialized processing hardware components may be deterred by forcing cache misses, cache latencies, and processor stalls. Hashing, difficulty, and/or proof-of-work schemes require less programming code, consume less storage space/usage in bytes, and execute faster. Blockchain mining schemes may further randomize byte or memory block access, further improve cryptographic security.

IPC Classes  ?

  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06F 16/2458 - Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06F 16/23 - Updating
  • G06F 21/60 - Protecting data

38.

Data structure having internal self-references suitable for immutably representing and verifying data generated over time

      
Application Number 16130619
Grant Number 10873457
Status In Force
Filing Date 2018-09-13
First Publication Date 2020-12-22
Grant Date 2020-12-22
Owner INVENIAM CAPITAL PARTNERS, INC. (USA)
Inventor
  • Beaudoin, Valérie
  • Grano, Evin T.
  • O'Meara, Patrick D.
  • Shotton, Charles T.

Abstract

Some embodiments described herein relate to a computer implemented method that includes receiving a token that includes a reference to a first encrypted archive recorded in a distributed ledger. The first encrypted archive can be decrypted using the token to retrieve a first manifest document, which can be associated with a first activity of the complex transaction. The first manifest document can identify a second encrypted archive. The second encrypted archive can be decrypted using the token to retrieve a second manifest document, which can be associated with a second activity of the complex transaction. The second manifest document can include a reference to a data product, which can be retrieved. A continuity of the complex transaction between the second activity and the first activity can be verified based on the data product.

IPC Classes  ?

  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06Q 40/06 - Asset managementFinancial planning or analysis
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06F 16/93 - Document management systems
  • G06F 16/182 - Distributed file systems

39.

Import and export in blockchain environments

      
Application Number 16905947
Grant Number 11347769
Status In Force
Filing Date 2020-06-19
First Publication Date 2020-10-08
Grant Date 2022-05-31
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Importation and exportation allows software services in blockchain environments. Blockchains may import data and export data, thus allowing blockchains to offer software services to clients (such as other blockchains). Individual users, businesses, and governments may create their own blockchains and subcontract or outsource operations to other blockchains. Moreover, the software services provided by blockchains may be publically ledgered by still other blockchains, thus providing two-way blockchain interactions and two-way ledgering for improved record keeping.

IPC Classes  ?

  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06F 9/455 - EmulationInterpretationSoftware simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 16/18 - File system types
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • G06Q 20/38 - Payment protocolsDetails thereof

40.

Recordation of device usage to blockchains

      
Application Number 16905958
Grant Number 11587074
Status In Force
Filing Date 2020-06-19
First Publication Date 2020-10-08
Grant Date 2023-02-21
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

A personal blockchain is generated as a cloud-based software service in a blockchain environment. The personal blockchain immutably archives usage of any device, perhaps as requested by a user. However, some of the usage may be authorized for public disclosure, while other usage may be designated as private and restricted from public disclosure. The public disclosure may permit public ledgering by still other blockchains, thus providing two-way public/private ledgering for improved record keeping. Private usage, though, may only be documented by the personal blockchain.

IPC Classes  ?

  • G06Q 20/38 - Payment protocolsDetails thereof
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • G06F 16/907 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
  • G06F 16/18 - File system types
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/40 - Network security protocols
  • H04L 51/52 - User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail for supporting social networking services
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

41.

Digital contracts in blockchain environments

      
Application Number 16905961
Grant Number 11531981
Status In Force
Filing Date 2020-06-19
First Publication Date 2020-10-08
Grant Date 2022-12-20
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a contract identifier in a blockchain. Because there may be many digital contracts offered as services, the contract identifier uniquely identifies a particular digital contract offered by a vendor or supplier. The blockchain is thus not burdened with the programming code that is required to execute the digital contract. The blockchain need only include or specify the contract identifier (and perhaps one or more contractual parameters), thus greatly simplifying the blockchain and reducing its size (in bytes) and processing requirements.

IPC Classes  ?

  • G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 20/12 - Payment architectures specially adapted for electronic shopping systems
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
  • G06F 21/53 - Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity, buffer overflow or preventing unwanted data erasure by executing in a restricted environment, e.g. sandbox or secure virtual machine
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

42.

Auditing of electronic documents

      
Application Number 16905945
Grant Number 11580534
Status In Force
Filing Date 2020-06-19
First Publication Date 2020-10-08
Grant Date 2023-02-14
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • Snow, Paul
  • Nadeau, Jason
  • Paolini-Subramanya, Mahesh
  • Deery, Brian

Abstract

Auditing of mortgage documents is faster and simpler. An electronic mortgage application often contains or references a collection of many separate electronic mortgage documents. Electronic data representing an original version of an electronic mortgage document and its current version may be hashed to generate digital signatures. Any auditor may then quickly compare the digital signatures. If the digital signatures match, then the audit reveals that the electronic mortgage document has not changed since its creation. However, if the digital signatures do not match, then the electronic mortgage document has changed since its creation. The auditor may thus flag the electronic mortgage document for additional auditing processes.

IPC Classes  ?

  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 40/02 - Banking, e.g. interest calculation or account maintenance
  • G06Q 50/18 - Legal services
  • G06Q 50/16 - Real estate
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system

43.

Recordation of device usage to public/private blockchains

      
Application Number 16905955
Grant Number 11580535
Status In Force
Filing Date 2020-06-19
First Publication Date 2020-10-08
Grant Date 2023-02-14
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

A personal blockchain is generated as a cloud-based software service in a blockchain environment. The personal blockchain immutably archives usage of any device, perhaps as requested by a user. However, some of the usage may be authorized for public disclosure, while other usage may be designated as private and restricted from public disclosure. The public disclosure may permit public ledgering by still other blockchains, thus providing two-way public/private ledgering for improved record keeping. Private usage, though, may only be documented by the personal blockchain.

IPC Classes  ?

  • G06Q 20/38 - Payment protocolsDetails thereof
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • G06F 16/907 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
  • G06F 16/18 - File system types
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/40 - Network security protocols
  • H04L 51/52 - User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail for supporting social networking services
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

44.

Due diligence in electronic documents

      
Application Number 16877648
Grant Number 11468510
Status In Force
Filing Date 2020-05-19
First Publication Date 2020-09-03
Grant Date 2022-10-11
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • Snow, Paul
  • Deery, Brian
  • Nadeau, Jason
  • Paolini-Subramanya, Mahesh

Abstract

Due diligence of mortgage documents is faster and simpler. An electronic mortgage application often contains or references a collection of many separate electronic mortgage documents. Electronic data representing an original version of an electronic mortgage document and its current version may be hashed to generate digital signatures. Any auditor may then quickly conduct the due diligence by comparing the digital signatures. If the digital signatures match, then the due diligence reveals that the electronic mortgage document has not changed since its creation. However, if the digital signatures do not match, then the electronic mortgage document has changed since its creation. The auditor may thus flag the electronic mortgage document for additional due diligence. Regardless, a result of the due diligence may be incorporated into one or more blockchains.

IPC Classes  ?

  • G06Q 40/02 - Banking, e.g. interest calculation or account maintenance
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

45.

Due diligence in electronic documents

      
Application Number 16877665
Grant Number 11443371
Status In Force
Filing Date 2020-05-19
First Publication Date 2020-09-03
Grant Date 2022-09-13
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • Snow, Paul
  • Deery, Brian
  • Nadeau, Jason
  • Paolini-Subramanya, Mahesh

Abstract

Due diligence of documents is faster and simpler. An electronic mortgage application, for example, often contains or references a collection of many separate electronic documents. Electronic data representing an original version of an electronic document and its current version may be hashed to generate digital signatures. Any auditor may then quickly conduct the due diligence by comparing the digital signatures. If the digital signatures match, then the due diligence reveals that the electronic document has not changed since its creation. However, if the digital signatures do not match, then the electronic document has changed since its creation. The auditor may thus flag the electronic document for additional due diligence. Regardless, a result of the due diligence may be incorporated into one or more blockchains.

IPC Classes  ?

  • G06Q 40/02 - Banking, e.g. interest calculation or account maintenance
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

46.

Blockchain recordation of device usage

      
Application Number 16877614
Grant Number 11044097
Status In Force
Filing Date 2020-05-19
First Publication Date 2020-09-03
Grant Date 2021-06-22
Owner INVENIAM CAPITAL PARTNERS, INC. (USA)
Inventor
  • Snow, Paul
  • Deery, Brian
  • Paolini-Subramanya, Mahesh
  • Nadeau, Jason

Abstract

Data verification in federate learning is faster and simpler. As artificial intelligence grows in usage, data verification is needed to prove custody and/or control. Electronic data representing an original version of training data may be hashed to generate one or more digital signatures. The digital signatures may then be incorporated into one or more blockchains for historical documentation. Any auditor may then quickly verify and/or reproduce the training data using the digital signatures. For example, a current version of the training data may be hashed and compared to the digital signatures generated from the current version of the training data. If the digital signatures match, then the training data has not changed since its creation. However, if the digital signatures do not match, then the training data has changed since its creation. The auditor may thus flag the training data for additional investigation and scrutiny.

IPC Classes  ?

  • H04W 12/06 - Authentication
  • H04L 29/06 - Communication control; Communication processing characterised by a protocol
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06N 20/00 - Machine learning
  • H04L 9/08 - Key distribution
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems

47.

Due diligence in electronic documents

      
Application Number 16877629
Grant Number 11443370
Status In Force
Filing Date 2020-05-19
First Publication Date 2020-09-03
Grant Date 2022-09-13
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • Snow, Paul
  • Deery, Brian
  • Nadeau, Jason
  • Paolini-Subramanya, Mahesh

Abstract

Due diligence of documents is faster and simpler. An electronic mortgage application, for example, often contains or references a collection of many separate electronic documents. Electronic data representing an original version of an electronic document and its current version may be hashed to generate digital signatures. Any auditor may then quickly conduct the due diligence by comparing the digital signatures. If the digital signatures match, then the due diligence reveals that the electronic document has not changed since its creation. However, if the digital signatures do not match, then the electronic document has changed since its creation. The auditor may thus flag the electronic document for additional due diligence. Regardless, a result of the due diligence may be incorporated into one or more blockchains.

IPC Classes  ?

  • G06Q 40/02 - Banking, e.g. interest calculation or account maintenance
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

48.

Digital contracts in blockchain environments

      
Application Number 16116967
Grant Number 11276056
Status In Force
Filing Date 2018-08-30
First Publication Date 2020-02-06
Grant Date 2022-03-15
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a contract identifier in a blockchain. Because there may be many digital contracts offered as services, the contract identifier uniquely identifies a particular digital contract offered by a vendor or supplier. The blockchain is thus not burdened with the programming code that is required to execute the digital contract. The blockchain need only include or specify the contract identifier (and perhaps one or more contractual parameters), thus greatly simplifying the blockchain and reducing its size (in bytes) and processing requirements.

IPC Classes  ?

  • G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 20/12 - Payment architectures specially adapted for electronic shopping systems
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
  • G06F 16/29 - Geographical information databases
  • G06F 21/53 - Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity, buffer overflow or preventing unwanted data erasure by executing in a restricted environment, e.g. sandbox or secure virtual machine
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures

49.

Digital contracts in blockchain environments

      
Application Number 16116969
Grant Number 11295296
Status In Force
Filing Date 2018-08-30
First Publication Date 2020-02-06
Grant Date 2022-04-05
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a contract identifier in a blockchain. Because there may be many digital contracts offered as virtual services, the contract identifier uniquely identifies a particular digital contract offered by a virtual machine, vendor or supplier. The blockchain is thus not burdened with the programming code that is required to execute the digital contract. The blockchain need only include or specify the contract identifier (and perhaps one or more contractual parameters), thus greatly simplifying the blockchain and reducing its size (in bytes) and processing requirements.

IPC Classes  ?

  • G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 20/12 - Payment architectures specially adapted for electronic shopping systems
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
  • G06F 16/29 - Geographical information databases
  • G06F 21/53 - Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity, buffer overflow or preventing unwanted data erasure by executing in a restricted environment, e.g. sandbox or secure virtual machine
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures

50.

Digital contracts in blockchain environments

      
Application Number 16116972
Grant Number 11334874
Status In Force
Filing Date 2018-08-30
First Publication Date 2020-02-06
Grant Date 2022-05-17
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a contract identifier in a blockchain. Because there may be many digital contracts offered as virtual services, the contract identifier uniquely identifies a particular digital contract offered by a virtual machine, vendor or supplier. The blockchain is thus not burdened with the programming code that is required to execute the digital contract. The blockchain need only include or specify the contract identifier (and perhaps one or more contractual parameters), thus greatly simplifying the blockchain and reducing its size (in bytes) and processing requirements.

IPC Classes  ?

  • G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 20/12 - Payment architectures specially adapted for electronic shopping systems
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • A41D 31/06 - Thermally protective, e.g. insulating
  • D03D 15/47 - Woven fabrics characterised by the material, structure or properties of the fibres, filaments, yarns, threads or other warp or weft elements used characterised by the structure of the yarns or threads multicomponent, e.g. blended yarns or threads
  • D03D 15/56 - Woven fabrics characterised by the material, structure or properties of the fibres, filaments, yarns, threads or other warp or weft elements used characterised by the properties of the yarns or threads elastic
  • D03D 15/567 - Shapes or effects upon shrinkage
  • A41D 1/00 - Garments
  • A41D 11/00 - Garments for children
  • A41D 13/005 - Professional, industrial or sporting protective garments, e.g. surgeons' gowns or garments protecting against blows or punches with controlled internal environment with controlled temperature
  • A41D 15/00 - Convertible garments
  • A41D 31/00 - Materials specially adapted for outerwear
  • D02G 3/36 - Cored or coated yarns or threads
  • D02G 3/44 - Yarns or threads characterised by the purpose for which they are designed
  • D03D 1/00 - Woven fabrics designed to make specified articles
  • G05B 15/02 - Systems controlled by a computer electric
  • H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
  • G06F 16/29 - Geographical information databases
  • G06F 21/53 - Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity, buffer overflow or preventing unwanted data erasure by executing in a restricted environment, e.g. sandbox or secure virtual machine
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
  • A41D 3/00 - Overgarments
  • G06F 1/16 - Constructional details or arrangements

51.

Digital contracts in blockchain environments

      
Application Number 16116975
Grant Number 11348097
Status In Force
Filing Date 2018-08-30
First Publication Date 2020-02-06
Grant Date 2022-05-31
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a contract identifier in a blockchain. Because there may be many digital contracts offered as virtual services, the contract identifier uniquely identifies a particular digital contract offered by a virtual machine, vendor or supplier. The blockchain is thus not burdened with the programming code that is required to execute the digital contract. The blockchain need only include or specify the contract identifier (and perhaps one or more contractual parameters), thus greatly simplifying the blockchain and reducing its size (in bytes) and processing requirements.

IPC Classes  ?

  • G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06Q 20/12 - Payment architectures specially adapted for electronic shopping systems
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
  • G06F 16/29 - Geographical information databases
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
  • G06Q 20/38 - Payment protocolsDetails thereof
  • A41D 31/06 - Thermally protective, e.g. insulating
  • D03D 15/47 - Woven fabrics characterised by the material, structure or properties of the fibres, filaments, yarns, threads or other warp or weft elements used characterised by the structure of the yarns or threads multicomponent, e.g. blended yarns or threads
  • D03D 15/56 - Woven fabrics characterised by the material, structure or properties of the fibres, filaments, yarns, threads or other warp or weft elements used characterised by the properties of the yarns or threads elastic
  • D03D 15/567 - Shapes or effects upon shrinkage
  • A41D 1/00 - Garments
  • A41D 11/00 - Garments for children
  • A41D 13/005 - Professional, industrial or sporting protective garments, e.g. surgeons' gowns or garments protecting against blows or punches with controlled internal environment with controlled temperature
  • A41D 15/00 - Convertible garments
  • A41D 31/00 - Materials specially adapted for outerwear
  • D02G 3/36 - Cored or coated yarns or threads
  • D02G 3/44 - Yarns or threads characterised by the purpose for which they are designed
  • D03D 1/00 - Woven fabrics designed to make specified articles
  • G05B 15/02 - Systems controlled by a computer electric
  • G06F 21/53 - Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity, buffer overflow or preventing unwanted data erasure by executing in a restricted environment, e.g. sandbox or secure virtual machine
  • A41D 3/00 - Overgarments
  • G06F 1/16 - Constructional details or arrangements

52.

Stable cryptocurrency coinage

      
Application Number 16191574
Grant Number 11328290
Status In Force
Filing Date 2018-11-15
First Publication Date 2020-02-06
Grant Date 2022-05-10
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • Snow, Paul
  • Deery, Brian
  • Gillas, Gavin

Abstract

A two-coin mechanism for maintaining a stable value of cryptographic coinage traded in a decentralized market exchange without requiring a reserve. A pegged cryptographic token and a variable-priced cryptographic token are both traded in the reserveless decentralized market exchange. The pegged cryptographic token and the variable-priced cryptographic token are value related based on a cryptographic exchange rate. Whenever a market transaction is processed (such as a buy or sell order), at least one of a destruction operation and a creation operation are performed. The destruction operation destroys at least one of the pegged cryptographic token and/or the variable-priced cryptographic token, while the creation operation creates new ones of the pegged cryptographic token and/or the variable-priced cryptographic token. The two-coin mechanism thus implements a decentralized and algorithmic monetary policy that removes and/or deposits cryptographic tokens to/from the reserveless decentralized market exchange to alter supply and to maintain stable coinage values.

IPC Classes  ?

  • G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme

53.

Debt recordation to blockchains

      
Application Number 16191585
Grant Number 11044095
Status In Force
Filing Date 2018-11-15
First Publication Date 2020-02-06
Grant Date 2021-06-22
Owner INVENIAM CAPITAL PARTNERS, INC. (USA)
Inventor Lynde, Zachary

Abstract

Accounts receivables, accounts payables, and other debt instruments are registered to blocks of data in a blockchain. The blockchain may then be dispersed to subscribers for inspection. Any subscriber may inspect the blockchain, evaluate the debt instruments registered to the blockchain, and conduct automated, electronic purchases of any debt instruments. Smart, digital contracts executed by the blockchain may automate purchase of the debt instruments.

IPC Classes  ?

  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06Q 20/10 - Payment architectures specially adapted for electronic funds transfer [EFT] systemsPayment architectures specially adapted for home banking systems
  • H04L 9/30 - Public key, i.e. encryption algorithm being computationally infeasible to invert and users' encryption keys not requiring secrecy

54.

Smart contracts in blockchain environments

      
Application Number 16191595
Grant Number 11042871
Status In Force
Filing Date 2018-11-15
First Publication Date 2020-02-06
Grant Date 2021-06-22
Owner INVENIAM CAPITAL PARTNERS, INC. (USA)
Inventor Snow, Paul

Abstract

Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a blockchain. Because there may be many digital contracts offered as virtual services, the contract identifier uniquely identifies a particular decision table and/or the digital contract offered by a virtual machine, vendor or supplier. The blockchain is thus not burdened with the programming code that is required to execute the decision table and/or the digital contract. The blockchain need only include or specify the contract identifier (and perhaps one or more contractual parameters), thus greatly simplifying the blockchain and reducing its size (in bytes) and processing requirements.

IPC Classes  ?

  • H04L 29/06 - Communication control; Communication processing characterised by a protocol
  • G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06F 16/29 - Geographical information databases
  • G06F 21/53 - Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity, buffer overflow or preventing unwanted data erasure by executing in a restricted environment, e.g. sandbox or secure virtual machine
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 20/12 - Payment architectures specially adapted for electronic shopping systems
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system

55.

Stable cryptocurrency coinage

      
Application Number 16351592
Grant Number 11164250
Status In Force
Filing Date 2019-03-13
First Publication Date 2020-02-06
Grant Date 2021-11-02
Owner INVENIAM CAPITAL PARTNERS, INC. (USA)
Inventor
  • Snow, Paul
  • Deery, Brian
  • Gillas, Gavin

Abstract

A multi-coin mechanism for maintaining a stable value of cryptographic coinage traded in a decentralized market exchange without requiring a reserve. Multiple, pegged cryptographic tokens are traded in the reserveless decentralized market exchange. Each of the multiple, pegged cryptographic tokens may be pegged to a different asset (such as different currencies and/or commodities). The multiple, pegged cryptographic tokens are value related based on cryptographic exchange rates. Whenever a market transaction is processed (such as a buy or sell order), at least one of a destruction operation and a creation operation are performed. The destruction operation destroys at least one of the pegged cryptographic tokens, while the creation operation creates new ones of the pegged cryptographic tokens n. The multi-coin mechanism thus implements a decentralized and algorithmic monetary policy that removes and/or deposits cryptographic tokens to/from the reserveless decentralized market exchange to alter supply and to maintain stable coinage values.

IPC Classes  ?

  • G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
  • G06Q 40/04 - Trading Exchange, e.g. stocks, commodities, derivatives or currency exchange
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme

56.

Factom protocol in blockchain environments

      
Application Number 16351597
Grant Number 11205172
Status In Force
Filing Date 2019-03-13
First Publication Date 2020-02-06
Grant Date 2021-12-21
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

A Factom protocol cost effectively separates any blockchain (such as the Bitcoin blockchain) from any cryptocurrency (such as the Bitcoin cryptocurrency). The Factom protocol provides client-defined Chains of Entries, client-side validation of Entries, a distributed consensus algorithm for recording the Entries, and a blockchain anchoring approach for security.

IPC Classes  ?

  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
  • G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06F 16/29 - Geographical information databases
  • G06F 21/53 - Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity, buffer overflow or preventing unwanted data erasure by executing in a restricted environment, e.g. sandbox or secure virtual machine
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 20/12 - Payment architectures specially adapted for electronic shopping systems
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system

57.

Digital contracts in blockchain environments

      
Application Number 16116970
Grant Number 11620642
Status In Force
Filing Date 2018-08-30
First Publication Date 2020-02-06
Grant Date 2023-04-04
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a contract identifier in a blockchain. Because there may be many digital contracts offered as virtual services, the contract identifier uniquely identifies a particular digital contract offered by a virtual machine, vendor or supplier. The blockchain is thus not burdened with the programming code that is required to execute the digital contract. The blockchain need only include or specify the contract identifier (and perhaps one or more contractual parameters), thus greatly simplifying the blockchain and reducing its size (in bytes) and processing requirements.

IPC Classes  ?

  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 20/12 - Payment architectures specially adapted for electronic shopping systems
  • H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
  • G06F 21/53 - Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity, buffer overflow or preventing unwanted data erasure by executing in a restricted environment, e.g. sandbox or secure virtual machine
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
  • H04L 67/10 - Protocols in which an application is distributed across nodes in the network

58.

Decisional architectures in blockchain environments

      
Application Number 16116976
Grant Number 11348098
Status In Force
Filing Date 2018-08-30
First Publication Date 2020-02-06
Grant Date 2022-05-31
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a table identifier in a blockchain. Because there may be many digital contracts offered as virtual services, the table identifier uniquely identifies a particular decision table and/or the digital contract offered by a virtual machine, vendor or supplier. The blockchain is thus not burdened with the programming code that is required to execute the decision table and/or the digital contract. The blockchain need only include or specify the table identifier (and perhaps one or more contractual parameters), thus greatly simplifying the blockchain and reducing its size (in bytes) and processing requirements.

IPC Classes  ?

  • G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06Q 20/12 - Payment architectures specially adapted for electronic shopping systems
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • A41D 31/06 - Thermally protective, e.g. insulating
  • D03D 15/47 - Woven fabrics characterised by the material, structure or properties of the fibres, filaments, yarns, threads or other warp or weft elements used characterised by the structure of the yarns or threads multicomponent, e.g. blended yarns or threads
  • D03D 15/56 - Woven fabrics characterised by the material, structure or properties of the fibres, filaments, yarns, threads or other warp or weft elements used characterised by the properties of the yarns or threads elastic
  • D03D 15/567 - Shapes or effects upon shrinkage
  • A41D 1/00 - Garments
  • A41D 11/00 - Garments for children
  • A41D 13/005 - Professional, industrial or sporting protective garments, e.g. surgeons' gowns or garments protecting against blows or punches with controlled internal environment with controlled temperature
  • A41D 15/00 - Convertible garments
  • A41D 31/00 - Materials specially adapted for outerwear
  • D02G 3/36 - Cored or coated yarns or threads
  • D02G 3/44 - Yarns or threads characterised by the purpose for which they are designed
  • D03D 1/00 - Woven fabrics designed to make specified articles
  • G05B 15/02 - Systems controlled by a computer electric
  • H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
  • G06F 16/29 - Geographical information databases
  • G06F 21/53 - Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity, buffer overflow or preventing unwanted data erasure by executing in a restricted environment, e.g. sandbox or secure virtual machine
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
  • A41D 3/00 - Overgarments
  • G06F 1/16 - Constructional details or arrangements

59.

Transactional sharding of blockchain transactions

      
Application Number 16116991
Grant Number 11989208
Status In Force
Filing Date 2018-08-30
First Publication Date 2020-02-06
Grant Date 2024-05-21
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • Douglass, Clay
  • Snow, Paul

Abstract

A complex cryptographic coinage transaction is transactionally sharded into multiple simple cryptographic coinage transactions. The complex cryptographic coinage transaction specifies cryptographic debits and/or deposits to/from multiple input accounts and/or multiple output accounts. The simple cryptographic coinage transactions, however, only specify a single one of the input accounts and/or a single one of the output accounts. A single server within a blockchain environment may thus process one of the simple cryptographic coinage transactions without requiring calls for data from other servers responsible for other accounts.

IPC Classes  ?

  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • G06F 16/182 - Distributed file systems
  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols

60.

Secret sharing via blockchains

      
Application Number 16548932
Grant Number 11296889
Status In Force
Filing Date 2019-08-23
First Publication Date 2019-12-26
Grant Date 2022-04-05
Owner Inveniam Capital Partners, Inc. (USA)
Inventor
  • Snow, Paul
  • Deery, Brian
  • Paolini-Subramanya, Mahesh

Abstract

Confidential, secret data may be shared via one or more blockchains. Mortgage applications, medical records, financial records, and other electronic documents often contain social security numbers, names, addresses, account information, and other personal data. A secret sharing algorithm is applied to any secret data to generate shares. The shares may then be integrated or written to one or more blockchains for distribution.

IPC Classes  ?

  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06F 21/60 - Protecting data
  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
  • H04L 9/08 - Key distribution
  • H04L 29/06 - Communication control; Communication processing characterised by a protocol

61.

Validating documents

      
Application Number 16548963
Grant Number 11044100
Status In Force
Filing Date 2019-08-23
First Publication Date 2019-12-26
Grant Date 2021-06-22
Owner INVENIAM CAPITAL PARTNERS, INC. (USA)
Inventor
  • Deery, Brian
  • Snow, Paul
  • Paolini-Subramanya, Mahesh

Abstract

Authentication of electronic document is based on multiple digital signatures incorporated into a blockchain. Structured data, metadata, and instructions may be hashed to generate the multiple digital signatures for distribution via the blockchain. Any peer receiving the blockchain may then verify an authenticity of an electronic document based on any one or more of the multiple digital signatures incorporated into the blockchain.

IPC Classes  ?

  • H04L 29/06 - Communication control; Communication processing characterised by a protocol
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system

62.

Load balancing in blockchain environments

      
Application Number 15983595
Grant Number 11134120
Status In Force
Filing Date 2018-05-18
First Publication Date 2019-11-21
Grant Date 2021-09-28
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

Hardware and software resources are load balanced when processing multiple blockchains. As more and more entities (whether public or private) are expected to generate their own blockchains for verification, a server or other resource in a blockchain environment may be over utilized. For example, as banks, websites, and retailers issue their own private cryptocoinage, the number of financial transactions may clog or hog networking and/or hardware resources. A blockchain load balancing mechanism thus allocates resources among the multiple blockchains.

IPC Classes  ?

  • G06F 15/173 - Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star or snowflake
  • H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06F 9/455 - EmulationInterpretationSoftware simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • G06F 16/18 - File system types

63.

Private blockchain services

      
Application Number 15983655
Grant Number 11170366
Status In Force
Filing Date 2018-05-18
First Publication Date 2019-11-21
Grant Date 2021-11-09
Owner Inveniam Capital Partners, Inc. (USA)
Inventor Snow, Paul

Abstract

A personal blockchain is generated as a cloud-based software service in a blockchain environment. The personal blockchain immutably archives usage of any device, perhaps as requested by a user. However, some of the usage may be authorized for public disclosure, while other usage may be designated as private and restricted from public disclosure. The public disclosure may permit public ledgering by still other blockchains, thus providing two-way public/private ledgering for improved record keeping. Private usage, though, may only be documented by the personal blockchain.

IPC Classes  ?

  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • G06Q 30/02 - MarketingPrice estimation or determinationFundraising
  • G06Q 20/32 - Payment architectures, schemes or protocols characterised by the use of specific devices using wireless devices
  • G06Q 20/34 - Payment architectures, schemes or protocols characterised by the use of specific devices using cards, e.g. integrated circuit [IC] cards or magnetic cards
  • G06Q 20/38 - Payment protocolsDetails thereof
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • G06F 16/907 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
  • G06F 16/18 - File system types

64.

Import and export in blockchain environments

      
Application Number 15983612
Grant Number 10783164
Status In Force
Filing Date 2018-05-18
First Publication Date 2019-11-21
Grant Date 2020-09-22
Owner INVENIAM CAPITAL PARTNERS, INC. (USA)
Inventor Snow, Paul

Abstract

Importation and exportation allows software services in blockchain environments. Blockchains may import data and export data, thus allowing blockchains to offer software services to clients (such as other blockchains). Individual users, businesses, and governments may create their own blockchains and subcontract or outsource operations to other blockchains. Moreover, the software services provided by blockchains may be publically ledgered by still other blockchains, thus providing two-way blockchain interactions and two-way ledgering for improved record keeping.

IPC Classes  ?

  • G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06F 9/455 - EmulationInterpretationSoftware simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
  • G06Q 20/06 - Private payment circuits, e.g. involving electronic currency used only among participants of a common payment scheme
  • G06Q 20/38 - Payment protocolsDetails thereof
  • G06F 16/18 - File system types

65.

Secret sharing via blockchain distribution

      
Application Number 16351606
Grant Number 10693652
Status In Force
Filing Date 2019-03-13
First Publication Date 2019-08-29
Grant Date 2020-06-23
Owner INVENIAM CAPITAL PARTNERS, INC. (USA)
Inventor
  • Nadeau, Jason
  • Deery, Brian
  • Snow, Paul
  • Paolini-Subramanya, Mahesh

Abstract

Data verification in federate learning is faster and simpler. As artificial intelligence grows in usage, data verification is needed to prove custody and/or control. Electronic data representing an original version of training data may be hashed to generate one or more digital signatures. The digital signatures may then be incorporated into one or more blockchains for historical documentation. Any auditor may then quickly verify and/or reproduce the training data using the digital signatures. For example, a current version of the training data may be hashed and compared to the digital signatures generated from the current version of the training data. If the digital signatures match, then the training data has not changed since its creation. However, if the digital signatures do not match, then the training data has changed since its creation. The auditor may thus flag the training data for additional investigation and scrutiny.

IPC Classes  ?

  • H04W 12/06 - Authentication
  • H04L 29/06 - Communication control; Communication processing characterised by a protocol
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06N 20/00 - Machine learning
  • H04L 9/08 - Key distribution
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems

66.

HARMONY INTEGRATE

      
Serial Number 88320480
Status Registered
Filing Date 2019-02-28
Registration Date 2020-10-27
Owner INVENIAM CAPITAL PARTNERS, INC. ()
NICE Classes  ?
  • 09 - Scientific and electric apparatus and instruments
  • 42 - Scientific, technological and industrial services, research and design

Goods & Services

Downloadable computer software using a consensus engine incorporating blockchain technology for securing data with cryptographic information including services and software instructions that can be incorporated into other software for data immutability, provenance and publication for workflow management, process transparency and trusted data exchanges Software-as-a-service featuring software using a consensus engine incorporating blockchain technology for securing data with cryptographic information including services and software instructions that can be incorporated into other software for data immutability, provenance and publication for workflow management, process transparency and trusted data exchanges

67.

HARMONY

      
Serial Number 88320468
Status Registered
Filing Date 2019-02-28
Registration Date 2020-03-10
Owner INVENIAM CAPITAL PARTNERS, INC. ()
NICE Classes  ? 42 - Scientific, technological and industrial services, research and design

Goods & Services

Software-as-a-service featuring software using a consensus engine incorporating blockchain technology for securing data with cryptographic information including services and software instructions that can be incorporated into other software

68.

HARMONY CONNECT

      
Serial Number 88320474
Status Registered
Filing Date 2019-02-28
Registration Date 2020-03-10
Owner INVENIAM CAPITAL PARTNERS, INC. ()
NICE Classes  ? 42 - Scientific, technological and industrial services, research and design

Goods & Services

Software-as-a-service featuring software using a consensus engine incorporating blockchain technology for securing data with cryptographic information including services and software instructions that can be incorporated into other software for data immutability, provenance and publication

69.

Data reproducibility using blockchains

      
Application Number 15499558
Grant Number 10270599
Status In Force
Filing Date 2017-04-27
First Publication Date 2018-11-01
Grant Date 2019-04-23
Owner INVENIAM CAPITAL PARTNERS, INC. (USA)
Inventor
  • Nadeau, Jason
  • Deery, Brian
  • Paolini-Subramanya, Mahesh
  • Snow, Paul

Abstract

Data verification in federate learning is faster and simpler. As artificial intelligence grows in usage, data verification is needed to prove custody and/or control. Electronic data representing an original version of training data may be hashed to generate one or more digital signatures. The digital signatures may then be incorporated into one or more blockchains for historical documentation. Any auditor may then quickly verify and/or reproduce the training data using the digital signatures. For example, a current version of the training data may be hashed and compared to the digital signatures generated from the current version of the training data. If the digital signatures match, then the training data has not changed since its creation. However, if the digital signatures do not match, then the training data has changed since its creation. The auditor may thus flag the training data for additional investigation and scrutiny.

IPC Classes  ?

  • H04W 12/06 - Authentication
  • H04L 29/06 - Communication control; Communication processing characterised by a protocol
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06N 20/00 - Machine learning

70.

Due diligence in electronic documents

      
Application Number 15475199
Grant Number 10685399
Status In Force
Filing Date 2017-03-31
First Publication Date 2018-10-04
Grant Date 2020-06-16
Owner INVENIAM CAPITAL PARTNERS, INC. (USA)
Inventor
  • Snow, Paul
  • Deery, Brian
  • Nadeau, Jason
  • Paolini-Subramanya, Mahesh

Abstract

Due diligence of mortgage documents is faster and simpler. An electronic mortgage application often contains or references a collection of many separate electronic mortgage documents. Electronic data representing an original version of an electronic mortgage document and its current version may be hashed to generate digital signatures. Any auditor may then quickly conduct the due diligence by comparing the digital signatures. If the digital signatures match, then the due diligence reveals that the electronic mortgage document has not changed since its creation. However, if the digital signatures do not match, then the electronic mortgage document has changed since its creation. The auditor may thus flag the electronic mortgage document for additional due diligence. Regardless, a result of the due diligence may be incorporated into one or more blockchains.

IPC Classes  ?

  • G06Q 40/02 - Banking, e.g. interest calculation or account maintenance
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system

71.

Auditing of electronic documents

      
Application Number 15465702
Grant Number 10817873
Status In Force
Filing Date 2017-03-22
First Publication Date 2018-09-27
Grant Date 2020-10-27
Owner INVENIAM CAPITAL PARTNERS, INC. (USA)
Inventor
  • Paolini-Subramanya, Mahesh
  • Deery, Brain
  • Nadeau, Jason
  • Snow, Paul

Abstract

Auditing of mortgage documents is faster and simpler. An electronic mortgage application often contains or references a collection of many separate electronic mortgage documents. Electronic data representing an original version of an electronic mortgage document and its current version may be hashed to generate digital signatures. Any auditor may then quickly compare the digital signatures. If the digital signatures match, then the audit reveals that the electronic mortgage document has not changed since its creation. However, if the digital signatures do not match, then the electronic mortgage document has changed since its creation. The auditor may thus flag the electronic mortgage document for additional auditing processes.

IPC Classes  ?

72.

Secret sharing via blockchains

      
Application Number 15435612
Grant Number 10411897
Status In Force
Filing Date 2017-02-17
First Publication Date 2018-08-23
Grant Date 2019-09-10
Owner INVENIAM CAPITAL PARTNERS, INC. (USA)
Inventor
  • Paolini-Subramanya, Mahesh
  • Deery, Brian
  • Snow, Paul

Abstract

Confidential, secret data may be shared via one or more blockchains. Mortgage applications, medical records, financial records, and other electronic documents often contain social security numbers, names, addresses, account information, and other personal data. A secret sharing algorithm is applied to any secret data to generate shares. The shares may then be integrated or written to one or more blockchains for distribution.

IPC Classes  ?

  • G06F 21/60 - Protecting data
  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
  • H04L 9/06 - Arrangements for secret or secure communicationsNetwork security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
  • G06F 21/64 - Protecting data integrity, e.g. using checksums, certificates or signatures
  • H04L 9/08 - Key distribution
  • H04L 29/06 - Communication control; Communication processing characterised by a protocol

73.

Validating documents via blockchain

      
Application Number 15419033
Grant Number 10419225
Status In Force
Filing Date 2017-01-30
First Publication Date 2018-08-02
Grant Date 2019-09-17
Owner INVENIAM CAPITAL PARTNERS, INC. (USA)
Inventor
  • Deery, Brian
  • Snow, Paul
  • Paolini-Subramanya, Mahesh

Abstract

Authentication of electronic document is based on multiple digital signatures incorporated into a blockchain. Structured data, metadata, and instructions may be hashed to generate the multiple digital signatures for distribution via the blockchain. Any peer receiving the blockchain may then verify an authenticity of an electronic document based on any one or more of the multiple digital signatures incorporated into the blockchain.

IPC Classes  ?

  • H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
  • H04L 29/06 - Communication control; Communication processing characterised by a protocol

74.

SMARTPROVENANCE

      
Serial Number 87936447
Status Registered
Filing Date 2018-05-25
Registration Date 2019-05-28
Owner INVENIAM CAPITAL PARTNERS, INC. ()
NICE Classes  ? 09 - Scientific and electric apparatus and instruments

Goods & Services

Component feature of downloadable computer software using a consensus engine incorporating blockchain technology for tracking and securing data related to provenance with cryptographic information, namely, blockchain record or records that trace an item or entity by its identity from its origin by tracking the sequences of its formal ownership, custody, and places of storage or handling, and interactions with other identities, people or computers, along with the integrity of the item through the means of a blockchain