Github Gengbingbing Chrome Extension This repository contains the code for a chrome extension implementing the erc 4804 urls (web3: urls). this can be used to create censorship resistant websites hosted directly on evm compatible blockchains such as ethereum. the extension supports most erc 4804 websites. Chrome extension for web3: (erc 4804) urls. contribute to comfygummy chrome web3 development by creating an account on github.
Github Divyanshmishra101010 Chrome Extension Comfygummy has 3 repositories available. follow their code on github. Chrome extension for web3: (erc 4804) urls. contribute to comfygummy chrome web3 development by creating an account on github. We gave up on browser extensions because it was restricted and censored app store policy. we have an mvp available via conet project we will also support erc4804. i'd love to discuss about technology with you if i get the chance. We are currently thinking about adding an extension to erc 4804 to support customized headers (see eip 6944 and eip 5219). definitively we can take this into account to make the standard more powerful!.
Github Brow Chrome Extension Experiment We gave up on browser extensions because it was restricted and censored app store policy. we have an mvp available via conet project we will also support erc4804. i'd love to discuss about technology with you if i get the chance. We are currently thinking about adding an extension to erc 4804 to support customized headers (see eip 6944 and eip 5219). definitively we can take this into account to make the standard more powerful!. The standard here aims to provide a simple way for web2 users to directly access the content of web3, especially on chain web contents such as svg html. moreover, this standard enables interoperability with other standards already compatible with uris, like svg html. A very cool extension to support web3: url in chrome browser is here github comfygummy chr โฆ! now with web3: defined in erc 4804, we can browse a fully decentralized dynamic website on evm. When not designed for erc 4804, we cannot ask these contracts for a specific content type we want, and they donโt tell us which is the content type of the resulting data. The problem is, the ethereum wallet (i.e. "web3") is itself a chrome extension which means it isn't accessible in the sandboxed environments, which means i have to inject the script in order to access the user's wallet in the window object.
Comments are closed.