The text below can be translated into any language using the Google Translate button directly above.
This document covers Standards that will be implemented with HlyGrail. Because the applications and usage are infinite with unlimited format options and program code, no basic standard can be presented.
Keep in mind the purpose of the HlyGrail Algorithm – Protect Intellectual Property Files (IPF) by identifying the IPF with a bitcoin address and an OP_RETURN by storing the address in the IPF and the hash of the IPF containing the address in the OP_RETURN without bloating the blockchain.
To work correctly, access to the media is required. Due to security, some media is private and must be held by the owners. In other cases, such as an NFT the media needs to be public, but you still want to protect the copyright. The HlyGrail IPF is a Content ID because we use the hash of the file to identify the IPF. The IPF can be stored anyplace, and the Hash is the ID. It is easy to store your IPFs in a directory using the hash as the name to easily identify the file. To identify the file uses the HlyGrail algorithm, “HlyGrail” in hex was added to the front of the hash. We recommend you put HlyGrail in the front of every IPF hash so that systems will recognize them and try to decode them correctly.
There are many public storage options that use Content IDs (hashes) like the IPFS (Inter Planetary File System). They are now developing standards by adding code to the front of the hash, such as encrypted, file type, etc. which makes it easier for people to identify what is held by the hash. They are good storage options, but standards are hard once again. If you use our Standard file format you can put your IPF on IPFS for a content ID then use our DomainName / ID format to store the IPFS CID in the OP_RETURN.
There are many file usages with HlyGrail especially since 2015. Many are just a document (IPF) with the address inside, then hashed and stored in the OP_RETURN. Some encrypt the file first for secure storage then hash. The address is used to encrypt and decrypt the IPF.
To standardize we suggested creating the IPF separate from the document so you could store multiple media of any type with one OP_RETURN. Each media is independently plain or encrypted with the address, then stored along with the title, description, and hash in the IPF with no format other than adding contact and owner information.
We went to a JSON format for standard Patents to make them easier to create and read with unlimited documents. This is our IPF Patent format.
Finally, because of many storage system formats, unlimited types of HlyGrail applications, NFTs, and licensing we recommended the IPF contain three specific and two optional keypairs:
"HlyGrail”: “TYPE” This identifies IPF, Domain, Colored, NFT, unlimited.
"addressIPF”: “ADDRESS” This is your IPF Address.
"license”: “https://hlygrail.com” This eliminates the full license required.
“addressDomain”: “Colored Address” Holds your ID or Domain Address
"domainName”: “Colored Coin” This is Domain Name, ID, CID etc
Many Colored Coins exist but without ID or copyright protection. It would be easy as example to create a Domain Name IPF and include the link to your NFT file location in “domainName” such as a CID on IPFS instead of a Domain Name, then create the IPF file to protect the address and NFT.
For new NFTs we recommend using HlyGrail IPF by watermarking in the image your IPF address or embedding your IPF address in the metadata of other media. Then create an attribute IPF that includes your NFT address.
WARNING: Do not IPF someone else’s intellectual property because it will be easy to prove you stole it.
Check some standard formats and do not hesitate to recommend other standards.
Copyright 2023: Genus Enterprises LLLP All Rights Reserved.