[Proposal] Push Business Development SubDAO

Initial Discussion

Authors: @MrJaf @christiandike @SixtyKeys
Co-Authors: @Rene @incakolitazero


The BD SubDAO aims to motivate and incentivize the Push Community and Push contributors to actively engage in business development activities for Push Protocol by offering rewards that vary according to the project size. The classification of project size will depend on the number of X (formerly Twitter) followers and the level of Discord activity.

The initial iteration of the SubDAO will primarily be overseen and managed by the BD SubDAO working group, with a member of the Push Team serving in an advisory role. As with our other initiatives, the long-term vision is to gradually decentralize this program and more business development activities to transfer complete ownership to the community via the DAO.

The operations of the SubDAO will continue to be refined and adjusted over time to integrate all lessons learned into the program’s best practices.


Push is the Communication Protocol of Web3, and to ensure the protocol’s continual growth, we need to onboard more users to the platform. The BD SubDAO will leverage a global community of contributors to spread awareness and encourage the adoption of Push Products.

The SubDAO also furthers the Push mission to become a community-governed, decentralized autonomous organization (DAO) by promoting ecosystem growth and shaping the future of Push Protocol. Through progressive decentralization, the SubDAO will allow community members to participate in the growth of the protocol while gaining new skills, building professional networks, and growing their ownership of the Protocol. Push Protocol will also benefit from increased awareness and adoption of Push products in other communities and DAOs.


What defines a Collaboration?

A collaboration is defined as a successful partnership between Push and another project, as facilitated by a DAO contributor. For the BD SubDAO it will consist of two main steps:

  • Implementation: A successful integration of one of the Push Products by the partner project. This could be Push Notifications, Push Chat, or Push Spaces.

  • Announcement: An official announcement on their Twitter and other social channels. This should ideally include an article by the partner project highlighting Push technology and why they have chosen to integrate with us.

  • The BD SubDAO will vet all collaborations. The SubDAO Lead should confirm approval of all potential collaborations before contributors can begin collaboration on behalf of the DAO.

Collaboration Tiers

Contributors will be rewarded based on collaborative efforts with any of the different project tiers as defined below:

Screenshot 2024-03-06 at 22.48.57

Reward Phases

Business development consists of various phases/stages. The BD SubDAO will be rewarding contributors in two phases, which will serve as milestones for rewarding business development efforts. This means that when a contributor completes a particular phase, upon verification by the BD SubDAO working group, they will be eligible to receive rewards for that specific phase.

A phase is considered complete when the contributor can provide proof of completion, which will be submitted to a BD SubDAO database. A portion of the rewards for each collaboration tier is unlocked for contributors as they complete each BD phase.

The rewards for each collaboration tier and the unlock schedule are broken down below:

Screenshot 2024-03-06 at 22.49.38

Rules and Guidelines

  • Push Ambassadors are eligible for a 1.2x multiplier on top of their rewards for completing both phases.

Screenshot 2024-03-06 at 22.52.03

  • Participants in the Program can leverage the established Push Infrastructure to contribute to the program’s success:

    • Push Grants Program: projects can apply to micro and rapid grants for the implementation portion.
    • Demo Thursdays: invite projects to join our weekly session to showcase what they are building.
    • Ambassadors chapters: get help from the fantastic Push Ambassadors to get your message to more places!
  • To streamline the definition of a successful implementation, the following rules must be fulfilled for any of the integration types (Chat, Notifications, Spaces):

    • A chat (preferably telegram) must be created with both teams: Push and the Project that will be implementing Push Protocol.
    • For notifications: The Push Team will verify and validate that a channel is created and will observe the growth of subscribers and notifications so that they look organic.
    • For chat: upon the successful implementation Push team can observe how many chats have been initiated from a project. Same as for notifications, organic growth is expected.
  • An announcement will only be rewarded once implementation is complete to ensure that incentives are aligned between Push DAO and contributors. This means you can unlock the reward for a successful announcement but can only be rewarded once the implementation is complete.

  • At the end of each month, reward distribution will be done for all contributors. All rewards will be distributed in PUSH tokens, the amount of which will be determined using a 30-day rolling average.

Working Group

The BD SubDAO Working Group will coordinate the activities of the BD subDAO and ensure that the program runs smoothly. They will also be the primary point of contact for DAO contributors engaging in Business Development activities.


  1. Working Group Lead
  2. Working Group Co-Lead
  3. Español Community Liaison
  4. Push Team Advisor

BD SubDAO WG Authorities and Responsibilities

  • Onboard contributors into the BD subDAO by providing support and resources.
  • Review and approve potential collaborations.
  • Coordinate outreach efforts and track and manage engagements.
  • Validate contributions by ensuring that contributors to the BD subDAO have completed the relevant BD phases as a condition precedent for unlocking rewards.
  • Assist with the technical aspects of the integration of Push products.
  • Facilitate the creation of marketing materials for collaborations.
  • Hosting public ceremonies and designating office hours for providing support and attending to inquiries.
  • Encourage and increase participation in the BD subDAO program. Generate marketing content and campaigns to attract more contributors to take part in the program.
  • Maintain a comprehensive database of projects that are in existing partnership or collaboration with Push Protocol. This database should continuously be updated with new collaborations and publicly accessible to contributors.
  • Publish a monthly report highlighting the primary KPI of the number of collaborations achieved and the progress of the different collaborations. The third report (quarterly report) will highlight the successes and shortcomings of the program, as well as improvements to be made.

How to approach projects

For community members who are new to Business Development, the following phases can assist you in planning out and documenting your efforts and ensure your collaboration is a success.

Screenshot 2024-03-06 at 22.53.36

Additional Resources:


The initial iteration of the BD SubDAO will run for a single Push DAO season (3 months). The goal of the first season will be to complete 31 collaborations and reach a minimum audience of 1,820,000 X followers across all successful partnerships.

Push Protocol currently has a following of ~ 131,000 followers, so the program will bring awareness and exposure to Push Protocol and its products to 15x the current Push audience, in addition to 31 potential new integrations.

The BD SubDAO working group requests a budget of $38,000 in PUSH Tokens (~ 137,000 PUSH as of March 6th 2024) to be used over the next 3 months to complete this vision.

This amount will be transferred to a 3 / 5 multi-sig consisting of the working group members and an additional Push Team member before the program commences.


FOR: Establish and fund a Business Development SubDAO for 1 Push Season (3 months).

AGAINST: Do not establish and fund a Business Development SubDAO.


Great proposal.

Since we are in a bull market, most market participants (including $PUSH tokenholders) engage actively with many other projects and individuals. It creates a lot of networking opportunities for expanding Push Protocol’s services — if we add to it the incentives proposed by the authors of this proposal, we can assume the probability rate for success lies on a satisfying level.

To clarify a few things:

  1. Will the classification be based solely on the absolute numbers mentioned in the proposal, or— besides them— will the team assess whether a given project is a “worthy” counter-party to cooperate with?

As we know, X is still full of bots and scam projects’ accounts with fake followers whose engagement levels can look as organic as the real ones’.

  1. Will the team assess by closer examination
    whether the organic growth is real? If so, what measures will the team take to examine it?

  2. How much time is it estimated to take to examine if implementation is successful? Are there plans for any rigid timeframes?


Hey @ELI5ofTLDR, welcome back to the forum! The main criteria we will be looking at is the number of followers a project has, but the BD working group will always vet the project before giving contributors the go-ahead to engage with it.

Yes, we plan to work closely with the core Push team to assess whether the activity of new channels is organic. Since Push is an on-chain platform, measures taken can be as simple as checking how recently the wallets interacting with the Push channel were created and their on-chain activity to determine whether they are real users.

There are no rigid timeframes yet; as you can imagine, different projects will have different adoption rates. A Tier 1 collaboration may show satisfactory growth in as little as a few days after implementation, whereas a Tier 4 collaboration might take a little longer to see the same results. We will continue to iterate and provide estimated timelines for contributors based on how this initial iteration goes.

Thank you for taking the time to give some feedback on this proposal! Feel free to drop any more questions you might have here :handshake:


That is how the BD SubDAO plan can be seen as a good example of the motivation of the business engagement of the Push Protocol ecosystem. The introduction of the awarding period schemata and the collaboration tiers visibilities help clarify the work done by the contributors, which is further enhanced with the Push Ambassadors’ additional encouragement. The important guidelines for cooperation provide a ground for a common understanding and quality outcomes. Great Proposal!!


Hey @ELI5ofTLDR, Thank you for your question. I appreciate your interest. Now, let me provide you with some insights…

Well we do consider the numbers mentioned in the proposal to decide which category a project falls into, but we also look at other important things. For example, we think about whether the project matches well with what Push Protocol is trying to achieve. We also check if their audience is interested in what Push Protocol offers and if the project has a good reputation in the community. It’s important for us to team up with partners who share the same values and goals as Push Protocol, so we can create partnerships that really make a difference.

Absolutely, the team will check if the collaborations are growing naturally. We’ll look at things like how much people are interacting with the collaboration, if the interactions are consistent and meaningful, and we’ll compare data from different places to make sure everything adds up. This helps us know if the growth is real and if it fits well with Push Protocol’s goals. By doing this careful checking, we can be sure that the collaborations are genuine and are helping Push Protocol grow in a positive way.

The time it takes to check if the implementation is successful can change based on how hard it is to put everything together and what’s needed in the collaboration agreement. We don’t have strict deadlines, but we’ll try to make a plan with clear goals and timelines for each collaboration. We might set smaller goals along the way, check in regularly, and help out the people working on the project. By staying in touch and keeping an eye on things, we can make sure everything is going well and deal with any problems that come up quickly.


Nice update.
Friends, how are we going to measure the impact of this discussions, also i think that we need a different approach besides de BD subDAO, more like a public goods. I mean, Push needs some external development and overview to keep the track in the public good ecosystem, all the things that we do, besides advertising, it’s related to education and public goods, so if we are planning something entirely directed for revenue we are loosing some scope and opportunities to use all the new ethos that are growing with us.


thanks, @CryptoReuMD, for bringing this up. i believe public goods funding is something that we will need to pay more attention to as the DAO continues to grow.

with Push Grants Program V3, we can explore public goods funding as one of the secondary goals of the program, in addition to the primary goal of funding projects that have a clear ROI for Push.

we can follow in the footsteps of other leading projects which have designed programs for specifically ensuring that public goods are funded for the benefit of all. however, this will be a step-by-step process for Push DAO, with the whole community involved.


Thanks for the input @CryptoReuMD , I know it isn’t mentioned in the proposal, but we will have a big drive to educate contributors and community members on the Business Development process. We want the Push community to be able to learn new skills from participating in the DAO and gain knowledge they might not have previously had. This will be our soft addition to the public goods space as these educational resources will be free for both present and future community members to use.

And as @christiandike stated above, support and development of public goods will be something the DAO will continue to focus on in the future.


GM guys, please find the finalized BD SubDAO Proposal here.

A summary of some of the final changes are listed below:

  • Adjusted Tier 1 collaboration from 300k X followers down to 200k X followers.
  • Changed the reward distribution methodology from 30D moving average to TBD by Push DAO Governance Lead.
  • Added members of the BD Working Group
  • Added BD SubDAO KPIs
  • Adjustments in the Budget section