Transition Stewards Meetings - notes

Core Context

The group convened to reboot Gitcoin with ~$16–17M remaining treasury and a clean slate after a difficult DAO era. The goal is a 12-month “transitionary stewards cohort” to redefine strategy, governance, and sustainability.

Key Retrospective Insights

• Gitcoin fulfilled its original DAO promises, but failed to achieve sustainable revenue or scale.

• The DAO era suffered from:

• Over-expansion (large team, high burn)

• Weak market demand for public goods funding

• Token design limitations and governance friction

• Broader market conditions mattered:

• Capital concentrated in DeFi/speculative categories

• Public goods + regen lost momentum

• Despite this, Gitcoin created:

• New categories (quadratic funding, public goods funding, onchain crowdfunding)

• Significant cultural and ecosystem impact

Major Lessons (group consensus themes)

• You can’t run DAOs on vibes → need real business models

• Trust + structure balance is critical (too flat = chaos)

• Tooling must serve real users, not abstractions

• Incentives and accountability in governance are underdeveloped

• Crypto tooling has historically been too hard for normal users

Strategic Direction (Emerging)

• Shift toward building something people actually want (priority over governance purity)

• Strong interest in:

• Local/community use cases

• Real-world capital allocation

• Recognition that public goods funding is important but economically hard

Governance Experiment

• Proposal for a “trust graph” delegation system:

• Voting power flows through networks of trust (transitive delegation)

• Designed to decentralize power over time

• Intention: eventually the steward group could outvote the founder

Operating Plan

• Weekly meetings initially → then monthly

• Light compensation for stewards (debated)

• Next steps:

• Budget proposal

• Legal restructuring options

• Define product direction

Tensions / Open Questions

• How to create sustainable revenue

• How do evolve GTC token

• Whether DAO structure is even the right long-term form

• Balancing:

• Decentralization vs execution speed

• Governance vs product-market fit

Underlying Tone

• Honest reflection on past failures

• Desire to move forward without baggage

• Emphasis on focus, pragmatism, and rebuilding from first principles


Disclaimer: This post is for informative purposes only and is not financial advice. This post reflects my personal views, not a decision or commitment by Gitcoin governance. Forward-looking items in it are targets, not commitments. The information in these posts is subject to change as we continue learning. This post may contain estimates, may contain errors, and is provided on a best-effort basis. DYOR, do not make any financial decisions based on these posts.

2 Likes

heres a summary of the feedback i’ve gotten from yall since our first meeting (chattham house ofc)

• gtc retrospective was healthy for clearing the air and composing learnings

• the group needs direction from owocki before it can self-organize

- main fault line: some think treasury power belongs in private (CEO + challenging board), and doubt a renaissance without a hard pivot (and product market fit). one voice still says spin down the DAO

- open worry: sustained engagement. needs a heartbeat, watch who shows up weeks 2-4

- bull case: new direction lands in market

- bull case: trust-graph governance could set an industry standard

• warnings: hand-picked delegates can read as performative, and big pots of money attract extractors. but same critics are aligned overall and say don’t exit prematurely, owocki is still still the vision holder


Disclaimer: This post is for informative purposes only and is not financial advice. This post reflects my personal views, not a decision or commitment by Gitcoin governance. Forward-looking items in it are targets, not commitments. The information in these posts is subject to change as we continue learning. This post may contain estimates, may contain errors, and is provided on a best-effort basis. DYOR, do not make any financial decisions based on these posts.

Summary (Chatham House Rules)- Meeting 2

The group discussed a proposed new direction for Gitcoin centered on localism and “cosmolocal” infrastructure, with the goal of shifting time, money, and attention from online/network monopolies toward local, real-world communities.

A key influence on this direction has been guidance from a MENTOR, including a potential fundraising pathway via aligned high-net-worth networks interested in social impact.

Core Direction
• Build a local-first platform (“Hometown, name TBD”) to:
• Redirect online behavior into offline local participation
• Create a community-owned local data layer
• Enable interoperability across cities via shared schema + SDK
• Initial pilot in Node Zero, expanding to multiple cities by end of 2026
• Parallel effort to explore nonprofit (501c3) structure

Key Hypotheses
• The problem is not lack of information, but lack of behavior change
• Success depends on:
• Converting intent → action
• Leveraging social accountability (groups, pods)
• Targeting high-transition life moments (e.g. moving, new parents)
• Existing platforms fail due to:
• Misaligned incentives (ads, engagement maximization)
• Network capture and “enshittification”

Product + Tech Concepts
• Early-stage, still in discovery (“let us cook”)
• Potential elements:
• Local data layer owned by users (federated / protocol-based)
• Integration with AI (e.g. LLM routing, future agent-based commerce)
• Privacy + data sovereignty as core primitives

Risks & Open Questions
• Cold start problem for network effects
• Cultural fragmentation of local communities
• Avoiding disintermediation of existing grassroots efforts
• Differentiation vs AI tools (e.g. ChatGPT)
• Future-proofing for agentic / intent-based economies

Plan (H2 2026)
• Aug–Sep: data layer + product V1
• Oct: launch in Node Zero
• Nov–Dec: iterate + expand to ~5 cities
• Evaluate product-market fit + fundraising traction

Bet Framing
• ~15–20% of ops treasury deployed as a high-conviction bet
• Success criteria:
• Real-world engagement
• Product usage
• New capital inflows

Overall, the group aligned that this is a high-risk, exploratory pivot, with strong emphasis on behavioral design, local coordination, and alternative network effects—but with many unresolved questions still in active discovery.


Disclaimer: This post is for informative purposes only and is not financial advice. This post reflects my personal views, not a decision or commitment by Gitcoin governance. Forward-looking items in it are targets, not commitments. The information in these posts is subject to change as we continue learning. This post may contain estimates, may contain errors, and is provided on a best-effort basis. DYOR, do not make any financial decisions based on these posts.

