Accountablity: [EP 5.29] Funding request for Unruggable

[clowes.eth]

I wanted to follow up on the accountability that we have built into our executable proposal.

This includes providing the calldata necessary to cancel our streams at any time should we not deliver on our promises.

---

Our executable was built using the following GitHub repository: GitHub - unruggable-labs/unruggable-stream

This codebase:

• Generates the calldata for setting up both our requested Superfluid USDC stream and our Hedgey ENS token stream.

• Simulates execution of these transactions using Tenderly.

USDC Stream

• approve - https://www.tdly.co/shared/simulation/7a33ba80-767d-4764-891f-b93690ad7b25

• upgrade - https://www.tdly.co/shared/simulation/d564e4b9-3c5d-4e90-91f7-9ae78e32fbd1

• setFlowrate - https://www.tdly.co/shared/simulation/725d872b-8174-4fa5-a60b-5d45eea1812f

• increaseAllowance - https://www.tdly.co/shared/simulation/d94d705b-0025-4500-b5d0-e4eba5221abe

ENS Stream

• approve - https://www.tdly.co/shared/simulation/82838efa-2dda-4660-abf7-991f2787388a

• batchVestingPlans - https://www.tdly.co/shared/simulation/d33f9323-8ec0-4402-a458-265b7fa546f7

Delegates are able to see, and confirm exactly what the proposal executes.

In addition to this, we are providing calldata for cancelling both of these streams should Unruggable not deliver on their promises.

• Cancel Superfluid Stream

• Cancel Hedgey Stream

We have also provided milestones within our proposal:

@clowes.eth

We are adding the following milestones for accountability.

1. Recruitment: Hire a DevOps Engineer and a Blockchain Engineer to lead infrastructure deployment, and performance optimisation.
   2.Timeline:* Complete hiring by Q1 2025.
2. Production Gateway Deployment: Launch scalable, redundant gateways across five chains (Arbitrum, Base, Linea, Optimism, and Scroll) in five globally distributed regions (North America, Europe, Asia-Pacific, Middle East/Africa, South America).
   4.Timeline:* Deployment complete by Q1 2025.
3. Infrastructure Optimisation: Finalise infrastructure design and demonstrate cost reductions through performance and efficiency optimisations.
   6.Timeline:* Initial optimisation complete by Q2 2025, with ongoing improvements.
4. L2 Collaboration and Documentation: Collaborate with L2 developers to enhance gateway compatibility and API stability. Publish documentation detailing performance improvements and best practices.
   8.Timeline:* Ongoing, with quarterly reports.
5. Resiliency Benchmark: Maintain 99.9% uptime (excluding external dependencies) over a monitored evaluation period, with transparent reporting on outages and performance metrics.
   10.Timeline:* Achieve benchmark by Q4 2025.

And have adapted our ENS token request to have a 1 year cliff as visually shown in the below graph.

If for any reason delegates decide to cancel our stream within the first 12 months, the ENS tokens will immediately be returned to the DAO Wallet (TimelockController). This is clearly illustrated in this Tenderly cancellation simulation.

This is true DAO led decentralised Governance whereby everything is explicitly on chain, and cancellable at any time should we not execute to an ENS worthy standard. There are no up-front lump-sum payments.

We acknowledge that many prefer that we wait to use the next iteration of the Service Provider program. We support the program and are very appreciative of it.

We have requested funding directly from the DAO because we feel that it is in the best interest of the ENS DAO to support our work on production gateways with a stable funding stream. This will allow us to expand our team with exceptional talent and focus on delivering on our milestones.

We look forward to working collaboratively with the entire ENS community in 2025 and beyond to make ENSv2 a resounding success.