A General Purpose Bridge for Ethereum Layer 2 was demoed.  Nick Johnson, Founder and Lead Developer of ENS has explained it in detail.

He pointed to how there is a proliferation of layer 2 solutions for Ethereum and on how many of them are beginning to reach maturity.  Also, it is important for ENS to be able to provide resolution services across the entire ecosystem.  Thus, making it possible for the ENS users to be able to take advantage of the efficiencies that are made possible by Layer 2 solutions.

Sydney Ifergan, the crypto expert tweeted:  “Layer-2 solutions are the life line of anything other than Bitcoin happening in the Blockchain Space. Ethereum (ETH) already has capitalized well on it.”

For those who do not understand Layer 2 solutions, they are reduce the need to interact directly with Ethereum while helping verify the correctness of data.

Binance Academy states, two major examples of layer 2 solutions are the Bitcoin Lightning Network and the Ethereum Plasma. Despite having their own working mechanisms and particularities, both solutions are striving to provide increased throughput to blockchain systems.

An interesting statement reads:  Ethereum (ETH) is Socialism and Bitcoin (BTC) is Capitalism in the Blockchain Space – Politics somehow creeps in no matter how decentralized we want things to be.

Ethereum (ETH) ENS Domains

For those who do not know about Ethereum Name Service, it is the way by which you can have one name for all your cryptocurrency wallets, a decentralized website, and more – with the security, censorship-resistance, and programmability of Ethereum.

Scott Cunningham stated, “The ENSDomains is an amazing project that allows you to purchase and set up a human-readable .eth address for people to send various cryptocurrencies to. ENS will handle all the transactions, all you need is one address.”

The community are discussing on Who is going to support ENS Domains by default first? Chrome or Mozilla? We need .eth to be resolved natively without any extensions. It’s as simple as reading the ipfs hash from ENS resolver contract. Wouldn’t be that cool for the whole world?

When someone asked if it is a W3C Standard, the reply was:  It’s not, but you’re right, we need a W3C standard for alternative domain name systems like ENSDomains and Unstoppable Web.

Interestingly someone pointed to stating, Boomers are boomers. Unless Mozilla turns into an DAO, Firefox and (for sure) Chromium will never implement Web3 specific protocols by default, but agnostically support custom protocols. Microsoft Edge is a big possibility, of course(new browser and MS seems interested in ETH)

.