RE: Poll: Soft Consensus?
I couldn't agree more with this, "We should instead embrace both, which was always the original vision of Steem to begin with."
If the message from Steemit seems contrary to this, then we need to change the way we're communicating about it. Figuring out how to talk about Steem's hybrid approach to consensus is my real goal here. Maybe I'm asking the wrong question and the right question is, "How do we talk about Steem's unique approach which features both hard and soft/embedded consensus." But in a way that ordinary people can understand.
"Steem uses a novel hybrid approach to decentralized computing which features both hard and embedded consensus. This provides the security of smart contracts with the flexibility of traditional programming." Thoughts?
Somebody made a post explaining how Steem is an ASIC to Ethereum's FPGA. I like the analogy and hopefully developers are aware of this kind of hardware terminology as well. Steem can easily become the authentication layer to the decentralized internet of content or other similar marketing terms.
My view is that actual smart contracts are very useful and can play a role, often for bridge purposes in interacting with native functions of the chain such as access control, token movement, etc.
Almost every single blockchain including Bitcoin (almost the poster child for simplicity and stability over functionality) has at least some limited form of smart contracts. They're very useful for bridge purposes such as atomic swaps, token exchanges, adapters to lightning-network-like solutions, for security features such as time locks, two/multi-factor authentication without custody, etc. This does not mean that you build an entire application into the blockchain and expect consensus nodes to verify it for you for free, but there are portions of many applications that are useful for the core blockchain to support natively without the hard coding, risking the stability of the core chain, and hard forking the way we have been doing it.
I think we should stop hating on real smart contracts and should embrace them (with appropriate controls on resource use and bloat via RCs) in addition to soft consensus, not keep trying to pitch soft consensus as an alternative. For many applications it is, but for many others (at least not without great difficulty and enormous unforced marketing challenges) it is not.
We are marginalizing ourselves unnecessarily by trying to convince developers they don't need something they think they need. The better approach is to give them both and let them choose the tool they want to use.