crypto-econ-lab
      • 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
--- title: Cryptoeconomic impacts of Direct Data Onboarding tags: Econ monitor --- **Authors**: CryptoEconLab ## Summary * [FIP-0076](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0076.md) (Direct Data Onboarding/DDO) introduces technical upgrades to the Filecoin network that offer alternative messaging pathways for onboarding deal power that reduce gas. * In this note, we assess the cryptoeconomic impacts of DDO, namely the supply statistics. Since DDO frees block space, we identify three relevant cases: * Case 1 - There is no increase in onboarding or chain activity to fill emptied block space. * Case 2 - There is an increase in onboarding, but not enough to fill block space to the target of 5B gas units. * Case 3 - There is an increase in onboarding and chain activity to fill block space to the target. * **Findings**: * Gas burn from $\mathtt{basefee}$ is a small percentage of the $\mathtt{net_outflow}$ of circulating supply. This implies that DDO has a small impact on overall circulating supply (CS) and Locked/CS. * However, because burned tokens exit the supply permanently while locked tokens exit temporarily, burning provides permanent protocol revenue and thus remains an essential aspect of the network’s cryptoeconomic health. * Increasing onboarding rates will decrease CS and increase L/CS, even if no protocol revenue is generated from burning $\mathtt{basefee}$. This is because the outflow due to locking pledge is significantly higher than the outflow due to burn of PSD messages, when onboarding deal power. * DDO frees up block space, enabling a higher throughput for onboarding power onto the network. With current estimates of gas savings and onboarding rates, the chain will be able to support ~300 PiB/day of deal power. This would require ~350M FIL of investment into the network. ## Introduction In this note, we examine the cryptoeconomic effects of Direct Data Onboarding (DDO) on the supply statistics of Filecoin. Direct Data Onboarding is a FIP that introduces technical upgrades which enable a cheaper pathway to onboard deal power onto the Filecoin network. Many expenses are associated with onboarding FIL+ data, but DDO addresses gas-related expenses. ### Gas & Base-Fee Background Gas is a measure of the computational resources that a message will impose on the blockchain. Therefore, different messages require different amounts of gas. The Gas Fee (or transaction fee) used to charge for those computational resources contains two components, the amount of Gas used to submit a message (in units of Gas) and the $\mathtt{basefee}$ (fee per unit of gas). Since transactions are settled in units of FIL, the cost of submitting a particular message at epoch=t is given by: $$ \mathtt{cost} = (\mathtt{basefee_t} + \mathtt{minertip}) * \mathtt{gasrequired_t} $$ $\mathtt{gasrequired_t}$ depends both on the type of message being sent as well as when the message is sent to be included in the blockchain. $\mathtt{basefee_t}$ is a time-varying value in units of (FIL/gas) that sets an economic cost for submitting messages to the blockchain. In Filecoin, this cost amount of tokens is burned, indirectly compensating blockchain validators and token holders due to a permanent reduction in supply. This is denoted as the $\mathtt{basefee}$ component of protocol revenue; the other components of protocol revenue are from penalties, estimation fees, and fees for batching messages. $\mathtt{basefee_t}$ varies according to the following relation: $$ b[i+1] = b[i] \left( 1 + \frac{s[i] - s^*}{8 s^*} \right)$$ where $s^*$ is the target block size (5B Gas units in Filecoin), and $s[i]$ is the block size at epoch=i, b[i] is the $\mathtt{basefee}$ at epoch=i and b[i+1] is the next epoch’s $\mathtt{basefee}$. $\mathtt{basefee}$ increases from its previous value if the block size at the previous epoch exceeds the target block size, and vice-versa. If block space usage is consistently below the target block space, then $\mathtt{basefee}$ goes to it's minimal value. Similarly, as $\mathtt{basefee}$ starts to increase, the cost to submit messages to the blockchain increases and becomes increasingly uneconomical, incentivizing users to wait to submit new messages until the $\mathtt{basefee}$ is reduced. ### DDO Relevance to Gas To onboard deal-power onto Filecoin, two specific messages need to be submitted to the network, the PSD message and the ProveCommit message. DDO reduces the amount of gas needed when onboarding a deal sector by offering an alternative messaging pathway to PSD and reducing the gas needed for ProveCommit messages. The reduction in gas usage changes the $\mathtt{basefee_t}$ trajectory which then results in a change to the protocol revenue. There are three relevant cases to consider: * Case 1 - There is no increase in onboarding or chain activity to fill emptied block space. * Case 2 - There is an increase in onboarding, but not enough of an increase to fill up excess block space. * Case 3 - There is an increase in onboarding and chain activity to fill up block space to the target of 5B gas units. The case where block space exceeds the target is irrelevant because the economic disincentive for miners to exceed the target block space is strong and grows stronger the longer this behavior is sustained. This is a result of the $\mathtt{basefee_t}$ update given in Eq. 2. We now consider what happens to the supply characteristics in each case outlined. ## Case 1 - No change in onboarding & no increase in chain activity due to other sources Case 1 simulates the belief that current macroeconomic forces (high interest rates, etc.) are the primary driver for onboarding and renewals in Filecoin. This belief translates to no increased onboarding of deal power onto Filecoin because the most significant cost for onboarding power is the initial pledge. The lack of additional onboarding, combined with the gas reduction of the PSD and ProveCommit messages results in overall reduced gas usage. From Eq. 2, this will result in $\mathtt{basefee}$ remaining near zero because the increase in available chain capacity is not utilised with increased onboarding or chain activity. To simulate Case 1’s impact on the circulating supply, we first estimate the change in the cumulative amount of gas burned over the simulation window if $\mathtt{basefee}$ is zero. In this case, protocol revenue comes from $\mathtt{penalty}$, $\mathtt{batchfee}$, and $\mathtt{overestimationfee}$ and excludes $\mathtt{basefee}$. The simulation framework, mechaFIL, simulates gas burned by taking the mean of daily burn over a historical window and linearly extending that to forecast the future. Following this approach, we compute over the same window the percentage of gas burn attributed to base_fee. The median value is 54%, meaning that 46% of gas burn is attributed to the other sources previously mentioned. Using this forecasted burn and extending onboarding, renewals, and FIL+ rate at current levels, we can compute the difference in supply statistics between the case where DDO is implemented and where it is not. Fig. 1 shows the relevant supply metrics. ![case1](https://hackmd.io/_uploads/HJfEA9SIT.png) *Fig 1: The difference in circulating supply and L/CS trajectories with DDO.* We observe that there are minimal changes to the supply statistics. That is because burn is a small percentage of $\mathtt{net_outflow}$. Outflow from the circulating supply has two components: $$ \mathtt{net_outflow = locking + burning} $$ Fig. 2 shows various perspectives of gas burn on supply statistics. Fig 2A shows the percentage of FIL burned as a percentage of the total circulating supply. Fig 2B shows the percentage of daily outflow attributed to burn, while 2C shows the daily outflow attributed only to the base_fee component of burn. ![attrib_basefee_burn](https://hackmd.io/_uploads/SyR0f5SUT.png) *Fig 2: A) Daily burn as a function of total circulating supply B) Daily outflow attributed to protocol burn over the past 6 months C) Daily outflow attributed to $\mathtt{basefee}$ burn over the past 6 months.* We observe that the mean values of daily outflow attributed to burn and $\mathtt{basefee}$ burn are small compared to the outflow attributed to locking. However, an important point to note is that while burn is a smaller component, it has a different effect on the network. Burn permanently removes tokens from the circulating supply, while the effect of locking is temporary. We can model the impact of locking and burn on circulating supply by applying a discount factor to locking. The discount factor expresses the idea that removing items from the circulating supply is more beneficial now than in the future; akin to the time value of money, where money is more valuable in the present than the future. We leave it to future research to select appropriate discount factors that align with network goals. ## Case 2 - Increased onboarding, but not enough to fill emptied block space. We now analyze Case 2 - the scenario where block space is not filled to the target, even though onboarding increases. To show the effect of this on supply, let us define the base case to be the same level of onboarding as before DDO was implemented. Then, define the FIL conserved case as the onboarding level increased by the percentage of gas-cost savings afforded by DDO. Using SP cost information, we find that on average, the percentage of costs attributable to gas for onboarding sectors is 0.026% (Fig 3) of the total onboarding costs across a range of exchange rates considered under assumptions detailed [here](https://hackmd.io/gzftJx5eQDKhv4-UEubSgg?view=#When-Filecoin-Plus-works-and-when-it-doesn%E2%80%99t). ![gas_cost_pct](https://hackmd.io/_uploads/r1G-m9SIa.png) *Fig 3: Gas cost percentage of total cost needed to onboard a sector, swept across multiple FIL exchange rates* We then compute multipliers of increased onboarding amounts from that level to see how those situations affect network supply statistics. We keep the gas burn due to $\mathtt{basefee}$ zero, as in Case 1 - this is a consequence of the assumptions of Case 2. Fig 4 shows the effect on supply for the FIL conserved case defined, 1.1x, and 1.2x the FIL conserved case. The increased rates are in units of RBP; at the current FIL+ rate of ~92%, this translates to a 9.2x increase in deal onboarding rate. ![case2](https://hackmd.io/_uploads/BJn-75B86.png) *Fig 4: Changes to the supply statistics in Case 2. Even though $\mathtt{basefee}$ is 0 in Case 2, increases in onboarding result in noticeable changes to circulating supply, locked, and L/CS.* The changes in supply are significant because: 1. The change in RBP is maginified for deal power due to the 10x QA multiplier 2. As onboarding is scaled up, circulating supply decreases while network locked increases. These are compounding effects that result in a large change to the L/CS trajectory. In the FIL conserved regime, the small increase in onboarding that results from decreased gas costs does not result in any meaningful changes to the supply statistics (blue line) from the status-quo. This makes sense because gas costs are a small percentage of the total cost for onboarding sectors. ## Case 3 - Increased onboarding and chain activity for gas to reach target block space. We now analyze Case 3 - the scenario where block space is filled to the capacity through increased onboarding and other chain activities. We use the same simulation methodology as above, but implement gas burn due to $\mathtt{basefee}$, and scale RBP onboarding as before. Fig 5 shows the changes from status quo for the supply statistics when the same scaling is considered. The trends are almost identical to Case 2, where there is no gas burn due to $\mathtt{basefee}$. From a supply perspective, this makes sense b/c burn due to $\mathtt{basefee}$ is a small percentage of circulating supply. ![case3a](https://hackmd.io/_uploads/HJ1Xm9HUp.png) *Fig 5: Changes to the supply statistics in Case 3.* ## Monetary Considerations of DDO In this section, we estimate the additional investment needed to fully utilize the chain through power onboarding. More precisely, we aim to answer the question: what does the power onboarding rate need to be, such that the same amount of gas is used for onboarding as it was previously? We examine the PSD case in isolation since it is the most significant contributor to gas usage when onboarding deal sectors. To do so, we build a Generalized Linear Model (GLM) that forecasts the amount of PSD gas used based on the amount of onboarded deal power. This should be a strong relationship because mechanistically, onboarding power causes PSD messages to be generated. The model is trained using historical data from the network. Fig 6 shows the trained model’s fit to the historical data. ![glm_case2_historical](https://hackmd.io/_uploads/Sk3Q75rUp.png) *Fig 6: GLM trained on historical paired data of onboarded deal power to PSD gas used. The blue dots are historical data, and the dotted red line represents the GLM forecast.* Next, we use estimates from the DDO engineering team that DDO will reduce gas usage by 85% if the new pathway for onboarding is used, rather than the PSD pathway. To model this, we scale the GLM model In Fig 6 by 85%. More precisely, if gas usage for PSD is reduced by 85%, then power will need to scale up by 85% to match the same gas usage as before. The DDO model compared to the status quo is shown in Fig 7. ![glm_case2_extrapolate](https://hackmd.io/_uploads/HJ6N7qHIp.png) *Fig 7: Hypothetical model for forecasting the gas used when onboarding deal power with DDO implemented.* Current onboarding levels are roughly 4.76 PiB RBP/day at 92.6% FIL+ Rate, which translates to 44 PiB/day of deal power being onboarded. If DDO reduces gas usage by 85%, this increases the capacity of the chain to onboard upto ~293 PiB/day of deal power (under the linear scaling assumption). Next, we compute the necessary investment to flow into the Filecoin network to support the increased QA power. We simulate this via MechaFIL, which takes into account the fact that pledge decreases as network QAP increases (below): $$ ConsensusPledge = 0.3 \times CS \times \frac{SectorQA}{max\{b(t), NetworkQA\}}$$ The simulation results are shown below in Fig 8 - they indicate that even though the pledge per sector decreases as onboarding increases, the overall investment increases. ![onboarding_vs_investment](https://hackmd.io/_uploads/SyFL7cBLT.png) *Fig 8: Dynamics of pledge per sector and total investment needed to onboard various multipliers of the current onboarding rate (in black). The figure shows that while pledge per sector decreases as the onboarding rate increases, the total investment is still greater.* A related perspective is to compute the total investment needed to increase onboarding over the simulation timeframe as a function of increasing the onboarding rate, normalized to the status quo level. Fig 9 shows this perspective and indicates that the additional investment needed for the pledge to increase onboarding is significant, even though the growth rate is sublinear. ![onboarding_vs_investment_cumulative](https://hackmd.io/_uploads/S1ND7cSLp.png) *Fig 9: Total investment needed to onboard greater amounts of RBP than status quo.* ## Conclusion The cryptoeconomic impacts of DDO have been explored in this report. We find that it is unlikely to have a significant impact on supply. This is due primarily to the fact that gas_burn is a minor contributor to overall $\mathtt{net_outflow}$. The reduced gas burn has two potentially negative consequences: * Reduced cost to spam the blockchain with irrelevant messages * Reducing the permanent outflow effect of burn Finally, while the cryptoeconomic impacts are reduced, the technical upgrades enable more data onboarding throughput, and consquently enable more investment to flow into the network. While the amount of investment needed is large, the technical upgrade enables it to be possible. ## References 1. [MechaFIL](https://github.com/protocol/filecoin-mecha-twin) 2. [Simulation Notebooks](https://github.com/protocol/CryptoEconLab/tree/mechafil-jax-notebooks/notebooks/mechafil_jax/direct_filp_v2)

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