Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update MVP.md #3

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update MVP.md #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 26 additions & 1 deletion MVP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
# Introduction
LexDAO has been working for the last two years to try to move into a stable and long-term solution for managing its membership. Our specifications have been developed in the [Readme.md File](https://github.com/cimplylimited/LexDAO-MembershipToken-2023) to determine the base needs for operating a pay-for-membership ecosystem that brings together networks of professionals with non-transferrable "light" credentials. It is easy to take for granted how simple it is to deploy memberships in today's day in age using conventional methods. After all, membership organizations are not a new concept. So one might wonder "how could it take this long to solve something so basic?"
LexDAO has been working for the last two years to try to move into a stable and long-term solution for managing its membership. Our specifications have been developed in the [Readme](https://github.com/cimplylimited/LexDAO-MembershipToken-2023) to determine the base needs for operating a pay-for-membership ecosystem that brings together networks of professionals with non-transferrable "light" credentials. It is easy to take for granted how simple it is to deploy memberships in today's day in age using conventional methods. After all, membership organizations are not a new concept. So one might wonder "how could it take this long to solve something so basic?"

<details><summary><b>TL;DR</b> we insource to <a href="https://unlock-protocol.com/">Unlock Protocol</a></summary>
We have taken extraordinary care to try to find solutions that are complete for the basic specifications we deemed critical to effectively deploying a membership protocol for our organization. We operate a web3 native organization and have attempted to apply some of the core concepts around tokens and blockchains to organize and manage a DAO structure in a smart and thoughtful manner. Therefore, we have gone through a painful process of not "settling" for incomplete solutions, possibly to a fault.

In our discovery process, we've found that the concepts around NFTs fits so naturally to the idea of a validated membership card and yet the web3 ecosystem remains incredibly nascent and difficult to configure for such a baseline use case. Most solutions and options are fundamentally incomplete. There are a number of providers and solutions out there that seem to get most of the way there, but somehow manage to fall short of any number of critical needs which might include payment options, metadata configuration, permission structures, chain compatibility, among others.
Expand All @@ -11,3 +12,27 @@ In all of our investigations to-date, we have discovered one protocol which has

The best solution we have found is a provider known as [Unlock Protocol](https://unlock-protocol.com/) which offers ERC-721 tokens that are fully configurable and can be implemented on a variety of common L1 and L2 blockchains. From a pure functional perspective

</details>

# Problem = Signal 2 Noise Ratio

<details><summary>The tokenomics of LexDAO are simple but the interactions are subtle:</summary>
1. mmmber - annual fixed subscriptionin fiat but payable in stablecoins;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we say something like "member - annual fixed subscription pegged to a firm USD value but payable in multiple currencies both digital and fiat."

- working for membership - a loosely pegged conversion from base membership to LXCHAT, a timebank
- this timebank represents ~15 hrs of sweat as in-kind contribution in lieu of the annual membership subscription
- it is arguable whether these l'externs should have access to all guild channels given the semi-confidential nature of some projects but conceptually they have all access to the same platforms members have (discord, hackMD, github, etc)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to move this out from a Membership oriented topic to a topic related to roles and priviledges

2. guest pass (discord only) - as a privilege members are permitted to issue guest passes for public to participate in special events within discord such as hackathons or study groups
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this idea.

- however most guest passes are automatically granted 4 wks via #introduction or by following the decision tree triage in #find-a-lawyer
- these guest passes are expoential backdown which means the 2nd renewal is at half the time
- they are automatically renewed if they submit a common which is "liked" by a LEETHodler or member performing the druid role (guest concierage)
- however, the same druids have power to revoke such guest privileges upon spam, behaviour contrary to community norms or upon complaint by regular member but which is appealable at @Ops total discretion
3. LEETHodlers are a special case as there were certain historical discussions which grandfathered in certain privileges and retained as result of legacy (beware of cryptowizards for theur anger is slow but revenge is subtle.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to determine the right way to grandfather status from this circle. But I want LEETH to be claimable. Both for new holders who earn the right to claim and old holders who have the right to claim. Claim is the key mechanism here that needs to be structured.

<!-- if people think this is unfair try growing a community of <40 through cryptowinter via unpaid vounteers sacrificing time as busy professionals, then come back to me -->
</details>

# solutiion = Fostering Interaction

In addition to `CRED` which is the paidup membership token, we use sourceCred to
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be smarter to think of cred as reputation and membership as the baseline to be eligible for CRED. I also believe that would be in line with what Jared intended. At least in his larger mission for CRED. We require a reputation system that is separate and distinct from the 721 membership card and which augments a user's reputation. In this process is a substack of ontology and lexicon items that go alongside different permission gates for roles across the org. As well as dashboards that can read and display these attributes clearly to other members.

1. measure github activity
2. /tbd\ passively monitor discord reactions as proxy for "oreference"voting (temp polls etc) on opt-in basis
3. /tbd\ connect the different summon circles for l'externs. We send rogues on quests to other servers and whlist we have ambassaDAOs (formal) or members at other DAOs, it is simply impossible to overwatch all of them manually. Hence as opt-in service, we request l'externs on quests to alter their display name to append`| Le⚔️DAO` so `lexy` our bot-in-training can recognise you and come running to collect evidence of abuse. This is definitely in alpha-testing.