You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+22-6Lines changed: 22 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,18 @@ An IPFS Pinning Service API implementation that pins to Filecoin's PDP service,
6
6
7
7
Filecoin Pin is a TypeScript daemon that implements the [IPFS Pinning Service API](https://ipfs.github.io/pinning-services-api-spec/) to enable users to pin IPFS content to Filecoin using familiar IPFS tooling like Kubo's `ipfs pin remote` commands.
8
8
9
+
### How It Works
10
+
11
+
1.**Serve Pin Service**: The daemon runs an HTTP server that implements the IPFS Pinning Service API
12
+
2.**Receive Pin Requests**: When you run `ipfs pin remote add`, Kubo sends a pin request to the service
13
+
3.**Fetch Blocks from IPFS**: The service connects to the IPFS network and fetches blocks for the requested CID (usually from the requesting node itself)
14
+
4.**Store in CAR**: As blocks arrive, they're written directly to a CAR (Content Addressable aRchive) file on disk
15
+
5.**Upload to PDP Provider**: Once all blocks are collected, the CAR file is uploaded to a Proof of Data Possession (PDP) service provider
16
+
6.**Commit to Filecoin**: The PDP provider commits the data to the Filecoin blockchain
17
+
7.**Start Proving**: The storage provider begins generating ongoing proofs that they still possess your data
18
+
19
+
This bridges the gap between IPFS's content-addressed storage and Filecoin's incentivized persistence layer, giving you the best of both worlds - easy pinning with long-term storage guarantees.
20
+
9
21
**⚠️ Alpha Software**: This is currently alpha software, only deploying on Filecoin's Calibration Test network with storage providers participating in network testing, not dedicating long-term persistence.
10
22
11
23
You need a Filecoin calibration network wallet funded with USDFC. See the [USDFC documentation](https://docs.secured.finance/usdfc-stablecoin/getting-started) which has a "Testnet Resources" section for getting USDFC on calibnet.
@@ -48,8 +60,8 @@ Configuration is managed through environment variables. The service uses platfor
48
60
#### Environment Variables
49
61
50
62
```bash
51
-
#Required for Filecoin operations
52
-
export PRIVATE_KEY="your-filecoin-private-key"# Ethereum private key (must be funded with USDFC)
63
+
#REQUIRED - Without this, the service will not start
64
+
export PRIVATE_KEY="your-filecoin-private-key"# Ethereum private key (must be funded with USDFC on calibration network)
53
65
54
66
# Optional configuration with defaults
55
67
export PORT=3456 # API server port (default: 3456)
@@ -71,12 +83,14 @@ When `DATABASE_PATH` and `CAR_STORAGE_PATH` are not specified, the service uses
71
83
72
84
### Running the Daemon
73
85
86
+
⚠️ **PRIVATE_KEY is required** - The service will not start without it.
0 commit comments