Skip to content

Instantly share code, notes, and snippets.

@jaekwon
Last active January 7, 2025 20:27
Show Gist options
  • Save jaekwon/918ad325c4c8f7fb5d6e022e33cb7eb3 to your computer and use it in GitHub Desktop.
Save jaekwon/918ad325c4c8f7fb5d6e022e33cb7eb3 to your computer and use it in GitHub Desktop.

GOVDAO

Tiers T1, T2, and T3.

T1 is the highest tier, T3 the lowest.

T1: self-selecting "core" with supermajority vote from T1. T2: selected by GovDAO w/ T3 abstaining, with simple majority vote. T3: permissionless invitation from T1 and T2.

The maximum age for any member is 70; after is automatically withdrawn.

T1 membership can only be withdrawn by supermajority vote WITH CAUSE. T2, T3 membership can be withdrawn for any reason.

Voting Power.

In general,

  • a T1 member gets 3 votes.
  • a T2 member gets 2 votes.
  • a T3 member gets 1 vote.

However,

  • T2 class is capped at 2/3 the voting power of T1 class.
  • T3 class is capped at 1/3 the voting power of T1 class.
  • --> T1 1/2, T2 1/3, T3 1/6 (unless...)

Example 1:

  • T1 100 members --> 300 VP, 3 votes per member
  • T2 100 members --> 200 VP, 2 votes per member
  • T3 100 members --> 100 VP, 1 votes per member

Example 2:

  • T1 100 members --> 300 VP, 3 votes per member
  • T2 50 members --> 100 VP, 2 votes per member *
  • T3 10 members --> 10 VP, 1 votes per member *

Example 3:

  • T1 100 members --> 300 VP, 3 votes per member
  • T2 200 members --> 200 VP, 1 votes per member *
  • T3 100 members --> 100 VP, 1 votes per member

Example 4:

  • T1 100 members --> 300 VP, 3 votes per member
  • T2 200 members --> 200 VP, 1 votes per member *
  • T3 1000 members --> 100 VP, 0.1 votes per member *

Basic Membership Requirements

All members must be known identities. T1 members must meet T1,T2,T3 criteria. T2 members must meet T2,T3 criteria. T3 members must meet T3 criteria.

T1 criteria includes expertise in categories, significant contributions, and demonstration of value alignment. T2 criteria includes expertise in categories, continuing contributions. T3 criteria includes expertise in categories, continuing contributions.

T1 and T2 members are added via individual proposals, each with a markdown resume/portfolio application document.

T1 Membership Size

Target is minimum 70 members after 7 years.

If the minimum is not reached, 2 members SHOULD be added every quarter, but 1 new member is tolerated.

If the minimum is not reached, AND 2 years has passed, AND no members are added for the quarter, AND there are Qualified Candidates, 1 Qualified Candidate may be elected by GovDAO, but with T1 abstaining.

If the minimum is not reached, AND 2 years has passed, AND no members are added for the quarter STILL, AND there are Qualified Candidates, AND GNOT-DAO exists and is approved by GovDAO, 1 Qualified Candidate may be elected from GNOTDao.

T2 Membership Size

The T2 membership maximum target is 2 x size(T1).

While size(T2) can be greater than 2 x size(T1), no more members can be added to T2.

There is no minimum size of T2, but the desired minimum size is at least floor(size(T1)/4).

T3 Membership Size

T1 members get 3 invitation points. T2 members get 2 invitation points. T3 members get 1 invitation points.

2 invitation points from 2 members must be delegated for T3 membership. Delegation/invitation can be withdrawn at any time.

Payment

T1 and T2 members may get paid equally, if they are actively working.

The payment itself will be good, but not exceed 90th percentile of senior software architect roles in the highest paid city globally.

The number of members who get paid T1T2PaySize is min(70, T1T2PayCapacity).

T1T2PayCapacity is determined by the size of the GovDAOPayTreasury.

GovDAOPayTreasury is a diversified portfolio with at least 1/3 GNOT, the rest may only be more stable token assets, Bitcoin is allowed.

T1T2PayCapacity is the number of members who can be paid for 7 years.

If GovDAOPayTreasury shrinks, T1T2PaySize may also shrink. Seniority is used to determine pay priority.

All T1 and T2 members who get paid must agree to a conflict of interest and profit sharing policy.

Validators

The GovDAO effective voting power (e.g. 3 points, 2- points, and 1- points) is also used for delegating to at least 70 validators.

The number of validators is determined by GovDAO.

Like the GovDAOPayTreasury, there is a ValidatorTreasury with similar rules.

Forking Gno.land

+1/3 of voting power can create a fork.

All deployed contracts may exist on both forks. (XXX limitations?)

T1,T2,T3 members agree to be exclusive to one fork.

2/3+ of T1 determines which keeps "gno.land", OR, majority of GovDAO keeps "gno.land", OR, both forks must change name, GIVEN THAT all names must be acceptable to NT,LLC if name includes "gno".

GNOTDao

  1. GovDAO T1 membership election, in certain cases where T1 membership is inadequate.
  2. All proposals that involve GNOT inflation, with GovDAO approval, with quorum and supermajority of GNOT holders.

70% airdrop 25% NT,LLC 5% for user acquisition

If GNOTDao exists within 2 years, AND GNOTDao does NOT VETO, 10% more (GNOT/9) can be inflated into a DAO for more user acquisition.

@moul
Copy link

moul commented Oct 23, 2024

To consider:

  • Increasing bonding to register a new validator.
  • Validators to self-register somewhere, then pass KYC or other; and then to become active thanks to the delegation system.
  • How can we rotate T2 to replace the least active individuals with the most active ones?
  • How categories work: how to assess them, how to use them like for antispam/reducing noise?

Challenges:

  • Determine how we will conduct KYC for individuals.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment