This website uses cookies
We use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners who may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services.
Consent Selection
Details
  • Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

    • Learn more about this provideropens in a new window
      CookieConsentStores the user's cookie consent state for the current domain
      Maximum Storage Duration: 1 yearType: HTTP Cookie
    • Learn more about this provideropens in a new window
      bcookieUsed in order to detect spam and improve the website's security.
      Maximum Storage Duration: 1 yearType: HTTP Cookie
      li_gcStores the user's cookie consent state for the current domain
      Maximum Storage Duration: 180 daysType: HTTP Cookie
    • Learn more about this provideropens in a new window
      datadomeUsed in context with the website's BotManager. The BotManager detects, categorizes and compiles reports on potential bots trying to access the website.
      Maximum Storage Duration: 1 yearType: HTTP Cookie
    • _pk_testcookie_domainThis cookie determines whether the browser accepts cookies.
      Maximum Storage Duration: 1 dayType: HTTP Cookie
    • __cf_bm [x3]This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.
      Maximum Storage Duration: 1 dayType: HTTP Cookie
  • Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in.
    • Learn more about this provideropens in a new window
      lidcRegisters which server-cluster is serving the visitor. This is used in context with load balancing, in order to optimize user experience.
      Maximum Storage Duration: 1 dayType: HTTP Cookie
  • Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.
    • Learn more about this provideropens in a new window
      guestRegisters data on visitors' website-behaviour. This is used for internal analysis and website optimization.
      Maximum Storage Duration: 1 monthType: HTTP Cookie
    • Learn more about this provideropens in a new window
      personalization_idThis cookie is set by Twitter - The cookie allows the visitor to share content from the website onto their Twitter profile.
      Maximum Storage Duration: 400 daysType: HTTP Cookie
    • _pk_uidUsed by Piwik Analytics Platform to identify the visitor on repeat visits to the website.
      Maximum Storage Duration: 1 yearType: HTTP Cookie
      _pk_id#Collects statistics on the user's visits to the website, such as the number of visits, average time spent on the website and what pages have been read.
      Maximum Storage Duration: 1 yearType: HTTP Cookie
      _pk_ses#Used by Piwik Analytics Platform to track page requests from the visitor during the session.
      Maximum Storage Duration: 1 dayType: HTTP Cookie
    • FPGSIDRegisters statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
      Maximum Storage Duration: 1 dayType: HTTP Cookie
      FPIDRegisters statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
      Maximum Storage Duration: 400 daysType: HTTP Cookie
      FPLCRegisters a unique ID that is used to generate statistical data on how the visitor uses the website.
      Maximum Storage Duration: 1 dayType: HTTP Cookie
    • _gaRegisters a unique ID that is used to generate statistical data on how the visitor uses the website.
      Maximum Storage Duration: 2 yearsType: HTTP Cookie
      _ga_#Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit.
      Maximum Storage Duration: 2 yearsType: HTTP Cookie
  • Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.
    • Learn more about this provideropens in a new window

      Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization.

      ads/ga-audiencesUsed by Google AdWords to re-engage visitors that are likely to convert to customers based on the visitor's online behaviour across websites.
      Maximum Storage Duration: SessionType: Pixel Tracker
    • Learn more about this provideropens in a new window
      userRefererDetermines how the user accessed the website. This information is used by the website operator in order to measure the efficiency of their marketing.
      Maximum Storage Duration: 1 monthType: HTTP Cookie
    • Learn more about this provideropens in a new window
      #:session-dataTracks the individual sessions on the website, allowing the website to compile statistical data from multiple visits. This data can also be used to create leads for marketing purposes.
      Maximum Storage Duration: PersistentType: HTML Local Storage
      eng_mtTracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website.
      Maximum Storage Duration: PersistentType: HTML Local Storage
      t_gidThis cookie assigns a specific visitor ID, when the visitor interacts with ads or content from the website - this allows the website to target the visitor with similar ads or content.
      Maximum Storage Duration: 1 yearType: HTTP Cookie
      t_pt_gidCollects information on user preferences and/or interaction with web-campaign content - This is used on CRM-campaign-platform used by website owners for promoting events or products.
      Maximum Storage Duration: 1 yearType: HTTP Cookie
      taboola global:user-idSets a unique ID for the visitor, that allows third party advertisers to target the visitor with relevant advertisement. This pairing service is provided by third party advertisement hubs, which facilitates real-time bidding for advertisers.
      Maximum Storage Duration: PersistentType: HTML Local Storage
      taboola_session_idThis cookie is used to collect information on a visitor. This information will become an ID string with information on a specific visitor – ID information strings can be used to target groups with similar preferences, or can be used by third-party domains or ad-exchanges.
      Maximum Storage Duration: SessionType: HTTP Cookie
    • Learn more about this provideropens in a new window
      1/i/adsct [x2]Collects data on user behaviour and interaction in order to optimize the website and make advertisement on the website more relevant.
      Maximum Storage Duration: SessionType: Pixel Tracker
      muc_adsCollects data on user behaviour and interaction in order to optimize the website and make advertisement on the website more relevant.
      Maximum Storage Duration: 400 daysType: HTTP Cookie
      guest_idCollects data related to the user's visits to the website, such as the number of visits, average time spent on the website and which pages have been loaded, with the purpose of personalising and improving the Twitter service.
      Maximum Storage Duration: 400 daysType: HTTP Cookie
      guest_id_adsCollects information on user behaviour on multiple websites. This information is used in order to optimize the relevance of advertisement on the website.
      Maximum Storage Duration: 400 daysType: HTTP Cookie
      guest_id_marketingCollects information on user behaviour on multiple websites. This information is used in order to optimize the relevance of advertisement on the website.
      Maximum Storage Duration: 400 daysType: HTTP Cookie
    • _gcl_auUsed by Google AdSense for experimenting with advertisement efficiency across websites using their services.
      Maximum Storage Duration: 3 monthsType: HTTP Cookie
      _gcl_lsTracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website.
      Maximum Storage Duration: PersistentType: HTML Local Storage
    • pardot [x2]Used in context with Account-Based-Marketing (ABM). The cookie registers data such as IP-addresses, time spent on the website and page requests for the visit. This is used for retargeting of multiple users rooting from the same IP-addresses. ABM usually facilitates B2B marketing purposes.
      Maximum Storage Duration: SessionType: HTTP Cookie
  • Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.
    • cs_analytics_ip_blockedPending
      Maximum Storage Duration: SessionType: HTTP Cookie
      user_tokenPending
      Maximum Storage Duration: 1 yearType: HTTP Cookie
    • _twpidPending
      Maximum Storage Duration: SessionType: HTTP Cookie
