IBC: Inter-blockchain Communication
Q1 How to Scale & Moore Law? -- Jose
1.1. tx has scopes, two tx in common cycle can run parallel
1.2. Inter-blockchain Communication (IBC)
1.3. Region / Foreign Chains
1.3.1 foreign chain with same bp and same stream
1.3.2 Computational Efficiency
1.3.3 for Computational Heavy but NOT bandwidth Intensive
Reference IBC via merkle proofs
Q2: How does Region reach consensus?
2.1 Cluster or Individual?
2.2 Sync as whole chain & data different
Github Issues: User configurable generic security delay
Q3: set_code doesn't change the database
3.1 mandatory delay, set_code is public
3.2 delay for set_code
3.3 Customize demand
@eosgo @dan For all the non-tech guys like me out there:
Could eos contain gmail and facebook and even more sites like amazon? yes or no?
Thank you for all the great stuff you're doing!
Hi @andymandy - in short, most likely; an Amazon on EOS would look like a peer to peer exchange (think Ebay, or what Amazon has actually become with its sellers program) and a third party is already building a dapp along these lines.
Gmail doesn't have a strong use case for decentralization, and we can't confirm whether it's technically possible on EOS. Facebook could be facing stiff competition in 5 years.
Ok thanks, exiting with the perhaps "ebay-like" dapp.
Wow man it would be awesome if steemit could handle Gmail. And if steemit could be able to perform operations like Facebook, extra efficiency can do the trick. @eosgo
EOS is really becoming the potential platform on which very diverse Dapps would be built. It is equipped to make blockchain mainstream. Ethereum and Hyperledger are adopted widely for different reasons, and now EOS has a chance to be both with its capability/scalability and decentralized governance.
Thanks guys @eosgo