RE: EOS with DPOS is immune to the GFW attack _because it is more decentralised_ by demotruk

View this thread on: hive.blog | peakd.com | ecency.com

Viewing a response to: @o1o1o1o/re-iang-eos-with-dpos-is-immune-to-the-gfw-attack-because-it-is-more-decentralised-20170924t222157113z

eos · @demotruk · Sep 26 '17 (edited)

$0.18

Yes it does. The difficulty adjustment mechanism for Bitcoin is based on every 2016 blocks, not dynamic every block, meaning that Bitcoin does not handle large drops in hashpower well at all. In fact it could be catastrophic, especially with a feedback mechanism of dropping prices and long backlogs as a result of the drop.

👍 ackza, o1o1o1o, gregaria

`author`	demotruk
`permlink`	re-o1o1o1o-re-iang-eos-with-dpos-is-immune-to-the-gfw-attack-because-it-is-more-decentralised-20170926t074605077z
`category`	eos
`json_metadata`	{"tags":["eos"],"app":"steemit/0.1"}
`created`	2017-09-26 07:46:06
`last_update`	2017-09-26 07:46:54
`depth`	2
`children`	3
`last_payout`	2017-10-03 07:46:06
`cashout_time`	1969-12-31 23:59:59
`total_payout_value`	0.141 HBD
`curator_payout_value`	0.043 HBD
`pending_payout_value`	0.000 HBD
`promoted`	0.000 HBD
`body_length`	324
`author_reputation`	279,453,298,745,864
`root_title`	"EOS with DPOS is immune to the GFW attack _because it is more decentralised_"
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	15,959,429
`net_rshares`	52,736,529,066
`author_curate_reward`	""

properties (23)vote details (3)

voter	rshares	pct
ackza	27,744,578,780	18%
gregaria	6,812,629,037	100%
o1o1o1o	18,179,321,249	100%

@o1o1o1o · Sep 26 '17 (edited)

Thanks, that's a good point. All these numbers can be changed if miners felt like it.  But a reduction in block time to 1/10 what it is now doesn't seem like it would be that harmful. Ditto a big reduction in the readjustment time. Reduce the difficulty and block reward appropriately so it's effectively a no-op for miner income and what do they have to worry about? 

Sure we mine all the coins a lot sooner and things get squirly at the end sooner (did anyone really think about that?) but in the mean time BTC is a lot more stable and usable. If we lost 90% of the hash power it wouldn't be any worse than it is right now and the network would adjust a lot sooner.

properties (22)

`author`	o1o1o1o
`permlink`	re-demotruk-re-o1o1o1o-re-iang-eos-with-dpos-is-immune-to-the-gfw-attack-because-it-is-more-decentralised-20170926t090314505z
`category`	eos
`json_metadata`	{"tags":["eos"],"app":"steemit/0.1"}
`created`	2017-09-26 09:03:15
`last_update`	2017-09-26 09:04:09
`depth`	3
`children`	2
`last_payout`	2017-10-03 09:03:15
`cashout_time`	1969-12-31 23:59:59
`total_payout_value`	0.000 HBD
`curator_payout_value`	0.000 HBD
`pending_payout_value`	0.000 HBD
`promoted`	0.000 HBD
`body_length`	668
`author_reputation`	2,728,456,787,729
`root_title`	"EOS with DPOS is immune to the GFW attack _because it is more decentralised_"
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	15,964,514
`net_rshares`	0

@demotruk · Sep 26 '17 (edited)

>But a reduction in block time to 1/10 what it is now doesn't seem like it would be that harmful.

I assume you mean ten times increase. That would reduce effective transaction capacity by 90% for several weeks. I think that would be extremely harmful for users.

Edit: I think I understand what you mean now. Bitcoin doesn't have a "block time" parameter. "Block time" is a function of difficulty, available hashpower and chance. Miners cannot change these at will, it requires consensus across the community (miners, exchanges, wallets, all relevant economic participants).

>Reduce the difficulty and block reward appropriately so it's effectively a no-op for miner income and what do they have to worry about?

That would require a hard fork. The history of Bitcoin governance suggests that would be anything but a smooth fix these days.

properties (22)

`author`	demotruk
`permlink`	re-o1o1o1o-re-demotruk-re-o1o1o1o-re-iang-eos-with-dpos-is-immune-to-the-gfw-attack-because-it-is-more-decentralised-20170926t090833704z
`category`	eos
`json_metadata`	{"tags":["eos"],"app":"steemit/0.1"}
`created`	2017-09-26 09:08:36
`last_update`	2017-09-26 09:21:06
`depth`	4
`children`	1
`last_payout`	2017-10-03 09:08:36
`cashout_time`	1969-12-31 23:59:59
`total_payout_value`	0.000 HBD
`curator_payout_value`	0.000 HBD
`pending_payout_value`	0.000 HBD
`promoted`	0.000 HBD
`body_length`	841
`author_reputation`	279,453,298,745,864
`root_title`	"EOS with DPOS is immune to the GFW attack _because it is more decentralised_"
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	15,964,827
`net_rshares`	0

@o1o1o1o · Sep 27 '17 (edited)

Yes, you got what I meant second time - I should have been more precise.  And I understand the "block time" issue - it's a statistical measure of the effect of hash difficulty and available hash power and difficulty is adjusted every X blocks to approximate to the mean 10 minute block time, right?  (I've never read the code but that was my understanding).

And I understand it requires a hard fork vs. soft fork, but for miners why wouldn't they go with it.  More stability for the net, no change in revenue, and since it would increase TPS capacity for BTC and decrease mean confirmation time it would make BTC more competitive with ETH as a utilitarian payment system vs. "store of value" not traded often.  Although personally, I think all the work on payment channels and off-chain settlement is the way forward there.

I wish that more people would look at the work being done with [Tezos](https://www.tezos.com/) where the consensus protocol is part of the blockchain - which makes it easy to change the rules within the system itself.   And a "do-over" is possible - again with consensus.

properties (22)