Cookie declaration last updated on 8/20/26 by Cookiebot
[#IABV2_TITLE#]
[#IABV2_BODY_INTRO#]
[#IABV2_BODY_LEGITIMATE_INTEREST_INTRO#]
[#IABV2_BODY_PREFERENCE_INTRO#]
[#IABV2_BODY_PURPOSES_INTRO#]
[#IABV2_BODY_PURPOSES#]
[#IABV2_BODY_FEATURES_INTRO#]
[#IABV2_BODY_FEATURES#]
[#IABV2_BODY_PARTNERS_INTRO#]
[#IABV2_BODY_PARTNERS#]
About
Cookies are small text files that can be used by websites to make a user's experience more efficient.

The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies we need your permission.

This site uses different types of cookies. Some cookies are placed by third party services that appear on our pages.

You can at any time change or withdraw your consent from the Cookie Declaration on our website.

Learn more about who we are, how you can contact us and how we process personal data in our Privacy Policy.

Please state your consent ID and date when you contact us regarding your consent.
Image How The Merge Could Impact Yields

How The Merge Could Impact Yields

Timer9 Min. Lesezeit

  • Ethereum
  • Technologie

The Merge aims to move Ethereum from Proof of Work (PoW) to Proof of Stake (PoS), and provide the foundation for increased scalability and reduced energy consumption. Detrimental trade-offs in terms of censorship resistance, trust minimisation and decentralisation could occur as we have detailed here.

This article aims to investigate possible optimistic, base and pessimistic scenarios across three different potential Merge dates for a validator with >=32ETH. Our research assumes The Merge could occur in H2 2022 with:

  1. base case yields sitting at around 8% APY - approximately double (x2) current yields of 4.3% (as of 23 May 2022)

  2. optimistic yields sitting at around 10-12% APY

  3. pessimistic yields sitting at 4% APY

Please note that this article is intended as research only and is not intended to be taken as investment advice.

Model results

Potential ETH Yield at Merge

Outcome Explanation

High Yield Case Calculation

Model methodology & critique

Ethereum’s changing monetary policy makes revenues hard to project over the long term in a granular fashion. However, assumptions need to be made that provide possible varying degrees of potential yield vs realised yield. This includes the date of The Merge which is not set, although consensus seems to be around August 2022, and what could be optimistic or pessimistic scenarios for multiple Variable Inputs.

Risks and rewards of staking

Staking 32ETH as soon as possible means a validator will likely receive a higher yield than staking later on. Becoming a validator allows the earning of maximum rewards directly from the protocol by proposing (batching transactions into a new block) and attesting (checking proposals from other validators) blocks, as well as tip fees from users. The key part is that in the future, it is very likely that there will be more ETH staked than presently. This is likely to reduce the yield because the block subsidies are distributed to a higher number of people, so each validator is likely to receive a smaller percentage of the rewards.

However, staking now does entail some risks. A validator is risking a lot of money which could be lost partially through penalties such as going offline or slashed severely by performing malicious actions (like double proposing or double voting). Or even being ejected from the network - but in reality, the penalties for imperfect behaviour are quite low. If one stakes prior to the Merge, their staked funds and rewards are locked up and cannot be withdrawn and it is unclear as to precisely when withdrawals can be allowed post-Merge as well.

Summary

Once The Merge occurs, Ethereum will intrinsically produce cash flow as investors deposit ETH to become a validator (propose and attest blocks to secure the chain and keep the chain moving forward) and receive ETH as a reward. This creates a dynamic yield which depends on two main factors: a) how much revenue (tip fee and block subsidy) one earns; b) how much ETH is staked.

RevenueNetwork StakeYield
HighLow/AverageHigh
Low/AverageHighLow
HighHighAverage
LowLowAverage

Appendix

Below is CoinShares’ estimate calculation for the July 2022 optimistic case.

CoinShares’ estimate calculation for the July 2022 optimistic case

The Merge date was denounced once again

I chose July 2022, September 2022 and November 2022 as potential Merge dates because Vitalik Buterin, at the Ethereum Shanghai Summit, and other core Ethereum developers have mentioned it could occur in August if there are no issues. The Arrow Glacier fork rescheduled the Difficulty Bomb for June 2022 but it is likely to be pushed back again. These are noticeable exponential increases in block times, making it almost impossible for miners to create a block, and therefore reducing their ability to earn revenue for their operations. This practically leaves them redundant on a chain that doesn’t move forward. The community would not like to be forced onto a chain that is not fully complete with minimise or no issues. So it is likely that validators will accept a rescheduled Difficulty Bomb proposal to fork the chain and buy more time for the community to successfully Merge.

Multiple testnet and shadow fork merges have been deemed a success with Merge readiness almost seemingly complete. These practice merges reduce the execution risk of the Proof of Work chain (Mainnet) docking onto the Proof of Stake chain (The Beacon Chain). Issues such as integrating clients and facilitating effective block gossip and state synchronisation is imperative to how consensus is reached and transactions become finalised.

Hence, potential Merge dates align towards H2 2022.

The amount of ETH Staked is critical to your yield

After the Beacon Chain’s Staking Deposit Contract deployed on October 12th 2020. The first ETH staked was on November 3rd 2020. I took the trendline from the first date to current with an r2(accuracy) of over 0.98 as the base case and chose an optimistic scenario (base case 95%) and pessimistic scenario (base case 110%). Less ETH staked likely means a higher yield because a validator’s own validator balance (stake) is a higher proportion of overall network stake. Therefore, their revenue is a higher proportion of their overall network stake.

I think it’s highly likely that the amount of ETH staked will continue to increase which is proportionately bad for network and validator yields. This extrapolation works because these dates are not far in the future.

ETH Staked

ETH staked is one of the models’ Variable Inputs to show the total ETH issuance on a daily and annual basis given the current state of the network (determined by the calculator user). It is important to note that this is imperfect due to the dynamic nature of ETH 2 issuance rate.

The more ETH staked directly increases the Number of Validators Online and Per Shard because validators can only deposit in 32 ETH batches and there is likely a fixed limit of 64 shards. And, indirectly, more ETH staked likley means higher block subsidy from increased block proposals and attestation and, therefore, a higher network issuance rate.

However, more ETH staked decreases the Base Reward for Full Validators. Even though the total block subsidy increases to fund those validators, the return rate per validator decreases because they individually receive less rewards proportionately to the growing network as the number of validators increases.

Validator revenue is composed of Tip Fee and Block Subsidy.

Tip Fees are what is paid to the validator by the user to prioritise their transaction in the next block. Without tips, validators would find it economically viable to create empty blocks, as they would receive the same block reward. A fee market for transactions is created for users to outbid competing transactions. Users that need their transaction to get stuffed into a block, gossiped across the network according to the blockchain’s rules and and accepted by other nodes ahead of other transactions in the same block, are likely to pay a higher tip.

Daily Free Revenue (ETH) Since EIP 1559

I took the daily total miner fee revenue distribution for optimistic (75th percentile), base (50th percentile) and pessimistic (25th percentile) scenarios and projected each scenario out to the three different Merge dates using the Compound Annual Growth Rate (CAGR) of -3% since Ethereum’s most recent monetary policy change, EIP 1559.

This method shows much revenue a validator could receive depending on their network-weighted stake as a full peer.

YoY Daily Free Miner Revenue Distribution (ETH)

Having calculated what the daily fee miner revenue distribution is, I extracted only the tip (removed base fee).

The average fee burn percentage is 85% since The London Hard Fork (EIP1559) on December 1st 2020. Therefore, it is reasonable to assume in an optimistic case, less fees (80%) would be burned so miners would likely receive more revenue; and, in a pessimistic case, more fees (90%) would be burned and they would likely receive less revenue.

Annualised validator revenue = average daily fee revenue (1 - fee burn percentage) 365

The higher the annualised tip fee revenue and the lower the fee burn percentage, the higher the yield.

The other side of the equation

Block subsidy (newly minted supply) is issued by validators proposing blocks. This is a complicated calculation and involves a few components. Essentially, the block reward is the outcome of subtracting the total number of offline validator penalties - taking into account network uptime and validator uptime - from online validator rewards. If there are less validators online, there are less validators to reward because less blocks have been proposed and attested. Therefore, the total block subsidy per year decreases.

Uptime affects the amount total network rewards

To sustain perfect market conditions with full validator and network uptime is very unlikely because of issues such as electricity outages. Slashing validators for being offline and punishing them for incorrect proposals and attestations incentivises them to act honestly and be online for as long as possible.

Post MainNet Shadow Fork 2 (a recent practice Merge), only around 95% of all validators were live and correct. Therefore, an optimistic case would be 100% and a pessimistic case would be 90%

Veröffentlicht amJuni 8th, 2022

Schriftsteller
CoinShares Author Logo
Max Shannon

Willkommen bei CoinShares

Personenbezogene Daten

0102

Wir verwenden Cookies, um Inhalte und Anzeigen zu personalisieren, um Funktionen für soziale Medien bereitzustellen und um unseren Datenverkehr zu analysieren. Wir geben auch Informationen über Ihre Nutzung unserer Website an unsere Partner für soziale Medien, Werbung und Analysen weiter, die diese mit anderen Informationen kombinieren können, die Sie ihnen zur Verfügung gestellt haben oder die sie aus Ihrer Nutzung ihrer Dienste gesammelt haben. Wenn Sie die Verwendung von Cookies akzeptieren, erklären Sie sich mit der in der Datenschutzrichtlinie und der Cookie-Richtlinie beschriebenen Verarbeitung dieser Daten einverstanden.

 

Wir verwenden Cookies auf unserer Website, um unsere Dienste zu optimieren. Erfahren Sie mehr über unsere EU-Cookie-Richtlinie oder unsere US-Cookie-Richtlinie.

  • Erforderlich
    Question circle icon
  • Präferenzen
    Question circle icon
  • Statistisch
    Question circle icon
  • Marketing
    Question circle icon
Notwendige Cookies helfen dabei, eine Website nutzbar zu machen, indem sie grundlegende Funktionen wie die Seitennavigation und den Zugang zu sicheren Bereichen der Website ermöglichen. Ohne diese Cookies kann die Website nicht richtig funktionieren.
Präferenz-Cookies ermöglichen es einer Website, Informationen zu speichern, die das Verhalten oder Aussehen der Website verändern, wie z. B. Ihre bevorzugte Sprache oder die Region, in der Sie sich befinden.
Statistik-Cookies helfen Website-Betreibern zu verstehen, wie Besucher mit Websites interagieren, indem sie Informationen anonym sammeln und melden.
Marketing-Cookies werden verwendet, um Besucher auf verschiedenen Websites zu verfolgen. Ziel ist es, Anzeigen zu schalten, die für den einzelnen Nutzer relevant und ansprechend sind und damit für Verlage und dritte Werbetreibende wertvoller sind.