2 Likes

Looking at the ontology of this post alongside the ontology of the Kokonut Framework, Kokonut Intelligence, the emerging agent marketplace, and the composable DAO governance used to create each local instance, the ontological overlap is difficult to miss.

Ontologically speaking, of course.

The proposed model appears to be:

local communities retain sovereignty, operate through their own governance, produce locally owned data, use shared standards, connect through a broader intelligence layer, and benefit from what the other local instances learn without becoming subordinate to a centralized system.

That is very close to the architecture Kokonut has spent the last five years building and refining through an actual local implementation.

The governance stack is live. The common data schema is live. The MRV and evidence infrastructure are live. Kokonut Intelligence is live. Adelphi provides a real operating instance rather than a theoretical diagram. The agent marketplace is still emerging, so I would not claim that every component is finished, but a substantial part of the underlying coordination substrate already exists and has years of learning embedded in it.

The domains are not identical. Kokonut begins with regenerative agriculture, while this Gitcoin direction is broader. But the ontology is remarkably similar, and the framework was designed to be reusable across locally governed instances.

So before spending significant resources rebuilding the ontology of hyperlocal coordination from first principles, it may be worth inspecting the ontology that is already here.

But don’t take my word for it. I think trust has to be earned through inspection.

This is a fairly smart comparative analysis of the two systems:

discoverable through our AI overlords.
A pretty smart comparative analysis. Gitcoin Transition x Kokonut Intelligence

very cool! want to DM me and lets chat more?


Disclaimer: This post is for informative purposes only and is not financial advice. This post reflects my personal views, not a decision or commitment by Gitcoin governance. Forward-looking items in it are targets, not commitments. The information in these posts is subject to change as we continue learning. This post may contain estimates, may contain errors, and is provided on a best-effort basis. DYOR, do not make any financial decisions based on these posts.

1 Like

Summary (Chatham House Rules)- Meeting 3

TL;DR — Chatham House Rules

  • Dev Strategy: Build an open, federated SDK for locally oriented networks—community commerce, events, funding, mutual aid—where users own their data and apps share network effects instead of trapping them.
  • Product thesis: The platform can go broad, but success depends on one compelling flagship app. The strongest candidate is an AI-native asks/offers and intent-matching experience that solves an immediate local need.
  • Opportunity: AI agents could reduce transaction costs and enable complex mutual-credit or non-monetary exchanges, potentially leapfrogging incumbent marketplaces rather than cloning them.
  • Main risk: There’s plenty of theory and infrastructure, but no proven go-to-market product yet. The priority is practical value, not a sprawling feature set.
  • Brand: Two leading directions are REDACTED1 and a REDACTED2 family of brands. No decision yet; target is mid-to-late August. Using “REDACTED2” would require alignment with the concept’s originator.
  • Budget: Proposed H2 spend is roughly $1.2M over six months (~$170K/month), about 15% of the $6.8M operating treasury. December is the checkpoint: fundraising and product/technical momentum mean double down; weak momentum means teardown and rebuild.
  • Next steps: Continue SDK/intent exploration, identify and build the focused flagship use case, finish brand diligence, and have stewards review the budget proposal asynchronously
2 Likes

Summary (Chatham House Rules)- Meeting 4

TL;DR from todays call:
• Runway: Proposed $1.2M for six months, about 17% of the operational treasury. At the current burn, Gitcoin has roughly three years of runway. December 2026 is the checkpoint: reduce spending if traction is weak; double down if strong
• Success by December: Complete several measurable pilots, turn the learnings into a credible fundraising story, and show movement toward major gifts. ADVISOR’s network is viewed as a potential path to $10–30M in philanthropic capital
• Funds stay separate: Approximately $6.8M operational treasury and $10M public-goods/matching pool. The matching pool remains governed by the community and dedicated to public-good purposes
• Product strategy: Run at least three pilots that move attention, time, and spending from online/national systems toward local communities. First pilot, Beacon, targets affluent mothers in NODE ZERO and helps trusted circles coordinate local activities and recommendations
• Primary risk: ADVISOR’s vision is extremely broad, while the team is only about eight people. The near-term strategy is therefore to pick one achievable wedge; Kevin believes distribution—not building—is the bottleneck
• Development model: Explore a T-shaped/open-source approach: the core team builds polished reference products, while outside developers experiment using an SDK/shared data layer. Strong community contributions could later become official product features
• Major unresolved questions: Whether Beacon is the right first wedge; whether Gitcoin should lean closer to its crowdfunding competency; how to wind down the token and obligations to past investors; and what happens to the Gitcoin brand.
• Brand direction: The localist consumer product will probably use a new, non-crypto brand. No decision yet on whether Gitcoin continues separately, transfers to another public-goods organization, or winds down.

Next steps
• Julia to share the work-in-progress product hypothesis.
• Team to send product notes to stewards.
• Legal counsel continues iterating on structure.
• Steward meetings likely shift to monthly.

1 Like

Supporting local solutions with global implications

Hi everyone, I’ve been following the Gitcoin reboot conversations with a lot of interest, particularly the recent discussions around local solutions and what Gitcoin’s next chapter could look like.

So I wanted to take the opportunity to share an idea: What if Gitcoin’s role in a local-first future isn’t primarily to build another product, but to help the people already building local solutions become more capable, connected, and successful?

This is obviously just a hypothesis, and I don’t think I have the answer to what Gitcoin should become. But I’ve spent a fair amount of time working through a similar transformational process in another decentralized organization, with its own struggles around purpose, governance, community, and sustainability. And now I’m also experiencing the other side of the equation by working on a local solution myself.

