Introduce EP5.1 & EP5.2 (#177)

app/src/config/navigation/protocol.ts

@@ -403,7 +403,21 @@ export const navigation: SectionData[] = [
                 ],
             },
             {
-                title: '📖 Proposals Term 4',
+                title: '📖 Proposals Term 5',
+                links: [
+                    {
+                        // eslint-disable-next-line prettier/prettier
+                        title: '5.2 - [Social] Determine ENS Labs\' next steps in eth.link litigation',
+                        href: '/dao/proposals/5.2',
+                    },
+                    {
+                        title: '5.1 - [Executable] Upgrade DNSSEC support',
+                        href: '/dao/proposals/5.1',
+                    },
+                ],
+            },
+            {
+                title: '📙 Proposals Term 4',
                 links: [
                     {
                         title: '4.10 - [Social] Transfer ENS Root Key Ownership to the ENS DAO',

docs/dao/proposals/5.1.mdx

@@ -0,0 +1,36 @@
+{/** @type {import('@/lib/mdxPageProps').MdxMetaProps} */}
+export const meta = {
+    description: 'Deploy a new version of the DNSSEC oracle and DNS registrar that enables \'gasless DNSSEC\' functionality.',
+    emoji: '📖',
+    contributors: [
+        'arachnid'
+    ],
+    proposal: {
+        discourse: '18535',
+        // snapshot: '0x8e3c8812bd52d1760eb2bbf8dc603d68860741f80d489dc051017e863151a242',
+        type: 'executable'
+    }
+};
+
+# [EP5.1] [Executable] Upgrade DNSSEC support
+
+## Abstract 
+
+The ENS labs team has been working on a new version of the DNSSEC oracle and the DNS registrar that, combined with wildcard resolution (ENSIP 10) and CCIP-Read, allow for 'gasless DNSSEC' - enabling the use of DNS names inside ENS with no onchain transactions required. This proposal replaces the existing DNSSEC registrar with the new one.
+
+Existing DNS names will continue to function as before, and names can still be imported using the 'legacy' method. The new registrar also allows configuring a name by setting a TXT record on _ens.name.tld, containing the address of a special resolver contract to use, followed by any resolver-specific data. Resolvers designed for the purpose can be configured to parse this extra data, making configuration entirely offchain a possibility.
+
+Alongside the new registrar and oracle contracts, a simple resolver is provided that reads the Ethereum address to resolve a name to from the extra data.
+
+Post-execution, ENS Labs will run a process to upgrade all current DNS TLDs to use the new registrar. TLDs will only function with the new registrar once this (permissionless) transaction is sent for the TLD.
+
+## Specification 
+
+Call `setController` on the Root contract at `root.ens.eth`, passing in the address of the new DNS registrar (`0xb32cb5677a7c971689228ec835800432b339ba2b`).
+
+## Transactions 
+
+| Address                                    | Value | Function      | Argument | Value                                      |
+| ------------------------------------------ | ----- | ------------- | -------- | ------------------------------------------ |
+| 0xaB528d626EC275E3faD363fF1393A41F581c5897 | 0 ETH | setController |          | 0xB32cB5677a7C971689228EC835800432B339bA2B |
+|                                            |       |               |          | true                                       |

docs/dao/proposals/5.2.mdx

@@ -0,0 +1,46 @@
+{/** @type {import('@/lib/mdxPageProps').MdxMetaProps} */}
+export const meta = {
+    description: 'Decide ENS Labs\' next steps in the eth.link litigation, and consider reimbursement for ENS Labs\' legal expenses in this case.',
+    emoji: '📖',
+    contributors: [
+        'arachnid'
+    ],
+    proposal: {
+        snapshot: '0x456ccb438eed5d189cbe51e5e36a88d2bb4dc0c61f12f6d9e310a7ba4798d5fc',
+        type: 'social'
+    }
+};
+
+# [EP5.2] [Social] Determine ENS Labs' next steps in eth.link litigation
+
+## Abstract
+
+Since 2017, ENS Labs has been operating eth.link as a public gateway for the Ethereum community, providing access to ENS+IPFS sites. Eth.link has been used by some of the largest projects in the space, including Uniswap.
+
+Eth.link was kindly delegated to ENS Labs for this purpose by its owner, Virgil Griffith. In August 2022, a dispute arose between ENS Labs, Dynadot, GoDaddy, and Manifold Finance about ownership of eth.link after the transfer and auction of the domain without ENS' consent. The highest bidder for eth.link at the auction was Manifold Finance, who expressed their intention to [operate the service themselves](https://twitter.com/foldfinance/status/1566200320375476225). A full recitation of the facts surrounding the dispute can be found within [the complaint that ENS Labs filed](https://drive.google.com/file/d/1951CeiKQZ4jQvcpjKU53BnugVedIf8go/view?usp=sharing) in September 2022.
+
+Before the domain could be transferred, ENS Labs and Virgil successfully obtained a preliminary injunction from a federal district court judge in Phoenix, Arizona. The Court ordered that Dynadot had to immediately return eth.link to ENS Labs. Since then, this litigation has been proceeding slowly through the courts. ENS Labs had to enforce the preliminary injunction as to Dynadot and Manifold Finance exited the lawsuit on jurisdictional grounds. Settlement discussions between the parties indicated that Manifold Finance should be included in any global settlement because of its potential claims to eth.link and against Dynadot.
+
+Recently, Manifold Finance has extended a settlement offer. They are demanding $300,000, along with confidentiality and non-disparagement clauses. In return, they are offering an allparties settlement, which would result in the dismissal of the case and ENS Labs retaining the eth.link domain name.
+
+ENS Labs believes that this is the appropriate juncture to solicit the DAO's input on how to proceed with the litigation. We are thus asking the DAO to instruct ENS Labs on the next steps to take in this case, whether that be agreeing to the settlement, offering a compromise amount, continuing the lawsuit, or dismissing the matter altogether, which would relinquish ENS Labs' possession of eth.link. Thus far, ENS Labs has been funding this litigation from its own finances. Our expenses so far amount to approximately $750,000. Continuing the case is likely to incur substantial additional costs.
+
+Further, given the criticality of eth.link to the ENS ecosystem, we would like to request reimbursement from the DAO for the legal fees incurred in protecting possession of eth.link.
+
+## Specification
+
+This will be an approval vote, with four independent items:
+
+1. Do you approve the proposed settlement?
+2. Do you approve of offering a compromise amount?
+3. Do you approve of continuing the litigation?
+4. Do you approve reimbursing ENS labs for its legal expenses involved in pursuing this case?
+
+You should vote on each outcome you would be happy with. For example, if you would be happy with either continuation or a compromise settlement, but not the full amount, you would vote for options 2, 3 and 4. If you prefer that the case be dismissed, vote only for option 4, or for no options.
+
+If the reimbursement is not approved, or none of the options receive a majority (50%) of approving votes, ENS Labs will:
+
+* Promptly post an interstitial on eth.link, warning users of the potential change in ownership and functionality of the domain, and offering alternatives including eth.limo.
+* Dismiss the litigation without delay and without unnecessary further expenditure of funds.
+
+Based on the outcome of the vote, ENS Labs will proceed with the case based on whichever of the courses of action (settlement or continuation) receives the higher proportion of approving votes. Subsequently, ENS Labs will post an executable proposal seeking reimbursement from the DAO for its legal expenses pursuing the case.