Dynamic SP fees pricing about filefilego HOT 6 CLOSED

Notes: This feature should override the node's global fees per byte. There is some refactoring needed in order for us to support this feature. The refactoring includes the following:

1. DB file metadata to indicate if fees are set
2. Data query response contains the SP's global storage_per_byte and we rely on that. Now with this feature for each file in the data query response we need to specify the fee.

from filefilego.

3. Currently 0 Fees means its a free data retrieval, and anything else is the actual fees per byte. This feature should work in the following cases:

• Even if global fees are 0, we can specify the amount needed for the specific file
• If non zero, we can still specify a file with 0 fees

With the above implementation we can cover every possible combination of dynamic pricing

from filefilego.

In the storage access token introspection rpc method, we have the field which shows if we can override the fees

from filefilego.

UI work must also be done

from filefilego.

We might need an additional protocol to identify SP capabilities and settings. e.g. we could know if SP allows dynamic fees and such so we can propagate this capabilities to UI and other apps

from filefilego.

Work have been completed here

from filefilego.