Sidechain transactions using a two-way peg effectively only allow for intra-chain transactions. A transfer from Bitcoin (parent chain) to Ethereum (sidechain) would allow a user to use the functionality of Ethereum (i.e., fully expressive smart contracts), but the underlying original asset would remain precisely that, Bitcoin. So, a Bitcoin on an Ethereum sidechain technically remains a Bitcoin.
Step back from the details for moment and consider what’s been described. We now have a way to move coins from Bitcoin onto another platform (a sidechain) and move them back again. That’s pretty much what we do when we move them to a wallet platform or an exchange. The difference is that the “platform” they’ve been moved to is also a blockchain… so it has the possibility of decentralised security, visibility and to gain from other innovation in this space.
The public blockchain is open to anyone who wants to deploy smart contracts and have their executions performed by public mining nodes. Bitcoin is one of the largest public blockchain networks today. As such, there is limited privacy in the public blockchain. Mining nodes in the public blockchain requires a substantial amount of computational power to maintain the distributed ledger at a large scale. In the Ethereum public blockchain, smart contract codes can be viewed openly.
Instead, what if the game was played in its own “channel”? Each time a player made a move, the state of the game is signed by each player. After an epic battle where the Protoss player takes out the remaining Zerg forces and forces a gg, the final state of the game (Protoss wins) is sent to a smart contract on the main chain. This neutral smart contract, known as a Judge, waits a while to see if the Zerg player disputes the outcome. If the Zerg player doesn’t, the Protoss player is paid the 1 ETH.
To scale Blockchain, sidechain or childchain solutions cannot be undermined. Sidechains are separate Blockchains that are linked to the main Blockchain using a two-way peg. They are an auxiliary network that executes the complementary function of: faster transactions, lower transaction costs and greater scalability in terms of the number of transactions that can be supported in a network at a given time.
– we provide no uniqueness of names, unlike the domain registrars, social networks, namecoin, onename.io, etc. There is no uniqueness of names in real life either. Instead the identity is just a hash of a [json] object that contains a public key. Identity object can not be modified directly, but a new version of it can be created, pointing to a previous version. The owner of the identity object can optionally connect it with the real life credentials, e.g. the social account, internet domain, email, etc. by proving the proof of ownership of that account the way onetime.io does it, the way Google Analytics does it, etc. This allows a spectrum of identities from fully anonymous to fully disclosed and verified. This also allows a person to have multiple identities, for work, for social, for gaming, for interest-specific forums. To simulate OAUTH2, a new site-specific identity can be created and signed with person’s other identity.
External Account, which stores ETH balance – This contains the address of the User that was created using the Web3.js API, e,g, personal.newAccount(…). These accounts are used for executing smart contract transactions. ETH is your incentive received for using your account to mine transactions. The address of the account is the public key, and the password of the account is the private key.