Skip to content

Commit 47f7466

Browse files
TippyFlitsUKjennijuju
authored andcommitted
Add FIP-0100 guidance
Adds a new section to the Storage Provider Basics page explaining daily fees introduced in FIP-0100. Covers how fees are charged, fee debt behaviour, and startup readiness considerations for new SPs, including the 10 TiB threshold and delayed block rewards. Based on internal guidance and FIPs discussion thread #1105.
1 parent a2721ba commit 47f7466

File tree

1 file changed

+37
-3
lines changed

1 file changed

+37
-3
lines changed

storage-providers/basics/README.md

Lines changed: 37 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,42 @@ You need to understand the various earning mechanisms in the Filecoin network.
3434

3535
[Filecoin deals ->](../filecoin-deals/storage-deals.md)
3636

37+
### Daily fees and startup readiness (FIP-0100)
38+
39+
With the activation of [FIP-0100](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0100.md) in network version 25, all new sectors - and any sectors that are extended or updated - incur a daily fee.
40+
41+
This fee replaces the previous batch fee model and introduces a predictable cost structure tied to each sector’s quality-adjusted power and the network’s circulating supply.
42+
43+
The fee begins accruing the day after a sector is committed or extended. It is deducted automatically at the end of each proving deadline.
44+
45+
The network first draws from vesting block rewards. If those are insufficient, it draws from the miner’s available balance. If both are empty, the unpaid amount becomes **fee debt**.
46+
47+
Fee debt does not directly cause faults. However, it can impact operations:
48+
49+
- A miner with fee debt may be blocked from submitting certain messages (e.g., pre-commits or recoveries).
50+
- If the balance is too low to pay for WindowPoSt messages, sectors may fault.
51+
52+
To avoid this, storage providers should:
53+
54+
- Keep a FIL buffer in the miner actor’s balance.
55+
- Avoid fully withdrawing unlocked funds unless upcoming rewards will cover future fees.
56+
57+
### Startup considerations
58+
59+
Miners become eligible to win block rewards once they reach **10 TiB of raw byte power (RBP)**.
60+
61+
However, rewards are not guaranteed as soon as that threshold is met. Block production is probabilistic, and smaller miners may wait longer to win a block - especially when competing against larger ones.
62+
63+
This creates a funding gap during the startup phase.
64+
65+
New storage providers must plan for this by funding their miner actor with enough FIL to:
66+
67+
- Cover daily fees during onboarding,
68+
- Support message submission (like WindowPoSt),
69+
- And continue sealing until rewards start arriving.
70+
71+
While the amount of FIL required is relatively small compared to overall infrastructure costs, it is operationally critical. Without it, the miner may become stuck - unable to seal new sectors or submit required messages due to fee debt or insufficient balance.
72+
3773
## Make sure you have the right skills <a href="#make-sure-you-have-the-right-skills" id="make-sure-you-have-the-right-skills"></a>
3874

3975
As will become clear, running a storage operation is a serious business, with client data and pledged funds at stake. You will be required to run a highly-available service, and there are automatic financial penalties if you cannot demonstrate data availability to the network. There are many things that can go wrong in a data center, on your network, on your OS, or at an application level.
@@ -52,6 +88,4 @@ Take availability and suitable redundancy into consideration when choosing your
5288

5389
[Infrastructure ->](../skills/storage.md)
5490

55-
56-
57-
[Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill\_Page+URL=https://docs.filecoin.io/storage-providers/basics)
91+
[Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill_Page+URL=https://docs.filecoin.io/storage-providers/basics)

0 commit comments

Comments
 (0)