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 Ethereum 2.0 FAQ

Ethereum 2.0 FAQ

Timer8 min läsning

  • Ethereum
  • Teknik

UPDATED 27 MAY 2022

What is Ethereum 2.0?

Ethereum 2.0, also called Eth2 or “The Beacon Chain”, is the next major change to the Ethereum blockchain, introducing a Proof-of-Stake consensus mechanism, moving the network away from its existing Proof-of-Work architecture.

How will Ethereum 2.0 affect CoinShares and XBT ETP holders?

We continue to monitor developments and timing while reviewing all possible options. The final announcement will be made via our website in due course.

Why can’t I earn staking from my CoinShares and XBT ETPs?

CoinShares is reviewing the staking mechanism, its operational complexity, the length of any lock-ups, and other associated risks. Once we have more clarity, we will make appropriate announcements on our website.

When will Ethereum 2.0 be launched?

The Beacon Chain updates will not take place at a single point in time; instead, they will roll out in several phases over the next few years. We have deliberately not specified dates for the various phases mentioned below as they remain uncertain.

  • October 12th 2020 = The Beacon Chain Staking Deposit Contract deployed.

  • November 4th 2020 = Version 1 publicly released.

  • November 24th 2020 = The Beacon Chain Staking Deposit Contract reached its necessary trigger limit of 524,288 ETH (16384 deposits of 32 staked ETH).

  • December 1st 2020 = Beacon Chain launched seven days after the threshold was met.

  • October 27th 2021 = The first Beacon Chain upgrade enabled “light clients”, brought validator inactivity and ‘slashing’ penalties up to their full values.

  • October 27th 2021 – current date = multiple successful practice Merges and test-net forks.

  • May 2022 = as of writing, the difficulty bomb has been detonated. This eventually makes the Proof-of-Work chain redundant by making it almost impossible for miners to mine the blocks. Whether it gets delayed for the 6th time, or not, is still in question. But consensus seems to be that the Merge will occur in H2 2022.

What are the phases of Ethereum 2.0?

Ethereum 2.0 is launching in several phases: Phase 0 (The Beacon Chain), Phase 1 (The Merge) and Phase 2 (Shard Chains), (Phase 2.5 - State Execution). The first phase, Phase 0, otherwise known as The Beacon Chain, launched on December 1st 2020. According to the Ethereum Foundation, the next two phases (i.e. Phase 1 and Phase 2) will be released in the following few years after Phase 0. These dates are not yet set. Although, Ethereum’s test-net (a public, beta blockchain used for testing upgrades and decentralised applications), Kiln, upgraded to Proof-of-Stake under a ‘practice Merge’. It is expected to be the last merge test net created before existing public test nets are upgraded. There have also been successful shadow forks which reduce The Merge’s execution risk and flush out any problems that may arise.

Phase 0: the Beacon Chain

The first phase of Ethereum 2.0 is the launch of the Beacon Chain. The Beacon Chain stores and manages the registry of validators and deployed the Proof-of-Stake consensus mechanism. The original Ethereum Proof-of-Work chain will run alongside this, ensuring that there is no break in data continuity.

The launch of the Beacon Chain marked Phase 0. After the Beacon Chain is launched, the Ethereum 1.0 and 2.0 chains will exist in parallel for some time. Ethereum 1.0 will eventually become a shard in the Ethereum 2.0 system, merging the two chains.

Phase 1: The Merge

This phase represents the moment when Ethereum 1.0 merges with Ethereum 2.0. Specifically, the Ethereum 1.0 chain will become one of the shards that make up Ethereum 2.0. This is to ensure that the entire data history will be preserved.

Phase 1.5 - Rollups

This phase is the centre-piece of Ethereum’s long term roadmap, and is another type of scaling mechanism. This is a layer 2 technology that executes transactions off-chain and then submits those transactions on-chain, in order to be validated by the rest of the nodes. This reduces the data needed for a transaction and, in turn, reduces the costs associated with executing such a transaction.

Phase 2: Shard Chains

The next phase includes the implementation of shard chains. Proof-of-Stake is not technically needed but improves the security of shard chains above that of the implementation on top of Proof-of-Work. Shard chains are a scalability mechanism that is designed to spread the data into chunks across the network, making it easier to access. The first version of Shards will only provide data to the Beacon Chain and will not execute transactions or smart contracts. This may come in the second version, but it is not finalised or clear.

What is the difference between Ethereum 1.0 and Ethereum 2.0?

The overall goal of Ethereum 2.0 update is to increase the performance of the network. To achieve this, Ethereum 2.0 introduces:

  • The transition to Proof-of-Stake; and

  • Provide the foundations of Shard Chains

Proof-of-Stake is the most significant change in Ethereum 2.0 as it will completely change the economic incentive structure for validating the blockchain. Currently, Ethereum 1.0 runs on a fully trustless consensus mechanism known as Proof-of-Work. Proof-of-Stake hopes to retain Proof-of-Works’s existing benefits while avoiding its main issues – energy consumption. If successful, it would shift the cost of validating the blockchain from energy to total ETH stake. One of its main trade-offs is a change away from the trustless auditing model of Proof-of-Work to the Proof-of-Stake model whereby new entrants must trust some subset of existing network participants to tell them which blockchain is the correct one. The benefit would be a drastically reduced energy expenditure for the whole system.

