Content Gateway Season 3 Proposal

Title: Content Gateway Season 3 Budget Proposal
Authors: @0xNSHuman
Date Created: 2021-12-10
Date Posted: 2021-12-18


After releasing the Beta version of Content Gateway in Season 2 and having the aggregated data distributed to the first user-facing product, we are going to focus on growth towards being a platform for other projects in the DAO and organizations outside it, as well as adding new content to the system, which now has a good cost of implementation with our existing tools.

However, there are important considerations that affect our budget request.


In Season 2, we deliberately kept all the roles assigned to just two contributors, because we believe in the power and productivity of small and highly-specialized core teams at the earliest stage of development. We achieved everything we wanted, and I’m convinced that the value DAO received is worth the BANK spent.

In Season 3, we couldn’t be more inviting to have new contributors take the tools we’ve built and start executing on many of the roles. However, we just started talking to the first potential contributors and it will take more time to onboard people and start distributing the workload.

This presents a challenge for us, because one of our biggest goals in Season 3 is to achieve self-sustainability and marketability for the platform, and we can’t just keep working on features 70 hours a week. Besides that, we need to allocate time for participation in the DAO and Dev Guild governance.

For these reasons, we’re seeing the need to manage expectations and risks until we have a clearer picture of what our new team is going to look like, how delegation of the scope will affect productivity (remember, bigger teams are often less productive, as counter-intuitive as it sounds), and what our market opportunities are.

With the intention to remain a long-term asset in the DAO, for optimally distributed pressure on the treasury, and for our own peace of mind, we’re asking for 50% of what our actual estimated budget is — 336,000 BANK.

We will focus on team growth and market orientation, and once we’ve onboarded more contributors and synchronized with them on the workflow and values — we will submit application for additional funding later in the season.

In addition to that, we have allocated 69,420 BANK from our Season 2 budget to use for contributor incentives, which is going to be carried forward to Season 3.

Total funding requested: 336,000 BANK.


This season we started approaching the problem of content aggregation, organization, filtering and delivery in the DAO, to leverage all the individual guild and project outputs, maximize and multiply the value of the content produced, and ultimately enable any 3rd-party platform or application to build unique and rich consumer experiences on top of all this content, whether it’s isolated or combined together.

By the end of the season, we got our MVP complete, the system running, and the first DAO product built on top of it and distributed to initial group of users.

Our first batch of pilot integrations includes:

:articulated_lorry: BANK Token Accounts and Transfers data

:articulated_lorry: POAP Tokens, Events and Transfers data

:articulated_lorry: BanklessDAO Website Content, including Newsletter, Announcements, Partner articles etc.

:articulated_lorry: Bankless HQ Podcast videos, along with their metadata, stats and any intelligible descriptions/transcriptions

:articulated_lorry: Bankless Academy courses with all the data and metadata to provide learning experience on any platform

:articulated_lorry: Bounty Board data; applicable for read-only use cases only though

On the way to deliver this, we began researching a way establish references between all these data entities, so that in the future we can build a complete cross-product data collection for each DAO member that will let applications show all the content relevant to a particular user.

The full version of our most recent milestone update can be seen in the discord post here.


How and Why

Our Season 3 strategy relies heavily on the research and analysis that we’ve done recently, including discussions with other product teams and guilds, polls on the forum and internal roadmap prioritization.

:link: Content & User Experience - Season 3 Sentiment and Priorities
Click here to see our full research post.

Our priorities for the upcoming season are derived from the diagram above and split into three categories. This is a favour to ourselves, because it increases our awareness about the work that has to be done outside just adding features on top of features, and lets us leave room for other things in the bigger picture. These categories are:

  • Implementations — well-researched features and system components that address certain product needs and add value to the system.

  • Research — mid-to-long-term infrastructure goals that have enough stakeholders and marketable applications to make them worth spending some time on. They can’t steal too much of our time, but we need to care about these to be able to make big moves sooner than later.

  • Growth — the things that push the project towards self-sustainability and opening new streams of revenue for the DAO, either through discovering market niches to sell to directly, of helping other products generate revenue indirectly.



  • Snapshot Governance Data Integration

    • Have the snapshot proposal history and voting results included in the aggregated storage, and later connected to the notification engine to notify users about events.
  • Discord Server Data Integration

    • Start collecting Discord server data, beginning with the records that apps can utilize, such as the announcements feed.
  • International Media Nodes Content Integration

    • We have reached an agreement with some of the IMNs to introduce their translated content in Content Gateway, and link the translations to the original articles, as well as between each other, for easier delivery, enabling the apps to switch between languages on the fly. We are also looking to figure out ways to include metadata that will help IMNs promote themselves and possibly receive tips for their work from content consumers.
  • HQ Newsletter (Non-Premium) Integration

    • We’re looking to expand the HQ content collection with the Newsletter items in addition to the Podcast.
  • Notification Generator and Events Pipeline Development

    • Having fresh data records coming in every second from the different sources, Content Gateway can recognize and extract events from that data, and then send these events to users as push notifications, as well as to other systems that do their own magic, and so on. We are looking to create a platform capability to make this possible, so that every piece of data in Content Gateway can be turned into an actionable event.
  • Authorization and Content Gating

    • We need to protect the system and some of its data from unauthorized access and modifications in order to enable more serious use cases.
  • Zapier Platform Connection Development

    • Zapier is a platform that lets anyone automate tasks and build amazing workflows by connecting any two of 3000+ available integrated applications together to create something unique. With zero coding knowledge. This is huge, and we would like to connect Content Gateway to those 3000+ applications, so that our data can be fed into any pipeline. Skipping the code!
  • ENS Record Map Integration

    • In order to make it easier for applications to translate your ENS name into Ethereum address / Twitter / Discord / Github and other supported records – and back – we are going to get the entire ENS record database in Content Gateway.
  • Community, Guild and Project Call Recordings Integration

    • Ok, this is a last-minute idea that’s worth exploring and is technically a very low-risk opportunity. We can turn some of our public recordings into content pieces with a decent user experience around them. The biggest example is the Weekly Community Call. If we give applications a way to show them in a nice way and combine it with sponsorship opportunities — this presents education, promotion and monetization opportunities.


  • Entity Relationship Standard

    • Development and adoption of a cross-project entity relationships standard, to make it possible, for example, to link all the independent data sources to a certain DAO member.
  • Decentralization and Tokenomics

    • Researching monetization and decentralization models that would let independent content producers monetize their work, and figuring out how can we distribute the storage and maintenance to make it more decentralized.


  • Attracting Content Integration Partners

    • In late Season 2, we allocated 69,420 BANK for contributors that want to integrate new data sources into Content Gateway. We are carrying this amount to Season 3 and hoping to make this incentivization program a reality.
  • Attracting Application Developers

    • Same as with data sources integration, we need to attract application developers that would add new products to the line that started with the Mobile App.
  • Contributor Onboarding and Support

    • Our initial plan was to build a framework that other contributors can take over and build amazing stuff on top of it with us. We’re now going to work on making this a reality sooner than later, and dedicate a good amount of time to making newcomers happy and supported.
  • Out-of-DAO Outreach

    • As we believe that Content Gateway can be valuable to organizations outside Bankless DAO, we’d like to start looking for opportunities to attract support for the project from such organizations, in order to reduce the possibly the pressure on out treasury and promote Content Gateway as a platform provided and maintained by Bankless DAO.
  • Developer Toolbox Improvements

    • We’ve released API & SDK in Season 2 and are planning to work on feedback and various issues to make it a better tool to create integrations and applications with.


The assumed hourly rate is 1,000 BANK / hour.

The assumed delivery period is 12 weeks.

Project budget breakdown by role:

  • Platform Growth Dude

    • Duties:
      • Outreach to other teams and organizations to promote Content Gateway as a way to present content on new platforms.
      • Grow the network of partners and developers around the system.
      • Work on monetization strategy.
      • Collect feedback and translate product requirements to the team.
    • Hours per week: 4.
    • Weeks: 12.
    • Role funding subtotal: 48,000 BANK.
    • Assignee: @0xNSHuman.
  • Project Manager

    • Duties:
      • Manage roadmap and deliveries.
      • Maintain weekly reporting to the DAO and represent the team.
      • Organize meetings and coordinate discussions.
      • Track compensation for contributors.
    • Hours per week: 4.
    • Weeks: 12.
    • Role funding subtotal: 48,000 BANK.
    • Assignee: @0xNSHuman.
  • Integration Coordinator

    • Duties:
      • Maintain high-level architecture consistency with outside world.
      • Evaluate technical solutions based on priorities and risk tolerance.
      • Coordinate communication and collaboration with the other teams.
      • Manage integration priorities and verify the execution.
      • Schedule and take part in the integration testing and delivery.
    • Hours per week: 4.
    • Weeks: 12.
    • Role funding subtotal: 48,000 BANK.
    • Assignee: @0xNSHuman.
  • Team Lead

    • Duties:
      • Maintain implementations aligned with the roadmap.
      • Support other team members and eliminate blockers.
      • Onboard contributors.
    • Hours per week: 4.
    • Weeks: 12.
    • Role funding subtotal: 48,000 BANK.
    • Assignee: @addamsson.
  • Software Architect

    • Duties:
      • Design system components according to the roadmap.
      • Conduct research and lead the discussion around long-term priorities.
    • Hours per week: 4.
    • Weeks: 12.
    • Role funding subtotal: 48,000 BANK.
    • Assignee: @addamsson.
  • Software Engineer (Platform & Tools)

    • Duties:
      • Implement solutions according to system design and budget limitations.
      • Create documentation for the tools facing 3rd-party developers and platform users.
      • Participate in the discussions with the internal and 3rd-party teams.
    • Hours per week: 28.
    • Weeks: 12.
    • Role funding subtotal: 336,000 BANK.
    • Assignee: Contributor(s) to join or replace @addamsson.
  • Software Engineer (Integration)

    • Duties:
      • Integrate upstream systems (data / content sources) with Content Gateway.
      • Assist and support CG SDK users with integration.
      • Work with the rest of the core team on integration tool improvements.
    • Hours per week: 8.
    • Weeks: 12.
    • Role funding subtotal: 96,000 BANK.
    • Assignee: Contributor(s) to join or replace @addamsson.

Scope Total: 672,000 BANK.

Upfront ask: 50% of the Scope Total.

Total funding requested: 336,000 BANK.


As in the previous season, the growth of the infrastructure is measured by the amount of data integrated, and more importantly the amount of data consumed via consumer-facing interfaces such as the mobile app.

  • Content producers integrated.

    • Number of independent projects plugged-in and having their data passed through the gateway.
  • Content consumers connected.

    • Number of products using the aggregated content API.
    • Amount of data consumed via the API per a reporting period.


Do you support funding the growth, development and marketing of Content Gateway and Bankless Content Platform?


0 voters


The product is just out of the box cant wait for it to go mainstream integration with Zapier 3000 plus apps thats a no brainer. Good work guys keep up the spirit :muscle:

1 Like

Overall, this sounds fantastic.

However, I don’t see why the DAO needs to pay for another Discord data gathering bot when we in Analytics Guild have already done that, and worked through the details that aren’t entirety obvious at the outset.

1 Like

I don’t see why the DAO needs to pay for another Discord data gathering bot when we in Analytics Guild have already done that, and worked through the details that aren’t entirety obvious at the outset.

Couldn’t find a bot development mentioned anywhere in our proposal, but since we do consider creating a new bot as one of the options, the question is valid.

We are well aware that you guys nailed a lot of data sourcing brilliantly in DAODash. We also answered this very question about what you percieve as duplication of effort in our channel at least twice. And finally, we consider using your bot if it meets cetrain scalability guidelines, but my questions about the details had not been answered yet. In the meantime, I’m happy to give this more visibility on the forum.

Every piece of software out there has limited resources to turn some input into a specifically expected output. The output of such software typically adds value to either a group of systems or a group of users.

However, the input that a particular team may choose is limited to the interests and needs driven by the project roadmap in the absolute most cases. In other words, if you take a completely different product and ask its team to rely on the same input, chances are it will be suboptimal for their product quality or growth.

DAODash bot consumes raw Discord data as input and feeds it into a specific pipeline to produce output that serves the purpose of presenting analytics insights. This is amazing output, would love to have it in Content Gateway one day, because it’s the actual part that adds value to many potential applications.

Unlike DAODash though, Content Gateway aims to serve tens to hundreds to thousands of applications, not one. It’s a platform that cannot afford limiting its capabilities to the use cases of a particular domain if there is a way to avoid that.

  • Academy courses is a unique valuable output worth depending on Bankless Academy.

  • Bounties is a unique valuable output worth depending on Bounty Board.

  • BanklessDAO Newsletter articles is a unique valuable output worth depending on the Website.

  • DAODash insights and charts is a unique valuable output worth depending on DAODash.

  • Discord data is a raw input — not worth creating a dependency on anyone but Discord.

Perhaps a Discord bot that Analytics Guild has created, made a dedicated autonomous service usable by any other system, and passed this bot to be governed and maintained across the DAO is well worth depending on. Our proposal assumes this as an option. We are not crazy and we literally don’t care where the right solution is coming from.

But creating a dependency for a platform on a standalone product backend is a terrible limitation. Not only does it potentially limit all the future applications that use CG to the capabilities of such backend, but it also adds pressure on the team (DAODash or Analytics Guild) to support use cases that they aren’t interested in.

We already had people coming to us and asking to get Discord data from DEGEN, and our position was the same. We would choose being voted out of the stage over compromizing scalability of the entire system.

So coming back to the question:

why the DAO needs to pay for another Discord data gathering bot

The DAO doesn’t pay anyone for any bots. It pays for solutions.

1 Like

However, I don’t see why the DAO needs to pay for another Discord data gathering bot when we in Analytics Guild have already done that

I’d also like to comment on this point. Back at the start of Season 2, we discussed this topic and we proposed a detailed solution for data ingestion that you could use which allows you to focus on your problem domain (analytics) without having to care about how the data gets into your system.

For reasons, I still don’t understand this collaboration didn’t happen and you spent your valuable time working on something that we promised the DAO before a single line of code was written.

In my opinion, this is something that a DAO with limited resources and limited human capital can’t afford to do. After all, we’re all here (at least this is my naive hope) to help the DAO succeed and make some professional connections, friends, and $$$ in the process.

So the question I’d like to ask is this: why haven’t you utilized the resources of the DAO effectively by cooperating with another project that you knew was going to work on a problem that you didn’t have to solve at all?

I apologize if my tone came off poorly. What I meant was to say we have a much of the the DAOs Discord data in a Postgres db, updated realtime. If that is something that would be helpful to you, reach out. If not, that’s cool too.

Certainly, when there is data you have collected we want/need, we will reach out to you folks.

1 Like