ACTIVE

Ends Dec 24 at 4:35 AM UTC

[EP 5.29] Funding request for Unruggable to build and operate a network of gateways supporting the rollout of ENSIP-19: EVM-chain Reverse Resolution

Proposed byBy

0x9831...6744

on Dec 17

Skip to Votes

Temp Check Discourse link

Description

Summary

We are requesting funding from the ENS DAO to build a production network of gateways. These gateways will support the rollout of reverse resolution for Arbitrum, Base, Linea, Optimism, and Scroll. We also plan to continue our research and development on the ENS protocol and actively contribute to the ENS ecosystem with a focus on resolving names from L2s. Our funding request focuses on infrastructure, talent acquisition and retention, and ongoing development to sustain this critical ENS infrastructure.

Request

We are requesting $1,200,000 USDC annually and 24,000 ENS tokens (vested over 2 years with a one year cliff).

This request gives consideration to the feedback on our Temp Check on the ENS DAO forum.

Executable Code

This proposal constitutes two streams:

A stream of $1,200,000 USDC per year (12 months).
A stream of 24,000 ENS tokens over 2 years (24 months) with a 1 year cliff (12 months).

Both streams are controlled directly by the ENS DAO Wallet. They can be cancelled at any time with a DAO vote should Unruggable not fulfil their promises.

This calldata has been generated using thIs codebase: https://github.com/unruggable-labs/unruggable-stream/tree/3d3c49980defbab315b6e09385b22946dd9729b0, which generates and simulates execution of the below listed transactions.

Tenderly simulation links are listed below.

Stream 1 - $1,200,000 USDC.

Platform: Superfluid.

Superfluid is a tried and tested platform for streaming funds. It has been used for nearly a year now for [EP5.2] [Executable] Commence Streams for Service Providers.

Initialising the Superfluid stream involves 4 transactions:

Description	Target Name	Target Address	Function Signature	Function Arguments	Calldata [1]	Simulation
This function approves the Super USDCx contract to spend $100,000 of USDC on behalf of the sender, the ENS DAO wallet.	USDC	0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48	`function approve(address spender, uint256 amount) external returns (bool)`	`["0x1BA8603DA702602A8657980e825A6DAa03Dee93a", 100000000000]`	`0x095ea7b30000000000000000000000001ba8603da702602a8657980e825a6daa03dee93a000000000000000000000000000000000000000000000000000000174876e800`	Simulation
This function 'upgrades' $100,000 USDC from the ENS DAO wallet/'Timelock' to USDCx.	USDCx	0x1BA8603DA702602A8657980e825A6DAa03Dee93a	`function upgrade(uint256 amount)`	`[100000000000]`	`0x45977d03000000000000000000000000000000000000000000000000000000174876e800`	Simulation
This function sets up the stream to the Unruggable multisig wallet. [2]	Superfluid	0xcfA132E353cB4E398080B9700609bb008eceB125	`function setFlowrate(address tokenAddress, address receiverAddress, int96 amountPerSecond)`	`["0x1BA8603DA702602A8657980e825A6DAa03Dee93a", "0x64Ca550F78d6Cc711B247319CC71A04A166707Ab", 38026517538495352]`	`0x57e6aa360000000000000000000000001ba8603da702602a8657980e825a6daa03dee93a00000000000000000000000064ca550f78d6cc711b247319cc71a04a166707ab000000000000000000000000000000000000000000000000008718ea8ded5b78`	Simulation
This function increases the amount of USDC (owned by the ENS DAO wallet/Timelock) that the Autowrap strategy contract is able to spend.	USDC	0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48	`function increaseAllowance(address spender, uint256 increment)`	`["0x1D65c6d3AD39d454Ea8F682c49aE7744706eA96d", 1100000000000]`	`0x395093510000000000000000000000001d65c6d3ad39d454ea8f682c49ae7744706ea96d000000000000000000000000000000000000000000000000000001001d1bf800`	Simulation

Stream 2 - 24,000 ENS

Platform: Hedgey

Hedgey has been utilised by the ENS DAO for allocating delegateable ENS tokens to deserving ecosystem participants.

Initialising the Hedgey stream involves 2 transactions:

Description	Target Name	Target Address	Function Signature	Function Arguments	Calldata [1]	Simulation
Approve the `BatchPlanner` to spend 24,000 ENS tokens owned by the ENS DAO Wallet	ENS Token	0xC18360217D8F7Ab5e7c516566761Ea12Ce7F9D72	`function approve(address spender, uint256 amount) external returns (bool)`	`[ "0x3466EB008EDD8d5052446293D1a7D212cb65C646", 24000000000000000000000 ]`	`0x095ea7b30000000000000000000000003466eb008edd8d5052446293d1a7d212cb65c6460000000000000000000000000000000000000000000005150ae84a8cdf000000`	Simulation
Create the Vesting Plan. Tokens vested over 24 months, with a 12 month cliff. [3]	Hedgey Batch Planner	0x3466EB008EDD8d5052446293D1a7D212cb65C646	`function batchVestingPlans(address locker, address token, uint256 totalAmount,(address recipient, uint256 amount, uint256 start, uint256 cliff, uint256 rate)[], uint256 period, address vestingAdmin, bool adminTransferOBO, uint8 mintType)`	`["0x1bb64AF7FE05fc69c740609267d2AbE3e119Ef82", "0xC18360217D8F7Ab5e7c516566761Ea12Ce7F9D72", 24000000000000000000000, [["0x64Ca550F78d6Cc711B247319CC71A04A166707Ab", 24000000000000000000000, 1735065935, 1766601935, 380517503805175]], 1, "0xFe89cc7aBB2C4183683ab71653C4cdc9B02D44b7", true, 4]`	0x94d37b5a0000000000000000000000001bb64af7fe05fc69c740609267d2abe3e119ef82000000000000000000000000c18360217d8f7ab5e7c516566761ea12ce7f9d720000000000000000000000000000000000000000000005150ae84a8cdf00000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000fe89cc7abb2c4183683ab71653c4cdc9b02d44b700000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000100000000000000000000000064ca550f78d6cc711b247319cc71a04a166707ab0000000000000000000000000000000000000000000005150ae84a8cdf00000000000000000000000000000000000000000000000000000000000000676b014f00000000000000000000000000000000000000000000000000000000694c34cf00000000000000000000000000000000000000000000000000015a1422a526f7	Simulation

[1] You can deep dive into this calldata at the following link: https://ethtools.com/calldata-collections/unruggable-executable-proposal

[2] 38026517538495352 represents $0.038.. USDC per second noting that USDC has 18 decimals and there are 31556926 seconds in a year.

[3] period, and mintType arguments are taken from the Hedgey documentation: https://hedgey.gitbook.io/hedgey-community-docs/for-developers/technical-documentation/token-vesting/integration-and-direct-contract-interactions

Votes

Quorum progress: 94.42%

For votes: 944.21K

Against votes: 1.18M

0x5bfc...8390voted for

165.23K

After in depth consideration and discussion, we’ve decided to vote in favour of this proposal. Despite not following perfect procedure (especially considering the upcoming service provider streams discussion), we think the Unruggable team are an incredibly important technical contributor to ENS and should be supported.

0x89ed...aedcvoted against

143.01K

I believe the existing streaming system should be prioritized, and that it would make sense to leverage exiting service providers (for both cost savings and managing tremendous DevOPs loads). I have plenty of suggestions for a future proposal. Ask me. :)

0x2b88...7d12voted for

128.12K

https://discuss.ens.domains/t/temp-check-ep-5-29-funding-request-for-unruggable-to-build-and-operate-a-network-of-gateways-supporting-the-rollout-of-ensip-19-evm-chain-reverse-resolution/19902/76

0x8393...0780voted for

126.75K

Unruggable is ready to graduate out of the Service Provider program and build out their team to support ENS in a larger capacity. They are working on the most important feature - L2 Resolution, and I trust them to execute on that in coordination with ENS Labs, and other partners.