Shard Chains are separate blockchains that sit within Ethereum and take on a portion of the network's processing work, hence improving its scalability. At present, all nodes (i.e. computers) in the Ethereum network must download, compute, store and read every transaction in the history of Ethereum before processing a new one. In Ethereum 2.0, nodes will be dispersed across a subset of shards. They'll only need to download, compute, store, and read every transaction on that shard – not the whole network. The number of validators on each shard would be limited to whichever validators care for whichever shard.

How will Ethereum 2.0 affect the current Ethereum 1.0 chain?

The current plan is for the Ethereum 1.0 chain to effectively become the first shard on Ethereum 2.0 when Phase 1 takes place. Until then, the Ethereum 1.0 chain will continue as it is now and will undergo improvements to enable it to eventually be an Ethereum 2.0 shard.

How will Ethereum 2.0 affect ETH holders?

ETH holders will not be affected and can continue using their ETH just as they were before. During Phase 1.5, Ethereum 1.0 will become one of the shards that make up Ethereum 2.0. In other words, the ETH holders who are interested only in holding, trading, or using their ETH on Decentralised Applications (DApps) do not have to actively do anything to prepare for Ethereum 2.0.

Can I “buy” Ethereum 2.0 ether?

There will not be a new type of ETH token. For more information, please refer to the FAQ on the Ethereum Foundation website.

What are some main risks of Ethereum 2.0?

A main risk of Ethereum 2.0 is that Proof-of-Stake does not work as hoped. Unlike Proof-of-Work, Proof-of-Stake has not yet been proven to work at significant scale and its vastly increased complexity compared to Proof-of-Work creates a much larger surface area for unintended behaviour (bugs) and attacks.

Proof-of-Stake also has the potential to centralise the holding of ether in the hands of whoever are the currently largest holders. Because Proof-of-Stake rewards validators based on stake held, not work performed, there could emerge a plutocratic tendency in ether distribution whereby current large holders perpetually retain their proportions of ether holdings at the dilution expense of everybody else.

Another major risk is that these code changes are being done on a currently live system, potentially imperilling currently functioning dApps and smart contracts. While this should not be an immediate issue of Phase 0, it will resurface when the Ethereum 1.0 and 2.0 chains must at some point become fully integrated. Although this upgrade has been researched for years and has passed test-net upgrades and implementations such as the most recent one on Kiln, March 15th 2022. This risk is reduced through the difficulty bomb which increases the hash rate high enough to incentivise miners to vote for the hard fork and switch to another chain to circumvent the high fees.

Sources:

  1. https://blog.ethereum.org/2015/07/22/frontier-is-c...

  2. https://ethereum.org/roadmap/

  3. https://consensys.io/blog

  4. https://www.researchgate.net/publication/331148019...

  5. Vitalik Buterin, "Overview of Ethereum 2.0" - Youtube

  6. https://www.kraken.com/gb/learn/proof-of-work-vs-proof-of-stake

  7. https://medium.com/interdax/ethereum-2-0-explainer-e996ac7dc006

Publicerad denMaj 27th, 2022

Författare
Har lett Bitcoin Research sedan 2017.

Välkommen till CoinShares

Personuppgifter

0102

Vi använder cookies för att anpassa innehåll och annonser, för att tillhandahålla funktioner för sociala medier och för att analysera vår trafik. Vi delar också information om din användning av vår webbplats med våra sociala medier, annonserings- och analyspartners som kan kombinera den med annan information som du har lämnat till dem eller som de har samlat in från din användning av deras tjänster. När du accepterar användningen av cookies samtycker du till behandlingen av dem enligt beskrivningen i integritetspolicyn och cookiepolicyn.

 

Vi använder cookies på vår webbplats för att optimera vära tjänster. Läs mer om vår cookiepolicy för EU eller vår cookiepolicy för USA.

  • Nödvändiga
    Question circle icon
  • Preferences
    Question circle icon
  • Statistik
    Question circle icon
  • Marknadsföring
    Question circle icon
Cookies förbättrar din upplevelse när du besöker CoinShares webbplats. De hjälper oss att visa mer relevant innehåll för dig. Vissa cookies är nödvändiga för att webbplatsen ska fungera och dessa kommer alltid att vara aktiverade. Om du blockerar vissa typer av cookies kan det påverka din upplevelse av vår webbplats och de tjänster som vi erbjuder på webbplatsen.
Preferenscookies gör det möjligt för en webbplats att komma ihåg information som ändrar hur webbplatsen beter sig eller ser ut, t.ex. vilket språk du föredrar eller vilken region du befinner dig i.
Statistiska cookies hjälper webbplatsägare att förstå hur besökare interagerar med webbplatser genom att samla in och rapportera information anonymt.
Marknadsföringscookies används för att spåra besökare på olika webbplatser. Avsikten är att visa annonser som är relevanta och engagerande för den enskilda användaren och därmed mer värdefulla för utgivare och tredjepartsannonsörer.