2 Comments
User's avatar
Chris Coleman's avatar

Great exploration and explanation. I have been digging into how to pin my full collection and there are no great solutions…

Sean Moss-Pultz's avatar

Thanks for reading Chris. I think what you want is pretty close to being easy now with coding models. Paste this into Claude Code or any agent with shell access:

I collect art from Feral File and want to keep my own IPFS copies of

everything I own. Feral File publishes their full audit data openly at

status.feralfile.com. Please:

1. Ask me for my wallet addresses (Ethereum and/or Tezos).

2. Read https://status.feralfile.com/status.md and download the census

CSV linked under "Data" (a .csv.gz, ~25 MB). Each row is one file of

one work: columns include chain ("eth"/"tezos"), contract, token_id,

resource, and cid (empty when the file is not on IPFS).

3. Enumerate what I own — no API keys needed:

- Ethereum: https://eth.blockscout.com/api/v2/addresses/<wallet>/nft?type=ERC-721

(follow next_page_params to paginate)

- Tezos: https://api.tzkt.io/v1/tokens/balances?account=<wallet>&balance.gt=0

(select token.contract and token.tokenId)

4. Match my holdings against the census on chain + contract

(case-insensitive) + token_id, and collect every cid for the works

I own.

5. Check that the ipfs CLI (Kubo) is installed and the daemon is

running; help me install it if not. Then ipfs pin add each unique

CID, showing progress, and verify afterwards with ipfs pin ls.

6. Give me a summary: works pinned and total files; works I own whose

files have no CIDs yet (their media is still on Feral File's CDN —

nothing to pin until Feral File publishes addresses, which

status.feralfile.com tracks); and any pins that failed.

Be gentle with the APIs (small pages, brief pauses). Everything here is

read-only except the IPFS pinning on my own machine.