fxhash docs
discordonchfsfxhash$FXH
  • Docs Overview
  • Quickstart Guide
  • $FXH
    • Protocol overview
    • Programming open-form genart
  • Creating on fxhash
    • Project Setup & Development
      • Project Structure
      • Project Template
      • CLI Setup
      • CLI Reference
      • fxlens
    • fxhash API
      • API Overview
      • API Reference
      • fxparams module
      • fxparams API Reference
      • Parameter Definition Specs
    • Genart in the Browser
      • Canvas element & API
      • Including Libraries
      • Responsive Browser Projects
      • Deterministic Randomness
      • User Input & Media Exports
      • Testing Browser Compatibility
    • Releasing your Project
      • Minting Interface Walkthrough
      • Pricing and Supply
      • Reserves & Allow Lists
      • Licensing your Project
      • Collaborative Projects
      • Withdrawing Earnings on ETH/Base via splits
  • Collecting on fxhash
    • Platform Overview
      • Primary Market
      • Secondary Market
      • fx(params) & the Ticketing System
      • Allow Lists & Reserves
      • Redeemables
    • Collector Tips
      • Getting Started as a Collector
      • Token Discovery Tools
      • Towards Curation
      • Market Analysis & Dynamics
  • Knowledge Base
    • fxhash & Web3
      • Decentralization & Blockchain Tech
      • Multi-Chain Integration
      • NFTs & Smart Contracts
      • Web3 Storage
        • IPFS
        • ONCHFS
      • What is Generative Art?
      • Genart on the Blockchain
    • Onboarding
      • Creating a Wallet
      • Creating an Account
      • Adding Funds to Your Wallet
      • Account Verification
      • Platform Moderation
    • Policies & Guidelines
      • Code of Conduct
        • Artists' Code of Conduct
        • Collector's Code of Conduct
      • Terms and Conditions
      • Privacy Policy
      • Safety Notes
  • ONCHFS
    • What is ONCHFS?
    • Motivations
    • System Overview
    • Cross-chain Referencing
    • Limitations
    • References
  • Find us on Social Media
    • X (Twitter)
    • Farcaster
    • Join the Discord
Powered by GitBook
On this page
  • Content Availability
  • Ecosystem integration

Was this helpful?

  1. ONCHFS

Limitations

PreviousCross-chain ReferencingNextReferences

Last updated 7 months ago

Was this helpful?

Content Availability

In contrast to other on-chain on-demand storage solutions, onchfs requires an http proxy to display the content of a resource, as it cannot reliably serve files directly from on-chain read calls. In essence, we consider this limitation to be fairly acceptable as this in-between http-proxy layer is very straightforward and can easily be ran by anyone with an internet connection, without even having to rely on a 3rd party service.

Read more

More infos about the .

Ecosystem integration

While ipfs is fairly supported on most platforms nowadays, onchfs is not. As such, platforms will not be capable of reliably displaying onchfs absolute URIs found on-chain due to the infancy of the protocol.

However, some solutions exist to get around this temporary problem. Smart Contract can store updateable base URIs to onchfs assets, initially configured to a valid http proxy, later updated to the onchfs:// schema string:

onchfsCid = 3d767a081f6d...
baseUri = https://onchfs.proxy.com/
tokenUri = {baseUri}{onchfsCid}

at first ->
baseUri = https://onchfs.proxy.com/3d767a081f6d...

then when onchfs gets adopted ->
baseUri = onchfs://
tokenUri = onchfs://3d767a081f6d...
onchfs http proxy here