Eth Addresses Accessibility
It has been announced the capability of accessing sites via the .eth extension when Meta Mask is installed, this means that it’s possible to resolve vitalik.eth/ using a correctly configured browser.
Currently, this requires the slash on the end, which is reminiscent of the rsync on command line. Our ability to engage with web3 technologies is once again increasing, laying the foundation for new ways to securely transact online in a decentalised fashion
When using brave to access .eth/ extensions initially it will ask to enable Cloudflare as the resolver, with further adoption it is we should see this built in as standard on browsers
.eth .crypto .wallet
There is an ever increasing number of extensions that simplify transacting crypto currencies and utilising web3 technologies. The Ethereum blockchain has positioned itself at the main chain for smart contracts, the main issue currently is the unrealistic gas fee’s. Currently this can be put down to the stage of development Ethereum is currently at, it’s value will be pegged to its ongoing development and stability. To make it more accessible the cost of processing on chain has to come down in price.
This provides another use case for MetaMask and for anyone interested in learning about cryptocurrencies and engaging with web3 technologies then MetaMask makes for a perfect introduction. I use it through the Brave browser, which is my current defacto browser for engaging with Web3 technologies, which started with great support for IPFS.
We are getting to the point of convergence with web3 technologies, whereby there are reliable smart chains for processing transactions, seamless wallet integration via browsers, immutable websites where the data inside the corresponding hash is unchangeable. This is building to a level of stability and accessibility where decentralised technologies can replace established self-centre centralised organisations that are designed to server vested interest.