Sidechain is exclusive to elastos ecosystem. Friendchain lives outside of elastos ecosystem. DID chain is a sidechain. When ethereum or neo smart contracts get ported to elastos, we will have a corresponding sidechain for them too. Whereas, public chains like ethereum, neo, ada, EOS, whatever are friendchains.
There are two types of sidechains. System level sidechains and application level sidechain. System level sidechains are something that will be utilized by all DApps no matter what. For example, everyone and everything gets an ID via DID sidechain. Token sidechain is another system level sidechain that issues tokens to DApps. So everything on elastos is pegged to ela and will be used to power this system via system level sidechains.
Application level sidechains are specific only to applications. For example, ported neo or ported eth smart contract sidechain May be application level sidechain since applications can choose these or create their own specific for their needs. These types of sidechains will likely have their own sidechain token
Friendchains are what allows ela and other public chains to interoperate with each other. For example, dex and atomic swaps between ela and public chain tokens. Maybe eventually, we can even interoperate with the public smart contracts similar to what wanchain is doing.
🚨 Technical Development🚨 Trinity✅ Wallet ported to Trinity, it can run normally in the form of dApp, and the docking test network is verified. Currently, only Android platform is supported, and iOS platform is under development.✅ Improve the Wallet dApp, based on the testnet environment, has implemented DPoS voting✅ dApp signature and verification is basically completed, code finishing✅ Browser engine switches from WebView to Webkit plugin to provide better performance and user experience✅ Update the latest Carrier SDK and test the carrier plugin✅ Modified each plugin document to update the use of the plugin in Trinity (written directly in the manifest.json corresponding to the dApp) Hive✅ Solving the problem of synchronization instability between different nodes of Key-Value in Hive✅ Hive IPFS/Cluster releases new version v0.1 (Alpha developer trial version) and re-arranges Hive Cluster test cluster✅ Updated Hive Native SDK v0.1 (C++ version) to eliminate compilation errors and alarms, and release v0.1 SDK version after verification✅ Continue to write and review Hive Native/Java/Swift SDK✅ Start building and writing Hive Native SDK test case setsCarrier✅ Optimized Carrier Native offline message implementation (offline message changed to asynchronous send)✅ Merge offline message test case code (prepared as offline message stability test case) into offline message branch✅ Merging offline message branches into the Carrier Native repository Master branch✅ Verify offline messages and perform stress tests✅ Incorporate the iOS/Android offline messaging feature into the Master branch to begin verification✅ Released the Carrier Android-v5.2.2 version and released the generated aar package to the Bintrayenter platform for third-party Android applications to rely on the Carrier via Gradle✅ Publish a Technical Preview release (v5.3) that supports offline messaging✅ Synchronous debugging to verify offline messaging for Android/iOS CarrierELA main chain DPoS consensus✅ DPoS goes online for the second iteration, bug convergence✅ Use DNS instead of SeedList configuration to resolve the problem that the arbitrator network cannot be connected due to the inability of DNS to forward routes.✅ When the arbitrator becomes Inactive, the time to resume the transaction can be changed from one day to immediately✅ Solving the problem that the DPoS network cannot be connected due to dynamic IP✅ Modify python automated detection program to support ela, arbiter, andid configuration file changes✅ ela-cli command line tool adds info listproducers, active transactions, voting transactions, output multiple outputs, and updates to documents✅ A mechanism for degrading into a DPoS consensus of only 12 CRC nodes when the number of subsequent arbiters is insufficient when pre-connection, normal handover, and inactive handover are implemented.✅ Clean up the super node deployment plan and simplify the ELA configuration file✅ Improve the warning program for arbiter not to issue proposals SPV C++✅ dev branch adds support for Token chain has been completed✅ Modify the light node reconnection delay, change to gradually increase, and finally synchronize the time to the last block time.✅ Joint debugging ETH SPV synchronization encountered problems, can complete the head node chain download✅ Spv Python interface wrapper for automated testing of Spv wallet modulesEthereum compatible side chain✅ Write tests to other nodes that have processed the refill transaction and delete the transaction logic from the transaction pool.✅ Test contract compatibility, test new contract compiler✅ Researched the Ethereum logFilter and tested it in the light node background coroutine.✅ Modify the Ethereum wallet, you can automatically switch to the mainnet corresponding to the main chain when the mainnet, testnet, rikeby network switch, testnet, regnetOther✅ Neo side chain increases receipt structure