New project: Fair Sharing

Proposal: Fair Sharing

Title: Fair Sharing

Authors: Mike

Date Created: 2023.07.16

TL;DR

Fair Sharing aims to revolutionize human collaboration in the next generation.

It is to reshape the way human collaborate and distribute rewards within a decentralized, remote-first, digital era.

It ensures that contributions are transparently visible and rewards are distributed equitably.

This is achieved through a straightforward formula:

Your rewards = (Your contributions/Total contributions) * Total rewards

How does it work?

  1. Each member of the community:
    1. Records their daily contributions manually.
    2. Evaluates and claims their rewards.
    3. Other members vote on the claimed rewards, providing attestation and validation.
  2. Rewards are automatically allocated based on the proportion of validated contributions.

Mission:

Our mission is to redefine how humans collaborate and allocate rewards in the next generation.

Why us?

We have the experience and insights gained from over a year of experimentation with LXDAO. We have encountered pitfalls that DAOs often face. Our journey has provided us with valuable knowledge.

What sets us apart is our genuine passion for this field.

LXDAO’s mission is to gather the power of buidlers to buidl and support “LX” (valuable) Web3 projects sustainably and welcome 1 billion users into Web3.

Fair sharing is vital for empowering remote collaboration to keep building Public Goods.

Problems

The emergence of future work models, such as open-source communities and DAOs, has presented new challenges in measuring contributions and allocating ownership.

The processes involved in determining individual contributions and distributing ownership are often vague, diverse, and complex.

Consequently, achieving a sense of fairness in the allocation becomes challenging, as it becomes difficult to satisfy the majority and ensure their perception of fairness.

Existing web3 tools primarily focus on SBT (Smart Contracts), NFTs (Non-Fungible Tokens), and tokens. However, these tools tend to oversimplify the complexities of the real world and lack solid evidence or proofs.

Most centralized web2 tools designed for companies are ill-suited for the future. These tools are hierarchical in nature, owned by a select few stakeholders.

Like notion or gSheet are too centralized to address the challenges of contribution measurement and ownership allocation elegantly.

Real use cases

LXDAO Working Group and Projects.

Other potential use cases we have observed in other DAOs.

Similar products

Coordinape: Periodic social judgement determines the allocation (rely on human memory/impression)

SourceCred: Auto record and allocate the creds (e.g. Github, Forum, DC)

Govrn: Mainly focus on attesting contributions

More details of the product research:

Coordinape tryout

SourceCred research report

Govrn

Our Differentiations

  1. Simple and straightforward:
    1. Just a simple and transparent formula for reward allocation: Your reward = (Your contribution/Total contribution) * Total reward.
  2. Flexible and nuanced:
    1. Our approach allows each community member to actively participate in the process. Members record their contributions, evaluate them, and others in the community vote on the validity of those contributions.
    2. Through this deliberative process, a consensus is formed.
    3. Rewards are then automatically allocated based on the proportion of validated contributions, ensuring a fair and inclusive distribution.
  3. Deliberate and multicultural fit:
    1. We understand the importance of accommodating diverse cultures and perspectives within a community.
    2. To facilitate this, our system allows for anonymous voting using Zero-Knowledge technology.
    3. This ensures that individuals can express their opinions and make decisions without fear of bias or external influences, fostering a more inclusive and equitable environment.

Timing

Now is the ideal time for this type of product, as there is currently limited attention being given to the non-financial use case.

However, it is an essential component for the success of DAOs and communities, which are gaining increasing popularity worldwide.

By focusing on this crucial aspect early on, we can position ourselves as leaders in the space and cater to the growing demand for solutions that address collaboration and reward allocation in non-financial contexts.

Product scope and iteration rhythm

One phase per month, one release per week.

Phase Add projects Add contributors Add contributions Analytics dashboard Best practice
1 Add/Edit a project/DAO Creator is admin Connect wallet, Disconnect Proportions members owned LXDAO best practice doc
1 Customize cred token name - Delete, Edit
1 - - Add/Show/Edit rules
1 - - Upvote/Downvote: Like or Suggest more/less
2 Add a sample project/DAO, anyone can start right away Set admin role, customized roles, set base creds
2 - - Content: To (can exclude self); Proof; Creds claimed; Upvote/Downvote; Comment; Auto allocate grant/budget: Gnosis safe or 0xsplit or self written contract
3 Set association relations of projects Set deletion rules (TBD) Add to-do capability, streamline the contribution and validation process
3 - Allow outer community to contribute Anonymous vote (TBD)