0xb8c2...67d5voted against

117.16K

Unruggable is a solid team, but this should be part of the streaming provider program. More detailed rationale here: https://discuss.ens.domains/t/temp-check-ep-x-x-funding-request-for-unruggable-to-build-and-operate-a-network-of-gateways-supporting-the-rollout-of-ensip-19-evm-chain-reverse-resolution/19902/70

0xe52c...d726voted for

115.75K

The ENS protocol is a Public Good. The revenue from the protocol flows to the ENS DAO to be used to maintain the protocol and fund other public goods. I dislike many things about this vote. While I would prefer this process to have unfolded differently, using the ENS DAO Constitution and Ethereum's Infinite Garden Principle as a guide, I believe that funding Unruggable's initiatives here is in the best interest of both ENS and Ethereum. https://docs.ens.domains/dao/constitution https://ethereum.foundation/infinitegarden

0x9831...6744voted for

111.79K

0x809f...f68evoted against

105.09K

I look forward to working with unruggable and funding their work in february, when the Service Provider program is renewed. If this was a smaller ask, or if the renewal of the program wasn't happening so soon, or if they were already been a service provider for longer, I would have voted for the proposal.

0x1d54...6359voted against

100.39K

I maintain my previous comment that Unruggable is one of the few service providers showing up daily for ENS; it’s clear they’re all in and have been of immense value. Despite this, I have unresolved concerns/questions about the procedures for graduating providers from the service provider program. I would rather see a scalable system for evaluation and graduation before bypassing the service provider program altogether. I also encourage Unruggable to heed the suggestions for interim or gap funding as needed. My previous comment here: https://discuss.ens.domains/t/temp-check-ep-5-29-funding-request-for-unruggable-to-build-and-operate-a-network-of-gateways-supporting-the-rollout-of-ensip-19-evm-chain-reverse-resolution/19902/30

0x7ae9...0c0bvoted for

92.17K

0x7265...e176voted for

89K

Unruggable has a proven track record, with many years of contributions to the ENS ecosystem. They built the Unruggable Gateways and have the skills needed for ongoing maintenance and improvements. The Service Provider program isn’t designed to support teams operating core infrastructure. Unruggable has demonstrated their reliability, and everyone agrees they have excelled so far. They are best positioned to operate the production gateways and maintain the core infrastructure they have built for ENS. Funding them will ensure they can continue this critical work, supporting ENS's L2 strategy.

0xe391...b406voted against

80K

While we all appreciate Unruggable's contributions to the ecosystem, this EP is premature and an overreach of what the service provider program is here for. For Service Providers to peel off from a generous funding program in order to establish individual streams (that again, are in an amount that the Program can provide for) is redundant from a process perspective. For that reason, I am against this EP.

0x4e88...cc93voted against

79.27K

0xf6b6...c863voted against

72.11K

0x54be...7ab6voted for

69.7K

My full reasoning for this can be found here https://discuss.ens.domains/t/temp-check-ep-5-29-funding-request-for-unruggable-to-build-and-operate-a-network-of-gateways-supporting-the-rollout-of-ensip-19-evm-chain-reverse-resolution/19902/82?u=simona_pop

0x5346...42cfvoted against

51.09K

Unruggable did a good job improving the EVM gateways, originally developed by ENS Labs. However, this proposal fails to demonstrate that Unruggable is the best team to manage global infrastructure. After all, the best sports car drivers aren’t typically the engineers who designed them.

0x92fe...915bvoted against

46.89K

0xd132...e948voted against

46.54K

0x1904...a561voted against

44.13K

0x48db...d85dvoted against

41.88K

0xbdb4...f1dcvoted against

40.78K

0xed11...bb04voted against

35.68K

0xbce3...776fvoted against

34.33K

0x8c28...425cvoted against

34K

0x225f...c3b5voted against

17.5K

0xf342...3329voted against

16.31K

This proposal bypasses the service provider programme and is being pushed forward prematurely, despite ongoing discussions and feedback. Such practices are detrimental to the ENS DAO.

