RE: Blockchain Update: Platform Independent State Files by raycoms

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

Viewing a response to: @blake.letras/pys3r9

steem · @raycoms · Oct 3 '19

It depends always on the use case, if the code is open source, and a server is only there to make it perform well then it is a valid use case of softconsensus. Everyone can verify it, and everyone can create their own server with valid data if they wanted to as well as own frontend.

If it is not open source it is more complicated, then the things can be verified but in the end the company can still just stop existing the and the userbase might need years to develop an alternative to run on the past data.


But in the End, smart contracts end up being open source because they are deployed on the blockchain as well. So it don't think its good to compare non-open-source consensus projects with open source smart contracts

properties (22)

`author`	raycoms
`permlink`	pyt0qu
`category`	steem
`json_metadata`	{"app":"steemit/0.1"}
`created`	2019-10-03 15:08:54
`last_update`	2019-10-03 15:08:54
`depth`	2
`children`	2
`last_payout`	2019-10-10 15:08:54
`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`	728
`author_reputation`	115,046,969,395,583
`root_title`	"Blockchain Update: Platform Independent State Files"
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	91,191,835
`net_rshares`	0

@blake.letras · Oct 3 '19

True that if it is open source then it would be distributed. However, it is not autonomous or perpetually tangible, which I think is very important. The only way to obtain these valuable features is to create a replicating state machine for these items recorded by Steem, but that means the use of Steem becomes unnecessary. 



The value of on-chain execution is that your asset is preserved by a replicating state machine and thus perpetually tangible. Ethereum caused the intangible to become tangible. Soft consensus does not do this, but rather it only serves as a back up receipt of authenticity. 

I suppose soft consensus is good if you want everyone running their own servers, or design a system that rewards people for running servers, but then the cost would go up and it would be no different from on-chain costs. In this way, I could see something being built on top of IPFS. However, I still argue that smart contracts are better, because you don't have to run your own server. 

Thanks for sharing your comment. :)

properties (22)

`author`	blake.letras
`permlink`	pytcz5
`category`	steem
`json_metadata`	{"app":"steemit/0.1"}
`created`	2019-10-03 19:33:09
`last_update`	2019-10-03 19:33:09
`depth`	3
`children`	1
`last_payout`	2019-10-10 19:33:09
`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`	1,029
`author_reputation`	2,151,206,685,849
`root_title`	"Blockchain Update: Platform Independent State Files"
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	91,198,814
`net_rshares`	0

@raycoms · Oct 3 '19

I think the main difference between the two models is scalability. Smart contracts very difficultly scale well. If you look at the most scalable proposals of smart contracts at the moment all of them shard the public network and execute the state machines on a reduced subset which in the end also results in reduced decentralization.

So, either you have a model which doesn't scale at all (Ethereum) or you got a model which scales decently (Algorand) but is less decentralized and easier to attack, or you got a model which scales very well (Steem - "soft consensus") but you need to run it yourself and people have to verify things externally before trusting the values.

I did some comparisons in terms of price and ease in my last paper, and executing things on Steem via soft consensus was ridiculously cheap even if you add the server renting costs together.

properties (22)