@v1rtl.eth of StorageBeat team developed a website deployment too that sexily combines ENS addressing and storage backend deployment either into an IPFS node (pinning server) or to Swarm (decentralised backend "sea of nodes") https://blumen.stauro.dev 🌷

It is a CLI. So you dont even have to get up from your chair. StorageBeat.eth was deployed using thins.

building Stauro ❇ frontend dev at @ensdomains ❇
prev. @rainbow, @geniexyz, @fleek

Mathematician, Blockchain adjacent cryptography, Decentralised storage.

Let's decentralise the whole internet!

Only missing auto-deployment of an ERC-6860 contract pointing at the IPFS CID :)
Having web3://storagebeat.eth just work would be amazing.

Contributor @ /walletbeat.

Censorship resistance requires privacy.

It's a bit more than that; ERC-6860 is a standard for encoding an EVM call as a URL, but then has further conventions to return HTTP data in the EVM call response. This lets you treat a contract as an onchain HTTP backend. The contract takes in the URL parameters as input, and can return raw HTML or can redirect the caller to IPFS resources etc.

This lets you create onchain websites that aren't fully static, because you can encode dynamic logic into the contract.

There is a curl-like CLI tool and a fork of Chromium that speaks this protocol, letting you browse onchain websites. Check https://web3url.io/ (also available at web3://web3url.eth)

There is also an HTTP gateway at w3eth.io.
For example, here's an ERC-6860-served version of the ENS dapp frontend: https://app-ens-domain.w3eth.io/

cc @v1rtl.eth

@polymutex.eth this is a lovely discussion. I just *skimmed* ere6860 -- it seems that its a spec for an off-chain URI resolver to *send* data into the EVM. (please correct if im wrong!)

To serve Blumen's static content deployment to a "typical web2 user" (on, say, a browser), I think we don't need to interact with EVM.

Or: were u envisioning some dApp forward thinking? If so, im with you!

Yes, there's a curl-like CLI tool, a Chromium fork, and a Firefox extension (though I think that one just uses the gateway); check the bottom of https://web3url.io/

As for SC deployment, it's a smart contract, so like any smart contract you can use a proxy pattern to make the website updatable.

does anything support the ERC? and does it require SC deployment or an existing one could be updated?

Preaching to the choir!

What's the path forward?

Explore the EIPs / ERCs mentioned in this cast: