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 The Compromises and Benefits of Ethereum switching to a Proof of Stake network

The Compromises and Benefits of Ethereum switching to a Proof of Stake network

Timer10 min de lecture

  • Ethereum
  • Technologie

Before its launch in 2015, Ethereum developers already had a stated ambition to replace its Proof-of-Work (PoW) consensus mechanism with an alternative one: Proof-of-Stake (PoS). While it was deemed too technically risky to start the network with anything other than PoW, the eventual migration to PoS has been a major development goal of Ethereum developers and a highly anticipated milestone on their roadmap.

The migration to PoS is considered to be an extremely important milestone because developers regard it as a key prerequisite for several subsequent development goals, and because the Ethereum community believes the reduction in energy usage is worth the trade-offs in protocol attributes it generates.

Though subject to some changes, the development roadmap itself predates the launch of Ethereum and has existed since the network was only in its testnet phase. Many of the changes described in the evolving roadmap have already been implemented, but the migration to PoS, one of the most challenging and involved modifications, has yet to be completed, and is now delayed.

Ethereum Roadmap 2015 - 2023The reasons for the delays are many and complex, but they more or less reduce to PoS proving much more technically challenging to safely implement than developers first thought. Many prototypes have been proposed and evaluated, but problems have kept emerging, necessitating ongoing multi-year bouts of bug-fixes and redesigns.

We can even observe the serial delays of the migration, often referred to as the Merge, from blockchain data. Confident that the PoS implementation is ever near at hand, the Ethereum protocol contains a hard-coded exponential increase in mining difficulty. This mechanism is called the difficulty bomb and is designed to cause mining difficulty and revenues to disconnect, forcing miners to abandon the PoW chain, leaving the alternative PoS chain as the only viable one.

Ethereum Shift to Proof-of-Stake Attempts

Three separate ‘detonations’ of the difficulty bomb can be observed in the above figure. They are visible both as exponential increases in block times, and as rapid divergences between hashrate and difficulty. However, since PoS has never been ready to implement at the time of the detonation (or upcoming detonation) Ethereum developers have rolled back the difficulty bomb on five separate occasions.

All this being said, and while no specific date exists for the Merge as of the time of writing (and the Merge has indeed just been delayed again from H1 2022, tentatively to H2 2022), there are emerging signs perhaps warranting cautious optimism that PoS implementation might actually be forthcoming this time around.

So let’s have a quick look at what the next phase of Ethereum would actually look like.

 

Future Sharding Also Rests on The Merge

In addition to PoS (The Merge), the second major part of Ethereum’s next phase is the introduction of sharding. Sharding is a blockchain protocol scalability technique whereby the protocol increases its throughput by splitting the blockchain into many blockchains (shards), allowing single computers to choose which of the many blockchains to work on.

Sharding allows the total throughput of the protocol to increase without increasing the computational demand of the individual computers working on it. In other words, Ethereum will be able to process a lot more information while still hoping to rely on relatively casual users providing distributed processing power through regular consumer computers.

In the world of computer science this is referred to as a horizontal scaling technique. Horizontal scaling is characterised by increasing throughput/capability by adding more individual computers to a network. Its alternative is vertical scaling whereby increased scale is only achieved through increasing the throughput/capability of the individual network computers.

Vertical and Horizontal Sharding/Scaling split up the chain in opposite waysIn the world of blockchain protocols, increasing block sizes or increasing block frequencies (reducing the targeted time between blocks) are examples of vertical scaling as they require that all computers participating must be very powerful (which is expensive). Conversely, sharding allows additional throughput/capability—which means the ability to process a lot more transactions and smart contracts per second, at much lower costs—by adding more network participants, assuming that they will all care about separate shards.

 

Adding PoS and Sharding Incurs Important Trade-Offs in Network Attributes

When designing decentralised peer-to-peer networks there is no such thing as perfect solutions to problems. There are only costs, rewards and trade-offs.

Conversely, when analysing proposed changes to blockchain protocols it is very important to not get carried away by the optimism which often pervades the developer and user communities of the various networks (nor to fall prey to the pervasive pessimism common among competitors). So let’s have a brief look at the trade-offs the Ethereum community is willing to make in order to achieve increased throughput/capability on-chain and to reduce the energy use of the protocol down to effectively nothing.

 

