The text below can be translated into any language using the Google Translate button directly above.
This algorithm was initially created to enable smart contracts with the bitcoin blockchain. The concept was to allow any media or program to be stored in any electronic storage medium that can be verified by the bitcoin blockchain and or executed without bloating the blockchain. At the time of development the only available storage for bitcoin was the OP_RETURN with a 40 byte limit. (There were 80 bytes available but there was serious discussion to limit the OP_RETURN TO 40 bytes to prevent bloat.)
The first project was to encrypt the Bible on the blockchain in a way that no one could modify even a single character. Because of the limited space in the OP_RETURN, it was not practical to create thousands of transactions and chain them together one output into another input to create the Bible.
The HlyGrail algorithm uses a new unused receive ADDRESS that is either watermarked into an image or included in metadata of other media, and / or included in an Intellectual Property File (IPF). The IPF can contain reference to multiple media and include their SHA256 hash (or other hash). The media or IPF is either plain or AES-256 (or another encryption) encrypted. The final file or IPF is then SHA256 hashed (or another hash algorithm). The Hash / CID is then stored in a new blockchain transaction using the new ADDRESS as the receiving address with the Hash or CID placed in the OP_RETURN or other permanent register of the blockchain transaction. (If you do not include the ADDRESS in an image or protected document as currently done with NFTs, anyone can steal it.)
The HlyGrail license covers ANY blockchain that uses this or similar algorithm by using a unique ADDRESS or other unique part of a transaction that is known before the transaction which is embedded in the data (image/media, program etc.), and storing a Hash of the data in a permanent register (OP_RETURN) of the transaction. The hash identifies a unique data object and even with collisions would be easy to determine which file was intended. The intention is to use the ADDRESS from a transaction to tie off-chain media plain or encrypted back to a blockchain transaction for verification of ownership and authenticity while keeping the media usable off the blockchain.
Copyright 2023: Genus Enterprises LLLP All Rights Reserved.