Subcores are sharded cores of the mainchain that each function as a part of the mainchain and is run by curators in STEM enclaves just like subchains. They scale mainchain transactions by computing in STEM enclaves and pushing upcore to the maincore of the mainchain.
Each subcore performs specifically one narrow task or type of transaction or pallet. For example, there could a be a currency-subcore that only runs the currency protocol such as tokens, MultiCurrency, ERC20s, NFTs, transfers, minting, burning, etc., and a staking-subcore that specifically runs the staking protocol of the the network, there could also be a dex-subcore for the DEX, a ecdp-subcore for the ECDP stablecoin protocols, etc.
Subcores do not replace Subchains and they function differently from Subchains. A subcore is technically a system subchain that is run by the mainchain validators as an integral part of the mainchain, this is the metaphorical, however a subcore is an embedded part of the mainchain consensus that entirely runs in the STEM enclave for off-chain compute of transactions at the scalability and security level of subchains without having the need for external or independent validators.
Therefore we introduce a second type of validator to run subcores, these are called curators. The curators are operators selected from a rotating list of inactive-validators who run the subcores. One subcore could be run by 10-30 curators per ConclavePeriod, they are then rotated per ConclavePeriod.
A ConclavePeriod is the period when the hash of subcore or subchain transactions is pushed upcore to the maincore (or mainchain in terms of subchains).
We should also enable subchains to communicate with subcores directly, because the subchain stack should be built to leverage the Subcore system. SIAL should support Subcores to allow SIAL MultiLocations to communicate with subcores
balqaasem
commented
1 year ago
Subcores are sharded cores of the mainchain that each function as a part of the mainchain and is run by
curatorsin STEM enclaves just like subchains. They scale mainchain transactions by computing in STEM enclaves and pushing upcore to themaincoreof themainchain.Each
subcoreperforms specifically one narrow task or type of transaction or pallet. For example, there could a be acurrency-subcorethat only runs the currency protocol such as tokens, MultiCurrency, ERC20s, NFTs, transfers, minting, burning, etc., and astaking-subcorethat specifically runs the staking protocol of the the network, there could also be adex-subcorefor the DEX, aecdp-subcorefor the ECDP stablecoin protocols, etc.Subcores do not replace Subchains and they function differently from Subchains. A
subcoreis technically a systemsubchainthat is run by the mainchain validators as an integral part of the mainchain, this is the metaphorical, however asubcoreis an embedded part of themainchainconsensus that entirely runs in theSTEMenclave for off-chain compute of transactions at the scalability and security level of subchains without having the need for external or independent validators.Therefore we introduce a second type of validator to run subcores, these are called
curators. Thecurators are operators selected from a rotating list ofinactive-validatorswho run thesubcores. Onesubcorecould be run by 10-30 curators perConclavePeriod, they are then rotated perConclavePeriod.A
ConclavePeriodis the period when the hash ofsubcoreorsubchaintransactions is pushed upcore to themaincore(ormainchainin terms ofsubchains).We should also enable
subchainsto communicate withsubcoresdirectly, because the subchain stack should be built to leverage the Subcore system.SIALshould support Subcores to allow SIALMultiLocationsto communicate withsubcores