You are viewing a single comment's thread from:

RE: Proposal for an incremental Constitution and Dapp layer governance on EOS

in #eos6 years ago

Our versions of what's centralized and what's decentralized obviously differ greatly. Having more arbiters join ECAF won't make it more 'decentralized' if you think that, you're missing the point. More than the worry of corruption is the notion of having this body rule over us with powers (that can be ignored) to freeze accounts and reappropriate funds - thus having control over the immutability of the EOS blockchain. It's an oxymoron.

Sort:  

on the point of 'decentralisation' I just posted ECAF can be more decentralised than DPOS

thus having control over the immutability of the EOS blockchain.

ECAF doesn't have the power to control users' accounts, but BPs have. ECAF can only propose transactions which are finally made by BPs.

This doesn't have anything to do with "breaking immutability", because it's still preserved. All transactions are recorded in the blockchain and nothing is removed. The blockchain is immutable.

It's about multisig: BPs have the right to create any kind of transactions from any account, so basically all accounts in EOS blockchain are multisig accounts which are controlled by the account owner and BPs. If ECAF is removed from the constitution, users have more to fear because ECAF is supposed to an independent institution in this multisig scheme. Without ECAF, there is nobody to tell BPs what kind of multisig transactions they can make with the users' accounts.

In theory, ECAF could effect the immutability of the blockchain.

In theory, ECAF could effect the immutability of the blockchain depending on what precise point they intervened.

No, this is not possible even in theory. If the immutability of a blockchain is broken, there is some serious bug in the software.

This is how it should go: Transaction is recorded on the blockchain. A dispute arises considering that particular transaction. An arbitrator looks at the case and makes a ruling (which is recorded on the blockchain). A new transaction based on that ruling is proposed to the network. BPs check that the proposed transaction comes from a real arbitrator, etc. and accept it to the blockchain.

All transaction are recorded immutably on the blockchain: original disputed transaction, arbitrator's ruling, and enforcement of the ruling by BPs. Nothing is removed from the blockchain, only new transactions are added to it. Just like a blockchain is supposed to work.

This is semantics. My fault for not explaining fully in the above reply.
If an ECAF arbiter incorrectly rules on a case and orders the reappropriation of funds to another party, then it effectively interferes with the immutability of the blockchain. Yes, the blockchain code isn’t reversed in any way, but the outcome – the result the person who thought they had sent an immutable transaction in the first place - is being modified (by the arbiter) after being created, therefore the intended result becomes mutable.

My point is that talking about immutability of a blockchain in this kind of case doesn't make sense. The technical immutability is preserved, and on the level of token amounts the concept of immutability doesn't apply because everything is done by the rules.

If an account is a multisig account, like every account is in EOS, then everyone who has the keys to the account has an ability to do transactions.

So rather than speaking about "immutability", we should be speaking how to make the system fair, transparent, etc. so that all parties can trust it.

Coin Marketplace

STEEM 0.25
TRX 0.25
JST 0.040
BTC 94194.88
ETH 3392.03
USDT 1.00
SBD 3.50