`filecoin-pin add` "payment capacity" check miss

[BigLep]

Reproduction case:

I updated to use filecoin-pin 0.11.x. This was my first time using my wallet with the new contracts with synapse 0.35.x. (This means my wallet hadn't deposited any USDFC into the new contract.)

I did a filecoin-pin add. I got a "Payment capacity verified", but then later on the operation failed because:

✗ Add failed: StorageContext addPieces failed: Failed to add piece to data set - Failed to create data set.

Details: Warm Storage
InsufficientFundsForMinimumRate(address payer, uint256 minimumRequired, uint256 available)
                               (0x6080Df36FD9B74D04dB3ecCC23b17D6b748CDc26, 60000000000000000, 0) 

This seems like it should have been caught earlier and not given me a "Payment capacity verified".

---

filecoin-pin add output:

filecoin-pin add ~/Downloads/foo.txt
┌  Filecoin Pin Add
│
◇  ✓ File validated (65.5 KB)
│
◇  ✓ Connected to calibration
│
◇  ✓ Payment capacity verified
│
◇  ✓ File packed with root CID: bafybeibpyudd3oprbfzw6spjuvshx5nw5tk3zj6ypphvcirhol7ln3v254
│
◇  ✓ IPFS content loaded (65.7 KB)
│
◇  ✓ Payment capacity verified
│
◇  ✓ Storage context ready
│
│  Storage Context
│
│    Data Set ID: undefined
│    Provider: ezpdpz-calib2
│
◇  ✓ Upload complete
│
│  Download IPFS CAR from SP
│
│    https://calib2.ezpdpz.net/ipfs/bafybeibpyudd3oprbfzw6spjuvshx5nw5tk3zj6ypphvcirhol7ln3v254
│
◇  ✗ Add failed: StorageContext addPieces failed: Failed to add piece to data set - Failed to create data set.

Details: Warm Storage
InsufficientFundsForMinimumRate(address payer, uint256 minimumRequired, uint256 available)
                               (0x6080Df36FD9B74D04dB3ecCC23b17D6b748CDc26, 60000000000000000, 0)
└  Add failed

filecoin-pin payment setup output:

filecoin-pin payments setup
┌  Filecoin Onchain Cloud Payment Setup
│
◇  ✓ Connected to calibration
│
◇  ✓ Balance check complete
│
│  Account:
│    Wallet: 0x6080Df36FD9B74D04dB3ecCC23b17D6b748CDc26
│    Network: calibration
│  Balances:
│    FIL: 1.0998 tFIL
│    USDFC wallet: 190.0000 USDFC
│    USDFC deposited: 0.0000 USDFC
│
◇  ✓ Pricing loaded
│
◇  ✓ WarmStorage permissions already configured
│
│  Current Storage Capacity:
│    No deposit yet
│
│  Current Pricing:
│    1 GiB/month: 0.0024 USDFC
│    1 TiB/month: 2.5000 USDFC
│    (for each upload, WarmStorage service will reserve 30 days of costs as security)
│
◇  Would you like to deposit USDFC to enable storage?
│  Yes
│
│  Storage Examples (per month):
│    100 GiB capacity: ~0.2686 USDFC
│    1 TiB capacity:   ~2.7500 USDFC
│    10 TiB capacity:  ~27.5000 USDFC
│    (deposit covers 1 month + 30-day safety reserve)
│
◇  How much USDFC would you like to deposit?
│  10.0
│
◇  ✓ Deposit complete
│
│    Approval tx: 0x0e4866701257cac3124296ef74790d8c795e1dbaf8ad3dbd27b584c4ebc897dd
│    Deposit tx: 0x8b3aeeca941b3f89eaa03a92c2c2139f1a1d38de878dba2fba68674c061f7225
│  
│  New Storage Capacity:
│    Total deposit: 10.0000 USDFC
│    Capacity: ~3.6 TiB for 1 month
│
◇  ━━━ Setup Complete ━━━
│
│  Network: calibration
│  
│  Wallet
│    190.0000 USDFC available
│  
│  Storage Deposit
│    10.0000 USDFC deposited
│    Capacity: ~3.6 TiB for 1 month
│    (includes 30-day safety reserve)
│
└  Payment setup completed successfully

[BigLep]

@rvagg : here is the issue I shard verbally with you earlier on my 2025-11-04. Let me know if you think this is something others can/should take on, or if this involves synapse changes you'll need to take.

[SgtPooki]

@BigLep we should be able to just add checkAndSetAllowances() inside the add flow to fix this.

There is also a problem with Payment capacity verified showing twice in the add flow. I meant to open an issue for this last week when I cleaned up the output.

[rvagg]

I was hoping to solve this in Synapse and export methods from there to deal with all of this cost jank, but that's turning out to be a stretch this week.

What this needs is a look-up of the floor price, which I'm not sure is even available from Synapse yet, but it's 0.06 per 30 days so if the per-byte amount we come up with is less than that then we need to min() it with 0.06 to find the real number. We could just hardcode that here until we have better Synapse APIs for this.

[BigLep]

Another instance of this: https://filecoinproject.slack.com/archives/C095WFA0QK1/p1762474153468649?thread_ts=1762439779.865969&cid=C095WFA0QK1

[SgtPooki]

gonna hop on this tomorrow