I was asked about the differences between a #blockbase sidechain and a private #EOSIO chain. These were my answers: thread

(1/8) a blockbase sidechain can be public, private or mixed, and benefits from being pegged to a strong chain, a private EOSIO chain is as secure as the nodes running it

(2/8) a blockbase sidechain is requested and provided through an open market, where providers join the sidechain if it makes economic sense to them, on a private EOSIO chain you either choose the producers or you elect them in some fashion

(3/8) a blockbase sidechain has consensus on the history of the data, any EOSIO chain has consensus on the operations through smart contracts and the state in RAM (history nodes are unreliable and grow very quickly)

(4/8) a blockbase sidechain is designed to be used by one entity, and secured by many third-party public entities, a private EOSIO chain is designed to be used by one private entity, and secured by that private entity

(5/8) a blockbase sidechain offers a horizontal scalability option to EOSIO chains, because all data living on a sidechain doesn’t “pollute” the main chain, so you can have thousands of sidechains to a main chain. A private EOSIO chain is just that, a private chain

(6/8) a blockbase sidechain has privacy built in with encryption, all data you store there may be completely encrypted, currently EOSIO doesn’t offer that technology

(7/8) the blockbase requester node (and in the future all full nodes) supports direct sql queries with encrypted fields, giving you querying capabilities that are much more powerful than with EOSIO while being able to query over encrypted data, again something EOSIO doesn’t have

(8/8) a blockbase network lives alongside an EOSIO chain, and the nodes in the network can provide multiple sidechains simultaneously in an automatic fashion, without any manual intervention by the owner of the node. This concept doesn’t exist in EOSIO

I guess the list could go on and on, but these are the first ones that came to mind.