Both experiences have made me think a lot about what is missing between a promising idea and a solution that actually creates lasting impact. So I wanted to put this idea out there and see whether it resonates with others.

The problem

There are already a lot of people trying to solve important problems in their communities, but many of these efforts are fragmented. A project might have a strong idea and a capable team, but struggle to find appropriate funding. Another might have solved a similar problem somewhere else, but the two teams never meet. Another might need technical or organizational support. Another might have something that works locally but no way of figuring out whether or how it could be replicated elsewhere.

The problem isn’t necessarily a lack of ideas. It may be a lack of an ecosystem around the people who are trying to turn those ideas into real solutions.

A lot of the existing institutions aren’t necessarily designed for this either. Traditional capital generally needs a path to financial return. Government funding can be slow and constrained by existing frameworks. Foundations can have their own institutional priorities and restrictions. Traditional grant programs often work best when a problem and its solution already fit into recognizable categories.

But some of the most interesting local experiments may not fit neatly into any of those structures. They’re too early, too unconventional, too cross-disciplinary, or simply trying to change the assumptions behind an existing system. Meanwhile, many of these projects are already out there. They’re just operating largely in isolation.

The opportunity

This makes me wonder if there is another way to interpret Gitcoin’s local-first direction.

Rather than asking, “What product should Gitcoin build?”, perhaps the question could be: “How can Gitcoin make the ecosystem of people building local solutions more capable?”

Instead of becoming one more organization building a solution from scratch, Gitcoin could potentially become a place where promising local initiatives can be discovered, learn, connect, receive support, and grow. Not necessarily an accelerator in the traditional sense, and not necessarily a venture studio. Something different: an ecosystem built around helping promising solutions become real and helping successful approaches travel.

The goal wouldn’t be to maximize the financial return of a portfolio. It would be to maximize the real-world impact of the portfolio. That doesn’t mean sustainability becomes irrelevant. The projects themselves need viable ways to continue creating impact, and Gitcoin would need a sustainable model for providing this kind of support as well. I don’t have a definitive answer to what that model should look like, but I think it should be part of the experimentation.

What could that look like?

I imagine something along the lines of Discover > Curate > Support > Connect > Amplify > Replicate

Discover. Actively look for people and projects working on meaningful local problems. Not just wait for applications, but develop the ability to find interesting work that might otherwise remain invisible.

Curate. Develop a fair and transparent way of identifying projects that are worth supporting. This is something I think would require real experimentation. I’m not suggesting that Gitcoin simply appoint a group of experts to decide which projects are “good.” There could be a combination of demonstrated need, local validation, evidence, community signal, team capability, early traction, potential for impact, and potential for learning or replication. Gitcoin’s history with different allocation mechanisms could make this particularly interesting to explore.

Support. And then provide more than funding. Depending on what a project needs, that could include funding, mentorship, technical expertise, organizational support, research, introductions, distribution and visibility, connections to potential users and partners, etc.

Working on a local solution myself, I’ve found that money is important, but it’s often not the only thing missing. Sometimes the most valuable thing is simply finding someone doing something adjacent and having a conversation. Sometimes it’s an introduction to someone who can open a door. Sometimes it’s another team that has already made the mistake you’re about to make. Sometimes it’s simply having people around you who understand the problem you’re working on. That kind of support is difficult to find when everyone is operating independently.

Connect. This could be one of the most valuable parts. If several teams in different parts of the world are working on related problems, they shouldn’t have to rediscover everything independently. Gitcoin could help create the network through which knowledge, people, tools, capital, and opportunities move between them. A solution developed in one city might contain something useful for a team in a different one. The local context remains important, but the learning doesn’t have to stay local.

Amplify. There are also projects that simply need a push. They may have something genuinely valuable, but lack the audience, distribution capabilities, or connections to get it in front of the people who need it. Gitcoin already has a network and reach that could potentially help with this.

Replicate. And eventually, when something works, the network can help ask: What exactly worked here, and under what conditions could it work somewhere else? That’s where I see the “global implications” part becoming particularly interesting. Not every local solution should be replicated, but some will contain models, knowledge, or approaches that can travel.

Why Gitcoin?

There are already accelerators, foundations, grantmakers, governments, and venture funds. So why Gitcoin?

I think Gitcoin has a somewhat unusual combination of things: Capital. Network. Reputation. Distribution. And, perhaps most importantly, a willingness to experiment with new ways of organizing and allocating resources.

Gitcoin has spent years experimenting with questions that are still unresolved: How do we identify valuable work? How do we allocate resources? How do we coordinate people who don’t share the same organization? How do we create community-driven systems? How do we experiment with governance?

Some of those experiments have worked better than others. I don’t think the lesson is that Gitcoin has already figured these problems out. Perhaps the lesson is that Gitcoin has accumulated a lot of experience trying to figure them out. And it still has the resources and, seemingly, the willingness to keep experimenting. That combination feels relatively rare right now.

A different kind of community

There’s another reason I find this interesting. Instead of trying to create engagement around Gitcoin itself, what if the community formed around shared work?

People building local solutions could support one another. Mentors could contribute expertise. Funders could contribute capital. Researchers could contribute knowledge. Local communities could contribute context and validation. Projects could share what they learn. Gitcoin could provide the connective tissue.

The relationship becomes reciprocal. Gitcoin provides resources and support. Projects create real-world impact. Projects contribute knowledge and experience back into the network. The network makes everyone more capable. And the value of the ecosystem grows with every useful connection and every successful experiment.

This could also create a different definition of success

The goal wouldn’t necessarily be for Gitcoin to own the successful products. In fact, I think the opposite could be more powerful.

Imagine Gitcoin supporting 10 projects, then 50, then 200. Gitcoin’s success wouldn’t be measured by whether Gitcoin itself built the winning product. It would be measured by whether the network helped more good ideas become viable, more local solutions reach people, and more successful approaches travel between communities.

