TeaBox Launch

Name of Project


Proposal overview

We aim to create an accessible and open source web3 social platform on Harmony where DAOs truly own their experience. DAOs can deploy custom UX to help members engage more easily and more often, and focus on what moves the needle towards the mission of the DAO.


  • Short-term: provide value to online communities such as DAOs to communicate in a token-gated space and with accompanying useful crypto-native features.
  • Mid-term: bring this utility to a larger audience whereby token-based ecosystems replace current ‘goodwill’-based social media networks - fans and consumers own a piece of the network and can directly support creators/entities rather than deal through middlemen, aka “token buys are higher signal than likes/follows/thoughts and prayers”
  • Long-term: Be an enterprise-grade solution for businesses, artists, and communities to communicate with their members in high-fidelity channels, share media, conduct transactions, and discover new functionality within online ecosystems (what can I ‘do’ with this membership as opposed to just who can I follow on this centralized platform)

Project-specific Deliverables:

For the first stage, we will create a platform where users can:

  • log in with a crypto wallet.
  • identify a range of servers they have token-dependent access to as determined by DAO admins whom we will partner with initially.
  • Once verified, the user will be able to enter a server’s community page, the particular functionality of which can be tailored to the DAO’s specific mission or operations (early examples: third module = vote, donate, or trade).

User Experience:

  • The user can jump between these servers treating the DAO community page like a more interactive instagram page they want to check out versus a gigantic mass of text messages through which most operations are currently run on Discord. From this experience, the DAO member will be able to keep better track of the organizations they participate in, decrease friction in terms of time & energy when participating in different DAOs, and access potentially exclusive areas or even functionality.

Admin Experience:

  • On the DAO admin end, the DAO will have finer control over the initial onboarding process and continued user experience, and importantly will also retain ownership of the components of their specific page in a censorship-resistant manner.

Natively integrating DAO-specific tools at the level of the communications platform will therefore solve several problems:

  1. reduce further user friction if an organization asks its members to perform particular actions via Discord, which they then have to leave and access a plethora of third-party sites.
  2. improve the issue of having to document and keep track of all the different tools any given organization is using (as determined by the lack of a single cookie-cutter set that every org uses, on the contrary there is immense variation and for good reason given the variable nature of decentralized groups) - if it were customizable which tools your platform of choice would deploy to a user at any given time, DAO operations would be significantly streamlined and members would be able to see at a glance the changes or new features their org has introduced. Each successive “ask” from a DAO to its members would cause less friction.
  3. Lastly, a framework for setting up and deploying complete DAO toolsets could evolve into a more consumer-friendly web3 app that allows casual users to set up template-based “DAO-lites” to access the desired functionality of the general suite of DAO tools for lower security requirement purposes without needing to spend several months reading and researching the space and learning how to manually operate their own DAO.

Therefore, the first step to bringing DAO+web3 functionality into the mainstream is a token-gated DAO-tooling platform allowing admins to deploy custom-built toolsets to their users. For our MVP, we will use the Harmony protocol and DAOs built on Harmony to have users log in with Harmony, see an array of communities they have access to, and display within each community a set of variably-customized functions or apps, likely:

  1. Chat/Forum,

  2. Feed/posts,

  3. Variable apps depending on the community to test and validate our thesis (this would likely either look like A) Buy/sell, B) News, or C) Vote, if applicable.)

N) Down the line, the “modular” aspect of the UI will become helpful as we move to decentralize this functionality, allowing any DAO to leverage the platform and deploy their own apps permissionlessly to their user base without our help.

Use cases:

In the case of “DAO to Raise Money for X”, a community may form around the stated goal of raising and deploying funds for/on behalf of a particular group or cause. Currently, such a DAO might start a (1) Twitter account and (2-3) Discord/Telegram group to get the word out, after a few days/weeks of back-and-forth with each other, a few vocal members may emerge based on various factors such as general interest/free time/early awareness, and these members may volunteer or be volunteered to be the steward of the group and future activities. The DAO would now be ready to graduate to deploying a (4-6) Gnosis Safe/JuiceBox/Llama to raise and manage funds. Once funds are raised, they may utilize Snapshot to organize decision-making and voting. If this step is successful and sustained, services like (7) Utopia Labs can help run the DAO’s operations. There are also tools like (8+) Aragon that help admins set these functions up, but users may be left feeling like the DAO is fragmented, hard to follow, and most importantly may feel inhibited from sustained involvement - especially if they are part of several DAOs.

Our opinion is that it is advantageous for the DAO to distribute the handling of various functions to different services, to avoid centralization risk and maintain leverage and ownership over their operational stack, however DAO admins and members could benefit from an underlying framework to help them organize these disparate tools into a more easily accessible experience of being involved in any given DAO. With (1) TeaBox, the DAO would simply select from a list of modular tools that they already use (set up once, see all at once) and immediately deploy to their members, instead of each current member having to remember and each new recruit having to spend a week acclimating themselves to the suite of DAO tools (and possibly losing interest along the way) instead of asking a user to familiarize themselves with this array of websites and extensions, they would see each module clearly and immediately in an onboarding flow, and be able to move much more rapidly to participation and contribution (in this case, donating funds or accomplishing marketing tasks).


  • Lucas Ward: Early-stage startup sales lead & biz dev/strategy, web3/crypto market research
  • Mario Habashy: Computer Science @ Harvard, frontend development
  • Nick Taras: Technical advisor, 7+ yrs experience blockchain development

This project is based on a hackathon submission for EthDenver hackathon, we started with a mobile app demonstrating token-gating functionality applied to community groups. We will reproduce the concept on Harmony on the web, as well as develop a proof-of-concept for our modular UI component, and work to move both aspects to mobile shortly after.

We have several years of experience building early stage startups. We will be seeking rigorous feedback and professional expertise as we continue to learn, iterate, and build out the product, as well as working closely with community members to design our product to best drive value for the community. We will actively reach out to community members and contacts to assist with items such as blockchain integrations and development assistance. As we gain traction, we hope to bring on one or two other members to the team, and also use open source contributions and feedback to keep development up to date.


  • Privacy/security - especially if people’s social data are connected to their address in some way. While not a priority for our MVP, we eventually want to integrate the signal protocol or something similar to protect user data from any of our servers
  • Similar current products like myco, commonwealth.im, gm.xyz, or bitclout take slightly different approaches and are solving for slightly different problems, we think there will be room in the market for several approaches to Dao tools as well as social. We have not yet seen any platforms that aim to aggregate tools rather than replace them, introducing centralization risk for the DAOs that rely on them.
  • Regulatory risk - our platform will interact with many assets or features that may be or soon be regulated especially in the US. We will be slightly protected by the fact that we are not ourselves offering to sell these assets to users, but nevertheless we plan on incorporating abroad and consulting with counsel.


  • For the first two stages of our product we plan on working with a small group of power-users (DAO admins and active users) to develop the functionality of the app and determine what methods work best. This will limit growth slightly while we hone the user experience, when we release the third stage product to target users unfamiliar with web3 as a semi-whiteglove experience we imagine we will be able to scale and grow rapidly.


As one of the most promising up-and-coming L1s, Harmony would be an ideal partner for us to work with and deliver a compelling MVP for early exclusive use with Harmony DAOs and other projects on Harmony. It would also allow us to potentially begin implementing our social buying & selling/other functionality ideas that are currently prohibitively expensive on other chains. [We love the ONE.wallet concept and think it fits well with our thesis of the future of DAO-tooling from a user perspective, we want to increase the amount of tools and dapps that can be used alongside something like Onewallet.] TeaBox will be purpose built to enhance the best aspects of decentralized functionality and self-governing communities and organizations, we would like to see a future free of walled gardens where the only tools & functions available are those thought up by centralized teams in MANGA hq’s. In TeaBox’s final form, DAO admins will be able to collect and compensate tool submissions from the community, approve, and then deploy to users immediately. Traditional companies need users to be exclusively plugged into their proprietary ecosystems. DAOs recognize that they are the ones who need users’ involvement, and that users will inevitably be involved in multiple DAOs, therefore it is advantageous to DAOs to compete to quickly provide utility in various forms to attract their users’ involvement. TeaBox will leverage this trend and new reality to provide a compelling product for both DAO admins and users.

Proposal ask


Task-based bounties for product development $10000
Project-based bounties for prototyping and operations $25000
Marketing, communication, beta-testing $15000


  • Milestone 1: Conduct DAO user research + produce proof-of-concept: 1 month, $3000
  • Milestone 2: shippable MVP + soft launch: +3-4 months, $35,000
  • Milestone 3: user alpha-testing + marketed launch: +2 months, $7000
  • Incidentals & other costs $5000

Metrics for success

Project Scope

Success will be measured by a few factors:

Description KPI1 KPI2
Github Once we reach a reasonable level of functional viability we will open source the project Forks, stars, watches, & downloads Positive qualitative reviews by friends, colleagues, community members
DAO Feedback We will work with a predetermined set of initial DAOs to solicit feedback usage & analytics, identify bugs potential custom modules for the next stage of the project
Demonstrated Interest Collect contacts on a landing page to build interest in a hosted SaaS+Mobile version and run an organic marketing campaign to build interest Email signups Social media engagement + Harmony community engagement


  1. Milestone 01:

  2. Budget:$3K

  3. Timeframe: 2-4 Weeks

  4. Tasks:

  5. User Research

  6. Interview DAOs, product validation.

  7. Reach out to DAOs on Harmony.

  8. Develop a comprehensive set of interview questions (e.g., What do your DAO members use to communicate? How many are token holders? etc. etc.)

  9. Maintain an active working list of potential beta testers to follow up with.

  10. Proof of Concept

  11. Developing a proof of concept based on user research.

Milestone 2


Timeframe: 8-12 Weeks

  1. Product Requirements

  2. What is the real core functionality that we want this MVP to have? What do we want it to do?

  3. Product Specs

  4. What do we need to build exactly? Timeframe, budget, etc.

  5. Prototype

  6. Figma, designing, UX.

  7. Front-End

  8. UI, coding, React, React Native.

  9. Back-End

  10. Data integration, integrating APIs, maybe software, etc.

  11. Blockchain

  12. Smart contracts, Harmony compatibility.

Milestone 3


Timeframe: 2-4 Weeks

  1. Deploy MVP

  2. Working list of people who we interviewed – keep in touch. These are our first testers/users.

  3. been building hype the whole time (email list)

  4. Feedback from First Users

  5. Feedback, we know what we need to iterate on, next steps - we probably need more money to continue. Having a plan for next steps.

  6. Organize the beta test

  7. Target Harmony DAOs.

  8. Harmony sandbox?

  9. Come up with key metrics that we’re testing for.

  10. Get feedback.


  • Milestone 1: Conduct DAO user research + produce Harmony proof-of-concept: 1 month, $3000
  • Milestone 2: shippable MVP + soft launch: +3-4 months, $35,000
  • Milestone 3: user alpha-testing + marketed launch: +2 months, $7000
  • Incidentals & other costs $5000

External links

[Pitch deck]


Lucas gave a great presentation on this at our Austin meetup. TLDR: modular UI for DAO tools that covers the Social and Coordination aspect while allowing integration of other DAO tools.

I love the concept, instead of a one stop shop for DAO tools, it’s a place where you can plugin the DAO tools you use the most and access everything from a Social UI.


Thank you for submitting a proposal to Harmony’s $300M Ecosystem Fund. We are in the process of reviewing your proposal and will assign a representative on behalf of the Grants Ops team.

We would also love :blue_heart: to have the Harmony community participate to ask questions and provide feedbacks.

If you have more details to add, please do so by replying to this thread.

1 Like

Do you have any social media like Twitter or discord, to announce something?

We will soon! You can sign up here if you’d like to get notified when we do: https://forms.gle/N7J9Ez81MJzGYXTv6

1 Like

so basically discord web3 version

Thank you, @lucascantsleep

Really enjoyed reading through the Pitch Deck. Your proposal is under review. I would like to provide a brief update from Harmony.

All approvals and proposals for DAO Bootstrap Funding are still paused. This is a temporary measure. Please do not let this dissuade you and your team from building. Stay tuned for another update regarding DAO Bootstrap Funding :soon:

note: this comment is not an approval of this proposal.

I would also like to loop in @ElixirofLife to review this as a DAO Tool.

Hello, @lucascantsleep

The Harmony team has decided to decline this proposal without prejudice. Please visit our Q3 and Q4 Execution Plan for more information.

I apologize that this process has been lengthy and drawn-out and I appreciate your patience. Harmony wanted to exhaust every option before responding with a declination. I’m looking forward to your success.

This thread will be closed.

1 Like

This topic was automatically closed after 4 hours. New replies are no longer allowed.