# [Executable] SPP3 Marketplace RFP Award: Nomentum Labs (Grails)
https://discuss.ens.domains/t/spp3-marketplace-rfp-recommendation/22371
## Abstract
The SPP3 Marketplace RFP committee recommends Nomentum Labs, operating Grails (grails.app), as the Marketplace RFP awardee. The total award is $500,000, the maximum authorized under \[7.1] \[Social] SPP3 Marketplace RFP, consisting of a $400,000 base award and up to $100,000 released on performance-based traction gates. This executable moves the full award in USDC to the MetaGov Stream Management Pod (`stream.mg.wg.ens.eth`), from which it is released to Nomentum Labs under the Award Notice, after KYC. The awardee joins the SPP3 cohort's reporting and oversight structure for a term co-terminating with the cohort in Q3 2027. Unreleased funds return to the treasury at term end.
## Specification
The award moves to the MetaGov Stream Management Pod (`stream.mg.wg.ens.eth`, `0xB162Bf7A7fD64eF32b787719335d06B2780e31D1`) in three USDC transfers, one per tranche of the payment structure:
1. **$90,000 upfront:** released to Nomentum Labs in $30,000 monthly installments over the first quarter, subject to KYC and the executed Award Notice.
2. **$100,000 performance-gated:** held in the pod across four $25,000 gates and released only on verified results. Q1 2027: attributed protocol revenue at or above the at-signing baseline, and at least 150 distinct wallets completing value-transferring actions in the quarter. Term end: revenue on pace for $1,000,000 a year, and at least 250 ETH of filtered secondary volume over the prior two quarters. The revenue baseline is Grails's attributed revenue over the 90 days before signing.
3. **$310,000 as a stream:** opened by MetaGov from the pod on committee verification of the ENSv2 readiness milestone (target Q4 2026, or sufficient progress at the committee's judgment), running to term end. The $25,000 wind-down escrow is funded from the award when the stream opens.
Release mechanics (installments, gates, stream open, wind-down escrow) are executed pod-side by the MetaGov stewards using the existing custody structures. Unreleased funds return to the treasury at term end.
## Transactions
| Address | Value | Function | Argument | Value |
| --------------------------------------------------- | ----- | ---------- | -------- | --------------------------------------------------------------------- |
| `0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48` (USDC) | 0 | `transfer` | to | `0xB162Bf7A7fD64eF32b787719335d06B2780e31D1` (`stream.mg.wg.ens.eth`) |
| | | | value | `90000000000` (90,000 USDC) |
| `0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48` (USDC) | 0 | `transfer` | to | `0xB162Bf7A7fD64eF32b787719335d06B2780e31D1` (`stream.mg.wg.ens.eth`) |
| | | | value | `100000000000` (100,000 USDC) |
| `0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48` (USDC) | 0 | `transfer` | to | `0xB162Bf7A7fD64eF32b787719335d06B2780e31D1` (`stream.mg.wg.ens.eth`) |
| | | | value | `310000000000` (310,000 USDC) |
# [EP 6.49] SPP3: Cohort Recommendation
https://discuss.ens.domains/t/draft-spp3-cohort-recommendation/22237
# Summary
The committee recommends a four-provider SPP3 cohort totaling $1,690,000 of the \~$3.25M available under the ratified budget. The remaining is not allocated by this proposal.
The committee received 26 applications requesting a combined $12.2M. Each qualifying application was evaluated by every member unless recused, and a structured interview was conducted with each qualifying team.
One application was disqualified at the eligibility gate, the remaining 25 were scored against the published rubric. Five were initially selected with one (EthID) declining the offer
This proposal names the final four selected providers, states the rationale for each, publishes the committee's assessment, and explains in aggregate why the other applicants were not funded.
Per the ratified proposal, this recommendation will be submitted as an on-chain executable. If this proposal passes, streams will begin in accordance with the Award Notices pending the selected providers pass the KYC checkpoint.
## Cohort Scores
| Provider | Category | Award | Application |
| ---------- | -------- | -------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Namespace | 1, 2 | $500,000 | [Link](https://bronze-accused-porpoise-217.mypinata.cloud/ipfs/bafybeiee73y2jwinefaszeng3frn47wmqini562qtcibzgnh42cnqiu2la) |
| Goldsky | 1 | $450,000 | [Link](https://bronze-accused-porpoise-217.mypinata.cloud/ipfs/bafybeidblcll7pt7s4jzlte6khv7twiqnckdoalanj2aoemd27afefhyou) |
| Unruggable | 1, 2 | $400,000 | [Link](https://bronze-accused-porpoise-217.mypinata.cloud/ipfs/bafybeiedajocrvgfnj3y6ec2mrqyt62d46uiyfb6xyqraxyyosvto5tmyq) |
| Fluidkey | 1, 2 | $340,000 | [Link](https://bronze-accused-porpoise-217.mypinata.cloud/ipfs/bafkreiaplckhk72bu3wuxofgkbdoky7jb3o24kk7olbb6urfaquz2os4sm) |
| **Total** | | **$1,690,000** | |
\*sovereignsignal.eth recused from the Namespace evaluation and vote under the program's conflict of interest rules.
# The Cohort
The initial cohort presented included five selectees. The application from EthID was withdrawn. The remaining four will continue unaffected.
### Namespace: $500,000 ([Application](https://bronze-accused-porpoise-217.mypinata.cloud/ipfs/bafybeiee73y2jwinefaszeng3frn47wmqini562qtcibzgnh42cnqiu2la))
Namespace is a third-cycle provider and one of the ecosystem's primary subname infrastructure teams: SDKs, APIs, CCIP gateways, and custom deployments including Celo, Filecoin, and Rootstock. Their SPP2 subname issuance exceeded target by more than an order of magnitude, though the committee notes that figure is concentrated in a small number of large deployments. The SPP3 scope covers the ENSv2 migration of their onchain subname stack, continued maintenance of existing tooling, and business development. The award reflects the counterfactual: no comparable subname infrastructure exists at this scale, and the ENSv2 transition makes that infrastructure work time-critical. Key milestones depend on ENSv2 shipping to mainnet; the committee has accounted for this in the negotiated milestone structure.
\*sovereignsignal.eth recused from the Namespace evaluation and vote under the program's conflict of interest rules.
### Goldsky: $450,000 ([Application](https://bronze-accused-porpoise-217.mypinata.cloud/ipfs/bafybeidblcll7pt7s4jzlte6khv7twiqnckdoalanj2aoemd27afefhyou))
Goldsky, with eRPC, is funded to operate ENS indexing as a dedicated public service. The award reflects the expanded scope presented as Option B in their application, which the team confirmed at the committee's request before selection. Indexing is a shared dependency consumed across the ecosystem, and it has previously been funded as one component inside larger provider scopes. The committee's judgment is that a dependency of this weight is best held as a standalone mandate: one accountable owner, priced on its own merits, and decoupled from any broader award. Goldsky is new to the SPP and was evaluated accordingly. The team operates production indexing infrastructure across the EVM ecosystem at scale, and selection was conditioned on their explicit commitment to the full scope.
### Unruggable: $400,000 ([Application](https://bronze-accused-porpoise-217.mypinata.cloud/ipfs/bafybeiedajocrvgfnj3y6ec2mrqyt62d46uiyfb6xyqraxyyosvto5tmyq))
Unruggable is a returning SPP2 provider whose gateway infrastructure powers cross-chain resolution in production, including base.eth and ENSIP-19 reverse resolution. The SPP3 scope continues gateway operation and extends into developer tooling and interoperability R\&D. The committee funded the full ask on the strength of shipped, verifiable protocol infrastructure that ENS depends on today, and a delivery record with no abandoned commitments.
### Fluidkey: $340,000 ([Application](https://bronze-accused-porpoise-217.mypinata.cloud/ipfs/bafkreiaplckhk72bu3wuxofgkbdoky7jb3o24kk7olbb6urfaquz2os4sm))
Fluidkey is funded to build privacy-preserving ENS infrastructure: an ENSIP, wallet-agnostic contracts, and a resolver kit designed to be maintained independently of Fluidkey's own product. This is the smallest award in the cohort and the committee treats it as a deliberate position on an underdeveloped capability. The proposal cleanly separates the public-goods layer from the company's commercial product, budgets an audit, and self-funds its own reference integration. The registration upside is less proven than elsewhere in the cohort; the cost is priced accordingly.
## Committee Assessment
Scores are the mean of individual Member scores against the published rubric. Weights: Prior Delivery 25%, Scope Clarity 15%, Milestone Structure 15%, Adoption/Revenue/Utility 40%. The 5% discretionary component is excluded from the weighted figure, which is therefore out of 4.75. The Chair scored every application independently but Chair scores enter the mean only in the case of Namespace which saw a recusal, noted below. Individual scoring records remain internal working documents, available to the accountability body or ENS Foundation on request per the ratified proposal.
| Provider | C1 Prior Delivery | C2 Scope Clarity | C3 Milestones | C4 Adoption/Revenue | Weighted |
| ---------- | ----------------- | ---------------- | ------------- | ------------------- | -------- |
| Namespace | 4.1 | 3.4 | 3.3 | 3.5 | 3.43 |
| Goldsky | 4.0 | 3.8 | 3.4 | 3.3 | 3.37 |
| Unruggable | 4.5 | 3.4 | 3.1 | 3.0 | 3.30 |
| Fluidkey | 4.0 | 4.0 | 3.8 | 2.4 | 3.11 |
\*sovereignsignal.eth recused from the Namespace evaluation under the conflict of interest rules. The Chair's independent scores stand in for the recused seat on this row, keeping four scoring inputs.
## Why Applications Were Not Funded
This section removed to fit character limit. See full post [here](https://discuss.ens.domains/t/draft-spp3-cohort-recommendation/22237).
## Process
This section removed to fit character limit. See full post [here](https://discuss.ens.domains/t/draft-spp3-cohort-recommendation/22237).
## Next Steps
1. Award Notices have been issued to each selected provider for review; they will be finalized by the ENS Foundation
2. The executable proposal is scheduled for posting on Wednesday, July 8th.
3. Streams will turn on after successful completion of KYC and signing of Award Notices by both the selected providers and the Foundation.
# Specification
The attached payload includes five transactions that facilitate the provider and committee streams, and four transactions to pay the committee as defined in [\[6.42\] \[Social\] SPP3: Program Authorization and Committee Model](https://discuss.ens.domains/t/6-42-social-spp3-program-authorization-and-committee-model/22086#p-61193-term-and-payment-12). Source: [Github](https://github.com/blockful/dao-proposals/pull/93/changes#diff-abce5ec202f8620398bdf4ede6d54defa3acbee46708fd9b8fcc83e57d9e2e3e).
Nine transactions, all run by the timelock:
1. USDC.approve(USDCx, 517,500e6) - lets the USDCx contract pull the USDC we are about to wrap.
2. USDCx.upgrade(517,500e18) - wrap it. 517,500 is one month of the stream ($267,500) plus the pod margin ($250,000).
3. USDCx.transfer(pod, 250,000e18) - send the margin to the pod. It carries the pod through the overlap until the switch.
4. CFAv1Forwarder.setFlowrate(USDCx, pod, 101720934415475068) - set the master stream to $3.21M/yr.
5. USDC.approve(autowrapper, 4,547,500e6) - refresh the autowrap allowance (\~17 months, the ratio SPP2 used).
6. USDC.transfer(coltron) - committee chair 9k USDC
7. USDC.transfer(sovereignsignal) - committee member 7k USDC.
8. USDC.transfer(austingriffith) - committee member 7k USDC.
9. USDC.transfer(abdullah) - committee member 7k USDC.
# [EP 6.41] [Executable] Endowment permissions to KPK - Update #9
## Abstract
This proposal introduces a routine update to the permissions for the Endowment Manager. This update expands access to liquid staking and restaking protocols on Ethereum, adds exposure to Morpho USDT vaults, and extends CoW Swap routing to include weETH and eETH.
## Motivation
The update opens positions in Stader and Ether.fi, two liquid staking and restaking protocols that allow the endowment to earn yield on ETH while preserving the ability to exit via standard or express unstaking paths. Adding Morpho's KPK USDT Prime vaults (v1 and v2) provides additional yield opportunities on stablecoin holdings consistent with the Investment Policy Statement (IPS). Extending CoW Swap permissions to cover weETH and eETH supports efficient token management across the expanded position set. These changes are additive and consistent with prior endowment strategy.
## Specification
This proposal adds the following contracts:
### Additions
#### 1. Liquid Staking & Restaking
| Protocol / Contract | Description | Contract Address (Mainnet) |
| ----------------------------------- | ---------------------------------------------------------- | ------------------------------------------ |
| Stader / UserWithdrawalManager | Allows unstaking ETHx to receive ETH | 0x9F0491B32DBce587c50c4C43AB303b06478193A7 |
| Ether.fi / LiquidityPool | Allows staking ETH/WETH/stETH/wstETH/eETH to receive weETH | 0x308861A430be4cce5502d0A12724771Fc6DaF216 |
| Ether.fi / WithdrawRequestNFT | Allows unstaking eETH/weETH to receive ETH (Standard) | 0x7d5706f6ef3F89B3951E23e557CDFBC3239D4E2c |
| Ether.fi / EtherFiRedemptionManager | Allows unstaking eETH/weETH to receive ETH (Express) | 0xdadef1ffbfeaab4f68a9fd181395f68b4e4e7ae0 |
#### 
2\. Morpho Lending Markets
| Market | Description | Vault Contract Address (Mainnet) |
| ------------------- | ------------------------------------------- | ------------------------------------------ |
| kpk USDT Prime | Allows approvals, deposits, and withdrawals | 0xdaD4e51d64c3B65A9d27aD9F3185B09449712065 |
| kpk USDT Prime (v2) | Allows approvals, deposits, and withdrawals | 0x870F0BF29A25A40E7CC087cD5C53e70C11F2C8A8 |
#### 3. Other
| Protocol / Contract | Description | Contract Address (Mainnet) |
| ------------------------------- | ---------------------------------------------- | ------------------------------------------ |
| CoW Swap / Cowswap Order Signer | Expands swap routing to include weETH and eETH | 0x23dA9AdE38E4477b23770DeD512fD37b12381FAB |
## Reviewing Zodiac Roles Modifier Permissions Policy
To review, the following resources are below:
* **Payload:** [client-configs/clients/ens-dao/mainnet/payloads/ensPermissionsUpdate9.json](https://github.com/karpatkey/client-configs/blob/main/clients/ens-dao/mainnet/payloads/ensPermissionsUpdate9.json)
* **Tenderly Simulation:** [https://dashboard.tenderly.co/public/tallyxyz/project/simulator/59b3d7f8-3196-475f-bd87-097e8ef672c6](https://dashboard.tenderly.co/public/tallyxyz/project/simulator/59b3d7f8-3196-475f-bd87-097e8ef672c6)
## Next Steps
The proposal will be introduced in the next meta-governance call. Pending review from Blockful and no revisions following discussion during the meta-gov call, this proposal will progress to an on-chain executable vote.
# [EP 6.39] [Executable] Treasury Flow Automation
## Abstract
ENS protocol revenue currently requires three separate steps to move from registrar controllers to productive use in the endowment and fund operations. This proposal introduces a Registrar Manager contract that takes ownership of all registrar controllers and enables permissionless withdrawals directly to the endowment. It also configures a Zodiac module permission on the endowment to allow the treasury manager to send ETH and USDC to the timelock without a proposal, following a two-year stablecoin runway policy consistent with the current Investment Policy Statement.
The result is zero proposals for routine treasury operations, faster yield on collected revenue, permissionless withdrawals, and increased income for the DAO. A conservative estimate suggests that since January 2024, approximately $1 million in yield was missed due to idle capital in registrar controllers and the timelock.
## Specification
### Problem
ENS protocol revenue requires three steps to move from collection to productive use.
Registrar controllers collect ETH from .eth registrations and renewals, and the current controller (controller.ens.eth) already sends withdrawn ETH to the timelock. However, the old registrar controller at 0x283Af0B28c62C092C9727F1Ee09c02CA627eb7F5 holds roughly 772 ETH that requires a dedicated proposal just to withdraw.
Once ETH reaches the timelock, sending it to the endowment (endowment.ensdao.eth) for investment requires another proposal. Capital can sit idle in the timelock for several months before it starts earning yield.
When the DAO needs to fund operational expenses like ENS Labs, the Service Provider Program, or Working Groups, yet another proposal is needed to transfer from the endowment back to the timelock or to execute operations with [twap.ensdao.eth](https://etherscan.io/address/0x02D61347e5c6EA5604f3f814C5b5498421cEBdEB). For context, [EP 6.32](https://discuss.ens.domains/t/ep-6-32-executable-transfer-2-5m-usdc-from-endowment-to-wallet-ensdao-eth/21882) proposed a $2.5M USDC transfer from the endowment to the timelock just to cover Working Group budgets that had already been approved.
On top of that, there is currently roughly 4,148 ETH sitting in the timelock that could be earning yield in the endowment. The operational funding process today is reactive and not smooth. Each transfer requires a full governance cycle, and capital that could be generating yield sits idle throughout.
#### Key Addresses
• Timelock: 0xFe89cc7aBB2C4183683ab71653C4cdc9B02D44b7 (wallet.ensdao.eth)
• Current Registrar Controller: 0x253553366Da8546fC250F225fE3d25d0C782303b (controller.ens.eth)
• Old Registrar Controller (~772 ETH): 0x283Af0B28c62C092C9727F1Ee09c02CA627eb7F5
• Endowment: 0x4F2083f5fBede34C2714aFfb3105539775f7FE64 (endowment.ensdao.eth)
• Governor: 0x323A76393544d5ecca80cd6ef2A560C6a395b7E3 (governor.ensdao.eth)
• TWAP safe: 0x02D61347e5c6EA5604f3f814C5b5498421cEBdEB (twap.ensdao.eth)
### Solution
This proposal introduces two components that eliminate all three bottlenecks: a Registrar Manager and an Endowment Zodiac Module permission.
#### Registrar Manager
The Registrar Manager is a contract that becomes the owner of all registrar controllers. Its key properties:
a) Exposes a permissionless withdraw() function that anyone can call. When called, it pulls ETH from each controller and routes it directly to the endowment.
b) The destination address is configurable by the DAO through the timelock, so governance can redirect the flow at any time.
c) Acts as a pass-through for governance calls, meaning the DAO retains full control over controller parameters.
d) New controllers can be added over time.
e) Never holds funds.
[Source code of Registrar Manager contract.](https://github.com/blockful/dao-proposals/blob/ep-registrar-manager-endowment/src/ens/proposals/ep-registrar-manager-endowment/contracts/RegistrarManager.sol)
#### Endowment Zodiac Module
The Zodiac module is already part of how the endowment is managed. This proposal adds a scoped permission that allows the treasury manager (Karpatkey) to send ETH and USDC to wallet.ensdao.eth without a proposal. It cannot send to any other address or use any other token. All other endowment operations remain unchanged.
### Funding Policy
This is the current suggestion for the funding policy.
The timelock maintains a 6 months runway in USDC (~$8M at current spending). Each quarter, Karpatkey calculates the current runway on the timelock. If it falls below 6 months, the endowment sends the shortfall. If it exceeds 6 months, no transfer is needed and the excess stays invested in the endowment. If an additional governance proposal requiring capital is approved, this may trigger an earlier runway evaluation and transfer, consistent with this policy.
The initial policy is included in this executable proposal, so no separate vote is needed to get started.
Any future changes to the funding policy require a social vote. This establishes clear expectations about responsibilities and decision-making: the treasury manager handles routine rebalancing within the policy, and the community sets the policy itself.
This proposal remains aligned with the IPS. The required three-year stablecoin runway is calculated at the Endowment level, including stablecoins held and deployed there, as is currently done. The expansion guidelines reference transferring 33% of protocol revenue to the Endowment. This proposal modifies that mechanism by routing revenue directly to the Endowment to improve operational efficiency and capital deployment.
### Impact
The operational funding process is reactive, requiring a full governance cycle for each transfer. Meanwhile, capital that could be earning yield sits idle in controllers and the timelock for several months at a time.
With this proposal, capital flows from registrars to the endowment as soon as anyone calls withdraw(). The endowment begins generating yield immediately rather than after several months of governance overhead. Operational funding follows a clear quarterly process based on the two-year runway target, removing the need for ad-hoc proposals.
To put this in perspective: looking at the period from January 2024 until now, and considering ETH staking yields if this capital had been allocated to the endowment, a conservative estimate of $1 million in yield was left on the table. This is based on the balances held in the [timelock](https://etherscan.io/address/0xFe89cc7aBB2C4183683ab71653C4cdc9B02D44b7#analytics), the [current registrar controller](https://etherscan.io/address/0x253553366Da8546fC250F225fE3d25d0C782303b#analytics), and the [old registrar controller](https://etherscan.io/address/0x283Af0B28c62C092C9727F1Ee09c02CA627eb7F5#analytics) (which still have a relevant number of registrations). Going forward, every ETH collected will begin earning yield within days, compounding the DAO's income over time.
# [EP 6.38] [Executable] Endowment permissions to karpatkey - Update #8
## Abstract
This proposal introduces a **routine update** to the Endowment Manager’s permissions. The changes remove deprecated permissions no longer required and upgrade the Roles instance to the latest version.
## Specification
This proposal updates the Zodiac Roles Modifier configuration for the ENS Endowment by disabling the Roles V1 instance, updating the Roles V2 instance, and revoking token permissions that are no longer required.
The following permissions are added:
* Buy and sell GHO/FLUID via CoW Swap
* Claim rewards from the Fluid Merkle Incentive distributor
### Summary of Updates
#### **1. ZRM Instance Updates**
| **Roles Version** | **Action** |
| ----------------- | ---------- |
| Roles V1 | Disabled |
| Roles V2 | Updated |
#### **2. Permission Additions**
| **Roles Version** | **Action** | **Token Address (Mainnet)** |
| ----------------- | ------------ | ------------------------------------------ |
| Roles v2 | `buy` `sell` | 0x40D16FC0246aD3160Ccc09B8D0D3A2cD28aE6C2f |
| Roles v2 | `sell` | 0x6f40d4a6237c257fff2db00fa0510deeecd303eb |
| Roles v2 | `claim` | 0xF398E66B1273a34558AeBbEC550DccaF4AcC7714 |
> Added permission to Buy GHO and Sell GHO/FLUID through Cowswap
> Added permission to be able to claim GHO rewards from the Fluid Merkle Incentive
#### **3. Permission Removals**
| **Token** | **Functions Allowed** | **Token Address (Mainnet)** |
| --------- | --------------------- | ------------------------------------------ |
| SPK | `claim` `transfer` | 0xc20059e0317DE91738d13af027DfC4a50781b066 |
> Removed permission to claim and transfer SPK
## Reviewing Zodiac Roles Modifier Permissions Policy
To review, the following resources are below:
* **Payload:** [link here](https://github.com/karpatkey/client-configs/blob/main/clients/ens-dao/mainnet/payloads/ensPermissionsUpdate8.json)
* **Zodiac Diff Page:** [link here](https://roles.gnosisguild.org/eth:0x703806E61847984346d2D7DDd853049627e50A40/roles/MANAGER/diff/44zkxJCEz3H0WcK87fvtfsKSrqb3KtOdlx2NJlAWiw?annotations=false)
## Next Steps
The proposal will be introduced in the next meta-governance call. Pending review from Blockful and no revisions following the discussion in during the meta-gov call, this proposal will progress to an on-chain executable vote.
# [EP 6.37] [Executable] Transfer 900,000 USDC from Endowment to wallet.ensdao.eth
## Abstract
The ENS DAO timelock (`wallet.ensdao.eth`) currently holds insufficient USDC to cover stream payments claimable by ENS Labs. This proposal requests a **one-time withdrawal of 900,000 USDC** from the ENS Endowment's stablecoin runway to cover that shortfall, bridging operations while the DAO works through more automated solutions such as [Treasury Flow Automation](https://discuss.ens.domains/t/executable-treasury-flow-automation/21923) proposal by @blockful.
No new budget or funding program is created by this proposal.
## Motivation
The ENS DAO timelock (`wallet.ensdao.eth`) currently holds insufficient USDC to cover stream payments claimable by ENS Labs.
A transfer of **900,000 USDC** is sufficient to cover what is currently claimable by ENS Labs, enabling execution of previously approved governance decisions and maintaining operational continuity. No new budget or funding program is created by this proposal.
> **Note:** The root cause of these recurring shortfalls is being addressed structurally through the [Treasury Flow Automation](https://discuss.ens.domains/t/executable-treasury-flow-automation/21923/6) proposal, which aims to automate USDC top-ups from the Endowment and eliminate the need for one-off transfers like this one.
## Specification
Transfer **900,000 USDC** from the **ENS Endowment Safe** to **wallet.ensdao.eth (Timelock)**.
**Addresses**
| Label | Address |
|---|---|
| wallet.ensdao.eth (Timelock) | `0xFe89cc7aBB2C4183683ab71653C4cdc9B02D44b7` |
| ENS Endowment Safe | `0x4F2083f5fBede34C2714aFfb3105539775f7FE64` |
**Transaction simulation:** [Tenderly](https://dashboard.tenderly.co/public/tallyxyz/project/simulator/41ec6e27-0532-4efd-8377-ad130b2982cc)
**Transaction parameters:**
```
to: 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48,
value: 0,
data: 0xa9059cbb000000000000000000000000fe89cc7abb2c4183683ab71653c4cdc9b02d44b7000000000000000000000000000000000000000000000000000000d18c2e2800,
operation: 0,
safeTxGas: 0,
baseGas: 0,
gasPrice: 0,
gasToken: 0x0000000000000000000000000000000000000000,
refundReceiver: 0x0000000000000000000000000000000000000000,
signatures: 0x000000000000000000000000fe89cc7abb2c4183683ab71653c4cdc9b02d44b7000000000000000000000000000000000000000000000000000000000000000001
```
## Next Steps
Pending review from Blockful and no revisions following the discussion in during the meta-gov call, this proposal will progress to an on-chain executable vote.
# [EP 6.32] [Executable] Transfer $2.5M USDC from Endowment to wallet.ensdao.eth
# Abstract
Following the approval of the [\[Executable\] Collective Working Group Funding Request (Oct 2025)](https://www.tally.xyz/gov/ens/proposal/77525093718307720477107269225240955392442633055266271196124066559357053541713), the transactions included in that proposal cannot fully execute due to insufficient USDC in the ENS DAO timelock (`wallet.ensdao.eth`).
This proposal enables a **one-time internal transfer of 2.5M USDC** from the ENS Endowment to the ENS DAO timelock (`wallet.ensdao.eth`) to ensure execution of already approved governance decisions. It is an operational treasury action designed to maintain execution continuity without requiring ETH sales under current market conditions.
# Motivation
The Working Group funding proposal was submitted on January 22, 2026, and its execution tests were performed against the block in which it was created (block 24293146). At that time, sufficient USDC was available.
On January 25, 2026, Superfluid wrapped approximately 616K USDC using the AutoWrap functionality to fund SPP streams. When the proposal became ready for execution, it required 959K USDC, while the timelock held approximately 505K USDC.
As a result, the approved proposal cannot execute as intended. This creates immediate operational risk, including:
* SPP streams running out of funds and triggering liquidation on Superfluid
* Labs and service providers being unable to claim approved streams
* Failure of otherwise valid proposals due to insufficient timelock balance
* Increased dependence on additional governance cycles for routine treasury operations
Historically, the DAO has sold ETH to meet USDC-denominated obligations. However, given current market conditions, selling ETH to cover this shortfall is suboptimal. The ENS Endowment holds sufficient USDC reserves to cover near-term obligations. An internal transfer avoids unnecessary market impact and preserves overall treasury flexibility.
This action enables execution of previously approved governance decisions, maintains operational continuity, and provides the Meta-Governance Working Group time to develop improved processes to prevent similar situations in the future. No new budget or funding program is created by this proposal.
# Specification
* Transfer **2,500,000 USDC** from the **ENS Endowment Safe** to **wallet.ensdao.eth (Timelock)**.
**Addresses**
* wallet.ensdao.eth (Timelock): `0xFe89cc7aBB2C4183683ab71653C4cdc9B02D44b7`
* ENS Endowment Safe: `0x4F2083f5fBede34C2714aFfb3105539775f7FE64`
***
Acknowledgements: thanks to coltron.eth and the kpk team for the readiness and support to solve this together.
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
# [EP 5.5] Funding Request: ENS Public Goods Working Group Term 5 (Q1/Q2)
# Abstract
The ENS Public Goods Working Group requests funding of the below to **support operations until the September 2024 funding window**.
The Public Goods working group funds projects and builders improving the Web3 ecosystems. This funding stream is authorized in [Article III](https://docs.ens.domains/dao/constitution#iii-income-funds-ens-and-other-public-goods) of the ENS DAO Constitution. This funding supports initiatives related to open-source software, tooling, research and any practical implementations that broadly benefit a wide range of users of Ethereum and Web3.
This social proposal is submitted to satisfy the requirements set out in Rule 10.1.1 of the Working Group Rules ([EP 1.8](https://docs.ens.domains/v/governance/governance-proposals/term-1/ep12-working-group-rules)) and further required by [this snapshot proposal in Nov. 2023 modifying steward rules.](https://snapshot.org/#/ens.eth/proposal/0x26a5c8dec547837495707e70446d1e7cd874a91f75753c602998f6e70083a266) If this proposal is passed, the funding request will be included in a collective executable proposal put forward by all three Working Groups.
# Specification
The balance of the Public Goods multisig at the time of Snapshot contained 147.2k USDC and 33.5 ETH. 
If passed, this proposal will transfer 450.3k USDC and 21.5 ETH from the DAO wallet to the Public Goods working group to accommodate the proposed budget below.
## Balances (March 2024)\*
| **USDC** | **ETH** | **ENS** |
| :------- | :------ | :------ |
| 147.2k | 33.5k | 200 |
**\****Balances above reflect amounts at time of original proposal at time of Snapshot. Current balance information can be found at* [*https://enswallets.xyz*](https://enswallets.xyz/)*.* 
## Expected Spend (Through September 2024)\*
| **Initiative** | **USDC** | **ETH** |
| :------------------ | :------- | :------ |
| Large Grants | 387.5k | 0 |
| Small Grants | 0 | 50 |
| Bounties | 45k | 0 |
| Events + Hackathons | 115k | 0 |
| Discretionary | 50k | 5 |
| Total | 597.5k | 55 |
**\****Mult-sig contains 200 ENS that has no planned use. This may be transferred back to the DAO wallet during the term.*
***
# Description of Initiatives
## Large Grants
Grants up to 50k USDC with applications accepted on a rolling basis throughout the year-long term. Large Grants will resume in Q2. With five grantees completing milestones from last term, the budget includes remaining payouts yet to be disbursed. We plan to add at least two more grantees during Q2 while piloting new grants management software. In the second half of the year, we will run another full-size round supporting up to 10 grantees at a time with a 200k USD total prize pool.
## Small Grants
Multiple micro-grantsvoted on by the community. Small Grants will resume during the first half of the year shortly after ETHDenver. We have added the amount expected to spend through the end of the year with no increase from last term. This is approximately 12.5 ETH per quarter. With market fluctuations, stewards may right-size and lower the amounts distributed during round
## Events and Hackathons
The working group will support Public Goods events and hackathons. Funds have included expenses related to the funding of hackathons, events, and related participation in events (judging, panels, speaking) where necessary.
The current earmarked events are:
* [ETHGuatemala](https://ethereum.gt/)
* [EthLatam](https://ethlatam.org/)
* [ETHGlobal London](https://ethglobal.com/events/london2024)
* [ETHCanal](https://www.ethcanal.xyz/)
* [ETHCC](https://ethcc.io/)
* [ETHGlobal Brussels](https://ethglobal.com/events/brussels)
* [DAO Tokyo](https://dao-tokyo.xyz/)
* [ETHGlobal San Francisco](https://ethglobal.com/events/sanfrancisco2024)
* [ETHGlobal Bangkok](https://ethglobal.com/events/bangkok)
* [Devcon](https://devcon.org/en/)
This list is not guaranteed as several events are still in the planning stages. The PG stewards will continuously assess opportunities to expand the public goods conversation and collaborations.
## Discretionary
The funds in this initiative are reserved for additional grant opportunities and expenses that arise during the term. Spending on this initiative is at the discretion of the working group stewards.
eth.ens.delegatehttps://discuss.ens.domains/t/ens-dao-delegate-applications/815/1191coltron.eth@protonmail.comhttps://www.vote-coltron.xyzThe public identity address of Coltron.ethENS, Delegate, Steward, Community