Hey everyone, first, a sincere thank-you to the MetaGov stewards (s/o @daostrat.eth @netto.eth @5pence.eth ) for making room on short notice for us to walk through this proposal during the most recent call. We appreciate the chance to field questions directly and to clarify how Tally hopes to serve the ENS DAO going forward.
–
1. How does this proposal relate to Dennison’s “ Programmatic Tooling Rewards ” concept?
Dennison’s post outlines a baseline funding framework to keep essential governance rails - actions like proposal creation/execution, voting, delegation, up and running in a sustainable way. Our proposal tackles a different (and, we believe, complementary) layer:
-
Customisable Webhooks – real-time notifications tied to ENS governance events (draft, on-chain publish, quorum reached, execution, etc.) that can pipe into Slack, Discord, or any endpoint the DAO chooses.
-
Deep ENS & Namechain Integration – indexing CCIP-Read and wildcard sub-registries (e.g., *.cb.id, *.fcast.id) with signature verification, action to ‘Update ENS record’ which lets all DAOs on Ethereum mainnet easily modify text records directly from a proposal, and day-one support for the forthcoming Namechain migration.
-
Enterprise-Grade Support & SLAs – direct access to Tally engineers, sub-hour critical-issue response, 99.9 % uptime guarantees, quarterly reporting, and the continued waiving of our 0.25% proposal fee.
There is some overlap in the support dimension, and if the DAO ultimately adopts Dennison’s rewards model we are happy to adapt. That said, a purely programmatic stipend would likely fund only the baseline services, leaving the webhook framework, deep integration work, and higher-touch SLAs unfunded.
–
2. Why seek funding outside the SPP, and why not have the DAO progress this through an RFP?
Tally is the de-facto interface for ENS governance. Approximately 70% of all token-weighted votes in the DAO are cast through Tally. Given this track record, we felt it appropriate to bring a targeted proposal rather than ask delegates to draft an RFP from scratch.
We fully understand that the community may wish to benchmark alternatives. If delegates decide an open RFP is the best path, we will participate in good faith.
–
Formalising the relationship now simply allows us to invest even more deeply in ENS-specific functionality, and turn governance into a clear competitive advantage for the DAO, while giving delegates predictable costs and SLA-backed assurance. We look forward to the community’s feedback and remain ready to iterate on the proposal to match ENS’s evolving needs.