Filecoin Pin CLI

How to use the Filecoin Pin CLI to store and retrieve IPFS data on Filecoin

⚠️ SECURITY WARNING: This tutorial uses throwaway private keys for demo purposes. NEVER commit private keys to repositories or expose them publicly. Use environment variables and GitHub secrets for production.

Overview

Filecoin Pin CLI is a command-line tool that allows you to store IPFS data on the Filecoin network with cryptographic proofs of storage. This guide walks you through the complete setup and usage process.

Setup Payments

Configure permissions for automatic payment handling:

Upload Data

Upload your file with automatic funding:

Retrieve over an IPFS Gateway

Retrieve your data using the IPFS gateway:

Prove Storage

Verify your data is stored with cryptographic proofs:

Who is this for

  1. Existing IPFS developers who want to use Filecoin to persist their data

  2. Agent builders that want to store their agent cards and validation materials on Filecoin for cryptographic proof of storage

Getting started

NOTE! For demo purposes, this example uses a THROWAWAY PRIVATE KEY. NEVER USE YOUR PRIVATE KEY IN A REPOSITORY OR EXPOSE IT. The repo references using your private key LOCALLY as an ENV VARIABLE. When you create a GITHUB ACTION, use GITHUB SECRETS to store your private key.

Prerequisites

Install Required Tools

Verify Installation


1. Wallet Setup

Note: The filecoin-pin CLI expects a PRIVATE_KEY for your Filecoin wallet to pay for storage service and transaction fees of using Filecoin warm storage service.

So the first step is to acquire some test FIL and USDFC on the Filecoin calibration testnet into your ETH-compatible wallet.

Generate a New Wallet

If you do not have an ETH-compatible Filecoin wallet, you can generate one using Foundry:

Save the private key and wallet address.

Get Testnet tokens


2. Create Environment File

This PRIVATE_KEY is for testing purposes only. Please NEVER USE YOUR PRIVATE KEY IN A REPOSITORY OR EXPOSE IT.

Save your credentials locally for easy reuse:


3. Using the Filecoin Pin CLI

Setup Payments

All commands in this section use the environment variables set in Create Environment File. If you're starting a new terminal session, reload them:

Note: These commands work directly without running a server/daemon. The PRIVATE_KEY environment variable must be set.

Configure payment approvals (permissions only - deposits handled automatically with --auto-fund):

What --auto does: Configures WarmStorage contract permissions automatically. No deposit required at this step - use --auto-fund when uploading to handle deposits automatically.

Upload Data

Use the --auto-fund flag to automatically handle payment deposits (v0.7.0+).

Upload a file:

Key values explained:

  • Root CID: bafybeibh422kjvgfmymx6nr7jandwngrown6ywomk4vplayl4de2x553t4 - IPFS CID for your data, which you can access from IPFS gateways, such as ipfs.io.

  • Piece CID: bafkzcibcfab4grpgq6e6rva4kfuxfcvibdzx3kn2jdw6q3zqgwt5cou7j6k4wfq - Filecoin piece commitment (cryptographic proof)

  • Piece ID: 0 - Reference within the data set

  • Data Set ID: 325 - On-chain data set containing your upload

  • Transaction: 0xc85e49d2ed745cc8c5d7115e7c45a1243ec25da7e73e224a744887783afea42b - Blockchain confirmation hash

  • Direct Download URL: Direct link to retrieve your data from the storage provider

Your file is now stored on Filecoin with ongoing proof of possession!

  1. Your file will be accessible via IPFS gateways, such as https://ipfs.io/ipfs/<ROOT-CID>

  2. It is also available to download from the Filecoin service provider using the Direct Download URL.

Upload Directory

You can also upload a directory - it will package multiple files into a single CAR:

Key details:

  • Root CID: bafybeig27btater5fpt3l67gbme3sebqk3ynwdhlbrbuk3q7espiyplan4 - IPFS CID for the directory structure

  • Size: 433.0 B - Includes all files plus directory metadata

  • Piece ID: 1 - Second piece in the same Data Set ID 325

  • Data Set ID: 325 - Same data set as the single file upload (multiple pieces grouped together)

💡 Note: Multiple uploads to the same payment configuration are grouped into the same Data Set, with each upload assigned a unique Piece ID.

Prove Storage

Filecoin-pin CLI also provide commands to check the proof of your storage in data set. First, you can list the dataset associate to your wallet.

Then you can get detailed information about your data set (this queries the blockchain directly) that includes proofs:

Expected Output:

Key information:

Data Set Status:

  • live - Data set is active with ongoing PDP proofs

  • Pieces stored: 2 - Our demo.txt (#0) and my-data/ directory (#1)

  • Leaf count: 21 - Total Merkle tree leaves across all pieces

  • Total size: 672.0 B - Combined size of both pieces

Payment Rails:

  • PDP rail ID: 631 - Active payment rail for storage proofs

  • Payer/Payee - Payment flows from your wallet to the provider

  • Commission: 0.00% - No commission on this testnet provider

Provider Details:

  • Service URL: Direct access to download pieces

  • Storage price: < 0.0001 USDFC/TiB/month

  • Min proving period: 30 epochs - Proofs submitted every 15 minutes

Pieces:

  • Each piece shows its CommP (Filecoin piece CID) and Root CID (IPFS content ID)

  • Piece #0 = demo.txt (our single file upload)

  • Piece #1 = my-data/ (our directory upload)

💡 Note: This command queries the smart contracts on-chain to retrieve all data set information. The data shown is live blockchain state, not cached data.

Documentation

Repositories

Last updated

Was this helpful?