Update MVP.md #3
Conversation
Cimply, i've highlighted the direction which I think is compatible with unlock protocol, and the use of sourceCred to replace onerous quarterly or weekly voting with low-cost but weak signals via discobot likes/gifts. The actual discobot `lexy` is yet to be grown so it is a medium term goal but the point is to send l'externs on quests to other DAOs and in return standup guests from say TokenEngineering Communiy or Bankless in rogue 1.x cross-skilling (legal philosophy, basic e-contracts etc)
There was a problem hiding this comment.
@drllau I've made comments and thank you for your thoughts. You've started a great dialogue.
| # 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; |
There was a problem hiding this comment.
Can we say something like "member - annual fixed subscription pegged to a firm USD value but payable in multiple currencies both digital and fiat."
| 1. mmmber - annual fixed subscriptionin fiat but payable in stablecoins; | ||
| - 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) |
There was a problem hiding this comment.
I'd like to move this out from a Membership oriented topic to a topic related to roles and priviledges
| - 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) | ||
| 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 |
| - 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. |
There was a problem hiding this comment.
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.
|
|
||
| # solutiion = Fostering Interaction | ||
|
|
||
| In addition to `CRED` which is the paidup membership token, we use sourceCred to |
There was a problem hiding this comment.
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.
Cimply, i've highlighted the direction which I think is compatible with unlock protocol, and the use of sourceCred to replace onerous quarterly or weekly voting with low-cost but weak signals via discobot likes/gifts.
The actual discobot
lexyis yet to be grown so it is a medium term goal but the point is to send l'externs on quests to other DAOs and in return standup guests from say TokenEngineering Communiy or Bankless in rogue 1.x cross-skilling (legal philosophy, basic e-contracts etc)