馃攳
ETHEREUM MERGE - The Most Anticipated Event In Crypto Explained - YouTube
Channel: Finematics
[0]
the ethereum merge despite being one of
[1]
the most significant blockchain upgrades
[3]
in the history of cryptocurrency is
[5]
still a poorly understood topic so what
[7]
is the theory merge what are its
[9]
economic implications and what are the
[11]
main merge risks and misconceptions
[13]
you'll find answers to these questions
[15]
and more in this video before we begin
[18]
if you want to learn more about
[19]
decentralized finance and the technology
[21]
behind it make sure you subscribe to my
[23]
channel hit the bell icon and enable all
[25]
notifications
[27]
let's start with understanding the
[28]
motivations behind the merge
[30]
the main purpose of the merge is to
[32]
transition ethereum from its current
[34]
proof of work consensus mechanism to the
[36]
proof of stake model in short in the
[39]
proof of work or pow model the network
[42]
is secured by miners who have to
[44]
purchase and run the mining hardware in
[46]
this model the miners consume
[48]
electricity in exchange for block
[50]
issuance and a portion of transaction
[52]
fees in the proof of stake or pos model
[55]
the network is secured by validators who
[58]
have to stake eth in order to validate
[60]
the network in this model the validators
[63]
don't consume much electricity
[66]
the transition to pos aims at making
[67]
ethereum more energy efficient more
[70]
secure and lays the groundwork for
[71]
enabling more scalability with sharding
[74]
later on
[75]
the move to pos was one of the big
[76]
milestones in the original ethereum
[78]
roadmap and research began before the
[81]
ethereum network launched
[82]
instead of transitioning ethereum to pos
[85]
in one huge and potentially dangerous
[87]
change the ethereum researchers and
[89]
developers decided to split it into two
[92]
steps
[93]
the first step launching the beacon
[95]
chain was successfully executed in
[97]
december 2020 this allowed for creating
[100]
a separate parallel pos chain that could
[102]
be tested in production for a period of
[104]
time without having any direct impact on
[108]
the already existing pow network that
[110]
secures hundreds of billions of dollars
[113]
of economic activity another important
[116]
reason for launching the beacon chain
[117]
earlier was to give enough time to
[119]
stakers so the amount of staked heath
[122]
can be sufficiently large to secure the
[124]
network at the time of the merge
[127]
when making this video the beacon chain
[128]
had over 400 thousand validators and
[131]
over 13 million it actively staking the
[134]
merge is the second step in the
[136]
transition to pos which merges the
[138]
consensus layer of the beacon chain with
[140]
the evm state of the ethereum pow chain
[143]
more on this later in the video
[145]
the transition to pos aims at reducing
[148]
the power consumption to secure ethereum
[150]
by around 99.95
[153]
this in turn brings down a lot of
[155]
arguments about ethereum defy and nfts
[158]
killing the planet
[160]
as a byproduct it also makes ethereum
[162]
esg compliant which can be good for more
[164]
regulatory driven institutions that may
[166]
want to start exploring the ethereum
[168]
ecosystem this can also make ethereum
[171]
more friendly to gamers and nft artists
[174]
concerned about the environmental impact
[176]
of crypto
[177]
another motivation for completing the
[179]
merge is the reduction in the eth
[181]
issuance as the security of the pow and
[184]
pos chains is funded by eth issuance
[188]
after the merge the pow network will
[190]
cease to exist which will dramatically
[193]
reduce its issuance
[195]
this was named triple halvings as the
[197]
issuance drop is similar to three
[199]
bitcoin insurance housings
[201]
on top of all of this another argument
[203]
for the merge and the transition to pos
[205]
is that ethereum enthusiasts will be
[207]
able to secure ethereum from home being
[210]
a consensus participant will no longer
[212]
mainly be for institutions and
[214]
sophisticated miners
[215]
this should further decentralize the
[217]
network and make it even more resistant
[219]
to attacks
[220]
now that we know the motivations behind
[222]
the merge time to dive a bit deeper into
[224]
the mechanics of this upgrade
[227]
let's start with a quick analogy imaging
[229]
ethereum as a car driving on the
[231]
motorway the merge aims at transitioning
[234]
the car's engine from gas to electric a
[237]
key difficulty is to do so without
[239]
stopping the car to achieve this the
[241]
ethereum developers built a separate
[243]
electric engine and have tested it with
[246]
real stake for over one and a half years
[249]
this new electric engine runs in
[251]
parallel to the existing gas engine
[254]
at the time of the merge the car will
[256]
switch to using the electric engine and
[258]
will stop using its current gas-fueled
[260]
motor
[261]
doing it in this way first of all allows
[263]
for testing the electric engine in
[265]
parallel the second benefit is that we
[267]
can swap the engines without stopping
[269]
the car
[270]
in the case of ethereum stopping the car
[272]
would mean holding the block production
[274]
which would result in no new
[276]
transactions being appended to the
[277]
blockchain as we can imagine this would
[279]
be very disruptive especially for defy
[282]
so ethereum developers try to avoid it
[284]
at all costs
[285]
i hope this analogy helps visualizing
[287]
the merge here's a bit more technical
[289]
explanation of this upgrade
[291]
the merge is responsible for merging the
[293]
user state of the ethereum network with
[296]
the pos beacon chain at the moment
[298]
before the transition to pos in order to
[301]
validate the ethereum network the node
[303]
operators run one of the existing client
[305]
implementations such as geth arrogan or
[308]
nethermind these client implementations
[311]
bundle the execution layer evm and the
[314]
consensus layer pow in order to
[317]
transition the ethereum network to the
[318]
pos model smoothly the execution and
[321]
consensus layers are unbundled this
[324]
means that both of these layers can be
[325]
run separately
[327]
they can also be developed by completely
[329]
different teams specializing in one of
[331]
the layers
[332]
after the merge a full node will consist
[334]
of an execution node and a consensus
[336]
node
[337]
there's also an engine api responsible
[339]
for the communication between the
[341]
execution and consensus node
[343]
decoupling the consensus and execution
[345]
layers allowed for a quicker initial
[347]
launch of the beacon chain without
[348]
having to worry about the execution
[350]
layer
[351]
when it comes to consensus layers the
[353]
most popular implementations at the
[355]
moment are prism lighthouse and taku the
[358]
existing client implementations will
[360]
transition to being execution layer
[362]
clients and will work with the consensus
[365]
layer clients to form a full ethereum
[367]
node
[368]
with multiple client implementations on
[370]
both layers there are multiple different
[372]
combinations of execution and consensus
[375]
clients for example one validator may
[377]
prefer to run prism with geth another
[380]
may prefer to run lighthouse with
[381]
nethermind with four popular execution
[384]
clients and five consensus clients there
[386]
are 20 pairwise combinations
[389]
at the time of the merge execution
[390]
clients like get will start listening to
[392]
blocks coming from the pos chain
[395]
the trigger for this switch will be
[396]
determined by a new variable called
[398]
terminal total difficulty which
[400]
represents the sum of the proof-of-work
[402]
difficulties of every block accumulated
[404]
on the ethereum pow network when the
[407]
chain accumulates enough proof of work
[408]
to exceed the terminal total difficulty
[411]
nodes switch to following the canonical
[413]
pos chain
[415]
it's interesting to notice that for the
[416]
first time an ethereum upgrade will be
[418]
triggered using total difficulty instead
[421]
of the usual block height this is to
[423]
avoid an attacker mining low difficulty
[425]
malicious forks that would satisfy the
[427]
block height requirements at the time of
[429]
the merge and cause confusion on the
[431]
final pow block
[433]
after the merge all applications running
[435]
on ethereum should run exactly as
[437]
pre-merged with the state and
[438]
transaction history maintained this
[441]
means that for example if we were a
[443]
liquidity provider on uni swap before
[445]
the merge after the merge the state will
[447]
be the same hence we will still be
[449]
providing liquidity on uni swap if we
[452]
had an open loan on the other this loan
[454]
will still be in place and users
[456]
shouldn't notice any changes
[458]
the transition has been going through
[459]
multiple intensive rounds of testing
[462]
that include merging shadow forks and
[464]
merging test nets shadow forks are
[466]
copies of an existing ethereum network
[468]
merging them helps catch potential
[470]
issues related to the current state of
[471]
the network these works are usually
[473]
abandoned after testing and the purpose
[475]
is to expose any potential problems
[478]
unlike most shadow forks merged test
[480]
nets usually persist as pos networks
[483]
this helps developers with testing their
[485]
applications on a chain that resembles
[487]
ethereum post merge
[489]
after robsten and sepolia the last and
[491]
most used long-lived test net to merge
[493]
is girly after this is successfully
[496]
executed we can expect the announcement
[498]
of the mainnet merge now let's discuss
[500]
one of the interesting topics which was
[502]
to a certain extent responsible for
[504]
postponing the merge which is client
[507]
diversity
[508]
ethereum in contrast to a lot of other
[510]
platforms doesn't rely on a single
[512]
client implementation in fact there are
[514]
currently four mainstream
[515]
implementations get nethermine arrigon
[519]
and basu
[520]
having multiple implementations allows
[522]
for quickly switching to a different
[523]
working client in case a bug is found in
[526]
the software you are running
[528]
this makes ethereum more resilient to
[530]
attacks as even a bug or an intentional
[532]
exploit introduced by one of the clients
[535]
would have limited consequences
[537]
after the merge client diversity plays
[539]
an even bigger role
[541]
this is because a bug introduced in the
[543]
pos network can have different
[544]
consequences depending on the staking
[547]
share it affects
[548]
let's start with the worst situation if
[550]
the problem affects 2 3 or more of the
[553]
stake this can result in finalizing a
[555]
bad state route not something we want
[558]
ever to happen
[559]
if the problem affects half or more of
[561]
the clients this can result in the
[563]
creation of a dominant and valid chain
[566]
that won't get finalized but will be
[568]
reverted better than two-thirds or more
[570]
but still pretty bad
[572]
finally if the problem affects at least
[574]
one-third of clients no new transactions
[576]
on the network would get finalized now
[579]
knowing these potential outcomes we can
[580]
understand better why client diversity
[583]
is so important
[584]
let's assume that 70 of the consensus
[587]
clients are running prism as their go-to
[589]
solution
[590]
in case there is a bug found in this
[592]
implementation the network instantly
[594]
suffers the worst scenario with more
[596]
than two-thirds of the clients being
[598]
affected and ethereum is prone to
[600]
finalizing a bad state now if prism has
[603]
40 of the network and a similar bug is
[606]
found the ethereum network would stop
[608]
finalizing until either the bug is fixed
[610]
or different backup clients are spun up
[613]
so the network share of prism goes under
[615]
one third
[616]
at the time of making this video prism's
[618]
market share is at around 40 of the
[620]
consensus clients this is a huge
[622]
improvement from around 70 percent in
[624]
early 2022 and will boost network
[627]
resilience
[628]
now let's discuss some important
[630]
implications of the merge
[632]
first of all the block time will not be
[633]
the same as on the existing pow chain
[636]
the block time on pow is usually quoted
[638]
as averaging around 13 seconds after the
[642]
merge time is divided into fixed
[643]
duration slots of 12 seconds some slots
[646]
can miss a block so the average block
[648]
time will almost certainly be higher
[650]
than 12 seconds though it should be
[652]
lower than 13 seconds
[654]
secondly the merge will also reduce the
[656]
block time variance and on average we
[658]
can expect faster transaction
[659]
confirmations
[661]
the merge will also make the distinction
[663]
between bitcoin and ethereum even
[664]
clearer bitcoin will remain the battle
[667]
tested proof-of-work network while
[669]
ethereum will be fueled by the fairly
[670]
new proof-of-stake energy-efficient
[672]
mechanism another important implication
[675]
is that it will be harder to attack the
[677]
network because of the higher economic
[679]
security and the power to slash
[681]
attackers and also good news for gamers
[684]
the gpu market will be most likely
[686]
flooded with millions of graphic cards
[688]
as mining will no longer be needed
[690]
the merge will also most likely decrease
[692]
the heat supply over time and spike more
[695]
media interest as a deflationary asset
[698]
also another important implication in
[700]
total there are around 100 people
[702]
working on the merge after the merge
[704]
these people can start working on other
[706]
improvements such as sharding
[708]
there are also a few big misconceptions
[710]
about the merge
[712]
first of all the merge does not improve
[713]
ethereum scalability and it doesn't
[715]
reduce transaction fees at least not
[717]
directly the previously mentioned minor
[720]
reduction in block time can result in a
[722]
small increase in throughput but what is
[724]
the most important is that the merge and
[726]
the transition to pos lay the groundwork
[729]
for further scalability improvements
[731]
that will be delivered in the subsequent
[733]
network upgrades
[734]
secondly the merge doesn't enable
[736]
withdrawals of eth from the validators
[738]
straight away this will be enabled in
[740]
one of the next hard forks after the
[742]
merge
[743]
it's worth mentioning that transaction
[745]
fees collected after the merge have
[746]
their own recipient ether address on the
[749]
evm so it accumulated from the
[751]
transaction fees will be immediately
[753]
available also as we know from the
[755]
previous section ethereum doesn't have
[757]
to stop to enable the transition this is
[759]
yet another common misconception
[761]
another common misconception is that
[763]
there will be another e token on the
[765]
beacon chain or for the ethereum 2.0
[768]
the last misconception worth mentioning
[771]
is that each supply will keep decreasing
[772]
and trends towards zero this is also
[775]
incorrect as the eighth supply will find
[777]
an equilibrium based on the network
[779]
demand specifically the heath burn rate
[781]
from transaction fees and the eth
[783]
issuance this equilibrium can be
[785]
established on different levels and
[787]
change over time but it will never reach
[790]
zero the current estimates predict the
[792]
heat supply to pick around 120 million
[795]
eath at the merge and find a long-term
[797]
equilibrium anywhere between 60 million
[799]
to 100 million each in a few decades
[802]
hopefully this clears up some of these
[804]
common misconceptions
[805]
the merge like any other complicated
[807]
technology upgrade doesn't come without
[810]
any risks here are some potential risks
[812]
that are worth keeping in mind most of
[814]
them are related to the transition to
[815]
pos rather than the merge itself but
[818]
they are still worth mentioning
[820]
after the merge validators proposing the
[822]
next block will be known ahead of time
[824]
as part of the public selection process
[826]
this makes proposals vulnerable to
[828]
networking denial of service attacks
[830]
as an example if the attacker knows they
[832]
are one of the next proposals in line
[835]
they can try to dos the current
[836]
proposers causing them to lose their
[838]
slot and not include any high value
[841]
transactions that now can be picked up
[843]
by the attacker the most popular
[845]
solution to this problem at the moment
[847]
is a single secret leader election that
[850]
uses clever cryptography to prevent the
[852]
attacker from knowing who the next
[853]
proposer is while still providing this
[856]
information to the actual proposer
[858]
there are also centralization risks that
[860]
come with the concentration of stake in
[862]
pools such as lido and coinbase this can
[865]
lead to attacks such as censorship or
[868]
extortion
[869]
in the case of lidar there is also
[871]
governance takeover risk and smart
[873]
contract risk one of the interesting
[875]
solutions suggested by the lido
[877]
community was to allow people who
[878]
deposit their eath to liza and receive
[881]
st eth to veto any potential dangerous
[884]
proposals
[885]
it's great to see the ethereum community
[887]
anticipating a lot of potential risks
[889]
associated with the merge and the
[891]
transition to pos and already finding
[894]
some potential solutions
[895]
these solutions even if not implemented
[897]
straight away can be added to the
[899]
network in one of the following hard
[901]
works making it more resilient in the
[903]
future
[904]
the ethereum merges clearly one of the
[906]
biggest and most anticipated upgrades in
[908]
the history of the cryptocurrency space
[911]
when it comes to the date of the merge
[912]
at the moment most people predict it to
[914]
happen around september 2022 this should
[917]
be possible if there are no major issues
[919]
founded during the girly test net merge
[922]
despite a few potential risks the
[923]
researchers and developers have been
[925]
spending countless hours making sure
[927]
there are no surprises during the
[929]
maintenance merge
[930]
after the merge ethereum will become
[932]
more secure and sustainable it will also
[934]
be perfectly positioned for the next big
[937]
upgrades the search the verge the purge
[940]
and the splurge we will learn more about
[942]
this in the following videos but it's
[944]
worth mentioning that all of these
[945]
subsequent phases can be worked on in
[948]
parallel so what do you think they'll
[950]
emerge and what are other topics that
[952]
you're interested in at the moment
[953]
comment down below and as always if you
[956]
enjoyed this video smash the like button
[958]
subscribe to my channel and check out
[960]
cinematics on patreon to join our
[962]
community of defy enthusiasts
[964]
thanks for watching
[968]
you
Most Recent Videos:
You can go back to the homepage right here: Homepage





