coredns-ens is only the DNS server (over ENS) on port 53, right?
In order to run a eth.link server, I need to run all these containers mentioned in the enscluster README?
CONFIGS="namespace-cert-manager clustermetadata ssd-storageclass tiller-rbac ipfs-volumeclaim geth-volumeclaim ipfs geth ipfs-service geth-service letsencrypt-staging letsencrypt-prod eth-domains-cert" for conf in $CONFIGS; do kubectl apply -f cluster/$conf.yaml; done
Ok, I see, I only need to change the
21-coredns-ens.yaml file, and if I want to use the ropsten test networking, I need to add
geth --ropsten on 20-geth.yaml, right?
containers: - name: geth image: ethereum/client-go:v1.9.9 - "--ropsten" <<<<
@andrewheadricke , thanks. It's great that it's only a one file script! :)
but it makes a redirection to https://gateway.ipfs.io/ipfs/<current_contenthash>, which is inconvinient because users might save this link, and when the contenthash changes, they would look at the old content.
Ethereum transactions have become so expensive.
Calling ENS setContenthash cost 92,497 gas, $2.25!
Imagine paying $2.25 each time I need to change (a small part of) the content of the website.
Will Ethereum survive to this overpricing?
Will it become cheaper soon?
Or will Ethereum die soon?