Tech arch (TBD and reviewed when get started)

  • Frontend
  • Minimal backend
  • Contract
  • AR
  • EAS
  • ZK (Semaphore)
  • 0xSplit, Gnosis safe, Superfluidintegration
  • PGN integration
  • AA integration
  • Gasless UX (tech TBD)

Team settings

  • 1 Sr. Project Owner + Sr. Product manager for managing progress and handling everything, and product defining
  • 1 UI/UX Sr. Designer
  • 2 Sr. Full Stack for website and integration
  • 1 Sr. contract developer and tech architect
  • 1 Sr. Operation (begin from late phase of project)

Duration and milestones (3-month long)

Time duration: July 24 - Oct 24

  • 1 Week
    • Kick off, assemble the team, PoC of architecture
    • 1 Week, UI/UX finished design, Developers kick off coding
  • 3 Weeks, finish phase 1 feature scope
  • 1 week, bug fixes and launch product, one customers start using it in practice
  • 4 Weeks, iterate phase 2 feature scope, one release per week
  • 4 Weeks, iterate phase 3 feature scope, one release per week

Budgets and distribution

Around 5 people in total, 20 hours/week/person, 25U /hour/person, 20x25x5 ppl x4 weeks = 1w U/LXP/month, for 3 months

In TTL, 3w U/LXP (6:4 U:LXP)

  • Product development: 70%
  • Operation: 30%

Allocation principle: based on contribution and community consensus.

If the work hours can not meet the estimated amount, we will allocate rewards at a discount, e.g. Discount % = TTL hours spent/TTL hours estimated

Revenue distribution

What are the potential benefits and profits of this project’s sustainable design?

  • Grants from EAS, DAO*, GCC
  • SaaS fee from DAO/users
  • Donation to us for each allocation
  • Reputation, as we are a public good driving the development of Web3.

Most of the revenue will be used to iterate this project and cover BD costs.

If we gained any revenue in 3 months, we will deduct the budget applied from LXDAO treasury.

With more revenue comes in, we will discuss sharing and ownership based on the contribution.

As a project initiated in LXDAO, LXDAO will have a fixed 20% ownership by default. The rest 80% will be allocated, but not limited to, early contributors, investors, and future new contributors, etc.

Key results

  • Successful completion of the project, including the website, apps, best practice doc
  • All WG and projects in LXDAO are happy to adopt this product
  • 5 outside projects/communities adopted this product successfully
  • Impact: measured by the number of followers, subscribers, and overall influence
  • Attend the hackathon at ETHGlobal Istanbul Nov, gain good exposure on the conference.

Other goals:

  • 3 DAOs adopted this product with good comments
  • Enlist a prominent DAO KOL as an advisor for this product
  • Gain some grants from DAO*
  • Get listed in doc of EAS
  • Win award at consensys Hackathon
  • Seek for some investment (individual, VC, DAOs, etc.)
  • I agree with the idea.
  • I don’t agree with that idea.
  • I don’t have a problem with that.

0 voters

2 Likes

Sofa!
Best wishes to this cooooooool project!

1 Like

First, AR costs $3000 to $8000 per TB, I dont think any product with this technology will go far.

More details, I cannot imagine any blockchain designer would put all the file data on chain. That’s why I always dislike this AR technology.

Second, for ZK voting. Do we have a solution on this? Or any existing opensourced ZK voting we can integrated? Moreover, 3 months is too limited for any project related to ZK, unless we already have the technology ready.

For the good part, maybe PGN network can bring the smart-contract some rewards. The more people use it, the public good can get more benifit.

1 Like

Thanks for the input above, the tech arch is TBD, will let the architect dev design it then get reviewed by expert working group. (e.g. if we should store data on chain/AR/L2-L1).
ZK anonymous voting is not a must so far, in future we may need it depending on the real use case as we explore. PGN could be selected too when we start working on it.

It looks like a very cool project.

