Bitcoin Forum
May 07, 2024, 01:02:25 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: EOS Block Producers Violate Constitution, Freeze 7 Suspect Accounts  (Read 98 times)
MatyasZaborszkyScam (OP)
Jr. Member
*
Offline Offline

Activity: 42
Merit: 6

John -ICO and Cryptocurrency Expert investigation


View Profile
June 20, 2018, 07:36:20 AM
 #1

In violation of the rules of the EOS constitution, the project’s 21 block producers have frozen seven accounts suspected to be compromised.

The move was made in line with the EOS911 Initiative — a new security protocol designed to recover stolen funds and return them to the victims of phishing attacks.

Knowingly violating rules of the EOS constitution, the block producers are facing criticism for acting beyond their authority. As per the constitution, such action can only be authorized by the blockchain’s arbitration bodies — EOS block producers may only execute their decisions.

Article III of the constitution outlines the breach in question:

Quote
-# Article III – Rights -The Members grant the right of contract and of private property to each other, therefore no property shall change hands except with the consent of the owner, by a valid Arbitrator’s order, or via community referendum.

Why did they do it?

Put forth by leading block producer EOS42, EOS911 was a hurried initiative to safeguard a number of token holders that were robbed of their private keys. While funds were offered momentary protection by the inactive EOS blockchain — as soon as the mainnet’s 72-hour staking period ended, all affected wallets were vulnerable.

EOS block producers (BPs) pleaded their case to EOS Core Arbitration Forum representatives — effectively the blockchain’s law enforcement agency. Waiting for a green light from the arbiters, the BPs received a preliminary notice from ECAF warning the freezing of accounts would soon be sanctioned.

Although, all did not unfold as expected. Pointing to the current interim constitution, ECAF’s ruling of inaction meant EOS BPs did not, in fact, have permission. However, this was not enough to deter BPs who swiftly froze the 7 accounts, explaining:

Quote
“EOS New York chose to enact this freeze because we believed that we were following the spirit of the governance system we as a community seek to create, despite it being formally absent. EOS is a platform meant to enable solutions which protect life, liberty, and property and that’s what we believed we were doing through this emergency action.”

Response to the move has been mixed.

Quote
Amongst proponents of decentralization, the collusion of the block producers has typically been met with disdain. Charlie Shrem, tweeted:

If crypto mass adoption involves someone having the power to control, freeze or reverse a transaction.

If it involves someone having the power to edit or reverse data on the chain.

If it involves losing immutability.

Then crypto mass adoption is not worth having. https://t.co/RRHuZKattE

— Charlie Shrem (@CharlieShrem) June 19, 2018

In favor of EOS, many have been quick to defend the actions, pointing to the BPs’ protection of legitimate account holders. EOS Nation — a public community of EOS advocates stepped in to explain the move:

Quote
Why the #BlockProducers proceeded with the accounts freeze?

Yves, from @EOS_Nation, give us the reason why the #BlockProducers acted this way, and why a #GovernedBlockchain is so important for the ecosystem.@TBCox @eosnewyork @EOS_Canada @cannon_eos https://t.co/vjxOTXhROM

— EOS Nation (@EOS_Nation) June 19, 2018

Just days after the stalled launch of its mainnet, the violation comes as the latest sting in a stream of controversies faced by EOS — including one Cornell professor’s prediction of a “massive exchange hack” brought about by a vulnerability in the blockchain’s code.


John - Team Leader of ICO and Cryptocurrency Expert investigation -
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!