That feels like a potentially powerful way to think about “local solutions with global implications.” The global layer doesn’t have to be one global product. It can be the movement of knowledge, capital, people, and successful models between local contexts.

What I would test first

I wouldn’t try to design the entire thing upfront. I’d test the hypothesis.

For example, Gitcoin could identify a small group of promising projects working on local problems across different contexts and spend a few months understanding them deeply. What are they actually struggling with? What support have they tried to access? What do they need that isn’t currently available? Can Gitcoin provide it? Do connections between these projects create value? Does the support actually improve their ability to execute? Can useful models or knowledge travel between them?

If the answer is yes, then there’s something worth building. If the answer is no, that’s useful information too.

The important thing would be to start from the actual needs of the people doing the work, rather than deciding in advance what they need.

A final thought

I’ve seen firsthand how difficult it can be for decentralized organizations to navigate questions of purpose, governance, community, funding, and sustainability. And now, on the other side, I’m experiencing what it is like to actually try to build a local solution.

That makes me wonder whether there is an opportunity for Gitcoin to occupy a different position altogether. Not necessarily the organization that builds the solution, but the organization that makes it easier for the people building solutions to succeed.

A place where someone can show up with a promising idea, find the people they need, test whether the problem is real, get the resources and support required to move forward, learn from others, and eventually help someone else do the same.

A kind of collaborative playground for serious experimentation, with enough structure to make participation fair and accountable, but enough openness to allow unexpected things to emerge.

Maybe that’s one way Gitcoin could turn “local solutions with global implications” from a vision into an actual organizational role.

I’d be very interested in hearing where this resonates, where it doesn’t, and what I’m missing. @owocki @MathildaDV

P.S. Apologies if this isn’t the right post or thread for this. I wasn’t sure where this kind of post would fit.

2 Likes

thanks for writing this, and right thread.

what grabs me isn’t the framework, it’s that you’re on both sides at once: inside a decentralized org grinding through governance and sustainability (tec, i’m assuming), and currently trying to get a local thing off the ground yourself. most people theorizing about local-first haven’t attempted it.

you wrote that money matters but is often not the only thing missing. that’s a great point.

a few questions:

  1. what are you building, where, and what did you go looking for and fail to find?

  2. of the six, which one was your binding constraint? any org attempting all six does none of them well. curate and connect look like different companies to me.

  3. on curation. you’re right that i don’t want a panel of experts picking winners, but qf’s known failure mode is rewarding whoever already has an audience, which is backwards for surfacing invisible local work. what broke the last time you watched someone attempt this?

  4. name five. if we ran your “understand a small cohort deeply” test starting in september, who’s in it? the list tells us whether this population is findable at all, or whether discovery is itself the hard part.

where we are: unresolved. we’re leaning toward building one wedge well, on the theory that distribution is our bottleneck rather than building.

3 Likes

Hey Kevin, thanks. And yes, TEC is the org I was referring to :wink:

1. On the local side, I’m currently working on a project called City/Sync. At the simplest level, we’re trying to make it easier for people to find meaningful ways to contribute to their local communities, and easier for local organizations to coordinate that participation.

What we’ve gone looking for and struggled to find is broader support around the work. Funding is obviously part of it, but so are the less tangible things previously mentioned: people who have worked on adjacent problems, potential partners, people who can give useful feedback, technical or organizational help, introductions, and just a place to learn from others going through similar things.

2. For us, support has probably been the binding constraint, with connection a close second. But I think this is also where I may not have explained the six clearly enough. I don’t think Gitcoin should try to operate six different functions. I see curation and support as the two core functions, with the other four largely enabling or emerging from those.

Discovery supports curation: you need some way of finding interesting work in the first place. Connection is part of support: Gitcoin doesn’t necessarily need to provide every resource itself, but it can create the conditions for projects to find one another, share knowledge, collaborate, and support each other. Amplification can also be a form of support, using Gitcoin’s existing network and reach when that is what a project needs. And replication is less a function Gitcoin would provide than an outcome of having a network where useful knowledge and successful approaches can travel.

I don’t think the goal is for Gitcoin to build a giant organization that manually does all of this. It could instead focus on the things it can do best, while creating the conditions for a broader network to do the rest. In that sense, Gitcoin becomes more of the connective tissue and facilitator rather than the operator of every function.

3. I completely agree with the QF failure mode you mentioned. I saw a version of that firsthand through the TEC grants program. QF can be very good at surfacing community signal, but community signal and value aren’t necessarily the same thing. That was part of why we experimented with things like TQF. But I don’t think the answer here is about a novel mechanism.

The first layer, to me, is actually defining what Gitcoin is looking for and what it isn’t: the kinds of problems, values, principles, evidence, and potential impact that make something worth supporting. Then you can build a simple, fair and transparent curation process with clear criteria and guidelines around that, looking at things like demonstrated need, local validation, evidence of value, team capability, early traction, potential impact, and potential to generate learning. I think there’s already a lot of experience here, both within and beyond Web3, so I’d build on that to come up with an effective process to serve this purpose.

4. I’d be careful about treating these five examples as proof that this population exists at a meaningful scale. I see them more as examples of the spectrum of things I’m talking about, and I think whether these projects are actually findable should itself be part of the experiment.

A few that come to mind are Permissioning the City, Cornerstone Indicators, IAIdea, Colorado Drivers Cooperative, and the Relational Tech Project. There are also smaller examples I’ve come across more informally, including people building tools for neighborhood cleanups, local environmental initiatives, mobility, mutual aid, and other very specific community needs, but with very little or zero visibility.

Something I find interesting is the range of maturity. Some are more established projects, while others are basically one or two people experimenting with a solution. So I don’t think the opportunity is necessarily about finding a huge “market.” It’s about finding a group of high-quality projects solving problems that people actually experience and care about.

