I was recently browsing through the governance page and discovered this proposal discussing domains and security for yearn.finance.
I believe creating an IPFS website for yearn.finance would be beneficial for a few reasons:
1. It would give users the ability to interact with Yearn in the case the website servers were attacked by a third party or government. 2. It would give users the ability to interact with Yearn in the case yearn.finance was seized by the domain registrar.
How could we do this?
I’m with the Unstoppable Domains team and we are willing to fund the development of this IPFS website and then transfer it over to Yearn’s controlling address.
We’ve identified a development firm who can deploy Yearn on IPFS and connect it to the blockchain domain yearn.crypto.
Once yearn.crypto is transferred to the multi-sig address, only the controllers of that address could take down the website.
I believe a censorship resistant version of Yearn is important for users of the protocol.
Why do we want to do this?
Our goal is to help onboard users and protocols to the decentralized web. Yearn is a fascinating project and we would love to facilitate the development of an IPFS website for the community. The creation of an IPFS website for Yearn would add an extra layer of security and censorship resistance.
Nice, would be interesting to have a censorship resistant atlernative… somethng like yearn.crypto. Who knows what autorities will do with decentralized projects like DEXses or projects like Yearn
Hi @mdunstoppable if you guys are willing to develop, I’ve been putting a few designs together.
None of these designs have been approved yet by the community. My plans are:
Produce end to end designs for desktop and mobile.
Produce two modes: light and dark.
Refine tone of voice, messaging and cover any edge cases.
Establish key journeys and propose each journey (or space) separately to the community for comment, amends and finally approval (or rejection and I start over)
Atm, it’s slow going only because I’ve other commitments. these however will thin in the next week and I’ll pump these out fast.
If you’re interested, with the communities blessing, I’d love to team up.
The current slides can be found here: https://scene.zeplin.io/project/5f1ae5afab9a393acc4d42bf
I can offer Zeplin access as well if we decide to move forward together.
It is easy to redeploy a website on IPFS from source, just a post build script like this to push it : ipfsDwebUploader.js example. It creates a new IPFS hash link. After that admin ( wallet or multisig) needs to update the ENS ( Ethereum Naming Service) with tx to target the new IPFS hash link. If you do not trust admin, you can always deploy from source to check if the IPFS hash is correct. The important part is to have access to website source code…
