Abstract: The present invention provides for employing SQL to introduce blockchain technologies into a relational database, and thereby leverage the inherent tamper-resistant properties of blockchain, without the need to completely rewrite existing or legacy relational database software. The invention creates a relational database inside of a blockchain and uses a conventional SQL interface for standard database operations. This reduces the burden of introducing blockchain technologies, while providing the benefits of the intrinsic security and verification features of blockchain technology. The invention provides a rich historical record of every transaction thereby greatly reducing, if not eliminating, the relational database's susceptibility to tampering. This allows for temporal queries on arbitrary records within the database and the generation of reports and audits for any point in the history of the database.

Abstract: Methods and systems for implementing an object identification system equipped to reduce the number of service calls for remote object identification lookups are disclosed. The object identification management server works to reduce the number of object identification requests, which overall improves the process of quickly and accurately providing object identifications when needed and without unnecessarily wasting computing resources. The object identification server can subsequently manage the number of identification requests by setting a tunable threshold, which allows a system to operate more efficiently and allocate computing resources accordingly.

Abstract: Methods and systems for implementing an object identification system equipped to reduce the number of service calls for remote object identification lookups are disclosed. The object identification management server works to reduce the number of object identification requests, which overall improves the process of quickly and accurately providing object identifications when needed and without unnecessarily wasting computing resources. The object identification server can subsequently manage the number of identification requests by setting a tunable threshold, which allows a system to operate more efficiently and allocate computing resources accordingly.

Abstract: The present invention provides for employing SQL to introduce blockchain technologies into a relational database, and thereby leverage the inherent tamper-resistant properties of blockchain, without the need to completely rewrite existing or legacy relational database software. The invention creates a relational database inside of a blockchain and uses a conventional SQL interface for standard database operations. This reduces the burden of introducing blockchain technologies, while providing the benefits of the intrinsic security and verification features of blockchain technology. The invention provides a rich historical record of every transaction thereby greatly reducing, if not eliminating, the relational database's susceptibility to tampering. This allows for temporal queries on arbitrary records within the database and the generation of reports and audits for any point in the history of the database.

Abstract: The present invention provides for employing SQL to introduce blockchain technologies into a relational database, and thereby leverage the inherent tamper-resistant properties of blockchain, without the need to completely rewrite existing or legacy relational database software. The invention creates a relational database inside of a blockchain and uses a conventional SQL interface for standard database operations. This reduces the burden of introducing blockchain technologies, while providing the benefits of the intrinsic security and verification features of blockchain technology. The invention provides a rich historical record of every transaction thereby greatly reducing, if not eliminating, the relational database's susceptibility to tampering. This allows for temporal queries on arbitrary records within the database and the generation of reports and audits for any point in the history of the database.