I’ve also noticed a broader pattern that makes me think this is worth investigating: there are clearly huge numbers of local problems, there are people with the motivation to do something about them, and dramatically lower barriers to actually building something because of new software and AI tools. Someone who previously had a good idea but couldn’t build it can now prototype a solution themselves. That doesn’t mean those projects will be meaningful or survive, but it may make curation even more valuable.

So yes, I think discovery itself is something to test: how hard is it actually to find these people, how much effort does it take, what proportion actually fit the criteria, can we distinguish genuinely promising work from people just building interesting things, and are there enough high-quality projects to form a meaningful cohort?

5. I think that makes sense, although I’m not totally sure what you mean by distribution here. Distribution of what, and to whom? Either way, I think the “one wedge well” approach is exactly why I’d treat this idea as a hypothesis rather than a proposal for what Gitcoin should become.

The thesis, I guess, is: there may be a population of people building meaningful local solutions that is currently fragmented, difficult to discover, and poorly supported. Gitcoin may have an unusually good position to curate and support that work, while creating the conditions for a broader network to connect, learn, and amplify itself.

But I think the population, the need, and Gitcoin’s ability to serve it all need to be tested rather than assumed. If these things turn out to be true, then I think there could be something pretty interesting here.

2 Likes

Jumping in with some reflections.

Gitcoin has been a Schelling point in Ethereum and through my lens the regenerative ecosystem, for years now. It has catalyzed a lot of growth across a very diverse set of projects globally. I have been involved as a grantee and as a grant operator curating projects for rounds, and beyond receiving or allocating capital, it has been a discovery lens. It is how I found like minded projects, adjacent work and things filling gaps we were not filling ourselves. Projects, not just products, because it ranges from people building apps to people building communities.

I have watched the transitions. Grants focused, then more general and funding what matters, then dedicated domains with sharper focus, and more recently the move toward AI and accelerating the technologies that protect against its downsides. And over these past few months, the shift toward localism and deploying these tools in real physical communities rather than only digital ones. That shift is where a lot of my work sits.

This is where I think @bear100 point lands. There is a lot already being actively built by projects Gitcoin supported and helped sprout and rebuilding it from scratch would be a loss.

If I compare Gitcoin to nature, the tension is whether Gitcoin is the tree, the thing that visibly grows and produces abundance or the root system, the mycelium that is not as present and does not get the credit but provides the substrate everything else grows in. My read is that Gitcoin has been the mycelium for years, sometimes spreading too far and at a cost to its own health. What has been missing is a strong bidirectional flow. The things Gitcoin helps grow being able to flourish and send something back and the nutrients Gitcoin spreads moving between projects and communities instead of only outward.

I have been on both sides of that, as a receiver and operator. The work I keep coming back to is connecting place based communities with emerging technology in a way that fits their context and gives them sovereignty and ownership. That is the part of blockchains I care about and with AI arriving it matters more, not less.

Capital in this space has been dwindling, but there is still a lot of untapped potential in connection. Workshops, seminars, bringing together the projects Gitcoin has supported over the years. Much of that costs very little and it moves Gitcoin’s vision forward.

I also understand the wariness. In the DAO space there has been grift, bad actors and loud voices setting the agenda. That is real and I can see how it leads to a more insular posture. The pendulum has swung from very decentralized and community driven to something more centralized, and I think many of the reasons for that are valid. My concern is balance. If it goes too insular and cuts off from the mycelium network Gitcoin grew, you get duplication, more competition over the little that is left, and a competitiveness that is not useful. We are not trying to compete with each other. We are trying to compete with old systems that are deeply rooted and invasive.

I come to this with bias, so I will name it.

I have been building Green Goods, a local-first impact reporting and funding platform. Local initiatives report their work in a verified way onchain, coordinate around the commitments they make to address their own needs, and access a lower risk path to capital where funders keep their principal and the yield does the work, alongside direct funding, Hypercerts, and revenue generating tokens like Revnets. We have been at this for a couple of years, and this past year it has really taken shape on very little funding.

What would help is not only financial support. Visibility, being in a cohort where we are learning alongside others, mentorship from people who have built businesses and products. That is where network effects come from and we built Green Goods to be interoperable for exactly that reason: Gardens conviction voting, Octant V2 vaults, Hats Protocol, Karma GAP, Unlock Protocol, Hypercerts, and Ethereum Attestation Service. Every integration keeps those projects growing.

The other project I am part of is Tech & Sun, building solar hubs at Nigerian universities. Providing reliable power and internet and a space where students get grounded in regenerative practice they can apply in their own lives and communities. Green Goods is the substrate there, giving that work visibility to both the community and funders, and coordinating it across hubs.

The thing I care most about is how capital flows between those two worlds. And by capital I mean not only financial but cultural, social, intellectual, material. There is enormous energy and willingness to build in Nigeria and across the global south. There are people in established economies who are apart of a diaspora or have roots somewhere and want to invest back home, but have no transparency or trust to cross on. Build that bridge and it runs both ways. Financial and social capital goes one direction, cultural, intellectual, and personal connection comes back.

I see a lot of potential in Gitcoin taking the local-first approach and being that substrate. Incubating projects like Green Goods, Tech & Sun, City Sync and others so they take root, and in more traditional terms, being the seed investor that gets in early.

I like the projects directory on the site. Grant rounds were open enough that they created a lot of noise, but the directory captures the tools and infrastructure actually being built across the space. If Gitcoin curated the best of that, the stewards and trust graph could look at those projects as Lego pieces and see which ones fit together well. Then it becomes clear what Gitcoin provides and what Gitcoin would want in return. Then you make the bet.

