create account

Ethereum merge; technical risk involved what to do by mccoy02

View this thread on: hive.blogpeakd.comecency.com
· @mccoy02 ·
$2.02
Ethereum merge; technical risk involved what to do
<div class="text-justify">



In full anticipation of the upcoming ethereum merge, there are speculations on what might likely transpire during/after the merge one of the technical risk involved is called [replay attack](https://leofinance.io/@leoglossary/leoglossary-replay-attack) where duplicated tokens, NFTs from Proof of Work will be copied to Proof of Stake during this transition bad actors will try to manipulate the blockchain by faking duplicate transactions to look real and luring users into selling off their assets in an attempt of stealing the real assets, which is a typical example of [double spending problem](https://leofinance.io/@leoglossary/leoglossary-double-spend-problem) on the blockchain, this kind of attack is feared might affect a lot of uninformed users into selling their real assets.

Ethereum core developer Terence Tsao, states such attack problems are well taken care of and ask users to stick to this little advice.....

>**My only advice is to do nothing** 
[source](https://decrypt.co/108791/ethereum-merge-almost-here-what-could-go-wrong)

![images (1).jpeg](https://images.hive.blog/DQmQ2pEcsx5S5RLGRQ1aKd1fuQWj1QKvNZVHhkCR5AukxAq/images%20(1).jpeg)

[Source](https://www.google.com/search?q=ethereum+merge&client=ms-android-transsion-tecno-rev1&prmd=nvi&sxsrf=ALiCzsYs0ZljcLX8FSnkRb3y9taj4HgSlw:1662195826959&source=lnms&tbm=isch&sa=X&ved=2ahUKEwiAlMD-ofj5AhXlgP0HHVySDC4Q_AUoA3oECAIQAw&biw=360&bih=660&dpr=2#imgrc=aRCjR5KWEJFJUM&imgdii=bJ0x48969YJmhM)

### **Historical twelve minutes** 

The merger which is due to happen between September 10th-20th will take about 12 minutes, to complete, during these historical last minutes hackers will be on the verge of attacking the blockchain with multiple bugs in an attempt to divert funds, exchanges like coinbase, binance, and more will be halting all ethereum based transactions during the migration process, to mitigate malicious users from taking advantage of the transition process. Van Der Wijden assured users that 150 ethereum developers will be on watch to fix any bug during the last twelve minutes there is no cause for panic, things will go smoothly without any hiccups.


What to do within these twelve minutes is to **do nothing** and allow the ethereum team to do all the work, as mentioned above those with little information about the merge might likely fall victim to bad actors, the long-anticipated merge is around the corner, and it's happening soon will it be a success? will all depends on a few days from now.

*What are your thoughts on the upcoming merge do you think there will be high risk involved?*



</div>
👍  , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , and 13 others
properties (23)
authormccoy02
permlinkethereum-merge-technical-risk-involved-what-to-do
categoryhive-167922
json_metadata{"tags":["leofinance","proofofbrain","merge","ethereum","piotr","risk"],"image":["https://images.hive.blog/DQmQ2pEcsx5S5RLGRQ1aKd1fuQWj1QKvNZVHhkCR5AukxAq/images%20(1).jpeg"],"links":["https://leofinance.io/@leoglossary/leoglossary-replay-attack"],"app":"hiveblog/0.1","format":"markdown"}
created2022-09-03 09:20:24
last_update2022-09-03 09:20:24
depth0
children3
last_payout2022-09-10 09:20:24
cashout_time1969-12-31 23:59:59
total_payout_value1.020 HBD
curator_payout_value1.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length2,628
author_reputation103,634,331,916,904
root_title"Ethereum merge; technical risk involved what to do"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id116,277,378
net_rshares2,979,818,935,137
author_curate_reward""
vote details (77)
@alaiza ·
Every risk has its consequences, as for thoughts on the upcoming ETH merger, I think everything will be fine and we will quickly enter normalcy. Thank you @mccoy02 for sharing this content.
properties (22)
authoralaiza
permlinkre-mccoy02-202293t162553270z
categoryhive-167922
json_metadata{"tags":["leofinance","proofofbrain","merge","ethereum","piotr","risk"],"app":"ecency/3.0.26-vision","format":"markdown+html"}
created2022-09-03 20:25:54
last_update2022-09-03 20:25:54
depth1
children1
last_payout2022-09-10 20:25:54
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length189
author_reputation86,979,432,073,694
root_title"Ethereum merge; technical risk involved what to do"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id116,291,294
net_rshares0
@mccoy02 ·
Everything have been put in place to make this merge a success there is no much need to be on alarm ethereum team have a group of best developers am sure they will deliver thanks for your time.
properties (22)
authormccoy02
permlinkrhnnci
categoryhive-167922
json_metadata{"app":"hiveblog/0.1"}
created2022-09-03 22:19:39
last_update2022-09-03 22:19:39
depth2
children0
last_payout2022-09-10 22:19:39
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length193
author_reputation103,634,331,916,904
root_title"Ethereum merge; technical risk involved what to do"
beneficiaries
0.
accounthiveonboard
weight100
1.
accountleofinance
weight300
2.
accounttipu
weight100
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id116,293,530
net_rshares0
@hivebuzz ·
Congratulations @mccoy02! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s):

<table><tr><td><img src="https://images.hive.blog/60x70/http://hivebuzz.me/@mccoy02/upvotes.png?202209050259"></td><td>You distributed more than 16000 upvotes.<br>Your next target is to reach 17000 upvotes.</td></tr>
</table>

<sub>_You can view your badges on [your board](https://hivebuzz.me/@mccoy02) and compare yourself to others in the [Ranking](https://hivebuzz.me/ranking)_</sub>
<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>



**Check out the last post from @hivebuzz:**
<table><tr><td><a href="/hive-122221/@hivebuzz/pum-202208-delegations"><img src="https://images.hive.blog/64x128/https://i.imgur.com/fg8QnBc.png"></a></td><td><a href="/hive-122221/@hivebuzz/pum-202208-delegations">Our Hive Power Delegations to the August PUM Winners </a></td></tr><tr><td><a href="/hive-122221/@hivebuzz/pud-202209-feedback"><img src="https://images.hive.blog/64x128/https://i.imgur.com/zHjYI1k.jpg"></a></td><td><a href="/hive-122221/@hivebuzz/pud-202209-feedback">Feedback from the September 1st Hive Power Up Day</a></td></tr><tr><td><a href="/hive-122221/@hivebuzz/pum-202208-result"><img src="https://images.hive.blog/64x128/https://i.imgur.com/mzwqdSL.png"></a></td><td><a href="/hive-122221/@hivebuzz/pum-202208-result">Hive Power Up Month Challenge 2022-08 - Winners List</a></td></tr></table>

###### Support the HiveBuzz project. [Vote](https://hivesigner.com/sign/update_proposal_votes?proposal_ids=%5B%22199%22%5D&approve=true) for [our proposal](https://peakd.com/me/proposals/199)!
properties (22)
authorhivebuzz
permlinknotify-mccoy02-20220905t032254
categoryhive-167922
json_metadata{"image":["http://hivebuzz.me/notify.t6.png"]}
created2022-09-05 03:22:54
last_update2022-09-05 03:22:54
depth1
children0
last_payout2022-09-12 03:22:54
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1,689
author_reputation369,201,087,004,281
root_title"Ethereum merge; technical risk involved what to do"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id116,328,003
net_rshares0