[EP 6.49] SPP3: Cohort Recommendation

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
Goldsky 1 $450,000 Link
Unruggable 1, 2 $400,000 Link
Fluidkey 1, 2 $340,000 Link
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)

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)

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)

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)

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

The committee is publishing decline rationale in aggregate, not per applicant. Individual applicants have been contacted directly. Declines fell into a small number of recurring patterns, and most declined applications exhibited more than one:

  • Overlapping deliverables. The applicant pool contained multiple marketplaces, multiple subname providers, and multiple indexing proposals. Funding duplicative work reduces total program value, so where proposals overlapped, the committee selected one and declined the others. Several declined teams scored competitively; redundancy, not quality, was the deciding factor;
  • Budget scale relative to the envelope. Some requests would have consumed a disproportionate share of the ~$3.25M pool relative to the outcomes they could credibly claim as uniquely theirs to deliver. A high rubric score does not obligate an award the budget cannot justify;
  • Business-development-only proposals. Standalone BD proposals consistently underestimated what closing an ENS integration actually requires. The committee’s view, reinforced across interviews, is that BD lands best when it comes from teams already building the product being sold, and the funded cohort carries BD capacity on that basis;
  • Milestone and scope weaknesses. Activity-framed milestones with no verifiable outputs, and scopes mismatched to the requested budget, scored poorly under the published rubric.
  • Right work, wrong program. A meaningful share of declined applications proposed good, discrete work: a tool, an integration, a one-off build. The SPP funds ongoing service relationships with a $200,000 floor, and stretching a discrete project into a 12-month service scope weakened otherwise credible proposals under the rubric. These declines are a judgment about program fit, not about the value of the work. The committee considers this a significant finding of the cycle. There is demonstrated demand for discrete, sub-$200K funding that no active program serves. The committee recommends the DAO establish a continued grants program to fill that gap. Several of the teams declined this cycle would be strong candidates for it.

One application was disqualified at the eligibility gate; its primary value accrues outside the ENS ecosystem, which the ratified program excludes.

The cohort includes no Category 3 (DAO Infrastructure) provider. The ratified program does not require the committee to fund every category, and the committee judged that none of the Category 3 proposals justified funding against the pool as a whole.

Process

All qualifying applications were evaluated by all members unless recused. Structured interviews were held with each qualifying team in a consistent format. Scoring was compared across members and outlier spreads were discussed before the committee converged on the cohort. The no-backchanneling rule held for the full cycle; all applicant contact ran through the structured process. One recusal occurred and is disclosed above. The review window was extended past the original timeline to complete interviews and negotiation properly, with submissions closing June 4 and review concluding the week of June 23.

The recommendation is take-it-or-leave-it by design. That design was ratified by the DAO in May precisely so that delegates vote on a deliberately composed cohort rather than re-running the evaluation themselves.

Delegates who disagree with the composition may vote against it, and the committee may revise and resubmit up to two times.

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. Source: Github.

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, 9,000e6) - committee chair 9k USDC.
  7. USDC.transfer(sovereignsignal, 7,000e6) - committee member 7k USDC.
  8. USDC.transfer(austingriffith, 7,000e6) - committee member 7k USDC.
13 Likes

We’re honored that you have chosen EthID for SPP3. As per our conversation earlier today, we have decided to decline SPP3 funding due to recent events with ENS. We’re grateful for the funding we received from past rounds, and we wish everyone luck.

More on moving on from ENS on twitter

8 Likes

I am disappointed to hear that because your application was one of the strongest and I believe deserves a top slot for funding.

I understand there have been events and discussions which have unfolded since the start of this process, and I imagine this was not an easy decision for you and your team.

10 Likes

Congrats to the cohort :confetti_ball:

It’s refreshing to see a enterprise player like Goldsky join the ranks and help influence a productive season.
Although as far as I can tell their eRPC offering seems to be proprietary and private. Is it safe to assume that the Foundation will be respectful and grant a exception to the open-source requirement?
Forcing a provider to expose proprietary system might produce a chilling effect in future cohorts and applications.

1 Like

Honoured to see Goldsky as a selected provider for SPP3, and for our team to play a more formal role in the ENS ecosystem as a result.

We’re grateful for the opportunity, and look forward to next steps.

4 Likes

eRPC is fully open source with an Apache 2.0 license (which in spirit is very similar to MIT). The other core piece of technology being leveraged, Streamling, is also open source, and while the core there is FSL, all ENS-related work will be a separate repo with a more permissive MIT / Apache license as well. This means that all work done as part of SPP3 is public and open for others, and adheres to the open-source requirements laid out by the program in full.

3 Likes

Thank you for the continued trust in us and in our work!

We’re honored to be part of SPP3 and excited for the 3rd year. :saluting_face:

Congrats to the rest of the cohort as well!

Looking forward to continuing to work with existing SPs and getting to know the new ones.

P.S. @brantlymillegan, for what it’s worth, I’m disappointed and sad to hear this too. I, like many others, have always appreciated having you as a colleague, ENS ecosystem contributor and service provider, and having your voice in the DAO.. and if possible, I hope you’ll reconsider.

15 Likes

Thank you for your trust! We’re extremely excited and grateful for the opportunity to make stealth address privacy more widely available to ENS users and integrators.

Congrats to all other projects selected!

6 Likes

Thank you for supporting our research and development work for ENS! We are incredibly grateful to the committee and delegates for your trust in our team.

Over the next year, we’ll continue focusing on two areas we believe are critical to ENS’s future:

• ENS × AI. Helping ENS become the identity layer for AI agents through initiatives like ENSIP‑26 (ens8004.xyz).

• Interoperability. Continuing our work on on.eth with the Ethereum Foundation and EthLabs, putting ENS at the center of how onchain chain data is discovered and resolved across the Ethereum ecosystem.

We’re excited to keep building.

11 Likes

This is a very well-written report, and I appreciate the level of detail given about the applications that were selected. All teams presented here are are very high-quality projects, and I am thankful for the committee’s professionalism and hard work handling so many applications. I think this process was much better than last year.

That said, as we are weighing the recommendations made here, it’s important to keep in mind the theme for this year’s SPP3 is supposed to be all about growth:

The program authorization thread stated:

Across all categories, growth in ENS registrations and integrations is a primary outcome the program is desires to advance.

Additionally, the rubric thread presented this as having the largest impact (40%):

Registration growth is the program’s first-order outcome. Every application receives explicit evaluation of how it connects to ENS registrations, renewals, and ecosystem utility.

In the report above, the majority of the focus appears to be centered on providing existing infrastructure: indexers, gateways, ENSv2, access to resolvers. While these services are certainly essential to the ENS ecosystem (and should be funded), it is not clear why we would expect adoption to increase by simply continuing to provide the same services we already do.

I do not see any mention of innovation, new user demographics to target, or partnership opportunities that are intended to make ENS the center of the conversation. This is what I would hope to see from a program focused on growth.

It could be that EthID’s proposal was meant to single-handedly drive adoption, but now that they have dropped out, the program’s number 1 goal is the only surface area not covered by this recommendation.

Should the committee consider reallocating EthID’s budget towards other proposals which are focused discretely on growth and adoption?

10 Likes

Thanks for the transparency in this recommendation. The reasoning is clear and the committee’s framing around “right work, wrong program” resonates with us directly — we were one of the teams that didn’t make it through.

We build Colibri, a trustless stateless Ethereum client. Our SPP3 application focused on proof-based ENS resolution: making name resolution cryptographically verifiable at the application layer, without trusting any RPC provider. The KelpDAO exploit in April showed exactly what happens when the read layer is trusted rather than verified — $292 million lost, no smart contract broken, the access path was the attack surface. ENS resolution runs on the same access path.

The case we want to leave on the table: ENS adoption depends on wallets and dApps integrating ENS names into user-facing flows. That integration stalls when developers can’t guarantee that the address they resolved is the address actually on-chain. Verified resolution removes that blocker. It doesn’t drive registrations directly — but it removes a structural reason not to integrate ENS in the first place. Privacy at the resolution layer does the same for users who don’t want their lookup patterns observable.

With EthID withdrawing, the DAO now has a genuine question in front of it: how should the freed-up budget be reallocated? We’d argue that building the conditions for sustainable growth — security and privacy at the resolution layer — deserves a seat in that conversation, not just a mention in the next grant cycle.

We’re open to that discussion here or directly with delegates.

1 Like

Thank you for the consideration and very detailed and transparent recommendation.

As a CEO of ENS Vision (ensvision.com) I would like to plead for reconsideration of ENS Vision’s application due to EthID declining their grant recommendation.

