EOS Advertised To Ethereum Co-Founder While Engaging In Discussion About Ethereum’s Smart Contracts

By January 15, 2020 DApps
Click here to view original web page at www.thecoinrepublic.com

  • EOS was capable of executing smart contracts in a way Ethereum couldn’t.
  • The discussion had started as a result of a tweet from Mikerah, a founder of HashCloak.

Block.One CTO, Daniel Larimer tweeted in response to Ethereum founder Vitalik Buterin’s that EOS was capable of executing smart contracts in a way Ethereum couldn’t. The discussion had started as a result of a tweet from Mikerah, a founder of HashCloak.

A blockchain R&D lab focused on privacy, where he tweeted out that dApps are just web apps that have smart contracts deployed onto the Ethereum network and hosted on traditional web-app hosting services like Heroku. Mikerah claimed that the backend code and the UI/UX of popular web apps and Ethereum didn’t differ much.

Here's your afternoon reminder that DApps are just basic web apps hosted on Heroku and the smart contract(s) deployed onto Ethereum and accessed through Infura.

Stop acting the UX/UI and backend is all that different from Twitter (Twitter's backend is more complex, anyway)

— Mikerah (@badcryptobitch) January 13, 2020

Other developers like Mark Beylin stepped into the mix to call Mikerah’s opinion, some stating that traditional backend development and UX design is easier to work with compared to Ethereum’s backend.

I can't speak about all dapps, but generally you are very very wrong. Most require off-chain caching for good UX, which opens a massive can of worms when users want to know wtf is going on, but Ethereum doesn't always gracefully handle transactions.

— Mark Beylin (@MarkBeylin) January 13, 2020

Others like Dean Eigenmann, a researcher at Vac, and a developer at Ethereum Name Service, had an opposite opinion, calling Web 3.0 node-setups considerably easier to execute than sharding databases for Web 2.0.

Not that big of a can of worms, it doesn’t require that much effort imo.

— Dean Eigenmann (@DeanEigenmann) January 13, 2020

The conversation soon turned into one about Ethereums dApps inability to send multiple transactions for the user and react to on-blockchain events at the same time.

This is when Ethereum’s co-founder Vitalik Buterin, threw his hat into the conversation by stating that handling ethereum nodes shouldn’t be a factor that dApp developers need to worry about.

The fact that dapp developers are the ones that need to worry about spinning up ETH nodes is itself a problem….. that should be a wallet-side thing.

— vitalik.eth (@VitalikButerin) January 14, 2020

It should be controlled by Ether wallets instead. Dean Eigenmann then raised the argument against Buterin that dApps wouldn’t be as reactive if they let wallets handle ethereum nodes.

Eigenmann then went on to build a point to Buterin that dApps would have to manage their nodes if they were to send multiple transactions for the user.

This is when Buterin acknowledged that it would be a welcome addition to the Ethereum network over an Ethereum Improvement Protocol (EIP) that handled sending transactions that ran code that worked in tandem with the transactor’s account.

Daniel Larimer quickly took this opportunity to step in and advertise EOS, stating that the ability to handle smart contracts that runs code with the context of the transactor’s account and also bundling multiple actions into a single transaction even if those actions require the authentication of various accounts.

Compared to Ethereum which sits as the 2nd largest cryptocurrency by market value, EOS sits at a lowly 8th place with a market value that’s about 5x lesser.

Ethereum popularised the idea of smart contracts and the fact that EOS can handle intelligent contracts in a way that Ethereum cannot, is a statement to the fact that Ethereum quickly needs to bridge gaps that makes it difficult for Web 3.0 developers to build dApps on the network.

The discussion had started as a result of a tweet from Mikerah, a founder of HashCloak.

[…]

Leave a Reply