[REQUEST FOR COMMENT] Future of Allo Protocol - What's Next?

Future of Allo Protocol - What’s Next?

TL;DR: While Allo Protocol has enabled innovative contributions, its complexity, high development costs, and rapid technological changes have led us to pause further development and refocus on the category of next-gen capital allocation.

Celebrating Progress

First, it’s important to recognize and celebrate the remarkable dapps built on top of the Allo Protocol so far. From innovative pools to standardized interfaces across diverse allocation mechanisms, the community has shown incredible creativity and resourcefulness in utilizing and expanding the protocol.

Strategic Shift

Since its spinout, allo.capital has experienced steady interest. However, our primary focus has been on exploring and developing understanding of the design space of next-generation capital allocation methods broadly, rather than specifically improving or expanding the Allo Protocol.

This strategic decision was guided by our belief that our past approaches were too solutionist - and too clustered around Quadratic Funding. Understanding the future of capital allocation in decentralized ecosystems demands a focus on the problems and the people who have them.

Strengths and Challenges

Allo Protocol undeniably excels in several critical areas—most notably, pool creation and providing standardized interfaces that simplify the implementation of diverse allocation mechanisms. These features have proven highly valuable for those well-acquainted with the protocol’s operations.

However, despite these strengths, we’ve encountered significant hurdles. The inherent complexity of Allo Protocol has been a notable barrier to entry for many users. The steep onboarding curve and complex user interface often discouraged new participants, limiting widespread adoption. Additionally, functionality that the market demanded (1) a la carte usage of the modules, (2) functionality for generating straightforward UI/UX for applications, was notably lacking. This gap made it increasingly challenging for developers to quickly prototype and launch intuitive interfaces for their users that would get adoption.

Technological Evolution and Financial Viability

The technological landscape has also rapidly evolved. Innovations in AI and vibecoding have fundamentally changed how quickly and efficiently new dApps and protocols can be developed. These advancements have dramatically reduced the value proposition of a dedicated solution like Allo Protocol, whose initial attraction was standardizing complex funding mechanisms. In an environment where developers can effortlessly deploy bespoke capital allocation mechanisms with AI-driven coding, Allo Protocol’s role as a necessary middleware becomes less clear.

Furthermore, the financial viability of continued protocol development has become a pressing concern. The high costs associated with maintaining and upgrading the Allo Protocol while it was incubated at Gitcoin—often running between $20,000 and $60,000 per month for development, coupled with prolonged timelines of six months for upgrades and another six months for security audits—are prohibitive. Customer resistance to activating fees further compounds the challenge, limiting the sustainability of funding such expensive operational and developmental overheads.

A detailed summary of these points can be found in the recent governance discussion: Allo 2.1 => 2.2.

Pros & Cons To Maintaining Allo Protocol

Pros

  • Battle-Tested Infrastructure: Allo Protocol has proven itself as a modular, reusable framework for onchain capital allocation. For advanced users, it continues to provide a reliable and flexible foundation to stand up capital allocation mechanisms quickly.

  • Ecosystem Familiarity: Many builders, especially within the Gitcoin and Grants Stack ecosystems, already understand how to interface with Allo. This familiarity lowers switching costs and creates continuity.

  • Standardization Potential: In a fragmented design space, Allo offers a shared language and architecture for allocation logic. Standard interfaces make it easier for downstream tooling, dashboards, and analytics to interoperate across funding mechanisms.

  • Composable by Design: The protocol’s architecture allows mechanisms like QF, direct grants, and milestone-based funding to share common infrastructure (e.g., registry, payouts), reducing duplication of effort.

  • Credible Neutrality: As a protocol, Allo allows communities to coordinate without privileging any single allocator or UX paradigm—an asset in pluralistic ecosystems.