I agree with jkm.eth in stating that in the SPP3 round current application and recommendation there is no program for user growth which is direct fact of ENS DAO revenue generation.

  • ENS Vision has been by far the largest contributor to ENS DAO treasury in the past 4 years.
    We have generated over 4500 ETH directly to the treasury with our bulk register and renew contracts and subdomains contract. Indirect influence of ENS Vision in promoting ENS throughout the social networks and IRL events cannot be measured but are definitely significant aswell.

  • Feel free to check all of our contract addresses from April 2022 until today as proof of what we delivered and how much revenue we generated and of course our abilities to do so in the future :

**0x78FE5B15685555EC0972272B826Cd8E7FF8790B2 **
**0x409A1Ea957B38517d395306c53Fcb553EefA7262 **
**0x9996FCFa25B234e80BcF876d83d2e7F338F9BDA5 **
**0x000000000000509081d6fcd3ee63e791ad1db763 **
**0x00000000008794027c69C26D2A048DbEc09DE67C **
**0xb3f4598d27bc18f3a7e155dba5e31083c9e1ec3f **
**0xD421895EC9FB4d6605246a9e8bab69A9419FFA1D **
**0xF5925E20e3F4002bA17130641A87f574c71A8B3c **
**0xfca3df2bcd9c3d594923ffae0f132bfa1e8297c4 **
**0x2935e24631E8F8Ed63E34f325AB967f09E9f7701 **
0x36C496cEA362dd5eE5d78E8B02Ba0Bb519c019dC

  • The SPP3 program puts a heavy accent on revenue generation and audience acrual which ENS Vision has proved in it’s 4 years of existence like no other provider.

  • The application itself was modest with realistic goals as the budget is limited and there was a number of applicants, but I assure you we can provide much more.

ENS Vision believes a better relations with existing users and bringing new users is very important, not just the tech itself, we have 4 years of history proving that we bring quality not only in tech but all aspects.
The tech is amazing but will not sell on it’s own.

Along with continuous “default” development and improvals on Vision UI/UX and all it’s functionalities, SEO growth and expansion, we presented a one year plan with tech development and BD, adding MCP servers to Vision functionalities and a real AI search (with serious weight, done properly and perpetually upgrading) we would like to add a few opinions for the commitee’s and ENS DAO consideration :

  • Development in ENS is very important but the missing ingredient is business and marketing, which is exactly what we presented in our application. Without good business and marketing (sales) solution, which is at the moment ENS’s weakest link, the biggest loss is revenue decrease.

  • ENS Vision doesn’t think adding more and more features, functionalities and categories to the marketplace are crucial to reviving and expanding .eth audience - but actually bringing more users. They are very useful tools but for a perpetually expanding and experienced audience which we have not seen since 2022.

  • Adding quality AI search with connection to top rated linguistic websites brings actual meaning - etymology, synonyms, cultural context, word relationships - not just AI related word strings, has a wider perspective on bringing new users than any category or feature.

  • ENS itself doesn’t do direct consumer marketing on .eth - yet it is the main revenue stream.
    That leaves a gap the size of the entire crypto user base — millions of people who already hold wallets and use dApps, but have never registered a .eth name because nobody ever showed them why they should.
    We talk to them. Vision has the largest ENS-focused community on X (20K+), we’ve got four years of proof that we can convert crypto-curious audiences into ENS registrants. We’re not competing with anyone. We’re doing the end-user acquisition that was never prioritised.

The marketing campaign we suggested in the SPP3 application document is a sum-up of our ideas with humble budget but should be elaborated more :

  • Precision marketing targeting - example : users with subdomain usernames from projects like uni.eth, linea.eth, cb.id etc were never targeted to come closer to ENS, to find the root, the parent .eth (and the beauty of all of it’s utilities)
  • target existing NFT audience (ENS is also an NFT)
  • reviving of the “lost” audience (loyalty rewards program with AI search tokens etc)
  • simplified educational materials (ENS has been too technical for an end-user)

In conclusion, I would evaluate ENS Vision both as a development and business solution as our history clearly shows.

Thank you for considering ENS Vision as a potential Service Provider.

5 Likes

The exclusion of EthID is a significant change to the presented cohort.

I will provide a response to the outstanding questions and updates on next steps later today.

4 Likes

Thank you for the explanation.

Congratulations to the teams who were selected.

Two questions:

  1. Will be the form for providing feedback be shared? It was my understanding that it was going to be shared alongisde the cohort, mainly because as an exercise of transparency, not only the form but the results of the form should be shared publicly.
  2. Can the teams have access to the rubrics with their points? This is a learning process for a lot of the applicants, and it would be healthy to have a sense making on what were the weak/strong points based on the rubrics.
2 Likes

