This article was first published on Horizen
Horizen is designing Sidechains and a Sidechain SDK to allow developers and enterprises to quickly and affordably spin up their own blockchains. Our next sidechain engineering milestone is just days away!
About this Sidechain Q&A
The Q&A you are reading today was sparked by Telegram community member Joker. Horizen co-founders, Rob and Rolf, and Rowan our Director of Business Development took turns answering his questions.
The questions and answers were so interesting, we wanted the entire community to be able to read them! This is the 2nd part of the conversation. Read the 1st part here
QRegarding sidechains, I think it’s a matter of achieving sufficient decentralization for each sidechain depending on each use case. How many nodes on average will do consensus for a sidechain? Or is that sidechain specific?A
Part of what goes into the design of the different aspects of the platform is to work to achieve an economic incentive. For the two main Horizen system sidechain applications that are designed to run on the supernodes, which are compensated to operate. This is not happening yet, but the expectation has always been there. Supernode operators will not be surprised if that becomes a requirement.
For third party sidechains, there will be a payment to the node operators who choose to run the third-party application designed into the system. It is with ZEN whenever a transfer to/from the mainchain to sidechain takes place.
QWhat smart contract languages will be supported on the sidechains? Will they be Turing complete?AThe great thing is that we can build any and all smart contracting languages because there’s no constraint; the system is fully generalizable.
from a second perspective, a great characteristic of doing the system architecture this way is that each ...
To keep reading, please go to the original article at: