No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
sndurkin and marcopeereboom [www] Add admin ability to lock users. (#541)
* [www] Fix a couple issues with dataload util.

* [www] Add admin ability to lock users.
Latest commit f63e36f Oct 18, 2018


Build Status ISC License

Politeia is the Decred proposal system. Politeia is a system for storing off-chain data that is both versioned and timestamped, essentially “git, a popular revision control system, plus timestamping”. Instead of attempting to store all the data related to Decred’s governance on-chain, we have opted to create an off-chain store of data that is anchored into Decred’s blockchain, minimizing its on-chain footprint.

The politeia stack is as follows:

~~~~~~~~ Internet ~~~~~~~~~
|      politeia www       |
|        politeiad        |
|       git backend       |
~~~~~~~~ Internet ~~~~~~~~~
|        dcrtimed         |


Core components

  • politeiad - Reference server daemon.
  • politeiawww - Web backend server; depends on politeiad.

Tools and reference clients

Note: politeiawww does not provide HTML output. It strictly handles the JSON REST RPC commands only. The GUI for politeiawww can be found at:


1. Install Go, dep, and Git.

Make sure each of these are in the PATH.

2. Clone this repository.

3. Setup configuration files:

politeiad and politeiawww both have configuration files that you should set up to make execution easier. You should create the configuration files under the following paths:

  • macOS

    /Users/<username>/Library/Application Support/Politeiad/politeiad.conf
    /Users/<username>/Library/Application Support/Politeiawww/politeiawww.conf
  • Windows

  • Ubuntu


Copy and change the sample-politeiawww.conf and sample-politeiad.conf files.

You can also use the following default configurations:




rpccert="/Users/<username>/Library/Application Support/Politeiad/https.cert"

Things to note:

  • The rpccert path is referencing a macOS path. See above for more OS paths.

  • politeiawww uses an email server to send verification codes for things like new user registration, and those settings are also configured within politeiawww.conf. The current code should work with most SSL-based SMTP servers (but not TLS) using username and password as authentication.

4. Build the programs:

cd $GOPATH/src/
dep ensure && go install -v ./...

5. Start the politeiad server by running on your terminal:


6. Download politeiad's identity to politeiawww:

politeiawww --fetchidentity

Accept politeiad's identity by pressing Enter.

The result should look something like this:

2018-08-01 22:48:48.468 [INF] PWWW: Identity fetched from politeiad
2018-08-01 22:48:48.468 [INF] PWWW: Key        : 331819226de0270d0c997749ce9f2b56bc5aed110f57faef8d381129e7ee6d26
2018-08-01 22:48:48.468 [INF] PWWW: Fingerprint: MxgZIm3gJw0MmXdJzp8rVrxa7REPV/rvjTgRKefubSY=
2018-08-01 22:48:48.468 [INF] PWWW: Save to /Users/<username>/Library/Application Support/Politeiawww/identity.json or ctrl-c to abort

2018-08-01 22:49:53.929 [INF] PWWW: Identity saved to: /Users/<username>/Library/Application Support/Politeiawww/identity.json

7. Start the politeiawww server by running on your terminal:


Awesome! Now you have your Politeia servers up and running!

At this point, you can:

  • Follow the instructions at decred/politeiagui to setup Politeia and access it through the UI.
  • Use the politeiawwwcli tool to interact with politeiawww.
  • Use the politeia tool to interact directly with politeiad.
  • Use any other tools or clients that are listed above.

Further information


This politeiawww feature prevents users from submitting new proposals and comments until a payment in DCR has been paid. By default, it needs a transaction with 2 confirmations to accept the payment.

Setting up the paywall requires a master public key for an account to derive payment addresses. You may either use one of the pre-generated test keys (see sample-politeiawww.conf) or you may acquire one by creating accounts and retrieving the public keys for those accounts:

Put the result of the following command as paywallxpub=tpub... in politeiawww.conf:

dcrctl --wallet --testnet createnewaccount politeiapayments
dcrctl --wallet --testnet getmasterpubkey politeiapayments

If running with paywall enabled on testnet, it's possible to change the minimum blocks required for accept the payment by setting minconfirmations flag for politeiawww:

politeiawww --minconfirmations=1
Paywall with politeiawww_refclient

When using politeiawww_refclient, the -use-paywall flag is true by default. When running the refclient without the paywall, set -use-paywall=false, but note that it will not be possible to test new proposals and comments or the admin flag.

  • To test the admin flow:
  • Run the refclient once with paywall enabled and make the payment.
  • Stop politeiawww.
  • Set the user created in the first refclient execution as admin with politeiawww_dbutil.
  • Run refclient again with the email and password flags set to the user created in the first refclient execution.

Integrated Projects / External APIs / Official URLs

Library and interfaces

  • politeiad/api/v1 - JSON REST API for politeiad clients.
  • politeiawww/api/v1 - JSON REST API for politeiawww clients.
  • util - common used miscellaneous utility functions.


nginx reverse proxy sample (testnet)

# politeiawww
location /api/ {
	# disable caching
	expires off;

	proxy_set_header Host $host;
	proxy_set_header X-Forwarded-For $remote_addr;
	proxy_set_header Upgrade $http_upgrade;
	proxy_set_header Connection "upgrade";
	proxy_bypass_cache $http_upgrade;

	proxy_http_version 1.1;
	proxy_ssl_trusted_certificated /path/to/politeiawww.crt;
	proxy_ssl_verify on;

# politeiagui
location / {
	# redirect not found
	error_page 404 =200 /;
	proxy_intercept_errors on;

	# disable caching
	expires off;

	proxy_set_header Host $host;
	proxy_set_header X-Forwarded-For $remote_addr;
	proxy_set_header Upgrade $http_upgrade;
	proxy_set_header Connection "upgrade";
	proxy_http_version 1.1;

	# backend