0xd5d1...cf2cvoted against

15.93K

0xa786...77c6voted against

11.44K

I believe there are updates to the Service Provider Program, particularly the extension of funding terms beyond one year, that address Unruggable's core needs. This is in addition to the already gracious terms that are given to service providers. If this proposal fails to go through, I hope to see them apply to be a service provider again in the new year.

0x8f73...faa0voted against

10.61K

0x035e...17d3voted for

10.29K

0x4aa5...df66voted for

10K

We are the best placed team to manage the research into, and deployment of productionised gateways noting that we built the codebase and have the appropriate domain knowledge. We have an incredible, and well documented track record in the ENS ecosystem and our proposal is for streamed funding conditional on us executing our milestones. Thank you for your support !

0x60db...8d77voted against

10K

0x4dc9...865avoted for

7.05K

0x29a8...de70voted against

6.15K

0x3335...81e1voted for

5.79K

0xb7f4...500evoted against

5.58K

I have great respect for the content of the proposal, the proposal team and their track record. I also appreciate the recent clarifications and engagement about the proposal in the dicussion forum. It seems that one of the main motivations for this proposal is around limitations of the Service Provider Program and its funding process. Finally, after reading the threads and discussing with others, I feel it would be more beneficial for the ecosystem if the team were to address the limitations of the Service Provider Program in a separate proposal directed specifically at the Service Provider Program. With their deep understanding of the issues, they can help to improve the process of bringing more qualified, trusted service providers onboard to benefit the ENS ecosystem and ensure that ENS maintains its public good orientation as an open and inclusive ecosystem of builders, innovators and experimenters. Private domain naming services (that raise private funding, and have more stable funding horizons) have their own advantages, but also their drawbacks, and part of the discussion we are having reflects the tension that alternative models present. Of course we want to be fast, competitive and efficient, but we are also building intentionally, slowly, with an eye on the long-term as well as on inclusion. I have a lot of respect for the ENS team, the creators of the Service Provider Program and the spirit in which ENS operates, which has gotten us this far. ENS itself is a long-standing collective experiment, and one of the projects we can be most proud of in the Ethereum ecosystem. I unfortunately will vote against this proposal in the hopes the team will resubmit one or more proposals that address the two important take-aways I see from the past day's discussions. First, we need to ensure that qualified teams can be hired to develop important improvements to the system (+ that they feel valued + that they don't go elsewhere). And second, we *also* need to improve the processes through which ENS is run and by which ENS engages service providers going forward. As the Service Provider Program is only in its first year, I am hopeful that folks will continue to step up to improve it. Voting against, but in gratitude.

0xe11d...a20bvoted for

4.31K

generally for funding public good / open source development

0x866f...2fdfvoted for

4.18K

Tech and potential outcome is great, trust into the team behind is high, monetary risk is low… so I don’t see any reason not to vote FOR

0xbc8d...7c63voted against

3.8K

0x934b...d649voted against

2.2K

0xaa7a...7d66voted against

2.18K

0x8e8d...3216voted against

0x30c7...c702voted for

1.8K

0x179a...9285voted against

1.7K

While I appreciate Unruggable's technical contributions to ENS and CCIP Read gateways — and would support their continued involvement in the service provider program — I don't feel they are the best team to operate this infrastructure.

0xac50...c039voted for

0x8b1f...feffvoted for

698

Unruggable is an amazing team! I am proud to lead them as CEO and know that we will do a great job on gateways to support reverse resolution for Arbitrum, Base, Linea, Optimism, and Scroll. 2025 is going to be a fantastic year for ENS!

0x866b...5eeevoted against

569

Bypasses the stream provider program that funded these ecosystem projects. Did not demonstrate why the streaming provider program doesn't fit their need.

0x5a38...0615voted against

293

0x0253...d11avoted against

246

0x0579...4048voted for

239

0x50b6...5a18voted for

173

0xebaa...ab80voted for

152

0x8da4...81e4voted for

0x0151...c3b9voted for