Sharding Trade-Offs

The trade-off for both horizontal scaling of a blockchain network, versus keeping throughput low, is that the network as a whole becomes more like a client-server network than a peer-to-peer network, losing out on important decentralisation benefits.

Why is that? Briefly explained, in order to be a full peer in a blockchain network—that is, someone who participates in the network without the need to trust any other network participant—a user must be able to fully verify every single event that happens on the network. With a multitude of blockchains (or a single huge one) to verify, the computational and bandwidth resources required to be a full peer increases dramatically, making fewer and fewer users able to afford the privilege of being full peers. This results in the reintroduction of trust as all users who are now unable to verify all shards (or a huge single blockchain) must trust other users to tell them the truth about what happened on other shards (or on the huge blockchain they can no longer afford to self-verify).

A high level of decentralisation is a sought after yet traditionally hard to define quality of peer-to-peer networks. The reason for its desirability is that a network with as many peers as possible becomes impossible to shut down due to the huge number of participants, all of whom must be disabled for the network to be fully extinguished.

Whereas network anonymity techniques make it impossible to reliably measure the number of participants on a blockchain network, there are useful proxies we can use to evaluate its level of decentralisation. In our opinion the best one is the cost of being a full peer. The more costly it is to be a full peer, the less decentralised a network will be.

Any protocol change which increases the cost of being a full peer therefore reduces the decentralisation of the network. This is the tradeoff cost incurred for the benefits of increased throughput/capability on-chain. To get a sense of the magnitudes of difference, consider that in order to be a full peer on Ethereum after the Merge, a user will need 32 ETH (~$92,000 at the time of writing, 25 April 2022) plus dedicated computer hardware, possibly not costing more than an additional thousand dollars. In contrast, being a full peer on the Bitcoin Network costs less than $300 and requires no amount of bitcoin, however, the tradeoff incurred on the Bitcoin Network is that the amount of transactions its base blockchain can process is limited to about 7 transactions per second.

 

PoS Trade-Offs

 

Trust minimisation

Discontinuing PoW mining also incurs important tradeoffs in return for a drastic reduction in energy consumption, which under our current global electricity production stack, also means massively reduced carbon emissions. Broadly summarised, Ethereum will suffer reductions or elimination of censorship resistance, trust minimisation and decentralisation as a result of implementing PoS. It will also suffer a large increase in its attack surface due to its increased complexity of code. Hackers will have more exploits to seek for.

PoS reintroduces the requirement to trust other network participants when joining or re-joining the network. This is because staking is a quantity internal to the blockchain network. That is, you cannot know who has what stake unless you know which blockchain is the correct one. This means that before a user can validate whether the blockchain before them has been correctly executed, they must first trust someone else to tell them what the blockchain is in the first place.

This is a problem if a new user or a returning user is faced with a choice between multiple conflicting blockchains presented to him by a malicious actor. Since a PoS blockchain costs nothing to create, fake histories that are otherwise valid can be created and presented to outsiders en-masse by dishonest participants.

Work, on the other hand, is external to the system. This means that if two conflicting blockchains are presented to a new or returning user, they can trivially check for themselves which blockchain is the correct one simply by looking at the amount of accumulated work (the one with the most accumulated work is by definition the correct one). In a PoS system the only way to get around this is to introduce checkpoints, which again, require trusting other participants to tell you what the correct blockchain was at various times in the past. PoS therefore creates a need to trust other network participants through multiple new avenues, which it must trade-off against its benefits.

Censorship Resistance and Centralisation

PoS also trades-off its ability to resist censorship. Censorship Resistance, in this context and as defined in Cryptoeconomics by Voskuil, means the ability of the network to resist the actions of a network participant trying to prevent some or all transactions from being entered into the transaction record. The only effective way to do this is to control more than 51% of block producers—miners in a PoW system, stakers in a PoS system.

An entity controlling a majority of block production can simply refuse to enter some or all transactions into the blockchain, effectively censoring any or all parties.

In a PoW system, miners need to consume a resource external to the system and also require external capital (hardware). This can be procured without the majority miner knowing anything about it, meaning that there exists a mechanism by which a censor can lose its place as a majority miner.

