Viewing a response to: @jga/re-inertia-re-yabapmatt-re-inertia-comparing-steem-engine-to-dstors-and-dlive-20190412t144159684z
I think what Dan is saying is that implementing a side-chain next to a main-chain, where the main-chain itself already has smart contracts, is trivial due to multisignature (side-chains in Easy Mode). Steem Engine is setting up a side-chain in Hard Mode, without a main-chain smart contract system. Then, in its own side-chain, it defines a smart contract system within the side-chain. Without the benefit of main-chain smart contracts, Steem Engine needs to establish consensus some other way. This external consensus could possibly leverage side-chain signatures in some way. E.g., when a block is included in the side-chain, it's signed in some way by a block producer. I'm not sure if side-chain multisignature has a role in block production in this scenario. We already have main-chain multisignature, but by itself, multisignature is not a solution without main-chain smart contracts. **By the way, [check this out](http://scribe.steemian.info/?url=https%3A%2F%2Fsteemit.com%2Flisk%2F%40dan%2Fwhy-lisk-is-inferior-to-ethereum).**
| author | inertia |
|---|---|
| permlink | re-jga-re-inertia-re-yabapmatt-re-inertia-comparing-steem-engine-to-dstors-and-dlive-20190412t155834546z |
| category | steemengine |
| json_metadata | {"tags":["steemengine"],"app":"steemit/0.1","links":["http://scribe.steemian.info/?url=https%3A%2F%2Fsteemit.com%2Flisk%2F%40dan%2Fwhy-lisk-is-inferior-to-ethereum"]} |
| created | 2019-04-12 15:58:33 |
| last_update | 2019-04-12 16:00:51 |
| depth | 4 |
| children | 1 |
| last_payout | 2019-04-19 15:58:33 |
| 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,043 |
| author_reputation | 346,568,901,399,561 |
| root_title | "Comparing Steem Engine to dstors and dlive" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 82,965,369 |
| net_rshares | 0 |
Thanks for the link with the history of changes. > I'm not sure if side-chain multisignature has a role in block production in this scenario. Suppose that the actions of @steemsc are made by consensus between several parties, like the witnesses of the side chain. In this scenario, @steemsc is a multisignature account, and one action requires 17 of 21 signatures to be performed. The authorities (active/owner) of @steemsc are updated in the main chain as the witnesses change in the side chain. I think that it is what Dan is saying in his article. In fact, he is saying that this is the way Lisk is working, and that we could do the same in steem: > Lisk relies on 3rd party multi signature solutions to evaluate the code and authorize any transfers out of the smart contract. ... App developers could use Steem and BitShares to implement smart contracts via *Side Chains* in the same manner
| author | jga |
|---|---|
| permlink | re-inertia-re-jga-re-inertia-re-yabapmatt-re-inertia-comparing-steem-engine-to-dstors-and-dlive-20190415t071347965z |
| category | steemengine |
| json_metadata | {"tags":["steemengine"],"users":["steemsc"],"app":"steemit/0.1"} |
| created | 2019-04-15 07:13:48 |
| last_update | 2019-04-15 07:13:48 |
| depth | 5 |
| children | 0 |
| last_payout | 2019-04-22 07:13:48 |
| 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 | 900 |
| author_reputation | 76,172,796,162,312 |
| root_title | "Comparing Steem Engine to dstors and dlive" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 83,124,252 |
| net_rshares | 0 |
hiveblocks