FAQ

Are there network resources given to the network from each node?

There are, but it's a restricted set of resources defined through a narrowly scoped type-safe interface (i.e. no arbitrary function serialization,) which deal with consensus oriented interactions, throughput is shared in a fashion similar to a torrent network, where we act like a tracker / bandwidth liquidity provider and the chains can configure their interactions with other chains, and for performance purposes prefer to transact with chains that offer them dependencies (i.e. a crypto-kitty chain is more likely to interact with the underlying service chains that power it and our network, but not necessarily a crypto-kitty competitor chain.)

Are those resources application defined (dynamic) and accessed off-chain or on chain?

Both, applications have some components that are tracked against our main chain, but can apply application specific logic to their own internal chain which deviates from our schema. additionally many privacy oriented concerns require off-chain solutions but may need certain aspects to be pegged on-chain to support verifications and consensus, which necessarily requires a combined approach.

I am having trouble understanding if the computational layer of Constellation is relatively strong compared to Ethereum or another blockchain.

We view execution providers as another service layer abstraction to be implemented within the network, this prevents centralization of execution ala ethereum and empowers flexibility / plug-and-play approaches to supporting arbitrarily many decentralized hosting providers (ala a decentralized form of AWS, GCP, etc) each with its own competitive service.

Is it similar to Holochain/Perlin where the main purpose of the network is to have cheaper and more network resources available on chain for dApp developers

The end goal is very similar, but we are not enforcing a particular VM selection / compute pipeline, instead approaching this as an integrations problem.