Deploy to ENS

[ligi]

Context/spark: https://twitter.com/kevingaspar/status/1273785607479844866

website as in http://chainid.network
and the json

opening as issue to discuss the following with @pedrouid and @bmann :

• deployment pipeline
• ENS key handling
• update frequency (after each PR?)
• fee handling

[ligi]

might have been too many questions. I think with the low update frequency we can just publish manually for now with each new chain (are not too many). Just are we OK with using our grants fund a bit for this? Also @bmann feel free to take out what you are paying for the DNS domain. Hope there is a bit left to do the ENS updates afterwards. As far as I see currently we have >20$

[bmann]

I think I shared ownership of the domain, I’ll double check.

I think you can automate this with Fleek directly from GitHub.

[ligi]

fleek sounds like a good idea. Should the domain go to 0xfcd819c8a13de2d9e409fdf7d61161091f58dd63 - do you have the keys to this?

[bmann]

@ligi sorry! I'll check. This is the old Gnosis Multisig, and I am the owner of it with an account I control. Looks like we never completed adding you two :P

There is a little bit of DAI in there, like ~$23 https://etherscan.io/address/0xfcd819c8a13de2d9e409fdf7d61161091f58dd63#tokentxns

Which I will convert / retrieve using this https://help.gnosis-safe.io/en/articles/4100585-how-to-use-your-legacy-mobile-gnosis-safe-with-the-safe-multisig-web-interface

I suggest setting up a (new) Gnosis Safe as the owner?

FYI, Fission now has Github Actions to publish to IPFS, but not planning on ENS automation any time soon.

[ligi]

@bmann you are the one that has most costs currently as you pay for the domain. So please also take this out first.
There seems to be also something on the zk-chain - wondering how this works with the multisig.