I have some previous experience with similar products. Here are a few suggestions:

  1. Establish specific measurement criteria for different job roles, such as the value points of the product’s requirements, the efficiency of development, and the quality of testing.
  2. Regarding personal contributions, consider assigning corresponding story points to the required items. These story points can serve as indicators when allocating/claiming tasks, making it easier to calculate contribution values in the future.
2 Likes
  1. Establish specific measurement criteria for different job roles, such as the value points of the product’s requirements, the efficiency of development, and the quality of testing.

Yes, this is a good point, the key is measure the result of contribution and gain consensus in the community. Using the cred store is one way to do it.

  1. Regarding personal contributions, consider assigning corresponding story points to the required items. These story points can serve as indicators when allocating/claiming tasks, making it easier to calculate contribution values in the future.

Yeah, this is similar to a bounty task, the task is brokwn down top-down, then the community evaluaite the result then triage on the creds.

Wow, The idea sounds very cool, and it could effectively solve the issue about unreasonable labor hours.
But no offense, I’m confused about the percentage. As the development time extends, the percentage of some positions that are unique and necessary at a period of the project time would get lower and lower, even maybe can’t cover the basic labor hours. It appears to be unfair.
We should consider this case in future plan. My current suggestion is, dividing the project into N phases with milestones, a dedicated pool for each phase.
This approach would ensure that each phase has sufficient resources to support the necessary work.

3 Likes

Good feedback, besides phased budget allocation, we may consider a base income plus bonus to ensure deeply involved collaborators can work in a longer term. It may be fairer to everyone.

rewards?

I intend to highlight some keywords to better define the next generation. For instance, Fair Sharing’s mission is to reshape the way humans collaborate and distribute rewards within a decentralized, remote-first, digital era.

It would be better to be formal for the proposal.

These statements may come across as somewhat vague. It would be beneficial to note that this principle aligns with LXDAO’s mission as well. Fair sharing is vital for sustained remote collaboration, offering a superior solution for the long-term upkeep of Public Goods.

We have not yet obtained their explicit consent for use, as we are still in the conceptual stage. Therefore, I recommend deleting this section.

This portion of the information lacks sufficient detail. If you wish to compare products, it would be advisable to provide more information and specific details, as well as their current status and relevant links.

I believe this one may not be necessary if the community intends to support the project. Feels like a discount on grants? However, establishing ownership is a requisite.

Typically, LXDAO holds around 15% to 30%. We should not allocate the entire 90% to contributors based on proof of work, as we may want to attract some investment and reserve a portion for early contributors. You don’t have to list how to handle the rest 90% here.

We might need to be prepared for it start from now, checking the events, etc.

AR storage isn’t on-chain? Just a storage that you cannot delete or change?

This is just a concept, no need to do it now, or we could you a centralized solution for now. And use zk later for the hackathon.

Good points. These can be further enhanced by implementing flexible time range filters and sharing models.

In your scenario, if you continue to contribute, your percentage will keep increasing. Yes, if many people join the project, your percentage might decrease, BUT it signifies that the project is continually growing in size you might get more rewards.

1 Like

Good and sincere feedbacks, I have updated all the suggestions. Please help check it agaiin.

1 Like

Cool, looks better! Cool, looks better!

1 Like

Currently, the funding setup is for 5 people, but the team configuration is for 6 people, including an operator at a later stage, and whether the operator’s fee is to be applied for additionally at that time, or whether it is included in the proposal.

Others who have not joined the LXDAO notion may not be able to open the reports, I’ve set all your notion reports to public sharing mode.

1 Like

I think it’s possible to find a spot to do a demo show to entice people to use it and test it out

Included in the budget, I will specify it.

Sure, we can also open a twitter space or meeting to showcase the product.

I don’t have any more questions, nice idea!

1 Like

Maybe it could be a way to define special contributions aka. tasks if I can say so, make a fix reward for it, use maybe wonderland AI Chain Task Management to reward or look for things to do aka. contribut and the rewards would be by creating the task already on chain, and when task is done just clame…just a thought

1 Like

Yeah, there are two layers, this is on the business logic layer, we could create different business logic for the use cases to make it easier to use for sure. At the moment, we are making the base layer.