# Overview of Filehub · Chromia Docs (concept)

> Filehub is a scalable, reliable, and secure storage platform that Chromia's relational blockchain powers.

Source: https://docs.chromia.com/ecosystem/filehub/overview/

# Overview of Filehub

On this page

* [Cost](#cost)
* [File access](#file-access)
* [Getting started with Filehub](#getting-started-with-filehub)
* [Components](#components)
* [Filehub](#filehub)
* [Filechain](#filechain)
* [ICCF and anchoring chain](#iccf-and-anchoring-chain)

Filehub is a scalable, reliable, and secure storage platform that Chromia's relational blockchain powers. It provides
developers with a decentralized solution for storing and accessing files, ensuring data integrity and availability even
when faced with external disruptions.

## Cost

Filehub operates on a fixed payment model for storage. The current price is $0.10 per MB for perpetual storage. Your
files will remain accessible for a minimum of 30 years. Access continues indefinitely with no renewal fees, as long as
the network remains operational.

## File access

Everyone can access all files stored in Filehub free of charge. If you want to store private files, you must encrypt
them before upload.

## Getting started with Filehub

To use Filehub, you need to provide it with CHR from the Economy Chain. A minimum deposit of 1 CHR is required to create
an account.

* If your CHR is currently on an EVM chain, you can create an Economy Chain account and bridge it over using the
  [Vault Transfer](https://vault.chromia.com/en/transfer/) feature.
* Once your CHR is on the Economy Chain, you can create an account and transfer your CHR to the Filehub Chain using the
  [Vault UI for Filehub](https://vault.chromia.com/en/dapps/dapp/?dapp=17-Filehub).
* Finally, navigate to the [Filehub UI](https://filehub.chromia.com/) and start uploading your files.

You can also access the [Filehub UI on Testnet](https://filehub.testnet.chromia.com), which behaves the same as the
Mainnet version but uses Testnet CHR. You can request Testnet CHR from the
[Chromia Faucet](https://faucet.testnet.chromia.com). Files uploaded to Testnet are not guaranteed to be stored
permanently.

## Components

Filehub consists of two fundamental components:

* **Filehub blockchain**: This acts as the central index, tracking files and managing references to data chunks
  distributed across multiple Filechains.
* **Filechain blockchain(s)**: These function as the actual blob storage, responsible for persisting file data

### Filehub

The Filehub blockchain serves as the central indexing system, responsible for:

* Managing the administration and availability of Filechains.
* Selecting the appropriate Filechains for distributing and storing each file chunk.
* Maintaining a comprehensive index of file chunks and their corresponding Filechain locations.
* Handling the billing system for file storage, ensuring proper payment for services.

Filehub’s architecture is modular and scalable. It starts with a single Filehub and two Filechains, with the flexibility
to expand incrementally by adding more Filechains as storage requirements grow. This design supports unlimited
horizontal scaling, increasing both storage capacity and file distribution efficiency.

### Filechain

The Filechain Blockchain(s) function as blob storage, handling the following tasks:

* Storing file chunks in a secure and decentralized manner.
* Validating payments made to Filehub using
  [ICCF (Interchain Confirmation Facility)](https://docs.chromia.com/get-started/use-cases/cross-chain/iccf/)-proofs.
* Hashing incoming data and verifying it against expected hashes to ensure data integrity.
* Accepting transactions and persisting file chunks on the Filechain blockchain.

Filechain serves strictly as a blob storage solution. It operates without knowledge of file metadata or the
relationships between chunks. Its sole responsibility is to store data chunks and validate their integrity.

## ICCF and anchoring chain

The [ICCF (Interchain Confirmation Facility)](https://docs.chromia.com/get-started/use-cases/cross-chain/iccf/) facilitates communication between
Filehub and Filechains. This framework ensures that file chunks are only stored on Filechains after payment has been
confirmed.

Here's how the process works:

1. **Payment and allocation**: When a user uploads a file to Filehub, the platform allocates storage on a suitable
   Filechain and processes the payment.
2. **ICCF proof generation**: Filehub generates an ICCF proof, which is a cryptographic signature verifying that the
   file has been allocated and paid for.
3. **Proof submission**: The ICCF proof is submitted to the target Filechain.
4. **Proof verification**: The Filechain independently verifies the ICCF proof to confirm that the payment for the
   corresponding file chunk has been completed.

This indirect communication mechanism, facilitated by the ICCF and the anchoring chain, ensures the security and
integrity of the file storage process. By verifying payments before storing file chunks, Filehub prevents unauthorized
access and ensures that users only pay for the storage they use.

[View this page on docs.chromia.com](https://docs.chromia.com/ecosystem/filehub/overview/)Content mirrored from the live docs