In a PoS system, no such recourse exists within the protocol rules. As soon as an entity achieves a majority stake in the system they will perpetually increase their proportion of the total stake and nothing can force them to sell any of their stake meaning that their position is impossible to dislodge. The only way to recover from a situation like this is by recourse to a social consensus hard fork, which is just another way of saying centralised management by a select committee—which is by definition the opposite of decentralised.

PoS systems are also extremely complex compared to PoW systems, which vastly increases the attack surface of their networks. While the increased risks incurred by complexity are impossible to enumerate, any amount of increased complexity will cause an increase in risk, making it an important consideration to take into account.

In short, by implementing PoS and sharding, Ethereum trades off decentralisation, trust minimisation and censorship resistance. On top of that it will suffer from a much larger attack surface. In return it gets vastly increased on-chain data throughput (scalability), and drastically reduced energy consumption.

 

Recent Events Suggest Work Towards the Merge is Progressing

A major development step on the path towards the Merge was the launch of the Beacon Chain in December 2020. The Beacon Chain is an isolated PoS blockchain which, in the future, will act as the coordinator chain between all the Ethereum shards. It will act as Ethereum’s ‘consensus layer’, which is first designed to allow access to transaction data, and in a later version, to execute transactions themselves taking place on 64 planned separate shards.

There have been tests and practice merges, most recently on 23 April 2022, conducted to ensure the mainnet transition proceeds safely. The Kiln testnet merged on 15 March 2022 and incorporated the last major specification changes. Although many of these tests have been successful, others have raised concerns and probably contributed to the latest delay of the Merge from H1 2022 to H2 2022.

A list of concrete tasks to be completed before the Merge can take place can be found here. While the list still includes a large number of unfinished tasks, many are also completed.

 

Ethereum’s Future Post-Merge Is Determined by Users and Investors

Proof-of-Stake has been estimated to decrease energy consumption by over 99.5%. The requirements for which blocks are created, validated, ordered and added to the chain have shifted from an external resource to the network (energy) to an internal resource (capital). Sharding also has trade-offs in relation to decreased decentralisation while increasingd throughput.

Whether Ethereum’s trade offs are worth it is another question entirely. It is a question that rests heavily on subjective perceptions of the real-world risks likely to be faced by Ethereum in the future, and at the end of the day, is a question that can only be answered individually by Ethereum users and investors.

Whenever it happens, the Merge (probably this year) will represent a major shift in Ethereum design, capabilities and attributes. The Ethereum 2.0 moniker is therefore quite fitting—post the Merge Ethereum will be a completely different system. We look forward to this next phase of the Ethereum project and will keep our investors informed as the work progresses.

Publié leAvr 26th, 2022

Écrivain
CoinShares Author Logo
Max Shannon

Bienvenue to CoinShares

Données personnelles

0102

Lorsque vous consultez le site Internet de CoinShares, les cookies améliorent votre expérience en nous aidant à vous présenter un contenu plus pertinent. Certains cookies, nécessaires au fonctionnement du site, seront activés en permanence. Le refus de certains types de cookies peut avoir une incidence sur votre expérience de notre site Internet et sur les services qui y sont proposés.

Nous utilisons des cookies sur notre site pour optimiser nos services. En savoir plus sur notre politique de cookies pour l’UE ou notre politique de cookies pour les États-Unis.

  • Nécessaires
    Question circle icon
  • Preferences
    Question circle icon
  • Statistiques
    Question circle icon
  • Marketing
    Question circle icon
Les cookies nécessaires contribuent à rendre un site web utilisable en permettant des fonctions de base telles que la navigation sur les pages et l'accès aux zones sécurisées du site web. Le site web ne peut pas fonctionner correctement sans ces cookies.
Les cookies de préférence permettent à un site web de mémoriser des informations qui modifient le comportement ou l'apparence du site, comme votre langue préférée ou la région dans laquelle vous vous trouvez.
Les cookies statistiques aident les propriétaires de sites web à comprendre comment les visiteurs interagissent avec les sites web en collectant et en rapportant des informations de manière anonyme.
Les cookies marketing sont utilisés pour suivre les visiteurs sur les sites web. L'objectif est d'afficher des publicités pertinentes et attrayantes pour l'utilisateur individuel et donc plus intéressantes pour les éditeurs et les annonceurs tiers.