Epic: Filecoin Pin Server

[jennijuju]

Context: https://www.notion.so/filecoindev/filecoin-pin-daemon-25bdc41950c18088bd4cdafbdc2e2a9a

TODO: create tasks for the related work

[BigLep]

In 202604, https://github.com/wjmelements/pinmfs-pdp-demo used the filecoin pin server affordance.

[SgtPooki]

2026-06-17

A public summary of what this epic covers, drawn from the internal daemon design doc, so it is not just a link:

The filecoin-pinning-server is a long-running daemon implementing the IPFS Pinning Service API, so an IPFS client (Kubo, IPFS Desktop) configured with ipfs pin remote service add stores pinned content to Filecoin via the Synapse SDK. The roadmap is three milestones:

• M1 (stored private key): terminal install/run, guided first-run setup (wallet key, USDFC check, WarmStorage authorization), serving the Pinning Service API for Kubo/IPFS Desktop. The core of this is shipped (the server command, pinning API, token auth) and already in use (wjmelements/pinmfs-pdp-demo). M1 polish left to confirm: the guided first-run setup and systemd/launchd run-on-boot templates.
• M2 (deal-management UI): a localhost web UI for viewing server state/config. This overlaps the management console work in Epic: Filecoin Pin Web Management Console #74 / Management console: deal management #58 (currently deprioritized), so M2 should be reconciled with that rather than built twice.
• M3 (Metamask support): browser wallet signing instead of a stored key, which needs Kubo signing-interruption support.

Next step is breaking the remaining M1 polish and the M2/M3 scope into concrete issues, and resolving the M2-vs-#74 overlap. Marking needs-triage until that breakdown exists.

[BigLep]

Triage comment from 2026 FOC Board Triage (Post GA): No real demand for this yet, wait on customer requests?