I’d like to also urge the committee to examine the impact of EthID’s withdrawal. There may be other candidates who were passed over because EthID’s contributions overlapped with theirs, who now warrant re-evaluation. There’s also SIWE, an important effort that Jalil has signaled an interest in continuing separate from EthID.

7 Likes

On EthID’s withdrawal

EthID’s withdrawal removes $1,200,000 from the recommended cohort. Combined with the originally unallocated remainder, $1,560,284 of the authorized SPP3 budget is now uncommitted.

After much deliberation today, the committee has decided that the cohort is not being recomposed. The committee will proceed with the remaining four providers (Namespace, Goldsky, Unruggable, and Fluidkey) at a total of $1,690,000.

Losing EthID does not leave the cohort devoid of growth orientation. Namespace runs a full BD operation pushing ENS into wallets, payments, and fintech. Unruggable is building the on-ramp for agent identity, a new class of registrant. Fluidkey opens ENS to privacy-conscious users, and Goldsky gives integrators reliable indexing to build on.

However, not having a funded marketplace leaves a significant gap in the program’s primary objective of funding providers that grow ENS registrations and integrations.

The committee will therefore suggest rolling the remainder of the funding into an RFP specifically for a marketplace provider. Exact details are forthcoming, but it is expected to have an aggressive timeline, require no new funding, and not delay the selected cohort. (cc: @jkm.eth @furyan.eth)

SIWE

The committee cannot fund a team that did not submit an application. EthID applied and was evaluated as a whole team with a defined scope; carving SIWE out and awarding it separately would constitute a new application that never went through the process.

That said, SIWE is a prime example of high-value work the committee recommended should be evaluated under a grants program, should these types of programs continue. (cc: @nick.eth)

Transparency

@vegayp:

  1. A feedback form is live here: SPP3 Feedback Form. It is anonymous, and results will be shared with the DAO once responses are in.
  2. Yes. Any applicant may request their own aggregated rubric scores via Telegram and the committee will provide them privately.

Next steps

With EthID’s exclusion and the marketplace RFP being drafted, the executable proposal is pushed to Wednesday, July 8th. The cohort proposal goes up on that date regardless of where the RFP drafting stands, pending payload review.

Current drafts have that proposal carrying two actions:

  1. Ratifying the four selected providers
  2. Authorizing the uncommitted remainder for awards under the marketplace RFP

The cohort will not be dependent on a passing RFP component, and no new funding is requested beyond the budget the DAO ratified in May. The full RFP framing, including scope, award structure, and timeline, will be posted for discussion before the RFP opens.

For the four selected providers, nothing changes: Award Notices have been sent to the ENS Foundation for KYC, the proposal is scheduled, and streams turn on after the passing proposal as outlined in the original post.

4 Likes

Just a procedural question: if we are expecting delegates to review and approve or deny the committee’s recommendation, shouldn’t the chosen applicants’ proposals be published so delegates know what scope of work they are authorizing?

1 Like

I edited the original post to include pinned links to the applications. I also updated the table to reflect EthID’s declination.

1 Like

This proposal is now live for voting on Anticapture: https://app.anticapture.com/ens/proposals/30153206728472299340257495645753485226870528642942223493225654414745632348879

Thanks to @blockful for the assistance with the payload and review.

2 Likes

Live proposal calldata security verification

Proposal is now live on-chain.

We reconstructed all transactions and confirmed they match the on-chain calldata. The proposal simulates the full lifecycle (propose, vote, queue, execute) and produces the expected outcome:

  • Master USDCx stream from the timelock to the Stream Management Pod set to $3.21M/yr (down from $4.5M): the SPP3 cohort ($1.69M) + the continuing SPP2 two-year streams ($1.4M) + the committee salary streams ($120k, the 80% streamed portion).
  • One month of funding plus a $250k transition margin wrapped, the margin sent to the pod, and
    the autowrap allowance refreshed.
  • Committee 20% upfront paid in USDC: $9k to the chair and $7k to each of the three
    compensated members.

The simulation and tests of the live proposal are available here.

To verify locally:

  1. Clone: git clone https://github.com/blockful/dao-proposals.git
  2. Checkout: git checkout 04d349a
  3. Run: forge test --match-path "src/ens/proposals/ep-6-49/*" -vv

Operational note: this executable reduces the master stream immediately, but the pod-side
switch (stopping the retired SPP2 streams and starting the SPP3 provider and committee streams)
is a separate MetaGov Safe transaction. The $250k margin keeps the pod solvent for ~71 days
after execution, so that switch should be done well within that window to avoid stream
liquidation.

1 Like