Inveniam Capital Partners, Inc.

Factom, Inc.

Other

Sourcepulse LLC

Paul Snow

Brian Deery

Mahesh Paolini-Subramanya

Jason Nadeau

Gavin Gillas

Ying W Chan

Clay S Douglass

Brain Deery

Clay Douglass

Bhushan Naniwadekar

Benjamin D Newman

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.

Validating authenticity of electronic documents shared via computer networks

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.

RAM hashing in blockchain environments

Separating hashing from proof-of-work in blockchain environments

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.

Artificial intelligence modifying federated learning models

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.

Systems and methods for processing blockchain transactions

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.

Recordation of device usage to blockchains

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.

Import and export in blockchain environments

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).

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.

Transactional sharding of blockchain transactions

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.

Load balancing in blockchain environments

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.

Decisional architectures in blockchain environments

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.

Growing community of inventors

Austin, TX, United States of America

Paul Snow