I will close there. Gitcoin is at a crossroads. If it can identify the bright spots, the projects with potential and the people who have been consistent about showing up and building, and then create the substrate for them to flourish and grow with Gitcoin rather than apart from it, I think a lot of the work many of us have been doing for years finally reaches the point of adoption and integration in the places we have been building in all along.

1 Like

Summary (Chatham House Rules)- Meeting 5

Gitcoin Stewards Q&A — Chatham House Rule Notes

Purpose

The group discussed Gitcoin’s proposed next chapter: a foundation focused on building pro-human, pro-local technology and renegotiating society’s relationship with technology. The working brand is Techne, drawing on the Greek root of “technology” and “technique.”

The ambition is not to reject technology, but to use it to make people more capable, sovereign, connected, creative, and engaged in their physical communities.

Why now

Participants described a convergence of conditions:

  • Digital platforms increasingly concentrate power, wealth, attention, and data.
  • AI is accelerating worker de-skilling and weakening human craft and agency.
  • Existing social networks optimize for extraction and engagement rather than human flourishing.
  • Gitcoin has accumulated financial capital, technical capability, and a trusted network that could support a different model.
  • Independent funding creates room to explore without immediately adopting venture-capital incentives.

The core thesis is that network effects can potentially be redirected toward commons and public-good outcomes rather than monopoly extraction.

Localism and translocalism

The group challenged any simple framing of “local good, global bad.”

Local communities can provide embodied relationships, meaningful work, mutual aid, civic participation, and a stronger sense of belonging. But they can also be parochial, exclusionary, unequal, or unsafe. For some people, especially those marginalized by their immediate surroundings, internet communities are liberating.

The emerging direction is therefore translocal:

  • Strengthen local relationships and economies.
  • Preserve access to global communities and knowledge.
  • Help communities exchange practices and solutions.
  • Connect local networks so they can coordinate at regional, national, or global scales.
  • Design for many different kinds of locality rather than assuming a wealthy US city is the universal model.

Product hypothesis

The product should use digital technology to move people from the screen into meaningful participation in the world, rather than attempting to maximize time spent online.

Potential functions discussed included:

  • Discovering nearby people, activities, services, and opportunities.
  • Matching residents with volunteer work and civic participation.
  • Supporting local commerce without replicating advertising-driven extraction.
  • Making community needs and unmet demand legible.
  • Helping municipalities and funders understand what is and is not working.
  • Sharing successful local practices across communities.
  • Connecting local participation with governance.

A recurring point was that individual-purpose platforms often suffer from weak network effects. Combining social, commercial, civic, volunteer, and governance functions may create substantially more value than treating each as a separate product.

Lessons from earlier local platforms

The team is reviewing the “graveyard” of previous attempts rather than treating this as a novel category.

Likely failure modes include:

  • Extractive advertising and engagement-based business models.
  • Insufficient activity or inventory within a locality.
  • Replicating fear, conflict, and surveillance dynamics.
  • Expanding before establishing community trust.
  • Focusing on only one use case.
  • Assuming localism is naturally equitable or prosocial.
  • Failing to distinguish the interests of residents, businesses, governments, and funders.

A heavily moderated, community-specific platform with high adoption was raised as a useful reference point. Its commitment to serving one place, rather than maximizing geographic expansion, may be central to its success.

The proposed effort would differ by combining multiple community functions with a shared data layer and a non-extractive institutional model.

Technology, attention, and human needs

Participants compared today’s digital information environment to highly processed food: engineered to exploit human reward systems while failing to provide genuine nourishment.

The discussion distinguished between:

  • Pseudo-satisfiers: scrolling and other behaviors that temporarily stimulate a need while increasing craving and lowering well-being.
  • Deeper satisfiers: embodied relationships, nature, meaningful work, creativity, community, and shared experience.

Simply encouraging people to put down their phones is unlikely to work if their offline environments remain lonely, inaccessible, or unfulfilling. The product must help create viable alternatives that meet the underlying need.

At the same time, the group warned against romanticizing pre-digital life. Older local institutions also used social and psychological mechanisms to enforce hierarchy and conformity. The challenge is to use modern behavioral and algorithmic tools transparently, collectively, and in service of user-chosen outcomes—not to retreat naively from technology.

Economic and philanthropic model

The initiative is expected to be structured as a nonprofit foundation.

There may be a significant opportunity around localized philanthropy:

  • Major funders are increasingly interested in place-based work.
  • Local funders often do not know what comparable communities have tried or learned.
  • They want better ways to identify and share effective practices.
  • They prefer interventions that can become economically durable rather than requiring permanent subsidy.
  • Philanthropic capital could complement market and government funding where neither works alone.

A platform that improves local economies, coordinates capital, and transfers learning between communities could therefore serve residents, municipalities, businesses, and funders simultaneously.

The organization reportedly has approximately three years of existing runway, with the intent to attract additional philanthropic capital and build something durable.

Governance

Over time, governance could be redistributed through commons-based structures as contributors demonstrate value and the institutional design matures.

Trust graphs and related mechanisms were discussed as possible foundations for assigning voting power, distributing incentives, and eventually decentralizing authority. The sequence matters:

  1. Consolidate enough authority to execute.
  2. Develop the product and institutional model.
  3. Identify meaningful contributions and stakeholders.
  4. Progressively decentralize through mechanisms suited to the actual network.

Important unresolved questions

  • What is the initial user and the first indispensable use case?
  • How will the product achieve sufficient local density?
  • What specifically distinguishes it from unsuccessful hyperlocal platforms?
  • Which functions must be bundled to create a strong attractor?
  • How will moderation, safety, and community norms work?
  • How will the system avoid reproducing local inequality and exclusion?
  • What data will be collected, who controls it, and how will it be governed?
  • How can algorithms guide people toward offline activity without becoming paternalistic or manipulative?
  • What are the value propositions for residents, local businesses, governments, and philanthropists?
  • How should local autonomy interact with cross-community learning?
  • What milestones should trigger progressive decentralization?
  • How openly should the organization frame itself as a challenge to incumbent attention platforms?

