Decentralized Storage (IPFS/Arweave)

All critical asset information and documents are stored in a decentralized manner. Liquid uploads asset metadata, legal documents, proof of ownership files, and more to IPFS or Arweave, rather than relying on a centralized server.

The resulting content address (IPFS CID or Arweave TX hash) is linked to the token’s on-chain metadata. This ensures that anyone holding the token can independently access the underlying asset information and legal terms, and that this data remains tamper-proof and persistent.

In practice, when a token is minted, Liquid’s backend:

• Uploads the asset’s info JSON and any associated documents (PDFs, appraisals, legal structures) to IPFS.

• Obtains the IPFS content hashes.

• Writes these hashes into the token’s metadata (often using Solana’s Metadata program or embedded in the smart contract state).

This architecture guarantees transparency, immutability, and trustlessness for asset data, perfectly aligning with blockchain’s core principles.