Marko
    • Create new note
    • Create a note from template
      • 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
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me 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
    • Save as template
    • 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 Create Help
Create Create new note Create a note from template
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
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me 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
1
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
# SSV network tokenomics analysis [TOC] ### Economics 101 Price is determined ***ONLY* by Supply & Demand,** thus only those effects that change either of the above have any effect on price. $Price(S,D)$ We can *increase* $Price$ by either, making $S$ go down or $D$ go up or both. The inverse is true for decreasing it. **Important takeaway** is to always look for what changes if any has a particular mechanism Supply or Demand. ## Value transfer mechanism ### Direct effect The Token total supply in the system can be thought of as a sum of all agent's balances $B_{a}$ in the system. $$ \sum_{i=1}^n B_{ai}=B_{a1} +B_{a2} ... + B_{ai} $$ All of these mechanisms facilitate transfers between agents in the system. Here is a basic example, where *Staker* pays *Operator* for his services. For simplicity's sake we disregard the network fee for now. We can say that *Payment* $P_i$ is subtracted from Staker's *Balance* $B_{s}$ and added to Operator's *Balance* $B_{o}$ $B_{s}$ - $P_i$ , $B_{o}$ + $P_i$ $=>$ $B_{a1}$ + $P_i$, $B_{a2}$ - $P_i$ $=>$ $$ \sum_{i=1}^n B_{ai}=(B_{a1}+ P_i) +(B_{a2}-P_i) ... + B_{ai} $$ .... What is easy to spot but important to note, that these payments have no effect on the overall sum of balances as they will always net each other to zero. Thus all payments within the system within certain time window can be added separately or netted for each agent, to be a pure inflow or outflow if negative payment $P_{ai}$ of a particular $Agent_i$ but their sum will always be equal to zero. $$ \sum_{i=1}^n P_{ai} = P_{a1} +P_{a2} ... + P_{ai} = 0 $$ Thus we can say that pure transfer payments **within agents in the system** have no direct effect on either *Demand* or *Supply*, thus **no effect on price**. They also do not change *Total supply*, thus no effect on MCap. #### Special case There is a special case, where token transfers have direct effect on the price. That is, if some part of the supply is taken permanently off the market, thus decreasing supply. In our case this would be network fees that are burned. **NOTE:** If fees are used by the governance to fund protocol or whatever else, they have no effect on the token price, as they are only redistributed. ### Indirect effect #### Increased demand The *ONLY* reason why using a native token for value transfer has an indirect effect on MCap is because of transaction costs and system inefficiencies. If and only if a new user ($Agent_{i+1}$) wants to use the system, he needs to acquire some tokens, thus increasing *Demand* $D$, thus having positive effect on token price. It is also important note that in a perfect world forcing users doing transfers in a native token has *NO effect* on the price. Why? Because an agent $Agent_{i}$ has a set utility preference $u_i()$ for holding $Token_x$ at $T_0$ which will amount to $u(Token_x)$ = $B_x$ . Thus he may be holding a non-zero Balance $B_x$ of a given token, but there is no reason to believe that using the system would make him more or less bullish on the project since this is already reflected in his utility function. Thus the rational thing for him to do is to buy every block only the amount he needs for the payment within this block. If he were to buy more, he would increase his exposure above his $u(Token_x)$ and desired target balance $B_x$ . Conversely if he did not buy more he would be decreasing his exposure below his target balance. Of course to buy a specific token on a block-by-block basis is impractical and unrealistic. Thus it is reasonable to assume that a part of agent's balances $B_{a}$ is a balance used for transfers. **NOTE:** Even though we do not live in a perfect world it is important to be cognizant of *"unnaturallity"* of this demand, since it is dictated by system inefficiencies thus it is unstable, since it does not correspond to agents' utility function. In SSV only *Stakers* need to hold a balance for this purpose, lets call it *transfer balance* $B_t$ since, they are the only agents in the system with outflow of payment within it. Neither Governance, nor Operators perfom any transfer payments. Thus what we are looking for is a cumulative sum of *transfer balance*s for stakers $S$ (s of n) $\sum_{s=1}^s B_{ts}$ at a specific time $T_0$. The question then is, what will be the the expected ranges of: number of validators $num(V)$ what will be the average price per validator $avPrice(V)$ and what would be the the average runaway $avRunway(V)$? thus we need input into this function that we need to find are as follows: $$ B_{ts}= avPrice(V)*num(V)*avRunway(V) $$ Important to note here, is that stake operated by private Operators needs to be substracted. Thus we need to find $privateStakeRatio$ = $privateStake/allStake$ as well as $operatorFeesRatio=Operator fees / total fees$, since total fee will include $networkFee$ which should not be subtracted. To subtract privateOperators: $$ B_{ts}= avPrice(V)*num(V)*avRunway(V) - privateStakeRatio*operatorFeesRatio* avPrice(V)*num(V)*avRunway(V) $$ #### Decreased Supply - Token stickiness / inelasticity We can observe in the market that there is a certain "token stickiness" in the market. As reported in [this article]() after a token airdrop, the MCap of the project usually goes up. This may be obvious but is not rational, thus should be accounted for in any system that supposes rational agents. Why this should not be so? Because an agent $Agent_{i}$ has a set utility preference $u_i()$ for holding $Token_x$ at $T_0$ which will amount to $u(Token_x)$ = $B_x$ . There is no reason why a sudden helicopter money (airdrops) should affect his utility function $u(Token_x)$, thus a rational thing for him to do is to sell the whole airdrop, push the price down, thus have no effect (or negative) on the MCap. In practice and especially in the bull market this does not happen. Stickiness could be defined as a ratio of tokens received either (from airdrops, payments, as gift, etc.) but not sold. (the ratio assumes non-zero stickiness, obviously) $$ stickiness = \frac{tokensReceived-tokensSold}{tokensReceived} $$ Thus if an a token stickiness is 10% or 0.1 we can expect an agent receiving 100 tokens to only sell on average 90 and keep 10. In our case Operators are the ones receiving tokens. It is hard to say what would be a stickiness of rewards received, since operators are forced to sell in the long term to cover their expenses, however the actual cost of running one would probably be negligable for most. It is also hard to say how usefull would be this, since in times of stress Operators' reserves that seemed to be sticky during good time can easily cause huge market dump. This can contribute in pronounced price volatility and system instability ### Systemic effects #### Increased volatility **token volatility** - "sticky liquidity" may turn out not to be so sticky in times of stress and be dumped **fee volatility** - fees change based on the token price - there is inherent mismatch between staker's profit in ETH and cost in SSV. He either needs to take on this risk or hedge it. Both are costly and bad UX - Sudden fee increases / drops bring perverse incentives and inefficiens into the system that are insuficciently addressed by `feeUpdate()`. #### Worse UX **system defualts to higher fee equilibrium** - automatic real fee increases caused by the rise in SSV price leads to higher fees - raise of operator fees due to SSV price increase is different to manual increase triggered by the operator - this is so, because the fee increase in this case is coordinated, put simply all operators raise fees at the same time - since this new price equilibrium is set automatically operators need to "defect" from it which would go against their own interests. Example Scenario: Price movement: SSV price goes up 100% in two weeks Operators: 1. Operators are super happy suddenly they are making 100% more. 3. Now if Not more than 50% of stakers were to change their operators, operators are still making more than 2 weeks ago and it makes no sense for them to lower their price. Stakers: 1. Can we expect at this point that staking services are able + willing to change operators at moments notice at this stage? Is it a good UX? 6. Who would they changed to? This is basically synchronized raise of prices of all operators, thus all large operators suddenly charge 100% more and unless more than 50% of stakers would leave them, they are making higher profit than before. Effects: Who has an incentive to defect from this new equilibrium? The only actors with incentive to defect are operators managing small amounts of validators who want to gain market share. Can we expect at this point that stakers will move their services to small lesser known operators? Even If they started doing this in mass this may have the effect on incumbent operators to somewhat lower their prices. Is this the UX we want the stakers to go through? #### Barriers to entry Stakers need to buy token in order to use the system ### Takeaways - Using native token for value trasfers (utility token) has no direct effect on MCap - It has indirect effect on MCap by creating Demand pressure. This is however unstable - We can Calculate size of this demand, if we can come up with reasonable ranges for the variables - It introduces higher tx costs for agents - It makes fees more volatile for the stakers — @Fod’s takeaways/ Marko’s points - Using SSV as the utility token worsens UX, and we want to make the UX as good as can to maximize the number of users. - If SSV is used as a utility token, it creates volatility in several ways (breaking of “stickiness”, selling when price changes, needing to keep operator fees stable/operators needing to change fees often. - Having the SSV as a utility token has weak value through “stickiness”, etc., but this is irrational and unreliable, and therefore it doesn’t really add much value. - We can have the SSV token as a governance token, where ownership is incentivized through a staking mechanism and other incentivization mechanisms. - The network fee drives value to the SSV token regardless if its used as a utility token or a governance token. - Therefore, we might want to use ETH (or other ERC-20) as the fee payments. - How practical is this change? - We might be able to copy and paste from RPL. - We might only have a month before audits.

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