Open cimplylimited opened 5 months ago
For the USPTO, if we have a parallel submission in as collective membership mark, there needs to be a policy as per TMEP §1304.09(d)(ii) Manner of Control
must specify the class of persons intended to be entitled to use the mark, indicating what their relationship to the applicant will be, and the nature of the control the applicant intends to exercise over the use of the mark.
A starting point for conversation is the new LEETH which can be implemented via the hats protocol
Category | Token | Notes |
---|---|---|
Emeritus Member | awarded by acclaimation | honorary only |
Member-in-Principle | LEETH (legacy) | Bar-Rogue HODLer |
Chartered Member | LEETH v2 | Based on legal engineering contributions |
Paidup Member | CRED | Membership fee |
Working for Membership | in lieu of fee | eligible for POAPs |
Constitution outlines this pretty clearly. Would suggest we start there. Thoughts? @drllau
Section 2.1 - Eligibility. Membership as defined in Wyo. Stat. Title 17, Ch. 22 shall be voluntary and application open to any individual of at least 18 years of age whose purpose or intent is to contribute, to build, and to use the services of LexDAO, and is willing to accept the responsibilities and terms of membership.
Section 2.2 - Admission. The membership of LexDAO applicants will be granted or denied by vote, or as otherwise prescribed in the LexDAO Handbook (Operating System), upon the submission of required information on a prescribed application form, paying any required application fee, and contributing to LexDAO, as determined by the membership. LexDAO is a decentralized network of members and may admit or deny admission arbitrarily.
LexDAO will review, and make adjustments to the admission requirements based on its evolving needs. The current path to become a member and to signal members for a vote can be found in the LexDAO Handbook (Operating System), and may be updated from time to time.
Section 2.3 - Responsibilities. By accepting and retaining membership each applicant shall agree to use the services or Platforms of LexDAO on at least an occasional basis. Each member shall keep reasonably current in payment of any dues or membership fees and other financial obligations of membership. Each member shall ensure that they are able to receive communication via the e-mail address provided in their application, by other means provided in the application (including platforms such as Discord, Twitter, Github), or by other acceptable means they provide..
If you are engaging with LexDAO Platforms, you consent to contact and agree to become legally bound by this Agreement as both a LexDAO participant and a "LexDAO Member".
Section 2.4 - Limitations. Status as a LexDAO Member does not (and shall not be deemed to) create, and the LexDAO Membership rights do not (and shall not be deemed to) include, any authority, right or power on the part of a LexDAO Member to act as the agent, representative or attorney of or otherwise act on behalf of LexDAO or any other Member, to bind LexDAO or any other Member to any Contract or Liability or to convey any LexDAO property or any asset, right or property owned or held by or on behalf of LexDAO or any Member. Without limiting the generality of the foregoing, no Member shall be deemed to be the partner of LexDAO or any other Member. No Member shall state, purport, imply, hold out or represent to any person that such Member or any other Member has any such authority, right or power.
To the maximum extent permitted by applicable law, no Member shall be (or shall be deemed to be) liable for any liability of the LexDAO or any other Member. This shall not (and shall not be deemed to) create or imply any obligation of LexDAO or any Member to indemnify or compensate any Member from, or hold any Member harmless against, any Liabilities incurred by such DAO Member under any applicable law, in connection with the Member's participation in LexDAO or otherwise.
Section 2.5 - Revocation or suspension of status. A LexDAO Member may have their membership revoked or suspended through the vote of LexDAO Members or as prescribed in the LexDAO Handbook (Operating System) and may be banned from future membership. Any such revocation, suspension, or ban may be appealed as prescribed in LexDAO Handbook (Operating System) or to membership vote. References herein to the rights and entitlements of members shall be understood to refer only to members in good standing.
Section 2.6 - Access to information. Members shall have access to information concerning the operational and financial affairs of LexDAO. The LexDAO Handbook (Operating System) will describe the manner of access.
Section 2.7 - Settlement of disputes. To the extent allowable by law, all disputes may be settled by membership vote. In any dispute between LexDAO and any of its members or former members which cannot be resolved through informal negotiation, it shall be the policy of LexDAO to prefer the use of mediation whereby an impartial mediator may facilitate negotiations between the parties and assist them in developing a mutually acceptable settlement. Neither party with a grievance against the other shall have recourse to litigation until the matter is submitted to mediation and attempted to be resolved in good faith. All Membership agree that there is a preference to settle disputes amongst members or between members and LexDAO via decentralized dispute mechanisms via smart contract protocols.
Section 2.8 - Transferability of Membership. Membership rights and interests may not be transferred. Any attempted transfer contrary to this section shall be wholly void and shall confer no rights on the intended transferee for member removal.
Section 2.9 - Withdrawal. A member may withdraw at any time upon notice to LexDAO through a vote to withdraw their membership and burn any related token. Said request will not be unreasonably denied and shall be deemed conclusively as the Members intent to withdraw from LexDAO.
This repository is from my private github. I've cloned and moved it to the repository here. The last time this was updated was months back. It does not contain the detailed updates based on the 721 deployment of Unlock protocol. In the coming weeks I will continue to update this document. Please provide comments.