Follow-ups

  • Produce and circulate a written strategy covering:
    • Comparable projects and prior failures.
    • How those lessons shape the design.
    • The unique value proposition.
    • Value to each stakeholder group.
  • Give participants space to leave detailed written comments before the next discussion.
  • Schedule a longer working session; the group felt the core questions require substantially more than a one-hour call.
  • Convene a focused conversation on DAOs, trust graphs, and decentralized governance.
  • Continue collecting open questions and offers of help through the steward group.
  • Connect people working on cognitive security and related research.
  • Explore how the cognitive-security work already being supported can inform the product’s approach to attention and behavioral design.

Bottom line

The strongest version of the idea is not “another local social network.” It is shared infrastructure for healthier local life: combining discovery, relationships, commerce, civic participation, philanthropy, governance, and learning between communities.

Its success will depend on whether the organization can turn that broad theory into a focused initial product, avoid extractive incentives, and create enough real-world value that people willingly redirect attention from incumbent platforms toward their communities.

4 Likes

I keep reading through the unresolved questions here and having basically the same reaction:

I think we already have a framework for asking most of them.

Not necessarily the answers. Those have to come from the people in each place. But a way of getting to the answers without rebuilding the coordination structure every time.

This is what I have been trying to point toward with Kokonut.

Take the first question: who is this actually for, and what problem are we trying to solve?

Before choosing an app feature, the Kokonut Framework starts by mapping the people involved, what each of them needs and can contribute, the problem being addressed, what value we expect to create, what risks sit around it, what kinds of capital are available, what an acceptable outcome looks like, and what evidence would tell us it actually happened.

Then you build.

Run the questions in this post through that process, and a lot starts to become clearer.

Local density: don’t create the locality from scratch. Map what is already there and connect it.

Partiful and Meetup already do pieces of discovery and real-world gathering. Localize is being built around discovering and connecting into local food and farmers. Wild Minds is already building a network around land and community projects, connecting people, skills, opportunities, and project leaders.

Wild Minds is particularly interesting here because they already went through part of the discovery process Gitcoin is discussing. They started by creating standalone resources, then learned that what people actually wanted was the people, connections, support, and opportunities around the work. They changed the product around that demand. The Wild Minds Network now has thousands of members and dozens of project leaders, with One Tree Farm acting as a real-world testing ground whose lessons can be carried into other local projects.

The desire is already there.

That means these things should not only be treated as products to study. Some could become integrations, partners, sources of existing local inventory, or straight BD opportunities for Techne. If Localize already has the farmer and food layer, why rebuild it? If Wild Minds already has project leaders and people actively looking for places to contribute, why recreate that graph from zero?

Fold in what fits. Partner where it makes sense. Build only what is missing.

Why would this be different from another failed hyperlocal app? Because the product isn’t the feed. The product is useful things happening in the real world. Time online is almost the wrong metric. A volunteer showing up, a local purchase, useful work created, a community need filled, or a project completed—those are the things worth measuring.

Local autonomy vs. learning across communities: this one is especially close to Kokonut. Use a common enough data structure that Monte Plata can learn from Texas without either one having to become the other. Same Framework, completely different local reality.

Hyper-local, at hyper scale.

Wild Minds is already moving in this direction as well. One Tree Farm is their local proof, but the point is not to reproduce One Tree Farm everywhere. It is to carry the systems, lessons, successes, and mistakes outward so other projects can build their own version.

That is translocalism in practice.

Governance: start with enough authority to get something done, document contribution and outcomes, then move authority outward as people demonstrate useful participation and the local governance system earns the ability to carry it.

Data: keep the underlying data as local and private as it needs to be, but turn the outcomes we choose to make public into inspectable evidence and attestations. An attestation does not make something true. It gives us a persistent record of who claimed what, based on which evidence, and when.

This is also where Kokonut Intelligence starts taking a lot of work off the humans.

If we have hundreds of local actors, needs, opportunities, funding sources, businesses, events, and projects, nobody should be manually trying to hold that entire graph in their head.

The intelligence layer can ingest the information coming from the local node and connected systems, identify missing evidence, surface unmet needs and underused resources, compare outcomes across localities, and help match the right type of capital to the right kind of work.

The human beings still make the decisions.

The machines make the complexity easier to see.

And I think there is another important point here around capital.

Philanthropy is one form of funding, but it shouldn’t have to carry an entire local economy. A useful intervention might combine philanthropic money, municipal funding, community commitments, commercial revenue, investment, research capital, equipment, labor, and knowledge.

If the resulting activity produces trusted, verifiable operating data, suddenly more of those capital sources have something they can actually diligence.

That is where these existing networks become interesting again from a BD perspective too.

A network of farmers is not just users. It can become a route for agricultural technology, research, financing, equipment, local buyers, and institutional capital.

A network like Wild Minds is not just a community. It is already a graph of people trying to build real land-based projects, with actual needs around capital, infrastructure, skills, planning, and execution.

Once those needs and outcomes become structured and verifiable, entirely different partners can enter the picture.

That is how we eventually get from “please fund this good thing” to “here is what this community is capable of producing, here is what it needs, here is what happened last time, and here are the forms of capital that actually fit.”

The thing I would really like to do next is take the full Techne hypothesis and actually run it through the Framework instead of continuing to talk about whether they sound similar.

Define what Gitcoin wants and doesn’t want.

Map every stakeholder.

Map the value and capital.

Map the existing tools and networks so we don’t rebuild Partiful, Meetup, Localize, Wild Minds, Gitcoin, or anything else unnecessarily.

Then look at them as possible integrations, partners, and BD channels—not only competitors or reference points.

Define the first outcomes and evidence standards.

Then see what is actually missing.

My suspicion is that we would discover that considerably less needs to be built than it currently appears, while the network Techne could potentially connect is considerably larger than it currently appears.

Which would be a pretty good first result.

I came across the public Head of Growth listing and noticed the current “mothers” Node Zero direction.

Since the transition notes have also raised questions around the initial user, the first indispensable use case, local density, and what still needs to be proven, I started thinking about what might be worth testing before interpreting early activity as product validation.

A few questions came up for me.

1. Are school and childcare networks actually social networks for the parents?

A school class can look like a dense social circle structurally, but there may be three very different graphs inside it:

  • the children’s friendship graph;
  • the parents’ coordination graph;
  • the parents’ actual friendship graph.

A parent may regularly exchange homework, schedules, or logistics with another parent and still have no desire to spend voluntary social time with them.

So I would want to understand:

How many people in a school or childcare circle would a mother genuinely choose to meet outside the original context?

Raw network density may be much less important than desired interaction density.

2. Are mothers short of social opportunities, or short of time and energy?

A child being at school does not necessarily mean the mother is socially available.

That time may already belong to work, errands, housework, appointments, recovery, exercise, or simply being alone.

If someone has one free hour, the competition may not be another app or another local activity.

It may be sleep, silence, unfinished work, or a close friend she already values much more highly.

So the unmet need may not be:

“I need more people available nearby.”

It may be:

“I need higher-quality connection with the people I already care about.”

Those are very different product problems.

3. What does a successful offline encounter actually look like?

A meeting happening is not necessarily a positive outcome.

Six mothers meeting with ten children may technically count as community time, but the actual experience may involve:

  • monitoring children;
  • resolving conflicts;
  • feeding them;
  • managing different ages;
  • repeated interruptions;
  • leaving more tired than before.

So I would be cautious about equating:

offline encounter = value.

A more useful signal may be:

Did this interaction leave the person more connected, supported, or energized — rather than more exhausted?

4. Are meetings with children and meetings without children actually the same use case?

They seem very different.

With children:

  • venue fit matters;
  • age compatibility matters;
  • child-to-child compatibility matters;
  • food and spending become part of the interaction;
  • parental attention is fragmented.

Without children:

  • the mother needs real discretionary time;
  • someone still has to manage pickup, dinner, work, or household responsibilities;
  • a rare free window may be too valuable to spend on weak ties.

So perhaps the real unit of analysis is not “mother” but the occasion.

5. How much privacy is someone willing to exchange for this value?

This seems especially important when children are involved.

Even if Beacon is not exposing continuous precise GPS location, there is still a perceived-risk question around sharing:

  • where I am;
  • where I intend to be;
  • whether my children are with me;
  • who can see that;
  • how long that information remains visible.

And “known person” is not the same thing as “trusted person.”

A parent from my child’s class may not be a stranger, but that does not mean I want them to know where I am.

So I would want to understand where the actual privacy boundary is:

  • everyone in the class?
  • selected parents?
  • close friends only?
  • temporary invitation-based groups?
  • different visibility for different contexts?

6. What happens when there is conflict inside the circle?

Institutional circles are not emotionally neutral.

Children fight. Parents disagree. There are people we like, people we tolerate, and people we actively avoid.

If one parent posts that they are going somewhere, how does the product handle the fact that there may be specific people within the same “circle” whom they do not want to meet?

This makes me wonder whether the meaningful boundary is not:

member / non-member

but:

people I permit into this context / everyone else.

7. How economically compatible are families inside the same local circle?

Families in the same school or neighborhood can have very different incomes and very different norms around spending.

Imagine two families meet at a café or family venue.

One parent casually orders meals, desserts, or extra activities for the children.

The other parent had not planned for that expense.

Now the second child also wants what the first child has.

The parent is no longer simply deciding what to buy. They are making that decision publicly, in front of another family and their own child.

That can create:

  • financial pressure;
  • embarrassment;
  • comparison;
  • parental guilt;
  • conflict with the child.

So location and activity sharing can also create a form of lifestyle exposure that the person did not intend.

8. Could children make otherwise compatible adults less compatible socially?

Two mothers may like each other.

Their children may not.

Or the children may be very different ages.

Or the families may have completely different rules around food, screens, spending, or behavior.

So:

parent affinity does not necessarily equal family compatibility.

If the product assumes family-level interaction, this seems important to understand early.

9. Are weak ties supposed to become stronger ties?

I am also not sure people necessarily want this.

Some relationships work precisely because they are bounded.

A parent I message about homework can be a useful and pleasant relationship without ever becoming a friendship.

A school or childcare connection can be valuable as a functional relationship.

Trying to increase interaction may actually create unwanted social obligation.

So one research question I would ask directly is:

Which weak ties do people actually want to deepen, and which do they prefer to keep weak?

10. Are the best distribution nodes necessarily the users with the strongest problem?

A highly connected mother may be excellent at activating a circle.

But she may already have plenty of social connection and very little need for additional social opportunities.

A newly arrived or isolated mother may have a much stronger need for connection, but almost no local network to activate.

So these may be different roles:

  • the problem holder;
  • the connector;
  • the activity generator;
  • the beneficiary.

If so, “mothers” may be a strong distribution wedge without necessarily being the final ICP.

The question I keep coming back to is:

Are we testing whether mothers are easy to find and activate as a local graph, or whether this group has a sufficiently strong unmet need for additional local social interaction?

Those are different hypotheses.

I would be very interested in how the team is thinking about this distinction in the first city test, and what signals would make you conclude that the current Node Zero hypothesis needs to be revised rather than simply optimized further.