Cons

  • High Maintenance Costs: Protocol development and auditing have been prohibitively expensive—often exceeding $500k per upgrade cycle—without a clear revenue stream to sustain that investment.

  • Steep Learning Curve: Onboarding new developers to Allo is hard. Its modularity, while powerful, introduces significant conceptual and technical complexity that limits adoption among newer teams.

  • Rigid UX Patterns: Builders often found themselves constrained by Allo’s design assumptions. The inability to quickly stand up custom frontends or modify logic without deep context made it hard to move fast or iterate.

  • Low Market Pull: Despite strong internal conviction, Allo Protocol has struggled to become a default choice in the broader ecosystem. Many developers now prefer to roll lightweight, app-specific logic using newer tools or frameworks.

  • Disintermediation by AI Tooling: With the rise of AI-powered code generation and app scaffolding, Allo’s initial value proposition—simplifying complex allocation logic—is being eroded by faster and more intuitive alternatives.

  • Lack of Sustainable Incentives: Attempts to monetize usage of the protocol (e.g., protocol fees) faced resistance. Without embedded incentive structures (e.g., a token or fee split), maintaining Allo becomes an altruistic public good with unclear funding.

Other Value Props

Beyond reusable protocol modules, Allo.Capital continues to offer additional valuable resources to builders engaged in on-chain capital allocation:

  1. Social: Leveraging community building to amplify impact and foster social schelling points around the design space.
  2. Intelligence: Providing insights, analytics, and strategic guidance on next-gen capital allocation dynamics.
  3. Distribution: Connecting builders with key stakeholders who will actually use their apps, increasing TVF (Total Value Flowed) through Gitcoin, bespoke intros, and other types of exposure.

Future offerings may include:

  1. Technology: Facilitating access to cutting-edge technologies and development tools to ease the pain and accelerate progress for app builders.
  2. Funding: Offering pathways and opportunities to secure funding and financial support.

Conclusion

Given these realities, we currently have no plans to pursue Allo Protocol 2.2 or Allo Protocol 3. Our strategic direction for the foreseeable future will focus instead on broader explorations in the category of next-generation capital allocation, which will then dive deep on specific niches where we think we can have an impact and generate revenue.

Possible Futures

While we’ve currently paused further development, several potential paths could emerge:

  1. No further development on Allo Protocol: Maintaining status quo and preserving existing implementations.

  2. Community-led development of Allo Protocol 2.2 or Allo Protocol 3: Empowering the community to take ownership and evolve the protocol according to user needs.

    1. Paul has put together a doc on this.
  3. Revisiting technological investments: Exploring completely new directions—tools that simplify the creation of crowdfunding apps, platforms focused on rapid scaffolding of decentralized apps, or integrations that leverage AI and vibecoding.

2 Likes

Notes from todays session, thanks gemini and read.ai.

read.ai

The discussion focused on the future of Allo Protocol, emphasizing the need for community involvement and a structured approach to governance. Kevin Owocki encouraged participants to engage with a pre-read document and submit questions via Slido, which helped prioritize topics such as community maintenance and the relationship between Allo Protocol, Gitcoin, and Allo Capital. Paul Glavin proposed a model for community maintenance, suggesting that if internal resources diminish, the community could take over development. Afolabi Aiyeloja highlighted the importance of identifying valuable aspects of the protocol to inform maintenance strategies, while Carl Barrdahl noted the significance of the registry and indexer in ongoing projects.

The conversation also addressed the evolution of Allo Protocol since 2022, with Kevin Owocki outlining its transition to a company holding significant assets. He expressed a desire to establish a proto DAO for decentralized governance and emphasized the importance of learning from Gitcoin’s experiences. Discussions included the potential for Allo Capital to create collaborative opportunities and the need for improved governance and context sharing. Afolabi introduced the Cap Owl research team, which aims to visualize connections within the ecosystem, while Evan Hudson pointed out the potential for engaging with real-world opportunities, such as government grants.

Towards the end of the discussion, Kevin Owocki proposed actionable next steps, including weekly AMAs to enhance collaboration and address the challenges faced by the protocol. He acknowledged the departure of current developers due to financial constraints and expressed a desire to clarify the technology offerings of Allo Capital. Updates on the Aloe Builders Fund indicated a shift in proposal requirements to encourage more successful outcomes. The meeting concluded with a timeline for collaboration on Allo Protocol and a suggestion for future discussions, including the possibility of creating a podcast episode to further explore these topics.

Chapters & Topics

CopyEdit

Descriptions

May 13, 2025

The Future of Allo Protocol

Invited Kevin Owocki Carey M

Attachments The Future of Allo Protocol DRAFT - Allo Protocol - Whats next?

Meeting records Recording

Summary

The discussion covered the potential for community maintenance of Aloe Protocol, the value of its registry component, and the evolution of the capital allocation landscape since its inception, as highlighted by Paul Glavin, Afolabi Aiyeloja, Carl Barrdahl, Evan Hudson, and Kevin Owocki. Kevin Owocki detailed the relationship between Gitcoin, Aloe Protocol, and Alo Capital, explaining Alo Capital’s current focus on software, research, and building a “protodow” to foster onchain capital allocation networks, emphasizing the importance of research as noted by Afolabi Aiyeloja and Evan Hudson. Coi groweco raised questions about leveraging Grand Stack’s wind-down and engaging with Alo Capital’s governance, while Paul Glavin provided an update on the Aloe Builders Fund, and the future development of Aloe Protocol was discussed, with Kevin Owocki addressing the involvement of original developers and the timeline for the patron sale deployment in response to Afolabi Aiyeloja and Gustavo Segovia’s inquiries regarding retroactive rewards.

Details

  • Community Maintenance of Aloe Protocol The meeting began with a discussion about the future of Aloe Protocol and community maintenance, prompted by a question in Slido. Paul Glavin shared a proposal for an “exit to community” strategy, suggesting that the community could maintain the protocol if Aloe Protocol decided to deprioritize its development. There was a consensus that the smart contract framework itself might not be the primary unifying element, with the registry being highlighted as a potentially more valuable component.
  • Value of Aloe Protocol Components Afolabi Aiyeloja raised the question of identifying the most valuable aspects of the current Aloe Protocol for the community and builders. Paul Glavin and Carl Barrdahl agreed that the registry seems to be a uniting smart contract function. Carl Barrdahl also suggested exploring pools in a similar way to the vault standard for extensibility. Evan Hudson noted the potential of pools but also their current limitations.
  • Evolution of Capital Allocation Landscape Kevin Owocki reflected on how the landscape of capital allocation has changed significantly since the inception of Aloe Protocol in 2022, with the rise of multi-mechanism approaches and AI capabilities. He questioned whether the original technology offering of Aloe Protocol still fits the current needs or if a rebuild with modern primitives is necessary.
  • Relationship Between Gitcoin, Aloe Protocol, and Alo Capital Kevin Owocki clarified the connections between Gitcoin, Aloe Protocol, and Alo Capital. He explained that Alo Capital is the IP spun out of Gitcoin, focusing on the broader category of onchain capital allocation, with the protocol being a subset of their plans. Gitcoin has a percentage stake in any future tokens from the Aloe ecosystem and is becoming a holding company for various subdows, including Alo Capital.
  • Current Status and Future Vision of Alo Capital Kevin Owocki described Alo Capital as currently a company with himself and Reena as co-founders, focusing on software and research rather than an active fund. He expressed an intention to gradually increase the governance capacity of a “protodow,” using the patron sale ETH as initial capital. The ultimate goal is to build a network where builders achieve product market fit, tokenize ventures, and share upside with each other.
  • Research as a Core Element Afolabi Aiyeloja and Evan Hudson emphasized the importance of research in understanding market needs and opportunities, including exploring real-world applications beyond the web3 bubble. Kevin Owocki highlighted ongoing research efforts, including a book on grassroots economics and upcoming work on AI in onchain capital allocation, positioning Alo Capital as a producer of original research in the design space.
  • Alo Capital’s Service Offering Kevin Owocki outlined Alo Capital’s intended service offering, which includes providing a straightforward path for organizations to translate their business goals into effective automated capital flows through expert design and implementation services. He sees Gitcoin as a potential customer, leveraging Alo Capital’s expertise to build their capital allocation systems.
  • Leveraging Grand Stack’s Wind-Down Coi groweco raised the question of how to leverage Alo Capital with the Grand Stack winding down, suggesting that local nodes could potentially hire Grand Stack experts to build their own stacks in different languages. This could create synergies and recycle funds distributed by Gitcoin for grant rounds. Evan Hudson pointed to existing community-led exploration workshops as valuable resources for moving forward.
  • Governance and Engagement with Alo Capital Coi groweco inquired about the current roles and governance layers for Alo Capital and how to engage with the core group. Kevin Owocki acknowledged that the interface between the company and the protodow needs further definition and suggested potential solutions like weekly AMAs. He committed to taking ownership of the research question around cohering the company and the protodow.
  • Aloe Builders Fund and Conviction Voting Paul Glavin provided an update on the Alob Builders Fund, a conviction voting fund for Alo builds, noting recent adjustments to parameters to facilitate proposal passing. Afolabi Aiyeloja emphasized the need for more funds in the pool to support more experiments. Kevin Owocki considered a proposal to allocate some protodow funds to the Builders Fund, recognizing conviction voting as a successful mechanism.
  • Future of Aloe Protocol Development Afolabi Aiyeloja inquired about the involvement of the original Aloe Protocol developers. Kevin Owocki clarified that they are no longer actively working on the protocol due to funding shifts but are available for questions in the short term. The possibility of the community forking the protocol and establishing their own maintenance structure was mentioned.
  • CO’s Research Rate and Future Steps Afolabi Aiyeloja mentioned their intention to propose a team around CO’s research rate. Kevin Owocki expressed interest in deploying 17 E towards coherence and later discussing revenue flow and sharing after the patron sale is deployed. Afolabi Aiyeloja inquired about the timeline for this deployment.
  • Timeline for Patron Sale Deployment Kevin Owocki indicated the timeline for the patron sale deployment is “when it’s done when it’s good,” referencing a potential six-month exploration period mentioned on allo.Capital. Gustavo Segovia then raised a question regarding how retroactive efforts would be recognized.
  • Retroactive Rewards and Future Planning Kevin Owocki clarified that while there are no promised future retroactive rewards, they are interested in collectively designing what such rewards could look like and potentially forming a social contract. Kevin Owocki encouraged individuals to invest in their own ventures, suggesting potential future token swaps or value flow through capital allocation networks. Gustavo Segovia stated they would prepare a forum entry to further evaluate the possibility of a more in-depth discussion.
  • Closing Remarks and Feedback Kevin Owocki considered the session generative and invited feedback via direct message, stating they would see everyone on Telegram. Carl Barrdahl added “Etc.” and Kevin Owocki concluded by saying goodbye.

Suggested next steps

  • [image]Kevin Owocki will research and share a proposal within the next couple of weeks on how to better cohere Alo Capital (the company) and its protodow.
  • [image]Paul Glavin will create a proposal for a community-led maintenance model for the Aloe Protocol.
  • [image]Kevin Owocki will continue to explore and define Alo Capital’s technology offerings for the community in the areas of AI, onchain, and capital allocation.
  • [image]Kevin Owocki will define Alo Capital’s offerings regarding distribution, funding for mechanism builders, and integration of community offerings into the company’s services.
  • [image]Kevin Owocki will facilitate introductions to the former Alo Protocol developers (at Grants Lab/Wonderland) for any questions within the next two weeks.
  • [image]Gustavo Segovia will provide information on using collab.land to address retroactive compensation efforts.
  • [image]Gustavo Segovia will prepare a forum entry to evaluate the worth of spending an hour discussing recognition of past efforts.

You should review Gemini’s notes to make sure they’re accurate. Get tips and learn how Gemini takes notes

Please provide feedback about using Gemini to take notes in a short survey.

Great call thanks for holding the space for an insightful conversation :folded_hands: :seedling: