bsci-filecoin
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Help
Menu
Options
Versions and GitHub Sync Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
Publish Note

Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

Your note will be visible on your profile and discoverable by anyone.
Your note is now live.
This note is visible on your profile and discoverable online.
Everyone on the web can find and read all notes of this public team.
See published notes
Unpublish note
Please check the box to agree to the Community Guidelines.
View profile
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Suggest edit
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
Emoji Reply
Enable
Import from Dropbox Google Drive Gist Clipboard
   owned this note    owned this note      
Published Linked with GitHub
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
--- ###### tags: `shared` --- ![](https://i.imgur.com/0foHdJT.png) # FIP Issue 123 | Qualitative Analysis & CLD > Economic Dynamics of Inner and Extra Protocol Negatively Priced Storage Deals This document aggregates ideas and insights related to the economic implications of [FIP Issue 123](https://github.com/filecoin-project/FIPs/issues/123). The goal is to explore the potential differences between negatively priced deals (NPDs) inside or outside of the Filecoin protocol (vs exploring the dynamics of NPDs in general). This is a high level qualitative analysis to inform discussion. In the future, with the release of the Filecoin [digital twin](https://medium.com/block-science/introducing-complex-adaptive-dynamics-computer-aided-design-cadcad-38b63b541eb8), it will be easier to quickly develop a more data driven understanding of FIP proposals like this one. ## FIP Summary > *The following summary is copied directly from the FIP Issue. More details and discussion can be found on the [FIP 123 GitHub Issue](https://github.com/filecoin-project/FIPs/issues/123).* > The Mission of Filecoin is to create a decentralized, efficient, and robust foundation for humanity’s information. As such, one of the core goals of Filecoin is to create strong incentives for capacity committed to the network to be utilized in storage deals for valuable data. To achieve that, Filecoin clients and storage providers should be able to propose and accept negatively priced deals - aka deals where the storage provider pays the client to store their Filecoin+ data. Right now, demand from storage providers for verified storage deals (made by clients with FIL+ datacap) is very high, since it confers a 10x multiple in block rewards proportional to the verified deal size (which helps storage providers quickly achieve and maximize profitability). However, access to these verified deals is constrained by the number of new storage clients onboarding data onto the network. To compete for this high-value resource, miners should be able to offer not just FREE storage and retrieval for verified deals, but NEGATIVELY PRICED storage/retrieval deals. Negatively priced deals (that share the 10x multiplier returns from FIL+ data with the storage client) will help attract new high-value clients to the Filecoin market, thereby increasing the network's utility and the overall number of FIL+ deals available. As @jbenet mentioned in his EthCC talk, this is a super exciting opportunity that is uniquely available in Filecoin. Instead of having to build these auction/incentive systems outside the deal-making structures of Filecoin, we should simply encode the ability for storage providers to set a negative ask price. ## Current Dynamics ![](https://i.imgur.com/CbmJDDY.jpg) > *Current Filecoin network dynamics wrt negatively priced storage deals.* - Filecoin storage miners have invested a lot of resources in the Filecoin network: capital to purchase storage equipment, time to develop expertise to understand the network, and FIL to participate in the network. - There's an abundance of committed capacity, but not very many storage deals. Supply >> demand. - Some clients are already creating negatively priced deals (NPDs) outside of the Filecoin protocol. This means miners are paying clients, in fiat (not FIL), for the privilege of storing their data on the Filecoin Network to earn FIL subsidies. This has the effect of moving economic activity outside of the Filecoin protocol, making the ecosystem activity/dynamics more opaque, and creating counterparty risk for users due to the use of subjective off-chain contracts rather than deterministic on-chain contracts built into the protocol. - There have been discussions of negatively priced storage deals in various channels such as the Filecoin Slack as well as past community calls. This would allow negatively priced storage deal activity to move on-chain inside the Filecoin network and protocol. - Regardless of whether FIP 123 is enacted or not, the Filecoin network is transitioning from growing Committed Capacity (CC) to growing Verified Deals (VD). Currently demand for VDs is so high that miners are going outside of the protocol to create negatively priced deals (NPDs). This makes the supply/demand dynamics of the deal marketplace crucial to the success of the Filecoin network. ## Potential Future Dynamics ![](https://i.imgur.com/UWDhJsQ.jpg) > *Potential Filecoin network dynamics wrt negative storage deals if FIP 123 is approved.* ### Demand for Storage Services Currently some miners and clients are engaging in NPDs outside of the Filecoin protocol. Were the protocol to natively support NPDs, the amount of clients and miners who engage in NPDs could increase. This might be due to the decreased counterparty risk of protocol coordinated deals, the ease of discovering and engaging in NPDs, or simply awareness that it's an option. Verified deal subsidies support miner operations, however, with a free floating market rate for storage this subsidy could be channeled to clients as miners pay them for deals. This would allow the market to determine where the subsidy is most needed in order to promote network growth and usage. With FIP 123 NPDs would be paid for in FIP, whereas currently it's unknown what currencies miners are using outside the protocol for NPDs. If NPDs were formerly adopted by the Filecoin protocol it would remain to be seen if there would be sustained demand for NPDs, or if the market would correct back to positively priced deals (PPDs) due to increased demand. There is a chance that NPDs could act as a market based "sale" dynamic where Filecoin storage services are offered at a discount when demand is low, but then the discount drives demand back to PPDs. If this happened within the protocol it would be much easier to measure as a signal wrt network health. Negative storage prices could mitigate the perceived risk of storing large amounts of deals, especially if the client has scarce resources. Because IPFS and Filecoin are new, potential clients might be unsure of the utility and reliability of the network. Validating utility/reliability could unlock latent demand. Negatively priced deals (NPDs) could make it easier for potential clients to try the network, then upscale their usage. This could apply to public datasets, for example Wikipedia. ### Supply of Storage Services Artificially setting constraints on storage prices (>= 0) does not allow the market to express preferences via the price signal. As a result, clients who would happily offer to store data on the network at a negative price are excluded from participating in the protocol. With limited demand for services miners might have an incentive to have less efficient operations in terms of computational infra (because no one's using the infra). If inner-protocol NPDs increase demand for storage services, that might incentivize miners to improve operations and/or increase supply to get more deals. If network power and VD grows over time, the VDS FIL reward per sector will go down. If at the same time the FIL price also increases the fiat value of the reward per deal might be the same over time even if the FIL reward per sector/deal is lower. But if the FIL price is uncorrelated with storage/deal volume, then miners might agree to NPDs now that are unprofitable in the future. If NPDs are enforced by the protocol and miners cannot meet the deal requirements they will be terminated deterministically (bad for miners and the clients they store data for). If NPDs are outside the protocol miners might have more flexibility to negotiate prices with clients, defer payment, etc.. allowing them to maintain operations in market downturns (better for miners and clients). So while inner-protocol NPDs could reduce short-term client risk and transaction costs, they could also increase long-term risks for miners - and if miners cease operations that would impact the clients whom they are storing data for. A way to mitigate this might be to restrict inner-protocol NPDs to short time horizons. Overall, these dynamics around NPDs are important because if NPDs really accelerate VD adoption, then the block reward per VD sector should fall quickly which could make NPDs unprofitable. *All that being said, miners could also source loans outside of the protocol to offset volatility (network power and FIL price) regardless of if NPDs are inside or outside of the protocol.* ### Circulating FIL Supply Due to the mechanics of the market actor, miners would likely have to lock FIL into VDs to be released to the client [over the lifetime of the deal](https://spec.filecoin.io/#section-systems.filecoin_markets.onchain_storage_market.storage_deal_flow.deal-payment-and-slashing) based on the [CronTick](https://github.com/filecoin-project/specs-actors/blob/master/actors/builtin/market/market_actor.go#L502) function. We say *likely* here because the exact implementation of FIP 123 has not yet been specified. At the moment both clients and miners deposit FIL into the [StorageMarket](https://spec.filecoin.io/#section-systems.filecoin_markets.onchain_storage_market.storage_market_actor) at the beginning of a deal (see step 1. [here](https://spec.filecoin.io/#section-systems.filecoin_markets.onchain_storage_market.storage_deal_flow.add-storage-deal-and-power)). Currently NPDs happen outside of the protocol and are not released over the lifetime of the deal via CronTick. Due to the fact that extra-protocol NPDs are outside of the protocol we do not have visibility into their structure. They could be paid out over time, all at once, or via any other schedule. Were NPDs to happen within the protocol, these dynamics would become apparent and the FIL token flows would be more predictable. - *Note: It's unclear how a client would technically supply negative FIL to a deal contract. In order to proceed with this analysis we assume that any implementation of FIP 123 would allow the miner to supply the FIL needed for an NPD.* If inner-protocol NPDs increase demand, and thus supply and network usage, that could lead to more FIL being burned via 1559 gas dynamics. This could help offset the inflation of circulating supply that comes from VD subsidies. As the Filecoin network distributes verified deal subsidies (VDS) to miners, those miners might need to sell FIL to pay for operations. Also, end users who receive FIL for NPDs might sell their tokens, esp if they are a business that has their own operating expenses or doesn't want volatile assets on their balance sheet. With inner-protocol NPDs FIL would (probably) be locked and distributed according to the StorageMarket, making the flow of FIL steady and predictable. With extra-protocol NPDs, however, it's unknown if miners would be pricing NPDs in FIL or fiat, or paying for deals upfront or over time. ## Further Research ![](https://i.imgur.com/OfNiVQB.jpg) This high level qualitative analysis is not a complete view of the Filecoin network. It is a perspective based around how [FIP 123](https://github.com/filecoin-project/FIPs/issues/123) (negatively priced storage deals within the Filecoin protocol) might impact key metrics such as end user demand for storage services (clients), storage provider profitability (miners), and value flows (FIL token price). Filecoin is a decentralized network with a diverse set of stakeholders. Different people may have differing interests, goals, and time preferences. Depending on your perspective, enabling negatively priced storage deals could be good or bad. While we cannot advocate for a particular perspective, we hope this high level qualitative analysis provides some insights wrt the dynamics at play. For more information on some of the dynamics that affect Filecoin network economics we recommend: - The Baseline Minting series ([part 1](https://medium.com/block-science/sustainability-goal-achieved-filecoin-network-crosses-baseline-target-cec13a3ed8f) and [part 2](https://medium.com/block-science/baseline-minting-incentives-743b229b9b80)) by [BlockScience](https://block.science/). - The [Economics of Providing Web3 Storage on Filecoin](https://www.starboard.ventures/post/economics-of-providing-web3-storage-on-filecoin) by [Starboard](https://www.starboard.ventures/). To further explore the economic dynamics of Filecoin wrt FIP 123 you can interact with and [fork](https://docs.kumu.io/guides/forking.html) the [causal loop diagram](https://kumu.io/burrrata/fip-123#fip-123) presented in this doc.

Import from clipboard

Paste your markdown or webpage here...

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lose their connection.

Create a note from template

Create a note from template

Oops...
This template has been removed or transferred.
Upgrade
All
  • All
  • Team
No template.

Create a template

Upgrade

Delete template

Do you really want to delete this template?
Turn this template into a regular note and keep its content, versions, and comments.

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Help & Tutorial

How to use Book mode

Slide Example

API Docs

Edit in VSCode

Install browser extension

Contacts

Feedback

Discord

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync
Get Full History Access

  • Edit version name
  • Delete

revision author avatar     named on  

More Less

Note content is identical to the latest version.
Compare
    Choose a version
    No search result
    Version not found
Sign in to link this note to GitHub
Learn more
This note is not linked with GitHub
 

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub
      • Please sign in to GitHub and install the HackMD app on your GitHub repo.
      • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
      Learn more  Sign in to GitHub

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Include title and tags
      Available push count

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully