Title: BD3 Proposal Champion: Sanzhi Date: 2023.10.18

TL;DR

A collaboration platform for Web3 organizations and super individuals based on credit mutual evaluation.

基于信用互评的 Web3 组织和超级个体的协作平台

Description

Via BD3,

• Establish standard information criteria necessary for project teams to showcase for collaboration.
• Provide templates for handling collaborative information, enhancing the efficiency of team cooperation.
• Create a social network founded on collaboration and peer review.

The primary objective of BD3 is to forge social networking relationships between project parties and resource parties, aiming to elevate the quality and efficiency of Business Development for project initiators.

We are committed to offering project initiators a platform where they can effectively display their projects to foster better inter-project collaboration and attract potential investors. Concurrently, we aim to present investors with a comparatively secure environment, enabling them to make investments and receive returns. By bridging the divide between project initiators and investors, we promote the establishment of a social network that bolsters project development and collaboration.

Background

The current Web3 project parties face the following issues in their collaborations with other project parties, investment institutions, and DAOs:

• High Costs of Communication and Connection with Unfamiliar Teams

For many organizations, especially smaller-scale teams, establishing contact with external teams through KOLs or other intermediaries is a relatively costly process. This involves not just the costs of information transmission, but also significant time and resource consumption.

• Difficult to Reduce Trust Costs

In collaborations, knowing the reputation and historical records of the other party becomes particularly critical. There are mainly two traditional methods: the first is obtaining endorsements from large KOLs or organizations, and the second is understanding the history of the collaborator through close contacts. However, both methods have their issues. Firstly, they often involve paying a certain proportion of fees, and the information, having been passed through multiple parties, can be unreliable. Secondly, verifying this information requires us to invest more time and resources for confirmation, undoubtedly increasing the cost of collaboration.

• Difficulty in Screening High-quality Projects or Teams

To avoid centralized biases, we should rely more on decentralized methods and the reputation of partners to assess a project or team. In this way, we can more effectively filter out high-quality teams and projects, providing investors with more reliable investment recommendations.

In summary, we need an effective strategy to address these pain points. This involves not only reducing the costs of communicating with unfamiliar teams but, more crucially, establishing a reliable, transparent, and decentralized evaluation system to ensure our collaboration with high-quality teams and projects while minimizing unnecessary costs and risks.

Product Planning and Timeline

In the product's earliest stages, there was no commitment to any salary, but this part of the work cannot be overlooked. Early members' participation and contributions are worth recording and retracing. However, "promoting the long-term development of BD3 and making it a great product" is also our goal.

Thus, the early workload before the LXDAO proposal will be recorded on a retracement basis, and the funds obtained in the LXDAO proposal will be used for product advancement, beta testing, iterative updates, and a three-month operation fund for launching. The injection of funds can concentrate resources on development, launching, and operation. Therefore, early contributions will be retraced and compensated when the second round of funding comes in.

The overall development rhythm is divided into 3 stages:

MVP

1. Connect Wallet
2. Main Page: show all organizations & search
3. Collaboration Hub: Show All Needs
4. Create organization profiles
5. Create Needs
   1. Set partnership Needs
   2. Promotion Needs
   3. Activity Needs
6. My profile Page (can be edit)
   1. Info & social media icon
   2. Post needs (Secondary page)
   3. Participate needs (Secondary page)
   4. Relationship (Secondary page)
7. Others profile Page
   1. Info & social media icon
   2. Post needs (Secondary page)
   3. Participate needs (Secondary page)
   4. Relationship (Secondary page)
8. Relationship networking: partners & partners
9. Set Partnership interaction
10. Collaboration interaction
    1. Needs Creators interaction
       1. Accept Join & Send message onchain(need discuss more)
       2. Reject Join & Send messag
       3. Complete Needs & Send message(Onchain & EAS)
       4. Confirm Complete(Onchain & EAS)
       5. Cancel Needs & Send message (Onchain & EAS)
       6. Send message, if Participants canceled or confirmed - EAS
    2. Needs Participants interaction
       1. Join Needs & Send message(text; once)
       2. Complete Needs & Send message(Onchain & EAS)
       3. Confirm Complete(Onchain & EAS)
       4. Cancel Needs & Send message (Onchain & EAS)
       5. Send message, if Participants canceled or confirmed - EAS
    3. Pay Fee / Ask Fund contract
       1. Lock, wait time, Unlock
11. Logo Branding authorize

First-version

1. Download all partners’ Logo
2. Create individual profile
3. Show comment from organization & individual
4. Relationship networking:
   1. organization & individual：Owner, Operator, Member

Milestone:

Stage 1

• Finalizing design drafts
• Product technical architecture review
• First Version Design confirm
• Develop details:

1. connect wallet(function)
2. Main Page: show all organizations & search(function)
3. Collaboration Hub: Show All Needs(function)
4. Create organization profiles (function)
5. Create Needs (function & UI)
   1. Set partnership Needs
   2. Promotion Needs
   3. Activity Needs
6. My profile Page (can be edit)
   1. Info & social media icon
   2. Post needs (Secondary page)
   3. Participate needs (Secondary page)
   4. Relationship (Secondary page)
7. Others profile Page
   1. Info & social media icon
   2. Post needs (Secondary page)
   3. Participate needs (Secondary page)
   4. Relationship (Secondary page)
8. Collaboration interaction (backend & frontend)

Stage 2

• Second Version Design start
• Research of network and EAS
• Team collaboration adjustments based on LXDAO's PoC.
• Early work records and retrospectives.
• MVP version development, joint debugging.
• Contract development.
• Deployment and testing on the test network.
• Mainnet deployment research: OP, Arb, Ton (ecosystem development, support, user base).
• Market information collection, commencement of first-version design.
• Mainnet deployment.
• Initiation of beta testing.
• Develop details:

1. Connect Wallet (function & UI)
2. Main Page: show all organizations & search (function & UI)
3. Collaboration Hub: Show All Needs (function & UI)
4. Create organization profiles (function & UI)
5. Create Needs (function & UI)
   1. Set partnership Needs
   2. Promotion Needs
   3. Activity Needs
6. My profile Page (can be edit) (function & UI)
   1. Info & social media icon
   2. Post needs (Secondary page)
   3. Participate needs (Secondary page)
   4. Relationship (Secondary page)
7. Others profile Page (function & UI)
   1. Info & social media icon
   2. Post needs (Secondary page)
   3. Participate needs (Secondary page)
   4. Relationship (Secondary page)
8. Relationship networking: partners & partners (function & UI)
9. Set Partnership interaction (function & UI)
10. Collaboration interaction
    1. Needs Creators interaction
       1. Accept Join & Send message onchain(need discuss more)
       2. Reject Join & Send messag
       3. Complete Needs & Send message(Onchain & EAS)
       4. Confirm Complete(Onchain & EAS)
       5. Cancel Needs & Send message (Onchain & EAS)
       6. Send message, if Participants canceled or confirmed - EAS
    2. Needs Participants interaction
       1. Join Needs & Send message(text; once)
       2. Complete Needs & Send message(Onchain & EAS)
       3. Confirm Complete(Onchain & EAS)
       4. Cancel Needs & Send message (Onchain & EAS)
       5. Send message, if Participants canceled or confirmed - EAS
    3. Pay Fee / Ask Fund smart contract
       1. Lock, wait time, Unlock
11. Logo Branding authorize (design & function & UI)

Stage 3

• Market information collection, commencement of first-version design.
• Begin beta testing with 5 project parties for the MVP version.
• Bug fixes, product experience enhancements.
• Finalize first-version design.
• Develop details:

1. Download all partners’ Logo
2. Create individual profile
3. Show comment from organization & individual
4. Relationship networking:
   1. organization & individual：Owner, Operator, Member

Tech Stack

• Front-end
• Back-end
• FFM Recommendation System (TBD)
• Contracts
• AR/IPFS (TBD)
• EAS (TBD)
• Nostr (TBD)
• 0xSplit, Gnosis Safe, Superfluid integration (TBD)
• AA integration (Onboarding UX)
• Gasless user experience (tech TBD)

Team Configuration

• 1 project lead + 1 product manager, responsible for managing progress, handling all affairs, and defining/planning the product.
• 1 senior UI/UX designer.
• 2 senior full-stack developers, responsible for website and integration work.
• 1 senior contract developer and technical architect.
• 1 senior operations personnel (starts in the later phase of the project, budget included).

Budget and Allocation

Some of the following roles may be duplicated.

And stage3 we will try to apply more fund from other way.

| | HC | Rate | hours（per month） | month | Budget（lxpu） | | --- | --- | --- | --- | --- | --- | | Project Lead | 1 | 25 | 40 | 2 | 2000 | | Product design | 1 | 25 | 20 | 2 | 1000 | | UI | 1 | 25 | 40 | 2 | 2000 | | Full-stack developers（frontend） | 1 | 30 | 60 | 2 | 3600 | | Backend | 1 | 30 | 60 | 2 | 3600 | | Contract developer | 1 | 35 | 30 | 2 | 2100 | | Ops/BD | 1～2 | 25 | 60 | 2 | 3000 | | Bounties | | | | | 6000 | | Marketing | | | | | 4000 | | Total | | | | | 27300 |

Allocation principles: Based on contributions and project’s milestone.

If actual work hours fall short of the estimated number, rewards will be distributed at a discount rate, e.g., Discount% = Total time spent/Total estimated time.

Revenue Distribution

What are the potential benefits and profits from this project's sustainable design?

• Ecosystem funding, donations.
• Service fees from DAOs/projects.
• Reputation, as BD3's underlying layer is a public good, advancing Web3 development.
• Investment, being a social platform capable of linking project parties, with immense potential value.

Most revenue will be reinvested into project iterations and covering BD costs. If new funds are introduced within these two months, they will be retrospectively attributed to early contributions and deducted from LXDAO treasury expenses.

By default, as a project initiated within LXDAO, LXDAO holds a fixed 15% ownership. The remaining 85% is allocated among early contributors, investors, future new contributors, etc., but not limited to these.

Key Results

• Successful project completion, including website, apps, best practice documentation, showcasing to potential users/communities.
• All working groups and projects within LXDAO are eager to adopt this product.
• 5 external projects/communities have successfully adopted this product.
• Influence: Measured by the number of followers, subscribers, and overall impact.