RE: EOS User Agreement v3.0 by samupaha

View this thread on steempeak.com

Viewing a response to: @eosvibes/eos-user-agreement-v3-0

· @samupaha ·
Really nice to see that you are moving to the right direction with your thinking! But there was still a little bit of misunderstanding in your proposal.

> I like that they have removed the EOS Core Arbitration Forum (ECAF) as the sole centralized arbitrator and replaced them with a free market arbitration system.

They didn't replace ECAF with another system, they removed base-layer arbitration completely and created the official way to use app-level arbitration. These are two completely different things. Base-layer arbitration means the arbitration of constitutional disputes. With EOS NY's proposal, this would be in the hands of BPs.

I see it as a step backwards. When the stakes are high, it's usually a good idea to decentralize the system and create several independent institutions to run the system. In this case, the model EOS uses resembles what countries are doing (at least some of them). They separate different powers: legislative (in EOS, voters through referendums), executive (BPs), and judicial (ECAF). With EOS NY's proposal, ECAF will be removed and its powers are given to BPs.

> ECAF was conceived as an arbitration forum, yet it oversteps the remit for what arbitration is and as yet, ECAF has not declared or clearly defined a scope for its organisation.

I'm not sure how ECAF could do any of this. The scope of disputes is defined by the community. It's the community which sets the rules, not ECAF. ECAF doesn't have any say in the constitution, and it really shouldn't. That's the job for the community. ECAF will only resolve the conflicts that the community asks it to resolve. The constitution is the scope.

If you don't like that ECAF is handling certain cases, you can't ask them to drop them. You need to ask the community to amend the constitution so that those cases of dispute are not possible to arise from the constitution anymore.

> ECAF has also proved that it takes an incredibly long time to reach conclusions and issue orders. Whilst this is good for arbitration (we want to make sure they take adequate time to access each case), it is not a good process for carrying out actions that need to happen quickly (such as removing bad actors from the system). Block Producers are probably in a better positioned and better equipped to assess and make decisions that require swift implementation.

BPs can do emergency actions also in the current system. They just need to file a case after that, so that ECAF can verify if the action was rightful or not.

> If ECAF were to reduce and define their scope as an independent body that only policed and enforced against non-compliant block producers (i.e. became a completely different organisation), then I would be willing to take a look at that as a viable role for them.

Again, if you want to reduce and/or define the scope of ECAF, you can't ask ECAF to do it for itself. You need to ask it from the community, because it's the community which writes its own rules.
properties (22)
post_id67,385,695
authorsamupaha
permlinkre-eosvibes-eos-user-agreement-v3-0-20181213t211321164z
categoryeosvibes
json_metadata{"tags":["eosvibes"],"app":"steemit\/0.1"}
created2018-12-13 21:13:21
last_update2018-12-13 21:13:21
depth1
children1
net_rshares0
last_payout2018-12-20 21:13:21
cashout_time1969-12-31 23:59:59
total_payout_value0.000 SBD
curator_payout_value0.000 SBD
pending_payout_value0.000 SBD
promoted0.000 SBD
body_length2,968
author_reputation43,651,583,224,016
root_title"EOS User Agreement v3.0"
beneficiaries[]
max_accepted_payout1,000,000.000 SBD
percent_steem_dollars10,000
@eosvibes ·
>They didn't replace ECAF with another system, they removed base-layer arbitration completely and created the official way to use app-level arbitration. These are two completely different things. Base-layer arbitration means the arbitration of constitutional disputes. With EOS NY's proposal, this would be in the hands of BPs.

I don't agree with your logic. By removing ECAF they are replacing it with something else.

>It's the community which sets the rules, not ECAF. ECAF doesn't have any say in the constitution, and it really shouldn't. That's the job for the community. ECAF will only resolve the conflicts that the community asks it to resolve. The constitution is the scope.

The EUA is the exact proposal that will hopefully remove them.

It was a mistake to install a group of under funded, inexperienced volunteers into the constitution in the first place.

>BPs can do emergency actions also in the current system. They just need to file a case after that, so that ECAF can verify if the action was rightful or not.

The community will decide if BP actions are rightful or not. We don't need ECAF for that.
properties (22)
post_id67,500,824
authoreosvibes
permlinkre-samupaha-re-eosvibes-eos-user-agreement-v3-0-20181216t181322821z
categoryeosvibes
json_metadata{"app":"steemit\/0.1","tags":["eosvibes"]}
created2018-12-16 18:13:21
last_update2018-12-16 18:13:21
depth2
children0
net_rshares0
last_payout2018-12-23 18:13:21
cashout_time1969-12-31 23:59:59
total_payout_value0.000 SBD
curator_payout_value0.000 SBD
pending_payout_value0.000 SBD
promoted0.000 SBD
body_length1,121
author_reputation108,531,437,568
root_title"EOS User Agreement v3.0"
beneficiaries[]
max_accepted_payout1,000,000.000 SBD
percent_steem_dollars10,000