Decentraland DAO Governance dApp

The governance hub for the Decentraland ecosystem. Create and vote on proposals that help shape the future of the metaverse via the Decentraland DAO (Decentralized Autonomous Organization).

Setup

Before you start make sure you have installed:

Node version

use node >= 16

If you are starting from scratch and you don't have Node installed in your computer, we recommend using a Node version manager like nvm to install Node.js and npm instead of the Node installer.

nvm install v16.14.2 will install node version 16 and the corresponding npm version.

NOTE

If you are using WSL (Windows Subsystem for Linux) as your development environment, clone the repository into the WSL filesystem. If you clone it inside the Windows filesystem, the project will not work.

Run npm install to install all the dependencies needed to run the project.

Environment setup

Create a copy of .env.example and name it as .env.development

  cp .env.example .env.development

to know more about this file see the documentation

If you are running this project locally you only need to check the following environment variables:

CONNECTION_STRING: make sure it is point to a valid database
COMMITTEE_ADDRESSES: list of eth addresses separated by , that will be able to enact finished proposals
DISCOURSE_API_KEY: the api key use to publish the proposals on the forum
RPC_PROVIDER_URL: the rpc provider to get the latest block
Snapshot env vars: see snapshot setup

These environment variables are used by the application backend. The environment variables for the frontend are located in src/config/env.

Setup the required voting power to pass

The minimum amount of voting power require to pass a proposal of each type it's defined in these variables, if they are not defined or are not numbers 0 will be used instead

  GATSBY_VOTING_POWER_TO_PASS_LINKED_WEARABLES=0
  GATSBY_VOTING_POWER_TO_PASS_CATALYST=0
  GATSBY_VOTING_POWER_TO_PASS_BAN_NAME=0
  GATSBY_VOTING_POWER_TO_PASS_POI=0
  GATSBY_VOTING_POWER_TO_PASS_POLL=0

Database setup

Make sure you have Postgres running.

To create the db, run in the terminal

createdb -U YOUR_USER snapshot

The default postgres user is postgres or your username and the default password is postgres.

Use your user and password for the connection string variable, it should look like this:

postgres://YOUR_USER:YOU_PASSWORD@localhost:5432/snapshot

Once you have a CONNECTION_STRING you can setup your database tables using the following command:

npm run migrate up

Snapshot Setup

GATSBY_SNAPSHOT_SPACE: the snapshot space where the proposals will be published
SNAPSHOT_PRIVATE_KEY, GATSBY_SNAPSHOT_ADDRESS: a pair address/key with permissions to publish at that snapshot space
The configured SNAPSHOT_PROPOSAL_TYPE for the project is 'single-choice', which means each voter may select only one choice. See available voting systems

Creating a Snapshot space

You are going to need to register an ENS name in the network you'll create the space in. For this purpose, you are going to need ETH / Rinkeby ETH / Goerli ETH. Use the faucets to get it:

Rinkeby Faucet

Goerli Faucet

Then follow instructions on Snapshot

Strategy

DCL Governance uses several strategies:

{
  "symbol": "VP (delegated)",
  "strategies": [
    {
      "name": "erc20-balance-of",
      "params": {
        "symbol": "MANA",
        "address": "0x The address of the token contract on the network you are using", 
        "decimals": 18
      }
    }
  ],
  "delegationSpace": "yourEnsName.eth"
}

erc721-with-multiplier

{
  "symbol": "LAND",
  "address": "0xf87e31492faf9a91b02ee0deaad50d51d56d5d4d",
  "multiplier": 2000
}

erc721-with-multiplier

{
"symbol": "NAMES",
"address": "0x2a187453064356c898cae034eaed119e1663acb8",
"multiplier": 100
}

decentraland-estate-size

{
"symbol": "ESTATE",
"address": "0x959e104e1a4db6317fa58f8295f586e1a978c297",
"multiplier": 2000
}

-multichain

{
  "name": "multichain",
  "graphs": {
    "137": "https://api.thegraph.com/subgraphs/name/decentraland/blocks-matic-mainnet"
  },
  "symbol": "MANA",
  "strategies": [
    {
      "name": "erc20-balance-of",
      "params": {
        "address": "0x0f5d2fb29fb7d3cfee444a200298f468908cc942",
        "decimals": 18
      },
      "network": "1"
    },
    {
      "name": "erc20-balance-of",
      "params": {
        "address": "0xA1c57f48F0Deb89f569dFbE6E2B7f46D33606fD4",
        "decimals": 18
      },
      "network": "137"
    }
  ]
}

If you need MANA for testing you can get it by interacting with the contract on etherscan

Rinkeby FakeMana

Goerli FakeMana

Connect your wallet and use the setBalance method on the Contract -> Write Contract section

to (address) is your address
amount (uint256) is whatever you want. Take into account that 1000000000000000000 = 1 MANA

Take into account that the voting power distribution response from snapshot returns an array with each voting power. The order in which each value is returned depends on the order in which strategies are added to the space on the space settings

Current Strategies Order

WMANA
LAND
ESTATE
MANA
NAMES
DELEGATED
WEARABLE

Run Tests

to run the tests you can do

npm test

or create a run configuration in your IDE with jest --no-cache --no-watchman --runInBand

Also, you can try adding the --verbose option.

The --runInBand parameter runs the tests in a single thread, which is usually faster, but you can try without it and see what works best for you.

Run

once you setup this project you can start it using the following command

  npm start

Note 1: this project run over https, if it is your first time you might need to run it with sudo

Note 2: you can disabled https removing the --https flag in the develop script of your package.json

the app should be running at https://localhost:8000/

Clear

To clear cache and update localization and internationalization renders, run

npm run clean

rm -r .cache

Project's structure

You can find a full documentation about the project's structure in the decentraland-gatsby repository

back and front ends

this project runs gatsby as front-end and a nodejs server as back-end both connected through a proxy

locally this proxy is defined in gatsby-config.js (proxy prop)
at servers this proxy is defined in Pulumi.ts (servicePaths prop)

routes

front-end routes are defined using gatsby routes + gatsby-plugin-intl, you can find each page in the src/pages directory

back-end routes are defined using express you can find each route in src/entities/{Entity}/routes.ts and those are imported at src/server.ts

Types and Utils

Types and Utils contain functions and types that will be accessible to both the backend and the frontend.

Be careful with what goes in here, because when webpack tries to compile everything for the frontend it won't have all the backend dependencies, which could result in an error (e.g. ERROR #98123 WEBPACK)

About proposals statuses

Proposals are created in pending, and automatically passed to active
After a voting period of 1 week, they are automatically marked as finished, passed, or rejected, depending on the kind of proposal and of the voting results.
If proposal is in finished status, a committee user can pass/reject it, with a comment.
Once passed, a proposal can be enacted by a committee user, with a comment.

About voting results

Voting results are calculated in two different ways, for different purposes:
- Votes/utils.ts calculates the results in a user-friendly way, so they can be displayed in the frontend. These results are rounded up for clarity.
- Proposal/jobs.ts has a more exact calculation, and is used to evaluate the real result of the voting

Copyright & License

This repository is protected with a standard Apache 2 license. See the terms and conditions in the LICENSE file.

GeeksCapital/governance