Tezos have made changes to the chains which gives developers a easy method to integrate with IPFS.The protocol is called TZIP-16(a standard for accessing contract metadata in JSON format in on-chain storage or off-chain using IPFS or HTTP(S).)
The goal of TZIP-16 is to provide a standardized location and shape of contract metadata, easing the integration, discoverability and querying of Tezos smart contracts for applications, explorers, and wallets. It enables developers to focus more on product development and less on questions of how to integrate with wallets and external parties (e.g. wallets).
Standardizing Contract Metadata
Many smart contracts need to define metadata that is not included in the contract script, whether corresponding to the contract code itself (e.g. to reason about the contract’s behavior, interface, storage, etc.) or how it relates to off-chain data (e.g. a token representing artwork).
TZIP-16 proposes a method of finding specific metadata about the contract: provenance information (authorship), references to other implementation standards, off-chain views (Michelson functions or REST API calls to query the contract), and enables developers to create their own custom extensions (e.g. a multimedia metadata extension).
This metadata is described using a JSON format and a URI scheme is used to locate the metadata, whether on-chain (as in contract storage) data or off-chain (as in web-services or IPFS).
By adopting this standard, smart contract authors and wallet/indexer implementers can agree on both the location and contents of a contract’s metadata.
Read more in details HERE
